Desperate to replace the 13 year old system used as an HTPC,
based on a Gigabyte Mini-ITX motherboard, I searched for a replacement.

It had to have a PCIe slot to take a Turbosoft DVB-T2 TV card.
It also had to take an AMD Ryzen 7700 7 because I had two brand new and
boxed that I couldn't sell. (Long story).

I found an ASRock B850M Pro-A microATX that seemed perfect. Except!
a microATX is larger than a Min-ITX board.

That turned out not bto matter.

It all went together OK, except the system would not recognise either
of my two Turbosoft TV cards. No manual is supplied with boards these
days so you have to download and print it yourself. Except!

There are no BIOS details in it. I spent many hours trying to tweak BIOS options but the system (Mint 22.3) could not seem to find a fix. In the
end I recruited my pal Hazim, a professional system builder and
debugger. As both TV cards had worked in my other machines, I wondered
if the problem was the motherboard itself.

Hazim, replaced the TV card with a network card. Sure enough, as we
booted up, the device's lamps twinkled. So the motherboard itself was
not faulty.

I had written to Turnosoft technical support. Their suggestion to
change the PCIe socket's link speed frpm Gen1 (my choice), to Gen2 di
not work.

Hazim did not trust Linux so we plugged in his portable Windows 10
portable SSD system and booted on that. It made no difference of course.

Although I did admire Windows driver handling windows. I had forgotten
that it did have some virtues.

Hazim's advice? Don't buy ASRock products. They are the cheapest and it
shows. My experience with motherboards during the last 12 months is
also to avoid ASUS because their boards have no diagnostic lamps. I try
to use Gigabyte because they do, although their user manual is also
spartan on configuring the BIOS but it does have some info.

I hope this helps someone else.

Regards, Alan

--
Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Le 14/05/2026 … 19:53, pinnerite a ‚critÿ:

Desperate to replace the 13 year old system used as an HTPC,
based on a Gigabyte Mini-ITX motherboard, I searched for a replacement.

It had to have a PCIe slot to take a Turbosoft DVB-T2 TV card.
It also had to take an AMD Ryzen 7700 7 because I had two brand new and
boxed that I couldn't sell. (Long story).

I found an ASRock B850M Pro-A microATX that seemed perfect. Except!
a microATX is larger than a Min-ITX board.

That turned out not bto matter.

It all went together OK, except the system would not recognise either
of my two Turbosoft TV cards. No manual is supplied with boards these
days so you have to download and print it yourself. Except!

There are no BIOS details in it. I spent many hours trying to tweak BIOS options but the system (Mint 22.3) could not seem to find a fix. In the
end I recruited my pal Hazim, a professional system builder and
debugger. As both TV cards had worked in my other machines, I wondered
if the problem was the motherboard itself.

Hazim, replaced the TV card with a network card. Sure enough, as we
booted up, the device's lamps twinkled. So the motherboard itself was
not faulty.

I had written to Turnosoft technical support. Their suggestion to
change the PCIe socket's link speed frpm Gen1 (my choice), to Gen2 di
not work.

Hazim did not trust Linux so we plugged in his portable Windows 10
portable SSD system and booted on that. It made no difference of course.

Although I did admire Windows driver handling windows. I had forgotten
that it did have some virtues.

Hazim's advice? Don't buy ASRock products. They are the cheapest and it shows. My experience with motherboards during the last 12 months is
also to avoid ASUS because their boards have no diagnostic lamps. I try
to use Gigabyte because they do, although their user manual is also
spartan on configuring the BIOS but it does have some info.

I hope this helps someone else.

Regards, Alan

think you very mutch !

i never need a led to say me what append !

your analyse is very chort...

what you see when you send this command line :

sudo lspci

and what the manufasturer TV is saying for linux driver ? they are or not ?

if lspci say, " i see it " ! is good !

do you try to find driver source for this tv card ?

i don't like say immediatly bad think about a trademark...how many
pc 'll start day after day because i change my analyse about the problem...




--
Amicalement,

Frenchy Friendly, & French touch !

german

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Thu, 5/14/2026 1:53 PM, pinnerite wrote:

Desperate to replace the 13 year old system used as an HTPC,
based on a Gigabyte Mini-ITX motherboard, I searched for a replacement.

