SEO

Hi

I have the following CDRW/DVD combo drive :

§» cdrecord -scanbus
Cdrecord-Clone 2.01a34 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg
Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of
cdrecord
and thus may have bugs that are not present in the original version.
Please send bug reports and support requests to
<cdrtools@packages.debian.org>.
The original author should not be bothered with problems of this
version.

Linux sg driver version: 3.5.31
Using libscg version 'schily-0.8'.
scsibus0:
0,0,0 0) 'QSI ' 'CDRW/DVD SBW242U' 'UU30' Removable CD-ROM
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *

From lsmod :

§» lsmod
Module Size Used by
sg 35744 0
sd_mod 21504 0
....
ohci1394 36868 0
pciehp 97804 0
pci_hotplug 35644 1 pciehp
....
sr_mod 18980 0
ide_scsi 18436 0
scsi_mod 84792 4 sg,sd_mod,sr_mod,ide_scsi
ide_cd 43012 0
cdrom 40736 2 sr_mod,ide_cd

From /etc/modules :

ide-detect

#Added 9/15/2004 (Madhusudan Singh)
ide-cd ignore=\"hdc\"
ide-scsi

Entries from /dev :

brw-rw---- 1 root cdrom 11, 0 Mar 23 16:49 /dev/scd0
lrwxrwxrwx 1 root cdrom 4 May 4 08:52 /dev/sr0 -> scd0
lrwxr-xr-x 1 root cdrom 4 Sep 15 14:08 /dev/cdrom -> scd0

From /etc/fstab :

/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,user,ro 0 0

And I do have hdc=ide-scsi in my /boot/grub/menu.lst (appended to the kernel
line).

When I try to list devices in k3b configure>devices, it shows only the
reader at (0,0,0). When I try to add the writer at /dev/scd0, I get the
error :

Could not find an additional device at /dev/scd0

An attempt to burn an iso image fails as the "start" button is deactivated
and no burning device is selectable.

I might mention at this stage that xcdroast works perfectly.

I have worked with k3b in the past (it was a different kernel, a different
time) with this hardware (a moot point since xcdroast works fine).

Any suggestions to get k3b to work would be welcome. I greatly prefer its
UI.

Thanks.

Hello

Madhusudan Singh (<spammers-go-here@spam.invalid>) wrote:

> I have the following CDRW/DVD combo drive :
>
> §» cdrecord -scanbus
> Cdrecord-Clone 2.01a34 (i686-pc-linux-gnu) Copyright (C) 1995-2004

You appear to be using cdrecord from testing or unstable. However I do
not know what kernel you use.

> scsibus0:
> 0,0,0 0) 'QSI ' 'CDRW/DVD SBW242U' 'UU30' Removable
> [...]
>
> And I do have hdc=ide-scsi in my /boot/grub/menu.lst (appended to the
> kernel line).

If you use kernel 2.6, you should stop using ide-scsi emulation
completely, because there is absolutely no need for it. Using the ide
cd driver for writing and reading works just fine for me.

best regards
Andreas Janssen

--
Andreas Janssen <andreas.janssen@bigfoot.com>
PGP-Key-ID: 0xDC801674 ICQ #17079270
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps.html

In alt.os.linux.debian, Andreas Janssen uttered these immortal words:

>> I have the following CDRW/DVD combo drive :
>>
>> §» cdrecord -scanbus
>> Cdrecord-Clone 2.01a34 (i686-pc-linux-gnu) Copyright (C) 1995-2004
>
> You appear to be using cdrecord from testing or unstable. However I do
> not know what kernel you use.

I recently had a problem with kernel 2.6.8 where by my CD writer wasn't
recognised by *any* burning software. Downgrading to 2.6.7 sorted this out.

--
Andy.

Hello

Andy Fraser (<andyfraser31@hotmail.com>) wrote:
> In alt.os.linux.debian, Andreas Janssen uttered these immortal words:
>
>>> I have the following CDRW/DVD combo drive :
>>>
>>> §» cdrecord -scanbus
>>> Cdrecord-Clone 2.01a34 (i686-pc-linux-gnu) Copyright (C) 1995-2004
>>
>> You appear to be using cdrecord from testing or unstable. However I
>> do not know what kernel you use.
>
> I recently had a problem with kernel 2.6.8 where by my CD writer
> wasn't recognised by *any* burning software. Downgrading to 2.6.7
> sorted this out.

