![](https://seccdn.libravatar.org/avatar/98de985e19069a920bc7160ac9560667.jpg?s=120&d=mm&r=g)
Hi all, Suddenly, out of the blue, my stock standard cdrecord on SUSE 9.0 Pro stopped working. Yes, I have changed some things since the last time I used it - compiled and installed KDE 3.2 - I don't see that that should interfere. Either ways, I'm getting this error:cdrecord: Permission denied. Cannot open '/dev/pg1'. Cannot open SCSIdriver. Why cdrecord would like to use /dev/pg1 I don't know - as I understand pg1 is a parallel port device of sorts. I have searched the archives and found references to the problem, but no solution or at least an rough idea of *why* cdrecord would suddenly want to access /dev/pg1 instead of sr1/sg1 - same for google. Things I've tried: -reinstalled cdrecord from the SUSE DVD -messed around with the permissions of /dev/pg1 -messed aronnd with the permissions of the cdrecord binary -tried k3bwsetup2 (both stock and 0.11.5 I d/l and compiled yesterday) on the permissions- tried compiling vanilla cdrecord - couln't get it to compile, couln't get smake to compile to use that either. -reboot (shock horror :-) cdrecord does work as root though, but even setuid root on cdrecord doesn't helpcdrdao has no problem workin either as user or root. Any ideas why this is bugging me? Thanks -- Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za
![](https://seccdn.libravatar.org/avatar/72ee3b9e0735cf98a1e936a90fc087ed.jpg?s=120&d=mm&r=g)
On Friday 27 February 2004 10.56, Hans du Plooy wrote:
Hi all,
Suddenly, out of the blue, my stock standard cdrecord on SUSE 9.0 Pro stopped working. Yes, I have changed some things since the last time I used it - compiled and installed KDE 3.2 - I don't see that that should interfere.
I guess the problem is that the new kde won't register you as logged in in resmgr. To verify that this is the problem, su to root and run resmgr login <username> :0 then try using cdrecord again as your regular user
![](https://seccdn.libravatar.org/avatar/98de985e19069a920bc7160ac9560667.jpg?s=120&d=mm&r=g)
On Friday 27 February 2004 12:08, Anders Johansson wrote:
I guess the problem is that the new kde won't register you as logged in in resmgr.
To verify that this is the problem, su to root and run
resmgr login <username> :0
then try using cdrecord again as your regular user
Thanks, I'll try that - it's my home machine, so I'll report back on monday :-) Just one question though. I'm getting the same behaviour if I work in a terminal, with no x or kde running - and that also worked before. What other apps/services/scripts that run when one boots up or logs in would log one into resmgr? I thingk you're right though, because on a previous occation I tried to burn a cd without resmgr running and it wasn't happy either. Can't remember the error though. Thanks -- Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za
![](https://seccdn.libravatar.org/avatar/72ee3b9e0735cf98a1e936a90fc087ed.jpg?s=120&d=mm&r=g)
On Friday 27 February 2004 11.19, Hans du Plooy wrote:
On Friday 27 February 2004 12:08, Anders Johansson wrote:
I guess the problem is that the new kde won't register you as logged in in resmgr.
To verify that this is the problem, su to root and run
resmgr login <username> :0
then try using cdrecord again as your regular user
Thanks, I'll try that - it's my home machine, so I'll report back on monday :-)
Just one question though. I'm getting the same behaviour if I work in a terminal, with no x or kde running - and that also worked before. What other apps/services/scripts that run when one boots up or logs in would log one into resmgr?
You'd need to add this line to /etc/pam.d/login session optional pam_resmgr.so grant=desktop Edit /etc/pam.d/sshd to get support for ssh sessions. It says in that file what to uncomment to get it working I forget exactly what I put in what file to solve it for kde logins, I *think* I put this line in /etc/pam.d/xdm session required pam_resmgr.so that is to say, I have that line in that file, but I forget if that was what solved it
![](https://seccdn.libravatar.org/avatar/98de985e19069a920bc7160ac9560667.jpg?s=120&d=mm&r=g)
On Fri, 2004-02-27 at 12:08, Anders Johansson wrote:
I guess the problem is that the new kde won't register you as logged in in resmgr.
Hi Anders, Thanks for the suggestion, I think that was the problem. However, I'm a bit bummed, because I tried using cdrecord again before fiddling with the resmgr stuff, and, it worked! Now I won't know for sure.... I think kde might have messed up those settings though. I tried to do rpmbuild --rebuild on all the src.rpms, but not all wanted to build. Most compiled fine, but broke while building the rpm. So when that happened I just cd into the source directory and did a make install (or make if it didn't finish compiling). That might have excluded something important. I started downloading the binaries this morning at work (we're already capped, so I might as well go crazy now - fortunately the cap is only on international bandwidth, so I can still grab stuff from local mirrors), and installed them before I tried fiddling with cdrecord again. That probably fixed it. Each day I learn something new! :-) Thanks -- Kind Regards Hans du Plooy Newington Consulting Service hansdp at newingtoncs dot co dot za
![](https://seccdn.libravatar.org/avatar/4380f8af3f24b864248651cab2fea673.jpg?s=120&d=mm&r=g)
Hello there, I have the same problem but results are different at my side. After I installed SuSE 9.0 Pro, everything worked fine: cdrecord, kooka, digital camera, etc... then suddenly things stopped working one by one. In some cases, I still could use them as root (i.e.: cdrecord) but now not even root can do much with those devices/utils... I did the "resmgr login <username> :0" and it returned a "sucess" - but cdrecord still doesn't work for neither my user (martin) nor root ... :-/ As root I issued a 'cdrecord -scanbus' and got all this crap on /var/log/messages: --- Feb 29 17:17:34 hexe resmgr[2017]: accepted connection from user root Feb 29 17:17:34 hexe cdrecord: resmgr: server response code 200 Feb 29 17:17:35 hexe modprobe: modprobe: Can't locate module paride_protocol Feb 29 17:17:35 hexe insmod: /lib/modules/2.4.21-99-default/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Feb 29 17:17:35 hexe insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 29 17:17:35 hexe insmod: /lib/modules/2.4.21-99-default/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Feb 29 17:17:36 hexe modprobe: modprobe: Can't locate module paride_protocol Feb 29 17:17:36 hexe resmgr[2017]: disconnect from root Feb 29 17:17:36 hexe insmod: /lib/modules/2.4.21-99-default/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Feb 29 17:17:36 hexe insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 29 17:17:36 hexe insmod: /lib/modules/2.4.21-99-default/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Feb 29 17:17:36 hexe modprobe: modprobe: Can't locate module paride_protocol Feb 29 17:17:36 hexe insmod: /lib/modules/2.4.21-99-default/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Feb 29 17:17:36 hexe insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 29 17:17:36 hexe insmod: /lib/modules/2.4.21-99-default/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Feb 29 17:17:37 hexe modprobe: modprobe: Can't locate module paride_protocol Feb 29 17:17:37 hexe insmod: /lib/modules/2.4.21-99-default/kernel/drivers/block/paride/pg.o: init_module: Operation not permitted Feb 29 17:17:37 hexe insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 29 17:17:37 hexe insmod: /lib/modules/2.4.21-99-default/kernel/drivers/block/paride/pg.o: insmod char-major-97 failed Feb 29 17:17:37 hexe kernel: paride: version 1.06 installed (parport) Feb 29 17:17:37 hexe kernel: pg: pg version 1.02, major 97 Feb 29 17:17:37 hexe kernel: pg0: Autoprobe failed Feb 29 17:17:37 hexe kernel: pg: No ATAPI device detected Feb 29 17:17:37 hexe kernel: paride: version 1.06 installed (parport) Feb 29 17:17:37 hexe kernel: pg: pg version 1.02, major 97 Feb 29 17:17:37 hexe kernel: pg0: Autoprobe failed Feb 29 17:17:37 hexe kernel: pg: No ATAPI device detected Feb 29 17:17:37 hexe kernel: paride: version 1.06 installed (parport) Feb 29 17:17:37 hexe resmgr[2017]: accepted connection from user root Feb 29 17:17:37 hexe kernel: pg: pg version 1.02, major 97 Feb 29 17:17:37 hexe cdrecord: resmgr: server response code 200 Feb 29 17:17:37 hexe kernel: pg0: Autoprobe failed Feb 29 17:17:37 hexe resmgr[2017]: disconnect from root Feb 29 17:17:37 hexe kernel: pg: No ATAPI device detected Feb 29 17:17:37 hexe kernel: paride: version 1.06 installed (parport) Feb 29 17:17:37 hexe kernel: pg: pg version 1.02, major 97 Feb 29 17:17:37 hexe kernel: pg0: Autoprobe failed Feb 29 17:17:37 hexe kernel: pg: No ATAPI device detected --- Which is quite weird, as I haven't messed up with the modules or the CDRW-device itself... yet. Information on this will be much appreciated! Regards, Martin
On Fri, 2004-02-27 at 12:08, Anders Johansson wrote:
I guess the problem is that the new kde won't register you as logged in in resmgr.
Hi Anders,
Thanks for the suggestion, I think that was the problem. However, I'm a bit bummed, because I tried using cdrecord again before fiddling with the resmgr stuff, and, it worked!
[ snip ]
![](https://seccdn.libravatar.org/avatar/72ee3b9e0735cf98a1e936a90fc087ed.jpg?s=120&d=mm&r=g)
On Monday 01 March 2004 11.39, Martin Mielke wrote:
Hello there,
I have the same problem but results are different at my side. After I installed SuSE 9.0 Pro, everything worked fine: cdrecord, kooka, digital camera, etc... then suddenly things stopped working one by one. In some cases, I still could use them as root (i.e.: cdrecord) but now not even root can do much with those devices/utils...
I did the "resmgr login <username> :0" and it returned a "sucess" - but cdrecord still doesn't work for neither my user (martin) nor root ... :-/
As root I issued a 'cdrecord -scanbus' and got all this crap on /var/log/messages: <snip> Which is quite weird, as I haven't messed up with the modules or the CDRW-device itself... yet.
Information on this will be much appreciated!
Try "cdrecord dev=ATAPI: -scanbus" That's what I need to do to get it to work without ide-scsi
![](https://seccdn.libravatar.org/avatar/0724cd2fec38c7b6f662bb7fda14c68c.jpg?s=120&d=mm&r=g)
On Mon, 1 Mar 2004 11:43:21 +0100
Anders Johansson
Try "cdrecord dev=ATAPI: -scanbus"
If you are using kernel > 2.6, you can also use the newer ATA, ie: cdrecord dev=ATA --scanbus Charles -- Running Windows on a Pentium is like having a brand new Porsche but only be able to drive backwards with the handbrake on. (Unknown source)
![](https://seccdn.libravatar.org/avatar/4380f8af3f24b864248651cab2fea673.jpg?s=120&d=mm&r=g)
Hi all, please see my reply inline... Anders Johansson wrote:
On Monday 01 March 2004 11.39, Martin Mielke wrote:
Hello there,
I have the same problem but results are different at my side. After I installed SuSE 9.0 Pro, everything worked fine: cdrecord, kooka, digital camera, etc... then suddenly things stopped working one by one. In some cases, I still could use them as root (i.e.: cdrecord) but now not even root can do much with those devices/utils...
I did the "resmgr login <username> :0" and it returned a "sucess" - but cdrecord still doesn't work for neither my user (martin) nor root ... :-/
As root I issued a 'cdrecord -scanbus' and got all this crap on /var/log/messages:
<snip>
Which is quite weird, as I haven't messed up with the modules or the CDRW-device itself... yet.
Information on this will be much appreciated!
Try "cdrecord dev=ATAPI: -scanbus"
That's what I need to do to get it to work without ide-scsi
I tried your suggestion as root and... oops! more weirdness...
See pasted text:
---
hexe:~ # cdrecord dev=ATAPI: -scanbus
Cdrecord-Clone 2.01a18-dvd (i686-suse-linux) Copyright (C) 1995-2003 Jörg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to
![](https://seccdn.libravatar.org/avatar/6d198f8c8f1c94ccef873cebcf4f5dfa.jpg?s=120&d=mm&r=g)
Martin Mielke wrote:
Hi all,
please see my reply inline...
Anders Johansson wrote:
On Monday 01 March 2004 11.39, Martin Mielke wrote:
Hello there,
I have the same problem but results are different at my side. After I installed SuSE 9.0 Pro, everything worked fine: cdrecord, kooka, digital camera, etc... then suddenly things stopped working one by one. In some cases, I still could use them as root (i.e.: cdrecord) but now not even root can do much with those devices/utils...
I did the "resmgr login <username> :0" and it returned a "sucess" - but cdrecord still doesn't work for neither my user (martin) nor root ... :-/
As root I issued a 'cdrecord -scanbus' and got all this crap on /var/log/messages:
<snip>
Which is quite weird, as I haven't messed up with the modules or the CDRW-device itself... yet.
Information on this will be much appreciated!
Try "cdrecord dev=ATAPI: -scanbus"
That's what I need to do to get it to work without ide-scsi
I tried your suggestion as root and... oops! more weirdness...
See pasted text:
---
hexe:~ # cdrecord dev=ATAPI: -scanbus Cdrecord-Clone 2.01a18-dvd (i686-suse-linux) Copyright (C) 1995-2003 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to
. Note: The author of cdrecord is not to be bothered with problems in this version.
There was a problem with 2.6.x kernels which has been resolved. There was quite a bit of vitriol on the kernel mailing list about this some time ago, looks like Jorg relented and later versions work. Grab the latest from freshmeat.net, "tar jxfv cdrtools-2.01a26.tar.bz2", "cd cdrtools-2.01", "Gmake", Gmake INS_BASE=/usr install" and enjoy. barrabas:/ftp/mar04 # cdrecord dev=ATAPI: -scanbus Cdrecord-Clone 2.01a26 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling scsidev: 'ATAPI:' devname: 'ATAPI' scsibus: -1 target: -1 lun: -1 Warning: Using ATA Packet interface. Warning: The related libscg interface code is in pre alpha. Warning: There may be fatal problems. Using libscg version 'schily-0.8'. scsibus0: 0,0,0 0) * 0,1,0 1) 'ATAPI ' 'COMBO48XMAX ' '1.10' Removable CD-ROM 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
![](https://seccdn.libravatar.org/avatar/72ee3b9e0735cf98a1e936a90fc087ed.jpg?s=120&d=mm&r=g)
On Thursday 04 March 2004 18.43, Martin Mielke wrote:
That's killing me... my CD-RW device has always been dev=0,0,0 -- and I swear I haven't messed up the wires inside my box. Furthermore, assuming that dev=1,0,0 would work is false, as I already tried it and stumbled again... so by now I can't burn CDROMs, which is starting to be quite annoying...
Suggestions?
Try burning with dev=ATAPI:1,0,0
participants (5)
-
Anders Johansson
-
Charles Philip Chan
-
Hans du Plooy
-
Martin Mielke
-
Sid Boyce