CD burning impossible, (kernel) configuration wrong?

Li... · 03-31-2005, 07:04 PM

Ola,

since few days I try to burn a CD. Current system is kernel 2.4.24 and Debian distribution "SID". The problem: if the burn-program (cdrecord) starts up, the pc seem to be locked-up/hanging, but every 5 sec. the mouse pointer moves when it is moved. console input echoed every 5 sec. Thus, every 5 sec. the system reacts. cdrecord itself did not burn.

The cdrecord log:
-----
/root# cdrecord dev=0,1,0 gracetime=2 -v kdebug=9 speed=40 -eject -dao /tmp/image.iso
Cdrecord-Clone 2.01a34 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
[blabla]
TOC Type: 1 = CD-ROM
scsidev: '0,1,0'
scsibus: 0 target: 1 lun: 0
Linux sg driver version: 3.1.25
Using libscg version 'schily-0.8'.
SCSI buffer size: 64512
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'CyberDrv'
Identifikation : 'CW088D CD-R/RW '
Revision : '110F'
Device seems to be: Generic mmc CD-RW.
Current: 0x0009
Profile: 0x000A
Profile: 0x0009 (current)
Profile: 0x0008
Profile: 0x0002
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
Drive buf size : 1806336 = 1764 KB
cdrecord: Input/output error. read buffer: scsi sendcmd: cmd timeout after 10.110 (200) s
CDB: 3C 00 00 00 00 00 00 FC 00 00
cmd finished after 10.110s timeout 200s
FIFO size : 4194304 = 4096 KB
Track 01: data 541 MB
Total size: 621 MB (61:35.48) = 277161 sectors
Lout start: 622 MB (61:37/36) = 277161 sectors
-----
(Ctrl-C pressed after 2 or 3 minutes waiting)

cdrecord recongnizes the drive, but does nothing, except semi-freezing/locking-up the system. The LED which indicated thats the laser is working is always off.

SYSLOG

kernel boot (hdc=cdrom, hdd=cdrw):

kernel: Kernel command line: root=/dev/hda3 hdc=ide-scsi hdd=ide-scsi ro BOOT_IMAGE=bzi-2.424
[....]
kernel: ide_setup: hdc=ide-scsi
kernel: ide_setup: hdd=ide-scsi
[....]
kernel: hdc: SAMSUNG DVD-ROM SD-616Q, ATAPI CD/DVD-ROM drive
kernel: hdd: CW088D ATAPI CD-R/RW, ATAPI CD/DVD-ROM drive
kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
kernel: ide1 at 0x170-0x177,0x376 on irq 15
kernel: hda: attached ide-disk driver.
kernel: hda: host protected area => 1
kernel: hda: 160836480 sectors (82348 MB) w/1821KiB Cache, CHS=10011/255/63, UDMA(100)
kernel: hdc: attached ide-scsi driver.
kernel: hdd: attached ide-scsi driver.
[....]
kernel: SCSI subsystem driver Revision: 1.00
kernel: scsi0 : SCSI host adapter emulation for IDE ATAPI devices
kernel: Vendor: SAMSUNG Model: DVD-ROM SD-616Q Rev: F403
kernel: Type: CD-ROM ANSI SCSI revision: 02
kernel: Vendor: CyberDrv Model: CW088D CD-R/RW Rev: 110F
kernel: Type: CD-ROM ANSI SCSI revision: 02
kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
kernel: Attached scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0
kernel: sr0: scsi3-mmc drive: 1x/48x cd/rw xa/form2 cdda tray
kernel: Uniform CD-ROM driver Revision: 3.12
kernel: sr1: scsi3-mmc drive: 4x/48x writer cd/rw xa/form2 cdda tray
[....]

generated using cdrecord (cmd see above), tons of these msgs.:
kernel: hdd: ATAPI reset complete
kernel: hdd: status error: status=0x08 { DataRequest }
kernel: hdd: drive not ready for command
kernel: hdd: status timeout: status=0xd0 { Busy }
kernel: hdd: drive not ready for command
kernel: hdd: ATAPI reset complete
kernel: hdd: status error: status=0x08 { DataRequest }
kernel: hdd: drive not ready for command
kernel: hdd: status timeout: status=0xd0 { Busy }
kernel: hdd: drive not ready for command
kernel: scsi : aborting command due to timeout : pid 3720, scsi0, channel 0, id 1, lun 0 Test Unit Ready 00 00 00 00 00
kernel: SCSI host 0 abort (pid 3720) timed out - resetting
kernel: SCSI bus is being reset for host 0 channel 0.
kernel: SCSI host 0 channel 0 reset (pid 3720) timed out - trying harder
kernel: SCSI bus is being reset for host 0 channel 0.
kernel: hdd: ATAPI reset complete
[...]
kernel: sr1: CDROM (ioctl) error, command: Prevent/Allow Medium Removal 00 00 00 00 00
kernel: sr00:00: old sense key None
kernel: Non-extended sense class 0 code 0x0
kernel: scsi0 : channel 0 target 1 lun 0 request sense failed, performing reset.
kernel: SCSI bus is being reset for host 0 channel 0.
====================
EOF syslog

