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