cdrecord errors in K3b

[miwarlock002]

If you experience errors trying to burn cd's or dvd's using k3b then try this:

sudo kate /etc/udev/rules.d/40-permissions.rules

and add this to the bottom line:

KERNEL=="sg[0-9]*",			GROUP="cdrom"

Then reboot and you will be able to burn cd's.

[askrieger]

Re: cdrecord errors in K3b

This tip assumes that your CDRW or DVDRW is, in fact, found at /dev/sg*, if that is not the case, then you'll have to try a more general procedure. I'd suggest reading this HowTo.

[crx-yem]

Re: cdrecord errors in K3b

This tip worked for me

for some unbeknownst reason cdrecord looks at sg0 which is not owned by group cdrom
sudo chgrp cdrom /dev/sg*

[askrieger]

Re: cdrecord errors in K3b

I found the following on a Redhat Forum (Google/linux is my friend):

> Whats the diff between /dev/sg0 And /dev/scd0

scd0 is a block device whilst sg0 is a character device. Generically,
block devices can be mounted and are cached, and char devices are for
communication devices, aren't cached nor block aligned, and can't be
mounted.

Specifically, scd* (block) are for cdroms, providing the block access
and commands for ejecting, closing, playing, etc.

sd* (block) are for normal harddisks, providing partitions and some
few commands.

sg* are for the rest. They accept any scsi command you dare to construct,
and so are used for controlling some esoteric devices or devices that have
no standard interface. Scanners and recorders follow under this one
(recorders, as they also relate to _reading_, have a corresponding scd*
device). They can't be cached and need specific commands by vendor by
action.