From owner-freebsd-scsi Sun May 3 11:41:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03951 for freebsd-scsi-outgoing; Sun, 3 May 1998 11:41:06 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03943 for ; Sun, 3 May 1998 11:41:01 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id NAA12375 for ; Sun, 3 May 1998 13:39:35 -0400 (EDT) Date: Sun, 3 May 1998 13:39:35 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: FreeBSD-scsi@FreeBSD.ORG Subject: scsi messages Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to get another new scsi disk working, and something that I've noticed in the past is puzzling me. The name of the drive, reported via the scsi bus, changes if I change the interface (such as changing the termination). The part that changes is a number at the end, something I've always seen as a 4 digit number. I don't know if it's restricted to be a 4 digit number, but values like 0512 or 0172 are reported, and these change. Does anyone know if there is any intelligence to be gleaned from this? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 3 12:57:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15773 for freebsd-scsi-outgoing; Sun, 3 May 1998 12:57:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15767 for ; Sun, 3 May 1998 12:57:16 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA04543; Sun, 3 May 1998 12:50:10 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd004541; Sun May 3 19:50:09 1998 Date: Sun, 3 May 1998 12:44:34 -0700 (PDT) From: Julian Elischer To: Chuck Robey cc: FreeBSD-scsi@FreeBSD.ORG Subject: Re: scsi messages In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't know about this.. it's supposed to be a 'software firmeware rev' or similar, however I'm sure that it's 'Manufacturer specific' so they are really within their rights to include 'configuration' if they want to. On Sun, 3 May 1998, Chuck Robey wrote: > I'm trying to get another new scsi disk working, and something that I've > noticed in the past is puzzling me. The name of the drive, reported via > the scsi bus, changes if I change the interface (such as changing the > termination). The part that changes is a number at the end, something > I've always seen as a 4 digit number. I don't know if it's restricted > to be a 4 digit number, but values like 0512 or 0172 are reported, and > these change. Does anyone know if there is any intelligence to be > gleaned from this? > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (NetBSD). > ----------------------------+----------------------------------------------- > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 3 13:05:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17307 for freebsd-scsi-outgoing; Sun, 3 May 1998 13:05:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17297 for ; Sun, 3 May 1998 13:05:47 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id PAA12548; Sun, 3 May 1998 15:04:06 -0400 (EDT) Date: Sun, 3 May 1998 15:04:06 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: Julian Elischer cc: FreeBSD-scsi@FreeBSD.ORG Subject: Re: scsi messages In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 3 May 1998, Julian Elischer wrote: > I don't know about this.. it's supposed to be a 'software firmeware rev' > or similar, however I'm sure that it's 'Manufacturer specific' so > they are really within their rights to include 'configuration' > if they want to. > I now have experience with 3 different drives that change that number depending on the state of the drive, so I was curious. Maybe I should write to the drive manufacturer. If I get any info, I'll pass it along. BTW, that was 3 different drives by 3 different mfg's. > > On Sun, 3 May 1998, Chuck Robey wrote: > > > I'm trying to get another new scsi disk working, and something that I've > > noticed in the past is puzzling me. The name of the drive, reported via > > the scsi bus, changes if I change the interface (such as changing the > > termination). The part that changes is a number at the end, something > > I've always seen as a 4 digit number. I don't know if it's restricted > > to be a 4 digit number, but values like 0512 or 0172 are reported, and > > these change. Does anyone know if there is any intelligence to be > > gleaned from this? > > > > ----------------------------+----------------------------------------------- > > Chuck Robey | Interests include any kind of voice or data > > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > > 213 Lakeside Drive Apt T-1 | > > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > > (301) 220-2114 | and jaunt (NetBSD). > > ----------------------------+----------------------------------------------- > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 4 23:52:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06634 for freebsd-scsi-outgoing; Mon, 4 May 1998 23:52:19 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06629 for ; Mon, 4 May 1998 23:52:15 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA06214 for freebsd-scsi@FreeBSD.org; Tue, 5 May 1998 08:52:10 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id IAA09907; Tue, 5 May 1998 08:50:31 +0200 (MET DST) Message-ID: <19980505085031.35826@uriah.heep.sax.de> Date: Tue, 5 May 1998 08:50:31 +0200 From: J Wunsch To: FreeBSD SCSI list Subject: SDR GEM200 Reply-To: Joerg Wunsch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anybody ever seen device? It pops up in a vendor PC (Siemens-Nixdorf) on a wide bus at ID 8. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 5 06:54:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18929 for freebsd-scsi-outgoing; Tue, 5 May 1998 06:54:33 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (root@[209.54.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18921 for ; Tue, 5 May 1998 06:54:29 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral-gw (mjacob@gw100.feral.com [192.67.166.129]) by feral.com (8.8.6/8.8.6) with SMTP id GAA15635; Tue, 5 May 1998 06:52:22 -0700 Message-ID: <354F1996.85FA020@feral.com> Date: Tue, 05 May 1998 06:52:22 -0700 From: Matthew Jacob Organization: Feral Software X-Mailer: Mozilla 3.04 (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: Joerg Wunsch CC: FreeBSD SCSI list Subject: Re: SDR GEM200 References: <19980505085031.35826@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ummm- it might be a SAF-TE device (environmental sensing). Does it say what type it is? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 5 09:51:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18926 for freebsd-scsi-outgoing; Tue, 5 May 1998 09:51:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nlanr.net (oceana.sdsc.edu [132.249.40.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18921 for ; Tue, 5 May 1998 09:51:28 -0700 (PDT) (envelope-from jambi@nlanr.net) Received: from localhost (jambi@localhost) by nlanr.net (8.8.6/8.8.6) with SMTP id JAA23633; Tue, 5 May 1998 09:51:02 -0700 (PDT) Date: Tue, 5 May 1998 09:51:01 -0700 (PDT) From: Jambi Reply-To: Jambi To: Matthew Jacob cc: Joerg Wunsch , FreeBSD SCSI list Subject: scsi benchmarx In-Reply-To: <354F1996.85FA020@feral.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey all, just wanted to point ppl out to a site we have put together about scsi benchmarx. these are benchmarx which are very specific for our needs (continuous write of big chunx to disk). check it out at http://moat.nlanr.net/Dskwtst/ _______________________________________________ Jambi Ganbar | (619) 8220938 | jambi@nlanr.net San Diego SuperComputer Center ________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 5 09:51:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18990 for freebsd-scsi-outgoing; Tue, 5 May 1998 09:51:51 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA18980 for ; Tue, 5 May 1998 09:51:48 -0700 (PDT) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org [205.179.79.65] by phoenix.volant.org with smtp (Exim 1.62 #1) id 0yWkwT-0000SO-00; Tue, 5 May 1998 09:51:46 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id JAA27948; Tue, 5 May 1998 09:49:57 -0700 Date: Tue, 5 May 1998 09:49:57 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: 'Vendor Specific' message on SEAGATE ST15230N 0168 To: freebsd-scsi@FreeBSD.ORG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Last night one of my machines started spitting out the message: sd1(ncr1:1:0): Vendor Specific asc:80,0 Vendor Specific ASC field replaceable unit: 1 , retries: 2 (I've added a line break after 'field', and the number after 'retries' varies. Occasionally the second line reads ", FAILURE".) The partition mounted from that disk was inaccessable, and I had to re-boot to clear it up. Can anyone on this list tell me what it means and whether there's anything I can do to prevent it? The disk is a Seagate ST15230N 0168. The machine is running FreeBSD 2.2.2. Thanks, -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 5 10:29:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28192 for freebsd-scsi-outgoing; Tue, 5 May 1998 10:29:15 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.artcom.de ([192.76.129.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28179 for ; Tue, 5 May 1998 10:29:10 -0700 (PDT) (envelope-from hans@artcom.de) Received: from transrapid.artcom.de by mail.artcom.de with smtp id m0yWlWG-00000nC; Tue, 5 May 1998 19:28:44 +0200 (MEST) Date: Tue, 5 May 1998 19:28:44 +0200 (MEST) From: Hans Huebner To: freebsd-scsi@FreeBSD.ORG Subject: ch.c: CHIOGSTATUS is broken - How should I fix it? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello there, today I moved our Q47 DLT robot from an SGI to a FreeBSD we intend to dedicate to backups. The Q47 talks SCSI-2, thus I assumed that the ch driver included with FreeBSD should do fine to control the thing. Unfortunatly, the 'chio status' command did not work. I tracked the problem down to a bug in the driver - The SCSI_DATA_IN flag in the scsi_scsi_cmd call is missing, and as such the driver is unable to transfer the status information from the robot. This was easy to fix, of course. As our DLT robot has a barcode reader, I now intend to add a way to read the complete status information including the barcode label information from the robot. Currently, only a restricted set of flags can be read through the ch driver into the user mode application. This raises the question whether I should actually add a new ioctl (say CHIOGSTATUSEXT) to the ch driver or change the current meaning of the CHIOGSTATUS call to return complete status information to the calling application. The first option would be transparent to binaries making use of the current ch interface, but it would add another ioctl which does behave similar to CHIOGSTATUS, only better. The second option could be implemented with source-level compatibility, requiring a recompile for applications which use the current interface, but it would also keep the ch driver free from redundancy. Given that most FreeBSD users use only software they have the source for, I'd rather change CHIOSTATUS to be smarter. This will only affect a few, if any, users of the ch driver since CHIOCSTATUS is currently broken anyhow. By the way: If anyone volunteers to commit the updated ch driver, I'd promise a manual page update for ch(4) as well ;) Opinions, anyone? -Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 5 13:39:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01980 for freebsd-scsi-outgoing; Tue, 5 May 1998 13:39:43 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01965 for ; Tue, 5 May 1998 13:39:41 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id OAA15238; Tue, 5 May 1998 14:39:18 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199805052039.OAA15238@panzer.plutotech.com> Subject: Re: ch.c: CHIOGSTATUS is broken - How should I fix it? In-Reply-To: from Hans Huebner at "May 5, 98 07:28:44 pm" To: hans@artcom.de (Hans Huebner) Date: Tue, 5 May 1998 14:39:18 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hans Huebner wrote... > today I moved our Q47 DLT robot from an SGI to a FreeBSD we intend to > dedicate to backups. The Q47 talks SCSI-2, thus I assumed that the ch > driver included with FreeBSD should do fine to control the thing. > Unfortunatly, the 'chio status' command did not work. I tracked the > problem down to a bug in the driver - The SCSI_DATA_IN flag in the > scsi_scsi_cmd call is missing, and as such the driver is unable to > transfer the status information from the robot. This was easy to fix, of > course. > > As our DLT robot has a barcode reader, I now intend to add a way to read > the complete status information including the barcode label information > from the robot. Currently, only a restricted set of flags can be read > through the ch driver into the user mode application. > > This raises the question whether I should actually add a new ioctl (say > CHIOGSTATUSEXT) to the ch driver or change the current meaning of the > CHIOGSTATUS call to return complete status information to the calling > application. > > The first option would be transparent to binaries making use of the > current ch interface, but it would add another ioctl which does behave > similar to CHIOGSTATUS, only better. The second option could be > implemented with source-level compatibility, requiring a recompile for > applications which use the current interface, but it would also keep the > ch driver free from redundancy. > > Given that most FreeBSD users use only software they have the source for, > I'd rather change CHIOSTATUS to be smarter. This will only affect a few, > if any, users of the ch driver since CHIOCSTATUS is currently broken > anyhow. > > By the way: If anyone volunteers to commit the updated ch driver, I'd > promise a manual page update for ch(4) as well ;) > > Opinions, anyone? Well, no one else has spoken up, so I will. :) IMO, you should change the CHIOGSTATUS ioctl to return all the relevant information. If folks update their kernels, they'd better update their userland binaries as well. I just ported the NetBSD ch(4) driver to CAM a few weeks ago. It will be in the next CAM snapshot. The FreeBSD changer driver (the one in -current) is basically an older version of the same driver. I would be interested to see your changes to display volume tags; I think they would be useful, and I'd like to add them to the CAM changer driver. If you want to implement your changes under CAM, I can give you the CAM changer driver and the chio changes in patch form against the last snapshot. Or, if you want, send me private email and I can give you access to the CAM source repository. For information on CAM, see: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/README or ftp://ftp.kdm.org/pub/FreeBSD/cam/README If you'd rather put your changer fixes in -current, I'm still interested but I can't commit them for you. (I'm not a committer.) I'm sure someone else would be willing to do it, though. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 5 14:39:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17667 for freebsd-scsi-outgoing; Tue, 5 May 1998 14:39:06 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (mjacob@[209.54.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17647 for ; Tue, 5 May 1998 14:38:56 -0700 (PDT) (envelope-from mjacob@feral.com) Received: (from mjacob@localhost) by feral.com (8.8.6/8.8.6) id OAA16908; Tue, 5 May 1998 14:38:30 -0700 Date: Tue, 5 May 1998 14:38:30 -0700 From: Matthew Jacob Message-Id: <199805052138.OAA16908@feral.com> To: hans@artcom.de, ken@plutotech.com Subject: Re: ch.c: CHIOGSTATUS is broken - How should I fix it? Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Umm... do a OCHIOSTATUS call that preserves the old CHIOGSTATUS binary compatibility. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 5 15:10:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23189 for freebsd-scsi-outgoing; Tue, 5 May 1998 15:10:33 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23163 for ; Tue, 5 May 1998 15:10:27 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA24777; Tue, 5 May 1998 15:03:18 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd024770; Tue May 5 22:03:17 1998 Message-ID: <354F8C9F.794BDF32@whistle.com> Date: Tue, 05 May 1998 15:03:11 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Hans Huebner CC: freebsd-scsi@FreeBSD.ORG Subject: Re: ch.c: CHIOGSTATUS is broken - How should I fix it? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hans Huebner wrote: > > Hello there, > > today I moved our Q47 DLT robot from an SGI to a FreeBSD we intend to > dedicate to backups. The Q47 talks SCSI-2, thus I assumed that the ch > driver included with FreeBSD should do fine to control the thing. > Unfortunatly, the 'chio status' command did not work. I tracked the > problem down to a bug in the driver - The SCSI_DATA_IN flag in the > scsi_scsi_cmd call is missing, and as such the driver is unable to > transfer the status information from the robot. This was easy to fix, of > course. > > As our DLT robot has a barcode reader, I now intend to add a way to read > the complete status information including the barcode label information > from the robot. Currently, only a restricted set of flags can be read > through the ch driver into the user mode application. > > This raises the question whether I should actually add a new ioctl (say > CHIOGSTATUSEXT) to the ch driver or change the current meaning of the > CHIOGSTATUS call to return complete status information to the calling > application. > > The first option would be transparent to binaries making use of the > current ch interface, but it would add another ioctl which does behave > similar to CHIOGSTATUS, only better. The second option could be > implemented with source-level compatibility, requiring a recompile for > applications which use the current interface, but it would also keep the > ch driver free from redundancy. > > Given that most FreeBSD users use only software they have the source for, > I'd rather change CHIOSTATUS to be smarter. This will only affect a few, > if any, users of the ch driver since CHIOCSTATUS is currently broken > anyhow. > > By the way: If anyone volunteers to commit the updated ch driver, I'd > promise a manual page update for ch(4) as well ;) > > Opinions, anyone? so few people have these devices that anyone who has one is encouraged to submit patches and fixes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 6 09:42:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27056 for freebsd-scsi-outgoing; Wed, 6 May 1998 09:42:23 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rm-rstar.sfu.ca (root@rm-rstar.sfu.ca [142.58.120.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27051 for ; Wed, 6 May 1998 09:42:19 -0700 (PDT) (envelope-from mcquiggi@sfu.ca) Received: from kmcquiggin.teleconsult.com ([134.87.180.44]) by rm-rstar.sfu.ca (8.8.7/8.8.7/SFU-4.0H) with SMTP id JAA09138 for ; Wed, 6 May 1998 09:42:18 -0700 (PDT) Message-Id: <3.0.5.32.19980506094028.007b1780@mail.sfu.ca> X-Sender: mcquiggi@mail.sfu.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 06 May 1998 09:40:28 -0700 To: freebsd-scsi@FreeBSD.ORG From: Kevin McQuiggin Subject: Problem with Wangtek 5150ES SCSI Tape Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >X-Sender: mcquiggi@ferrari.sfu.ca >X-Mailer: Windows Eudora Light Version 3.0.1 (32) >Date: Tue, 05 May 1998 22:33:05 -0700 >To: questions@FreeBSD.ORG >From: Kevin McQuiggin >Subject: Problem with Wangtek 5150ES SCSI Tape >Sender: owner-freebsd-questions@FreeBSD.ORG >X-Loop: FreeBSD.ORG > >Hi: > >I'm having a problem with my new (well new to me) SCSI tape. My tape drive >is as follows: > >(from dmesg:) > >(bt0:5:0): "WANGTEK 5150ES SCSI ES41 B170" type 1 removable SCSI 1 >st0(bt0:5:0): Sequential-Access density code 0x5, 512-byte blocks, >write-enable > >or if empty: > >(bt0:5:0): "WANGTEK 5150ES SCSI ES41 B170" type 1 removable SCSI 1 >st0(bt0:5:0): Sequential-Access density code 0x10, drive empty > >and when I try to write to the drive I observe: > ># mt status >Present Mode: Density = X3.136-1986 Blocksize = 512 bytes >---------available modes--------- >Mode 0: Density = 0x00 Blocksize variable >Mode 1: Density = X3.136-1986 Blocksize = 512 bytes >Mode 2: Density = X3.39-1986 Blocksize variable >Mode 3: Density = X3.54-1986 Blocksize variable ># dd if=/kernel of=/dev/rst0 >dd: /dev/rst0: Invalid argument >1+0 records in >0+0 records out >0 bytes transferred in 0.016702 secs (0 bytes/sec) ># tar cvf /dev/rst0 /usr/sbin >tar: Removing leading / from absolute path names in the archive. >usr/sbin/ >usr/sbin/uuchk >tar: can't write to /dev/rst0 : Invalid argument ># > > >and this is generated on the console: > >st0(bt0:5:0): ILLEGAL REQUEST csi:0,8,0,0 >st0(bt0:5:0): ILLEGAL REQUEST csi:0,8,0,0 >st0(bt0:5:0): ILLEGAL REQUEST csi:0,8,0,0 >st0(bt0:5:0): ILLEGAL REQUEST csi:0,8,0,0 >st0(bt0:5:0): ILLEGAL REQUEST csi:0,8,0,0 >st0(bt0:5:0): ILLEGAL REQUEST csi:0,8,0,0 > > >But mt erase seems to work. At least the tape runs for quite awhile. > >My question: why is this happening? Could it be a media problem? The tapes >were previously used with a lower density Wangtek (and Archive) drive on a >Sun 3/60. > >I have tried using mt density to reset the density to different values, but >this makes no difference. > >Any assistance appreciated. I've already searched the FAQ, Handbook, and >mailing list archives. > >Kevin > > >--- >Kevin McQuiggin VE7ZD >mcquiggi@sfu.ca > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 6 18:23:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05459 for freebsd-scsi-outgoing; Wed, 6 May 1998 18:23:50 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from roma.coe.ufrj.br (jonny@roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05425 for ; Wed, 6 May 1998 18:23:27 -0700 (PDT) (envelope-from jonny@coe.ufrj.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id WAA04644 for scsi@freebsd.org; Wed, 6 May 1998 22:23:25 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199805070123.WAA04644@roma.coe.ufrj.br> Subject: CD locked on boot ? To: scsi@FreeBSD.ORG Date: Wed, 6 May 1998 22:23:25 -0300 (EST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Maybe the folks in this list may help me one way or another. I don't know why, my CDROM decided not to accept the user command of manual eject. In case it matters, it's a TEAC CD56-S (6X), SCSI of course. The controler is an AHA1542CF, and also controls an internal ZIP drive. The BIOS is hardware enabled, but software disabled, as my hard disks are IDE (el cheapo). Playing a little with the DOS ASPI utilities, I found that the drive is indeed locked. (Why ???). Well, at DOS I just had to put the ASPI command to unlock the drive and everything get ok. I was trying to do the same in FreeBSD, using the CDIO ioctls, but open(2) returns ENXIO, which means "No disc in drive". Ok, there's no disc in drive, but it's locked, and I want to unlock in order to put a disc inside. It seems to be a chicken and egg problem. :) I would try the scsi commands if I knew then. Even better, I would love to know why this CD starts locked after every boot. Does anybody have a suggestion ? TIA, Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 ( Job ) jonny@coppe.ufrj.br M.Sc. Student Electrical Engineering Universidade Federal do Rio de Janeiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 6 23:21:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23289 for freebsd-scsi-outgoing; Wed, 6 May 1998 23:21:58 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23277 for ; Wed, 6 May 1998 23:21:49 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA12276 for freebsd-scsi@FreeBSD.ORG; Thu, 7 May 1998 08:21:49 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id HAA17630; Thu, 7 May 1998 07:56:06 +0200 (MET DST) Message-ID: <19980507075605.01312@uriah.heep.sax.de> Date: Thu, 7 May 1998 07:56:05 +0200 From: J Wunsch To: FreeBSD SCSI list Subject: Re: SDR GEM200 Reply-To: Joerg Wunsch References: <19980505085031.35826@uriah.heep.sax.de> <354F1996.85FA020@feral.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <354F1996.85FA020@feral.com>; from Matthew Jacob on Tue, May 05, 1998 at 06:52:22AM -0700 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Matthew Jacob wrote: > Ummm- it might be a SAF-TE device (environmental sensing). That might be quite possible. > Does it say what type it is? Type 3 `Processor target device'. I can successfully configure the pt(4) driver for it, but can't do anything, not even view some mode page. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 6 23:23:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23530 for freebsd-scsi-outgoing; Wed, 6 May 1998 23:23:41 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23523 for ; Wed, 6 May 1998 23:23:37 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA12292; Thu, 7 May 1998 08:23:17 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id IAA17760; Thu, 7 May 1998 08:20:33 +0200 (MET DST) Message-ID: <19980507082033.57406@uriah.heep.sax.de> Date: Thu, 7 May 1998 08:20:33 +0200 From: J Wunsch To: Joao Carlos Mendes Luis Cc: scsi@FreeBSD.ORG Subject: Re: CD locked on boot ? Reply-To: Joerg Wunsch References: <199805070123.WAA04644@roma.coe.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199805070123.WAA04644@roma.coe.ufrj.br>; from Joao Carlos Mendes Luis on Wed, May 06, 1998 at 10:23:25PM -0300 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Joao Carlos Mendes Luis wrote: > I would try the scsi commands if I knew then. scsi -f /dev/rcd0.ctl -c "1e 0 0 0 0 0" -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 7 01:06:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05111 for freebsd-scsi-outgoing; Thu, 7 May 1998 01:06:26 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (mjacob@[209.54.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05104 for ; Thu, 7 May 1998 01:06:24 -0700 (PDT) (envelope-from mjacob@feral.com) Received: (from mjacob@localhost) by feral.com (8.8.6/8.8.6) id BAA22380; Thu, 7 May 1998 01:06:02 -0700 Date: Thu, 7 May 1998 01:06:02 -0700 From: Matthew Jacob Message-Id: <199805070806.BAA22380@feral.com> To: j@uriah.heep.sax.de Subject: Re: SDR GEM200 Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >From owner-freebsd-scsi@FreeBSD.ORG Wed May 6 23:46:14 1998 > >As Matthew Jacob wrote: > >> Ummm- it might be a SAF-TE device (environmental sensing). > >That might be quite possible. > >> Does it say what type it is? > >Type 3 `Processor target device'. I can successfully configure the >pt(4) driver for it, but can't do anything, not even view some mode >page. > Ah. Yes. Very likely a SAF-TE device. Funny- I've on my list to port a driver that would include snagging this. Will you do some testing for me? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 7 03:27:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21709 for freebsd-scsi-outgoing; Thu, 7 May 1998 03:27:11 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21704; Thu, 7 May 1998 03:27:08 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id DAA18877; Thu, 7 May 1998 03:24:16 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd018867; Thu May 7 10:24:07 1998 Date: Thu, 7 May 1998 03:24:04 -0700 (PDT) From: Julian Elischer To: current@FreeBSD.ORG cc: scsi@FreeBSD.ORG Subject: SLICE broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Because I origially wrote the scsi code I was under the mistaken impression that I knew what was going on there and today's checkins of sd.c have screwed up if SLICE/DEVFS is defined. backing down to 1.127 should make it work as well as before. 1.128 is definitly bogus. I'm working on it but some things happenned in the scsi code during my absence that are definately done absolutly backwards. (right idea but backwards.) for example one cannot get rid of all the devsw entrypoints even of one doesn't need them any more :-] julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 7 05:37:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07215 for freebsd-scsi-outgoing; Thu, 7 May 1998 05:37:10 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07208; Thu, 7 May 1998 05:37:05 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id FAA20692; Thu, 7 May 1998 05:33:23 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd020690; Thu May 7 12:33:20 1998 Date: Thu, 7 May 1998 05:33:18 -0700 (PDT) From: Julian Elischer To: current@FreeBSD.ORG cc: scsi@FreeBSD.ORG Subject: Re: SLICE broken In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To reply to my own mail.. I've (I think) made this work (I'm typing on such a kernel) at least in the common case. If you are really worried about system integrety (then what are you doing on -current :-) then it might be an idea to not use SLICE/DEVFS for a few days till I manage to go through all the code paths again just to be sure. I think I've just added "fix SCSI code" back onto my list, at least till we see CAM more completely deployed. julian On Thu, 7 May 1998, Julian Elischer wrote: > > Because I origially wrote the scsi code I was under the mistaken > impression that I knew what was going on there and today's checkins > of sd.c have screwed up if SLICE/DEVFS is defined. > > backing down to 1.127 should make it work as well as before. > 1.128 is definitly bogus. I'm working on it but > some things happenned in the scsi code during my absence that are > definately done absolutly backwards. (right idea but backwards.) > for example one cannot get rid of all the devsw entrypoints > even of one doesn't need them any more :-] > > julian > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 7 22:51:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26767 for freebsd-scsi-outgoing; Thu, 7 May 1998 22:51:42 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26759 for ; Thu, 7 May 1998 22:51:39 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id HAA29777 for freebsd-scsi@FreeBSD.ORG; Fri, 8 May 1998 07:51:27 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id HAA21045; Fri, 8 May 1998 07:36:17 +0200 (MET DST) Message-ID: <19980508073617.01742@uriah.heep.sax.de> Date: Fri, 8 May 1998 07:36:17 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: SDR GEM200 Reply-To: Joerg Wunsch References: <199805070806.BAA22380@feral.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199805070806.BAA22380@feral.com>; from Matthew Jacob on Thu, May 07, 1998 at 01:06:02AM -0700 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Matthew Jacob wrote: > Ah. Yes. Very likely a SAF-TE device. Funny- I've on my list to > port a driver that would include snagging this. Will you do > some testing for me? Sorry, probably not possible. The machine is a customer's one, and will become a firewall/proxy/Internet server host. I could try to convince the guy there to do some testing on another machine of this class however, provided the tests would fit onto a boot floppy. (As i understand it, they usually (ab)use these parts for WinNT.) The box will be around in our company for another couple of days, in case i should try something for you so far. A pt(4) driver is configured already (mainly since i've been sick of the `Unknown' boot message :). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 8 09:29:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17010 for freebsd-scsi-outgoing; Fri, 8 May 1998 09:29:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from Masters.leader-group.com (masters.leader-group.com [12.10.238.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17005 for ; Fri, 8 May 1998 09:29:10 -0700 (PDT) (envelope-from bmccloskey@leader-group.com) Received: from leader-group.com ([172.20.149.128]) by Masters.leader-group.com (Netscape Messaging Server 3.0) with ESMTP id AAA23388 for ; Fri, 8 May 1998 10:25:49 -0600 Message-ID: <355331E8.CEC7328B@leader-group.com> Date: Fri, 08 May 1998 10:25:12 -0600 From: "Brian McCloskey" Organization: Leader Group X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Latest 3.0 SNAPSHOT and CAM boot Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I've been running into problems attempting to get FreeBSD running on my machine. I have an Adaptec AIC-7895 controller, so I've been using the CAM boot floppy image to install the latest 3.0 Snapshot. I have two problems I was wondering if anybody could help me to resolve. The first one isn't prohibiting me from installing, but it is very wierd and seems out of place. When I boot from the floppy, everything is fine, until the system begins the install. I am installing from a DOS partition. When I go in to set the partitions, I have a root (/) partition of 50MB, a var (/var) partition of 100MB, a swap of 256MB, and the rest dedicated to /usr. Even if I have the newfs toggle set to N, the sysinstall still wants to newfs the /var and /usr partitions (at this point /mnt2/dev/da0s2e and /mnt2/dev/da0s2f respectively), and never touches the root. Even if I do toggle the newfs to Y on all partitions, it still won't newfs the root partition (which should be /mnt2/dev/da0s2a). Because of this, the install fails due to the inability to write to /etc. So, I switch to the emergency holographic shell and newfs it manually. If I then run the fixit floppy, I can see what is mounted. The following appears... / /dev/da0a /mnt /mnt2/dev/da0s2e /mnt/var /mnt2/dev/da0s2f /mnt/usr /dev/fd0 /mnt2 Is there a reason why the supposed root is not being mounted as /mnt2/dev/da0s2a? Also, once I newfs, and manually create the /etc directory, it copies all the files after I commit, and then crashes with DEBUG: Signal 10 caught. This is bad! I think it's Signal 10, but it states 10, and that I need to contact freebsd.org. Anybody have any insight as to what is going on? I'm also assuming that the latest CAM support has been put into the latest 3.0 snapshot. Thanks for any help, Brian -- _________________________________________________ Brian McCloskey | Leader Group Consultant | 5200 DTC Parkway ph: 303-773-9700 | Suite 500 fax: 303-773-9610 | Englewood, CO 80111 ____________________________|____________________ http://www.leader-group.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message