It had to have a PCIe slot to take a Turbosoft DVB-T2 TV card.
It also had to take an AMD Ryzen 7700 7 because I had two brand new and
boxed that I couldn't sell. (Long story).

I found an ASRock B850M Pro-A microATX that seemed perfect. Except!
a microATX is larger than a Min-ITX board.

That turned out not bto matter.

It all went together OK, except the system would not recognise either
of my two Turbosoft TV cards. No manual is supplied with boards these
days so you have to download and print it yourself. Except!

There are no BIOS details in it. I spent many hours trying to tweak BIOS options but the system (Mint 22.3) could not seem to find a fix. In the
end I recruited my pal Hazim, a professional system builder and
debugger. As both TV cards had worked in my other machines, I wondered
if the problem was the motherboard itself.

Hazim, replaced the TV card with a network card. Sure enough, as we
booted up, the device's lamps twinkled. So the motherboard itself was
not faulty.

I had written to Turnosoft technical support. Their suggestion to
change the PCIe socket's link speed frpm Gen1 (my choice), to Gen2 di
not work.

Hazim did not trust Linux so we plugged in his portable Windows 10
portable SSD system and booted on that. It made no difference of course.

Although I did admire Windows driver handling windows. I had forgotten
that it did have some virtues.

Hazim's advice? Don't buy ASRock products. They are the cheapest and it shows. My experience with motherboards during the last 12 months is
also to avoid ASUS because their boards have no diagnostic lamps. I try
to use Gigabyte because they do, although their user manual is also
spartan on configuring the BIOS but it does have some info.

I hope this helps someone else.

Regards, Alan

As an engineer, I don't believe in superstitions.
Just cold hard facts.

Was Secure Boot turned off ?

For video cards, they can be VESA BIOS, they can
be GOP BIOS, they can be GOP BIOS with some
sort of certificate for boot purposes. And even when
you turn off Secure Boot, the Secure Boot system is
not entirely passivated, and a screwed up certificate
store can still influence the way the BIOS behaves
during early POST.

And of course Hazim flashed up the motherboard to the latest BIOS.
While that does not help quite as much on an Asrock product,
it is still the recommended procedure on new computer equipment.
Twenty years ago, our advice was the exact opposite, because
of the risk of brickage, you would not flash the thing. But
today, we are all for flashing of the UEFI BIOS, as that is part of
patching out issues with the Secure Boot (Black Lotus).

A TV Tuner, is not a "key part" of booting anything. It
only comes into play, when the OS comes up. But a historical
observation is, that the BIOS will not only ignore card
types it does not recognize, it will also disable the chip select
such that you cannot try when the system comes up. The gating
the BIOS does, can be quite effective (for the "Plug and Play OS" "Yes" setting).

Now, your system won't have this, but there are an unending
series of possibilities in computers.

https://support.hpe.com/hpesc/public/docDisplay?docId=sd00001068en_us&page=GUID-D347CDE5-AA66-4CF6-BBDE-FDECBDBA3B99.html&docLocale=en_US

"Obtaining UEFI serial output log data"

Since UEFI is its own little OS, you never know what might be
lurking in there, in the way of assistance.

*******

Did you ask your AI, specific and pointed questions about
older cards of a certain "type", regarding compatibility issues ?

The compatibility matrix is quite a mess now, with more
possibilities than I can even generate a table for you.
Just video cards and their GPU, there are well more than
two types involved now. There could be four types or
four possibilities, that affect "compatibility" on new kit.

Legacy VESA
UEFI GOP VBIOS
Both (Hybrid, was supposed to be common)
UEFI GOP with trusted computing certificate <=== don't have details, cannot be positive

If this motherboard is a UEFI only, does it have
"Secure Boot" "No" capability ? Even if we can no longer
have UEFI/CSM systems for maximum flexibility, we at least
need UEFI-SecureBootOff as an option, for our sanity.
There is already some sort of issue where a GPU is not
"trusted" and causes a problem if SecureBoot is ON.

I've already had a PCIe video card rejected, with the
"missing video" error code, and that might be the VBIOS
is the wrong type.

I did not clean this up, but you just need to read the exception
at the bottom, as a possibility. For the most part, the LLM-AI
relies on the pci-sig statements on backward compatibility.

*********************** A Section Of a CoPilot Answer ************************* **Short answer:**
All PCI Express versions from **1.0/1.1 through 5.0** are *intended*
to be electrically and logically backward? and forward?compatible.

