Hi Anders.

If you want to use k3b, then you have to enable scsi emulation for the writer. Edit /boot/grub/menu.lst, and on the vmlinuz line for SuSE, add"hdd=ide-scsi" and reboot. Then k3b will see your writer as/dev/sr<something> and /dev/sg<something>, where <something> is some number, depending on whether you have other scsi things on the system. If you don't it'll be sr0 and /dev/sg0

I have this: linux:~ # modprobe ide-scsi linux:~ # ls -al /dev/hdd /dev/hdc /dev/hdd /dev/cdrom /dev/cdrecorder /dev/dvd lrwxrwxrwx 1 root root 3 Jun 26 10:17 /dev/cdrecorder -> sr0 lrwxrwxrwx 1 root root 3 Jun 26 10:17 /dev/cdrom -> hdc lrwxrwxrwx 1 root root 3 Jun 26 10:17 /dev/dvd -> hdc brw------- 1 erik disk 22, 0 Mar 14 14:07 /dev/hdc brw-rw---- 1 root disk 22, 64 Mar 14 14:07 /dev/hdd brw-rw---- 1 root disk 22, 64 Mar 14 14:07 /dev/hdd I have tried /dev/sr0, but it wount work. I am not quite sure where to put in the /dev/sg0 ??. -- Med venlig hilsen - Best regards. Erik Jakobsen - eja@urbakken.dk. Licensed radioamateur with the callsign OZ4KK. SuSE Linux 8.2 Proff. Registered as user #319488 with the Linux Counter, http://counter.li.org.

You already have "hdd=ide-scsi" in menu.lst?

I have, Yes :-)

Then what does

cdrecord -scanbuslinux:~ # cdrecord -scanbus Cdrecord 2.0 (i686-suse-linux) Copyright (C) 1995-2002 Jörg Schilling Linux sg driver version: 3.1.24 Using libscg version 'schily-0.7' cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.75-resmgr-patch '@(#)scsi-linux-sg.c 1.75 02/10/21 Copyright 1997 J. Schilling'). scsibus0: 0,0,0 0) 'HL-DT-ST' 'CD-RW GCE-8160B ' '2.01' 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) *

...

I have tried /dev/sr0, but it wount work. I am not quite sure where to put in the /dev/sg0 ??.

You don't have to put sg0 anywhere, just make sure you have sufficient permissions on it

ls -l /dev/sr0 /dev/sg0

You need both read and write permissions

linux:~ # ls -l /dev/sr0 /dev/sg0 crw-r----- 1 root disk 21, 0 Mar 14 14:07 /dev/sg0 brw-r----- 1 root disk 11, 0 Mar 14 14:07 /dev/sr0 /Erik.

* Anders Johansson (andjoh@rydsbo.net) [030725 12:29]:

On Fri, 2003-07-25 at 21:23, Erik Jakobsen wrote:

...

linux:~ # ls -l /dev/sr0 /dev/sg0 crw-r----- 1 root disk 21, 0 Mar 14 14:07 /dev/sg0 brw-r----- 1 root disk 11, 0 Mar 14 14:07 /dev/sr0

And when you run k3bsetup as root, it still doesn't see it?

You have cdrdao installed, right?

Apart from the fact that my devices are owned by my regular user (automatically chowned at login in a default SuSE setup), your installation looks ok, and since cdrecord -scanbus sees the recorder, it should work.

Do you have the this line in /etc/pam.d/login? session required pam_resmgr.so Because of SuSE's resmgr program this is needed if a regular user is to burn CD's now. If you don't have that line in /etc/pam.d/login then I would put it in and logout then log back in. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.

And when you run k3bsetup as root, it still doesn't see it?

Negative. Then it does see it.

You have cdrdao installed, right?

Yep.

Apart from the fact that my devices are owned by my regular user(automatically chowned at login in a default SuSE setup), your installation looks ok, and since cdrecord -scanbus sees the recorder, it should work.

