SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'll have to direct my friend over this way, but he's got some internet issues with his new SuSE 10.2 install. Everything works from what I can gather, he's capable of IMing me and others. However, he can only get to Google.com. Any search will come up, but if he clicks on a result, the page gets hung up on finding site name or some variant. We've disabled IPv6 in Firefox and I will walk him through editing his modprobe.conf file. He's tried about every combo for configuring his wired ethernet connection. He's at a major University, so I imagine he's on a T1 network. His hardware is a 2 year old ASUS MB, with a Realtek 8201CL 10/100 M Fast Ethernet. His Windows boot will come up and connect fine. I figure while he's pestering his IT help there, I'd help by asking for any help here. I'm stumped. Any help is greatly appreciated!
(EDIT: Well we've walked through his /etc/modprobe.conf file and back again, no change.)
(EDIT: We might have narrowed it down. Once his IT help gets back to him we'll know for sure. Thanks!)
Editing the resolv.conf file didn't have the desired results either. According to my friend, IT concluded that the install went wrong. The problem is that it is the same problem even when using a livecd. I think he hit it on the nose, when he asked about a driver issue. So I appreciate everyone's help.
We solved it! It was a chipset not being completely supported by the kernel. I had him do a "modprobe sis900" as super user and reboot (never thought about checking his chipset module). Got the conformation today that it worked. Apparently, the SiS 649 chipset is not fully supported, which in turn controls his NIC. Thanks again to everyone.
Edit: Well, drat. The modprobe only worked a few intermittent times. Still, I think we narrowed it down to the chipset. So, the best bet is to buy a new NIC and go from there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.