SlackwareThis Forum is for the discussion of Slackware Linux.
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.
There's no hardware support list for CD-ROM readers, because there's no need. Support for CD-ROM readers has been built into the kernel for forever, and there is no reason that Slackware should not recognize it under normal circumstances. Is there something odd about your CD-R that might cause it to be incompatible (for example, it's insanely old, or connects via a serial port)?
Why are you concerned about this piece of hardware in particular?
Oh, please excuse me. You didn't say it was a SCSI device in this thread, and I didn't look up the model name in Google. My mistake.
You currently have Fedora installed? What kernel are you using (because this is a kernel issue, not a distribution issue)? Have you done a make menu config with your current kernel source (without saving or compiling, this is just to look) to see if your drive has a module available, and if it has been built? The problem may well be that the module exists, but just wasn't compiled, so (naturally) cannot load.
If the module does not exist in the 2.4 series kernels, you may well want to upgrade your kernel... I would also suggest doing the same thing with a 2.6 series kernel (install the source, then do a make menuconfig without saving) to see if a module for this driver (or the controller that it's connected to) is available.
Kernel 2.6 tends to have all its modules enabled, in my experience, so if there is one, you probably won't have to change much if anything in the config (for those devices, in any case, there will probably be other stuff you want to change/add).
However, if it doesn't work with Win2K either, I would also wonder if there wasn't a problem with the drive itself (is it old?). Win 98 is pretty "dumb", so a piece of hardware that is not in top shape may still work, but Win2K and beyond are somewhat more strict-- as is Linux, but since we don't know what the driver status is under Linux, it's hard to say if Libranet and Fedora are also being strict, or not.
Hi carboncopy and motub, but i dont understand both of your suggestions. It sounds to complicated. I havnt installed Slackware yet by the way. I am still on Fedora core 1. By the way i found out what the problem is.
Is it a Advansys ABP5140 ISA SCSI card. And i need to enable the module some how. I did modprobe advansys, and then the busy light comes on in my burner, it flickers for a while and my whole system freezes and i had to restart manually. I think i might need to load it during startup. Btw i have the kernel version: 2.4.22-1.2174.nptl. Thanks
OK, so at least you don't have to recompile the kernel for the controller card, anyway. But you probably still do need to recompile the kernel, because if the module for the card exists, but is not loading on startup, you probably don't have isapnp running as a kernel option-- this would scan the ISA bus as well as the PCI bus and load any needed modules it found for ISA devices (which is not happening for you). And we still have to make sure that the module for the burner itself exists (you need two modules running... one for the controller card, and one for the drive itself).
So my advice remains:
1. install the kernel-source for your currently-running kernel if not installed;
2. open a terminal, su to root and cd to /usr/src/linux;
3. type make menuconfig to open the kernel configuration tool;
4. Go through the SCSI options to see if there is an "M" next to the drivers for both the controller card and the CD-drive;
5. Go through the General Setup options and confirm that ISAPNP is enabled (with either a * or an M; a * is preferable in your case)
6. Once you know that, you can either
a) exit out (if you're panicked and don't want to recompile the kernel right now; in that case, read PhpWiki - How to compile your own kernel before proceeding); nothing will have changed on your system. Or,
b) make the required adjustments (add the modules you need based on what you've learned of your current config), recompile the kernel and the modules, install the new kernel, and reboot to it.
I'm sorry that this sounds too complicated, but 1) it's not, really; 2) if you expect to use Slackware, you are going to have to get used to it because Slackware makes you manually configure things like this (you're going to have very few GUI tools to do advanced configuration tasks like under Fedora); and 3) compiling and recompiling a kernel is a necessary skill (some would say "evil") under any distribution of Linux, and even more so if you're going to use old hardware (like ISA cards), new hardware (like the latest whiz-bang video card, or gigabit ethernet cards), or anything in any way unusual from the most bog-standard vanilla hardware that was current some 2-4 years ago.
Hope this helps; please let us know what you don't understand and hopefully we can explain further.