Okay, so your hardware and drivers are configured for the Realtek NIC. Don't mess with those levels again. (-:
Sounds like you aren't configured as a DHCP client. Or maybe you aren't logging DHCP. On my Ubuntu box, I can see the dhcp client running. ~> ps ax | grep dhcp 1658 ? Ss 0:00 dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0 4722 pts/0 R+ 0:00 grep dhcp Check that . If it's running, then it isn't logging. If it's not running, either look at NetworkManager's configuration, if you're using NetworkManager, or else /etc/network/interfaces. I'm not running NetworkManager on my desktop. (I left my laptops in the office tonight, so can't check them.) Here's what I have in /etc/network/interfaces. (Plus comments, which I'm not showing.) ~> cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp However, I recommend you use NetworkManager on Ubuntu if you can. It's the default config and better tested. I don't know anything about Puppy Linux, so can't advise you about configuring it. On Thu, Nov 19, 2009 at 11:59 PM, marbux <[email protected]> wrote: > On Thu, Nov 19, 2009 at 11:24 PM, Bob Miller <[email protected]> wrote: > > Hi, Bob, > >> Lowest: hardware. Card is seated, cable is good, cable is plugged >> in securely at both ends. (Have you swapped cables yet?) > > Yes. > >> Electrical connectivity between the CPU and the NIC. Run >> "lspci | grep Ether". Verify you see each installed device. > > > Only one is showing: > > 00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL-8139/8139C/8139C+ (rev 10) > > That seems to match the card I added. But no sign of the onboard > ethernet connection. > > Since this seems half right, I'll proceed to the next problem area found. > >> Drivers. This was working when you showed that ifconfig sees eth0. >> If you have two cards installed, then "ifconfig -a" should show both. >> If it's not working, try to revert to where you were when it worked. > > ifconfig -a agrees; only eth0 and the local loopback. > >> IP configuration. Run ifconfig, verify you have an IP address. (You >> didn't in the screen shot you showed.) If you're using DHCP, then >> you need a working DHCP server. I'm not a Comcast customer, but >> it sounds like the DHCP server should be outside your premises. >> Either look in syslog (/var/log/message or /var/log/daemon.log) >> for DHCP activity. You should see DHCP DISCOVER followed >> by DHCP OFFER. If you don't see DISCOVER, your box isn't >> configured to use DHCP. If you don't see OFFER, either the DHCP >> server can't hear your box, your box can't hear the server, or the >> server is refusing to serve you. The first two problems indicate >> that your hardware connectivity is bad -- revert to first level. >> The last problem indicates that Comcast sucks. I'm not a >> Comcast customer, so I don't know what their rules are nor >> how they enforce them. > > Neither log shows DHCP DISCOVER or DHCP OFFER. > > Quo vadis? > > Best regards, > > Paul > > -- > Universal Interoperability Council > <http:www.universal-interop-council.org> > _______________________________________________ > EUGLUG mailing list > [email protected] > http://www.euglug.org/mailman/listinfo/euglug > -- Bob Miller K<bob> [email protected] _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
