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.
I guess that I can understand your problem if you are not used to or uncomfortable with the command line, so start by opening the terminal.
Next you should become the root. To do this type...
You will then be prompted for your administrator (root) password. Enter it, and you should see the prompt turn from a $ to a # (or was it the other way around.... well, you get the idea).
Now you need to find the downloaded file. Use the command (no quotes) "whereis e1000*". It is most likely in your home directory somewhere, so the output will probably be "/home/[your user name]/***". So now enter the command "cd /whatever the file is/". This will bring you to to the subdirectory (they're called folders now...*sigh*) that the file is located in. Test this by typing "ls e1000*" and make sure the output contains your driver file.
This is where you will start to really follow the directions of the README file. The file that you dl'ed is a compressed tarball, which means that it's a bunch of files all packed and shrunk into one file. The "tar zxf e1000-x.x.x.tar.gz" (replace the *'s with the numbers on the file, should be 4.3.15) command will unpack the tarball. After that is done, using the "ls" command ("ls|more" if necessary) should show that you now have a new subdirectory called 'e1000-*.*.*'.
Now go to that directory with "cd e1000-*.*.*/". Once there, move again to the scr subdirectory with "cd src/". Now the fun part. Run the command "make install" and hope everything works. If it doesn't, post the errors and well see if a solution is available. If it does work, on to the next step.
Next the README says to install the module. So enter the command "insmod e1000". I don't think that you need to include the parameters (should have a default) and such, unless you need some special setup, in which case the README has that information to include at the end of the command.
Now here is where I am not sure what you should do. The README says to use "ifconfig" and assign yourself an IP address, but, someone correct me if I am wrong, doesn't SUSE's YAST program like to set that part up. Besides, it sounds like your router is assigning your computers a IP address (did you set the addresses on the others yourself?), so wouldn't YAST be better at setting that aspect up? I have no idea what you should do here, so you will have to wait and see if someone else knows, or pick a method of continuing at this point and go for it.
All that is left is to test your network and verify that it is working (as far as I know that is all thats left anyway). Good luck.
ty volvogga for those instructions , these are exactly the instructions i needed.
now this is what i done and the ERROR i get
i made a folder in home called e1000 first.
opened terminal keyed in su -
keyed in cd /home/user/e1000
keyed tar zxf e1000-5.0.43.tar.gz
keyed cd e1000-x.x.x/src/
keyed make install
i get this error makefile :65: ***Linux kernel source not found. stop***
and if i key in rpmbuild -tb e1000-5.0.43.tar.gz
i get this error *** cannot open file '/etc/red-hat/release' for reading (no such file or directory)
Okay.... it looks like the first error is the easier of the two to solve (the second, to me anyway, looks like it is Redhat/Fedora specific, so lets see if that option can be ignored for now), so lets go with that one. I think that there is only two possible causes for this error. The first would be that your source code for the kernel is not installed, and the second would be that the makefile is not looking in the right place for the source code.
I would guess that the first cause is the more likely one. From the googleing that I did, it looks like all you have to do in SUSE is startup YAST, go to some add/remove applications kind of area, and tell it to install the kernel development packages and the kernel packages. Once this is done, try to install the driver again.
If that doesn't work, then perhaps the kernel source is located in a different place on your system than the makefile is looking. The info I found said that is should be in /usr/src/linux/ directory. The looks to me to be configured to look in this directory (I dl'd the file and took a look). If your source is somewhere else, then you will have to locate it on your system (need a SUSE user's input on this one) and then add the path to that file to the makefile (open the makefile in a text editor and go about a quarter down the file to find the part about where to look for the source).
I hope that this helps. I don't know the exact steps you will need to follow to do either of these tasks. Can a SUSE user clarify, fix, add to, and/or OK these instructions for me?
Sorry about not replying for a few days, been busy.
Anyway, I may have found a solution to your problem. Only problem is that it sounds a bit dangerous. Seems that it is possible to generate that missing file yourself (along with another file called version.h) by going to the directory that contains your source code, making sure that there is a file there called .config, and then running the command 'make oldconfig' (this is all done as root, of course).
Here is the source of this information for your own review...
that talks about having your problem on an older version of SUSE. The solution they give is to install a new kernel (personally, I don't see that as a valid option for installing one driver, but...), or download a "new kernel tree package
supplied by SuSE." I looked for a little while, but I couldn't find what this "kernel tree package" was or where you can get it from. If I did find it (or if you can find it), I think that I would recommend this solution over the previous one.
If anyone has any better solutions, can back-up the first solution I found, or knows where to get the "kernel tree package", please post. I feel like I'm shooting in the dark with my advice here, as the information is all from the internet with a little deductive reasoning from me, but with no real experience on my part with messing with the kernel. I don't want anyone's system to be destroyed (although, I have no problem with destroying my own...).
I had the same issue with WinXP and FC4, today on this very same forum someone gave me the answer, which i already tried and worked like a charm.
First of all you have to make your LINUX HD the primary HD, this makes winxp your slave or secondary HD.
Install Linux on your 30GB HD (as primary), whenever you are asked to setup GRUB make sure GRUB installs on the Boot Partition of your LINUX HD (not on the MBR !!!), and name the second OS (which LINUX will recognize as Other) "Win XP" or whatever works for you.
After the LINUX is installed edit the /etc/grub.conf, and under the [Windows] section add the following lines:
map (hd0) (hd1)
map (hd1) (hd0)
This will trick WinXP making it believe it is running on the primary drive (which it loves) and allowing you to have dual boot on your PC.