Trying to get my ide cdrw onto my scsi bus --

added "append="hdc=ide-scsi" for the last line of this particular kernels lilo.conf --

ide control is compiled into the kernel, ide-scsi is loaded as a module in rc.modules--

hdc is mounted in fstab, thus:
/dev/hdc /mnt/cdrom iso9660 user,noauto, ro 0 0

I am missing something, 'cause when I execute "cdrecord -scanbus" all I see on my scsi bus is my usb hard drive.

Any suggestions are greatly appriciated!

I think you would also need the generic SCSI module loaded to enable the sg devices. But I am not sure exactly what modules are required. I do not use modules, but I think it might be gscd.o. Once it is detected and a driver is loaded the drive would be referenced as /dev/scd0 and not /dev/hdc. If cdrecord is reporting a USB hard disk then it must be using a SCSI type of control system as well. But I do not know if it would provide the generic SCSI support though.

general scsi support, scsi disk support, and scsi cd-rom support are also compiled into the kernel...

Is the IDE SCSI support option builtin to the kernel as well?

no, that is being loaded as a module -- the howto suggests this as the most common setup, saying that the append addition to the kernel loading sequence will wrest the ide control away from the cdrom drive before the ide-scsi module is loaded..if I interpreted it correctly.

Well it sounds like you have everything loaded, so lets what is left.

If your USB is being seen as a SCSI bus, how many SCSI busses do you have present in your system? I seem to recall having an issue where cdrecord -scanbus would only scan the first two for devices. If the IDE-SCSI is coming in third or fourth then that might explain what is going on. Look in the /proc/scsi directory to see how many different directories are present. The /proc/scsi/sg should be there and any other scsi busses (like ide-scsi) that are present. You can "cat" the /proc/scsi/scsi file to report what devices and busses are available. It might provide some info as to what is going on.

If the CDRW is listed in the SCSI listing then attempt to mount a CD using /dev/scd0 as the block device and see if it works.

If the CDRW is not listed then check the syntax of the append command in the lilo.conf. It should read

append = "hdc=ide-scsi"

Run /sbin/lilo after any changes and then reboot. Check the /proc/scsi/scsi file again and attempt the /dev/scd0 mount. Run the cdrecord -scanbus and see if it reported.

Other than that verify using the "dmesg" command exactly what the kernel is doing during each phase of the hardware detection. If the drive is still operable using /dev/hdc (or the normal assignment) then it still isn't right.

That did it! As far as the drive going onto my scsi bus, that is. I've only been a slacker for a week, and into linux for two, so never assume I know what I'm doing!
I had 2 problems in my setup, the cdrom howto did not properly display the spaces to either side of the "=" in the lilo append instruction, a characteristic that was painfully obvious after you pointed it out and I saw the way I had set up the other instructions (with spaces). That corrected, I thumped my forehead with a "doh!", and ran lilo -- something I had only done once before upon installation of my custom kernel configuration, and so I had forgotten that it was necessary after modifying the config. In the distro I tried last week (RH), a mod to the config file was sufficient into itself (it was kept in the /boot/lilo directory).

So, now scd0 is recognized, and mounted, and with a scanbus it is reported on bus 1 entry 0, bus 0,0 is where the usb drive is. Now the next task, getting my cdr software to see it. When I run Gtoaster or Arson, they report nothing on my scsi bus (which we know is wrong). Perhaps they are only scanning bus 0? Actually, I have not investigated this enough to make it a question yet -- unless you know a simple answer.

Thank you very much for your help, Excalibur, this is the second time in two days you have patiently provided me with a solution (yesterday you clued me in on using the "\" character so that bash would look at a "%20" with the proper respect).

Final note: Drive is recognized when cdrw software is run as root, therefore it must just be a permission problem, easily corrected...thanks again.

You are most welcome.

Looking at your original post, you might want to change the fstab to /dev/scd0 instead of /dev/hdc for the mount point. I have also found it helpfull to have or change the sym link /dev/cdrom to point to /dev/scd0 as well. Some programs look for it automagically. The permissions issue is probably "chmod 777 /dev/scd0" if you are not too worried about security issues. Else use "770" and change the group ownership to users.

I can't help you with the GUI frontends for cdrecord though. I have never used any of them. But I would expect many others here have.

Enjoy, I hope that you find Slackware as rewarding as I have.

How about this one! I'm using arson everything works but it says "It doesn't have root permission for real time scheduling". Its not a big deal, but it bothers me. I they and change ownership and permission but it goes right back when I logout and back in.

I start with
brw------- 1 joeblow root 11, 3 Feb 14 17:06 /dev/scd0
So I
chmod 660 /dev/scd0
chown root /dev/scd0
chgrp joeblow /dev/scd0

All the changes take effect until I log out and log back in. Can it be KDE doing this to me are possibly arson. I'm at a loss.

All help appreciated
Thank-you!

It sounds like your /etc/fstab is configured to mount the device for a user. I think it changes the ownership for the device for the user that mounted it. You may want to look at /etc/fstab and perhaps try changing the "user" to "users" plural. (Simply add the "s") This change would allow another user to unmount the device that someone else mounted.

There are also several other options for the device in /etc/fstab that you may want to invsitigate.
suid - does not require any options
umask=000
gid=0
uid=0

But I am not sure if any or all would apply to block scsi devices or iso9660 file systems or what the defaults are though.

I would not think that KDE is changing any of the device settings. The program "arson" could be, or Redhat login procedure could be though.

If you login as root I assume this problem does not exist. So the suid option may be all that is required on the device in the /etc/fstab.

Also I do not know what distro/version you are using. Your sidebar states Redhat 8.0. I am not a Redhat user and I am unable to state what Redhat might be doing in the background either. As well as I have not heard of a program called "arson" before. So I am not sure that I will be of much assistance.

But I think I have read in some mail lists I subscribe too though automounters can cause many unusual problems regarding CD recording devices. You might want to check and see if you have an automounter running. If so, then try to disable it.

Excalibur