I just compiled kernel version 2.6.11.5, and that is what I have been using since this weekend. I tried to burn a CD today using k3b, and it gave me an IO error and nothing in the debugging report of any substance. Does anyone know if there are any issues with this kernel and cd writing? I know there were with 2.6.8 (maybe?). Has anyone else seen anything similar?

What were you using before 2.6.11.5? With 2.6 kernels you don't have to use scsi-ide emulation.

I was using 2.6.10 before. I looked for the scsi-ide emulation, and couldn't find it in the menuconfig tree. Do you know the exact name of the kernel package?

I think you do. I couldnt get my external usb2 dvd burner to work without getting scsi emulation running again. I still can't burn CDs on it,

And my internal burner burns DVDs only at speeds below 4x, CDs only at speeds below 4x otherwise it says 'fixating', and then fails.

So without scsi emu, the external one refuses to be even recognised by linux, and internal one refuses to burn anything.

With scsi emu, its slightly better...

f you are using ATAPI devices then you don't need scsi emulation. If you are using USB drives, then you probably do because some emulate scsi devices.

Space balls,

Just a thought, but you did compile into the kernel during menuconfig:
device drivers -> block devices -> packet writing for CD/DVD media ?

I think that is needed, but not sure if its selected by default.

And you can look here if you want:
device drivers -> ata/atapi/mfm/rll supports -> SCSI enulation support
Good read on the <help> for this.

just passing thoughts - good luck
-tw

I checked my kernel config and it seems to be in order. Are could there just be some sort of incompatibility between 2.6.11.5 and cdrtools or one of those packages?

I booted up kernel 2.6.10, and I still got the sam I/O error with nothing significant in the error log. Packet writing was included in the kernel configuration.

K3B is what I normally use to burn CD's (and all that I have tried in this case). Is this a K3B issue or is it a kernel options issue?

In the past I have found that K3B usually wasn't at fault, and it was something else, though not necessarily a kernel option.

Can anyone tell me what an I/O error really means?

One more thing- SCSI-IDE emulation wouldn't hurt anything, would it?

Hi,

Do you log in as root when using K3B? Somewhere around kernel 2.6.8 or so security in the kernel changed and cdrecord (which K3B is front-end to) runs only with root privileges.

Just worth a try, new release of cdrecord should fix it.


Rgds
Sam