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.
It's not a big deal but you can remove it by commenting out "/sbin/modprobe ide-scsi" in rc.modules. Since you're calling it via the append line in lilo, it's not needed.
It's not a big deal but you can remove it by commenting out "/sbin/modprobe ide-scsi" in rc.modules. Since you're calling it via the append line in lilo, it's not needed.
If i do that the module does not start by default and i cannot access my cd-roms until i modprobe it manually.
Personally, it is a "non error" error message. Uncomment the lines and ignore it. Better that than no optical drives
I've had this error message for years. Don't worry about it.
I kind of guessed this. Googling a little i saw it in many posted dmesg's. Anyway commenting the lines did not "fix" it either...it just stoped my cd drives from working.
Thank you both for your replies
I'm a new slackware user. It's definitely the best distro i ever tried
Try putting "alias scsi_hostadapter off" in your /etc/modules.conf
Jim
This didn't work either but the message dissapeared after i recompiled my default kernel.
I don't know how i solved this since i changed a lot of things, added himen support, used athlon insted of 486, striped my scsi hd and tape support, removed framebuffer support. probably the scsi hd support was to blame.
Thaks for your replies
I guessing at this, but since you've added hdc=ide-scsi to lilo.conf, I think that is why your CD-ROM fails when you comment out the module.
SCSI Simulation is no longer required (hasn't been for a while) and you don't need to make any modification to lilo.conf to get burners to work. You will need to rerun
Code:
cdrecord -scanbus
and see where your burner is.
With a single CD burner installed a typical burn command looks like this:
Originally posted by dennisk
SCSI Simulation is no longer required (hasn't been for a while) and you don't need to make any modification to lilo.conf to get burners to work.
You do with 2.4.26 which is what he said he is using.
Quote:
By the way i'm using Slack 10 with tha default kernel (2.4.26) and i have 2 IDE CD's and use ide-scsi.
Originally posted by perfect_circle I had the same impression, that you don't need scsi emulation in the 2.6 series. To write a cd with the 2.4 kernel you need scsi emulstion.
And you would be correct
If the errors bother you, close your eyes during boot.
They are harmless.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.