2.6.x/cd burning ridiculousness

Can you burn successfully as root in either of those 2 kernels? I ran into the same problem recently where I could only burn as root in 2.6.8.1, but there was still a memory leak (or so I read, but wasn't affected).

I eventually got fed up and downgraded to 2.6.7 and it worked fine. I'm going to wait for the situation to stabilize before I upgrade again. :-/

nope. tried burning as root and got the same crap...it just hung and couldn't be killed (the status that showed up in ps ax was DL+)...i tried killing the process and kill -9 and kill -15, to no avail. maybe it's because i su'd to root instead of "actually" logging in as root and doing it? probably not...

su'ing to root should bee fine. It's SuExec that doesn't work anymore.

I was having problems, but 2.6.7 works for me. About all the advice I can give (insert acknowledgement of 2.6.7 working because it has broken/flawed ide-scsi).

ide-scsi is and always has been a dirty, dirty hack, and its death is appreciated by many, myself included.

Jörg's an asshole and Linus is stubborn, but stubbornly right, imho.

I use Debian and Linux 2.6.x (where x is 0 to 9) and have had no problems. The Debian version of cdrecord adds patchs to support writing to IDE devices. When you start it up it says:

bradfitz@bini:~$ cdrecord dev=/dev/hdc win2kpro.iso
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01a38 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to <cdrtools@packages.debian.org>.
The original author should not be bothered with problems of this version.

cdrecord: Warning: Running on Linux-2.6.9-rc2
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
cdrecord: Warning: Linux-2.6.8 introduced incompatible interface changes.

it could be my drive. i've had the same program i mentioned (hanging, unkillable) when running cdrecord dev=/dev/hdc and cdrecord dev=ATA:1,0,0

...

of course i've only tried 2.6.8 with debian patches and 2.6.9 without the patches. maybe i will give 2.6.7 a spin.

ide-scsi or how to burn in linux

> ide-scsi is and always has been a dirty, dirty hack,

Yes and no.

> and its death is appreciated by many, myself included.

ide-scsi is and has been a hack *in linux*.
We are talking about ATAPI/SCSI-3/MMC commands here which are send
to the CD-writer. You could say ATAPI is more or less SCSI-over-IDE.
So the approach of writing/using a 'ide-scsi' driver is actually a
very reasonable one, since you are actually sending (encapsulated) SCSI
commands to your (IDE) CD burner. At least if you do it right.

When the first CD-ROM drives were introduced, they were expensive and
they were SCSI. Then the price dropped and the first IDE models became
available. In the need to extend the IDE command set to support
removable drives (CD-ROM, tape, SuperFloppy etc.), they decided to
reuse the already established way of communicating to those devices:
SCSI.
They only adapted it so that those devices could be attached to a IDE
bus and the commands could be send via the ATA interface.
ATAPI was born.

Right now, as of Feb. 2005, the ide-scsi driver in the vanilla kernel
is still superior to the new ide-cd driver; the latter lacks proper
support for error reporting, monitoring (eg. end-of-medium).
But they are working on getting the missing bits implemented in ide-cd
(most bits are tested in the -ac kernels first).


So why would anybody want to get rid of ide-scsi in the first place?

First of all, it was badly implemented and it lacked a real
maintainer for a long time.
Secondly, ATAPI devices are not real SCSI devices, they just use a
subset of SCSI commands. The ide-scsi driver adds a lot of 'emulation'
to make the device appear like a full SCSI device. This is not really needed, and makes maintainance a real pain.
At the end ide-cd should become a leaner, cleaner way of supporting
ATAPI devices ...

There is a lot of confusion which way to use to burn a CD.
Why would anyone recommend ide-cd when it is not yet as good as ide-scsi?
Well, in the early 2.6 kernels, ide-scsi was broken (bit-rot)
and nobody bothered to fix it, since they were mostly working on
getting ide-cd out of the door. So at that time people were told
that the 'new way' of burning CDs is using ide-cd.
They just happened to forget to mention that it was/is not really finished yet :-/
In the mean time, ide-scsi has been fixed again, but its use is not
being recommended, as the kernel developers want to get rid of
ide-scsi sooner or later.

The kernel developers say the future is using the ide-cd
driver and use cdrecord with "dev=ATA:x:y:z" or similar (don't use dev=/dev/hda or dev=ATAPI:x:y:z, which is sub-optimal).
And for most people ide-cd works fine already, but it is still in
development and now and then they break it (at least in the -pre patches).

So that's the story. Or at least a glimpse of it.
That is why cdrecord is complaining about using a "unstable, experimental kernel interface" if you are using ide-cd, and
recommends to use ide-scsi emulation instead.
But that is also why in the kernel help it says that "ide-scsi is no
longer needed to burn CDs and there is no need to compile it in".

So right now, use ide-scsi. In future, use ide-cd.

Max G.

Re: ide-scsi or how to burn in linux

The kernel developers say the future is using the ide-cd
driver and use cdrecord with "dev=ATA:x:y:z" or similar (don't use dev=/dev/hda or dev=ATAPI:x:y:z, which is sub-optimal).
And for most people ide-cd works fine already, but it is still in
development and now and then they break it (at least in the -pre patches).

Actually, it seems to be "dev=ATA:x,y,z", where x is channel, y is 0 for master and 1 for slave, and z seems to be always zero, so for /dev/hdb you would put "dev=ATA:0,1,0", for /dev/hdc "dev=ATA:1,0,0", and /dev/hdd "dev=ATA:1,1,0".

Re: ide-scsi or how to burn in linux

Actually, it seems to be "dev=ATA:x,y,z", where x is channel, y is 0 for master and 1 for slave, and z seems to be always zero, so for /dev/hdb you would put "dev=ATA:0,1,0", for /dev/hdc "dev=ATA:1,0,0", and /dev/hdd "dev=ATA:1,1,0".

Now I find that even that doesn't seem to work... one thing that does work is "dev=ATAPI:0,0,0", though I get the distinct feeling that I've forgotten something...

--SamB

Re: ide-scsi or how to burn in linux

I'm having the same burning problem (only 4x on a 48x burner) and I'd like to try using dev=ATA:1,1,0 instead of dev=/dev/hdd, but I can't seem to find where or how to set this in k3b, and I'm not sure what command to use from the command line to copy from hdc to hdd.

Any suggestions on configuring this into k3b?

tend to agree, since 2.6.8 k3b craps out on me

> couldn't kill it without rebooting.

Could you try killing it with MagicKey (SysRq)?...

cdrecord

With kernel 2.6.10-rc1 cdrecord works like a charm,besides that you get some xtra
security features as well.

have fun.

Re: cdrecord

In response to the last anonymous user,

I was working fine on 2.6.7 but I went to 2.6.10-gentoo-r1 and I hit the error reported in the thread above!! Is there a resolution to the problem? I heard someone say that 2.6.10-r3 had it fixed but I'm not holding my breath.

What's going on with the cdrecord / linux kernel atapi drivers development?

PS. Which is best linux atapi driver (with bus master) or the ide-scsi emulator. I heard the ide-scsi emulator turns of DMA on disks if you compilie it into your kernel.. Does it use DMA when it's a module?

Any updates. Cheers

Luke
tallmc@hotmail.com

Re: cdrecord

Hi Guys,

Gentoo fixed this!

Yes, if I go to 2.6.10-gentoo-r3 it should be resolved, and change how security is handled by cdrecord.

http://forums.gentoo.org/viewtopic.php?t=247459&postdays=0&postorder=asc&highlight=cdrecord&start=100

Once upon a time I had debian. Who wants a "LugNut Debian 1.0 CD :P"

Luke

Re: cdrecord

I just acquired a DVD dobule layer burner and compiled/installed 2.6.9 by hand in Debian. (I don't like the mkpkg scripts, too many extra steps.) If I run cdrecord -scanbus, it hangs. Same thing if I run xcdroast without arguments. So I think I have the same problems as the OP. However, this worked,

xcdroast -f /dev/hdc

From what previous posters say, this means I'm using ide-cd. Indeed, it's loaded as a module. It follows that cdrecord -scanbus hangs because it assumes ide-scsi but I'm using ide-cd.

Since I found this on google, I bet other people will find this useful. :-)

My cd and dvd burns Ok at last in debian 2.6.10 using ATAPI (ide-cd)

This post is long, so maybe it is better to read the full version at my page 'Manual: Linux (debian) installation on Athlon (AMD K7) processors family (Athlon + NVidia + Ati-RadeOn9550; kernel2.6.10'
http://www.larkin.chuhloma.ru/athlon_history/athlonXP3100.html
(see the end of the page).

How to burn CD and DVD disks?

One of my problems was that I'm using ATA harddrive via LibAta - e.g. my harddrive is /dev/sda, but not /dev/hda. Also,

cdrecord -dev="ATA:" -scanbus

didn't work for me. So I could not use ATAPI solution (ide-cd modern one) as is - it doesn't work. Also I could not use old linux-hacking way

cdrecord -dev="0,0,0" -scanbus

(ide-scsi one), because ide-scsi is completely broken in 2.6.x kernerls (see explanation: very good discussion about 'why there are so many problems with CD/DVD burning starting from kernel 2.6.x' at http://www.livejournal.com/community/debian/186598.html
"Find a comment of 'Max G.' at this page")

I made my CD/DVD-RW drive working as ATAPI by disabling IDE-SCSI. First I made few changes to kernel:

-- e.g. set ide-cd as kernel-internal, set ide-scsi as module, turn off scsi emulation CD-specific things (sr, sg).

As I found, these changes doesn't help. Ide-cd doesn't work correctly still, probably because it conflicts with /dev/sda harddrive SCSI. I solved it by adding line

append="hda=ide-cd"

to /etc/lilo.conf (add this line after 'read-only' line in 'image=/vmlinuz' section). After this

sudo cdrecord -dev=ATA -scanbus

worked OK for me (so it output '0,0,0 0) '_NEC ' 'DVD_RW ND-2510A ' '2.04' Removable CD-ROM' as result).

Now 'cdrecord_2.01+01a01-0.backports.org.1_i386.deb' should work ok for you (this is cdrecord 2.0+01a01 version that works ok for CD disks, but not DVD). I used xcdroast-0.98alpha15 as GUI for cdrecord. Some help on how to set it up:

cp xcdroast-0.98alpha15.tar.gz ~/xcdroast/

# Install required packages
[...skiped]
cd ~/xcdroast/

./configure

make

sudo make install

...

Compilation of cdrecord that supports DVD
# Download cdrtools-2.01.01a01-dvd.patch.bz2 from http://people.mandrakesoft.com/~warly/files/cdrtools/archives/
# Download cdrtools-2.01.01a03.tar.bz2 from ftp://ftp.berlios.de/pub/cdrecord/alpha/
(this one should be like a38 or never)

# Here some commands to do:

--- This installs cdrecord_2.0+01a01 for debian ( take it at www.backports.org/debian/dists/stable/cdrtools/binary-i386/ ) -
sudo dpkg --install cdrecord_2.01+01a01-0.backports.org.1_i386.deb
--- this cdrecord works good for burning CD disks via ATAPI ( using xcdroast for GUI in my case )

...

patch <cdrtools-2.01.01a01-dvd.patch --- answer questions by sec file name starting from entering 'cdrtools-2.01/libscg/scsitransp.c[ENTER]' and so on cd cdrtools-2.01.01 --- I recomend to update version of cdrecord from 'Cdrecord-Clone 2.01-dvd' to 'Cdrecord-ProDVD-Clone 2.01a38' --- ( this would make up mind of xcdroast that understands only old versions format ) sudo vi ./cdrecord/cdrecord.c --- Make sure that the version is like ...char cdr_version[] = "2.01";... --- Find ...printf("Cdrecord%s%s %s-dvd (%s-... line and change it to printf("Cdrecord%s%s %sa38 (%s-%s-%s) Copyright (C) 1995-2004 J\xf6rg Schilling\n", -- Also change line ...# define PRODVD_TITLE ""... to # define PRODVD_TITLE "-ProDVD" --- Now make everything make sudo make install find ./ -name "cdrecord" sudo cp ./cdrecord/OBJ/i686-linux-cc/cdrecord /usr/bin/cdrecord.prodvd Also it looks like unfortunatly 'cdrecord-prodvd-2.01b31-i686-pc-linux-gnu' and other cdrecord-prodvd doesn't support ATAPI way ( e.g. ide-cd ). Also 'blanking DVD disk' may not work. Anyway, writing the disk works ok. It looks like patch-compiled cdrecord works for CDs and DVDs both, but I recomend using 'sudo xcdroast -w' for CDs and 'sudo xcdroast' for DVDs. At last I got this text (successfully written DVD-disk) - yee! ... see http://www.larkin.chuhloma.ru/athlon_history/athlonXP3100.html alarkin@iname.ru