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 ]