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.
I have Slackware installed on a Dell Dimension L667r with a 6GB drive and only 128MB of RAM. I'm running out of drive space and the RAM causes limitations with OpenGL apps, but other than that it runs great. I'm waiting for the day that I can install Slackware on my current WindowsXP box with a bigger drive and more RAM.
Dude, no offense, but it just sounds like you don't know squat about what's in your computer. I'm using a Soundblaster Live! that says DELL right on the card, and I havn't had any problems with it. I'm also using 3 hard drives, two of which are 80GB's, those are on my first IDE cable, the third is a 40GB, and that's on a IDE cable connected via PCI cards.
I refuse to use cfdisk any more. It made me change some settings so hde had a bootable partition, which completely hosed my abilities to boot into Windows for a day (Until I realized that was the culprate and untoggled the flag). Instead, use fdisk. It doesn't look as pretty, but usually it's those programs that look ugly that do the best jobs.
Bottom line:
Learn what hardware you have in your system, find out what drivers they use, and then choose the proper kernel when you install. If all ends up working, keep that kernel as a backup, then download the latest in either the 2.4 branch or the 2.6 branch, take your pick, and compile, only choosing what your system needs.
I even looked took off the case cover, pulled the card out and looked at it... IT IS NOT A REGULAR SOUND BLASTER CHIPSET...... NUMBERS DON'T LIE.... Do some research on it. I have. Hours and hours worth. It's a paperweight in Linux. Those 4front oss drivers suck bad. They made sound come out but it wasn't very nice....
SATA isn't supported by Slackware either or the 2.4 kernels for that matter. I have an SATA ICH5 controller. Had to use a custom boot disk and 2 root disks that JollyRoger over at ISO was kind enough to provide. That got the install started and to a desktop then I downloaded the libata patch for 2.4.25 and the kernel source and I recompiled a completely supported kernel....
Give me a shipping address and you can have this card because it will do me no good. I'm dead serious. If you want it you can have it, otherwise I'm going to give it to my neighbors dog...
I don't even bother installing alsa via their packages any more, I only use the alsa packages that are under Slackware-current. What I do to get my sound supported is compile the emu10k1 driver and alsa directly into my kernel.
Gotta go check on the cookies, make sure they're not burnt...
r_jensen11
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.