cant connect to internet on fresh install of suse9.1
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
cant connect to internet on fresh install of suse9.1
I have just installed SUSE 9.1 on a partition and everything went well beyond my expectations, except that my network devices, an intel pro/100 and a cheap dynex pci card were configured correctly, but neither of them pass during the boot process and cannot connect. When I rebooted with w#%$ows xp they were read automatically, as usual. I have cable high speed service and do not have a set ip address, so I dont know what I'm doing wrong, or not doing. Any advice or experiences would be much appreciated.
I've heard that it is ok if an eth# "fails" during the boot process, because most of the time they DO in fact work. Nevertheless, open a terminal window, and become root (type 'su'). Post what you see when you type
I have tried `if config' along with many other commands and I still have the same issue. Also, on the boot screen, I get "FATAL: error inserting hw_random", and "/lib/modules/2.6.4-52-default/kernel/drivers/char/hw_random.ko: no such device". Also a "no interface found" after the "waiting for mandatory devices". I dont know how helpful that is, but I hope so. Thanks for the help.
Sorry for taking so long to respond. I have tried all of these commands and it seems that everything is configured. I went back and reconfigured with YAST. I dont have access to the router because I share the service with a buisness in my building, but I've heard that sometimes it needs to be reset for a new os to get the service. I hope that is the case, but I'm not too hopeful.
Originally posted by springdog I dont have access to the router because I share the service with a buisness in my building, but I've heard that sometimes it needs to be reset for a new os to get the service. I hope that is the case, but I'm not too hopeful.
That might be the problem. I have a router at home, and I am on it currently. My laptop runs apache on port 80, and SSL on port 81. The router associates any requests to these ports to my computer (coming from the one internet connection). If another computer outside on the internet were to ask to connect to a computer behind the router on port 80, and, say, a family member were to have set up an apache server on THEIR computer as well, then my guess would be that the router forwards it to the first computer. Though what i just wrote is not the same, it is similar.
I definitely could be wrong, as i didn't test it yet
Thank you for the renewed hope. I hope that is the case, because I can't keep running Knoppix everytime I want to connect. I will let you know if it works manana. If anyone else has any ideas in the meantime, I'm wide open.
Originally posted by springdog Thank you for the renewed hope. I hope that is the case, because I can't keep running Knoppix everytime I want to connect. I will let you know if it works manana. If anyone else has any ideas in the meantime, I'm wide open.
I hate to break it to you, but this doesn't sound like a router problem to me. If you can get knoppix to connect, then you should also be able to get any other distro to connect also. Start knoppix and verify that you have a working network connection. Try:
Each of these will output data about your system. I've ordered them roughly in the order that I think could be useful. Run these also in SuSE and compare the two. There is something different here, and you should be able to solve it if you can figure out the difference. I'm guessing it's a module (driver) problem.
I'm almost dead tired right now. Anybody else care to give another suggestion (somewhere else to look or try)?
Originally posted by springdog ...I can't keep running Knoppix everytime I want to connect.
Originally posted by gd2shoe I hate to break it to you, but this doesn't sound like a router problem to me. If you can get knoppix to connect, then you should also be able to get any other distro to connect also.
THIS i didn't know. So, gd2shoe is correct and I am wrong (I predicted I might be) and it also makes a little bit of sense. Knoppix auto-configures your computer everytime it loads, so something on your SUSE install must be preventing it from working correctly. And if your computer can connect then any OS on it should be able to, as well.
And.. if i dare add.. this thread would be better in the networking section
In response to gd2shoe, I ran the commands and got some drastic differences that are too long to post. In lsmod the entire list was different, and scince I dont have a printer I wrote out the list from Knoppix free hand and compared w/SuSE. Thankfully I chose to run Knoppix first scince the list was much shorter.
And to the student, you have been extremely helpful, and thank you for your patience. And you are probably right about being in the wrong forum, although I'm scared to venture outside of the newbie forum. I will probably try there tommorow. Now I have a migraine and have resorted to booting window$. Thank you and good nite.
Just food for thought. I don't know how to figure it, but I installed Mandrake 10.1 last night and it auto configured and works great. I've decided to switch distros, since Mandrake seems to be as newbie friendly as SuSE(although I did really like Yast). But thanks again everyone for the help. This community is amazing. I learned everything about Windows through trial and error because the 10 year old hackers in help forums were too condescending to take seriously and made me feel stupid. I feel like part of this comm. everytime I post or get a reply. So thanks.
Sorry about that. You could have mounted your drive and then redirected the output.
example (assuming /dev/hda1 is SuSE's root):
lspci -v > /mnt/hda1/lspciFile
Then the output of lspci would have been put into a file instead of the screen. You could then open up the file in SuSE (now at /lspciFile) and compare the contents side by side. I don't know if I'm being real clear here. But oh well. Good luck in the path that you've chosen.
Distribution: SuSE 9.1 Pro on Intel 2.4GHz (Dell Optiplex GX260)
Maybe it's too late now, but I have had similar problems. It's been the only real issue I've had with SuSE Linux.
1) The hw_random module - don't worry about it. I had called SuSE on that one and they said it's safe to ignore. At some point (presumably through online updates) this error went away by itself on my system.
2) The problems starting networking. I also have an Intel Pro NIC (built into the Dell PC that I installed SuSE on) and the network startup has been unreliable when I boot the machine for some reason. However, if the networking doesn't start correctly (which happened something like 50% of the time but seems to be much better now for some reason) then I would open up a shell window, su to root, and type
This would restart my network services, and it works every time.