[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#708757: linux-image-3.2.0-4-amd64: via-rhine network card fails to initialise correctly - similar and workaround.



I encountered a similar problem with an Averatec 3270 notebook: ethernet stopped working after upgrading to wheezy, and the 3.2.0-4-686-pae kernel package. I still have the 2.6.32-5-686 kernel installed, and the network adapter does work if I boot it. My final workaround was to install linux-image-3.14-0.bpo.1-686-pae from wheezy-backports, and the adapter does work with it also. So it would appear that the problem is now fixed in the kernel source.

FYI, I did try backporting the module source (via-rhine.c) from the latest (3.15) kernel back into 3.2.0 and rebuilding the via-rhine.ko module, but it didn't compile, and I don't see any point in investigating the source code changes.

From lspci:
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)

Some dmesg output for failing 3.2.0 kernel (it's not reading the MAC address correctly, for one thing):
[    1.298333] via_rhine: v1.10-LK1.5.1 2010-10-09 Written by Donald Becker
[    1.298372] via-rhine 0000:00:12.0: enabling device (0080 -> 0083)
[    1.298409] via-rhine 0000:00:12.0: setting latency timer to 64
[ 1.298431] via-rhine 0000:00:12.0: (unregistered net_device): Woke system up. Reason: Link went down [ 1.298437] via-rhine 0000:00:12.0: (unregistered net_device): Reset not complete yet. Trying harder. [ 1.299778] via-rhine 0000:00:12.0: eth0: VIA Rhine II at 0x11000, 40:80:00:00:20:a0, IRQ 23 [ 1.304266] via-rhine 0000:00:12.0: eth0: MII PHY found at address 68, status 0x0001 advertising 0001 Link

For the 3.14.0 kernel:
[    1.356702] via_rhine: v1.10-LK1.5.1 2010-10-09 Written by Donald Becker
[    1.371223] via-rhine 0000:00:12.0: enabling device (0080 -> 0083)
[ 1.371223] via-rhine 0000:00:12.0: e[ 1.410064] via-rhine 0000:00:12.0 eth0: VIA Rhine II at 0x11800, 00:40:45:26:87:72, IRQ 23 [ 1.410841] via-rhine 0000:00:12.0 eth0: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 00


Reply to: