Suse/NovellThis Forum is for the discussion of Suse Linux.
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.
Overall, I'm pretty pleased with the hardware detection of SuSE 9.3. It was able to recognize my ethernet adapter (eth0) and my wireless card (eth1), and both worked out of box.
I use the ethernet adapter (the one that connects to a CAT5 cable) when I'm in college. When I go home, however, my only available connection is via a USB interface. I have configured this properly in YaST so that SuSE recognizes it. This interface is eth2.
However, eth2 only works sometimes (and eth0 may have a similar problem now that I configured eth2, but I haven't had the chance to check). It seems as though when booting up, there is a race condition between eth0 and eth2, and the one that loads first works. Therefore, it seems that eth2 works at random times and doesn't work at other times.
I'd appreciate if someone can help me either
1) Configure my computer to load the correct network interface during boot up.
2) Show me how to manually select (and change) network interfaces from KDE after boot up.
Thanks for the help. I'm not at home any longer, but I believe there are no modules associated with the drivers (i.e., they are all in the kernel). When I manually start the network, do I have to stop all other interfaces?