Thanks Paul - I took my computer into a local shop for a look-see. He noted some missing drivers and tried to upload a new driver. When he got busier and we couldn't easily upload the new driver, I left his shop so he could work with his paying costumers.
Rob did tell me that he had luck with another distro, too. So I can try that, I guess. Maybe I can get one to work. I agree, a working system is a whole different ballgame. Thanks and I will keep on trying. Jim in Ohio --- In [email protected], "Paul" <pfrederick1@...> wrote: > > > > --- In [email protected], "Jim" <jverhovec@> wrote: > > > > Thanks for the response. > > > > Yes - I plugged an Ethernet directly into the computer from a router. I > > recycled the computer more than once. In my terminal, I used /sbin/ifconfig: > > > > jim@jim-laptop:~$ sudo /sbin/ifconfig > > [sudo] password for jim: > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > inet6 addr: ::1/128 Scope:Host > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:8 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:480 (480.0 B) TX bytes:480 (480.0 B) > > > > jim@jim-laptop:~$ netstat -nr > > Kernel IP routing table > > Destination Gateway Genmask Flags MSS Window irtt > > Iface > > > > I don't know if this may help. > > It shows you do not have an eth0 interface. Without that network interface > you of course have no gateway access point to the Internet either. > > Like others have pointed out in the thread you have to get the driver for > your hardware and load it before you can bring your network interface up. > > Everything I've read about that Ethernet Controller suggests you should have > the driver now. A couple of years ago you would have had to go out and get it > special but now I think it is included? > > I could swear when I ran a live image of Fedora 17 on an Acer laptop here it > just worked. That laptop is out for unrelated hardware repairs now so I > cannot verify it again though. I think the HDD died in it. Being as > networking just worked in it I didn't look too closely at what it had. When I > get that system back I will now though. > > Maybe you can get Roy to tell you what the module name is and you can try to > manually load it? > > I know how frustrating solving these problems can be but look on the bright > side, by the time you've figured it out you'll have learned so much you'll be > an expert! Knowing about modules and basic networking comes in handy. > > BTW one valid troubleshooting technique in Linux is to load up another > distribution where stuff just works, see how and why it works, then use that > information to make a broken distribution work. When hardware works you can > see what the module name being used is etc. UNCLAIMED isn't very helpful. But > seeing stuff working can be very enlightening when it comes to > troubleshooting. Oh, so that is how it is supposed to work. As opposed to why > doesn't it work? > > Of course doing that can have the side effect of changing distributions. So > be careful :) > ------------------------------------ To unsubscribe from this list, please email [email protected] & you will be removed.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/LINUX_Newbies/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/LINUX_Newbies/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
