K3b and kernel 2.6.8 NOT SUSE specific
Hi, The 'owner' of K3b, Sabastian T. has this posted on the www.k3b.org page: "Do not use Kernel 2.6.8 A patch that was introduced into the kernel shortly before the 2.6.8 release makes K3b and also the dvd+rw-tools unusable on Linux (unless run as root but that is not recommended). The very important GET CONFIGURATION MMC command is rejected by the kernel for reasons I cannot see and writing commands like MODE SELECT also fail (K3b cannot detect CD writers without it) even when the device is opened O_RDWR. Until this issue has been solved I strongly recommend to stick to kernel version 2.6.7. Update: The kernel guys are currently fixing the problem so the next kernel release should work again. :) Update 2: The problem is NOT fixed in 2.6.8.1 Update 3: Be aware that kernel 2.6.8 also contains the memory leak which makes it impossible to write audio cds, even as root." Now this is Not Distro specific, so we don't know if the SUSE 2.6.8 in 9.2 has any in-house tweaks for this prob, but he certainly describes the "Need to run as root" prob. Also he stated that newer kernels will also have issues. Perhaps this is the reason Shilling at SUSE has modified 'cdrecord'? My advice == Follow the work-arounds as you have discussed here on the list and await more news. PeterB
On Sun, Nov 28, 2004 at 02:28:24PM -0600, Peter B Van Campen wrote:
Hi,
The 'owner' of K3b, Sabastian T. has this posted on the www.k3b.org page:
When was that posted?
"Do not use Kernel 2.6.8
A patch that was introduced into the kernel shortly before the 2.6.8 release makes K3b and also the dvd+rw-tools unusable on Linux (unless run as root but that is not recommended). The very important GET CONFIGURATION MMC command is rejected by the kernel for reasons I cannot see and writing commands like MODE SELECT also fail (K3b cannot detect CD writers without it) even when the device is opened O_RDWR. Until this issue has been solved I strongly recommend to stick to kernel version 2.6.7.
Update: The kernel guys are currently fixing the problem so the next kernel release should work again. :)
Update 2: The problem is NOT fixed in 2.6.8.1 Update 3: Be aware that kernel 2.6.8 also contains the memory leak which makes it impossible to write audio cds, even as root."
Now this is Not Distro specific, so we don't know if the SUSE 2.6.8 in 9.2 has any in-house tweaks for this prob, but he certainly describes the "Need to run as root" prob.
From kernel-default-2.6.8-24.3 changelog:
* Tue Aug 17 2004 - garloff@suse.de - bio-uncopy-free-on-write: fix mem leak triggered by writing audio CDs. (#43821) Please check your facts before posting. Regards, -Kastus
On Sunday 28 November 2004 2:45 pm, Kastus wrote:
On Sun, Nov 28, 2004 at 02:28:24PM -0600, Peter B Van Campen wrote:
Hi,
The 'owner' of K3b, Sabastian T. has this posted on the www.k3b.org page:
When was that posted?
"Do not use Kernel 2.6.8
A patch that was introduced into the kernel shortly before the 2.6.8 release makes K3b and also the dvd+rw-tools unusable on Linux (unless run as root but that is not recommended). The very important GET CONFIGURATION MMC command is rejected by the kernel for reasons I cannot see and writing commands like MODE SELECT also fail (K3b cannot detect CD writers without it) even when the device is opened O_RDWR. Until this issue has been solved I strongly recommend to stick to kernel version 2.6.7.
Update: The kernel guys are currently fixing the problem so the next kernel release should work again. :)
Update 2: The problem is NOT fixed in 2.6.8.1 Update 3: Be aware that kernel 2.6.8 also contains the memory leak which makes it impossible to write audio cds, even as root."
Now this is Not Distro specific, so we don't know if the SUSE 2.6.8 in 9.2 has any in-house tweaks for this prob, but he certainly describes the "Need to run as root" prob.
From kernel-default-2.6.8-24.3 changelog:
* Tue Aug 17 2004 - garloff@suse.de
- bio-uncopy-free-on-write: fix mem leak triggered by writing audio CDs. (#43821)
Please check your facts before posting. Sabastian posted this entry w/o a date, and he added 3 updates afterward. What was unfactual about my post?
PeterB
On Sun, Nov 28, 2004 at 03:05:12PM -0600, Peter B Van Campen wrote:
Sabastian posted this entry w/o a date, and he added 3 updates afterward. What was unfactual about my post?
That the problems he mentioned have been fixed in SUSE kernels. Regards, -Kastus
On Sunday 28 November 2004 3:14 pm, Kastus wrote:
On Sun, Nov 28, 2004 at 03:05:12PM -0600, Peter B Van Campen wrote:
Sabastian posted this entry w/o a date, and he added 3 updates afterward. What was unfactual about my post?
That the problems he mentioned have been fixed in SUSE kernels.
Regards, -Kastus Hi Kastus,
I've been experiancing the 'run as root' prob on 9.2 up to date via YOU inc new kernel. Fred has also. A very vexing situation to say the least. Ken Schneider posted this as his solution, and it works like a dream for me: "One thing I have done for a long time is create an icon on the desktop for k3b (hint - go to the menu entry, right click and hold and drag to the desktop), go into the properties and change the the "run as" to root. Now when I launch k3b it will ask for the root password and I never have a problem burning CD's/DVD's." Before I did that K3b refused to see my recorder. So I think Fred and I would say that "IT" isn't fixed in 9.2!! PeterB p.s. xmas must be here, the Chia Pet ads, and the shaver ads are on TV again --
On Sunday 28 November 2004 21:28, Peter B Van Campen wrote:
Perhaps this is the reason Shilling at SUSE has modified 'cdrecord'?
:) Jörg Schilling doesn't work at SuSE. In fact he seems to hate SuSE with a vengeance. The modifications to cdrecord far predates the changes in the kernel, and mainly concerns DVD recording I think. As far as I understand it, SuSE has added dvd recording capabilities to cdrecord, which is something Schilling has implemented in a different version and I don't think he likes the competition. btw, the SuSE version of 2.6.8 contains the patches from 2.6.9 that enables non-root CD and DVD burning. The change had to do with what SCSI commands were allowed.
On Sun November 28 2004 3:45 pm, Anders Johansson wrote:
On Sunday 28 November 2004 21:28, Peter B Van Campen wrote:
Perhaps this is the reason Shilling at SUSE has modified 'cdrecord'?
:) Jörg Schilling doesn't work at SuSE. In fact he seems to hate SuSE with a vengeance.
Yes.....and I wonder why.
The modifications to cdrecord far predates the changes in the kernel, and mainly concerns DVD recording I think. As far as I understand it, SuSE has added dvd recording capabilities to cdrecord, which is something Schilling has implemented in a different version and I don't think he likes the competition.
Maybe that's it.
btw, the SuSE version of 2.6.8 contains the patches from 2.6.9 that enables non-root CD and DVD burning. The change had to do with what SCSI commands were allowed.
Well, there still are problems, and I've been assuming most are permission problems. Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah
On Sunday 28 November 2004 21:59, Fred A. Miller wrote:
Well, there still are problems, and I've been assuming most are permission problems.
Perhaps. What sort of trouble? Is there a thread on SLE about it? If there is, I must have missed it. What's the subject line?
On Sun November 28 2004 4:03 pm, Anders Johansson wrote:
On Sunday 28 November 2004 21:59, Fred A. Miller wrote:
Well, there still are problems, and I've been assuming most are permission problems.
Perhaps. What sort of trouble? Is there a thread on SLE about it? If there is, I must have missed it. What's the subject line?
'Can't tell you know, Anders. Presently, it won't run at all here.......can't find the drive. I messed around last night for over an hour trying to get it to work. Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah
* Fred Miller
'Can't tell you know, Anders. Presently, it won't run at all here.......can't find the drive. I messed around last night for over an hour trying to get it to work.
Give him/us specifics and what routes you followed to try to solve the problem, Fred. If you were discussing aspects of a photograph (one of Fred's fields) you would be *much* more detailed and specific. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Sun November 28 2004 4:47 pm, Patrick Shanahan wrote:
* Fred Miller
[11-28-04 16:44]: 'Can't tell you know, Anders. Presently, it won't run at all here.......can't find the drive. I messed around last night for over an hour trying to get it to work.
Give him/us specifics and what routes you followed to try to solve the problem, Fred. If you were discussing aspects of a photograph (one of Fred's fields) you would be *much* more detailed and specific.
Cute. :) I tried changing /dev/hdc to my ownership, same with /dev/cdrecorder, and the same with cdrecorder and other related files.......nada. Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah
On Sunday 28 November 2004 22:23, Fred A. Miller wrote:
I tried changing /dev/hdc to my ownership, same with /dev/cdrecorder, and the same with cdrecorder and other related files.......nada.
have you updated your kernel? (YOU) I thought they fixed it.
On Sun November 28 2004 5:28 pm, Jake wrote:
On Sunday 28 November 2004 22:23, Fred A. Miller wrote:
I tried changing /dev/hdc to my ownership, same with /dev/cdrecorder, and the same with cdrecorder and other related files.......nada.
have you updated your kernel? (YOU) I thought they fixed it.
Yes.......right after it was available. Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah
On Sunday 28 November 2004 22:42, Fred A. Miller wrote:
On Sun November 28 2004 4:03 pm, Anders Johansson wrote:
On Sunday 28 November 2004 21:59, Fred A. Miller wrote:
Well, there still are problems, and I've been assuming most are permission problems.
Perhaps. What sort of trouble? Is there a thread on SLE about it? If there is, I must have missed it. What's the subject line?
'Can't tell you know, Anders. Presently, it won't run at all here.......can't find the drive. I messed around last night for over an hour trying to get it to work.
Can you mount it if you have a recorded data CD or DVD in there? If you can, what is the line in fstab? And what are the permissions on the device node?
On Sun November 28 2004 5:29 pm, Anders Johansson wrote:
On Sunday 28 November 2004 22:42, Fred A. Miller wrote:
On Sun November 28 2004 4:03 pm, Anders Johansson wrote:
On Sunday 28 November 2004 21:59, Fred A. Miller wrote:
Well, there still are problems, and I've been assuming most are permission problems.
Perhaps. What sort of trouble? Is there a thread on SLE about it? If there is, I must have missed it. What's the subject line?
'Can't tell you know, Anders. Presently, it won't run at all here.......can't find the drive. I messed around last night for over an hour trying to get it to work.
Can you mount it if you have a recorded data CD or DVD in there? If you can, what is the line in fstab? And what are the permissions on the device node?
By "recorded," I assume you mean audio. If so, no....not even with using "audiocd:/" for the address......worked in 9.1. Fstab result is: /dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset= utf8 0 0 Thanks, Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah
On Tuesday 30 November 2004 01:14, Fred A. Miller wrote:
On Sun November 28 2004 5:29 pm, Anders Johansson wrote:
On Sunday 28 November 2004 22:42, Fred A. Miller wrote:
On Sun November 28 2004 4:03 pm, Anders Johansson wrote:
On Sunday 28 November 2004 21:59, Fred A. Miller wrote:
Well, there still are problems, and I've been assuming most are permission problems.
Perhaps. What sort of trouble? Is there a thread on SLE about it? If there is, I must have missed it. What's the subject line?
'Can't tell you know, Anders. Presently, it won't run at all here.......can't find the drive. I messed around last night for over an hour trying to get it to work.
Can you mount it if you have a recorded data CD or DVD in there? If you can, what is the line in fstab? And what are the permissions on the device node?
By "recorded," I assume you mean audio.
No, I said data CD and I meant data CD. I said recorded in the sense that you were talking about trying to burn things in K3B, so I was just wondering if you could use CDs that had something already on them. i.e. regular data CDs, like the SuSE CDs.
If so, no....not even with using "audiocd:/" for the address......worked in 9.1. Fstab result is: /dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset= utf8 0 0
ok, and how about "/sbin/resmgr list" (run as your regular user)
On Monday 29 November 2004 6:21 pm, Anders Johansson wrote:
On Tuesday 30 November 2004 01:14, Fred A. Miller wrote:
On Sun November 28 2004 5:29 pm, Anders Johansson wrote:
ok, and how about "/sbin/resmgr list" (run as your regular user)
Hi Anders, here is my output: @linux:~> /sbin/resmgr list rw-- /dev/audio rw-- /dev/mixer rw-- /dev/dsp rw-- /dev/sequencer rw-- /dev/video rw-- /dev/modem rw-p /dev/cdrom rw-p /dev/cdrom1 rw-- /dev/cdrecorder rw-p /dev/dvd rw-p /dev/dvd1 rw-- /dev/sr0 rw-- /dev/sr1 rw-- /dev/sr2 rw-- /dev/sr3 rws- /dev/scanner r--- /dev/console rw-- /dev/pilot rw-- usb:any ***a@linux:~> /sbin/resmgr login *** :0 status code 502 server message follows: you are not allowed to do this ***@linux:~> su Password: su: incorrect password ***@linux:~> su Password: linux:/home/*** # /sbin/resmgr login pbvanca :0 success linux:/home/*** # /sbin/resmgr list status code 200 server message follows: no devices available PeterB
On Tuesday 30 November 2004 03:13, Peter B Van Campen wrote:
On Monday 29 November 2004 6:21 pm, Anders Johansson wrote:
On Tuesday 30 November 2004 01:14, Fred A. Miller wrote:
On Sun November 28 2004 5:29 pm, Anders Johansson wrote:
ok, and how about "/sbin/resmgr list" (run as your regular user)
Hi Anders,
here is my output:
@linux:~> /sbin/resmgr list rw-- /dev/audio rw-- /dev/mixer rw-- /dev/dsp rw-- /dev/sequencer rw-- /dev/video rw-- /dev/modem rw-p /dev/cdrom rw-p /dev/cdrom1 rw-- /dev/cdrecorder rw-p /dev/dvd rw-p /dev/dvd1 rw-- /dev/sr0 rw-- /dev/sr1 rw-- /dev/sr2 rw-- /dev/sr3 rws- /dev/scanner r--- /dev/console rw-- /dev/pilot rw-- usb:any
This looks good, this means resmgr sees your login and gives you permissions to the devices. If there's some device you still don't get permissions on, it means either it's not listed in the above (in which case, add it to /etc/resmgr.conf) or the program you're using isn't set to use resmgr, in which case use the regular unix permissions
***a@linux:~> /sbin/resmgr login *** :0 status code 502 server message follows: you are not allowed to do this ***@linux:~> su Password: su: incorrect password ***@linux:~> su Password: linux:/home/*** # /sbin/resmgr login pbvanca :0
:)
success linux:/home/*** # /sbin/resmgr list status code 200 server message follows: no devices available
Yeah, you should exit from root. The "list" should be run as regular user
On Mon November 29 2004 7:21 pm, Anders Johansson wrote:
On Tuesday 30 November 2004 01:14, Fred A. Miller wrote:
On Sun November 28 2004 5:29 pm, Anders Johansson wrote:
On Sunday 28 November 2004 22:42, Fred A. Miller wrote:
On Sun November 28 2004 4:03 pm, Anders Johansson wrote:
On Sunday 28 November 2004 21:59, Fred A. Miller wrote:
Well, there still are problems, and I've been assuming most are permission problems.
Perhaps. What sort of trouble? Is there a thread on SLE about it? If there is, I must have missed it. What's the subject line?
'Can't tell you know, Anders. Presently, it won't run at all here.......can't find the drive. I messed around last night for over an hour trying to get it to work.
Can you mount it if you have a recorded data CD or DVD in there? If you can, what is the line in fstab? And what are the permissions on the device node?
By "recorded," I assume you mean audio.
No, I said data CD and I meant data CD. I said recorded in the sense that you were talking about trying to burn things in K3B, so I was just wondering if you could use CDs that had something already on them. i.e. regular data CDs, like the SuSE CDs.
Sorry.....missed the "data." Sure......look at any data CD.
If so, no....not even with using "audiocd:/" for the address......worked in 9.1. Fstab result is: /dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset= utf8 0 0
ok, and how about "/sbin/resmgr list" (run as your regular user)
Ah........the first time I ran it, I didn't put in a CD....now I did, and I get: /sbin/resmgr list rw-- /dev/audio rw-- /dev/mixer rw-- /dev/dsp rw-- /dev/sequencer rw-- /dev/video rw-- /dev/modem rw-p /dev/cdrom rw-p /dev/cdrom1 rw-- /dev/cdrecorder rw-p /dev/dvd rw-p /dev/dvd1 rw-- /dev/sr0 rw-- /dev/sr1 rw-- /dev/sr2 rw-- /dev/sr3 rws- /dev/scanner r--- /dev/console rw-- /dev/pilot rw-- usb:any Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah
On Sunday 28 November 2004 22:42, Fred A. Miller wrote:
On Sun November 28 2004 4:03 pm, Anders Johansson wrote:
On Sunday 28 November 2004 21:59, Fred A. Miller wrote:
Well, there still are problems, and I've been assuming most are permission problems.
Perhaps. What sort of trouble? Is there a thread on SLE about it? If there is, I must have missed it. What's the subject line?
'Can't tell you know, Anders. Presently, it won't run at all here.......can't find the drive. I messed around last night for over an hour trying to get it to work.
Also, what is the output from "/sbin/resmgr list"? Did you try running (as root) "/sbin/resmgr login fred :0"? (replace 'fred' with whatever your username is)
On Sun November 28 2004 5:32 pm, Anders Johansson wrote:
On Sunday 28 November 2004 22:42, Fred A. Miller wrote:
On Sun November 28 2004 4:03 pm, Anders Johansson wrote:
On Sunday 28 November 2004 21:59, Fred A. Miller wrote:
Well, there still are problems, and I've been assuming most are permission problems.
Perhaps. What sort of trouble? Is there a thread on SLE about it? If there is, I must have missed it. What's the subject line?
'Can't tell you know, Anders. Presently, it won't run at all here.......can't find the drive. I messed around last night for over an hour trying to get it to work.
Also, what is the output from "/sbin/resmgr list"?
/sbin/resmgr list status code 200 server message follows: no devices available
Did you try running (as root) "/sbin/resmgr login fred :0"? (replace 'fred' with whatever your username is)
Yes.....it works. Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah
On Tuesday 30 November 2004 01:49, Fred A. Miller wrote:
Did you try running (as root) "/sbin/resmgr login fred :0"? (replace 'fred' with whatever your username is)
Yes.....it works.
meaning what? That everything works after you've run that? What's in /etc/pam.d/login ? Perhaps you should just use kdm to log in, to avoid all these hassles?
On Mon November 29 2004 8:06 pm, Anders Johansson wrote:
On Tuesday 30 November 2004 01:49, Fred A. Miller wrote:
Did you try running (as root) "/sbin/resmgr login fred :0"? (replace 'fred' with whatever your username is)
Yes.....it works.
meaning what? That everything works after you've run that?
What's in /etc/pam.d/login ?
#%PAM-1.0 auth requisite pam_unix2.so nullok #set_secrpc auth required pam_securetty.so auth required pam_nologin.so #auth required pam_homecheck.so auth required pam_env.so auth required pam_mail.so account required pam_unix2.so password required pam_pwcheck.so nullok password required pam_unix2.so nullok use_first_pass use_autht ok session required pam_unix2.so none # debug or trace session required pam_limits.so session required pam_resmgr.so
Perhaps you should just use kdm to log in, to avoid all these hassles?
'SHOULDN'T be any hassles. Fred -- "As Internet technology itself vaults into new areas, so too does the Microsoft monopoly and its tried-and-true bag of tricks." -US Senator Orrin Hatch, (R) Utah
On Tuesday 30 November 2004 18:08, Fred A. Miller wrote:
Perhaps you should just use kdm to log in, to avoid all these hassles?
'SHOULDN'T be any hassles.
I know there shouldn't, but apparently there is, so why not try it and see if you avoid the problems you've seen so far. It would be a good way to isolate the problem
On Sun, 28 Nov 2004, Fred A. Miller wrote:
On Sun November 28 2004 4:03 pm, Anders Johansson wrote:
On Sunday 28 November 2004 21:59, Fred A. Miller wrote:
Well, there still are problems, and I've been assuming most are permission problems.
Perhaps. What sort of trouble? Is there a thread on SLE about it? If there is, I must have missed it. What's the subject line?
'Can't tell you know, Anders. Presently, it won't run at all here.......can't find the drive. I messed around last night for over an hour trying to get it to work.
Don't know if this helps, but I had a weird one last night.
I used to use /dev/sg0 without issue.
*Sometimes* it works with /dev/sr0.
I works *every* time if I strace it. THAT is messed up.
Again: if I run cdrecord blah blah blah it fails, if I run strace
cdrecord blah blah blah it works.
--
Carpe diem - Seize the day.
Carp in denim - There's a fish in my pants!
Jon Nelson
Anders Johansson wrote:
On Sunday 28 November 2004 21:28, Peter B Van Campen wrote:
Perhaps this is the reason Shilling at SUSE has modified 'cdrecord'?
:) Jörg Schilling doesn't work at SuSE. In fact he seems to hate SuSE with a vengeance.
He hates Linux as the kernel developers want to phase out the crazy idea of ide-scsi. We went through a period when cdrtools wouldn't build on 2.6, I think Linus corrected that, but Herr Schilling is not a happy man when it comes to Linux, just that SuSE riles him raw. From his homepage:- "The user land SCSI transport implementations on Linux and *BSD (except FreeBSD/cam) are the worst ones. Linux will not tell you all errors while *BSD (except FreeBSD/cam) hides the device files from you. SGI does not allow SCSI disconnects on odd-byte-count boundaries. Look for my SCSI implementation ratings."
The modifications to cdrecord far predates the changes in the kernel, and mainly concerns DVD recording I think. As far as I understand it, SuSE has added dvd recording capabilities to cdrecord, which is something Schilling has implemented in a different version and I don't think he likes the competition.
I bypassed the crazy rants and put ide-cd into my kernels instead of ide-scsi and went permanently xcdroast. I tried using udftools, I was able for format CD-RW's, but I couldn't mount them so I could do a straight cp of stuff to them - that was sometime ago. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
On Sunday 28 November 2004 02:28 pm, Peter B Van Campen wrote:
Hi,
The 'owner' of K3b, Sabastian T. has this posted on the www.k3b.org page:
"Do not use Kernel 2.6.8
Perhaps this is the reason Shilling at SUSE has modified 'cdrecord'?
My advice == Follow the work-arounds as you have discussed here on the list and await more news.
Anyone can say anything, I guess, so I'll say --It works for me-- My Suse 9.2 amd64 install using 2.6.8-24.3-default burns dvd's using k3b and I did nothing but intall from the dvd and you updates. Nothing special... it just works... for me. Doug
participants (9)
-
Anders Johansson
-
Doug B
-
Fred A. Miller
-
Jake
-
Jon Nelson
-
Kastus
-
Patrick Shanahan
-
Peter B Van Campen
-
Sid Boyce