On Thu, 16 Dec 2004 16:42:38 +0000 (GMT), Mrugesh Karnik
k3b should detect the drive without problem. If it does not, there is something else wrong. Try from terminal, as root to issue: #cdrecord dev=ATA -scanbus
this should list all ATAPI devices attached. Try this as regular user as well, to see if it is the same. If you see your device, the k3b should recognize it too. Actually k3b is only a very good frontend to various programs, incl. cdrecord.
Here's the cdrecord output as a regular user
ZY$�: Operation not permitted. WARNING: Cannot set RR-scheduler ZY$�: Permission denied. WARNING: Cannot set priority using setpriority(). ZY$�: WARNING: This causes a high risk for buffer underruns. Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 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 http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 cdrecord: No such file or directory. Cannot open '/dev/hd*'. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
And here's the output as root:
Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 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 http://www.suse.de/feedback Note: The author of cdrecord should not be bothered with problems in this version. scsidev: 'ATA' devname: 'ATA' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Using libscg version 'schily-0.8'. cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.80-resmgr-patch '@(#)scsi-linux-sg.c 1.80 04/03/08 Copyright 1997 J. Schilling'). scsibus1: 1,0,0 100) 'SAMSUNG ' 'CD-R/RW SW-252B ' 'R701' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) *
Now, K3B doesn't detect drive. I checked in YaST and it shows me the drive. I removed it as the Installation Source and added it again and it works fine.
So, this is permission problem. If as root the drive is detected, but not as regular user. I have some suggestions, but first respond with the k3b vershion info. From terminal, as regular user: $k3b -v
As I said, I've had this problem before. K3B just doesn't detect the drive even if I point it /dev/hdc
k3b uses cdrecord for drive detection, so if cdrecord fails, then k3b will fail as well.
The previous line in fstab was this:
/dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid ,nodev,exec,iocharset=utf8 0 0
and
/dev/cdrom /media/cdrom subfs fs=cdfss,ro,procuid,nosuid ,nodev,exec,iocharset=utf8 0 0
Sometimes it used to mount both cdrecorder and cdrom even though I have only one drive! Both the locations would show the same contents of course!
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
comment out the /cdrom line, you do not need 2 mount points. it can confuse the system. -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85