Kernel 2.8 had some changes to the permissions for accessing the drives.
I think the developers wanted to disallow users to overwrite the
firmware and the like, but they went a little too far, and with 2.6.8
normal users can't even write CDs anymore. Installing cdrecord suid
root doesn't help, because cdrecord throws away the root privileges as
soon as possible. Running cdrecord as root should however work.

best regards
Andreas Janssen

--
Andreas Janssen <andreas.janssen@bigfoot.com>
PGP-Key-ID: 0xDC801674 ICQ #17079270
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps.html

In alt.os.linux.debian, Andreas Janssen uttered these immortal words:

>> I recently had a problem with kernel 2.6.8 where by my CD writer
>> wasn't recognised by *any* burning software. Downgrading to 2.6.7
>> sorted this out.
>
> Kernel 2.8 had some changes to the permissions for accessing the drives.
> I think the developers wanted to disallow users to overwrite the
> firmware and the like, but they went a little too far, and with 2.6.8
> normal users can't even write CDs anymore. Installing cdrecord suid
> root doesn't help, because cdrecord throws away the root privileges as
> soon as possible. Running cdrecord as root should however work.

You're right. I forgot to mention that K3B and cdrecord worked as root. :-)

--
Andy.

Andreas Janssen wrote:

> Hello
>
> Madhusudan Singh (<spammers-go-here@spam.invalid>) wrote:
>
>> I have the following CDRW/DVD combo drive :
>>
>> §» cdrecord -scanbus
>> Cdrecord-Clone 2.01a34 (i686-pc-linux-gnu) Copyright (C) 1995-2004
>
> You appear to be using cdrecord from testing or unstable. However I do
> not know what kernel you use.

I am using a custom compiled kernel 2.6.8.1.

>> And I do have hdc=ide-scsi in my /boot/grub/menu.lst (appended to the
>> kernel line).
>
> If you use kernel 2.6, you should stop using ide-scsi emulation
> completely, because there is absolutely no need for it. Using the ide
> cd driver for writing and reading works just fine for me.

Is the speed affected ? (There were big warnings when I was using 2.4.26
about this.).

Thanks for your response.

Hello

Madhusudan Singh (<spammers-go-here@spam.invalid>) wrote:
> Andreas Janssen wrote:
>> Madhusudan Singh (<spammers-go-here@spam.invalid>) wrote:
>>
>>> I have the following CDRW/DVD combo drive :
>>>
>>> §» cdrecord -scanbus
>>> Cdrecord-Clone 2.01a34 (i686-pc-linux-gnu) Copyright (C) 1995-2004
>>
>> You appear to be using cdrecord from testing or unstable. However I
>> do not know what kernel you use.
>
> I am using a custom compiled kernel 2.6.8.1.

AHA! Currently, writing only works as root with that kernel. You /can/
make it work by uncommenting one or two lines in the sources and
recompiling the kernel. That will omit the new security checks and act
like 2.6.7 did. In my opinion better that using 2.6.7, because that one
had several security problems that have been fices with 2.6.8. There
was a small patch posted to LKML, but I cannot find it right now. Maybe
you google around a little under the groups search in linux.kernel.

>>> And I do have hdc=ide-scsi in my /boot/grub/menu.lst (appended to
>>> the kernel line).
>>
>> If you use kernel 2.6, you should stop using ide-scsi emulation
>> completely, because there is absolutely no need for it. Using the ide
>> cd driver for writing and reading works just fine for me.
>
> Is the speed affected ? (There were big warnings when I was using
> 2.4.26 about this.).

No. In fact, using ide-cd and the new system is the only way I know to
get DMA working both for reading /and/ writing CDs with blocksizes
other than 2048, e.g. Audio CDs.

best regards
Andreas Janssen

--
Andreas Janssen <andreas.janssen@bigfoot.com>
PGP-Key-ID: 0xDC801674 ICQ #17079270
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps.html

Andreas Janssen wrote:

