cd-rw confuses mandrake?
ARRG! alright, i've been toying with this thing for days now. having just installed a new motherboard and some additional ram, i tossed redhat and swapped up for mandrake 9.1, and was having great success with it until i tried burning cds. k3b tells me:
No support for ATAPI with cdrdao
You will not be able to use all your reading devices as copy sources since there is at least one not configured to use SCSI emulation and your system does not support ATAPI with cdrdao.
Solution: The best and recommended solution is to enable ide-scsi (SCSI emulation) for all writer devices. This way you won't have any problems.
yet when i "cdrecord -scanbus" i see:
Cdrecord 2.0 (i586-mandrake-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.7'
scsibus0:
0,0,0 0) 'SAMSUNG ' 'COMBO SM-304B ' 'BG05' Removable CD-ROM
0,1,0 1) 'IOMEGA ' 'ZIP 100 ' '23.D' Removable Disk
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
ok, so it's a combo dvd/cd-rw drive [shrug], but cdrecord and k3b setup recognized it immediately as a cd-rw and picked up on its read and write speeds. right, so, what's my issue here? is mandrake not recognizing the drive consistently? if i launch kwikdisk and select /cdwriter witha blank cd-r in the drive, it says:
Called: mount /dev/scsi/host0/bus0/target0/lun0/cd
/dev/scsi/host0/bus0/target0/lun0/cd: Input/output error
mount: I could not determine the filesystem type, and none was specified
now, if i ignore the "use scsi emulation" message (since cdrecord tells me k3b is lying) and try to burn a disc, one of two things happens: 1. k3b tells me to insert a blank cd-r into the drive, even though one's already in. i click "Force"... sometimes this kicks in and the cd begins to burn but fails after one or two tracks with input/output error. 2. after decoding the audio files, k3b hopelessly locks my whole system, while the progress timer in the burning window continues to count, but i can't click cancel or get to system guard to kill the prog, at which point i nearly toss myself out a window. i once let this freeze stand for a solid 5 minutes before doing a manual reboot. so... what the hell is going on here?
for reference: P3 500MHz, 256 MB RAM running kde 3.1 under mdk 9.1 and it's k3b 0.9
[update] so last 2 times around it says input/output error, not necessarily serious a few times, then says drive probably does not like medium, so i try a different brand (memorex instead of generic staples). the 2nd time it fails almost immediately and says buffer underrun probably occurred.
Last edited by RaulConQ; 08-01-2003 at 10:48 AM.
|
