You are not logged in.

#1 2006-01-29 02:24:43

dekernel
Member
From: Vassar, MI USA
Registered: 2004-03-22
Posts: 117

K3b Burning Issue

Not sure at what point, I stopped being able to burn CD's. I have seen issues with K3b on the mailing list it had to do with DVD's.

I have within the last few months, successfully burned CD's so I am confy with thinking that my hardware is good. I have a Yamaha SCSI writer. I can mount the device (dev/scd0) and read a CD. The problem I get in K3b is that it won't accept it as a valid device. When I start the app up from the shell, I get the messag:

k3b: (K3bDevice::DeviceManager) scanning fstab: /dev/scd0
k3b: (K3bDevice::Device) Error: could not open device /dev/scd0for reading
k3b: could not open device /dev/scd0 (No such device or address)
k3b: /dev/scd0 resolved to /dev/scd0
k3b: (K3bDevice::Device) Error: could not open device /dev/scd0for reading
k3b: could not open device /dev/scd0 (No such device or address)

Any suggestions?

Offline

#2 2006-01-29 02:45:27

afu
Member
From: Tuscalooser, Alabummer
Registered: 2004-02-19
Posts: 155

Re: K3b Burning Issue

Can you do it as root? Can you mount and read a data CD? Make sure you have the proper permissions in the /etc/groups file. Can you use different burner software like Xcdroast? As a last resort, look at the cd burning howto or try running the comands manually from a terminal. You may get more info this way.

Oh - and make sure the hal and dbus damons are running. I got burnt by this not long ago (excuse the pun).
-Shawn

Offline

#3 2006-01-29 04:03:14

iphitus
Forum Fellow
From: Melbourne, Australia
Registered: 2004-10-09
Posts: 4,927

Re: K3b Burning Issue

make sure the kernel module 'sg' is loaded too.

Offline

#4 2006-01-29 15:57:35

dekernel
Member
From: Vassar, MI USA
Registered: 2004-03-22
Posts: 117

Re: K3b Burning Issue

Yes, I do have DBUS and HAL running, NO I didn't have sg loaded. I loaded the module with still the same results. I even tried as root with no success.

I am thinking that permissions are OK because I was able to mount and read a CD. Also here are the permissions:

brw-rw----  1 root optical 11, 0 2006-01-29 05:38 /dev/scd0

I appear to be loading the correct SCSI driver because there is what I am seeing in /proc/scsi.
[tim@dellmachine ~]$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: YAMAHA   Model: CRW4416S         Rev: 1.0f
  Type:   CD-ROM                           ANSI SCSI revision: 02


What I am really concerned is that I think my hardware is going on me. The mount to read a CD did take a considerable amount of time, upwards of 20 seconds, and I am seeing this in dmesg:
(scsi0:A:1:0): No or incomplete CDB sent to device.
scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
sr 0:0:1:0: SCSI error: return code = 0x10000

Any suggestions?

Offline

#5 2006-01-29 16:13:48

dekernel
Member
From: Vassar, MI USA
Registered: 2004-03-22
Posts: 117

Re: K3b Burning Issue

I need to retract my statement about questioning the hardware. I forgot that I had a copy of Windows XP on this machine. I rebooted into Windows and was able to burn some files to CD.

Offline

#6 2006-01-29 16:24:04

shadowhand
Member
From: MN, USA
Registered: 2004-02-19
Posts: 1,142
Website

Re: K3b Burning Issue

What kind of drives do you have? Are they actually SCSI, or are you using ide-scsi?


·¬»· i am shadowhand, powered by webfaction

Offline

#7 2006-01-29 19:35:19

dekernel
Member
From: Vassar, MI USA
Registered: 2004-03-22
Posts: 117

Re: K3b Burning Issue

The devices are SCSI. I was able to get Xcdroast to not only see the device but write an ISO image so I am pretty sure the problem is with K3b.

I now for sure that I haven't written to a CD since the mkinitrd conversion. I am wondering if I am missing a kernel module since I was already missing the sg module.

Offline

#8 2006-01-29 19:54:02

dekernel
Member
From: Vassar, MI USA
Registered: 2004-03-22
Posts: 117

Re: K3b Burning Issue

Two bits of additional info. I switched back to using the full initrd image and autodecting the hardware via rc.conf. Still nothing.

The second bit is strange, when I start K3b for the shell, the process seems to hang forever when attempting to ID my /dev/scd0 device which is my writer. While id'ing the LED's on the from on the device go out!!!!

I hope this can help the powers that be because obviously I am clueless and out of idea's.

Offline

Board footer

Powered by FluxBB