Re: READ_BIG timed out errors on acd0
Sorry for the delay... I had memory issues I had to resolve first. I'm now ready to revisit this issue. Predrag Punosevac wrote: I will also mention something which is probably stupid. But you know that in FreeBSD you must have a wire between DVD/CD rom and audio card to be able to listen to CDs. Can you listen to the CDs? I have no clue if you could rip CD without that wire. The CD-audio cable is not used or needed for ripping which is also known as DAE = digital audio extraction. Garrett Cooper wrote: Try cd0, not acd0, or create appropriate links via /etc/devfs.conf. Sound Juicer doesn't allow you to pick between the two. It identifies the drive by name, not by its /dev entry, and it only gives me the one option. Everyone else: here's my original post for reference. I'm trying to doing a fresh buildworld with the latest -STABLE but it doesn't seem stable and isn't building as the tree currently is, so I might have to wait on that. I'm hoping there's a multimedia guru who can help walk me through a series of sensible troubleshooting steps in order to get to the bottom of this, because multimedia isn't my forte and I'm sort of flying by the seat of my pants here. Scott I. Remick wrote: Hello... I'm using 6.2-STABLE from Aug 8th. Trying to get a CD ripping program to work on this new box. Have used Grip in the past, also trying Sound Juicer but both are having issues... I think it's something to do with the drive. Here's what I get in /var/log/messages: Aug 29 00:30:52 desktop kernel: acd0: WARNING - TEST_UNIT_READY freeing taskqueue zombie request Aug 29 00:31:28 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:05 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:41 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:41 desktop kernel: (cd0:ata3:0:0:0): cddone: got error 0x5 back And so on and so forth. The drive is a Samsung SH-S183L DVD+RW connected via SATA: acd0: DVDR TSSTcorpCD/DVDW SH-S183L/SB01 at ata3-master SATA150 # atacontrol mode acd0 current mode = SATA150 I think the freezes I get with Grip and Sound Juicer are related to these errors. Any suggestions? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
I've got this message when I use cd-rw's in my cdrom drive, or when I use certain cdroms. It seems like the OS tries to read the cdrom and fails. It could be a bad sector on the cdrom, dust or something else. Joe 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 - Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
How about if you read first page from Chapter 18 from the Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html There are several rock solid command line programs for burning CDs and DVDs. Burn cd is the simplest one. cdrecord is the second one. Forgive me for saying this but before we declare something is wrong with hardware lets check if the thing can record from the command line when you are supper user. This way we will check if something is wrong with hardware or with configuration files i.e. permissions , links etc. If you can rip CD from the command line hardware is OK. Scott I. Remick wrote: Predrag Punosevac wrote: What happens when you try to rip a CD from the command line with let say burncd program? You'll have to forgive me... but I don't normally use burncd, and as far as I can tell from the man page there isn't a way to rip with it. Seems to be just for writing. Can you pass along the proper syntax? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
Predrag Punosevac wrote: How about if you read first page from Chapter 18 from the Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html There are several rock solid command line programs for burning CDs and DVDs. Burn cd is the simplest one. cdrecord is the second one. Except I am not trying to burn a CD. I am trying to rip (extract CD audio tracks into a file). Both burncd and cdrecord are for burning (writing) CDs, which is not the issue. Now, the dd command mentioned on that page... that I am familiar with, and already had tried. Through me for a loop at first since I thought it was outputting a .wav file, but once I realized it was just a raw PCM file I was able to play it fine. So it works. cdda2wav seems to extract a wav file fine, with no errors. File is playable. cdparanoia also creates a playable wav file just fine. Forgive me for saying this but before we declare something is wrong with hardware lets check if the thing can record from the command line when you are supper user. This way we will check if something is wrong with hardware or with configuration files i.e. permissions , links etc. If you can rip CD from the command line hardware is OK. It's not that I thought I had bad hardware, but I figured I might need some config/settings tweaks, especially since it's an SATA drive. Anyhow, sorry for the confusion... don't mean to seem dense. Just didn't seem like we were on the same page (burning vs. ripping). Hopefully the command-line results give you an idea of where to look next. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
Ok Scott I got you. You want to rip the CD. That should be easier. Let me suggest something elementary first. 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. Did you read Gnome project documentation on using sound juser as *Nautilus-cd-burner does not let me burn CDs or Totem/Goobox/Sound-juicer cannot find my CD/DVD drive. How can I fix this?* Nautilus-cd-burner, totem, goobox, and sound-juicer cannot use CD/DVD drives unless support for those devices is enabled in the kernel, and the permissions on the device nodes allow write access. Nautilus-cd-burner, totem, goobox, and sound-juicer talk to CD/DVD drives through the SCSI CAM subsystem. Therefore, you must make sure you have the following configured in your kernel: device scbus device cd device pass You must also make sure you have the following configured in your kernel if you are using an ATAPI CD/DVD drive: device atapicam Finally, if you are running GNOME 2.16 or later, you must have HAL running http://www.freebsd.org/gnome/docs/faq2.html#q19, or you will only be able to burn to an ISO image file. To figure out which CD/DVD drive you will be using, run the following command as root: # camcontrol devlist Your output will look similar to the following: QSI CDRW/DVD SBW-242 UD22 at scbus1 target 0 lun 0 (cd0,pass0) 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. 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: permcd0 0666 permxpt00666 permpass0 0666 If you encounter problems burning to discs with nautilus-cd-burner, set the following GConf /apps/nautilus-cd-burner/debug to /true/ using *Applications System Tools Configuration Editor* (gconf-editor from the command line). Then run nautilus-cd-burner from the command line, reproduce the problem you are having, and capture the output on the command line. Include this along with the rest of your bug report http://www.freebsd.org/gnome/docs/bugging.html. Let me know what is going on. Scott I. Remick wrote: Predrag Punosevac wrote: How about if you read first page from Chapter 18 from the Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html There are several rock solid command line programs for burning CDs and DVDs. Burn cd is the simplest one. cdrecord is the second one. Except I am not trying to burn a CD. I am trying to rip (extract CD audio tracks into a file). Both burncd and cdrecord are for burning (writing) CDs, which is not the issue. Now, the dd command mentioned on that page... that I am familiar with, and already had tried. Through me for a loop at first since I thought it was outputting a .wav file, but once I realized it was just a raw PCM file I was able to play it fine. So it works. cdda2wav seems to extract a wav file fine, with no errors. File is playable. cdparanoia also creates a playable wav file just fine. Forgive me for saying this but before we declare something is wrong with hardware lets check if the thing can record from the command line when you are supper user. This way we will check if something is wrong with hardware or with configuration files i.e. permissions , links etc. If you can rip CD from the command line hardware is OK. It's not that I thought I had bad hardware, but I figured I might need some config/settings tweaks, especially since it's an SATA drive. Anyhow, sorry for the confusion... don't mean to seem dense. Just didn't seem like we were on the same page (burning vs. ripping). Hopefully the command-line results give you an idea of where to look next. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
Predrag Punosevac wrote: Ok Scott I got you. You want to rip the CD. That should be easier. Let me suggest something elementary first. 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. Did you read Gnome project documentation on using sound juser as *Nautilus-cd-burner does not let me burn CDs or Totem/Goobox/Sound-juicer cannot find my CD/DVD drive. How can I fix this?* Nautilus-cd-burner, totem, goobox, and sound-juicer cannot use CD/DVD drives unless support for those devices is enabled in the kernel, and the permissions on the device nodes allow write access. Nautilus-cd-burner, totem, goobox, and sound-juicer talk to CD/DVD drives through the SCSI CAM subsystem. Therefore, you must make sure you have the following configured in your kernel: device scbus device cd device pass You must also make sure you have the following configured in your kernel if you are using an ATAPI CD/DVD drive: device atapicam Finally, if you are running GNOME 2.16 or later, you must have HAL running http://www.freebsd.org/gnome/docs/faq2.html#q19, or you will only be able to burn to an ISO image file. To figure out which CD/DVD drive you will be using, run the following command as root: # camcontrol devlist Your output will look similar to the following: QSI CDRW/DVD SBW-242 UD22 at scbus1 target 0 lun 0 (cd0,pass0) 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. 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: permcd0 0666 permxpt00666 permpass0 0666 If you encounter problems burning to discs with nautilus-cd-burner, set the following GConf /apps/nautilus-cd-burner/debug to /true/ using *Applications System Tools Configuration Editor* (gconf-editor from the command line). Then run nautilus-cd-burner from the command line, reproduce the problem you are having, and capture the output on the command line. Include this along with the rest of your bug report http://www.freebsd.org/gnome/docs/bugging.html. Let me know what is going on. Scott I. Remick wrote: Predrag Punosevac wrote: How about if you read first page from Chapter 18 from the Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html There are several rock solid command line programs for burning CDs and DVDs. Burn cd is the simplest one. cdrecord is the second one. Except I am not trying to burn a CD. I am trying to rip (extract CD audio tracks into a file). Both burncd and cdrecord are for burning (writing) CDs, which is not the issue. Now, the dd command mentioned on that page... that I am familiar with, and already had tried. Through me for a loop at first since I thought it was outputting a .wav file, but once I realized it was just a raw PCM file I was able to play it fine. So it works. cdda2wav seems to extract a wav file fine, with no errors. File is playable. cdparanoia also creates a playable wav file just fine. Forgive me for saying this but before we declare something is wrong with hardware lets check if the thing can record from the command line when you are supper user. This way we will check if something is wrong with hardware or with configuration files i.e. permissions , links etc. If you can rip CD from the command line hardware is OK. It's not that I thought I had bad hardware, but I figured I might need some config/settings tweaks, especially since it's an SATA drive. Anyhow, sorry for the confusion... don't mean to seem dense. Just didn't seem like we were on the same page (burning vs. ripping). Hopefully the command-line results give you an idea of where to look next. The big assumption is that the CD that you're ripping from doesn't have copyright protection on it. That kind of a CD will show that particular set of behavior in FreeBSD. For that case you'll have to grab a Mac or a Windows PC to properly rip the CD, and I recommend iTunes for that (apparently Apple made it simple to rip copyright protected CDs. Heh). I'm not trying to encourage anything illegal. I did that with a lot of Japanese CDs I own just because I prefer MP3/MP4 formatted tracks on my iPod / PC. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
cdda2wav seems to extract a wav file fine, with no errors. File is playable. cdparanoia also creates a playable wav file just fine. so use them especially last, as it corrects well music if CD isn't clean/is scratched dd is not for audio CDs, as RAW reading isn't supported by acd driver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
Ok Scott I got you. You want to rip the CD. That should be easier. Let me suggest something elementary first. Why don't you mount your cd as su - password mount-t cd9660 /dev/acd0 /mnt ripping CD means reading music out of it. not data CD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
Garrett Cooper wrote: The big assumption is that the CD that you're ripping from doesn't have copyright protection on it. That kind of a CD will show that particular set of behavior in FreeBSD. I'm pretty sure I'm safe... the CD I'm testing with at the moment is from 1990. :) It happened with another old CD too, but I thought it was due to some scratches on that one so I tried another. I'm not trying to encourage anything illegal. I did that with a lot of Japanese CDs I own just because I prefer MP3/MP4 formatted tracks on my iPod / PC. I prefer Ogg Vorbis, and I'd rather not have to scour the internet for songs that I already have the CDs for and could just rip/encode myself (in better-quality than what I'd find too). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
You are right! However the first page of the chapter 18 from the handbook (which I asked him to read first) does explain how to rip the Audio cd from the command line. My hunch was that everything is ok with his DVD rom and that the problem is some configuration file. Somebody also made a point that some audio CD are protected for ripping. I had no clue about that.(You see how often I rip CDs) Wojciech Puchar wrote: Ok Scott I got you. You want to rip the CD. That should be easier. Let me suggest something elementary first. Why don't you mount your cd as su - password mount-t cd9660 /dev/acd0 /mnt ripping CD means reading music out of it. not data CD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
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: [EMAIL PROTECTED] /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: permcd0 0666 permxpt00666 permpass0 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
Ok, That thing with mount is my stupidity (you are not trying to mount file system) people already commented on it. I looked again the book and in Chapter 18, section 18.6 first page they talk about ripping music (Duplicating CD) from the command line right after they talk about about burncd and cdrtools. In particular can you follow the subsection 18.6.5 from the handbook and rip a single song to a file? My sound juser works perfectly with the editing I followed from the FreeBSD Gnome book. Somebody mentioned that your CD might be protected from reading. I will also mention something which is probably stupid. But you know that in FreeBSD you must have a wire between DVD/CD rom and audio card to be able to listen to CDs. Can you listen to the CDs? I have no clue if you could rip CD without that wire. As I said I have the wire. I followed the FreeBSD-Gnome handbook and everything works as expected. 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: [EMAIL PROTECTED] /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: permcd0 0666 permxpt00666 permpass0 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
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: [EMAIL PROTECTED] /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: permcd0 0666 permxpt00666 permpass0 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
READ_BIG timed out errors on acd0
Hello... I'm using 6.2-STABLE from Aug 8th. Trying to get a CD ripping program to work on this new box. Have used Grip in the past, also trying Sound Juicer but both are having issues... I think it's something to do with the drive. Here's what I get in /var/log/messages: Aug 29 00:30:52 desktop kernel: acd0: WARNING - TEST_UNIT_READY freeing taskqueue zombie request Aug 29 00:31:28 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:05 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:41 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:41 desktop kernel: (cd0:ata3:0:0:0): cddone: got error 0x5 back And so on and so forth. The drive is a Samsung SH-S183L DVD+RW connected via SATA: acd0: DVDR TSSTcorpCD/DVDW SH-S183L/SB01 at ata3-master SATA150 # atacontrol mode acd0 current mode = SATA150 I think the freezes I get with Grip and Sound Juicer are related to these errors. Any suggestions? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: READ_BIG timed out errors on acd0
What happens when you try to rip a CD from the command line with let say burncd program? Scott I. Remick wrote: Hello... I'm using 6.2-STABLE from Aug 8th. Trying to get a CD ripping program to work on this new box. Have used Grip in the past, also trying Sound Juicer but both are having issues... I think it's something to do with the drive. Here's what I get in /var/log/messages: Aug 29 00:30:52 desktop kernel: acd0: WARNING - TEST_UNIT_READY freeing taskqueue zombie request Aug 29 00:31:28 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:05 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:41 desktop kernel: acd0: FAILURE - READ_BIG timed out Aug 29 00:32:41 desktop kernel: (cd0:ata3:0:0:0): cddone: got error 0x5 back And so on and so forth. The drive is a Samsung SH-S183L DVD+RW connected via SATA: acd0: DVDR TSSTcorpCD/DVDW SH-S183L/SB01 at ata3-master SATA150 # atacontrol mode acd0 current mode = SATA150 I think the freezes I get with Grip and Sound Juicer are related to these errors. Any suggestions? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