My opinion that due to kernel misconfiguration was that I can burn CD's when i've booted with the Knoppix-CD (3.7) and burn with that configuration. But I've checked the configuration so far and I can't find a reason why my kernel config is wrong.

The config-file /etc/cdrecord/cdrecord is configured as follows (fields with tabs delimited)

CDR_DEVICE=cdrw
CDR_FIFOSIZE=4m
cdrw= 0,1,0 -1 -1 ""
cdrom= 0,0,0 -1 -1 ""

$ ls -l /dev/cdrom /dev/cdrw /dev/scd0 /dev/scd1
lrwxrwxrwx 1 root root 4 Apr 1 01:20 /dev/cdrom -> scd0
lrwxrwxrwx 1 root root 4 Apr 1 01:20 /dev/cdrw -> scd1
brw-rw-rw- 1 root cdrom 11, 0 Mar 14 2002 /dev/scd0
brw-rw-rw- 1 root cdrom 11, 1 Mar 14 2002 /dev/scd1

Why can I burn with a Knoppix-Cd and not with my installtion?

Li

jailbait · 03-31-2005, 09:50 PM

"kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
kernel: Attached scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0"

The only thing that I can see is that maybe your CD devices are at sr0 and sr1 instead of scd0 and scd1.

Try linking
/dev/cdrom -> sr0
/dev/cdrw -> sr1
and see if that works.

----------------------------------
Steve Stites

Li... · 04-01-2005, 05:35 AM

sr0 and sr1 are symlinks to scd0 and scd1.

$ ls -l /dev/sr[01] /dev/scd[01] /dev/cd*
lrwxrwxrwx 1 root root 3 Aug 31 2003 /dev/cdrecorder -> sg0
lrwxrwxrwx 1 root root 4 Apr 1 01:20 /dev/cdrom -> scd0
lrwxrwxrwx 1 root root 4 Apr 1 01:20 /dev/cdrw -> scd1
brw-rw---- 1 root cdrom 24, 0 Mar 14 2002 /dev/cdu535
brw-rw-rw- 1 root cdrom 11, 0 Mar 14 2002 /dev/scd0
brw-rw-rw- 1 root cdrom 11, 1 Mar 14 2002 /dev/scd1
lrwxrwxrwx 1 root root 4 Mar 15 2003 /dev/sr0 -> scd0
lrwxrwxrwx 1 root root 4 Mar 15 2003 /dev/sr1 -> scd1

Li

jailbait · 04-01-2005, 10:30 AM

"Why can I burn with a Knoppix-Cd and not with my installtion?"

You should check how the Knoppix-CD has set up the CD-RW and see how that differs from how your Debian system has the CD-RW set up.

---------------------------
Steve Stites

thegeekster · 04-01-2005, 01:26 PM

Probably a dumb question, but are you using the correct scsi address for the device?.............What is the output of 'cdrecord -scanbus | grep -i 'cd-rom'.......

For myself, I created hdc and hdd symlinks pointing to sr0 and sr1, respectively, for my dvd burner and cd burner, and then pointed the /dev/dvd and /dev/cdrom symlinks to hdc and hdd, like so:

Code:

# ls -l /dev/{cdr*,dvd,hdc,hdd,sr[0-1],scd[0-1]}
lrwxrwxrwx  1 root root      8 2005-03-18 21:29 /dev/cdrom -> /dev/hdd
lrwxrwxrwx  1 root root      8 2005-03-19 11:45 /dev/cdrom0 -> /dev/hdc
lrwxrwxrwx  1 root root      8 2005-03-19 11:45 /dev/cdrom1 -> /dev/hdd
lrwxrwxrwx  1 root root      8 2005-03-18 21:29 /dev/dvd -> /dev/hdc
lrwxrwxrwx  1 root root      8 2005-03-19 08:38 /dev/hdc -> /dev/sr0
lrwxrwxrwx  1 root root      8 2005-03-19 08:39 /dev/hdd -> /dev/sr1
brw-rw----  1 root cdrom 11, 0 2005-02-25 22:43 /dev/scd0
brw-rw----  1 root cdrom 11, 1 2005-02-25 22:43 /dev/scd1
lrwxrwxrwx  1 root root      4 2005-03-18 10:12 /dev/sr0 -> scd0
lrwxrwxrwx  1 root root      4 2005-03-18 10:12 /dev/sr1 -> scd1

