SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Newbie using Slackware64 v13 here. When I installed and started running slack with the default huge.s kernel, my ALSA and x-fi didn't work, so I switched to a self-compiled 'generic' kernel. When I booted with the new kernel, the sound worked, why did this happen? I also notice that the system seems less responsive, but I can't say for sure. For instance I notice a delay when i click the mouse to close things.
Did I do the correct thing to self-compile the generic kernel? In the slackware documentation, Pat says I should be using huge kernel only for installation and generic kernel once the system is up and running. Does the generic kernel come precompiled or was I correct to build it from source?
Anyway, I'm looking for a thorough guide on custom kernel building. I followed Alien Bob's wiki article but it seems to be out of date and doesn't have a whole lot of information on the actual kernel config options.
Has anyone looked at gentoo's kernel guides? Are they full of 'gentoo-only' things or is it all the same for whatever distro you run, i.e., applicable to slackware?
Last edited by delta_waves; 03-03-2010 at 09:03 PM.
Newbie using Slackware64 v13 here. When I installed and started running slack with the default huge.s kernel, my ALSA and x-fi didn't work, so I switched to a self-compiled 'generic' kernel. When I booted with the new kernel, the sound worked, why did this happen? I also notice that the system seems less responsive, but I can't say for sure. For instance I notice a delay when i click the mouse to close things.
Did I do the correct thing to self-compile the generic kernel? In the slackware documentation, Pat says I should be using huge kernel only for installation and generic kernel once the system is up and running. Does the generic kernel come precompiled or was I correct to build it from source?
Anyway, I'm looking for a thorough guide on custom kernel building. I followed Alien Bob's wiki article but it seems to be out of date and doesn't have a whole lot of information on the actual kernel config options.
Has anyone looked at gentoo's kernel guides? Are they full of 'gentoo-only' things or is it all the same for whatever distro you run, i.e., applicable to slackware?
You should have no problem running the generic kernel that ships with Slackware and there should be no need to compile it yourself.
You may need to create an initrd (Read /boot/README.initrd) or you can try the script "/usr/share/mkinitrd/mkinitrd_command_generator.sh" to help create one.
Does anybody understand why my sound didn't work until I started running the generic kernel? I'm happy that my problem is solved but I'd really like to understand why.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.