Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Hey everyone, thanks for taking the time to read my post.
Currently, I'm trying to install Slackware 10.2 onto one of my harddrives, but I've run into a problem. When I try to install, for some reason, Slack thinks my HD is 10 gigs, instead of 30 gigs. I should probably let you all know that I use to have Fedora Core 4 installed before, however, I'm trying to get rid of FC4 and install Slack. It seems very odd that I cannot reclaim all of my previous space. Anyways, the 10 gig limit is preventing me from installing Slack because I'm supposedly "filling" the disk by installing the first CD (635 MB != 10 GB). Something is very wrong. I'm writing this on my laptop, staring at my desktop, trying to figure out what is wrong.
Now I just have to get Slack to properly determine my network card, video card, monitor, and soundcard!
Hehe, the thing about Slack is it takes a little finesse to configure it the way you need. First, I would suggest installing the 2.6 kernel since hardware is supported a lot better then the default 2.4 kernel. You can get this from kernel.org or from the /testing directory on the slackware install medium.
First, uninstall the 'alsa-driver' package with 'pkgtool'. Make sure you leave 'alsa-lib' and 'alsa-utils' alone. Then from the kernel source directory, run 'make menuconfig'. Make sure you have all the appropriate hardware support installed as modules (could be hardcoded but easier to debug if module). For sound, you have to compile "Sound Support" as a module, as well as alsa and the appropriate module for your sound card in alsa directory. When finished with kernel config, run:
make clean && make && make modules && make modules_install && make install
then reboot with 'init 6'. WHen you get back in your system, run 'alsaconf' and 'alsamixer' to set volume levels (make sure channel is not muted 'MM')
make sure your hardware is enabled as module in the kernel (see above) Then run 'xorgsetup' to configure your '/etc/X11/xorg.conf'
make sure your network card is enabled as a module then run 'netconfig' to configure the network.
What video card and sound card do you have? You should be able to select your video driver with xorgconfig, or download one and install it. I also recommend getting the 2.6 kernel, though I've never had to uninstall the alsa-driver. Since I use my sound card on an everyday basis, I just configured my card directly into the kernel, no module. Slack is pretty good at detecting your network card for you. You can run "pkgtool" and run the "netconfig" tool to set it up. I wrote a little kernel compiling guide if you're going to compile a new 2.6 kernel.
You should be able to select your video driver with xorgconfig, or download one and install it.
this also works, but I think just running 'xorgsetup' is better for new users since it autodetects your hardware. (assuming it works correctly of course)
though I've never had to uninstall the alsa-driver. Since I use my sound card on an everyday basis, I just configured my card directly into the kernel, no module.
Uninstalling asla-driver is not necessary per say, it just won't get loaded if you use the alsa module from the 2.6 kernel. The 2.4 module wont work with 2.6 kernel. Uninstalling was just a matter of freeing up some disk space. You can choose to compile the sound card directly into the kernel, but as I mentioned before, this is better for more advanced users. For things like 'alsaconf' to work, it needs the sound card as a module. (note: if sound card is module, "sound support" or 'soundcore' must also be compiled as module.)