"READ_BIG timed out" errors on acd0

[Garrett Cooper]

Scott I. Remick wrote:
> Predrag Punosevac wrote:
>> Why don't you mount your cd as
>>
>> su -
>> password
>> mount-t cd9660 /dev/acd0 /mnt
>>
>> You should see you disk mounted and songs like files that you can 
>> transfer to hard disk. Of course you
>> can convert them latter to some format you like best.
>
> # mount -t cd9660 /dev/acd0 /mnt
> mount_cd9660: /dev/acd0: Invalid argument
>
>> device          scbus
>> device          cd
>> device          pass
>
> Yes, all 3 of those are already in my kernel.
>
>> device     atapicam
>
> I also have this. Verified by the following dmesg output:
>
> cd0 at ata3 bus 0 target 0 lun 0
> cd0: <TSSTcorp CD/DVDW SH-S183L SB01> Removable CD-ROM SCSI-0 device
> cd0: 3.300MB/s transfers
> cd0: cd present [3281952 x 2048 byte records]
>
>> Finally, if you are running GNOME 2.16 or later, you must have HAL 
>> running 
>
> Yep:
>
> [root at desktop /data/home/scott]# ps -ax | grep hald
>   893  ??  Ss     0:59.80 /usr/local/sbin/hald
>   894  ??  I      0:00.02 hald-runner
>   904  ??  S      2:22.76 hald-addon-storage: /dev/da0 
> (hald-addon-storage)
>   907  ??  S      2:20.78 hald-addon-storage: /dev/da1 
> (hald-addon-storage)
>   910  ??  S      2:20.42 hald-addon-storage: /dev/da2 
> (hald-addon-storage)
>   913  ??  S      2:20.95 hald-addon-storage: /dev/da3 
> (hald-addon-storage)
>   918  ??  S      3:29.59 hald-addon-storage: /dev/cd0 
> (hald-addon-storage)
>
>
>> To figure out which CD/DVD drive you will be using, run the following 
>> command as root:
>>
>> # camcontrol devlist
>
> <Generic USB SD Reader 1.00>       at scbus0 target 0 lun 0 (pass0,da0)
> <Generic USB CF Reader 1.01>       at scbus0 target 0 lun 1 (pass1,da1)
> <Generic USB SM Reader 1.02>       at scbus0 target 0 lun 2 (pass2,da2)
> <Generic USB MS Reader 1.03>       at scbus0 target 0 lun 3 (pass3,da3)
> <TSSTcorp CD/DVDW SH-S183L SB01>   at scbus5 target 0 lun 0 (cd0,pass4)
>
>> The devices in parentheses at the end are important. You must make 
>> sure the /dev entries for those devices are writable by the users 
>> that will be using nautilus-cd-burner, totem, goobox, or sound-juicer.
>
> Hmm well I didn't realize that Sound Juicer used /dev/cd0, I figured 
> it used acd0 (which had suitable permissions). I granted write 
> permissions across the board for /dev/cd0 but that didn't fix it.
>
>> In addition to those devices, /dev/xpt* must also be writable to your 
>> nautilus-cd-burner, totem, goobox, and sound-juicer users. The 
>> following /etc/devfs.conf configuration will achieve the desired 
>> results given the above devlist:
>>
>> perm    cd0     0666
>> perm    xpt0    0666
>> perm    pass0   0666
>
> Those I also didn't have set, but granting permissions still doesn't 
> allow Sound Juicer to work.
>
> Basically the symptoms are that Sound Juicer detects the drive (as 
> "CD/DVDW SH-S183L") but never displays a track list. Grip loads up but 
> seems to freeze for several moments at a time... sometimes Grip will 
> display a track list for the duration of one freeze only to have it 
> vanish and say "no disc" after the next freeze. And periodically I see 
> messages like these in my /var/log/messages:
>
> Aug 29 17:42:10 desktop kernel: acd0: FAILURE - READ_BIG timed out
> Aug 29 17:43:59 desktop last message repeated 3 times
> Aug 29 17:43:59 desktop kernel: (cd0:ata3:0:0:0): cddone: got error 
> 0x5 back

    Try cd0, not acd0, or create appropriate links via /etc/devfs.conf.
Cheers,
-Garrett