From reading your Dmesg output it looks like the kernel is finding two eth devices. Eth0 is going to the realtek driver and eth1 is used by a dlink pocket device (USB?). what happens if you do 'ifconfig -a'? > I've tried another card with a different chip and it still does it so I'm > positive it's the software side of things. More specifically, the kernel. > Attached (hopefully) is my dmesg output from the livecd's boot and my current > kernel config, after many things being removed and it still doesn't work. > > > > Quoting "Bryce C." : > > >>It's a Netgear FA310TX that's using the tulip module compiled-in to the >>kernel. >> I don't htink it's going to work but I'm going to try taking iptables out >>of >>the kernel entirely. >> >>Quoting Kevin Brown : >> >> >>>Bryce C. wrote: >>> >>>>It may be because it's late but I can not for the life of me get eth0 >>>>talking to >>>>anything. It works under gentoo's livecd and it worked before then in >>>>all the >>>>other distros I ran. I can even restart to the livecd and it works. In >>>>dmesg, I >>>>get alot of net watchdog: eth0 transmit timeout but also mii-tool does >>>>negotiate >>>>(successfully) with the switch. >>> >>>What module is the Gentoo LiveCD loading to work with that card? I had >> >>this >> >>>issue with an Intel 10/100/1000 card that I had to download the driver from >> >>>Intel's site and then after completing the step to build the kernel, built >>>the >>>driver and then it would work. >>> >>> >>>--------------------------------------------------- >>>PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us >>>To subscribe, unsubscribe, or to change you mail settings: >>>http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss >>> >> >> >> >>--------------------------------------------------- >>PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us >>To subscribe, unsubscribe, or to change you mail settings: >>http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss >> > > > >