On Mon, 2010-12-13 at 10:05 +0100, Jon Black wrote: > On Mon, 13 Dec 2010 02:11 +0000, "Ben Hutchings" <ben@decadent.org.uk> > wrote: > > On Sun, 2010-12-12 at 13:51 +0100, Jon Black wrote: > > [...] > > > The following output is from dmesg after running 'modprobe -r r8169; > > > modprobe r8169': > > > > > > udev[76]: starting version 163 > > > r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded > > > r8169 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > > > r8169 0000:01:00.0: setting latency timer to 64 > > > r8169 0000:01:00.0: irq 28 for MSI/MSI-X > > > eth0: RTL8168d/8111d at 0xf7c62000, <what-looks-like-a-mac-address>, > > > XID 081000c0 IRQ 28 > > > r8169 0000:01:00.0: firmware: requesting rtl8168d-1.fw > > > eth0: unable to apply firmware patch > > > > > > This last line doesn't appear during boot. > > > > Does eth0 exist after this? Does anything else appear in the log? > > No, there is neither eth0 in ifconfig output nor any other messages in > the dmesg log. Wait, did you use just 'ifconfig' or 'ifconfig -a'? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part