### Electrical / Protocol Compatibility Matrix

| Card ? / Slot ? | PCIe 1.0/1.1 | PCIe 2.0 | PCIe 3.0 | PCIe 4.0 | PCIe 5.0 |
|-----------------------|--------------|----------|----------|----------|----------|
| **PCIe 1.0/1.1 card** | ? | ? | ? | ? | ? |
| **PCIe 2.0 card** | ? | ? | ? | ? | ? |
| **PCIe 3.0 card** | ? | ? | ? | ? | ? |
| **PCIe 4.0 card** | ? | ? | ? | ? | ? |
| **PCIe 5.0 card** | ? | ? | ? | ? | ? |

**There are no officially incompatible combinations.**
All versions use the same link?training mechanism (LTSSM), lane negotiation, and fall?back speeds.

## Why compatibility works

PCIe maintains compatibility through:

1. **Link training (LTSSM)**
Every PCIe device and root complex begins at the lowest common denominator and negotiates upward. If a device cannot train at a higher speed, the link falls back automatically.

2. **Same encoding families (with version?specific improvements)**
- PCIe 1.x / 2.x: **8b/10b**
- PCIe 3.0+: **128b/130b**
Even though encoding changes, the negotiation happens *before* high?speed signaling begins.

3. **Same electrical interface**
Signaling amplitude, lane polarity inversion, equalization, and channel requirements evolve, but backward compatibility is preserved by design.

4. **Same software model**
Configuration space, BARs, capabilities, and enumeration remain consistent.

## Known Real?World Exceptions (Vendor Bugs)

These are **not** spec-level incompatibilities - they are implementation defects:

### 1. **Early PCIe 2.0 GPUs failing in PCIe 1.0/1.1 motherboards**
- Some Radeon HD 38xx / 48xx and early NVIDIA 2xx cards failed to train at Gen2 or even Gen1 speeds on older chipsets.
- Vendors issued **VBIOS updates** to force **Gen1 mode** (2.5 GT/s) because the
motherboard?s signal integrity could not meet Gen2 requirements.

*********************** End: A Section Of a CoPilot Answer *************************

Oh, I forgot one other aspect.

When a motherboard has an "excess" of NVMe slots, that excess
comes with "we will disable slot 3 if you put an NVMe
into the bottom connector on the board". There are population
rules, which disable certain slots, as a function of where
you stick NVMe and/or video cards. Let us check your manual now, for this.

Page 4

https://download.asrock.com/Manual/B850M%20Pro-A.pdf

"If M2_3 is occupied, PCIE2 will be disabled"

On a new system, I would be tempted to do test-bringup
while using a SATA drive. Even if you are not booting
from the M2_3 NVMe slot, you MUST remove the NVMe physically,
so it stops flipping the mux the wrong way. The CPU/Chipset
makers are doing us no favours, with all this lane-sharing
crap that disables things. You really have to read the
manual carefully, to "find that one sentence".

Paul

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Le 14/05/2026 … 21:36, Paul a ‚critÿ:

As an engineer, I don't believe in superstitions.
Just cold hard facts.

Was Secure Boot turned off ?
Paul

if you use " secure boot " word immediatly ! sure you are right !

is very important to be a engineer ! and may be to day...if you
give your mind to a iA...sure you 'll better and better !

i think you and your friend are very kendy guys, very all !

so ! we could not to know if the manufacturer do linux driver for
this card ? or if someone in community tux do it ! and may be they
are source, open source...

no we can not ? the first...you suck a copilot ?


--
Amicalement,

Frenchy Friendly, & French touch !

german

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 5/14/26 3:04 PM, George wrote:

22.3 is based on ubuntu 24.4 NOT 26.4 as far as I know.

You're right. "Based On: Ubuntu 24.04 noble" from neofetch. (love that program).

--
Mint 22.3, Thunderbird 140.10.2esr, Firefox 150.0.2
Alan K.

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Alan K. wrote:

"Based On: Ubuntu 24.04 noble" from neofetch. (love that program).

Neofetch gives some quick info; but I LUV the depth and power of inxi.

--
Mike Easter

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Thu, 14 May 2026 20:04:32 +0100
George <invalid@invalid.invalid> wrote:

