Hi!

I have a question about using a CD-Burner with Kernels 2.4.26 and 2.6.7.

While I configured my system (Slack 10) for the Kernel 2.4 to use the writer, I told lilo to use hdc=ide-scsi and my links from /dev/sr0 (scd0) to /dev/cdrom and /dev/cdrecorder.

This works fine for 2.4.26 but with 2.6.7 k3b dies imideatly after launching, when the splashscreen tells me k3b is looking for the drives ...

I guess that is because 2.6.7 doesn't need this kind of scsi emulation anymore, right?

But, what to do against it? If I simply change the links again, it won't work with 2.4.26 ...

Or is it not possible to use both ?

Thanks very much!

MfG, Sascha Lasner

You're right, kernel 2.6.7 doesn't need the scsi emulation for CD burners. One thing I can suggest is to add something to the 2.4.26 startup script to create the link and then in the shutdown script delete the link

What does the Kernel 2.6.7 want?

Do I need to make links to /dev/hdc ?

Thanks, Sascha

The 2.6.x kernel doesn't require any special links as far as I know. CD burning should would right away.

also fyi I found that K3B and Kernel 2.6.8 = coasters Don't know if it's been fixed yet. Just a heads up. Took me 3 cds to figure out

Yes, you need updated k3b. the newer kernels have protection built in to stop software damaging the drives and some older software does not access the drive correctly and so will not work with newer kernels. 2.6.9 also will not work with older k3b...

Thanks guys!

My problem is now, that when booted Kernel 2.6.7 and starting k3b (downloaded this week) it dies on the splashscreen when searching for devices ... kann even kill it.

When shutting down or rebooting to kernel 2.4.26 k3b comes up (the one process started under 2.6.7) and greets me friendly.

How can that be? with 2.6.7 it doesn't find the device...

Greetings, Sascha

I thought 2.6.7 should have been okay. It's been a while since I used it tho and now run 2.6.9-rc3... What sort of errors and such do you get running k3b from a terminal window?

I do know they have been having some trouble getting k3b right on the newer kernels and I'm still using an older copy that I hacked myself to work with 2.6.8.1...

I will look for the errors in a few hours, because I go swimming now...

but until there: Do you use emovix? Thats another problem with k3b, it won't find emovix even if I enter the directory to k3b's programm searchpath ... do you know something about that?

So long... Sascha

Hi there!

So, I ran k3b fro mthe console. Splashscreen came up and froze on searching for devices (like always) ... and turned white ... but nothing else happens.

No errors in the terminal... or logs ... when I boot the kernel 2.4.26 the started (under 2.6.7) k3b seems to find the device finally and starts up normally ... (like said before) but: no errors ... :-(

Don't know a thing...

Greetings, Sascha

It is an odd one as I ran k3b fine with 2.6.7 and 2.6.8.1 and now with several 2.6.9 variants...

what version of k3b is it exactly. I might try downloading it and try it here...

The version is 0.11.17 ... installed the Slackware 10.0 package if I remeber right...

Hope this might help you ...

for the kernel 2.6, you should use the ide-cd kernel module

In my lilo.conf, I put the option "append hdb=ide-cd" (hdb is my dvd burner)

if the module is not loaded at boot, try to add "ide-cd" in /etc/modules

I recently compiled a kernel 2.6.7 on a mandrake 10 official and it work with k3b.

best regards

Thanks, I'll give that a try!

Did you have similar problems before that?

Greetings, Sascha

@ ttottoro:

I tried what you said. I appended "append hdc=ide-cd" for hdc is my DVD-burner. But the only effect is, that it hangs up while booting, telling me my hdc "seems to be confused" ... had something similar before... but with SuSE 9.1 ...and I wasn't able to avoid this error for a month or so and this was how I came to slackware ... but that's another story :-)

We'll it seems to be a bit more complicated than I thought it might be...

Meanwhile I got rid of the slackpackage k3b and compiled my own ... but nothing changed ....

Hope someone has another nice idea?

Greetings, Sascha