> i wasn't aware that this chip was associated with this bug.
It wasn't until now. Or do you mean that this bug report is meant to cover only
specific chips? From the description and comments I thought it was a generic
bug covering 70-persistent-net.rules incrementing incorrectly on any net
hardware, but I can move to a different bug (or file a new one)
if you prefer.
I'm attaching the full dmesg log. The part where the net card is
initialized and the MAC address printed is:
[ 0.475359] via-rhine: Broken BIOS detected, avoid_D3 enabled.
[ 0.475436] via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker
[ 0.475512] via-rhine 0000:00:12.0: PCI INT A -> Link[LNKA] -> GSI 10
(level, low) -> IRQ 10
[ 0.479677] eth0: VIA Rhine II at 0xe8101000, 00:50:8d:c0:b9:30, IRQ 10.
[ 0.480447] eth0: MII PHY found at address 1, status 0x786d advertising 05e1
Link 45e1.
ifconfig for the card is:
eth0 Link encap:Ethernet HWaddr 00:50:8d:c0:b9:30
inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::250:8dff:fec0:b930/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:257 errors:0 dropped:0 overruns:0 frame:0
TX packets:264 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:117439 (117.4 KB) TX bytes:23805 (23.8 KB)
Interrupt:10 Base address:0x8000
MAC is 00:50:8d:c0:b9:30 in both.
I didn't quite follow the forcedeth discussion earlier in the bug. Isn't
forcedeth some kind of nvidia thing? I don't have any nvidia here.
Should I try installing forcedeth-dkms anyway?
** Attachment added: "dmesg.out"
http://launchpadlibrarian.net/24213328/dmesg.out
--
Ethernet device's number increases by one after every reboot
https://bugs.launchpad.net/bugs/153727
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
