Possible that I've fried the cdburning part of my kernel?

Trinity22 · 04-21-2004, 07:01 PM

If it sounds like a stupid question..... my last distro I fried the sound modules clean off the kernel

K3b spat out an error message while I was trying to burn a CD last night. I thought it was program related, but I've just tried to burn a cd from the command line and I'm getting the same errors, so I think its something more...

Quote:

[root@44ba0d45 Locale]# cdrecord dev=0,0,0 -eject speed=2 -pad -audio *.wav
Cdrecord-Clone 2.01a19 (i686-redhat-linux-gnu) Copyright (C) 1995-2003 Jrg Schilling
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.25
Error trying to open /dev/scd0 exclusively ... retrying in 1 second.
Error trying to open /dev/scd0 exclusively ... retrying in 1 second.
Error trying to open /dev/scd0 exclusively ... retrying in 1 second.
Error trying to open /dev/scd0 exclusively ... retrying in 1 second.
Error trying to open /dev/scd0 exclusively ... retrying in 1 second.
Error trying to open /dev/scd0 exclusively ... retrying in 1 second.
Error trying to open /dev/scd0 exclusively ... retrying in 1 second.
Error trying to open /dev/scd0 exclusively ... retrying in 1 second.
Error trying to open /dev/scd0 exclusively ... retrying in 1 second.
Error trying to open /dev/scd0 exclusively ... retrying in 1 second.
bailing out..
[root@44ba0d45 Locale]#

Can anyone please help? I'm running Fedora Core 1 btw.

Trinity

Nauguth · 04-21-2004, 07:51 PM

Do you have the necessary modules (sg, sr_mod, ide_scsi) loaded or compiled into the kernel? Apparently you do since it worked before, but better check them anyway. Also check that the CD-drives cable is still firmly at place.

J.W. · 04-21-2004, 08:22 PM

This is not a kernel issue - it's just telling you it can't reserve the device. Is another process accessing the CD? If so, stop it. Note that if you've got a directory listing open on it, that would count as something that's accessing the device. -- J.W.

Trinity22 · 04-21-2004, 10:53 PM

nothing else is accessing the device. or at least no program that I'm intentionally running. I'm not sure if KDE runs a lot of background processes a la how windows did, and if so, those processes are making use of my burner.

and how would I find out if I had the necessary modules loaded into the kernel? is there a command I can run in terminal to find that out or something else?

Trinity

Trinity22 · 04-22-2004, 03:04 AM

Problem has been solved.... I did a search on justlinux.com (not defaming lq here, but no queries came up with my search) and turns out that K3b spontaneously locked out non-root users. It works as root now, just not $home.

Edited to add that I'm not entirely sure why the same issue propegated in command line also.... maybe it was something involved in cdrecording not k3b specific that went root-only.. who knows.

Trinity

J.W. · 04-22-2004, 03:08 AM

edit - nevermind, it looks like you've solved the problem at the same time I was typing. Congrats -- J.W.