Date: Wed, 22 Jul 1998 09:06:46 -0400 From: WilsonFC@RASG.WPAFB.AF.MIL To: questions@FreeBSD.ORG Subject: FW: FreeBSD 2.2.6 Message-ID: <5421AD9121BBD1119A3A00A0C92683560EF579@ramail.ra.wpafb.af.mil>
next in thread | raw e-mail | index | archive | help
Help! I am having a problem installing version 2.2.6 from the Walnut Creek CD-ROM and was referred to you as a possible souce of assistance. Briefly the problem is that when the SCSI adapter is polling for attached devices an "invalid message error" results in an aborted command on the intended target disk. I tried version 2.1 and it identifies all of the attached devices. Most of the clues I have collected are in the following dialog. If there is additional information you can use I will try to obtain it. > -----Original Message----- > From: Phil Jenvey [SMTP:support@cdrom.com] > Sent: Tuesday, July 21, 1998 2:36 PM > To: Wilson, Fred C. > Subject: RE: FreeBSD 2.2.6 > > Could you email this problem to questions@freebsd.org? This is a mailing > list > answered by the FreeBSD developers. They should have some ideas on what > the > problem is. > > On Tue, 21 Jul 1998 WilsonFC@RASG.WPAFB.AF.MIL wrote: > > > This is pretty much the information I collected. When it is all said and > > done it appears that there are two things of interest. > > > > First, why would three out of four devices be corrrectly identified? One > > would assume that the same code is applied to each unit in sequence so > they > > should all work or none. > > > > Second, something is different about FreeBSD 2.2.6. I don't know if it > is > > broke, doing a new test, or being less error tolerant than older > systems. > > Note that FreeBSD 2.1, OS/2, Windows NT 4.0, DR/MS-DOS (actually the > Adaptec > > ASPI driver), and the adapter BIOS can all poll the adapter and identify > all > > the devices. > > > > Since this is a PCI adapter about the only thing that is user settable > is > > the SCSI ID. The hardware has been running without change for about two > > years which should indicate no major hardware conflicts. > > > > The support routines on the adapter report the following information: > > Bus Connections > > 0 MICROP 4345WS > > 1 MICROP 2217-15MZ1001905 > > 3 PLEXTOR CD-ROM PX-12CS > > 4 ARCHIVE VIPER 2525 25462 > > 7 AHA-2940 Ultra/Ultra W > > > > All devices are enabled for "Sync Negotiation" > > All devices are enabled for "Enable Disconnection" > > All devices are enabled for "Wide Negotiation" > > > > Units 0,1,3,4 set for "Include in BIOS scan" > > None are set for "Start Unit" command > > PnP Scan Support is disabled > > Reset SCSI Bus at IC Initialization is enabled > > Host Adapter BIOS is enabled > > Support Removable Disks under BIOS as Fixed Disks is set for "Boot Only" > > Extended BIOS Translation for DOS drives > 1GByte is enabled > > Multiple LUN support is disabled > > BIOS support for Bootable CD-ROM is enabled > > BIOS support for Int13 Extensions is enabled > > Support for Ultra SCSI speed is enabled > > > > This part goes by fairly quickly but this is the jist of the BIOS scan > after > > system reset: > > Adaptec 2940 Ultra/Ultra W BIOS V1.25 > > (c) 1996 > > > > Press <cntl><A> for SCSISelect(TM) Utility > > > > SCSI ID:LUN NUMBER #:# 0:0 MICROP 4345WS - Drive > > C:(80h) > > SCSI ID:LUN NUMBER #:# 1:0 MICROP 2217-15MZ1001905 - Drive > > D:(81h) > > SCSI ID:LUN NUMBER #:# 3:0 PLEXTOR CD-ROM PX-12CS > > SCSI ID:LUN NUMBER #:# 4:0 ARCHIVE VIPER 2525 25462 > > > > SCSI BIOS Installed Successfully > > > > This is the good stuff: > > ahc0:<Adaptec 2940 Ultra SCSI host adapter> rev 0 int a IRQ 14 on > pci0:10:0 > > ahc0:aic7880 Wide channel, SCSI id=7, 16 SCBs > > ahc0: waiting for scsi devices to settle > > (ahc0:0:0): "MICROP 4345WS P429" type 0 fixed SCSI 2 > > sd0(ahc0:0:0):Direct-Access 4340MB (8890029 512 byte sectors) > > (ahc0:1:0): ABORTED COMMAND asc:49,0 Invalid message error > > (ahc0:3:0): "PLEXTOR CD-ROM PX-12CS 1.01" type 5 removable SCSI 2 > > cd0(ahc0:3:0): CD-ROM cd present [323780 x 2048 byte records] > > ahc0:A:4: refuses WIDE negotiation. Using 8bit transfers > > ahc0:A:4: refuses synchronous negotiation. Using asynchronous transfers > > (ahc0:4:0) "ARCHIVE VIPER 2525 25462 -007" type 1 removable SCSI 1 > > st0(ahc0:4:0) Sequential-Access density code 0x0, drive empty > > > > The adapter has two cables, one for wide devices and one for normal > devices. > > The only thing on the wide cable is the 4345. The rest of the devices > are on > > the regular SCSI cable. > > > > > -----Original Message----- > > > From: Phil Jenvey [SMTP:support@cdrom.com] > > > Sent: Monday, July 20, 1998 12:34 PM > > > To: Wilson, Fred C. > > > Subject: Re: FreeBSD 2.2.6 > > > > > > It could be a problem with your SCSI controller. Make sure the SCSI > > > controller > > > is set correctly, as in IRQ, dma, and SCSI id settings. Then email me > the > > > output of all the SCSI messages. > > > > > > On Mon, 20 Jul 1998 WilsonFC@RASG.WPAFB.AF.MIL wrote: > > > > > > > While attempting to install FreeBSD 2.2.6 I encountered a problem. > > > > > > > > I have a Micropolis 4345WS (about a 4.4Gb Ultra Wide SCSI disk) at > SCSI > > > > address 0 and a 2217(about a 1.7 Gb fast SCSI disk) at SCSI address > 1 > > > > hanging off of an Adaptec 2940. > > > > > > > > The target for the installation is the 2217. > > > > > > > > During the initial probe of all the devices on the system I get the > > > > following message: > > > > > > > > "(ahc0:1:0): ABORTED COMMAND, asc:49,0 Invalid message error" > > > > > > > > while attempting to identify the 2217 disk. > > > > > > > > The devices before and after (4345, CD-ROM and Viper tape) are > properly > > > > recoginzed. > > > > > > > > I get this when booting from the CD-ROM and if I copy the CD-ROM to > my > > > DOS > > > > C: drive and run install from there after booting from a basic (no > > > memory > > > > manager) floppy disk. > > > > > > > > The initial boot messages go by so fast that I could not get all of > the > > > > information like load path but after several attempts I got. > > > > Version 2.2.6 Release #0 Wed Mar 26 .... > > > > I couldn't get the load address etc. > > > > > > > > Since I had used this disk on a previous computer with an Adaptec > 1542 > > > > adapter I attempted to load a minimal FreeBSD 2.1 system to see if > it > > > would > > > > recognize the disk. I am not sure of the exact version (I think it > was > > > 2.1.4 > > > > but can get it if it is important) but 2.1.? manages to identify the > > > disk > > > > with no problem. OS/2 3.0 [Wilson, Fred C.] &4.0, Windows NT 4.0 > and MS-DOS 6.22 also work OK. > > > > > > > > Any ideas? > > > > > > > > > > -- > > > Phil Jenvey > > > Technical Support > > > Walnut Creek CDROM > > > > -- > Phil Jenvey > Technical Support > Walnut Creek CDROM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5421AD9121BBD1119A3A00A0C92683560EF579>