>>> You appear to be using cdrecord from testing or unstable. However I
>>> do not know what kernel you use.
>>
>> I am using a custom compiled kernel 2.6.8.1.
>
> AHA! Currently, writing only works as root with that kernel. You /can/
> make it work by uncommenting one or two lines in the sources and
> recompiling the kernel. That will omit the new security checks and act
> like 2.6.7 did. In my opinion better that using 2.6.7, because that one
> had several security problems that have been fices with 2.6.8. There
> was a small patch posted to LKML, but I cannot find it right now. Maybe
> you google around a little under the groups search in linux.kernel.
>

That would probably explain all those root related setup questions with
xcdroast and why it works with that tool.

Is fixing this problem (security but no ability for users to burn their own
CDs - ok if you have a small network but imagine how this would affect a
university setup ) on a TODO list for the next kernel release ?

>>>> And I do have hdc=ide-scsi in my /boot/grub/menu.lst (appended to
>>>> the kernel line).
>>>
>>> If you use kernel 2.6, you should stop using ide-scsi emulation
>>> completely, because there is absolutely no need for it. Using the ide
>>> cd driver for writing and reading works just fine for me.
>>
>> Is the speed affected ? (There were big warnings when I was using
>> 2.4.26 about this.).
>
> No. In fact, using ide-cd and the new system is the only way I know to
> get DMA working both for reading /and/ writing CDs with blocksizes
> other than 2048, e.g. Audio CDs.

Well, I just burnt a data CD with scsi emulation and rarely if ever burn
audio CDs so maybe I can live with this for now.

Thanks for your response.

Andreas Janssen wrote:

>>> You appear to be using cdrecord from testing or unstable. However I
>>> do not know what kernel you use.
>>
>> I am using a custom compiled kernel 2.6.8.1.
>
> AHA! Currently, writing only works as root with that kernel. You /can/
> make it work by uncommenting one or two lines in the sources and
> recompiling the kernel. That will omit the new security checks and act
> like 2.6.7 did. In my opinion better that using 2.6.7, because that one
> had several security problems that have been fices with 2.6.8. There
> was a small patch posted to LKML, but I cannot find it right now. Maybe
> you google around a little under the groups search in linux.kernel.
>

That would probably explain all those root related setup questions with
xcdroast and why it works with that tool.

Is fixing this problem (security but no ability for users to burn their own
CDs - ok if you have a small network but imagine how this would affect a
university setup ) on a TODO list for the next kernel release ?

>>>> And I do have hdc=ide-scsi in my /boot/grub/menu.lst (appended to
>>>> the kernel line).
>>>
>>> If you use kernel 2.6, you should stop using ide-scsi emulation
>>> completely, because there is absolutely no need for it. Using the ide
>>> cd driver for writing and reading works just fine for me.
>>
>> Is the speed affected ? (There were big warnings when I was using
>> 2.4.26 about this.).
>
> No. In fact, using ide-cd and the new system is the only way I know to
> get DMA working both for reading /and/ writing CDs with blocksizes
> other than 2048, e.g. Audio CDs.

Well, I just burnt a data CD with scsi emulation and rarely if ever burn
audio CDs so maybe I can live with this for now.

Thanks for your response.

Hello

Madhusudan Singh (<spammers-go-here@spam.invalid>) wrote:
> Andreas Janssen wrote:
>
>> AHA! Currently, writing only works as root with that kernel. You
>> /can/ make it work by uncommenting one or two lines in the sources
>> and recompiling the kernel. That will omit the new security checks
>> and act like 2.6.7 did.
>> [...]
>>
> That would probably explain all those root related setup questions
> with xcdroast and why it works with that tool.
>
> Is fixing this problem (security but no ability for users to burn
> their own CDs - ok if you have a small network but imagine how this
> would affect a university setup ) on a TODO list for the next
> kernel release ?

As far as I know some people are working on it to make a pass-filter
list for commands necessary for writing, but I don't know if it will be
part of 2.6.9. For details, search the LKML.

best regards
Andreas Janssen

--
Andreas Janssen <andreas.janssen@bigfoot.com>
PGP-Key-ID: 0xDC801674 ICQ #17079270
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps.html