Any version of cdrtools greater than, or equal to 2.01-alpha33 freezes and changes status to D+ when used with CYBERDRV CW058D CD-R/RW. app-cdr/cdrtools-2.01_alpha28-r2 works flawlessly, with no problems. Reproducible: Always Steps to Reproduce: 1. Any cdrecord command to CYBERDRV, i.e. cdrecord dev=ATAPI:0,1,0 -atip 2. See it freeze, and D+ 3. Doesn't respond to KILL Actual Results: There's some cdrecord output until it states the drive name, then it just locks up. Expected Results: The software should have continued, given atip information, burned a cd, etc. Portage 2.0.51_rc1 (gcc34-x86-2004.2, gcc-3.4.1, glibc-2.3.4.20040916-r0, 2.6.8-ck7 i686) ================================================================= System uname: 2.6.8-ck7 i686 Intel(R) Pentium(R) 4 CPU 2.26GHz Gentoo Base System version 1.5.3 distcc 2.17 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -Os -mfpmath=sse,387 -fomit-frame-pointer -fPIC -ftracer -fforce-addr -ffast-math -fweb -maccumulate-outgoing-args -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/share/config:/usr/kde/3.3/env:/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -Os -mfpmath=sse,387 -fomit-frame-pointer -fPIC -ftracer -fforce-addr -ffast-math -fweb -maccumulate-outgoing-args -pipe" DISTDIR="/var/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://adelie.polymtl.ca/ http://gentoo.eliteitminds.com ftp://ftp.ussg.iu.edu/pub/linux/gentoo" MAKEOPTS="-j2" PKGDIR="/var/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/var/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.ca.gentoo.org/gentoo-portage" USE="X aalib acpi aim alsa apache2 apm arts avi berkdb bidi bitmap-fonts bonobo bzlib canna cdparanoia cdr chroot cjk crypt cups curl dba dga divx4linux dv dvd dvdr dvdread edl encode esd faad fbcon ffmpeg flac flash foomaticdb gd gdbm gif gimpprint gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile icc icq imagemagick imlib innodb java jikes joystick jpeg kde kerberos ldap libg++ libwww live lzo mad matroska matrox memlimit mikmod mmx mmx2 mng monkey mono motif mozilla mpeg msn mysql ncurses nls nptl oav oggvorbis opengl oscar oss pam pdflib perl pic plotutils png ppds python qt quicktime readline rtc samba scanner sdl slang slp socks5 spell sse sse2 ssl stroke svg svga tcltk tcpd tetex theora tiff transcode truetype unicode usb videos wmf wxwindows x86 xine xinerama xml xml2 xmms xosd xprint xv xvid yahoo zlib zvbi video_cards_radeon"
Do you call cdrecord as user or as root? Are there any patches in your kernel for cd-recording (2.6.8.1 has several issues)? Did you tried a 2.6.9-rc-kernel? The CFLAGS -fPIC -ftracer -fforce-addr -ffast-math -fweb -maccumulate-outgoing-args look very "evil" to me; could you test compiling cdrtools-2.01 without these flags (especially -fPIC)?
I tried as both root, and user. I tried kernel 2.6.7 and below as well, and a kernel from the 2.6.9-series to no avail. I tried using a blank set of CFLAGs, and the problem is still there. I recently tried cdrtools-2.01, and it also doesn't work and after a while gives the message "cdrecord: Input/output error. read buffer: scsi sendcmd: no error CDB: 3C 00 00 00 00 00 00 FC 00 00 status: 0x0 (GOOD STATUS) cmd finished after 30.146s timeout 40s" and then proceeds to lock-up and become unkillable. Also I cannot try and access the device via hdparm or any other utility, once cdrecord locks up. It works flawlessly with cdrtools-2.01_alpha28-r2, so I believe the problem lies somewhere in cdrtools.
After waiting a while, the cdrecord from cdrtools 2.01 finally dies from KILL, leaving this in my kernel log: "hdd: status timeout: status=0xd0 { Busy } hdd: status timeout: error=0xd0LastFailedSense 0x0d hdd: DMA disabled hdd: drive not ready for command hdd: ATAPI reset timed-out, status=0x80 hdc: DMA disabled ide1: reset: success hdd: irq timeout: status=0xd0 { Busy } hdd: irq timeout: error=0xd0LastFailedSense 0x0d hdd: ATAPI reset complete hdd: status error: status=0x08 { DataRequest } hdd: status error: error=0x01IllegalLengthIndication hdd: drive not ready for command hdd: status timeout: status=0xd0 { Busy } hdd: status timeout: error=0xd0LastFailedSense 0x0d hdd: drive not ready for command hdd: ATAPI reset complete hdd: status error: status=0x08 { DataRequest } hdd: status error: error=0x01IllegalLengthIndication hdd: drive not ready for command hdd: status timeout: status=0xd0 { Busy } hdd: status timeout: error=0xd0LastFailedSense 0x0d hdd: drive not ready for command hdd: ATAPI reset complete hdd: status error: status=0x08 { DataRequest } hdd: status error: error=0x01IllegalLengthIndication hdd: drive not ready for command hdd: status timeout: status=0xd0 { Busy } hdd: status timeout: error=0xd0LastFailedSense 0x0d hdd: drive not ready for command hdd: ATAPI reset complete hdd: status error: status=0x08 { DataRequest } hdd: status error: error=0x01IllegalLengthIndication hdd: drive not ready for command"
Can you check with hdparm (before you use cdrecord), if DMA mode is set? Try to change the value and use cdrecord. There have been some changes to DMA-mode in cdrecord between the alpha28 and 2.01-release.
I checked with hdparm and DMA mode is set. When DMA is on it locks up, however when DMA is off it gives an error message: cdrecord: Input/output error. read buffer: scsi sendcmd: no error CDB: 3C 00 00 00 00 00 00 FC 00 00 status: 0x0 (GOOD STATUS) cmd finished after 1.816s timeout 40s 01 00 00 01 00 00 00 00 01 AA 01 01 00 00 00 00 Track 1 start -150 01 00 A0 00 00 00 00 01 00 00 00 00 01 00 A1 00 00 00 00 00 00 00 00 00 01 00 A2 00 00 00 00 00 00 00 00 00 cdrecord: Cannot load media. And it fills dmesg with: hdd: drive not ready for command hdd: status timeout: status=0xd0 { Busy } hdd: status timeout: error=0xd0LastFailedSense 0x0d hdd: drive not ready for command hdd: ATAPI reset complete hdd: status error: status=0x08 { DataRequest } hdd: status error: error=0x01IllegalLengthIndication hdd: drive not ready for command Unfortunately I cannot downgrade to a working cdrtools as that ebuild has been pruned from portage.
I still have no clue about your problem, but according to a quick search you are not the only one. Probably you should test with enabling scsi-emulation (though it is deprecated).
Tried that already, no luck.
Closing that bug, as I never heard anything more.
According to this forum post: http://forums.gentoo.org/viewtopic-t-240670-highlight-cyberdrive.html the bug still exists; It in fact exists with my friends CyberDrive CW088D. The workaround was to download a previous version of cdrecord (I believe from Debian). I have not (yet) tried the work around on my friend's computer.
