On Sun, 29 Oct 2000 06:40:04 +0800, [EMAIL PROTECTED] said:
> I read somewhere about somebody's problems with xcdroast. My problem is even
> simpler (stupider?) I can't get cdrecord to work under debian.
>
> Here is some of the info I have been able to gather about my current setup.
>
> debian:/dev# lsmod
> Module Size Used by
> serial 19564 0 (autoclean)
> es1371 25344 0
> sound 57592 0 (unused)
> soundlow 416 0 [sound]
> soundcore 2628 7 [es1371 sound]
> parport_pc 7236 0 (autoclean)
> parport_probe 3332 0
> parport 7280 0 [parport_pc parport_probe]
> sg 15320 0 (unused)
> ide-scsi 7080 0
> vfat 9008 0 (unused)
> unix 10212 85 (autoclean)
>
> debian:/dev# cdrecord -scanbus
> Cdrecord 1.9 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
> cdrecord: No such file or directory. Cannot open SCSI driver.
> cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are
> root.
>
> debian:/dev# ls /dev/sg*
> /dev/sg0 /dev/sg11 /dev/sg14 /dev/sg2 /dev/sg5 /dev/sg8
> /dev/sg1 /dev/sg12 /dev/sg15 /dev/sg3 /dev/sg6 /dev/sg9
> /dev/sg10 /dev/sg13 /dev/sg16 /dev/sg4 /dev/sg7
>
> My kernel version is the potato default kernel 2.2.17. My CD-RW is an
> ironicially named Best CD Writer. It works under Linux-Mandrake.
>
> I believe I have loaded all the necessary modules (sg + ide-scsi) and have
> the
> proper devices in /dev. Just to be sure I did a MAKEDEV (something the
> installation of cdrecord is supposed to do anyways), deleting /potato
> default kerneldev/sg* and
> recreating them. So why the message "cdrecord: No such file or directory.
> Cannot open SCSI driver"?
>
> What have I forgotten/failed to do? This is the final piece of the puzzle in
> my
> making my Debian installation as usable as my Linux-Mandrake (I now have
> sound
> and ppp under Debian. Wow!)
>
Well i had a similar problem with my potato default kernel 2.2.17
which has IDECD driver compiled into the kernel and IDESCSI
loaded as a module. The IDESCSI driver can only access the
CDRW if the IDECD driver doesn't grab it first (the IDECD driver should be
compiled as a module or not at all if using IDESCSI).
So by adding to lilo.conf the line: append="hd?=ide-scsi"
the device file representing CDRW (hd?) is passed to the ide-scsi
driver in the kernel before the ide-cd driver can grab it.
This means that your bootup messages will list the drives
detected by the ide-scsi emulation. If you dont get these messages then it
hasn't worked.
Once you get these messages then run# cdrecord -scanbus
and you should get a listing with your CDRW dev at e.g. 0,0,0.
Then use that in cdrecord dev=0,0,0 ..... and all goes well.
This is a long-winded explanation because it took me a long
time to make sense out of this. In any case it worked. YMMV.
--
gEEk||dOOd^Deb+iaN&&XFce$aaZZ goes<Pronto>(-_-)
