[SOLVED] Install from Slack CD #1: Missing Firmware
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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 was installing Slack 13.1 from from a CD set. Unfortunately my old box uses an Advansys SCSI card. The "huge" kernel has the advansys driver compiled in all right, but it then calls for the advansys firmware "mcode.bin," which is missing from the CD.
Result: bootup stalls here on a "requesting/not found" loop.
Short of pulling the SCSI card (not trivial on an old Dell OptiPlex), any other ideas?
Problen is that CD #1 is the boot CD; i.e., the one to boot from to begin the Slack install. When the boot process hangs the story is over.
I thought of a fix, which I'll try soon. I recompiled the 'huge' kernel *without* advansys support. Unloaded the iso to a r/w dir tree, replaced the huge kernel with my own, and rewrote the iso file. I'll burn a new CD #1 and try it soon.
Problen is that CD #1 is the boot CD; i.e., the one to boot from to begin the Slack install. When the boot process hangs the story is over.
I thought of a fix, which I'll try soon. I recompiled the 'huge' kernel *without* advansys support. Unloaded the iso to a r/w dir tree, replaced the huge kernel with my own, and rewrote the iso file. I'll burn a new CD #1 and try it soon.
You can also put the firmware on the CD. That way you don't have to recompile the kernel.
Final Comment: Install from Slack CD #1: Missing Firmware
As posted, a custom 'huge' kernel solved the problem.
However, I learned that that the 'missing' firmware was there all along (!), in /lib/firmware/advansys. So what happened? It seems the Advansys *module* advansys.ko "knows" where to find its firmware (see modinfo advansys). Apparently when the driver is compiled into the kernel the path to the firmware is lost.
I seem to remember that a long time ago the lp' driver needed to be a module and not compiled in, but I admit it's kind of fuzzy now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.