[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

CD recording



Hello everyone,

I'm posting this to debian-user partially because everyone in the CD recording 
department seem a little upset these days, and partially because I suspect 
that my problem involves quite a few different components.

Since 2.6.8, I've been unable to burn CDs. Nothing new here, we've all heard 
of the famous root/non-root issue that appeared with 2.6.8. Unfortunately, 
this doesn't seem to be my issue, because I can't burn CDs as root either.

My CD burner is /dev/hdd, which does come up when I scan the ATA bus as disk 
1,1,0 - at least until I try one of the following:
a. burn a CD
b. do a -checkdrive (which xcdroast does)...

I can -checkdrive my DVD drive without problems, but when I -checkdrive the CD 
writer it turns into a process like this:
 4086 ?        D      0:05 cdrecord mmap dev= /dev/hdd -v -checkdrive

It stays there forever - I can't "kill -9" it or anything. I have to reboot to 
get it away. The same thing happens if I try to burn a cd. Then, after this 
eternal not-good-for-anything process has been started, subsequent tries to 
burn a CD nearly hangs my system, and then does nothing after presenting me 
with:

Device type    : Removable CD-ROM
Version        : 0
Response Format: 1
Vendor_info    : 'CyberDrv'
Identifikation : 'CW088D CD-R/RW  '
Revision       : '15HF'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-2 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R

At this point the responsiveness is near zero, but CTRL-C gives me some CPU 
cycles back after ~10 secs. Then I get this:

cdrecord: Success. read buffer: scsi sendcmd: no error
CDB:  3C 00 00 00 00 00 00 FC 00 00
status: 0xb (Reserved)
Sense Bytes:
Sense Key: 0xFFFFFFFF [], Segment 0
Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0
Sense flags: Blk 0 (not valid)
resid: 64508
cmd finished after 46.141s timeout 40s

Not much of a success though, it hasn't even "spun up" my drive.


All drive commands make the system unresponsive, and must be CTRL-C'ed to do 
anything else. Examples: eject, hdparm.

If I try to burn a CD in k3b before one of these evil cdrecord processes 
appear, the drive "spins up", and subsequent access to the drive (trying to 
burn again) just hangs.

It is very tedious to do any kind of debugging of this problem, because I have 
to restart my computer every thirty seconds to "reclaim" my drive.

Any ideas, or even suggestions on how to get rid of the cdrecord processes 
that are claiming my drive without rebooting, are greatly appreciated! I 
think this problem is rather big. After all, I shouldn't be able to 
completely bork up my system like this does.

Oh yeah, some versions and such is probably useful:

ulv:~# uname -r
2.6.8-2-k7

ulv:~# cdrecord --version
Cdrecord-Clone 2.01.01a01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg 
Schilling
-- 
Sigve Indregard

A crisis is when you can't say "let's forget the whole thing."
  (Ferguson's Precept)



Reply to: