On Tuesday 02 May 2006 17:10, Stefan Srdic wrote: > anoop aryal wrote: [snip]
> > ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xBFA8 irq 15 > usb 1-2: device not accepting address 2, error -71 > ata2: dev 0 cfg 49:0b00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 > 88:0407 > ata2: dev 0 ATAPI, max UDMA/33 > ata2: dev 0 configured for UDMA/33 > scsi1 : ata_piix > ata2(0): WARNING: ATAPI is disabled, device ignored. > > SATA ATAPI support is still experimental, therefore it is disabled by > default. > > There are two ways to enable libata atapi support in the kernel. Which > you you do this depends on how your kernel is compiled. > > If the SATA drivers are compiled directly into the kernel try using the > boot option libata.atapi_enabled=1 > > If the SATA drivers are compiled as modules you need to add the line: > > options libata atapi_enabled=1 > > to /etc/modules.conf > > Read the update-modules.modutils manual page to learn how to this is > done the debian way. > > If that works your ATAPI device should be configure as /dev/sr0. thanks for the advice, it works now. i had to put the option in /etc/mkinitrd/modules. i think the reason was that - since i'm using initrd and therefore the boot options didn't work - by the time modules in /etc/modules were loaded, it was already too late. the initrd wanted to load ata_piix (apparently for the hard sata drive(?)) which depended on libata which would get loaded without any options if i didn't put them in /etc/mkinitrd/modules. once i did, and remade the initrd, it worked like a charm. thanks for your help. [snip] > > Thanks > > Stefan -- anoop aryal [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
