Readcd doesn't seem to work on my system. Here's some output:

$ readcd -scanbus
readcd: No such file or directory. Cannot open SCSI driver.
$ sudo readcd -scanbus
Password:
/usr/bin/readcd: No such file or directory. Cannot open SCSI driver.
$ sudo readcd dev=1,0,0 f=test.iso
/usr/bin/readcd: Success. Cannot open SCSI driver.
/usr/bin/readcd: For possible targets try 'readcd -scanbus'.
/usr/bin/readcd: For possible transport specifiers try 'readcd dev=help'.

I looked through some newsgroup posts, and in older versions of Fedora magicdev seemed to be the problem. Magicdev has been killed off apparently, and I found a page that claims that hald is now a problem for CD devices. After killing all hald processes I get identical error messages:

$ ps -ef | grep -i hal
root 2839 1 0 19:00 ? 00:00:00 hald --retain-privileges
root 2844 2839 0 19:00 ? 00:00:00 hald-addon-acpi
root 2850 2839 0 19:00 ? 00:00:00 hald-addon-storage
root 2852 2839 0 19:00 ? 00:00:00 hald-addon-storage
root 2854 2839 0 19:00 ? 00:00:00 hald-addon-storage
root 2856 2839 0 19:00 ? 00:00:00 hald-addon-storage
root 2871 2839 0 19:00 ? 00:00:00 hald-addon-storage
alue 3427 3364 0 19:06 pts/0 00:00:00 grep -i hal
$ sudo kill -9 2839 2844 2850 2852 2854 2856 2871
$ ps -ef | grep -i hal
alue 3437 3364 0 19:07 pts/0 00:00:00 grep -i hal
$ sudo readcd -scanbus
/usr/bin/readcd: No such file or directory. Cannot open SCSI driver.
$ sudo readcd dev=1,0,0 f=test.iso
/usr/bin/readcd: Success. Cannot open SCSI driver.
/usr/bin/readcd: For possible targets try 'readcd -scanbus'.
/usr/bin/readcd: For possible transport specifiers try 'readcd dev=help'.

Any idea what the problem might be?

Fritz

did this occur outa the blue?

No this happens all the time. In fact it always happened; I just never did anything about it before.

Fritz

I forgot to mention I'm on a AMD Athlon(tm) 64 Processor 3000+ CPU and that I'm using the 64-bit version of Fedora Core 4. That might have something to do with it -- who knows.

Fritz

try a decent front end like k3b from the cmd line and read the msgs.. make sure you have k3bsetup installed as well.

and get ready to try either a different burner, and/or trying this one in another sys.

I have the same CPU too. And I found a solution.

#cd /dev
#ln -s hdc pg0

The pg0 is the scsi driver's prefer name. I learned that
when I was fighting to get cdrecord work in my system.

/dev/hdc is my cd recorder drive .

John