Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
ok i am a linux n00b, but i've been a computer geek since i was 2 (im 18)
mandrake 10.0
amd 64 3800+
i have an onboard nic card (abit mobo, via gigabit ethernet)
but every time i restart the computer i have to go to root and insmod velocityget.ko and ifconfig eth0, is there a way to set it up so that i dont have to do this?
on every boot it also says "eth0 [FAILED]" on startup
What exactly did you add to modules.conf? Also, look for a file in /etc that has 'preload' in the name - you might want to use that instead.
(modules.preload, modprobe.preload?)
That sets up an alias, but doesn't tell the system to load the module at boot time. This is why there is usually another file (/etc/modules, or the preload one in some distros) that tells the system which modules to use at boot.
One way to force the issue without a file like this is to add (for example):
Code:
path[boot]=/lib/modules/boot
to modules.conf, and then create that directory, and a symlink to the module in question, i.e:
Code:
mkdir -p /lib/modules/boot
cd /lib/modules/boot
ln -s /lib/modules/`uname -r`/kernel/drivers/net/velocityget.ko velocityget
ok the second half of that worked flawlessly, but is the first part (modules.conf insert) supposed to be exactly what you wrote? because if it is it still isn't working.
the link to velocityget.ko is in place but it still isn't loading it on start up, i am still getting the [FAILED] on boot too.
Right, I'm giving up on the 'right way' to do this, as it seems there are too many variables. Find out what your network script is called (in /etc/init.d or /etc/rc.d/init.d), and add "insmod velocityget" just below the PATH statement.
ok im sorry i got rabies or somethin, i couldn't get the init.d to work
but i did get the modprobe to work after typing alias eth0 velocityget into it. it finally worked and i decided not to touch anything, so thanx for the help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.