On 14/05/2026 18:53, pinnerite wrote:

Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda

It is time to change the signature of your posts as you are now using 22.3!

Did you skip 22.2 generation?

22.3 is based on ubuntu 24.4 NOT 26.4 as far as I know.

The messages are on one machine powered by 22.1.
The subject is a different machine powered by 22.3.


--
Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Thu, 14 May 2026 20:54:32 +0200
german newsgroups <usualsuspectrider@gmail.com> wrote:

Le 14/05/2026 ? 19:53, pinnerite a ?crit?:

Desperate to replace the 13 year old system used as an HTPC,
based on a Gigabyte Mini-ITX motherboard, I searched for a replacement.

It had to have a PCIe slot to take a Turbosoft DVB-T2 TV card.
It also had to take an AMD Ryzen 7700 7 because I had two brand new and boxed that I couldn't sell. (Long story).

I found an ASRock B850M Pro-A microATX that seemed perfect. Except!
a microATX is larger than a Min-ITX board.

That turned out not bto matter.

It all went together OK, except the system would not recognise either
of my two Turbosoft TV cards. No manual is supplied with boards these
days so you have to download and print it yourself. Except!

There are no BIOS details in it. I spent many hours trying to tweak BIOS options but the system (Mint 22.3) could not seem to find a fix. In the
end I recruited my pal Hazim, a professional system builder and
debugger. As both TV cards had worked in my other machines, I wondered
if the problem was the motherboard itself.

Hazim, replaced the TV card with a network card. Sure enough, as we
booted up, the device's lamps twinkled. So the motherboard itself was
not faulty.

I had written to Turnosoft technical support. Their suggestion to
change the PCIe socket's link speed frpm Gen1 (my choice), to Gen2 di
not work.

Hazim did not trust Linux so we plugged in his portable Windows 10
portable SSD system and booted on that. It made no difference of course.

Although I did admire Windows driver handling windows. I had forgotten
that it did have some virtues.

Hazim's advice? Don't buy ASRock products. They are the cheapest and it shows. My experience with motherboards during the last 12 months is
also to avoid ASUS because their boards have no diagnostic lamps. I try
to use Gigabyte because they do, although their user manual is also
spartan on configuring the BIOS but it does have some info.

I hope this helps someone else.

Regards, Alan

think you very mutch !

i never need a led to say me what append !

your analyse is very chort...

what you see when you send this command line :

sudo lspci

and what the manufasturer TV is saying for linux driver ? they are or not

?

if lspci say, " i see it " ! is good !

do you try to find driver source for this tv card ?

i don't like say immediatly bad think about a trademark...how many
pc 'll start day after day because i change my analyse about the problem.

..

--
Amicalement,

Frenchy Friendly, & French touch !

german

The driver has to be compiled against the running kernel.
This becomes tedious when sourcev components need editing.
This is irrelevant if the card is not recognised by the machine.

I forgot to mention that it has been tried with CSM enabled and
disabled.

I have a TV card in the machine I am using now. lspci shows:
07:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
When I get time I will compile the drivers against kernel
6.8.0-84-generic as that is known to work.

Regards,
Alan

--
Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Mike Easter wrote:

Alan K. wrote:

"Based On: Ubuntu 24.04 noble" from neofetch. (love that program).

Neofetch gives some quick info; but I LUV the depth and power of inxi.

Oooh. Neofetch has more power than I realized; BUT, I was able to get
inxi to tell me the base for LM, but I couldn't figure out how to get
neofetch to do it.

inxi -Sxx

--
Mike Easter

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 5/15/26 7:31 AM, Mike Easter wrote:

Mike Easter wrote:

Alan K. wrote:

"Based On: Ubuntu 24.04 noble" from neofetch. (love that program).

Neofetch gives some quick info; but I LUV the depth and power of inxi.

Oooh. Neofetch has more power than I realized; BUT, I was able to get
inxi to tell me the base for LM, but I couldn't figure out how to get neofetch to do it.

inxi -Sxx

I've tweaked the hell out of a bash script that calls neofetch and a few others to make
this. I get most of my info in one click.

