bad dmesg output when using ide-scsi boot parameter for IDE CD/DVD-ROM
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.
bad dmesg output when using ide-scsi boot parameter for IDE CD/DVD-ROM
When I use "hdc=ide-scsi" in my lilo.conf to try to make my CD/DVD-ROM drive use SCSI emulation, the drive works fine, but I get this error over and over again when I run dmesg, and no other info would appear, just the error.
followed by something about what sector it is testing or something like that. Sorry I don't have the whole error, I have since removed that parameter from my lilo.conf and reinstalled lilo so I would stop getting that error, and since then output from dmesg has returned to normal. I'll get the full error later today and post it.
Anways, I'm wondering if there is something else I need to do to get it to work 100% properly with with SCSI emulation. I did a search and found something about using hdparm ro set parameters for the drive, but I don't know if the problem applies to what is going on with my computer, and I am not really experienced with hdparm and don't want to screw up my system by using it.
OK, I got the full error. It appears that dmesg actually was printing out meaningful data before the error, running dmesg >out.txt and opening the text file revealed that. Here is the data for my CDROM drives:
I guess this is a Slackware quirk, because scsi emulation works fine on my Knoppix box and my previous RedHat 7.3 box. Thank goodness I read the above thread, which saved me from recompiling my kernel (as other threads have suggested).
However, I haven't tried writing to a CD-R yet; but, according to the above thread, cdrecord should work with an ATAPI device.
That's all well and good, guys, but there is no problem with my CD-RW drive. I can burn CDs without a hitch. The problem I'm having is getting my DVD-ROM to not display all that junk when I run dmesg. It seems to work fine, I can play DVDs on it and all, but I know that dmesg output is not normal.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.