>> # ls /sys/bus/pci/devices/0000:04:00.0 >> broken_parity_status device irq msi_bus reset >> resource2_wc subsystem_device vpd >> class dma_mask_bits local_cpulist net >> resource resource4 subsystem_vendor >> config driver local_cpus remove >> resource0 resource4_wc uevent >> consistent_dma_mask_bits enable modalias rescan >> resource2 subsystem vendor >> >> So I guess I'm missing net:eth0 in that last one? > > Looks that way. > >> >> It's a nearly brand new motherboard: >> >> http://www.newegg.com/Product/Product.aspx?Item=N82E16813128490 >> >> Maybe the r8169 driver hasn't caught up? > > I dunno; you said it worked in 2.6.36, but not in 2.6.38 and 2.6.39, > so that sounds like a regression. I don't know where you'd go from > here. Possibly contact the group that maintains the driver.
Well, I'm getting different behavior from the device on my laptop and on my desktop so I guess the devices are a bit different even though they look the same with lspci. On my laptop, everything is good under 2.6.36 without linux-firmware, on 2.6.39 everything is good as long as I install linux-firmware. On my desktop with linux-firmware, I get eth0 under ifconfig -a and iwconfig, but not ifconfig. On my laptop, it appears under all three. > If you do that, then they'd probably find it helpful if you checked to > see if 2.6.37 worked; that'd let them narow things down a bit. Also, > they'd likely find the relevant lines from "lspci -vv" useful. OK, thanks. - Grant
