@Chase Douglas:

Something fishy may be going on...those debug messages weren't
triggered.

I used:
patch < firmware.sh.patch
modprobe -r e100
modprobe e100
tail /var/log/syslog

which showed:
Mar  2 14:37:04 SERVER1 kernel: [407483.499357] e100: Intel(R) PRO/100 Network 
Driver, 3.5.24-k2-NAPI
Mar  2 14:37:04 SERVER1 kernel: [407483.499370] e100: Copyright(c) 1999-2006 
Intel Corporation
Mar  2 14:37:04 SERVER1 kernel: [407483.499499] e100 0000:00:07.0: PCI->APIC 
IRQ transform: INT A -> IRQ 23
Mar  2 14:37:04 SERVER1 kernel: [407483.522448] e100 0000:00:07.0: PME# disabled
Mar  2 14:37:04 SERVER1 kernel: [407483.524914] e100: eth0: e100_probe: addr 
0xfe87f000, irq 23, MAC addr 00:e0:81:29:37:a0

but none of your extra debug tracing. A full reboot shouldn't be needed
to trigger the firmware loader, should it?

-- 
e100: eth0: e100_request_firmware: Failed to load firmware "e100/d101m_ucode.bin
https://bugs.launchpad.net/bugs/530348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to