On 7/30/07, Joshua Doll <[EMAIL PROTECTED]> wrote: > Joshua Doll wrote: > > Daniel da Veiga wrote: > >> On 7/30/07, Albert Hopkins <[EMAIL PROTECTED]> wrote: > >> > >>> On Mon, 2007-07-30 at 13:33 -0300, Daniel da Veiga wrote: > >>> > >>>> Hi list, > >>>> > >>>> I've been struggling with this for a while, I am setting up this new > >>>> machine, but got stuck because I can't find a way to make the network > >>>> card work... According to lspci: > >>>> > >>>> 02:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet > >>>> Controller (Copper) (rev 03) > >>>> > >>>> The weird thing is, it works just fine when booting the LiveCD, > >>>> dmesg shows: > >>>> > >>>> Intel(R) PRO/1000 Network Driver - version 7.2.9-k4 > >>>> Copyright (c) 1999-2006 Intel Corporation. > >>>> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 17 > >>>> PCI: Setting latency timer of device 0000:02:00.0 to 64 > >>>> e1000: 0000:02:00.0: e1000_probe: (PCI Express:2.5Gb/s:32-bit) > >>>> 00:10:c6:a1:5a:41 > >>>> e1000: eth0: e1000_probe: Intel PRO/1000 Network Connection > >>>> e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex > >>>> e1000: eth0: e1000_watchdog: 10/1000 speed: disabling TSO > >>>> > >>>> but when booting the local kernel: > >>>> > >>>> Intel(R) PRO/1000 Network Driver - version 7.2.9-k4 > >>>> Copyright (c) 1999-2006 Intel Corporation. > >>>> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 17 > >>>> PCI: Setting latency timer of device 0000:02:00.0 to 64 > >>>> e1000: eth0: e1000_probe: Intel PRO/1000 Network Connection > >>>> > >>> It appears as if driver works and has created the device but... > >>> > >>> > >> > >> The device was not created (and yeah, that's weird since there's a > >> mention to "eth0" in dmesg), also the init script is there and there > >> is a config for the interface at rc.conf/net. It seems the probe is > >> not working, as it never detects the link is up or down... > >> > >> > > What does ifconfig -a return? A lot of times udev will "remap" the > > device name. Especially if there is IP over firewall. > > > > > > --Joshua Doll > Opps firewire not firewall. Long weekend. >
Happens to me all the time... ifconfig -a shows only "lo". I tried some crazy stunts (like copying the module from the livecd) and now I got the interface listed, but it doesn't work and yells a lot of "SIOCSIFFLAGS: Function not implemented" messages, along with "Unable to allocate interrupt Error: -38" in dmesg. I'm in the process of recompiling the kernel right now, and I hope that will solve it (so far I only compiled the kernel while in the LiveCD chroot, but now I have all packages and thus I'm trying to compile it at the real system). That should make no difference, but I'm trying everything... -- Daniel da Veiga Computer Operator - RS - Brazil -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ ------END GEEK CODE BLOCK------ -- [EMAIL PROTECTED] mailing list
