Previously, Tim Wunder chose to write:
Yeah, I know, replying to my own post, yada, yada....
<snip>
> My COL3.1 apparently uses both  srx and scdx to refer to the same things:
> brwxrwxrwx   2 root     disk      11,   0 Apr 27  2001 /dev/scd0
> brw-------   1 dad      root      11,   1 Apr 27  2001 /dev/scd1
> brw-------   1 dad      root      11,   0 Apr 27  2001 /dev/sr0
> brw-rw-r--   1 root     disk      11,   1 Apr 27  2001 /dev/sr1
>
> Interesting to note the user/group for my devices. Not sure what's going on
> there...
> sr0 and scd0 are my SCSI CDRW, sr1 and scd1 are my IDE CD-ROM, /dev/hdd. I
> happen to have hdd=ide-scsi in my menu.lst. I also have ide-scsi loaded as
> a module in /etc/modules/default. Everything works, but it sure seems
> horked. Guess I'll try to play around with it some to see if I can figger
> out what's going on. It is likely only the only thing this task will
> accomplish, though, is breakage...
> I'll start by removing the /dev/sr0 and sr1 files and take "hdd=ide-scsi"
> out of grub's menu.lst file and see what happens.

Well, I removed the /dev/sr0 and sr1 files and took "hdd=ide-scsi" out of 
grub's menu.lst file and, upon first reboot, my ide CD-ROM was no longer seen 
by xcdroast as a scsi device.

In order for my IDE CD-ROM to be seen as a scsi device, I had to add 
"hdd=ide-scsi" to the kernel line in my menu.lst file. This is contrary to 
what the bedtime reading document states. So I set out to determine why.

Upon investigation, I made a WAG that the reason I needed to load ide-scsi 
during boot was that I had IDE CDROM support compiled into the kernel. I 
tested my WAG by recompiling the kernel with IDE-CDROM support as a module. 
Upon reboot with this new kernel, I am able to access my IDE-CDROM using 
xcdroast.

Now, off to figure out why I can't access my IDE-ZIP drive with this same 
kernel. But that should be another thread...

Tim
_______________________________________________
Linux-users mailing list
Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users

Reply via email to