Hi all,

got a new problem with Linux, this time it's CD writing.

I've got a LITE-ON LTR-24103S IDE CD-Writer plugged in
and it's working absolutely fine - as long as I dont try
to write CD's with it *G*

I've followed the hints of this tutorial:

http://www.mandrakeuser.org/docs/utils/uiso.html
(The last section "Burning CD-Images" is the one I've tried to mimic)

and after that I've tried it out (logged in as root of course), here's what I've got so far:

*************************************************************************
cd '/home/faeroon/Desktop/too-CDR'
[root@localhost root]# cd '/home/faeroon/Desktop/too-CDR'
[root@localhost too-CDR]# cdrecord -scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jrg Schilling
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.5'
scsibus0:
0,0,0 0) 'LITE-ON ' 'LTR-24103S ' 'XB03' Removable CD-ROM
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
[root@localhost too-CDR]# cdrdao --help
ERROR: Illegal command: --help

Cdrdao version 1.1.5 - (C) Andreas Mueller <andreas@daneb.de>
SCSI interface library - (C) Joerg Schilling
L-EC encoding library - (C) Heiko Eissfeldt
Paranoia DAE library - (C) Monty

Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables.


Usage: cdrdao <command> [options] [toc-file]

command:
show-toc - prints out toc and exits
toc-info - prints out short toc-file summary
toc-size - prints total number of blocks for toc
read-toc - create toc file from audio CD
read-cd - create toc and rip audio data from CD
read-cddb - contact CDDB server and add data as CD-TEXT to toc-file
show-data - prints out audio data and exits
read-test - reads all audio files and exits
disk-info - shows information about inserted medium
msinfo - shows multi session info, output is suited for scripts
unlock - unlock drive after failed writing
blank - blank a CD-RW
scanbus - scan for devices
simulate - shortcut for 'write --simulate'
write - writes CD
copy - copies CD


Try 'cdrdao <command> -h' to get a list of available options

[root@localhost too-CDR]# cdrdao write --device 0,0,0 --buffers 64 --eject test.cue
Cdrdao version 1.1.5 - (C) Andreas Mueller <andreas@daneb.de>
SCSI interface library - (C) Joerg Schilling
L-EC encoding library - (C) Heiko Eissfeldt
Paranoia DAE library - (C) Monty

Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables.

Using libscg version 'schily-0.5'

0,0,0: LITE-ON LTR-24103S Rev: XB03
ERROR: No driver found for 'LITE-ON LTR-24103S', available drivers:
cdd2600
generic-mmc
generic-mmc-raw
plextor
plextor-scan
ricoh-mp6200
sony-cdu920
sony-cdu948
taiyo-yuden
teac-cdr55
toshiba
yamaha-cdr10x
ERROR: Cannot setup device 0,0,0.
**********************************************************************

I've tried to find out if there are driver available for my drive
but I can't find any info about that

On cdrdao's site there's a list of all the supported drives
( http://cdrdao.sourceforge.net/drives.html ) and mine's unfortunately not in it?!?
There are several LITEON drives but not the specific one I use.

I would be very glad if someone could tell me what I should try - maybe there's
other burn software I should use - maybe I've done the command wrong or what ever.
I'm still a Linux n00b, but I hope someone has mercy with me

Hi

What are you trying to do?

Here's my pathetic way of burning backups.

mkisofs -lJR -o filename.iso /path/to/files/to/backup

Then to burn the iso that was created with that:
cdrecord dev=0,0,0 speed=40 -v -eject /path/to/filename.iso

But this really depends on what you are trying to burn.

Cool

Plugged through your post a bit more and saw the cue file which you are using to test with. Although I might get a beat down for this suggestion, if I have a cue and a bin file I've gotta burn, I will use either eroaster (the better option) or xcdroast (the "in a pinch" option).

I'll read through some man pages, and poke around and get back with a better reply

Cool

<update>Try using the '--driver generic-mmc' option. I am still lookin though...</update>

Aaaaah... once again you save my day MasterC!
Just this little ...*grmlbmblmb* *swears and hits his workstation*

You were right , only needed the --driver generic-mmc to get it working but how should I know that :-/

But thx again - its absolutely brilliant how fast you find the answers to all my problems! *bows* You're the BEST!!!

It's all in a nights work for an uber geek

Nah, once you get the hang of things, it's easy to plug through the man pages, or google.com/linux and find answers for these types of things; or better than that, guess and be correct.

You're welcome

Cool