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've been trying for 2 days to install Slack 10.2 on a system I had 10.1 running on successfully.
My box runs dual Celerons, so I have to recompile with SMP enabled for it to work. I was able to do this easily with 10.1 and the 2.4.29 kernel.
However, now that I've decided to upgrade to Slack 10.2, my recompiled kernel always panics with the following:
ds: no socket drivers loaded!
kmod: failed to exec /sbin/modprobe -s -k block-major-33, errno = 2
VFS: Cannot open root device "2102" or 21:02
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 21:02
I'm using reiserfs and I've selected it to be compiled into my kernel each time, as I've seen that this will happen if fs support is not properly compiled, but I'm not sure that is my problem.
I ran another vanilla install of Slack 10.2 from the CD and this time, instead of running make mrproper first, I ran oldconfig to see what the precompiled kernel has in it. I noticed a lot of things on the menuconfig that were NOT present when I tried to compile my own kernel.
I reinstalled all of the kernel source packages. After that, I was able to see all of the options that I was previously missing (with the exception of the framebuffer support, which I really don't need now).
I'm almost certain the thing I missed that was causing my recompiled kernel to panic was a missing HD controller driver under the IDE section. Mine is HPT 366, and I never saw or selected the HPT 36x driver before.
Framebuffer support is in experimental stages. Your kernel may be hiding the experimental options. If so, you can enabled viewing all kernel options by:
"Going into the Code Maturity Level menu, and enable the prompt for development and/or incomplete drivers."
The only reason I was using it once before was so I could run top on the box itself and see all of the processes and memory usage on the screen with a 1024 x 768 resolution. (There may be another way to get the console to display that resolution, but I just used the framebuffer.)
However, since I don't need the screen for that anymore, I don't need the framebuffer.
Thanks for letting me know, though. I may need it sometime in the future.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.