Le Lundi 12 Janvier 2004 08:52, John Stamp a écrit :
> I had the same problem, too. It looks like k3b assumes that cdrdao
> 1.1.7-5 cannot handle the new kernel ATAPI interface. You need to
> change a line to let k3b recognize cdrdao's new abilities. Anyway,
> this did the trick for me:
> > --- k3b-0.10.3.orig/src/core/k3bdefaultexternalprograms.cpp
> > +++ k3b-0.10.3/src/core/k3bdefaultexternalprograms.cpp
> > @@ -521,7 +521,7 @@
> >
> >
> > // SuSE 9.0 ships with a patched cdrdao 1.1.7 which contains
> > an updated libschily - if( bin->version > K3bVersion( 1, 1, 7 )
> > ||
> > + if( bin->version > K3bVersion( 1, 1, 6 ) ||
> > ( bin->version == K3bVersion( 1, 1, 7 ) &&
> > bin->version.suffix() == "-suse" ) ) { bin->addFeature(
> > "plain-atapi" );
> > bin->addFeature( "hacked-atapi" );
shouldn't this patch be proposed for k3b, if isn't already set in
mainstream? But I don't know and didn't find if the version of cdrdao
in Cid supports atapi with kernel 2.6? If so, the code above should
also check the kernel version rather than base only on cdrdao
version.
Correct me if I am wrong but it is the combination of cdrdao 1.1.7 and
kernel 2.6 that makes trouble. Because cdrdao handles atapi devices
only with kernel 2.6 (without scsi emulation I mean).
Maybe I misunderstand all this....
--
Germain CHAZOT
* germs@gpl.insa-lyon.fr
* http://gpl.insa-lyon.fr/~germs
* Président de l'association GPL <http://gpl.insa-lyon.fr>
Attachment:
pgpxBTXGH8l6A.pgp
Description: signature