1 |
Joshua Doll wrote: |
2 |
> Daniel da Veiga wrote: |
3 |
>> On 7/30/07, Albert Hopkins <marduk@g.o> wrote: |
4 |
>> |
5 |
>>> On Mon, 2007-07-30 at 13:33 -0300, Daniel da Veiga wrote: |
6 |
>>> |
7 |
>>>> Hi list, |
8 |
>>>> |
9 |
>>>> I've been struggling with this for a while, I am setting up this new |
10 |
>>>> machine, but got stuck because I can't find a way to make the network |
11 |
>>>> card work... According to lspci: |
12 |
>>>> |
13 |
>>>> 02:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet |
14 |
>>>> Controller (Copper) (rev 03) |
15 |
>>>> |
16 |
>>>> The weird thing is, it works just fine when booting the LiveCD, |
17 |
>>>> dmesg shows: |
18 |
>>>> |
19 |
>>>> Intel(R) PRO/1000 Network Driver - version 7.2.9-k4 |
20 |
>>>> Copyright (c) 1999-2006 Intel Corporation. |
21 |
>>>> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 17 |
22 |
>>>> PCI: Setting latency timer of device 0000:02:00.0 to 64 |
23 |
>>>> e1000: 0000:02:00.0: e1000_probe: (PCI Express:2.5Gb/s:32-bit) |
24 |
>>>> 00:10:c6:a1:5a:41 |
25 |
>>>> e1000: eth0: e1000_probe: Intel PRO/1000 Network Connection |
26 |
>>>> e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex |
27 |
>>>> e1000: eth0: e1000_watchdog: 10/1000 speed: disabling TSO |
28 |
>>>> |
29 |
>>>> but when booting the local kernel: |
30 |
>>>> |
31 |
>>>> Intel(R) PRO/1000 Network Driver - version 7.2.9-k4 |
32 |
>>>> Copyright (c) 1999-2006 Intel Corporation. |
33 |
>>>> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 17 |
34 |
>>>> PCI: Setting latency timer of device 0000:02:00.0 to 64 |
35 |
>>>> e1000: eth0: e1000_probe: Intel PRO/1000 Network Connection |
36 |
>>>> |
37 |
>>> It appears as if driver works and has created the device but... |
38 |
>>> |
39 |
>>> |
40 |
>> |
41 |
>> The device was not created (and yeah, that's weird since there's a |
42 |
>> mention to "eth0" in dmesg), also the init script is there and there |
43 |
>> is a config for the interface at rc.conf/net. It seems the probe is |
44 |
>> not working, as it never detects the link is up or down... |
45 |
>> |
46 |
>> |
47 |
> What does ifconfig -a return? A lot of times udev will "remap" the |
48 |
> device name. Especially if there is IP over firewall. |
49 |
> |
50 |
> |
51 |
> --Joshua Doll |
52 |
Opps firewire not firewall. Long weekend. |
53 |
|
54 |
--Joshua Doll |
55 |
-- |
56 |
gentoo-user@g.o mailing list |