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.
and then created a soft link "S09ADMtek" in the /etc/rc.d/rc3.d that points to the "ADMtek" file. Certainly, I had to "chmod 'a+x' ADMtek" to make it a executable file. Now I have internet access as soon as a log in as any user.
I also found more than one reference to "unresolved symbols" warning, after copying 8211.o to /<path>/net and then doing depmod-a. The posts said 8211.o still works even when the "unresolved symbols" warning comes out of depmod-a.
What else might I try to get driver to load at boot?
Help is greatly appreciated!
Last edited by toastermaker; 12-10-2003 at 04:05 PM.
hmm if invoking
/sbin/insmod -f /lib/modules/2.4.22-10mdk/kernel/drivers/net/8211.o
works for you, I suppose you can do what he did as well, make a file which contains just the above command, make it executable, then make a symlink to your runlevel directory
(probably /etc/rc.d/rcX.d for Mandrake, can't remember on top of my head), do it for runlevel 3,4, and 5. The runlevel scripts run in ascending number order with regard to their name so make sure you name the symlink something like S008211.
It now loads at boot. The only different thing about it is during boot a new line comes up with all the rest - "starting admtek" followed by "OK" (great!) then two lines later the normal "starting eth1" comes up and pauses for a few seconds then outputs the error msg " sorry, another instance of eth1 is already loaded" ( or words to that effect ) then everything moves on fine.
Not a problem at the moment, I dont want to take the time right now to try to correct that because I'm in a rush to get wireless configured and "up and running"
Not that it would really be a problem anyway, its just that later on, when I have time I want to start taking measures to cause the quickest boot I can.
Extreme thanks to you Demonbane.
Continued gratitude to all those who help us newbies