Do you mean, that you use it as default by the SuSE install ?. To that I can say, that I haven't touched anything here - with reference to the subject - since the install of SuSE 8.2. The culprit is that my regular user hasn't previlegies set to use K3B. Am I right in that ?. linux:~ # ls -l /dev/sr0 /dev/sg0 crw-r----- 1 root disk 21, 0 Mar 14 14:07 /dev/sg0 brw-r----- 1 root disk 11, 0 Mar 14 14:07 /dev/sr0 /Erik.

Looks that way, yes. I think you should get a later version of k3b. The latest has support for SuSE's resmgr setup. I don't think the one included on the CDs can handle it, since it tries to simply chown the device and add the user to the cdrecorder group, but that doesn't work with resmgr

Ok Anders. I changed the runlevel from 3 to 5, and then it works ok. But I like to use the runlevel 3 !!. /Erik.

Erik Jakobsen wrote, On 07/26/2003 05:02 PM:

As I wrote yesterday, I could get user to use the K3B changing the runlevel from 3 to 5.

How can I do the trick to again set runlevel to 3, and still have the K3B possibility being the user ?.

Add "session required pam_resmgr.so" to /etc/pam.d/login (what is inside the quotes). -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.

Erik Jakobsen wrote, On 07/26/2003 05:02 PM:

...

As I wrote yesterday, I could get user to use the K3B changing the runlevel from 3 to 5.

How can I do the trick to again set runlevel to 3, and still have the K3B possibility being the user ?

I also log in through the console, i.e. runlevel 3. Runlevel 3 is without X, so if I go to X with startx (which is needed to run k3b), the runlevel changes to 5, right? So I'm not quite sure what you mean. Anyway, k3b also behaved somewhat strange here when run as user. For example, although k3bsetup correctly recognized the writer as a 16x device, k3b could only write at speed 4x. Everything went much better when I upgraded to the k3b 0.9 rpm, found at http://packman.links2linux.org SH

Erik Jakobsen wrote:

...

needed to run k3b), the runlevel changes to 5, right? So I'm not quite sure what you mean.

My runlevel is not changing to 5. Thats why the problem occure.

?? If you su to root and issue the command runlevel in an X-terminal, what does it say?

...

Anyway, k3b also behaved somewhat strange here when run as user. For example, although k3bsetup correctly recognized the writer as a 16x device, k3b could only write at speed 4x.

Ok. I did try it here for the first time today, and it was running 10 as the media was just for X12, it automatically lowered the speed set to 16 down to 10.

Oh, wait... my cd-rw discs (a few years old) are for x4. k3b recognizes this and adapts its speed to this? Amazing. Still, I find the new 0.9 to be an improvement. SH

I'm having a problem with K3b when it goes to write the disk , it will write the disk up to about 62% then it gives the message buffer under run and quits .. is there a fix for this , i've tried different disks and different settings but can't get it to work , runing 8.2 pro and kde . Thanks for any help Dave

On Sunday 27 July 2003 06:12 am, Pastor-kc1di wrote:

I'm having a problem with K3b when it goes to write the disk , it will write the disk up to about 62% then it gives the message buffer under run and quits .. is there a fix for this , i've tried different disks and different settings but can't get it to work , runing 8.2 pro and kde .

Thanks for any help Dave =============

Dave, Buffer underruns are caused when the data that fills the buffer can't keep up with the drive writing. If you are trying to copy from one cd to another, it can happen because IDE is not suited for such things. If you have a particularly fast cdrw, it could happen as the buffer gets used up too quickly. If you have many other processes running and you working with several other things, it could happen, because the the hard drive can't keep up with all the requests and filling the buffer. If it's a relatively new drive, it should have a buffer underrun protection. Turn it on in K3b to help keep down these problems. If you are burning a cd, try letting it do it's work then continue on with your other projects. If it's an older drive 16x or less top speed, it probably won't have the protection of buffer underrun built in, so wait for it to finish burning. Pat -- --- KMail v1.5.2 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...