https://bugzilla.novell.com/show_bug.cgi?id=437611 User lzw77rnc@gmx.at added comment https://bugzilla.novell.com/show_bug.cgi?id=437611#c6 --- Comment #6 from Alexander Oberhuber <lzw77rnc@gmx.at> 2008-11-05 16:00:54 MST --- Sorry, but... Directly connected to my 8139-ethernet-card is a ARRIS cable modem, model CM450B. It has a ethernet-led, which keeps blinking fast (3 times a sec, approx.) whenever the ethernet connection works, and which stays dark otherwise. Normally, if the cable modem is turned on first, as soon as I switch on the computer, the ethernet LED (of the cable modem) goes on and everything works. But booting some Linux distros, the cablemodem ethernet LED stays off and then I get the famous "Destination host unreachable" error. The only Linux distro and kernel that gets the cablemodem LED _ON_ is "Trinity Rescue Kit 3.3" and it KEEPS staying on even if I reboot and insert another CD of another Linux distro (www.grml.org, www.slax.org, etc.etc.) It is my wild guess that the Trinity Rescue Kit Kernel does just sort of "wake up" the ethernet card. It does so at a very early stage of booting - the cablemodem LED goes on immidately after booting the kernel image file, even before the kernel spits out the first message. I guess it is just setting one single "Wakeup-signal" using SETPCI, but I'm not sure about it. I will reboot and LSPCI and compare several LSPCI outputs whenever the netcard and the cable modem are in "proper" state and when they are in "non-proper" state. The "proper" state, once initialized by Trinity Rescue Kit 3.3, remains, even when hard-resetting the computer with the reset button. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.