I should have googled in the first place before trying to see what's
going on with the permissions, and now that I've found the command can
see that I get better info this way too. I saw that the permissions on
/media/cdrecorder (the mount point?) is everyone has rwx. And on the
device is only root had rw, the group and others had nothing. So using
chmod I gave group and others rw permission. Yet still the device
appears to be dead...
SuSEbox:/home/roger # ls -l /media/
total 12
drwxr-xr-x 5 root root 4096 2005-05-30 06:29 .
drwxr-xr-x 24 root root 4096 2005-06-05 08:27 ..
drwxrwxrwx 1 root root 0 2005-06-06 05:17 cdrecorder
drwxrwxrwx 1 root root 0 2005-06-06 05:17 floppy
drwxr-xr-x 2 root root 4096 2005-05-19 05:48
usb-storage-odd-Sony-SonyDSC:0:0:0p1
SuSEbox:/home/roger # ls -l /dev/hdd
brw------- 1 roger disk 22, 64 2004-04-07 01:27 /dev/hdd
SuSEbox:/home/roger # chmod a+rw /dev/hdd
SuSEbox:/home/roger # ls -l /dev/hdd
brw-rw-rw- 1 roger disk 22, 64 2004-04-07 01:27 /dev/hdd
SuSEbox:/home/roger # cd /media/cdrecorder/
SuSEbox:/media/cdrecorder # ls
/bin/ls: .: No medium found
The interesting thing that's come from this exercise is that I now
realise that I'm preferring to use the command line to do this, so in
that regard I'm making progress. Now if only I could get the drive
working...
Roger
Nick Rout wrote:
Sounds like you have a permission problem. So tell us what the ownership
& permissions are on the device and mount point.
On Sun, 2005-06-05 at 18:51 +1200, Roger Searle wrote:
SuSEbox:/home/roger # cdrecord --scanbus dev=ATAPI
scsidev: 'ATAPI'
devname: 'ATAPI'
scsibus: -2 target: -2 lun: -2
Use of ATA is preferred over ATAPI.
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) 'AOPEN ' 'CD-RW CRW4048 ' '1.05' 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) *
It's correctly identifying the manufacturer and speed of the device.
Still, I'm getting "Could not enter folder /media/cdrecorder" when
trying to view files on a cd. So my problem isn't really about k3b
itself, the drive won't see any files regardless of method in suse.
I'd swap another drive into the machine if I had one, unfortunately it's
the only one in the house right now. Got to boot to windows in the mean
time to make CDs :-( (would rather not).
Cheers,
Roger
Nick Rout wrote:
On Sun, June 5, 2005 12:06 am, Ross Drummond said:
Running cdrecord --scanbus from the command line may yield some useful
info.
AFAIK that will only get scsi emulated devices. To get IDE devices where
there is no scsi emulation in place (as should be the case with 2.6.x
kernels) you will need:
cdrecord --scanbus dev=ATAPI:
Cheers Ross Drummond
On Sat, 04 Jun 2005 15:56, Roger Searle wrote:
Hi, when trying to use k3b there is no device listed for the reading or
writing device. Trying to refresh or add a device through configure k3b
devices, using either /dev/hdd or /media/cdrecorder just gives
"could not find an additional device at [either of those paths]".
Cheers, Roger
