Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
Sorry, I neglected to remove your name. That was written by Andrea Venturoli, whose name appears after yours. On Saturday 25 March 2006 15:50, Duane Whitty wrote: Oliver Iberien wrote: On Saturday 25 March 2006 11:46, Andrea Venturoli wrote: Duane Whitty wrote: Please forgive me for stepping in, but I'm having the same problem, asked sometime ago and did not get any answer. My Yamaha burner is still detected as a read-only device. bye Thanks av. Hmm, I don't remember writing this at all... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
Oliver Iberien wrote: There is a thread here: http://lists.freebsd.org/mailman/htdig/freebsd-ports/2005-March/021958.html of someone with a scsi cd-r/w that was giving the same errors. The thread goes on to post some kind of fix to a flac decoder: http://lists.freebsd.org/mailman/htdig/freebsd-ports/2005-March/021969.html ...but I don't understand how this is related or how it is to be implemented. I don't know whether this is related either. However it mentions a build problem, which I haven't met. bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
Duane Whitty wrote: Please forgive me for stepping in, but I'm having the same problem, asked sometime ago and did not get any answer. I believe you may also need in defs.conf perm xpt0 0666 Did that, same situation. My Yamaha burner is still detected as a read-only device. bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
On Saturday 25 March 2006 11:46, Andrea Venturoli wrote: Duane Whitty wrote: Please forgive me for stepping in, but I'm having the same problem, asked sometime ago and did not get any answer. My Yamaha burner is still detected as a read-only device. bye Thanks av. There is a thread here: http://lists.freebsd.org/mailman/htdig/freebsd-ports/2005-March/021958.html of someone with a scsi cd-r/w that was giving the same errors. The thread goes on to post some kind of fix to a flac decoder: http://lists.freebsd.org/mailman/htdig/freebsd-ports/2005-March/021969.html ...but I don't understand how this is related or how it is to be implemented. I have found a number of postings of similar problems with k3b and scsi drives dating from after mid-2004, which is when it started happening to me, but none gives a fix. http://linux.derkeiler.com/Mailing-Lists/SuSE/2005-03/1489.html http://72.14.203.104/search?q=cache:wOJpu0m4BcwJ:k3b.plainblack.com/feedback%3Ffunc%3Dview%26wid%3D29%26forumId%3D1000%26forumOp%3DviewThread%26forumPostId%3D100898+k3b+%22mode+sense%22hl=engl=usct=clnkcd=1ie=UTF-8 http://www.linuxhardware.de/deutsch/dcoulh/news_38206.html http://linuxfromscratch.org/pipermail/blfs-support/2004-June/050551.html http://72.14.203.104/search?q=cache:Dh1vQLiRy40J:bbs.cse.yzu.edu.tw/show.php%3Ftype%3Dpost%26board%3Dbsd-ports%26pageno%3D15+k3b+%22mode+sense%22hl=engl=usct=clnkcd=6ie=UTF-8 http://lurker.oltrelinux.com/message/20040211.213612.0308c619.en.html Oliver k3b on FreeBSD 6.0 incorrectly identifies my SCSI CD-R/W as read-only. It reports mode sense failure, which, Plextor tells me, can be a sign of a problem with the drive or the media. I've appended this part of the output at the bottom. However, cdrecord is able correctly to query the drive. Here is that output: Cdrecord-Clone 2.01 (i386-unknown-freebsd6.0) Copyright (C) 1995-2004 Jörg Schilling TOC Type: 0 = CD-DA scsidev: '0,0' scsibus: 0 target: 0 lun: 0 Using libscg version 'schily-0.8'. SCSI buffer size: 64512 atapi: 0 Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : SYNC Vendor_info : 'PLEXTOR ' Identifikation : 'CD-R PX-W4012S' Revision : '1.01' Device seems to be: Generic mmc CD-RW. Current: 0x0009 Profile: 0x0008 Profile: 0x0009 (current) Profile: 0x000A Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE VARIREC FORCESPEED SINGLESESSION HIDECDR Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 2394336 = 2338 KB Drive DMA Speed: 13933 kB/s 79x CD 10x DVD FIFO size : 4194304 = 4096 KB This looks as if the information is there for the asking, but I am no SCSI expert. It went on to burn without a hitch. k3b worked with this drive when I used SuSE 9.1, and when I experimentally put in the old drive that had SuSE on it with its old version of k3b, it identified the drive without problems. Any clues leading towards getting k3b working would be much appreciated it. Thanks, Oliver k3b output (extract): k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::Device) /dev/cd0: modeSense 0x05 failed! k3b: (K3bDevice::Device) /dev/cd0: Cannot check write modes. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::Device) /dev/cd0: read mode page 2A failed! k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b:
Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
Oliver Iberien wrote: On Saturday 25 March 2006 11:46, Andrea Venturoli wrote: Duane Whitty wrote: Please forgive me for stepping in, but I'm having the same problem, asked sometime ago and did not get any answer. My Yamaha burner is still detected as a read-only device. bye Thanks av. Hmm, I don't remember writing this at all... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
On Friday 24 March 2006 12:29, you wrote: On 3/24/06, Oliver Iberien [EMAIL PROTECTED] wrote: On Friday 24 March 2006 12:12, you wrote: On 3/24/06, Oliver Iberien [EMAIL PROTECTED] wrote: I've got my Plextor PX-W4012S SCSI R/W drive recognized by k3b by adding ALL ALL = NOPASSWD: /sbin/camcontrol devlist to sudoers and starting k3b with sudo. Unfortunately, k3b has the idea that this is read-only. [snip] [snip] but /etc/devfs.conf (i think) has places where you can set the permission to devices. I believe I did 0666 (read/write to all) for acd0, cdrom0,... pass0, [snip] I had done that. I can access the drive, but it is still not being correctly recognized as a writer. [snip] What happens when you run k3b as root (just to test) Also, what are the permissions on (assuming the writer is the first cd device) /dev/cd0 /dev/acd0 /dev/pass0 From /etc/devfs.conf: own acd0root:wheel own cd0 root:wheel own pass0 root:wheel permpass0 0666 permacd 0666 permcd0 0666 perm/cdrom 0666 perm/cdrom1 0666 own /cdrom 0666 own /cdrom1 0666 k3b run as root fails though not being about to connect to X. Starting up k3b with sudo gives a bouquet of k3b errors, one of which is MODE SENSE FAILS: k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b:command:MODE SENSE (5a) k3b:errorcode: 70 k3b:sense key: ILLEGAL REQUEST (5) k3b:asc:24 k3b:ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::Device) /dev/cd0: modeSense 0x05 failed! k3b: (K3bDevice::Device) /dev/cd0: Cannot check write modes. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b:command:MODE SENSE (5a) k3b:errorcode: 70 k3b:sense key: ILLEGAL REQUEST (5) k3b:asc:24 k3b:ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::Device) /dev/cd0: read mode page 2A failed! k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b:command:MODE SENSE (5a) k3b:errorcode: 70 k3b:sense key: ILLEGAL REQUEST (5) k3b:asc:24 k3b:ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b:command:MODE SENSE (5a) k3b:errorcode: 70 k3b:sense key: ILLEGAL REQUEST (5) k3b:asc:24 k3b:ascq: 0 k3b: (K3bDevice::Device) /dev/cd0: MODE SENSE length det failed. k3b: (K3bDevice::Device) /dev/cd0: modeSense 0x05 failed! k3b: (K3bDevice::Device) /dev/cd0: Cannot check write modes. Would anyone have an idea how to fix this? Oliver Whole k3b startup follows: $ sudo k3b Password: ERROR: Communication problem with k3b, it probably crashed. $ k3b: (K3bExternalBinManager) Cdrecord 2.1 features: gracetime, overburn, cdtext, clone, tao, cuefile, xamix, plain-atapi, hacked-atapi k3b: (K3bExternalBinManager) 2 1 -1 seems to be cdrecord version = 1.11a02, using burnfree instead of burnproof k3b: (K3bExternalBinManager) seems to be cdrecord version = 1.11a31, support for Just Link via burnfree driveroption k3b: (BSDDeviceScan) number of matches 8 k3b: (BSDDeviceScan) add device /dev/cd0:0:0:0 k3b: (K3bDevice::Device) /dev/cd0: init() k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::openDevice) open device /dev/pass0 succeeded. k3b: (K3bDevice::ScsiCommand) transport command 12, length: 6 k3b: (K3bDevice::ScsiCommand) transport command 46, length: 9 k3b: (K3bDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bDevice::ScsiCommand) failed: k3b:command:GET CONFIGURATION (46) k3b:errorcode: 70 k3b:sense key: ILLEGAL REQUEST (5) k3b:asc:24 k3b:ascq: 0 k3b:
Re: k3b incorrectly identifies scsi r/w drive as read-only -- Mode sense fails
Oliver Iberien wrote: On Friday 24 March 2006 12:29, you wrote: On 3/24/06, Oliver Iberien [EMAIL PROTECTED] wrote: On Friday 24 March 2006 12:12, you wrote: On 3/24/06, Oliver Iberien [EMAIL PROTECTED] wrote: I've got my Plextor PX-W4012S SCSI R/W drive recognized by k3b by adding ALL ALL = NOPASSWD: /sbin/camcontrol devlist to sudoers and starting k3b with sudo. Unfortunately, k3b has the idea that this is read-only. [snip] [snip] but /etc/devfs.conf (i think) has places where you can set the permission to devices. I believe I did 0666 (read/write to all) for acd0, cdrom0,... pass0, [snip] I had done that. I can access the drive, but it is still not being correctly recognized as a writer. [snip] What happens when you run k3b as root (just to test) Also, what are the permissions on (assuming the writer is the first cd device) /dev/cd0 /dev/acd0 /dev/pass0 From /etc/devfs.conf: own acd0root:wheel own cd0 root:wheel own pass0 root:wheel permpass0 0666 permacd 0666 permcd0 0666 perm/cdrom 0666 perm/cdrom1 0666 own /cdrom 0666 own /cdrom1 0666 Hi, I believe you may also need in defs.conf perm xpt0 0666 --Duane [snip] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
