Jan Engelhardt wrote:
On Friday 2012-09-21 23:31, Linda Walsh wrote:
I have a broadcom 1Gb ethernet card in my server that effectively goes dead in 3.3.x and works in 3.2.28. By 'dead', I mean netlink claims it does not see the device. However, it is seen by "ip" when I list links (but "ip" can't set it up or set an address on it, as I get a message that netlink thinks there is no such device).
Is this perhaps a case where a firmware file is needed, but not available? (There should be a message in dmesg, and if a FW file is really needed, the "kernel-firmware" would be the place to look in.)
Bingo. So why does it need a firmware file post in 3.3 & higher? Or does it -- and if 'it', needs it, why isn't it 'there' (for some value of 'it', 'there')? I know that used to be a kernel op -- to only include drivers not needing firmware... I don't recall changing that option (I don't how it was set, but will look there... )... Weird...found it on my first kernel dissect (message in log)... Was looking for cause of a crash -- Last thing in log was: Oct 4 13:52:50 Ishtar kernel: [985735.911825] INFO: task fetchmail:25872 blocked for more than 120 seconds. Oct 4 13:52:50 Ishtar kernel: [985735.918777] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Then the whole computer hung. ;-/ Always fun here!! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org