I have recently compiled 2.4.10 onto my Mandrake 8.0
installation.
Since then I now can't access my CD burner, but am
able to mount my normal IDE CDRom.
As a matter of interest, I disabled the SCSII support
- do I need to reinstate this option ?
Pete
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
On Friday 19 October 2001 06:35 am, Peter Moscatt wrote:
> I have recently compiled 2.4.10 onto my Mandrake 8.0
> installation.
>
> Since then I now can't access my CD burner, but am
> able to mount my normal IDE CDRom.
>
> As a matter of interest, I disabled the SCSII support
> - do I need to reinstate this option ?
Yes. SCSI emulation/SCSI CDROM support is required for cdrecord etc to work.
-Naren
Yes, you need scsi for CDR. Frankly, this is one part of the kernel
configuration process that is a mess and hurts normal users pretty badly.
It's embarrassing. (Distributors like Mandrake can hide the mess from
people until they compile their own kernels.)
See, there are two drivers for IDE CD drives. One is the normal IDE CDROM
driver built into the IDE driver. This works for mounting ISO-9660 images
and reading files, but is bad for everything else. It is the default. It
has the advantages of not requiring SCSI support, saving some memory, and
being easier to set up.
The other driver is the IDE-SCSI emulation layer. This works better for
some things, including ripping music CD's. And, as you have discovered, it
is a requirement for CDR's. For example, using the IDE-SCSI driver I can
rip audio with my Toshiba DVD drive at 10x speed, but with the "normal IDE"
driver it could not even go at 1x speed.
In my configuration, I access both my CDR and DVD drives with the SCSI
emulation layer.
In the kernel config, I disable normal IDE CD support, turn ON SCSI support,
IDE-SCSI emulation, and turn ON Generic SCSI support and SCSI CD-ROM
support. You can also use modules for these drivers if you are really short
on memory.
On the kernel command line, you need the "hdc=ide-scsi" parameter. (Replace
hdc with whatever your CD device actually is.) This will be set in your
/etc/lilo.conf if you are using LILO as the bootloader, otherwise it will be
in /boot/grub/menu.lst if you are using GRUB as the boot loader.
Check to see how Mandrake originally set it up and copy that. If you
disabled normal IDE CD support, or just want to use the SCSI driver for both
drives, copy it for both CD drives - something like "hdc=ide-scsi
hdd=ide-scsi".
Then (sigh) you might need to mess around with stuff in your /dev directory,
so the /dev/cdrom is a symbolic link to the right real device. I have mine
set up with symbolic links /dev/cdrom for the DVD and /dev/cdr for the CDR,
with corresponding /mnt/cdrom and /mnt/cdr mountpoints. You may need to
edit your /etc/fstab as well.
Good luck!
Torrey
> -----Original Message-----
> From: Peter Moscatt [mailto:[email protected]]
> Sent: Friday, October 19, 2001 6:36 AM
> To: Linux Kernel Mailing List
> Subject: Can't see IDE CDR-W after compile ?
>
>
> I have recently compiled 2.4.10 onto my Mandrake 8.0
> installation.
>
> Since then I now can't access my CD burner, but am
> able to mount my normal IDE CDRom.
>
> As a matter of interest, I disabled the SCSII support
> - do I need to reinstate this option ?
>
> Pete
>
>
On Fri, Oct 19 2001, Torrey Hoffman wrote:
> The other driver is the IDE-SCSI emulation layer. This works better for
> some things, including ripping music CD's. And, as you have discovered, it
> is a requirement for CDR's. For example, using the IDE-SCSI driver I can
> rip audio with my Toshiba DVD drive at 10x speed, but with the "normal IDE"
> driver it could not even go at 1x speed.
THat is funny, since the code for ripping audio is in the generic CDROM
layer and this shared by both ide-cd and sr. Exactly the same cdb is
sent down regardless of your setup.
So maybe your ripping program is accessing the CDROM differently
depending on the bus type (eg using sg for sr, maybe?).
--
Jens Axboe
I use the cdparanoia ripper. Here's a quote from the
cdparanoia FAQ (cdparanoia III - alpha 9.8):
"Note that the native ATAPI driver is supported, but that IDE-SCSI
emulation works better with ATAPI drives. This is an issue of control;
the emulation interface gives cdparanoia complete control over the
drive whereas the native ATAPI driver insists on hiding the device
under an abstraction layer with poor error handling capabilities. Note
also that a number of ATAPI drives that do not work at all with the
ATAPI driver (error 006: Could not read audio) *will* work with
IDE-SCSI emulation."
That, (and the actual performance difference I experienced)
is about all I know about the reasons behind this problem.
I also used to read the cdrecord mailing list, and IIRC, Jorg
Schilling (author of cdrecord, general expert on CD ROM stuff)
is not too impressed with the default Linux driver. I don't
remember the details...
I do hope this gets sorted out properly in 2.5. Perhaps all
that's needed is better hints for people as they configure the
kernel, or an "auto-configure" that actually works for the 90%
of users who aren't experts on this stuff.
With the 2.5 makefile rewrites this may be easy to do.
Or perhaps the IDE-CD driver should be deprecated, kind of like
the old disk-only IDE driver?
Torrey
Jens Axboe wrote:
> On Fri, Oct 19 2001, Torrey Hoffman wrote:
> > The other driver is the IDE-SCSI emulation layer. This
> works better for
> > some things, including ripping music CD's. And, as you
> have discovered, it
> > is a requirement for CDR's. For example, using the
> IDE-SCSI driver I can
> > rip audio with my Toshiba DVD drive at 10x speed, but with
> the "normal IDE"
> > driver it could not even go at 1x speed.
>
> THat is funny, since the code for ripping audio is in the
> generic CDROM
> layer and this shared by both ide-cd and sr. Exactly the same cdb is
> sent down regardless of your setup.
>
> So maybe your ripping program is accessing the CDROM differently
> depending on the bus type (eg using sg for sr, maybe?).
>
> --
> Jens Axboe
>