I recently installed Suse 9.2 Professional on my AMD Atholon2400 machine
(512 ram). I'm generally pleased with the performance, but have one
nagging issue:
The cd drive an ATAPI COMBO52XMAX will not write to a cd. (it reads data
and plays music CD's fine) I've checked the SuSe knowledge base, and
tried the support email, neither with any luck. I searched the archives
of this list in "Aims", and it seems that several others reported
similar difficulties in 9.2 - but none of the suggested solutions did
the trick. Here is the situation:
-When I click on the "cdrecorder" icon I get an error message in a
dialog box:
The folder contents could not be displayed.
Sorry, couldn't display all the contents of "cdrecorder".
-When I attempt to use K3b to make a data cd I get the following
debugging output:
System
-----------------------
K3b Version:0.11.15cvs
KDE Version: 3.3.0
QT Version: 3.3.3
cdrdao
-----------------------
Cdrdao version 1.1.9 - (C) Andreas Mueller
On Thu, 2005-02-17 at 17:21 -0600, Regis Matejcik wrote:
I recently installed Suse 9.2 Professional on my AMD Atholon2400 machine (512 ram). I'm generally pleased with the performance, but have one nagging issue:
The cd drive an ATAPI COMBO52XMAX will not write to a cd. (it reads data and plays music CD's fine) I've checked the SuSe knowledge base, and
<Snip> I'd like to see the output of the following (from a terminal, as root): cdrecord dev=ATA -scanbus You might want to try a cd recording from the CLI too. Assuming you have a suitable iso ready made: cdrecord -v -eject driveropts=burnfree speed=16 dev=ATA:x,x,x -dao <path-to-iso> All on one line, and x,x,x replaced by the output from cdrecord dev=ATA -scanbus. The speed number should be conservative for testing; no more than 1/3 of the rated top speed of the drive. -- N. B. Day Registered User 333228 at http://counter.li.org 1:23pm up 4 days 6:02, 2 users, load average: 0.13, 0.08, 0.08 SuSE Linux 9.2 (i586)
On Fri, 2005-02-18 at 13:23 -0600, N. B. Day wrote:
On Thu, 2005-02-17 at 17:21 -0600, Regis Matejcik wrote:
I recently installed Suse 9.2 Professional on my AMD Atholon2400 machine (512 ram). I'm generally pleased with the performance, but have one nagging issue:
The cd drive an ATAPI COMBO52XMAX will not write to a cd. (it reads data and plays music CD's fine) I've checked the SuSe knowledge base, and
<Snip>
I'd like to see the output of the following (from a terminal, as root):
cdrecord dev=ATA -scanbus
You might want to try a cd recording from the CLI too. Assuming you have a suitable iso ready made:
cdrecord -v -eject driveropts=burnfree speed=16 dev=ATA:x,x,x -dao <path-to-iso>
All on one line, and x,x,x replaced by the output from cdrecord dev=ATA -scanbus. The speed number should be conservative for testing; no more than 1/3 of the rated top speed of the drive.
-- N. B. Day Registered User 333228 at http://counter.li.org 1:23pm up 4 days 6:02, 2 users, load average: 0.13, 0.08, 0.08 SuSE Linux 9.2 (i586)
Thanks for the reply N. B. Here are the results of cdrecord dev=ATA -scanbus as you requested: regis@linux:~> su Password: linux:/home/regis # cdrecord dev=ATA -scanbus Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this versio n. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 Warning: Using badly designed ATAPI via /dev/hd* interface. Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de- scsi-linux-sg.c-1.83-resmgr-patch '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling'). scsibus0: 0,0,0 0) * 0,1,0 1) 'ATAPI ' 'COMBO52XMAX ' '1.40' Removable CD-ROM 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * linux:/home/regis # I haven't tried the command line option yet. Thanks Regis Matejcik
On Fri, 2005-02-18 at 13:52 -0600, Regis Matejcik wrote:
On Fri, 2005-02-18 at 13:23 -0600, N. B. Day wrote:
On Thu, 2005-02-17 at 17:21 -0600, Regis Matejcik wrote:
<Whack>
Here are the results of cdrecord dev=ATA -scanbus as you requested:
regis@linux:~> su Password: linux:/home/regis # cdrecord dev=ATA -scanbus Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this versio n. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 Warning: Using badly designed ATAPI via /dev/hd* interface. Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de- scsi-linux-sg.c-1.83-resmgr-patch '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling'). scsibus0: 0,0,0 0) * 0,1,0 1) 'ATAPI ' 'COMBO52XMAX ' '1.40' Removable CD-ROM 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * linux:/home/regis #
I haven't tried the command line option yet.
It looks to me as if this device is a "slave" without a "master," i.e. it is device #1 on the IDE port where there is _no_ device #0. This sometimes works, but is likely to cause trouble like what you're experiencing: plays ok but can't record. If I'm right you'll find that the jumper on the drive is set to slave (this is how most of them ship) or you've got it in the middle of a cable-select cable (any 80 wire new flat cable or round cable) with cable-select jumpered. If you can, take a look at the jumpers on the back, confirm that either Master or CS is selected and put it on the end of the IDE cable. I just looked at your original message: it looks as if you have an hdc which is a hard disk and hdb which is this cdrw device. This suggests to me that (1) the cdrw is jumpered wrong and (2) the hard drive is plugged into IDE1 and the cdrw is in IDE0. I'd check the cdrw jumpers and verify that the hd is attached to the primary IDE port and the cdrw goes to the secondary. This should be silkscreened into the motherboard, but the mb manual (if you have it) is often easier to read. One more thing to try, again from a terminal: hdparm -iI /dev/hda Then /dev/hdb, /dev/hdc, and /dev/hdd. This should tell you where things are. HTH -- N. B. Day Registered User 333228 at http://counter.li.org 3:15pm up 4 days 7:54, 2 users, load average: 0.12, 0.09, 0.09 SuSE Linux 9.2 (i586)
On Fri, 2005-02-18 at 15:16 -0600, N. B. Day wrote:
On Fri, 2005-02-18 at 13:52 -0600, Regis Matejcik wrote:
On Fri, 2005-02-18 at 13:23 -0600, N. B. Day wrote:
On Thu, 2005-02-17 at 17:21 -0600, Regis Matejcik wrote:
<Whack>
It looks to me as if this device is a "slave" without a "master," i.e. it is device #1 on the IDE port where there is _no_ device #0. This sometimes works, but is likely to cause trouble like what you're experiencing: plays ok but can't record.
If I'm right you'll find that the jumper on the drive is set to slave (this is how most of them ship) or you've got it in the middle of a cable-select cable (any 80 wire new flat cable or round cable) with cable-select jumpered. If you can, take a look at the jumpers on the back, confirm that either Master or CS is selected and put it on the end of the IDE cable.
I just looked at your original message: it looks as if you have an hdc which is a hard disk and hdb which is this cdrw device. This suggests to me that (1) the cdrw is jumpered wrong and (2) the hard drive is plugged into IDE1 and the cdrw is in IDE0. I'd check the cdrw jumpers and verify that the hd is attached to the primary IDE port and the cdrw goes to the secondary. This should be silkscreened into the motherboard, but the mb manual (if you have it) is often easier to read.
One more thing to try, again from a terminal: hdparm -iI /dev/hda Then /dev/hdb, /dev/hdc, and /dev/hdd. This should tell you where things are. HTH
-- N. B. Day Registered User 333228 at http://counter.li.org 3:15pm up 4 days 7:54, 2 users, load average: 0.12, 0.09, 0.09 SuSE Linux 9.2 (i586)
Thanks N.B., You were correct about the jumper setting and the cable select cable connected in the middle (but it was the hard drive that was connected in the middle). I've corrected those items. The mother board IDE plugs are labeled IDE1 and IDE2. The hard drive is plugged into IDE1 the ATAPI CD Drive is plugged into IDE2. Unfortunately, after making those changes and rebooting. I get virtually the same results. For what it's worth the current results of cdrecord dev=ATA -scanbus are: linux:/home/regis # cdrecord dev=ATA -scanbus Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling Note: This version is an unofficial (modified) version Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 Warning: Using badly designed ATAPI via /dev/hd* interface. Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.83-resmgr-patch '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling'). scsibus1: 1,0,0 100) 'ATAPI ' 'COMBO52XMAX ' '1.40' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * Any other ideas? Thanks, Regis
On Sat, 2005-02-19 at 14:24, Regis Matejcik wrote:
On Fri, 2005-02-18 at 15:16 -0600, N. B. Day wrote:
On Fri, 2005-02-18 at 13:52 -0600, Regis Matejcik wrote:
On Fri, 2005-02-18 at 13:23 -0600, N. B. Day wrote:
On Thu, 2005-02-17 at 17:21 -0600, Regis Matejcik wrote: <Various snips>
One more thing to try, again from a terminal: hdparm -iI /dev/hda Then /dev/hdb, /dev/hdc, and /dev/hdd. This should tell you where things are. HTH
<More snips>
You were correct about the jumper setting and the cable select cable connected in the middle (but it was the hard drive that was connected in the middle). I've corrected those items.
The mother board IDE plugs are labeled IDE1 and IDE2. The hard drive is plugged into IDE1 the ATAPI CD Drive is plugged into IDE2.
Unfortunately, after making those changes and rebooting. I get virtually the same results. For what it's worth the current results of cdrecord dev=ATA -scanbus are:
1.83 04/05/20 Copyright 1997 J. Schilling'). scsibus1: 1,0,0 100) 'ATAPI ' 'COMBO52XMAX ' '1.40' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) *
Any other ideas?
Thanks,
Regis
Well, that's progress at least. I'd still like to see the results of hdparm -iI /dev/hda ..../dev/hdd. It is possible too, that the burning laser in your cdrw is knackered: this would allow you to read but not write with the device. At work, I'd just test this by substitution of a known good cdrw; at home, well.... I'd get myself into a world of trouble by taking the cdrw out of my wife's machine (probably after suggesting that she's lost so much weight that she must have nothing in her closet that fits and sending her to the mall). Do you have Knoppix or some other live-cd version of linux? Could you try a command-line burn with one of those? -- N. B. Day N 30, 1.2033 W 90, 4.0460 20:10:30 up 4 days, 2:13, 2 users, load average: 0.23, 0.10, 0.08 Mandrake Linux release 10.0 (Official) for i586
On Sat, 2005-02-19 at 20:11 -0600, nbday wrote:
On Sat, 2005-02-19 at 14:24, Regis Matejcik wrote:
On Fri, 2005-02-18 at 15:16 -0600, N. B. Day wrote:
On Fri, 2005-02-18 at 13:52 -0600, Regis Matejcik wrote:
On Fri, 2005-02-18 at 13:23 -0600, N. B. Day wrote:
On Thu, 2005-02-17 at 17:21 -0600, Regis Matejcik wrote: <Various snips>
One more thing to try, again from a terminal: hdparm -iI /dev/hda Then /dev/hdb, /dev/hdc, and /dev/hdd. This should tell you where things are. HTH
<More snips>
Well, that's progress at least. I'd still like to see the results of hdparm -iI /dev/hda ..../dev/hdd. It is possible too, that the burning laser in your cdrw is knackered: this would allow you to read but not write with the device. At work, I'd just test this by substitution of a known good cdrw; at home, well.... I'd get myself into a world of trouble by taking the cdrw out of my wife's machine (probably after suggesting that she's lost so much weight that she must have nothing in her closet that fits and sending her to the mall).
Do you have Knoppix or some other live-cd version of linux? Could you try a command-line burn with one of those?
It's always possible that the device is "knackered". I'm tempted to pick up another drive just to try it. May do that if nothing here strikes you as a possible solution. I do have a Knoppix CD, but... Maybe I'm missing something, but it runs directly from the cd drive. How would I test the burning laser with the Knoppix disk in the drive? In any event.. Here is the output from hdparm -iI /dev/hda , b,c,& d Here is hdparm -I /dev/hda: Model=WDC WD1200JB-00EVA0, FwRev=15.05R15, SerialNo=WD-WCAEK1616179 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq } RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=74 BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234441648 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 AdvancedPM=no WriteCache=enabled Drive conforms to: device does not report version: * signifies the current active mode ATA device, with non-removable media Model Number: WDC WD1200JB-00EVA0 Serial Number: WD-WCAEK1616179 Firmware Revision: 15.05R15 Standards: Supported: 6 5 4 3 Likely used: 6 Configuration: Logical max current cylinders 16383 65535 heads 16 1 sectors/track 63 63 -- CHS current addressable sectors: 4128705 LBA user addressable sectors: 234441648 LBA48 user addressable sectors: 234441648 device size with M = 1024*1024: 114473 MBytes device size with M = 1000*1000: 120034 MBytes (120 GB) Capabilities: LBA, IORDY(can be disabled) bytes avail on r/w long: 74 Queue depth: 1 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 128, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * READ BUFFER cmd * WRITE BUFFER cmd * Host Protected Area feature set * Look-ahead * Write cache * Power Management feature set Security Mode feature set SMART feature set * FLUSH CACHE EXT command * Mandatory FLUSH CACHE command * Device Configuration Overlay feature set * 48-bit Address feature set * Automatic Acoustic Management feature set SET MAX security extension * DOWNLOAD MICROCODE cmd * SMART self-test * SMART error logging Security: supported not enabled not locked not frozen not expired: security count not supported: enhanced erase HW reset results: CBLID- above Vih Device num = 0 determined by CSEL Checksum: correct hdb: linux:/home/regis # hdparm -iI /dev/hdb /dev/hdb: No such device or address linux:/home/regis # hdc: /dev/hdc: Model=ATAPI COMBO52XMAX, FwRev=VER 1.40, SerialNo= Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=0kB, MaxMultSect=0 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 IORDY=yes, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 AdvancedPM=no * signifies the current active mode ATAPI CD-ROM, with removable media Model Number: ATAPI COMBO52XMAX Serial Number: Firmware Revision: VER 1.40 Standards: Likely used CD-ROM ATAPI-1 Configuration: DRQ response: 50us. Packet size: 12 bytes Capabilities: LBA, IORDY(cannot be disabled) DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=227ns IORDY flow control=120ns hdd: linux:/home/regis # hdparm -iI /dev/hdd /dev/hdd: No such device or address linux:/home/regis # Thanks again for your help on this. I may pick up a new drive this afternoon if this looks like a dead end. Regis
On Sun, 2005-02-20 at 08:50, Regis Matejcik wrote: <Many big whacks>
Here is hdparm -I /dev/hda:
Model=WDC WD1200JB-00EVA0, FwRev=15.05R15, SerialNo=WD-WCAEK1616179 Obviously a newish Western Digital HD
<Much removed>
hdb: linux:/home/regis # hdparm -iI /dev/hdb /dev/hdb: No such device or address linux:/home/regis #
With no slave device.
hdc: /dev/hdc:
Model=ATAPI COMBO52XMAX, FwRev=VER 1.40, SerialNo= Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=0kB, MaxMultSect=0 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 IORDY=yes, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 AdvancedPM=no
* signifies the current active mode
ATAPI CD-ROM, with removable media Model Number: ATAPI COMBO52XMAX Serial Number: Firmware Revision: VER 1.40 Standards: Likely used CD-ROM ATAPI-1 Configuration: DRQ response: 50us. Packet size: 12 bytes Capabilities: LBA, IORDY(cannot be disabled) DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=227ns IORDY flow control=120ns
The CD is master on IDE 1 now, as it should be
hdd: linux:/home/regis # hdparm -iI /dev/hdd /dev/hdd: No such device or address linux:/home/regis #
With no slave device.
Thanks again for your help on this. I may pick up a new drive this afternoon if this looks like a dead end.
Darned if I can see anything wrong with this. I'd get Knoppix, Mandrake Move or some other live-cd and try to burn something with it: AFAIK they all support CD burning. But CDRWs are cheap enough now (and fail often enough too) that having two in the house isn't such a bad idea. Good luck! -- N. B. Day N 30, 1.2033 W 90, 4.0460 18:55:38 up 5 days, 58 min, 2 users, load average: 0.02, 0.07, 0.08 Mandrake Linux release 10.0 (Official) for i586
On Sun, 2005-02-20 at 18:56 -0600, nbday wrote:
On Sun, 2005-02-20 at 08:50, Regis Matejcik wrote:
<Many big whacks>
Darned if I can see anything wrong with this.
I'd get Knoppix, Mandrake Move or some other live-cd and try to burn something with it: AFAIK they all support CD burning. But CDRWs are cheap enough now (and fail often enough too) that having two in the house isn't such a bad idea.
Good luck! -- N. B. Day N 30, 1.2033 W 90, 4.0460 18:55:38 up 5 days, 58 min, 2 users, load average: 0.02, 0.07, 0.08 Mandrake Linux release 10.0 (Official) for i586
N.B., Thanks for all your effort on this. I loaded Knoppix as you suggested and added another cd burner as a slave to the ATAPI master. The slave burner worked perfectly in Knoppix. Just for fun, I rebooted in Knoppix from the slave drive, and tried burning from the ATAPI master. Once again - it worked perfectly. I kept the Master/slave configuration and rebooted into SuSe 9.2. Neither drive will burn a CD from SuSe 9.2 Kind of frustrating that the 700 mb Knoppix CD controls each burner perfectly - with no config options - and my 4+ gig SuSe 9.2 chokes on it. I may either need to do without CD burning, or SuSe. Thanks again, Regis
participants (3)
-
N. B. Day -
nbday
-
Regis Matejcik