USER: alan@HP-G11
?ÄÄÄÄÄÄÄÄÄÄÄÄ Software ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³? OS: Linux Mint 22.3 x86_64
³? Kernel: 6.8.0-117-generic
³ Packages: 3419 (dpkg), 5 (flatpak)
³ Shell: bash 5.2.21
³ DE: Cinnamon 6.6.7
³? WM: Mutter (Muffin)
³ Locale: en_US.UTF-8
ÃÄÄÄÄÄÄÄÄÄÄÄÄ Hardware ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³? Host: HP EliteBook 865 16 inch G11 Notebook PC SBKPF,SBKPFV2
³ Memory: 2343MiB / 31364MiB
³ Resolution: 1920x1200
³ CPU: AMD Ryzen 7 PRO 8840U w/ Radeon 780M Graphics (16) @ 5.132GHz
³ GPU: AMD ATI c3:00.0 Phoenix3
³ Disk (/): 33G / 102G (34%)
ÃÄÄÄÄÄÄÄÄÄÄÄÄ Other ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ Uptime: 15 hours, 27 mins
³ Theme: Mint-DarkRed [GTK2/3]
³ Icons: AKorange [GTK2/3]
³ Font: Verdana 16 [GTK2/3]
³? WM Theme: Mint-DarkRed (Mint-Y)
³ Terminal: gnome-terminal
³ Display Manager: lightdm
ÃÄÄÄÄÄÄÄÄÄÄÄÄ Misc ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ System Name: Linux Mint 22.3 (Zena)
³ System installed: 2025-04-29
³ Proc Version: Ubuntu 6.8.0-117.117-generic 6.8.12
³ Display Manager: lightdm
³ Current Lid Action: 'suspend'
³ Thunderbird: Mozilla 140.10.2esr
³ Firefox: 150.0.2
³ Chrome: 148.0.7778.167
³ Wine Version: wine-11.0
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
? ? ? ? ? ? ? ? ? Based On: Ubuntu 24.04 noble


--
Mint 22.3, Thunderbird 140.10.2esr, Firefox 150.0.2
Alan K.

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Le 15/05/2026 … 13:27, pinnerite a ‚critÿ:

The driver has to be compiled against the running kernel.
This becomes tedious when sourcev components need editing.
This is irrelevant if the card is not recognised by the machine.

I forgot to mention that it has been tried with CSM enabled and
disabled.

I have a TV card in the machine I am using now. lspci shows:
07:00.0 Multimedia controller: Philips Semiconductors SAA7160 (rev 03)
When I get time I will compile the drivers against kernel
6.8.0-84-generic as that is known to work.

Regards,
Alan

and...don't forget...try to know we must or not clean the key in TMP ROM
! ? #

hum...i don't all way for secure the boot if we need to signed all !

--
Amicalement,

Frenchy Friendly, & French touch !

german

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Alan K. wrote:

I've tweaked the hell out of a bash script that calls neofetch and a few others to make this.ÿ I get most of my info in one click.

I studied its help to see if there was a way to get neofetch config to
do the base, but I couldn't see doing it there either.

That's a nice info you rigged.

--
Mike Easter

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Thu, 14 May 2026 18:53:33 +0100, pinnerite wrote:

Hazim's advice? Don't buy ASRock products. They are the cheapest and it shows. My experience with motherboards during the last 12 months is
also to avoid ASUS because their boards have no diagnostic lamps.

Haven't they? I think my ASUS PRIME Z690-P D4 has at least two.

--
s|b

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Fri, 5/15/2026 1:01 PM, s|b wrote:

On Thu, 14 May 2026 18:53:33 +0100, pinnerite wrote:

Hazim's advice? Don't buy ASRock products. They are the cheapest and it
shows. My experience with motherboards during the last 12 months is
also to avoid ASUS because their boards have no diagnostic lamps.

Haven't they? I think my ASUS PRIME Z690-P D4 has at least two.

Both my MSI and Asus boards have the four white staging lights.
They're surface mount LEDs.

There are boards with the Port 80 "POST hex display", and Asrock might
be slightly more likely to do one of those. But that would be
a more expensive board. The ones for $250-$300 don't have Port 80
displays on them.

The green "+5VSB LED" is gone from Asus now. That would be lit, as
long as the switch on the back was ON and the PSU +5VSB was working.

Some boards, while the BIOS is being flashed, there
is a single red LED for communications. It has two
flash rates. One rate means "Error!", the second rate
means "I am progressing to program your BIOS chip". The
first time I used that, it was doing the "Error!" thing,
and I didn't know it. Nice.

