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!
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.
Make is not the right command for installing a module you already have. 'insmod' or 'modprobe' (either one. modprobe is preferred by some distributions) installs an existing module. Run 'lsmod' to be sure the module was installed. You usually have to do all this as root. Sometimes it's necessary to restart X or to reboot for things to work.
Both have to be run as root. When you get an error of 'Command not found' it often means it needs to be run as root. In effect, the machine is saying that only root is important enough to even know this command exists. The commands do the same thing. Modprobe is preferred in some distros.
It should not matter if you su to root. I would try logging in as root, myself, just to be certain. If neither command is available, then something is wrong. These are basic commands. If they're not there, you should probably check the installed packages to be certain all the administrative parts are really there. I only know about SuSE. I suppose it's possible one of the other distros might not use 'modprobe' but I would be surprised if it were so. Also check whatever documentation you have available, how-to's and help files, to see how your distro does things. What are you using, anyway?
In case anyone comes across this.... here is my final post on this ordeal.
YOU MUST LOG IN AS ROOT TO DO THIS.
All you have to do is get the driver off the cd, and follow the readme instructions for extracting it.
Then move into the folder containing the makefile (3c2000).
(for this to work you need to have the kernel source loaded in /usr/source/linuxXXX)
Then type:
make clean
then
make install
then
make load
This will do all the preperations and load the module to where it needs to go.
After this, you must go to /etc/sysconfig and edit the hwconf file. It will have a listing for your card and know that it is a 3com but not what type or what driver to use. It will look something like this:
go in and change 'driver: unknown' to 'driver: 3c2000' and then go to your network control panel and when u create a new ethernet card it will be listed so you can choose it now.
The only thing I don't quite get is I did this are root. I'm looking back at it for this post from a user and when I looked at my /etc/sysconfig/hwconf it shows that the driver is unknown but it still works. I dunno maybe I'll add it again or something but it did work for me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.