Hi All,

Had a customer yesterday whose networking, both wireless and
wired would not work. Cable disconnected. Huh. Could not
find anything wrong, so to check the hardware, I booted into
a Fedora Live USB. Networking worked fine, so not a hardware
issue. So back down and into Windows to continue troubleshooting
again. But this time the networking worked fine (yes I had rebooted
the computer several time in windows before going into Fedora).
Hmmm.

I had not seen this for several year. but as far as I can tell
Windows takes hardware states for granted and Linux does not.
So Linux set the hardware states correctly for me automatically
and now Windows is working fine.

My favorite spins:

https://fedoraproject.org/spins/xfce
https://fedoraproject.org/spins/mate

Mate is a little bit easier to use.

My favorite cutting software for the above: https://github.com/FedoraQt/MediaWriter/releases

-T

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 5/3/2024 6:51 PM, T wrote:

Hi All,

Had a customer yesterday whose networking, both wireless and
wired would not work.  Cable disconnected.  Huh.  Could not
find anything wrong, so to check the hardware, I booted into
a Fedora Live USB.  Networking worked fine, so not a hardware
issue.  So back down and into Windows to continue troubleshooting
again.  But this time the networking worked fine (yes I had rebooted
the computer several time in windows before going  into Fedora).
Hmmm.

I had not seen this for several year. but as far as I can tell
Windows takes hardware states for granted and Linux does not.
So Linux set the hardware states correctly for me automatically
and now Windows is working fine.

My favorite spins:

https://fedoraproject.org/spins/xfce
https://fedoraproject.org/spins/mate

Mate is a little bit easier to use.

My favorite cutting software for the above: https://github.com/FedoraQt/MediaWriter/releases

-T

I have not been able to get my RealTek NIC working, switched
back and forth (works on Linux), still did not work on Windows.
Replaced with Intel NIC, which works. My ASIX USB3-GbE adapter
also worked at the time, when the RealTek would not. No change
in driver, driver several years old.

Not all Windows issues resolve, so it's not a "state" problem.
I'd cycled power, I'd reinstalled the driver, I tried older driver,
then newer driver, all the usual rubbish. There were two Windows OSes
on the SSD, same symptoms on both.

It could always be an issue with Windows Defender, or it could
actually be a problem with core networking (like the recently
reported VPN issue), but it always seemed to happen at the
two minute mark (which is roughly when "delayed" services are started).

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

T <T@invalid.invalid> wrote:

Had a customer yesterday whose networking, both wireless and
wired would not work. Cable disconnected. Huh. Could not
find anything wrong, so to check the hardware, I booted into
a Fedora Live USB. Networking worked fine, so not a hardware
issue. So back down and into Windows to continue troubleshooting
again. But this time the networking worked fine (yes I had rebooted
the computer several time in windows before going into Fedora).
Hmmm.

I had not seen this for several year. but as far as I can tell
Windows takes hardware states for granted and Linux does not.
So Linux set the hardware states correctly for me automatically
and now Windows is working fine.

Hardware can get into an unknown state which won't work with the normal commands sent to it. I've run across this with defective drivers. You
need to do a *cold* boot of the computer, not a restart (warm reboot).
A cold boot will have the CPU issue a Reset signal to all hardware to
force into a known initial state.

You didn't say if you did a warm or cold boot of the computer. A cold
boot is needed to get the Reset signal sent to all hardware. A warm
reboot restarts the OS without fully powering off. A cold boot powers
off the hardware which gets a CPU reset sent to hardware on power up. A
cold boot also ensures memory is cleared on the OS load. No
oddball/corrupted memory images of drivers or programs. A cold boot
takes longer, because the BIOS/UEFI has to go through the power-on
self-tests (POST).

When you cold boot, you'll see the keyboard LEDs flash. That's the
keyboard getting the reset signal.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 5/3/24 23:36, VanguardLH wrote:

T <T@invalid.invalid> wrote:

Had a customer yesterday whose networking, both wireless and
wired would not work. Cable disconnected. Huh. Could not
find anything wrong, so to check the hardware, I booted into
a Fedora Live USB. Networking worked fine, so not a hardware
issue. So back down and into Windows to continue troubleshooting
again. But this time the networking worked fine (yes I had rebooted
the computer several time in windows before going into Fedora).
Hmmm.

I had not seen this for several year. but as far as I can tell
Windows takes hardware states for granted and Linux does not.
So Linux set the hardware states correctly for me automatically
and now Windows is working fine.

Hardware can get into an unknown state which won't work with the normal commands sent to it. I've run across this with defective drivers. You
need to do a *cold* boot of the computer, not a restart (warm reboot).
A cold boot will have the CPU issue a Reset signal to all hardware to
force into a known initial state.

You didn't say if you did a warm or cold boot of the computer. A cold
boot is needed to get the Reset signal sent to all hardware. A warm
reboot restarts the OS without fully powering off. A cold boot powers
off the hardware which gets a CPU reset sent to hardware on power up. A
cold boot also ensures memory is cleared on the OS load. No oddball/corrupted memory images of drivers or programs. A cold boot
takes longer, because the BIOS/UEFI has to go through the power-on
self-tests (POST).

When you cold boot, you'll see the keyboard LEDs flash. That's the
keyboard getting the reset signal.

It was a laptop. I always disable Fast Startup. The
tip off is when you can't get into BIOS. Cold
booting a laptop can be "interesting" as you have
to disconnect the power and remove the, often bolted
in now a days, battery.

I rebooted with
<win><R> shutdown /r /f /t 00
I realize you don't have to do that anymore, but
I just like to. It the removes the "it was suppose
to work this way" issues with restart.

To get into booting of the Fedora stick, I just
did a power off. Apparently I had previously
set their BIOS up to do that. They are a 25 year
customer.

Ferengi Rule Of Acquisition #57:
"Good customers are as rare as latinum. Treasure them"

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)