From owner-freebsd-questions Thu Sep 12 12:08:15 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA23273 for questions-outgoing; Thu, 12 Sep 1996 12:08:15 -0700 (PDT) Received: from mother.cdrom.com (mother.cdrom.com [204.216.28.172]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA23268 for ; Thu, 12 Sep 1996 12:08:13 -0700 (PDT) Received: from localhost (support@localhost) by mother.cdrom.com (8.7.5/8.7.3) with SMTP id MAA00364 for ; Thu, 12 Sep 1996 12:08:13 -0700 (PDT) X-Authentication-Warning: mother.cdrom.com: support owned process doing -bs Date: Thu, 12 Sep 1996 12:08:12 -0700 (PDT) From: "Christopher G. Mann" To: questions@freebsd.org Subject: NOP! 2.2 SNAP still does not burn cds on my HP4020i (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can you guys try to help this guy? Technical Support Walnut Creek CDROM ---------- Forwarded message ---------- Date: Thu, 12 Sep 96 10:42:22 EDT From: mjschiff@atsmail.gc.lucent.com To: support@cdrom.com Subject: NOP! 2.2 SNAP still does not burn cds on my HP4020i Hi, Still having worm problems, even after loading the latest SNAP of 2.2 from a cdrom. If in the config file I define my worm as: controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows device worm0 **** When I boot a kernel with the worm configured as above I get my worm as an unknown device: aha0 at 0x330-0x333 irq 11 drq 6 on isa aha0 waiting for scsi devices to settle (aha0:0:0): "SEAGATE ST15150N 0017" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 4095MB (8388315 512 byte sectors) sd0(aha0:0:0): with 3712 cyls, 21 heads, and an average 107 sectors/track (aha0:1:0): "HP C4324/C4325 1.20" type 5 removable SCSI 2 uk0(aha0:1:0): Unknown (aha0:6:0): "EXABYTE EXB-8200 263H" type 1 removable SCSI 1 st0(aha0:6:0): Sequential-Access density code 0x0, drive empty ***** But, if I define my worm as the following: controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr controller scbus0 device sd0 # device worm0 # The previous devices (ch, sd, st, cd) are recognized by config. # config doesn't (and shouldn't) know about these newer ones, # so we have to specify that they are on a SCSI bus with the "at scbus?" # clause. device worm0 at scbus? # SCSI worm # SCSI OPTIONS: # SCSIDEBUG: When defined enables debugging macros # NO_SCSI_SENSE: When defined disables sense descriptions (about 4k) # SCSI_REPORT_GEOMETRY: Always report disk geometry at boot up instead # of only when booting verbosely. options SCSIDEBUG #options NO_SCSI_SENSE options SCSI_REPORT_GEOMETRY ***** With the above "hardwired" (I thinks thats hardwiring?) config of worm device I get: aha0 waiting for scsi devices to settle (aha0:0:0): "SEAGATE ST15150N 0017" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 4095MB (8388315 512 byte sectors) sd0(aha0:0:0): with 3712 cyls, 21 heads, and an average 107 sectors/track (aha0:1:0): "HP C4324/C4325 1.20" type 5 removable SCSI 2 worm0(aha0:1:0): Write-Once - see worm(4) for usage warnings worm0(aha0:1:0): NOT READY asc:4,0 worm0(aha0:1:0): Logical unit not ready, cause not reportable worm0(aha0:1:0): could not get size - can't get capacity. (aha0:6:0): "EXABYTE EXB-8200 263H" type 1 removable SCSI 1 ***** And when I burn a CDROM, I still get the following along with an ioctl(FIXATE...): worm0(aha0:1:0): ABORTED COMMAND asc:50,0 Write append error worm0(aha0:1:0): ABORTED COMMAND info:80002883 asc:50,0 Write append error Help! Mark Schiff