kernel-2.6.7-1.494.2.2 and eth0 passive

[tomwitmer]

OK, problem not solved, but here's more light diagnostic info:

• Machine has one ethernet port
• kernel 2.6.7 detects 2, but doesn't identify any hardware with eth1 in the network settings
• kernel 2.6.7 works about 60% of the time
• Rebooting to windows 98, then back to FC2 _always_ triggers this problem
• The only fix is to revert to kernel 2.6.6 and delete and recreate my network settings. Then kernel 2.6.7 works fine.

[crackers]

Originally Posted by tomwitmer

Rebooting to windows 98, then back to FC2 _always_ triggers this problem

This one item makes me think that it's actually a PnP issue - Windows has always relied on it controlling PnP (doing whatever it thinks is right, whether it actually is or not) instead of the BIOS. Linux has relied more on the BIOS handling that - so it seems to me that it's the Windows OS that's screwing things up.

[tomwitmer]

Problem Fixed! Kernel 2.6.8 eliminates the problem completely. Yay!

[crackers]

Side note: seeing all these really wildly different issues has made me glad I didn't go to 2.6.7!

[johnc10]

This problem appears to be a change in acpi for new kernel. I saw this problem on FC3 2.6.9.681_FC3 with "irq 9: Please try booting with acpi=off and report a bug" in /var/log/messges. Kernel 2.6.9.667 works fine.

To turn acpi off at boot, wait for grub menu to appear, press letter "a" key then add

acpi=off

to end of command line, then enter to boot.

If this does cure your problem, then to turn off every boot, edit /boot/grub/menu.lst and add acpi=off to end of kernel line


kernel /vmlinuz-2.6.9-1.681_FC3 ro root=LABEL=/ acpi=off