Paul


--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Fri, 15 May 2026 19:01:08 +0200
"s|b" <me@privacy.invalid> wrote:

On Thu, 14 May 2026 18:53:33 +0100, pinnerite wrote:

Hazim's advice? Don't buy ASRock products. They are the cheapest and it shows. My experience with motherboards during the last 12 months is
also to avoid ASUS because their boards have no diagnostic lamps.

Haven't they? I think my ASUS PRIME Z690-P D4 has at least two.

--
s|b

I have two ASUS_PRIME_X670-P. They doi not have.
Alan

--
Linux Mint 22.1 kernel version 6.8.0-84-generic Cinnamon 6.4.8
AMD Ryzen 7 7700, Radeon RX 6600, 32GB DDR5, 2TB SSD, 2TB Barracuda

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Fri, 15 May 2026 17:54:43 -0400, Paul wrote:

The green "+5VSB LED" is gone from Asus now. That would be lit, as
long as the switch on the back was ON and the PSU +5VSB was working.

I have the green one. I'm pretty sure there's another one that has to do
with RAM.

Any idea why they removed them? I know they removed the speaker (for the
error beeps) as well, but I bought a separate speaker that I could
connect. I like my motherboard to say *BEEP* when it starts.

--
s|b

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Le 17/05/2026 … 16:36, s|b a ‚critÿ:

I have the green one. I'm pretty sure there's another one that has to do
with RAM.

Any idea why they removed them? I know they removed the speaker (for the error beeps) as well, but I bought a separate speaker that I could
connect. I like my motherboard to say*BEEP* when it starts.

beep is beep !

each motherboard have a codex for the beep ! they are chort beep,
loooonng beep !

and they are ECC RAM ! bullshit RAM for me ! R if remember well !
i have some ECC DDR3 if someone need it !!! do offert please !



--
Amicalement,

Frenchy Friendly, & French touch !

german

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Le 17/05/2026 … 17:08, german newsgroups a ‚critÿ:

Le 17/05/2026 … 16:36, s|b a ‚critÿ:

I have the green one. I'm pretty sure there's another one that has to do
with RAM.

Any idea why they removed them? I know they removed the speaker (for the
error beeps) as well, but I bought a separate speaker that I could
connect. I like my motherboard to say*BEEP* when it starts.

beep is beep !

each motherboard have a codex for the beep ! they are chort beep,
loooonng beep !

and they are ECC RAM ! bullshit RAM for me ! R if remember well !
i have some ECC DDR3 if someone need it !!! do offert please !

they are...a long time ago...when...they are led..on a pc portable...
is the genese of micro informatique...this century with virus!!!

:o)

--
Amicalement,

Frenchy Friendly, & French touch !

german

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Sun, 5/17/2026 10:36 AM, s|b wrote:

On Fri, 15 May 2026 17:54:43 -0400, Paul wrote:

The green "+5VSB LED" is gone from Asus now. That would be lit, as
long as the switch on the back was ON and the PSU +5VSB was working.

I have the green one. I'm pretty sure there's another one that has to do
with RAM.

Any idea why they removed them? I know they removed the speaker (for the error beeps) as well, but I bought a separate speaker that I could
connect. I like my motherboard to say *BEEP* when it starts.

When they do CR (cost reduction), anything is possible.

Removing the speaker pin header, would not save much, as
the timer that makes the tone is inside the Southbridge.
There are some "emulated chips" inside modern chippage,
that carry out the exact same functions as 30 years ago.
The timer that makes the beep tone, is one of them.
The timer can be programmed on the fly, to make the
European two-tone police siren noise (which on a PC
means "overheat").

As an example of "cheapness", they removed the header for
setting a USB port to run on +5V or +5VSB. Today, it runs
on +5VSB (good for "wake-from-sleep), but by running off
+5VSB, you only have 2.5A or 3A or so of current available,
which isn't nearly enough for a user with a lot of USB3
peripherals that are bus-powered. Ideally, you would
want some of the USB ports to run off +5V, as there is
20 amps available on that supply, and then you could
run NVME sleds with USB interfaces without worrying about
not-enough-power.

I'm surprised there aren't more reports of ATX supplies
having "stopped charging your phone", when the +5VSB limit
was exceeded.

Paul

--- PyGate Linux v1.5.14
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)