Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
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.
I need to run an install script for a custom Xilinx linux parallel port driver during the boot process on a SuSE 9.0 system. When i put the "source /lib/modules/misc/install_windrvr6 windrvr6" line in boot.local, the screen and log show that the driver is loaded with success.
However, when I launch the Xilinx program and attempt to program an fpga, the drivers are not found by the main program.
If I install the same drivers manually AFTER booting, the program works fine. I think that by putting the driver install command in boot.load that it's happening too early in the boot sequence.
Does anyone know where I should put the driver load commands so that they execute later in the boot sequence - or how to do it? I've looked at insserv and the man pages but don't really understand it.
"Does anyone know where I should put the driver load commands so that they execute later in the boot sequence - or how to do it? I've looked at insserv and the man pages but don't really understand it."
boot.local is the last script in the boot sequence. I would look to see if there are any differences in the command that you have in boot.local and the command you enter manually.
Steve - thanks so much for your reply. If SuSE boot.local is the last one to run, something's really wrong. After boot.local runs on my box, all the networking, pcmcia, xdm, etc runs . On an old box I have Fedora running on, their rc.local indeed IS the last thing to run.
"If SuSE boot.local is the last one to run, something's really wrong. After boot.local runs on my box, all the networking, pcmcia, xdm, etc runs . On an old box I have Fedora running on, their rc.local indeed IS the last thing to run."
I have two different thoughts about this.
1. Maybe SuSE is running startup scripts in parallel to speed up boot. So maybe boot.local is the last thing to start but not the last thing to finish. You could experiment with this idea by putting this command as the first command in boot.local:
sleep 10
I am not at a Linux box right now so I cannot check the sleep command against the man pages to make sure I have to time set to 10 seconds.
2. Maybe SuSE has changed things to where boot.local is no longer last. In that case figure out which script is last and pput your "source /lib/modules/misc/install_windrvr6 windrvr6" command as the last command in the last script.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.