Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
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.
What is the best way to load modules at boot time? I got LFS installed, rebooted, it couldnt find my netcard(Netgear FA310TX), i checked lsmod and tulip wasnt loaded, i loaded tulip, brought the interface up and it worked. Please help a poor newbie!
Just modify a startup script. I believe the path is /etc/rc.d
You should see a lot of scripts that you installed with LFS. I would suggest going to the script responsible for the network interface (I can't remember the name off-hand), and simply add the command to load the module(s) in the "start" portion of the script.
If you nit-pick (like me), you might want to add the commands to unload the modules in the "stop" portion, but isn't extremely necessary.
well, I'd suggest a much cleaner way:
put a line in /etc/modules.conf
alias eth0 <modulename>
where eth0 is the interface name and <modulename> is the name of the kernel module you'd like to load, for 3com Ethernet cards for example this would be: 3c59x.o
This option loads the modules automatically when you try to activate / use eth0, thus it's marked with an "autoremove" option (what doesn't make sense for network cards) where the kernel can remove the module automatically when it isn't used to save memory.
I recommend this because it's easier to check /etc/modules.conf if you want to compile a new kernel - most modules you use are in there - than to check every script in /etc/rc.d/init.d whether it loads a module or not.
And, imho, it's easier to play around with modules, let's say if you want to test a new driver.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.