BTW, this is a Sarge install.........cdrom0 and cdrom1 were created by the installation..........All I did was to create the symlinks hdc, hdd, cdrom, and dvd while the rest of the symlinks were already done automatically......

Li... · 04-02-2005, 12:25 PM

The output of cdrecord -scanbus:

/root# cdrecord -scanbus | grep -i 'cd-rom'
Linux sg driver version: 3.1.25
0,0,0 0) 'SAMSUNG ' 'DVD-ROM SD-616Q ' 'F403' Removable CD-ROM
0,1,0 1) 'CyberDrv' 'CW088D CD-R/RW ' '110F' Removable CD-ROM

The device which is used by cdrecord is correct because the disc in this drive is spinning up to max. speed when the burn process begins. After few seconds the disc is spinning down and that was it with burning. Then the computer is semi-freezed/locked-up and then I have to cancel the burn process. If the burn process is canceled then the semi-freezed/locked-up state is over few seconds later. Under normal conditions when the process is canceled in k3b, k3b makes a 'ping' to speaker (via soundcard, not pc-internal speaker). During the semi-freezed state, this ping comes again and again (ping-ping-ping...) for the next 5 seconds cycle. Only for information, could be a clue.

Was it neccessary for you to create the both symlinks hdd and hdc? Makes it a difference in connection with burning?

jailbait · 04-02-2005, 02:38 PM

"The device which is used by cdrecord is correct because the disc in this drive is spinning up to max. speed when the burn process begins. After few seconds the disc is spinning down and that was it with burning. Then the computer is semi-freezed/locked-up and then I have to cancel the burn process. If the burn process is canceled then the semi-freezed/locked-up state is over few seconds later. Under normal conditions when the process is canceled in k3b, k3b makes a 'ping' to speaker (via soundcard, not pc-internal speaker). During the semi-freezed state, this ping comes again and again (ping-ping-ping...) for the next 5 seconds cycle. Only for information, could be a clue."

k3b uses cdrecord to do the actual burn. Perhaps your problem is incompatible versions of the kernel and cdrecord. Linus changed the way that the kernel handles CD recording in kernel 2.6. Jeorg Schilling was reluctant to change cdrecord to use the new kernel method. Some of the distributions, including SuSE, created patched version of cdrecord to make it work correctly on kernel 2.6. Perhaps Debian did the same. The result is that there are several versions of cdrecord in circulation which are very dependent on the kernel version that they are run on. You should check the Debian documentation to make sure that your version of cdrecord is compatible with your kernel version.

----------------------------
Steve Stites

thegeekster · 04-02-2005, 03:52 PM

Quote:

Originally posted by Li...
...Was it neccessary for you to create the both symlinks hdd and hdc? Makes it a difference in connection with burning?

No, it's not necessary (AFAIK).............It only helps to simplify things a bit when you point /dev/cdrom to the ide block device (/dev/hd?)........If, at a later date, you want to replace it with something different (such as a regular cdrom drive or a dvd-rom drive) you simply change the /dev/hd? to something appropriate......Be sure to rename /dev/hd?, if it is a regular block device, before creating the link in case you need to change it back in the future........

<EDIT> It might make a difference in some programs that look for /dev/hd? when trying to access the cdrom </EDIT>

And jailbait makes a valid point about what kernel you are using........If you're using a 2.6.x kernel, then you do NOT want scsi emulation (ide-scsi module)........Although I see you are not using 2.6.x kernel.......

thegeekster · 04-02-2005, 04:13 PM

BTW, are there any known issues in Linux with the Cyber Drive burner?..............That might be a possibility........

noridlo45 · 02-24-2006, 04:48 PM

To Li...

I was having what seems to be the same problem with my Cyber drive burner. It also would not burn from a live CD. I swapped for a Sony burner, problem fixed. My assumption is that Cyber drive does not work for Linux. I am using Kubuntu Breezy and liking it a lot.

Li... · 02-24-2006, 05:29 PM

It makes no differences between booting from a live CD (independent from the distribution) or from harddisk. But I've found out that I should wait, I would say 2 or 3 minutes, and then the burning sessions starts. During this wait time the computer is nearly the freezed state I've already mentioned. After these 2-3 minutes the frezzed state is over and I can use the computer as always.