Dear sirs, i would agree if the errors appeared only when i pass ide-scsi at 
boot time.
But when i didn't pass it, i can neither access the cdrom drive !!!


When i use the linus kernel, i have the same problem, so i think it is a 
kernel-related problem, not just llinked to ide-cd nor ide-scsi nor 
supermount.
Stef

Le Jeudi 23 Mai 2002 01:41, Doug McClendon a �crit :
> Seth Zirin wrote:
> > This appears to me to be neither a kernel problem nor a cooker problem
> > - just a simple configuration error.
> >
> > While the equivalent of "hdc=ide-scsi" must be appended to the boot
> > command for a CD-writer in this scenario, you must also arrange for
> > the ide-cd driver to ignore the device by adding something like
> > "options ide-cd ignore=hdc" to /etc/modules.conf.  The ide-scsi driver
> > cannot control a device once it is claimed by the ide-cd driver.
>
> Thats not exactly true.  Ever try something like this in an init script-
> (if someone wants to offer a cleaner way to do this, I'm all ears)
>
> pushd /proc/ide > /dev/null
> for ide_interface in $( echo ide? ); do
>     [ "$ide_interface" = "ide?" ] && continue
>     cd $ide_interface
>         for ide_device in $( echo hd? ); do
>             [ "$ide_device" = "hd?" ] && continue
>             cd $ide_device
>                 if ( cat model | grep -q "^CD-R" ); then
>                     echo -n ide_scsi:1 >
> /proc/ide/${ide_interface}/${ide_device}/settings
>                     echo -n ide-scsi >
> /proc/ide/${ide_interface}/${ide_device}/driver
>                 fi
>             cd ..
>         done
>     cd ..
> done
> popd > /dev/null
>
> # load ide-scsi and sr_mod modules now that any cd-writers have been
> # told that they will be using the ide-scsi+sr_mod driver
> /sbin/insmod -q ide-scsi
> /sbin/insmod -q sr_mod
>
> > The success with other kernels is likely caused by kernel
> > configuration differences.  The ide-cd driver will always ignore a
> > CD-Writer when the driver is not configured.  Further information is
> > available in the CD-Writing HOWTO...
> >
> > [EMAIL PROTECTED]
> >
> >
> > -----Original Message-----
> > From: St�phane Teletch�a [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, May 22, 2002 6:16 AM
> > To: [EMAIL PROTECTED]; Ron Stodden
> > Subject: Re: [Cooker] Hanging for the cdrom ...
> >
> > Le Mercredi 22 Mai 2002 14:00, St�phane Teletch�a a �crit :
> > > Le Mercredi 22 Mai 2002 09:45, St�phane Teletch�a a �crit :
> > > > Le Mercredi 22 Mai 2002 04:30, Ron Stodden a �crit :
> > > > > St�phane Teletch�a wrote:
> > > > > > Le Mardi 21 Mai 2002 13:47, Ron Stodden a �crit :
> > > > > > > OK, thanks.
> > > > > > >
> > > > > > > You should have "idc=ide-scsi" in the append of _all_ linux
> > > > > > > stanzas. This and issue "lilo" as superuser and reboot is
> >
> > all that
> >
> > > > > > > is needed to make your cdwriter accessible to reading as
> >
> > /dev/scd0
> >
> > > > > > > or /dev/sr0 (mount in your /etc/fstab on /mnt/scd0 (you must
> >
> > mkdir
> >
> > > > > > > this directory yourself), for example) and for writing as the
> > > > > > > dev=n1,n2.n3 given by cdrecord -scanbus.
> > > > > >
> > > > > > If it was as easy as this ...
> > > > >
> > > > > It is.  Mind you, I do not use any supermount, nor see any need for
> > > > > it.  Try it without supermount - if OK, complain about supermount.
> > > >
> > > > I tried without and with supermount, this is the first thing i
> >
> > did, but
> >
> > > > it didn't change anything.
> > > > That's why i tried different kernels.
> > > > That's why i told you it would be far too easy.
> > > > Stef
> > >
> > > I'm using for the moment 2.4.3-20mdk kernel which works perfectly
> >
> > for the
> >
> > > cdrom drive.
> > >
> > > Stef
> >
> > As told me wally, i used the 2.4-linus kernel and the problem is still
> > there,
> > so it is definitely a kernel problem. I report them my complain.
> > Happy coding.
> > Stef

Reply via email to