Bug#611954: r8169: unable to start network after squeeze upgrade to kernel 2.6.32
I have now bypassed the problem by installing another network interface card. I was able to continue the squeeze upgrade, which is now essentially complete. However the onboard ethernet adaptor is still not working. syslog still contains a message ``eth0: unable to apply firmware patch''. I would like eventually to be able to use the onboard adaptor, but it is no longer urgent. Regards. Gerry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611954: r8169: unable to start network after squeeze upgrade to kernel 2.6.32
On Sun, 2011-08-07 at 11:58 +1000, Gerry Butler wrote: I have a partial upgrade to squeeze and I am unable to continue because there is no network connection. I followed recommendations in squeeze release notes. That is 1. do a minimal upgrade. 2. upgrade kernel and udev. 3. During kernel upgrade, apt-get reported missing firmware files: r8169: rtl_nic/rtl8168d-2.fw and ...-1.fw. 4. While the network connection still existed, I installed firmware-realtek. (I also installed firmware-linux-nonfree, as I was not quite certain at that point which package contained rtl8168d-1|2.fw.) 5. After installing firmware packages, /lib/firmware/rtl_nic/rtl8168d-1|2.fw both exist. 6. After re-booting into squeeze there is no network connection. syslog contains the entries: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded r8169 :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 r8169 :03:00.0: setting latency timer to 64 r8169 :03:00.0: irq 34 for MSI/MSI-X RTL8168d/8111d at 0xc9c44000, 00:24:1d:d2:e6:7b, XID 083000c0 IRQ 34 r8169 :03:00.0: firmware: requesting rtl_nic/rtl8168d-2.fw eth0: unable to apply firmware patch [...] This network controller has firmware in NVRAM (ROM or flash), but it has a bug that means it cannot make a good connection to some other devices. The driver tries to apply a bug fix to it. If this fails, it is *not* a fatal error and the driver should continue to work. What does 'ip link show eth0' report? What does 'ethtool eth0' report? Are there any further kernel log messages referring to eth0 or r8169? Ben. signature.asc Description: This is a digitally signed message part
Bug#611954: r8169: unable to start network after squeeze upgrade to kernel 2.6.32
I have a partial upgrade to squeeze and I am unable to continue because there is no network connection. I followed recommendations in squeeze release notes. That is 1. do a minimal upgrade. 2. upgrade kernel and udev. 3. During kernel upgrade, apt-get reported missing firmware files: r8169: rtl_nic/rtl8168d-2.fw and ...-1.fw. 4. While the network connection still existed, I installed firmware-realtek. (I also installed firmware-linux-nonfree, as I was not quite certain at that point which package contained rtl8168d-1|2.fw.) 5. After installing firmware packages, /lib/firmware/rtl_nic/rtl8168d-1|2.fw both exist. 6. After re-booting into squeeze there is no network connection. syslog contains the entries: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded r8169 :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 r8169 :03:00.0: setting latency timer to 64 r8169 :03:00.0: irq 34 for MSI/MSI-X RTL8168d/8111d at 0xc9c44000, 00:24:1d:d2:e6:7b, XID 083000c0 IRQ 34 r8169 :03:00.0: firmware: requesting rtl_nic/rtl8168d-2.fw eth0: unable to apply firmware patch I cannot complete the squeeze upgrade. Surely I am not the only person with this Gigabyte motherboard to upgrade to squeeze. How did it work for others? What's different about mine? My ethernet adaptor is on the motherboard (Gigabyte GA-P55-UD3P). Processor i7-860. Architecture is amd64. I have a working lenny in another partition on the same computer (which I am using to send this email). It may be useful for comparisons. I have only moderate linux knowledge, so if you ask me to do anything too difficult, don't assume I will know how to do it. I need to make a fairly quick decision whether to revert the squeeze partitions to lenny (using dd partition images I made before starting the upgrade), because the lenny partition I am currently using is designed to support repair work, not to support my normal work. Regards. Gerry -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
