From owner-freebsd-ports@FreeBSD.ORG Mon Mar 21 19:56:38 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 422D116A4CE for ; Mon, 21 Mar 2005 19:56:38 +0000 (GMT) Received: from po0.wam.umd.edu (po0.wam.umd.edu [128.8.10.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92EDB43D3F for ; Mon, 21 Mar 2005 19:56:37 +0000 (GMT) (envelope-from cog@umd.edu) Received: from dragon.student.umd.edu (dragon.student.umd.edu [129.2.217.220]) by po0.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j2LJuamH014243; Mon, 21 Mar 2005 14:56:36 -0500 (EST) From: Gregory Crosswhite To: h.eichmann@gmx.de Date: Mon, 21 Mar 2005 14:56:46 -0500 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200503211456.46873.cog@umd.edu> cc: ports@freebsd.org Subject: FreeBSD Port: k3b-0.11.20_1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 19:56:38 -0000 I got k3b to work under 5.2.1, but after upgrading to 5.3 I've started gett= ing=20 the following error message (using the k3b 0.11.20_1 port): =2D=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- k3b: (K3bCdDevice) /dev/cd0: init() k3b: (K3bCdDevice::ScsiCommand) open device /dev/pass1 succeeded. k3b: (K3bCdDevice::ScsiCommand) transport command 12, length: 6 k3b: (K3bCdDevice::ScsiCommand) transport command 46, length: 9 k3b: (K3bCdDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bCdDevice::ScsiCommand) failed: k3b: command: GET CONFIGURATION (46) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bCdDevice) /dev/cd0: GET_CONFIGURATION failed. k3b: (K3bCdDevice::ScsiCommand) open device /dev/pass1 succeeded. k3b: (K3bCdDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bCdDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bCdDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bCdDevice::CdDevice) /dev/cd0: MODE SENSE length det failed. k3b: (K3bCdDevice::ScsiCommand) device /dev/pass1 closed. k3b: (K3bCdDevice::CdDevice) /dev/cd0: modeSense 0x05 failed! k3b: (K3bCdDevice::CdDevice) /dev/cd0: Cannot check write modes. k3b: (K3bCdDevice::ScsiCommand) open device /dev/pass1 succeeded. k3b: (K3bCdDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bCdDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bCdDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bCdDevice::CdDevice) /dev/cd0: MODE SENSE length det failed. k3b: (K3bCdDevice::ScsiCommand) device /dev/pass1 closed. k3b: (K3bCdDevice) /dev/cd0: read mode page 2A failed! k3b: (K3bCdDevice::ScsiCommand) open device /dev/pass1 succeeded. k3b: (K3bCdDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bCdDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bCdDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bCdDevice::CdDevice) /dev/cd0: MODE SENSE length det failed. k3b: (K3bCdDevice::ScsiCommand) device /dev/pass1 closed. k3b: (K3bCdDevice::ScsiCommand) open device /dev/pass1 succeeded. k3b: (K3bCdDevice::ScsiCommand) transport command 5a, length: 9 k3b: (K3bCdDevice::ScsiCommand) transport failed (4): 336896 k3b: (K3bCdDevice::ScsiCommand) failed: k3b: command: MODE SENSE (5a) k3b: errorcode: 70 k3b: sense key: ILLEGAL REQUEST (5) k3b: asc: 24 k3b: ascq: 0 k3b: (K3bCdDevice::CdDevice) /dev/cd0: MODE SENSE length det failed. k3b: (K3bCdDevice::ScsiCommand) device /dev/pass1 closed. k3b: (K3bCdDevice::ScsiCommand) device /dev/pass1 closed. =2D=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- The end result is that although it detects my cdrw as a Reader, it doesn't= =20 detect it as a Writer. It worked just fine, though under 5.2.1. (Although= I=20 wipe and reinstalled the system and then recompiled the kernel, so maybe I= =20 changed something else without realizing it.) The kernel should have all the correct modules and everything loaded, =2D=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) =2D=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- and these problems were all reported under "root" so I know it's not an acc= ess=20 control error. Running "camcontrol" gives, =2D=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- su-2.05b# camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) at scbus0 target 5 lun 0 (cd0,pass1) =2D=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Running cdrecord gives =2D=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- su-2.05b# cdrecord -scanbus Cdrecord 2.00.3 (i386-unknown-freebsd5.3) Copyright (C) 1995-2002 J=F6rg=20 Schilling Using libscg version 'schily-0.7' scsibus0: 0,0,0 0) 'IBM ' 'DDYS-T18350N ' 'S96H' Disk 0,1,0 1) * 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) 'YAMAHA ' 'CRW2100S ' '1.0K' Removable CD-ROM 0,6,0 6) * 0,7,0 7) * =2D=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- I have also successfully burned CDs with cdrecord, so I know that the hardw= ard=20 itself is fine, and the cd driver in the kernel is fine. I know practically nothing about SCSI, but it looks to me as if the cd driv= er=20 in kernel doesn't like something about the commands that k3b is sending to= =20 it. I don't know, however, whether this means I've screwed something up in= =20 the kernel (which seems unlikely since I can burn using cdrecord), or wheth= er=20 k3b is sending the wrong command. (Or whether there's some third option=20 which I'm missing in my ignorance. :-) ) If you get a chance, could you advise me as to what might be causing this=20 problem? Thank you very much for your time. =2D Greg