From owner-freebsd-hardware Sun Nov 3 06:04:04 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA24974 for hardware-outgoing; Sun, 3 Nov 1996 06:04:04 -0800 (PST) Received: from itp.ac.ru (itp.ac.ru [193.233.32.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA24957 for ; Sun, 3 Nov 1996 06:03:55 -0800 (PST) Received: (ks@localhost) by itp.ac.ru (8.6.11/8.6.5) id RAA05007 for hardware@freebsd.org; Sun, 3 Nov 1996 17:12:06 +0300 Date: Sun, 3 Nov 1996 17:12:06 +0300 From: "Sergey S. Kosyakov" Message-Id: <199611031412.RAA05007@itp.ac.ru> To: hardware@freebsd.org Subject: SCSI CDROM Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After "eject" command my CD ejected, but SCSI controlled dies: ncr0: restart (ncr dead ?). ncr0:0: ERROR (80:4) (8-0-0) (0/13) @ (420:878b0000). script cmd = 72060000 reg: da 00 80 13 47 00 06 1f 31 08 06 00 80 00 0a 02. cd0(ncr0:6:0): COMMAND FAILED (ff ff) @f14b6c00. ncr0:6: ERROR (80:41) (e-aa-0) (0/13) @ (438:1e000000). script cmd = 60000008 reg: da 10 80 13 47 00 06 1f 06 0e 06 aa 80 00 0a 00. ncr0: restart (fatal error). cd0(ncr0:6:0): COMMAND FAILED (9 ff) @f14b6c00. ncr0: restart (ncr dead ?). And only reboot can reanime the controller. I use NCR PCI under FreeBSD-2.2-960801-SNAP on P-120 Triton box. Does anybody know why NCR die off ? Regards, Sergey. From owner-freebsd-hardware Sun Nov 3 08:21:30 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA03084 for hardware-outgoing; Sun, 3 Nov 1996 08:21:30 -0800 (PST) Received: from In-Net.inba.fr (root@arthur.inba.fr [194.51.120.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA03076 for ; Sun, 3 Nov 1996 08:21:23 -0800 (PST) Received: from uther.inba.fr (uther.inba.fr [194.51.120.62]) by In-Net.inba.fr (8.6.12/8.6.9) with SMTP id RAA13294 for ; Sun, 3 Nov 1996 17:21:10 +0100 Message-Id: <1.5.4.16.19961103172720.22a7156a@mail.inba.fr> X-Sender: psc@mail.inba.fr X-Mailer: Windows Eudora Light Version 1.5.4 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 03 Nov 1996 18:27:20 +0100 To: freebsd-hardware@FreeBSD.ORG From: Philippe SCHACK Subject: Micronics MotherBoard Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, I have installed FreeBSD with a P75 on a Micronics D5CUB PCI/ISA card and have the following problems: After the install (wich runs ok) when a try to acces to the 3'5 floppy, the system hangs without any messages. I only have to reset the system. I have installed a Adaptec SCSI AHA-1542B card with a TANDBERG TDC-3800 Streamer . When i boot on the BOOT FLOPPY, the system hangs after displaying a part of the Tandberg TDC 3800 informations. Does anyone have any information about this ? The same material (Adaptec card floppy) on a 486 DLC card works fine. Thank's P.SCHACK From owner-freebsd-hardware Sun Nov 3 13:52:26 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA29065 for hardware-outgoing; Sun, 3 Nov 1996 13:52:26 -0800 (PST) Received: from persprog.com (persprog.com [204.215.255.203]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA29055 for ; Sun, 3 Nov 1996 13:52:19 -0800 (PST) Received: by persprog.com (8.7.5/4.10) id RAA10589; Sun, 3 Nov 1996 17:04:57 -0500 Received: from dasa(192.2.2.199) by cerberus.ppi.com via smap (V1.3) id sma010587; Sun Nov 3 17:04:30 1996 Received: from DASA/SpoolDir by dasa.ppi.com (Mercury 1.21); 3 Nov 96 17:04:32 +0500 Received: from SpoolDir by DASA (Mercury 1.30); 3 Nov 96 17:04:03 +0500 From: "David Alderman" Organization: Personalized Programming, Inc To: Philippe SCHACK , freebsd-hardware@FreeBSD.ORG Date: Sun, 3 Nov 1996 17:03:58 +0500 Subject: Re: Micronics MotherBoard Priority: normal X-mailer: Pegasus Mail for Windows (v2.42a) Message-ID: <15626E528CA@dasa.ppi.com> Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Philippe SCHACK > I have installed FreeBSD with a P75 on a Micronics D5CUB PCI/ISA card and > have the following problems: > After the install (wich runs ok) when a try to acces to the 3'5 floppy, > the system hangs without any messages. I only have to reset the system. > I have installed a Adaptec SCSI AHA-1542B card with a TANDBERG TDC-3800 > Streamer . When i boot on the BOOT FLOPPY, the system hangs after displaying > a part of the Tandberg TDC 3800 informations. > > Does anyone have any information about this ? > > The same material (Adaptec card floppy) on a 486 DLC card works fine. > I have had problems with the 1542B floppy controller in the past. You might want to try adjusting the bus on/off time for the controller to see if it will work better. You might also want to run the controllers built in DMA test (in the BIOS at some oddball address) although I can't remember if the DMA speed affected the floppy or not. Maybe someone else on the group can elaborate? ====================================== When philosophy conflicts with reality, choose reality. Dave Alderman -- dave@persprog.com ====================================== From owner-freebsd-hardware Sun Nov 3 13:55:18 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA29199 for hardware-outgoing; Sun, 3 Nov 1996 13:55:18 -0800 (PST) Received: from persprog.com (persprog.com [204.215.255.203]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA29192 for ; Sun, 3 Nov 1996 13:55:13 -0800 (PST) Received: by persprog.com (8.7.5/4.10) id QAA10583; Sun, 3 Nov 1996 16:59:56 -0500 Received: from dasa(192.2.2.199) by cerberus.ppi.com via smap (V1.3) id sma010581; Sun Nov 3 16:59:33 1996 Received: from DASA/SpoolDir by dasa.ppi.com (Mercury 1.21); 3 Nov 96 16:59:34 +0500 Received: from SpoolDir by DASA (Mercury 1.30); 3 Nov 96 16:59:25 +0500 From: "David Alderman" Organization: Personalized Programming, Inc To: "Sergey S. Kosyakov" Date: Sun, 3 Nov 1996 16:59:16 +0500 Subject: Re: SCSI CDROM CC: hardware@FreeBSD.ORG Priority: normal X-mailer: Pegasus Mail for Windows (v2.42a) Message-ID: <15613350590@dasa.ppi.com> Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: "Sergey S. Kosyakov" > > After "eject" command my CD ejected, but SCSI controlled dies: > ncr0: restart (ncr dead ?). > > ncr0:0: ERROR (80:4) (8-0-0) (0/13) @ (420:878b0000). > script cmd = 72060000 > reg: da 00 80 13 47 00 06 1f 31 08 06 00 80 00 0a 02. > cd0(ncr0:6:0): COMMAND FAILED (ff ff) @f14b6c00. > ncr0:6: ERROR (80:41) (e-aa-0) (0/13) @ (438:1e000000). > script cmd = 60000008 > reg: da 10 80 13 47 00 06 1f 06 0e 06 aa 80 00 0a 00. > ncr0: restart (fatal error). > cd0(ncr0:6:0): COMMAND FAILED (9 ff) @f14b6c00. > ncr0: restart (ncr dead ?). > > And only reboot can reanime the controller. > I use NCR PCI under FreeBSD-2.2-960801-SNAP on P-120 Triton box. > Does anybody know why NCR die off ? > It's possible that the CDROM drive itself is the culprit. What model CDROM are you using? Perhaps someone on the group will know if this unit is a known rogue. ====================================== When philosophy conflicts with reality, choose reality. Dave Alderman -- dave@persprog.com ====================================== From owner-freebsd-hardware Sun Nov 3 15:26:10 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA11094 for hardware-outgoing; Sun, 3 Nov 1996 15:26:10 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA11074 for ; Sun, 3 Nov 1996 15:25:54 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-18.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA08430 (5.67b/IDA-1.5 for ); Mon, 4 Nov 1996 00:24:26 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.2/8.6.9) id XAA01032; Sun, 3 Nov 1996 23:51:07 +0100 (MET) Message-Id: <199611032251.XAA01032@x14.mi.uni-koeln.de> Date: Sun, 3 Nov 1996 23:51:07 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: ks@itp.ac.ru (Sergey S. Kosyakov) Cc: hardware@freebsd.org Subject: Re: SCSI CDROM In-Reply-To: <199611031412.RAA05007@itp.ac.ru>; from Sergey S. Kosyakov on Nov 3, 1996 17:12:06 +0300 References: <199611031412.RAA05007@itp.ac.ru> X-Mailer: Mutt 0.45 Mime-Version: 1.0 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sergey S. Kosyakov writes: > > After "eject" command my CD ejected, but SCSI controlled dies: > ncr0: restart (ncr dead ?). > > ncr0:0: ERROR (80:4) (8-0-0) (0/13) @ (420:878b0000). This is an unexpected disconnect. Did you eject the CD while the drive was active ? > ncr0:6: ERROR (80:41) (e-aa-0) (0/13) @ (438:1e000000). An SCSI parity error is reported. > And only reboot can reanime the controller. > I use NCR PCI under FreeBSD-2.2-960801-SNAP on P-120 Triton box. > Does anybody know why NCR die off ? Please let me know, what kind of CDROM drive you are using (best if you send me a boot message log). And please give more information about the exact situation that caused this problem: How was the CDROM used, how was the eject initiated ? Regards, STefan From owner-freebsd-hardware Sun Nov 3 16:45:45 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA16898 for hardware-outgoing; Sun, 3 Nov 1996 16:45:45 -0800 (PST) Received: from central.picker.com (central.picker.com [144.54.31.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA16880 for ; Sun, 3 Nov 1996 16:45:28 -0800 (PST) Received: from ct.picker.com by central.picker.com with smtp (Smail3.1.28.1 #3) id m0vKD0U-0004rmC; Sun, 3 Nov 96 19:35 EST Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA19943; Sun, 3 Nov 96 19:32:54 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id TAA15617; Sun, 3 Nov 1996 19:32:42 -0500 From: rhh@ct.picker.com (Randall Hopper) Message-Id: <199611040032.TAA15617@elmer.ct.picker.com> Subject: Re: SoundBlaster 32 PnP To: graham@fgate.flevel.co.uk (Graham Breach) Date: Sun, 3 Nov 1996 19:32:42 -0500 (EST) Cc: hardware@freebsd.org In-Reply-To: <199610311730.RAA04676@fgate.flevel.co.uk> from "Graham Breach" at Oct 31, 96 05:30:27 pm Reply-To: rhh@ct.picker.com Organization: Picker International, CT Division X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Graham Breach: |sb0 not found at 0x220 |sbxvi0 not found |sbmidi0 not found at 0x330 |joy0 at 0x201 on isa |joy0: joystick | |MAKEDEV doesn't have any entries for sb0, sbxvi0 or sbmidi0, so I assumed |you meant the snd* devices. "sh MAKEDEV snd0" should do it, though those exist by default I believe. |Do you have any more suggestions, as this has me a bit stumped... |> > Has anyone got a SoundBlaster 32 PnP to work under FreeBSD? |> > We're using 2.2-CURRENT, and the sb devices are "not found". |> > |> > Graham Breach Someone else posted to the multimedia group recently who was having similar trouble getting an AWE32 PnP to work. I'm running a SoundBlaster 32 non-PnP version without any problems. I think your trouble might be related to the PnP, so if the card supports it, you might disable that and hard-wire the card down to DMAs 5 & 1, and IRQ 7 or 5. A few other things you might check: 1) Possible IRQ/DMA conflict with another card (probably not as none of your devices are being detected), and 2) if you're running a PCI motherboard, do you have IRQ5 (or 7), DMA 1, and DMA 5 reserved for ISA in your BIOS? In case it might help, here are the relevent lines from my kernel config: controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 and here are the relevent boot-up messages: sb0 at 0x220 irq 5 drq 1 on isa sb0: sbxvi0 at 0x0 drq 5 on isa sbxvo0: sbmidi0 at 0x330 on isa opl0 at 0x388 on isa opl0: Randall Hopper rhh@ct.picker.com From owner-freebsd-hardware Sun Nov 3 18:24:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA28386 for hardware-outgoing; Sun, 3 Nov 1996 18:24:24 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA28376 for ; Sun, 3 Nov 1996 18:24:19 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id SAA08391 for ; Sun, 3 Nov 1996 18:24:20 -0800 (PST) To: hardware@freebsd.org Subject: OK, what's the deal with 2940W controllers and internal connectors? Date: Sun, 03 Nov 1996 18:24:20 -0800 Message-ID: <8387.847074260@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just recently had a WIDE drive fall into my lap, so I finally started putting that WIDE connector on my 2940UW controller to good use. While reading the Adaptec controller docs before jumping in, I saw that it very specifically said to use only ONE of the internal connectors, either the WIDE or the narrow, but not both. You could still use the external connector for either kind of drive, but not hook both internal connectors up at once. Well, this made sense to me since it seemed like otherwise you'd have a "Y" configuration in your SCSI bus, and it wasn't clear which devices you'd terminate if you plugged both internal connectors in - each end of the Y, or what? So I hooked all my narrow devices to a 1542 controller I had lying around and life was good again, once I remembered to put BOUNCE_BUFFERS back in for it (feh). Then I was talking to Poul-Henning last night who pooh-pooh'd my foolish conservatism and stated that I could have used both internal connectors on my 2940UW no problem. Since I could use that 1542 as my spare again (which is why I have it), I'd sort of like to know which one of us is correct? :-) Jordan From owner-freebsd-hardware Sun Nov 3 18:42:36 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA00133 for hardware-outgoing; Sun, 3 Nov 1996 18:42:36 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA00127; Sun, 3 Nov 1996 18:42:33 -0800 (PST) Message-Id: <199611040242.SAA00127@freefall.freebsd.org> To: "Jordan K. Hubbard" cc: hardware@freebsd.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-reply-to: Your message of "Sun, 03 Nov 1996 18:24:20 PST." <8387.847074260@time.cdrom.com> Date: Sun, 03 Nov 1996 18:42:33 -0800 From: "Justin T. Gibbs" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Adaptec, you are supposed to use only two or the three connectors on the card. I'm sure the EE members of the crowd can tell you why. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Sun Nov 3 18:58:49 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA01284 for hardware-outgoing; Sun, 3 Nov 1996 18:58:49 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA01278 for ; Sun, 3 Nov 1996 18:58:46 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id SAA09127; Sun, 3 Nov 1996 18:58:46 -0800 (PST) To: "Justin T. Gibbs" cc: hardware@freebsd.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-reply-to: Your message of "Sun, 03 Nov 1996 18:42:33 PST." <199611040242.SAA00127@freefall.freebsd.org> Date: Sun, 03 Nov 1996 18:58:46 -0800 Message-ID: <9124.847076326@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > According to Adaptec, you are supposed to use only two or the three > connectors on the card. I'm sure the EE members of the crowd can > tell you why. I assume you mean "two of the three" above, but that still doesn't quite clarify whether or not it's legitimate to use both internal connectors. In the Adaptec docs, they always show the "2 out of 3" example as involving the external connector. Jordan From owner-freebsd-hardware Sun Nov 3 19:01:39 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA01613 for hardware-outgoing; Sun, 3 Nov 1996 19:01:39 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA01599 for ; Sun, 3 Nov 1996 19:01:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id TAA25248; Sun, 3 Nov 1996 19:00:23 -0800 (PST) Message-Id: <199611040300.TAA25248@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" cc: hardware@freebsd.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-reply-to: Your message of "Sun, 03 Nov 1996 18:24:20 PST." <8387.847074260@time.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 03 Nov 1996 19:00:23 -0800 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I just recently had a WIDE drive fall into my lap, so I finally >started putting that WIDE connector on my 2940UW controller to good >use. While reading the Adaptec controller docs before jumping in, I >saw that it very specifically said to use only ONE of the internal >connectors, either the WIDE or the narrow, but not both. You could >still use the external connector for either kind of drive, but not >hook both internal connectors up at once. Well, this made sense to me >since it seemed like otherwise you'd have a "Y" configuration in your >SCSI bus, and it wasn't clear which devices you'd terminate if you >plugged both internal connectors in - each end of the Y, or what? So >I hooked all my narrow devices to a 1542 controller I had lying around >and life was good again, once I remembered to put BOUNCE_BUFFERS back >in for it (feh). > >Then I was talking to Poul-Henning last night who pooh-pooh'd my >foolish conservatism and stated that I could have used both internal >connectors on my 2940UW no problem. Since I could use that 1542 as my >spare again (which is why I have it), I'd sort of like to know which >one of us is correct? :-) You shouldn't have any trouble if you're only using the internal connectors. There could be a problem with mixing the use of the external connector and the internal connector that is on the same SCSI bus. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Sun Nov 3 19:04:52 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA01854 for hardware-outgoing; Sun, 3 Nov 1996 19:04:52 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA01843; Sun, 3 Nov 1996 19:04:48 -0800 (PST) Message-Id: <199611040304.TAA01843@freefall.freebsd.org> To: "Jordan K. Hubbard" cc: hardware@freebsd.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-reply-to: Your message of "Sun, 03 Nov 1996 18:58:46 PST." <9124.847076326@time.cdrom.com> Date: Sun, 03 Nov 1996 19:04:48 -0800 From: "Justin T. Gibbs" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I assume you mean "two of the three" above, but that still doesn't >quite clarify whether or not it's legitimate to use both internal >connectors. In the Adaptec docs, they always show the "2 out of 3" >example as involving the external connector. > > Jordan I meant two out of the three which includes using both of the internal conectors with the controller termination set to high byte on, low byte off. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Sun Nov 3 20:18:50 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA08496 for hardware-outgoing; Sun, 3 Nov 1996 20:18:50 -0800 (PST) Received: from zen.nash.org (nash.pr.mcs.net [204.95.47.72]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA08433 for ; Sun, 3 Nov 1996 20:18:20 -0800 (PST) Received: from zen.nash.org (localhost [127.0.0.1]) by zen.nash.org (8.7.6/8.6.12) with SMTP id WAA12240; Sun, 3 Nov 1996 22:17:32 -0600 (CST) Message-ID: <327D6E5B.167EB0E7@mcs.com> Date: Sun, 03 Nov 1996 22:17:31 -0600 From: Alex Nash X-Mailer: Mozilla 3.01b1 (X11; I; FreeBSD 2.1.5-STABLE i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: hardware@freebsd.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? References: <8387.847074260@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > I just recently had a WIDE drive fall into my lap, so I finally > started putting that WIDE connector on my 2940UW controller to good > use. While reading the Adaptec controller docs before jumping in, I > saw that it very specifically said to use only ONE of the internal > connectors, either the WIDE or the narrow, but not both. You could > still use the external connector for either kind of drive, but not > hook both internal connectors up at once. Well, this made sense to me > since it seemed like otherwise you'd have a "Y" configuration in your > SCSI bus, and it wasn't clear which devices you'd terminate if you > plugged both internal connectors in - each end of the Y, or what? This is perfectly legitimate, I run such a configuration here. You essentially have the following (excuse the poor quality ASCII art): Wide Devices Narrow Devices low bits !-------+------------! 2940 high bits !-------! Where '!' indicates termination points. In the Adaptec BIOS, you'll see termination options for low on/off and high on/off. These refer to whether or not the adapter is terminating those bits of the bus. For devices on the wide and narrow busses, you want high on/low off. The low bits are being terminated by the wide and narrow devices, whereas the high bits are only terminated on the wide bus. Alex From owner-freebsd-hardware Sun Nov 3 20:23:34 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA09339 for hardware-outgoing; Sun, 3 Nov 1996 20:23:34 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA09322 for ; Sun, 3 Nov 1996 20:23:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id VAA01364; Sun, 3 Nov 1996 21:23:13 -0700 Message-Id: <199611040423.VAA01364@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: "Jordan K. Hubbard" cc: hardware@freebsd.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-reply-to: Your message of "Sun, 03 Nov 1996 18:24:20 PST." <8387.847074260@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Nov 1996 21:23:13 -0700 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, >use. While reading the Adaptec controller docs before jumping in, I >saw that it very specifically said to use only ONE of the internal >connectors, either the WIDE or the narrow, but not both. You could >still use the external connector for either kind of drive, but not >hook both internal connectors up at once. Well, this made sense to me >since it seemed like otherwise you'd have a "Y" configuration in your >SCSI bus, and it wasn't clear which devices you'd terminate if you >plugged both internal connectors in - each end of the Y, or what? So use any 2 of the 3, both internal is fine as long as you don't use the external. As to termination, the card is at the end if using 1 cable (and thus should be terminated) and is in the middle if using 2 cables (any commbination) and should NOT be terminated. -- Steve Passe | powered by smp@csn.net | FreeBSD From owner-freebsd-hardware Sun Nov 3 20:32:40 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA10680 for hardware-outgoing; Sun, 3 Nov 1996 20:32:40 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA10632 for ; Sun, 3 Nov 1996 20:32:22 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id PAA12438; Mon, 4 Nov 1996 15:02:14 +1030 From: Michael Smith Message-Id: <199611040432.PAA12438@genesis.atrad.adelaide.edu.au> Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 4 Nov 1996 15:02:13 +1030 (CST) Cc: hardware@freebsd.org In-Reply-To: <8387.847074260@time.cdrom.com> from "Jordan K. Hubbard" at Nov 3, 96 06:24:20 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > Then I was talking to Poul-Henning last night who pooh-pooh'd my > foolish conservatism and stated that I could have used both internal > connectors on my 2940UW no problem. Since I could use that 1542 as my > spare again (which is why I have it), I'd sort of like to know which > one of us is correct? :-) Stub length limit on the SCSI bus is spec'ed at 7" IIRC. Pick one arm of the Y, say "hello stub", and make it as short as possible. I've run longer stubs (over about 50cm things get nasty), but only on old/slow stuff (old workstations, 1542 clones, slow disks). > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Sun Nov 3 21:13:48 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA16005 for hardware-outgoing; Sun, 3 Nov 1996 21:13:48 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA15989 for ; Sun, 3 Nov 1996 21:13:43 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id VAA00768; Sun, 3 Nov 1996 21:13:37 -0800 (PST) To: Alex Nash cc: hardware@freebsd.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-reply-to: Your message of "Sun, 03 Nov 1996 22:17:31 CST." <327D6E5B.167EB0E7@mcs.com> Date: Sun, 03 Nov 1996 21:13:36 -0800 Message-ID: <766.847084416@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks, I think that pretty much explains it all! Jordan From owner-freebsd-hardware Sun Nov 3 21:30:25 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA19325 for hardware-outgoing; Sun, 3 Nov 1996 21:30:25 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA19303 for ; Sun, 3 Nov 1996 21:30:15 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id QAA13032; Mon, 4 Nov 1996 16:00:03 +1030 From: Michael Smith Message-Id: <199611040530.QAA13032@genesis.atrad.adelaide.edu.au> Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 4 Nov 1996 16:00:02 +1030 (CST) Cc: jkh@time.cdrom.com, hardware@freebsd.org In-Reply-To: <199611040432.PAA12438@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Nov 4, 96 03:02:13 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith stands accused of saying: > > Jordan K. Hubbard stands accused of saying: > > > > Then I was talking to Poul-Henning last night who pooh-pooh'd my > > foolish conservatism and stated that I could have used both internal > > connectors on my 2940UW no problem. Since I could use that 1542 as my > > spare again (which is why I have it), I'd sort of like to know which > > one of us is correct? :-) > > Stub length limit on the SCSI bus is spec'ed at 7" IIRC. Pick one arm > of the Y, say "hello stub", and make it as short as possible. Urk, forgot you were running wide - make the narrow internal the stub, and terminate the wide internal, and wide either on the card or external. I'm sure you get the picture 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Sun Nov 3 21:45:23 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA22161 for hardware-outgoing; Sun, 3 Nov 1996 21:45:23 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA22128 for ; Sun, 3 Nov 1996 21:45:15 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id VAA10829; Sun, 3 Nov 1996 21:45:22 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id VAA28679; Sun, 3 Nov 1996 21:45:05 -0800 (PST) Message-Id: <199611040545.VAA28679@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" cc: Alex Nash , hardware@freebsd.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-reply-to: Your message of Sun, 03 Nov 96 21:13:36 -0800. <766.847084416@time.cdrom.com> Date: Sun, 03 Nov 1996 21:45:05 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Thanks, I think that pretty much explains it all! I'm not sure which "deal" you're referring to, but I'll guess... There is one narrow (8-bit) 50-pin internal connector, and one wide (16-bit) 68-pin connector internally. There is also a wide 68-pin external connector. You will need a different external cable if you currently have a narrow 50-pin external connector. You can't have drives connected to all three connectors at the same time -- you can only use two of the three simultaneously (else you have the low byte terminated in three places). ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hardware Sun Nov 3 21:45:26 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA22177 for hardware-outgoing; Sun, 3 Nov 1996 21:45:26 -0800 (PST) Received: from Mail.IDT.NET (mail.idt.net [198.4.75.205]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA22149 for ; Sun, 3 Nov 1996 21:45:21 -0800 (PST) Received: from sequoia (ppp-22.ts-1.mlb.idt.net [169.132.71.22]) by Mail.IDT.NET (8.7.4/8.7.3) with SMTP id AAA07588; Mon, 4 Nov 1996 00:45:09 -0500 (EST) Message-ID: <327D831B.1D0D@mail.idt.net> Date: Mon, 04 Nov 1996 00:46:03 -0500 From: Gary Corcoran Reply-To: garycorc@mail.idt.net X-Mailer: Mozilla 3.0 (WinNT; U) MIME-Version: 1.0 To: Steve Passe CC: "Jordan K. Hubbard" , hardware@FreeBSD.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? References: <199611040423.VAA01364@clem.systemsix.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Steve Passe wrote: > use any 2 of the 3, both internal is fine as long as you don't use the > external. As to termination, the card is at the end if using > 1 cable (and thus should be terminated) and is in the middle if using > 2 cables (any commbination) and should NOT be terminated. That explains it. Using one connector, the card terminates one end of the SCSI cable. Using any two of the connectors, the card is in the "middle" of the SCSI bus. But if you were to try to use all three connectors, then you *would* have a "Y" cable situation, which I'm sure would lead to all sorts of nasty reflections on the bus (in certain/most cases at least). Gary From owner-freebsd-hardware Sun Nov 3 21:47:25 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA22754 for hardware-outgoing; Sun, 3 Nov 1996 21:47:25 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA22735 for ; Sun, 3 Nov 1996 21:47:20 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id VAA10857; Sun, 3 Nov 1996 21:47:27 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id VAA28693; Sun, 3 Nov 1996 21:47:10 -0800 (PST) Message-Id: <199611040547.VAA28693@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Michael Smith cc: jkh@time.cdrom.com (Jordan K. Hubbard), hardware@freebsd.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-reply-to: Your message of Mon, 04 Nov 96 15:02:13 +1030. <199611040432.PAA12438@genesis.atrad.adelaide.edu.au> Date: Sun, 03 Nov 1996 21:47:05 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Jordan K. Hubbard stands accused of saying: >> Then I was talking to Poul-Henning last night who pooh-pooh'd my >> foolish conservatism and stated that I could have used both internal >> connectors on my 2940UW no problem. Since I could use that 1542 as my >> spare again (which is why I have it), I'd sort of like to know which >> one of us is correct? :-) >Stub length limit on the SCSI bus is spec'ed at 7" IIRC. Pick one arm >of the Y, say "hello stub", and make it as short as possible. Actually, the manual that comes with the Adaptec 3940 says that the maximum length is supposed to be something like a meter, and you should have at least twelve inches between devices for optimal performance (I can look up the exact wording if it's of interest). >I've run longer stubs (over about 50cm things get nasty), but only on >old/slow stuff (old workstations, 1542 clones, slow disks). ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hardware Sun Nov 3 21:49:12 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA23145 for hardware-outgoing; Sun, 3 Nov 1996 21:49:12 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA23129 for ; Sun, 3 Nov 1996 21:49:08 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id VAA10894; Sun, 3 Nov 1996 21:49:15 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id VAA28720; Sun, 3 Nov 1996 21:48:59 -0800 (PST) Message-Id: <199611040548.VAA28720@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Justin T. Gibbs" cc: "Jordan K. Hubbard" , hardware@freebsd.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-reply-to: Your message of Sun, 03 Nov 96 18:42:33 -0800. <199611040242.SAA00127@freefall.freebsd.org> Date: Sun, 03 Nov 1996 21:48:59 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >According to Adaptec, you are supposed to use only two or the three >connectors on the card. I'm sure the EE members of the crowd can >tell you why. It doesn't take an EE... Just think about it -- use all three connectors and you have the low byte terminated in three places (or if you only terminate two of the ends, you have a third "end" flapping in the electronic breeze...). ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hardware Sun Nov 3 22:06:39 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA24959 for hardware-outgoing; Sun, 3 Nov 1996 22:06:39 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA24947 for ; Sun, 3 Nov 1996 22:06:33 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id XAA01903; Sun, 3 Nov 1996 23:06:19 -0700 Message-Id: <199611040606.XAA01903@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: garycorc@mail.idt.net cc: "Jordan K. Hubbard" , hardware@FreeBSD.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-reply-to: Your message of "Mon, 04 Nov 1996 00:46:03 EST." <327D831B.1D0D@mail.idt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Nov 1996 23:06:19 -0700 Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, > > use any 2 of the 3, both internal is fine as long as you don't use the > > external. As to termination, the card is at the end if using > > 1 cable (and thus should be terminated) and is in the middle if using > > 2 cables (any commbination) and should NOT be terminated. > > That explains it. Using one connector, the card terminates one end > of the SCSI cable. Using any two of the connectors, the card is > in the "middle" of the SCSI bus. But if you were to try to use > all three connectors, then you *would* have a "Y" cable situation, > which I'm sure would lead to all sorts of nasty reflections on > the bus (in certain/most cases at least). with the detail (for case of card in middle) stated by Justin: > with the controller termination set to high byte on, low byte off. this for the common case where you have wide devices on one cable and narrow on the other. If you used wide devices on both int/ext wide connectors both high/low would be off on the card. It is nothing more than another SCSI device, but one which happens to have 3 physical connectors for convenience. Electrically the 3 are one connector, just like any other SCSI device has. Think of them as the equivalant of the cable in an external SCSI cabinet. -- Steve Passe | powered by smp@csn.net | FreeBSD -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzHe7tEAAAEEAM274wAEEdP+grIrV6UtBt54FB5ufifFRA5ujzflrvlF8aoE 04it5BsUPFi3jJLfvOQeydbegexspPXL6kUejYt2OeptHuroIVW5+y2M2naTwqtX WVGeBP6s2q/fPPAS+g+sNZCpVBTbuinKa/C4Q6HJ++M9AyzIq5EuvO0a8Rr9AAUR tBlTdGV2ZSBQYXNzZSA8c21wQGNzbi5uZXQ+ =ds99 -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-hardware Sun Nov 3 22:55:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA29213 for hardware-outgoing; Sun, 3 Nov 1996 22:55:42 -0800 (PST) Received: from itp.ac.ru (itp.ac.ru [193.233.32.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA29200 for ; Sun, 3 Nov 1996 22:55:31 -0800 (PST) Received: (ks@localhost) by itp.ac.ru (8.6.11/8.6.5) id KAA07181; Mon, 4 Nov 1996 10:01:10 +0300 Date: Mon, 4 Nov 1996 10:01:10 +0300 From: "Sergey S. Kosyakov" Message-Id: <199611040701.KAA07181@itp.ac.ru> To: se@zpr.uni-koeln.de Subject: Re: SCSI CDROM In-Reply-To: Mail from 'se@zpr.uni-koeln.de (Stefan Esser)' dated: Sun, 3 Nov 1996 23:51:07 +0100 Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is an unexpected disconnect. Did you eject the CD while the drive was active ? No Please let me know, what kind of CDROM drive you are using (best if you send me a boot message log). And please give more information about the exact situation that caused this problem: How was the CDROM used, how was the eject initiated ? It is CD-R, but with previous FreeBSD SNAP it works fine. I don't know what was the reason for errors - new SNAP or second NCR I added just before new SNAP install. I try "eject" from various programs (workman,xcd,etc) including cdcontrol. I use this CD-R as CD with MSDOS,Win95 and WinNT - work good. Below is boot message log: FreeBSD 2.2-960801-SNAP #0: Thu Oct 31 14:04:52 MSK 1996 ks@speecart.chg.ru:/usr/src/sys/compile/SPEECART Calibrating clock(s) relative to mc146818A clock... i586 clock: 119766895 Hz, i8254 clock: 1193331 Hz CPU: Pentium (119.75-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30556160 (29840K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7:0 piix0 rev 2 on pci0:7:1 vga0 rev 67 int a irq 10 on pci0:17 ncr0 rev 2 int a irq 12 on pci0:18 ncr0 waiting for scsi devices to settle (ncr0:6:0): "SONY CD-R CDU920S 2.0b" type 5 removable SCSI 2 cd0(ncr0:6:0): CD-ROM cd0(ncr0:6:0): 250ns (4 Mb/sec) offset 8. cd0(ncr0:6:0): UNIT ATTENTION asc:28,0 cd0(ncr0:6:0): Not ready to ready transition, medium may have changed cd present [400000 x 2048 byte records] ncr1 rev 3 int a irq 5 on pci0:19 ncr1 waiting for scsi devices to settle "DEC TZ87 (C) DEC 9514" type 1 removable SCSI 2 st0(ncr1:1:0): Sequential-Access st0(ncr1:1:0): 200ns (5 Mb/sec) offset 8. density code 0x19, variable blocks, write-enabled de0 rev 17 int a irq 11 on pci0:20 de0: DC21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:f8:d0:c2 Probing for devices on the ISA bus: ..................................... From owner-freebsd-hardware Sun Nov 3 23:55:03 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA04156 for hardware-outgoing; Sun, 3 Nov 1996 23:55:03 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA04146 for ; Sun, 3 Nov 1996 23:54:59 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id XAA03238; Sun, 3 Nov 1996 23:54:48 -0800 (PST) From: "Rodney W. Grimes" Message-Id: <199611040754.XAA03238@GndRsh.aac.dev.com> Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-Reply-To: <199611040242.SAA00127@freefall.freebsd.org> from "Justin T. Gibbs" at "Nov 3, 96 06:42:33 pm" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sun, 3 Nov 1996 23:54:47 -0800 (PST) Cc: jkh@time.cdrom.com, hardware@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > According to Adaptec, you are supposed to use only two or the three you CAN use ANY two OF the three connectors... > connectors on the card. I'm sure the EE members of the crowd can > tell you why. All three connectors on the card are electrically and MECHANICALLY within the ``stub'' length allowed by the SCSI spec, thus you don't have a Y (as some one else put it) as long as you only use 2 of the 3 connectors. The SCSI spec allows a small unterminated stub to exists on the SCSI bus. Your 2940UW looks something like this: XW--IW--IN XW is the eXternal Wide connector, IW is the Internal Wide connector, IN is the Internal Narrow connector, and -- is a very short distance. Now as you can see: XW--IW--IN | | | ---------ND WD When we add drives using both internal connectors we have this little stub bus out to the XW connector, no big deal, the SCSI spec allows it. Note that the 2940UW must terminate ONLY the high 8 bits of the wide bus in this configuration, and both WD and ND must be terminated. Other configurations can be found in the manuals, and as usual termination configuration is left as an excercise to the user... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hardware Sun Nov 3 23:58:23 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA04617 for hardware-outgoing; Sun, 3 Nov 1996 23:58:23 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA04598 for ; Sun, 3 Nov 1996 23:58:18 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id XAA03248; Sun, 3 Nov 1996 23:57:52 -0800 (PST) From: "Rodney W. Grimes" Message-Id: <199611040757.XAA03248@GndRsh.aac.dev.com> Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-Reply-To: <199611040423.VAA01364@clem.systemsix.com> from Steve Passe at "Nov 3, 96 09:23:13 pm" To: smp@csn.net (Steve Passe) Date: Sun, 3 Nov 1996 23:57:51 -0800 (PST) Cc: jkh@time.cdrom.com, hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi, > > >use. While reading the Adaptec controller docs before jumping in, I > >saw that it very specifically said to use only ONE of the internal > >connectors, either the WIDE or the narrow, but not both. You could > >still use the external connector for either kind of drive, but not > >hook both internal connectors up at once. Well, this made sense to me > >since it seemed like otherwise you'd have a "Y" configuration in your > >SCSI bus, and it wasn't clear which devices you'd terminate if you > >plugged both internal connectors in - each end of the Y, or what? So > > use any 2 of the 3, both internal is fine as long as you don't use the > external. As to termination, the card is at the end if using > 1 cable (and thus should be terminated) and is in the middle if using > 2 cables (any commbination) and should NOT be terminated. VERY common mistake here, if using 2 cables, and BOTH are wide, no termination is needed on the 2940*W, if using 2 cables and one is narrow the 2940*W MUST terminate the high 8 bits of the scsi bus (HIGH ON/LOW OFF) is what Adaptec calls it. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hardware Mon Nov 4 00:01:11 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA05009 for hardware-outgoing; Mon, 4 Nov 1996 00:01:11 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA04994 for ; Mon, 4 Nov 1996 00:01:05 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id AAA03336; Mon, 4 Nov 1996 00:00:15 -0800 (PST) From: "Rodney W. Grimes" Message-Id: <199611040800.AAA03336@GndRsh.aac.dev.com> Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-Reply-To: <199611040432.PAA12438@genesis.atrad.adelaide.edu.au> from Michael Smith at "Nov 4, 96 03:02:13 pm" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 4 Nov 1996 00:00:15 -0800 (PST) Cc: jkh@time.cdrom.com, hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Jordan K. Hubbard stands accused of saying: > > > > Then I was talking to Poul-Henning last night who pooh-pooh'd my > > foolish conservatism and stated that I could have used both internal > > connectors on my 2940UW no problem. Since I could use that 1542 as my > > spare again (which is why I have it), I'd sort of like to know which > > one of us is correct? :-) > > Stub length limit on the SCSI bus is spec'ed at 7" IIRC. Pick one arm > of the Y, say "hello stub", and make it as short as possible. SCSI-II and SCSI-III revised that, if I recall correctly it is now down to 3.5" on SCSI-II and 1.75" on SCSI-III (Ultra). > I've run longer stubs (over about 50cm things get nasty), but only on > old/slow stuff (old workstations, 1542 clones, slow disks). 50cm at 20MHZ gets pretty darn ugly on any transmission line stub I have looked at. Forced Perfect termination might make it work at these speeds, but then again it might not... :-). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hardware Mon Nov 4 00:31:34 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA07582 for hardware-outgoing; Mon, 4 Nov 1996 00:31:34 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA07567 for ; Mon, 4 Nov 1996 00:31:28 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id JAA25216; Mon, 4 Nov 1996 09:32:10 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id JAA25585; Mon, 4 Nov 1996 09:41:02 +0100 Date: Mon, 4 Nov 1996 09:41:02 +0100 From: Christoph Kukulies Message-Id: <199611040841.JAA25585@gilberto.physik.rwth-aachen.de> To: freebsd-questions@freefall.FreeBSD.org, hardware@freebsd.org Subject: Adaptec AVA 1505 SCSI controller Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a AVA 1505 here. It called 'TotalCD 16 bit SCSI-2 Host Adapter for CD-ROM Drive Connectivity' - brand new. Is this piece of hardware supported? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hardware Mon Nov 4 00:51:43 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA10835 for hardware-outgoing; Mon, 4 Nov 1996 00:51:43 -0800 (PST) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA10805; Mon, 4 Nov 1996 00:51:36 -0800 (PST) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id JAA08847; Mon, 4 Nov 1996 09:52:02 +0100 (MET) To: "Jordan K. Hubbard" cc: hardware@freebsd.org Subject: Re: OK, what's the deal with 2940W controllers and internal connectors? In-reply-to: Your message of "Sun, 03 Nov 1996 18:24:20 PST." <8387.847074260@time.cdrom.com> Date: Mon, 04 Nov 1996 09:52:01 +0100 Message-ID: <8845.847097521@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Then I was talking to Poul-Henning last night who pooh-pooh'd my >foolish conservatism and stated that I could have used both internal >connectors on my 2940UW no problem. The SCSI spec allows for a max of 10cm long "stubs" on a scsi-string, and at least my 2940W fullfills that dimension. It may not hold for ultra, but it sure works for me at 10mb/s -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hardware Mon Nov 4 01:19:20 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA16100 for hardware-outgoing; Mon, 4 Nov 1996 01:19:20 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA16084 for ; Mon, 4 Nov 1996 01:19:16 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id BAA00438; Mon, 4 Nov 1996 01:18:44 -0800 (PST) To: Christoph Kukulies cc: freebsd-questions@freefall.freebsd.org, hardware@FreeBSD.org Subject: Re: Adaptec AVA 1505 SCSI controller In-reply-to: Your message of "Mon, 04 Nov 1996 09:41:02 +0100." <199611040841.JAA25585@gilberto.physik.rwth-aachen.de> Date: Mon, 04 Nov 1996 01:18:44 -0800 Message-ID: <436.847099124@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I have a AVA 1505 here. It called 'TotalCD 16 bit SCSI-2 Host Adapter for > CD-ROM Drive Connectivity' - brand new. Erm. Are you sure that's an Adaptec? It sounds more like an AdvanSys controller to me. Jordan From owner-freebsd-hardware Mon Nov 4 01:36:30 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA18380 for hardware-outgoing; Mon, 4 Nov 1996 01:36:30 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA18076 for ; Mon, 4 Nov 1996 01:34:08 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id KAA26908; Mon, 4 Nov 1996 10:33:35 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id KAA25798; Mon, 4 Nov 1996 10:42:24 +0100 From: Christoph Kukulies Message-Id: <199611040942.KAA25798@gilberto.physik.rwth-aachen.de> Subject: Re: Adaptec AVA 1505 SCSI controller In-Reply-To: <199611040841.JAA25585@gilberto.physik.rwth-aachen.de> from Christoph Kukulies at "Nov 4, 96 09:41:02 am" To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Date: Mon, 4 Nov 1996 10:42:24 +0100 (MET) Cc: freebsd-questions@freefall.freebsd.org, hardware@freebsd.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I have a AVA 1505 here. It's called 'TotalCD 16 bit SCSI-2 Host Adapter for > CD-ROM Drive Connectivity' - brand new. > > Is this piece of hardware supported? I found it's recognized as aic0 at 0x340-0x35f irq 11 on isa The only quirk I note is that one of the two WD 8013EPC is disturbed (ed0 timeout) when the card is present. The card doesn't have a BIOS ROM on it (spare jumpers for the BIOS range) ed0 at 0x300 irq 10 iomem 0xcc000 ed1 at 0x280 irq 3 iomem 0xd8000 > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hardware Mon Nov 4 01:36:31 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA18396 for hardware-outgoing; Mon, 4 Nov 1996 01:36:31 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA18351 for ; Mon, 4 Nov 1996 01:36:22 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id KAA26945; Mon, 4 Nov 1996 10:34:49 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id KAA25810; Mon, 4 Nov 1996 10:43:47 +0100 From: Christoph Kukulies Message-Id: <199611040943.KAA25810@gilberto.physik.rwth-aachen.de> Subject: Re: Adaptec AVA 1505 SCSI controller In-Reply-To: <436.847099124@time.cdrom.com> from "Jordan K. Hubbard" at "Nov 4, 96 01:18:44 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 4 Nov 1996 10:43:47 +0100 (MET) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-questions@freefall.freebsd.org, hardware@FreeBSD.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > I have a AVA 1505 here. It called 'TotalCD 16 bit SCSI-2 Host Adapter for > > CD-ROM Drive Connectivity' - brand new. > > Erm. Are you sure that's an Adaptec? It sounds more like an AdvanSys > controller to me. No, definitely Adaptec. "Adaptec Altra(tm) Line" > > Jordan > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hardware Mon Nov 4 01:41:30 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA19096 for hardware-outgoing; Mon, 4 Nov 1996 01:41:30 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA19082 for ; Mon, 4 Nov 1996 01:41:26 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id BAA01835; Mon, 4 Nov 1996 01:41:11 -0800 (PST) To: Christoph Kukulies cc: freebsd-questions@freefall.freebsd.org, hardware@FreeBSD.org Subject: Re: Adaptec AVA 1505 SCSI controller In-reply-to: Your message of "Mon, 04 Nov 1996 10:43:47 +0100." <199611040943.KAA25810@gilberto.physik.rwth-aachen.de> Date: Mon, 04 Nov 1996 01:41:11 -0800 Message-ID: <1832.847100471@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > No, definitely Adaptec. "Adaptec Altra(tm) Line" Ah, never mind then. You remember what I said about my memory. :-) Send it to Justin? :) Jordan From owner-freebsd-hardware Mon Nov 4 07:37:11 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA25509 for hardware-outgoing; Mon, 4 Nov 1996 07:37:11 -0800 (PST) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA25502 for ; Mon, 4 Nov 1996 07:37:04 -0800 (PST) Received: from arts.ratp.fr (arts.ratp.fr [193.106.40.1]) by soleil.uvsq.fr (8.8.0/jtpda-5.2) with ESMTP id QAA10805 ; Mon, 4 Nov 1996 16:36:54 +0100 (MET) Received: by arts.ratp.fr id QAA03364 ; Mon, 4 Nov 1996 16:36:49 +0100 (MET) Received: from minos.noisy.ratp by arts.ratp.fr with SMTP id SAA003357 for ; Mon Nov 4 16:36:22 1996 Received: by minos.noisy.ratp id AA10748 for Pierre.David@prism.uvsq.fr; Mon, 4 Nov 1996 16:36:22 +0100 From: Janick TAILLANDIER Message-Id: <9611041536.AA10748@minos.noisy.ratp> Subject: Disk problem To: freebsd-hardware@freefall.freebsd.org Date: Mon, 4 Nov 1996 16:36:21 +0100 (MET) X-Mailer: ELM [version 2.4 PL24 ME8] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, I have an Adaptec 2940UW and a Fujitsu M2952Q disk. Here are the relevant boot messages on FreeBSD 2.2-961014-SNAP kernel: Nov 4 14:25:34 chaconne /kernel: ahc0 rev 0 int a irq 15 on pci0:17 Nov 4 14:25:34 chaconne /kernel: ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs Nov 4 14:25:34 chaconne /kernel: ahc0 waiting for scsi devices to settle Nov 4 14:25:34 chaconne /kernel: ahc0: target 6 Tagged Queuing Device Nov 4 14:25:34 chaconne /kernel: (ahc0:6:0): "FUJITSU M2952Q-512 0124" type 0 fixed SCSI 2 Nov 4 14:25:34 chaconne /kernel: sd0(ahc0:6:0): Direct-Access 2291MB (4693462 512 byte sectors) I am now getting repeated messages such as and lots of I/O errors: sd0(ahc0:6:0): HARDWARE FAILURE asc:44,84 Vendor Specific ASCQ , retries:4 sd0(ahc0:6:0): HARDWARE FAILURE asc:44,84 Vendor Specific ASCQ , retries:3 sd0(ahc0:6:0): HARDWARE FAILURE asc:44,84 Vendor Specific ASCQ , retries:2 sd0(ahc0:6:0): HARDWARE FAILURE asc:44,84 Vendor Specific ASCQ , retries:1 sd0(ahc0:6:0): HARDWARE FAILURE asc:44,84 Vendor Specific ASCQ , FAILURE Has anybody an idea of what is hapening ? Thanks in advance, Janick Taillandier From owner-freebsd-hardware Mon Nov 4 10:19:21 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11137 for hardware-outgoing; Mon, 4 Nov 1996 10:19:21 -0800 (PST) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA11132; Mon, 4 Nov 1996 10:19:17 -0800 (PST) Message-Id: <199611041819.KAA11132@freefall.freebsd.org> To: Janick TAILLANDIER cc: freebsd-hardware@freefall.freebsd.org Subject: Re: Disk problem In-reply-to: Your message of "Mon, 04 Nov 1996 16:36:21 +0100." <9611041536.AA10748@minos.noisy.ratp> Date: Mon, 04 Nov 1996 10:19:16 -0800 From: "Justin T. Gibbs" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Hello, > >I have an Adaptec 2940UW and a Fujitsu M2952Q disk. >Here are the relevant boot messages on FreeBSD 2.2-961014-SNAP >kernel: Perhaps it doesn't really support tagged queuing? Did this just start happening recently? >Has anybody an idea of what is hapening ? > >Thanks in advance, > >Janick Taillandier -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Mon Nov 4 10:45:31 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA13047 for hardware-outgoing; Mon, 4 Nov 1996 10:45:31 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA13037 for ; Mon, 4 Nov 1996 10:45:25 -0800 (PST) From: BRETT_GLASS@infoworld.com Received: from ccgate.infoworld.com (ccgate.infoworld.com [192.216.49.101]) by lserver.infoworld.com (8.7.5/8.7.3/GNAC-GW-1.2) with SMTP id KAA02228; Mon, 4 Nov 1996 10:44:49 -0800 (PST) Received: from ccMail by ccgate.infoworld.com (SMTPLINK V2.11) id AA847132867; Mon, 04 Nov 96 10:49:46 PST Date: Mon, 04 Nov 96 10:49:46 PST Message-Id: <9610048471.AA847132867@ccgate.infoworld.com> To: "Jordan K. Hubbard" , hardware@freebsd.org Subject: OK, what's the deal with 2940W controllers and internal conn Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From an EE standpoint, the key things to understand are as follows: * Each line on the bus must be a continuous transmission line; no "Y" configuration is allowed (though very short "spurs" into devices are). * Each line must be terminated at both ends. If some lines are longer than others (as when you mix narrow and wide devices), only SOME lines of the bus may be terminated at a given device (or at the host adapter) while the rest continue on. For example, suppose you want to attach both narrow and wide devices to a SCSI card like your Adaptec. The "narrow" section of the bus is a proper subset of the lines comprising the full bus, and will be longer because it goes to all of the wide devices as well as the narrow ones. So, in order to obey the above rules, your Adaptec card has a terminator that can terminate the "extra" lines that are ONLY part of the "wide" section while passing the rest through unterminated. The result looks like this: +-------+ |Host | +-------------+ |Adapter| T==|=============|="Extra" wide SCSI lines=|T | +---------------+ T==|"Wide" device|==="Narrow" SCSI lines===|=======|==|"Narrow" device|===T +-------------+ +-------+ +---------------+ In this picture, "T" represents a terminator. The terminators at the devices may be internal or external. The Adaptec has an internal wide connector, an internal narrow connector, and an external wide connector. This handles many situations gracefully. The glaring exception is when you need to use narrow devices (or, worse, a mix of narrow and wide) externally, in which case you'll need adapters or special cables to get the narrow external devices connected. In this case, it's often easier and cheaper to get another SCSI adapter -- a bargain one will do in most cases -- than to mess with the extra cables and gadgetry. This is what I do for my external Exabyte backup tape drive. There's also another advantage to having a second adapter: it can operate concurrently with the first. This can speed backups up a lot, with one exception: if your backup software is doing direct device-to-device transfers over the SCSI bus. UNIX doesn't have provisions in the OS for this, so I doubt that any UNIX backup utility does it. From owner-freebsd-hardware Mon Nov 4 11:12:16 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15165 for hardware-outgoing; Mon, 4 Nov 1996 11:12:16 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA15148 for ; Mon, 4 Nov 1996 11:12:12 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id LAA07807; Mon, 4 Nov 1996 11:09:07 -0800 (PST) Message-ID: <327E3F45.2781E494@whistle.com> Date: Mon, 04 Nov 1996 11:08:53 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Janick TAILLANDIER CC: freebsd-hardware@freefall.freebsd.org Subject: Re: Disk problem References: <9611041536.AA10748@minos.noisy.ratp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Janick TAILLANDIER wrote: > > Hello, > > I have an Adaptec 2940UW and a Fujitsu M2952Q disk. > Here are the relevant boot messages on FreeBSD 2.2-961014-SNAP > kernel: > > Nov 4 14:25:34 chaconne /kernel: ahc0 rev 0 int a irq 15 on pci0:17 > Nov 4 14:25:34 chaconne /kernel: ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > Nov 4 14:25:34 chaconne /kernel: ahc0 waiting for scsi devices to settle > Nov 4 14:25:34 chaconne /kernel: ahc0: target 6 Tagged Queuing Device > Nov 4 14:25:34 chaconne /kernel: (ahc0:6:0): "FUJITSU M2952Q-512 0124" type 0 fixed SCSI 2 > Nov 4 14:25:34 chaconne /kernel: sd0(ahc0:6:0): Direct-Access 2291MB (4693462 512 byte sectors) your drive is reporting that it is sick.. This message comes all the way from the drive. it is very unlikely that software has anything to do with it.. it is not a bad block.. there is a different message for that. > > I am now getting repeated messages such as and lots of I/O errors: > > sd0(ahc0:6:0): HARDWARE FAILURE asc:44,84 Vendor Specific ASCQ > , retries:4 > sd0(ahc0:6:0): HARDWARE FAILURE asc:44,84 Vendor Specific ASCQ > , retries:3 > sd0(ahc0:6:0): HARDWARE FAILURE asc:44,84 Vendor Specific ASCQ > , retries:2 > sd0(ahc0:6:0): HARDWARE FAILURE asc:44,84 Vendor Specific ASCQ > , retries:1 > sd0(ahc0:6:0): HARDWARE FAILURE asc:44,84 Vendor Specific ASCQ > , FAILURE > > Has anybody an idea of what is hapening ? > > Thanks in advance, > > Janick Taillandier From owner-freebsd-hardware Mon Nov 4 21:47:37 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA06783 for hardware-outgoing; Mon, 4 Nov 1996 21:47:37 -0800 (PST) Received: from murrow.prognet.com (prognet.com [205.219.198.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA06763 for ; Mon, 4 Nov 1996 21:47:31 -0800 (PST) Received: from peterh.dev.prognet.com (two89.dev.prognet.com) by murrow.prognet.com with SMTP id AA21646 (5.67b/IDA-1.5 for ); Mon, 4 Nov 1996 21:47:35 -0800 Message-Id: <3.0b36.32.19961104214507.011c0f04@prognet.com> X-Sender: peterh@prognet.com X-Mailer: Windows Eudora Pro Version 3.0b36 (32) Date: Mon, 04 Nov 1996 21:45:08 -0800 To: freebsd-hardware@freebsd.org From: Peter Haight Subject: Device driver specs and an ATAPI CD-ROM (Sanyo Torisan CDR-S1G drive) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've got a CD-ROM that half works with Freebsd-2.2-961014-SNAP. Basically if you tell it to play from the beginning, it will play the CD all the way through, but it has the track information messed up (different results depending on which cd playing program you use). It basically boils down to the fact that the CDROM apparently doesn't implement ATAPI correctly. It doesn't support the READ CD-ROM CAPACITY ATAPI packet command. (Executing this command produces an AER_SK_ILLEGAL_REQUEST). This keeps the FreeBSD ioctl library from correctly generating the leadout track. This leads to general weirdness in the different software because they use the leadout track to determine where the end of the last valid track is. Now, I really don't care whether this problem gets fixed or not, I can swap this CDROM with the one in my Windows95 box which has a driver that seems to work with this drive and the CDROM in the Window95 box works fine with FreeBSD. This was mostly just an exercise to learn about FreeBSD and its device drivers. There is one thing I do want to know, though. I figure that since the Window95 driver works, there must be some way to figure out the length of the last track. I can't seem to find anything that will work in any of the other ATAPI commands, so I figure that this drive must have a command similar to READ CD-ROM CAPACITY but not exactly the same as the ATAPI standard. Finally, we have hit my question: How can I get the specification for this drive to determine whether such a command exists? I have searched on the web quite a bit for anything related to Torisan, CDR-S1G, and/or Sanyo, but haven't come up with anything. I'm having problems even getting an address or phone number for Sanyo which I could use. Any suggestions? Is there some repository for this sort of information somewhere? Is ther some secret way to get companies to give you specs? From owner-freebsd-hardware Mon Nov 4 22:26:14 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08604 for hardware-outgoing; Mon, 4 Nov 1996 22:26:14 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA08599 for ; Mon, 4 Nov 1996 22:26:11 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id QAA22700; Tue, 5 Nov 1996 16:55:52 +1030 From: Michael Smith Message-Id: <199611050625.QAA22700@genesis.atrad.adelaide.edu.au> Subject: Re: Device driver specs and an ATAPI CD-ROM (Sanyo Torisan CDR-S1G To: peterh@prognet.com (Peter Haight) Date: Tue, 5 Nov 1996 16:55:51 +1030 (CST) Cc: freebsd-hardware@freebsd.org In-Reply-To: <3.0b36.32.19961104214507.011c0f04@prognet.com> from "Peter Haight" at Nov 4, 96 09:45:08 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Peter Haight stands accused of saying: > > Finally, we have hit my question: How can I get the specification for this > drive to determine whether such a command exists? > > I have searched on the web quite a bit for anything related to Torisan, > CDR-S1G, and/or Sanyo, but haven't come up with anything. I'm having > problems even getting an address or phone number for Sanyo which I could use. > > Any suggestions? Is there some repository for this sort of information > somewhere? Is ther some secret way to get companies to give you specs? Welcome to the frustrating world of the free software device-driver author. You have a number of options : - Lie outrageously to the manufacturer. Tell them you have an embedded application, and that you want to use their device for . Tell them that you plan to sell 10,000 units or more in the first 6 months, but that it is crucial that you have full access to the interface spec of their device. You need to be good at keeping your story straight, and avoid any questions along the lines of "would you like to commit to an order". It is sometimes desirable to rent a PO box for the receipt of said spec, and avoid giving them any details that could lead them to you. You may still be forced to an NDA here, at which point you lose. - Blackmail the manufacturer. This works best in the Linux community, with their incredible capacity for generating invective out of thin air, but has been quite effective at bringing large manufacturers (eg. Diamond) around. Generally works best if the device in question is a popular unit and lots of people want one. Avoid this until you are _certain_ that the manufacturer won't give you the spec, as otherwise you're likely to offend them. - Reverse-engineer the supplied driver for another OS. Requires some serious hacking studliness; not for the faint-of-heart. There are other techniques (hunting down a kindly tech/programmer working for the company is often a good way to go) which can sometimes be effective, but the above are the most popular. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Tue Nov 5 04:04:09 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA27670 for hardware-outgoing; Tue, 5 Nov 1996 04:04:09 -0800 (PST) Received: from hawk.gnome.co.uk (gnome.gw.cerbernet.co.uk [193.243.224.22]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA27657 for ; Tue, 5 Nov 1996 04:04:03 -0800 (PST) Received: (from jacs@localhost) by hawk.gnome.co.uk (8.7.6/8.7.3) id MAA00603; Tue, 5 Nov 1996 12:03:55 GMT Date: Tue, 5 Nov 1996 12:03:55 GMT From: Chris Stenton Subject: ncro 810 oops error To: hardware@freebsd.org Message-Id: Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have recently upgraded to a Asus Pentium PRO Motherboard with their NCR810 SCSI controller. While using the Amanda backup programme I am getting a large number of errors from the controller. They are of the form. Nov 5 11:51:35 hawk /kernel: ncr?: scatter/gather failed (residue=493925376). Nov 5 11:51:35 hawk /kernel: sd0: oops not queued Nov 5 11:51:35 hawk /kernel: biodone: buffer already done Nov 5 11:51:35 hawk /kernel: ncr?: scatter/gather failed (residue=493924864). Nov 5 11:51:35 hawk /kernel: sd0: oops not queued Nov 5 11:51:35 hawk /kernel: biodone: buffer already done Nov 5 11:51:35 hawk /kernel: ncr?: scatter/gather failed (residue=493924352). Nov 5 11:51:35 hawk /kernel: sd0: oops not queued Nov 5 11:51:35 hawk /kernel: biodone: buffer already done Nov 5 11:51:35 hawk /kernel: ncr?: scatter/gather failed (residue=493923840). Nov 5 11:51:35 hawk /kernel: sd0: oops not queued They only seem to happen when it is backing up partitions other than the root partition. I have tried putting the Tape drive on a second controller but it made no difference. I did not have this problem with my GigaByte Neptune board using their NCR810 controller. Any ideas what is wrong. Chris From owner-freebsd-hardware Tue Nov 5 04:39:38 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA29749 for hardware-outgoing; Tue, 5 Nov 1996 04:39:38 -0800 (PST) Received: from hawk.gnome.co.uk (gnome.gw.cerbernet.co.uk [193.243.224.22]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA29743 for ; Tue, 5 Nov 1996 04:39:33 -0800 (PST) Received: (from jacs@localhost) by hawk.gnome.co.uk (8.7.6/8.7.3) id MAA00711; Tue, 5 Nov 1996 12:39:30 GMT Date: Tue, 5 Nov 1996 12:39:30 GMT From: Chris Stenton Subject: Re: ncro 810 oops error To: hardware@freebsd.org Message-Id: Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have recently upgraded to a Asus Pentium PRO Motherboard with their >NCR810 SCSI controller. While using the Amanda backup programme I am >getting a large number of errors from the controller. I should have added that I am running FreeBSD-Stable. Chris From owner-freebsd-hardware Tue Nov 5 06:15:06 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA04306 for hardware-outgoing; Tue, 5 Nov 1996 06:15:06 -0800 (PST) Received: from seine.cs.umd.edu (10862@seine.cs.umd.edu [128.8.128.59]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA04301 for ; Tue, 5 Nov 1996 06:15:04 -0800 (PST) Received: by seine.cs.umd.edu (8.7.6/UMIACS-0.9/04-05-88) id JAA03670; Tue, 5 Nov 1996 09:14:56 -0500 (EST) Date: Tue, 5 Nov 1996 09:14:56 -0500 (EST) From: rohit@cs.umd.edu (Rohit Dube) Message-Id: <199611051414.JAA03670@seine.cs.umd.edu> To: freebsd-hardware@freebsd.org Subject: 4/8 (multi)port serial cards : What works? Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I am shopping for a multiport serial card for my freebsd box. I need the card to be able to hook up to modems for remote dial in and to other freebsd boxes thru NULL serial cable for kernel debugging. Is there a card simultaneously well suited for both these requirements? A recommended re-seller who has good prices? I looked at the Data Comm Warehouse site and they had 'CTRL CYBERPRO QUAD I/O 4PORT SERIAL CARD 16650UART' listed for $99.95. Haven't heard of this one in FreeBSD circles.... Cyclades lists its Cyclom-8Yo (8-port ISA) at $329. No 4-ports. It seems to be able to support full modem functionality. I would appreciate comments from anybody who has actually used these? Thanks. --rohit. PS: I have DB25 males at the back of my boxes. I am also looking for DB25 female to RJ45 female converters which could be put on the boxes make it possible to run RJ45 terminated serial cable between any 2 boxes. Recommendations for an outlet which stocks such things greatly appreciated. From owner-freebsd-hardware Tue Nov 5 06:22:11 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA04537 for hardware-outgoing; Tue, 5 Nov 1996 06:22:11 -0800 (PST) Received: from u2.bbrown.com (U2.BBROWN.COM [192.30.147.97]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA04525 for ; Tue, 5 Nov 1996 06:22:09 -0800 (PST) From: PEKARSKE_BOB/TUC_01@burr-brown.com Received: from by u2.bbrown.com with SMTP (1.38.193.5/16.2) id AA08199; Tue, 5 Nov 1996 07:17:18 -0700 X-Openmail-Hops: 2 Date: Tue, 5 Nov 96 07:19:00 -0700 Message-Id: Subject: looking for local expert To: hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Having big trouble with black screen of death. Is there anyone in Tucson, AZ building FreeBSD boxes? Thank you. pekarske_bob@burr-brown.com From owner-freebsd-hardware Tue Nov 5 21:28:07 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA18921 for hardware-outgoing; Tue, 5 Nov 1996 21:28:07 -0800 (PST) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA18910 for ; Tue, 5 Nov 1996 21:28:03 -0800 (PST) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id VAA28174; Tue, 5 Nov 1996 21:29:21 -0800 Date: Tue, 5 Nov 1996 21:29:19 -0800 (PST) From: Veggy Vinny To: "Kenneth J. Dupuis" cc: hardware@FreeBSD.ORG Subject: Re: /usr/obj size In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 5 Nov 1996, Kenneth J. Dupuis wrote: > On Tue, 5 Nov 1996, Veggy Vinny wrote: > > > Hmmm, is there even a triple channel SCSI controller available? > > Yeah! The Adaptec 3985! Its being touted as their RAID controller... Hmmm, how much does this beast cost? Vince GaiaNet Corporation - Unix Networking Operations - GUS Mailing Lists Admin From owner-freebsd-hardware Wed Nov 6 06:47:15 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA22626 for hardware-outgoing; Wed, 6 Nov 1996 06:47:15 -0800 (PST) Received: from ns.kensco.net (root@kensco.WillowSprings.mci.net [204.70.109.54]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA22618 for ; Wed, 6 Nov 1996 06:47:08 -0800 (PST) Received: from wabash.vinu.edu ([206.140.207.128]) by ns.kensco.net (8.6.12/8.6.12) with SMTP id KAA25298 for ; Wed, 6 Nov 1996 10:00:45 -0500 Message-Id: <199611061500.KAA25298@ns.kensco.net> Comments: Authenticated sender is From: "Earl W Reynolds, Jr." To: hardware@freebsd.org Date: Wed, 6 Nov 1996 09:43:52 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: SCSI Drivers Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42) Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm installing FreeBSD on a Compaq ProSignia 500, and I need a freebsd driver for the embedded SCSI controller. Does anybody know where I can get such a thing? I've scoured the installation manual and can't find a clue. Do I have to go out and buy another controller? Surely someone has written a controller for the ProSignia. Wes Reynolds Director of Technology T: 812-885-1474 Vincennes Community School Corporation F: 812-885-1466 E: wreynolds@kensco.net From owner-freebsd-hardware Wed Nov 6 08:54:19 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02448 for hardware-outgoing; Wed, 6 Nov 1996 08:54:19 -0800 (PST) Received: from apollo.it.hq.nasa.gov (apollo.it.hq.nasa.gov [131.182.119.87]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA02418 for ; Wed, 6 Nov 1996 08:54:06 -0800 (PST) Received: from wirehead.it.hq.nasa.gov (WireHead.it.hq.nasa.gov [131.182.119.88]) by apollo.it.hq.nasa.gov (8.6.12/8.6.12) with ESMTP id QAA27058; Wed, 6 Nov 1996 16:54:09 GMT Received: from localhost (cshenton@localhost) by wirehead.it.hq.nasa.gov (8.6.12/8.6.12) with SMTP id QAA22853; Wed, 6 Nov 1996 16:53:32 GMT Message-Id: <199611061653.QAA22853@wirehead.it.hq.nasa.gov> X-Authentication-Warning: wirehead.it.hq.nasa.gov: cshenton owned process doing -bs X-Authentication-Warning: wirehead.it.hq.nasa.gov: Host localhost didn't use HELO protocol To: wreynolds@kensco.net Cc: hardware@freebsd.org Subject: Re: SCSI Drivers In-Reply-To: Your message of "Wed, 6 Nov 1996 09:43:52 +0000" References: <199611061500.KAA25298@ns.kensco.net> X-Mailer: Mew version 1.03 on Emacs 19.31.8 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 06 Nov 1996 11:53:32 -0500 From: Chris Shenton Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 6 Nov 1996 09:43:52 +0000 "Earl W Reynolds, Jr." wrote: wreynolds> I'm installing FreeBSD on a Compaq ProSignia 500, wreynolds> and I need a freebsd driver for the embedded SCSI controller. wreynolds> wreynolds> Does anybody know where I can get such a thing? I've wreynolds> scoured the installation manual and can't find a clue. Do I wreynolds> have to go out and buy another controller? Surely someone wreynolds> has written a controller for the ProSignia. The problem, I think, is that Compaq doesn't tell you what the embedded controllers are. I fought a couple recently and had to disable the internal SCSI and Ethernet and replaced them with our own boards. This was *not* trivial, as you have to boot from a Compaq CD to reconfig it etc. After this experience, I wouldn't buy one. Anyway... After getting FreeBSD installed, I did a "scanpci" (for some reason in the /usr/X11R6/bin directory) to find out what the graphics was. It found not only a (real) basic graphics controller, but also a Lance Ethernet controllers. I believe I *could* have used the FreeBSD drivers on that ether, rather than my own card, if I had known. Sorry, I can't remember if it found a SCSI controller or not, and I ran out of time to try backing out and using the internal hardware. Take a look with scanpci, give it a shot, and let me know what you find. From owner-freebsd-hardware Wed Nov 6 10:34:40 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA00486 for hardware-outgoing; Wed, 6 Nov 1996 10:34:40 -0800 (PST) Received: from ns.kensco.net (root@kensco.WillowSprings.mci.net [204.70.109.54]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA00467 for ; Wed, 6 Nov 1996 10:34:36 -0800 (PST) Received: from wabash.vinu.edu ([206.140.207.128]) by ns.kensco.net (8.6.12/8.6.12) with SMTP id NAA06196; Wed, 6 Nov 1996 13:48:22 -0500 Message-Id: <199611061848.NAA06196@ns.kensco.net> Comments: Authenticated sender is From: "Earl W Reynolds, Jr." To: Chris Shenton Date: Wed, 6 Nov 1996 13:32:25 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: SCSI Drivers CC: hardware@freebsd.org Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42) Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chris, I can't run scanpci because I don't have freebsd running on the system because it doesn't recognize the disk controller and I can't get past that part of the installation. Is there any way you could check your system again and see what the disk controller is? Thanks! > To: wreynolds@kensco.net > Cc: hardware@freebsd.org > Subject: Re: SCSI Drivers > Date: Wed, 06 Nov 1996 11:53:32 -0500 > From: Chris Shenton > Take a look with scanpci, give it a shot, and let me know what you > find. Wes Reynolds Director of Technology T: 812-885-1474 Vincennes Community School Corporation F: 812-885-1466 E: wreynolds@kensco.net From owner-freebsd-hardware Wed Nov 6 10:37:20 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA01260 for hardware-outgoing; Wed, 6 Nov 1996 10:37:20 -0800 (PST) Received: from ns.kensco.net (root@kensco.WillowSprings.mci.net [204.70.109.54]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA01246 for ; Wed, 6 Nov 1996 10:37:16 -0800 (PST) Received: from wabash.vinu.edu ([206.140.207.128]) by ns.kensco.net (8.6.12/8.6.12) with SMTP id NAA06304; Wed, 6 Nov 1996 13:51:06 -0500 Message-Id: <199611061851.NAA06304@ns.kensco.net> Comments: Authenticated sender is From: "Earl W Reynolds, Jr." To: Chris Shenton Date: Wed, 6 Nov 1996 13:36:07 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: SCSI Driver CC: hardware@freebsd.org Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42) Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chris, I can't run scanpci because I don't have freebsd running on the system because it doesn't recognize the disk controller and I can't get past that part of the installation. Is there any way you could check your system again and see what the disk controller is? Thanks! > To: wreynolds@kensco.net > Cc: hardware@freebsd.org > Subject: Re: SCSI Drivers > Date: Wed, 06 Nov 1996 11:53:32 -0500 > From: Chris Shenton > Take a look with scanpci, give it a shot, and let me know what you > find. Wes Reynolds Director of Technology T: 812-885-1474 Vincennes Community School Corporation F: 812-885-1466 E: wreynolds@kensco.net From owner-freebsd-hardware Wed Nov 6 11:02:05 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA02753 for hardware-outgoing; Wed, 6 Nov 1996 11:02:05 -0800 (PST) Received: from apollo.it.hq.nasa.gov (apollo.it.hq.nasa.gov [131.182.119.87]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA02748 for ; Wed, 6 Nov 1996 11:01:58 -0800 (PST) Received: from wirehead.it.hq.nasa.gov (WireHead.it.hq.nasa.gov [131.182.119.88]) by apollo.it.hq.nasa.gov (8.6.12/8.6.12) with ESMTP id TAA27533; Wed, 6 Nov 1996 19:02:02 GMT Received: from localhost (cshenton@localhost) by wirehead.it.hq.nasa.gov (8.6.12/8.6.12) with SMTP id TAA24696; Wed, 6 Nov 1996 19:01:25 GMT Message-Id: <199611061901.TAA24696@wirehead.it.hq.nasa.gov> X-Authentication-Warning: wirehead.it.hq.nasa.gov: cshenton owned process doing -bs X-Authentication-Warning: wirehead.it.hq.nasa.gov: Host localhost didn't use HELO protocol To: wreynolds@kensco.net Cc: hardware@freebsd.org Subject: Re: SCSI Drivers In-Reply-To: Your message of "Wed, 6 Nov 1996 13:32:25 +0000" References: <199611061848.NAA06196@ns.kensco.net> X-Mailer: Mew version 1.03 on Emacs 19.31.8 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 06 Nov 1996 14:01:24 -0500 From: Chris Shenton Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 6 Nov 1996 13:32:25 +0000 "Earl W Reynolds, Jr." wrote: wreynolds> I can't run scanpci because I don't have freebsd running on the wreynolds> system because it doesn't recognize the disk controller and I can't wreynolds> get past that part of the installation. Is there any way you could wreynolds> check your system again and see what the disk controller is? I can't get at the machine, and I can't say I know what model of Compaq it is. Here's the scanpci output though; looks like it's an NCR 53C810 SCSI controller, which FreeBSD supports no problem. If anyone can identify what all this other hardware is, I'd like to hear it. Good luck. root@breadfruit{1} scanpci PCI says configuration type 2 PCI probing configuration type 1 pci bus 0x0 cardnum 0x00, vendor 0x0e11 device 0x4000 Device unknown STATUS 0x2200 COMMAND 0x0147 CLASS 0x06 0x00 0x00 REVISION 0x00 BIST 0x00 HEADER 0xff LATENCY 0x20 CACHE 0x00 BASE0 0x00f59910 addr 0x00f59910 MEM BASE1 0x00584fe0 addr 0x00584fe0 MEM BASE2 0x00842030 addr 0x00842030 MEM BASE3 0x00582020 addr 0x00582020 MEM BASE4 0x40000e11 addr 0x40000e10 I/O BASE5 0x22000147 addr 0x22000144 I/O BASEROM 0x00842070 addr 0x00840000 not-decode-enabled MAX_LAT 0x00 MIN_GNT 0x84 INT_PIN 0x20 INT_LINE 0xb0 pci bus 0x0 cardnum 0x0b, vendor 0x1022 device 0x2000 AMD 79C970 Lance STATUS 0x0200 COMMAND 0x0080 CLASS 0x02 0x00 0x00 REVISION 0x02 BASE0 0x00000001 addr 0x00000000 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x02 INT_LINE 0xff pci bus 0x0 cardnum 0x0c, vendor 0x1000 device 0x0001 NCR 53C810 STATUS 0x0200 COMMAND 0x0000 CLASS 0x01 0x00 0x00 REVISION 0x02 BASE0 0x00000001 addr 0x00000000 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0xff pci bus 0x0 cardnum 0x0f, vendor 0x0e11 device 0x0001 Device unknown STATUS 0x0200 COMMAND 0x0147 CLASS 0x06 0x02 0x00 REVISION 0x07 PCI probing configuration type 2 From owner-freebsd-hardware Wed Nov 6 17:16:03 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA13898 for hardware-outgoing; Wed, 6 Nov 1996 17:16:03 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA13868 for ; Wed, 6 Nov 1996 17:15:57 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA05984; Thu, 7 Nov 1996 11:45:24 +1030 From: Michael Smith Message-Id: <199611070115.LAA05984@genesis.atrad.adelaide.edu.au> Subject: Re: SCSI Driver To: wreynolds@kensco.net (Earl W Reynolds, Jr.) Date: Thu, 7 Nov 1996 11:45:22 +1030 (CST) Cc: cshenton@it.hq.nasa.gov, hardware@freebsd.org In-Reply-To: <199611061851.NAA06304@ns.kensco.net> from "Earl W Reynolds, Jr." at Nov 6, 96 01:36:07 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Earl W Reynolds, Jr. stands accused of saying: > > I can't run scanpci because I don't have freebsd running on the > system because it doesn't recognize the disk controller and I can't > get past that part of the installation. Is there any way you could > check your system again and see what the disk controller is? Being a Compaq you either have an NCR controller (but if you had one of those the boot floppy would have found it), or you have an AMD controller which is not (yet) supported. > Wes Reynolds Director of Technology -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Fri Nov 8 03:30:49 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA26260 for hardware-outgoing; Fri, 8 Nov 1996 03:30:49 -0800 (PST) Received: from salsa.gv.ssi1.com (salsa.gv.ssi1.com [146.252.44.194]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA26255; Fri, 8 Nov 1996 03:30:46 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.ssi1.com (8.7.5/8.7.3) id DAA19832; Fri, 8 Nov 1996 03:30:40 -0800 (PST) From: Don Lewis Message-Id: <199611081130.DAA19832@salsa.gv.ssi1.com> Date: Fri, 8 Nov 1996 03:30:40 -0800 In-Reply-To: "Jordan K. Hubbard" "The curtain is going down on 2.1-stable in 5 days!" (Nov 8, 2:09am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: "Jordan K. Hubbard" , stable@freebsd.org Subject: Re: The curtain is going down on 2.1-stable in 5 days! Cc: freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Nov 8, 2:09am, "Jordan K. Hubbard" wrote: } Subject: The curtain is going down on 2.1-stable in 5 days! } } So. David and I have decided that next Tuesday, the 12th of November, } would be an excellent time to start putting FreeBSD 2.1.6 to bed, and } if you've got any critical bug fixes or security problems to report in } 2.1-stable, now would be an excellent time to raise them before it's } too late. Security: the rwhod buffer overflow patch that's been circulating lately Bug fix: The de driver doesn't work especially well with the SMC 9332 10/100 card. About one in ten times, it is initialized to some funny state at boot time that causes the fault light on its hub to flash and all the HP-UX boxes on that hub to shut down their network interfaces. The de driver swiped from from -current a few weeks ago and butchered so that compiles under -stable seems to work perfectly. Judging by some of the comments in that version of the driver, I suspect this problem may affect other cards with the DC21140. --- Truck From owner-freebsd-hardware Fri Nov 8 05:08:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA01875 for hardware-outgoing; Fri, 8 Nov 1996 05:08:42 -0800 (PST) Received: from marlin.com.br (blue.marlin.com.br [200.255.107.33]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA01832; Fri, 8 Nov 1996 05:08:32 -0800 (PST) Received: by marlin.com.br (8.6.12/SMI-4.1) id LAA15711; Fri, 8 Nov 1996 11:05:25 -0200 Date: Fri, 8 Nov 1996 11:05:23 -0200 (EDT) From: "Alexsandro D. F. Correia" To: announce@FreeBSD.ORG cc: isp@FreeBSD.ORG, questions@FreeBSD.ORG, hardware@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Problems restoring Backups !!! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Sirs, I'm having lots of troubles with my backups, and i hope someone can HELP ME. Here we have two machines with the same configuration. Pentium 100, 32 Mb RAM, HD 2.0 gb SCSI and an EXABYTE - 4mm Cartridge tape drive Running FreeBSD 2.1. That's the problem i have. I can write to the tape, but i can't read anything from the tape. When i try to restore a backup, using tar for example my system crashes. The computer tries to access de tape, and nothing happens, waits about two minutes and then the system CRASHES. Here follows the error msg the system sends to me: ahc0:target 3,lun 0 (st0) timet out st0(ahc0:3:0):BUS DEVICE RESET message Queued. st0(ahc0:3:0):TARGET Busy ahc0:A:3:no active SCB for reconnecting target - issuing ABORT. SAVED_TCL == 0x30 ahc0:target1,lun0(sd0) timed out By the way, I tested the restore on both machines, using CPIO and TAR. But everytime i try to access something from the tape to the HD, the system crashes. Any help or information will be useful. I need to soon this problem as soon as possible. Please, I'll be very glad if someone help me. Thanx a lot. Alexsandro Correia +-------------------------------------------------------------+ Alexsandro Correia E-mail: acorreia@marlin.com.br Analista de Suporte Internet Tel : +55 21 224-9950 +55 21 253-2971 +-------------------------------------------------------------+ Marlin Internet http://www.marlin.com.br Rua 7 de Setembro 48/13 Andar Tel: +55 21 224-9950 Centro - Rio de Janeiro Fax: +55 21 223-427 RJ - Brasil +-------------------------------------------------------------+ From owner-freebsd-hardware Fri Nov 8 05:38:43 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA03418 for hardware-outgoing; Fri, 8 Nov 1996 05:38:43 -0800 (PST) Received: from groa.uct.ac.za (groa.uct.ac.za [137.158.128.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA03393; Fri, 8 Nov 1996 05:38:30 -0800 (PST) Received: by groa.uct.ac.za via sendmail with stdio id for current@freebsd.org; Fri, 8 Nov 1996 15:34:29 +0200 (SAT) (Smail-3.2 1996-Jul-4 #2 built 1996-Oct-2) Message-Id: From: rv@groa.uct.ac.za (Russell Vincent) Subject: Large RAM on ASUS P/E-P55T2P4D To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Fri, 8 Nov 1996 15:34:28 +0200 (SAT) Cc: current@freebsd.org, hardware@freebsd.org In-Reply-To: <199610291827.MAA24642@brasil.moneng.mei.com> from "Joe Greco" at Oct 29, 96 12:27:22 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Joe Greco wrote (about the ASUS P/E-P55T2P4D): > I can't get anything more than 192MB to work reliably on this board > (6 x 32MB SIMM modules) - unless we go with the mega mondo $$$$ 64MB > SIMM's.. and even those I have doubts about. We put the 4 that we > have on a P/I-P55T2P4 board and it refused to work until we relaxed > the RAM timing to 70ns. Gives me a sick feeling. Seems I may be encountering this problem on some of my 5 machines with 256MB, after all. Our supplier has just pointed me to pages 12-33 of: http://www.intel.com/design/pcisets/datashts/inte2.htm (which I am struggling to download on our poor international link). Apparently this document describes a method for increasing the current flow to DRAM (programatically) because as you put more chips into an Intel 430HX motherboard (probably any motherboard), the current flow drops, moving the trigger level (I had a nice little diagram drawn for me which would be tricky to duplicate here :-) ). This makes some sense to me (even with my poor technical knowledge) as the 4x64MB chips we are using are quite large. Reducing the DRAM timing to 70ns will also help, although, as you say, isn't suitable. If anyone does add some code for this, I would be most interested in testing it. I will try myself (when I can get the datasheet), but my programming skills are not good, so don't rely on me. :-) -Russell From owner-freebsd-hardware Fri Nov 8 08:44:34 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA21312 for hardware-outgoing; Fri, 8 Nov 1996 08:44:34 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA21303; Fri, 8 Nov 1996 08:44:25 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA12381; Fri, 8 Nov 1996 10:43:12 -0600 From: Joe Greco Message-Id: <199611081643.KAA12381@brasil.moneng.mei.com> Subject: Re: Large RAM on ASUS P/E-P55T2P4D To: rv@groa.uct.ac.za (Russell Vincent) Date: Fri, 8 Nov 1996 10:43:12 -0600 (CST) Cc: jgreco@brasil.moneng.mei.com, current@freebsd.org, hardware@freebsd.org In-Reply-To: from "Russell Vincent" at Nov 8, 96 03:34:28 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Joe Greco wrote (about the ASUS P/E-P55T2P4D): > > I can't get anything more than 192MB to work reliably on this board > > (6 x 32MB SIMM modules) - unless we go with the mega mondo $$$$ 64MB > > SIMM's.. and even those I have doubts about. We put the 4 that we > > have on a P/I-P55T2P4 board and it refused to work until we relaxed > > the RAM timing to 70ns. Gives me a sick feeling. > > Seems I may be encountering this problem on some of my 5 machines > with 256MB, after all. Our supplier has just pointed me to pages 12-33 of: > > http://www.intel.com/design/pcisets/datashts/inte2.htm > > (which I am struggling to download on our poor international link). You are really looking for the data on MAD... 3.2.13. DRAMEC - DRAM EXTENDED CONTROL REGISTER Address Offset: 56h Default Value: 00h Access: Read/Write This 8-bit register contains additional controls for main memory DRAM operating modes and features. [...] Bit Descriptions 2:1 Memory Address Drive Strength (MAD): This field controls the strength of the output buffers driving the MA and MWE# pins. Bit 2 Bit 1 MAA[1:0]/MAB[1:0] MA[11:2]/MWE# 0 0 8 mA 8mA 0 1 8 mA 12mA 1 0 12 mA 8mA 1 1 12 mA 12mA What is this? Well.. 2.2. DRAM Interface Name Type Description MA[11:2] O Memory Address: This is the row and column address 3V for DRAM. These buffers include programmable size selection. MAA[1:0] O Memory Address Copy A: One copy of the MAs that 3V change during a burst read or write of DRAM. These buffers include programmable size selection. MAB[1:0] O Memory Address Copy B: A second copy of the MAs 3V that change during a burst read or write of DRAM. These buffers include programmable size selection. MWE# O Memory Write Enable. MWE# should be used as the 3V write enable for the memory data bus. This signal has a programmable size selection (see DRAMEC[MAD] field). > Apparently this document describes a method for increasing the > current flow to DRAM (programatically) because as you put more > chips into an Intel 430HX motherboard (probably any motherboard), the > current flow drops, moving the trigger level (I had a nice little > diagram drawn for me which would be tricky to duplicate here :-) ). > This makes some sense to me (even with my poor technical knowledge) > as the 4x64MB chips we are using are quite large. Reducing the DRAM > timing to 70ns will also help, although, as you say, isn't suitable. > > If anyone does add some code for this, I would be most interested in > testing it. I will try myself (when I can get the datasheet), but > my programming skills are not good, so don't rely on me. :-) If I knew jack diddly about how to do this, I would. Failing that, I am providing this data in the hopes that some more enterprising hacker who has a clue about this sort of stuff can figure it out. However, it really seems to me like this should be a BIOS configuration option, because by the time you are loading a UNIX kernel it may already be too late to try to adjust these settings. Therefore I am cc:'ing this to ASUS Tech Support as well.. I would love to see this added as an option to all Triton-II motherboard BIOS'es. It is clearly an unusual problem, you don't see it until you have LOTS of memory. :-( ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-hardware Fri Nov 8 09:59:43 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA26204 for hardware-outgoing; Fri, 8 Nov 1996 09:59:43 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA26193; Fri, 8 Nov 1996 09:59:37 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id JAA00761; Fri, 8 Nov 1996 09:58:43 -0800 (PST) From: "Rodney W. Grimes" Message-Id: <199611081758.JAA00761@GndRsh.aac.dev.com> Subject: Re: The curtain is going down on 2.1-stable in 5 days! In-Reply-To: <199611081130.DAA19832@salsa.gv.ssi1.com> from Don Lewis at "Nov 8, 96 03:30:40 am" To: Don.Lewis@tsc.tdk.com (Don Lewis) Date: Fri, 8 Nov 1996 09:58:43 -0800 (PST) Cc: jkh@time.cdrom.com, stable@freebsd.org, freebsd-hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Nov 8, 2:09am, "Jordan K. Hubbard" wrote: > } Subject: The curtain is going down on 2.1-stable in 5 days! > } > } So. David and I have decided that next Tuesday, the 12th of November, > } would be an excellent time to start putting FreeBSD 2.1.6 to bed, and > } if you've got any critical bug fixes or security problems to report in > } 2.1-stable, now would be an excellent time to raise them before it's > } too late. > > Security: > the rwhod buffer overflow patch that's been circulating lately > > Bug fix: > The de driver doesn't work especially well with the SMC 9332 > 10/100 card. About one in ten times, it is initialized to some > funny state at boot time that causes the fault light on its > hub to flash and all the HP-UX boxes on that hub to shut down > their network interfaces. The de driver swiped from from -current > a few weeks ago and butchered so that compiles under -stable seems > to work perfectly. Judging by some of the comments in that version > of the driver, I suspect this problem may affect other cards with > the DC21140. Further notes on the if_de.c driver... D-Link has revised the DFE-500TX from revision B-1 to C-1, the card no longer works under RELENG_2_1_0, and infact behaves just like the Kingston KNE100TX card. So it now looks like the only card that I have qualified for 100MB/s operation is the SMC9332, and above is a report about problems with it :-(. Bottom line... the if_de.c driver in -stable is in need of some serious attention :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hardware Fri Nov 8 14:24:04 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA14078 for hardware-outgoing; Fri, 8 Nov 1996 14:24:04 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA14059 for ; Fri, 8 Nov 1996 14:23:50 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-45.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA27828 (5.67b/IDA-1.5 for ); Fri, 8 Nov 1996 23:23:32 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.2/8.6.9) id XAA04916; Fri, 8 Nov 1996 23:23:28 +0100 (MET) Message-Id: <199611082223.XAA04916@x14.mi.uni-koeln.de> Date: Fri, 8 Nov 1996 23:23:27 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: jacs@gnome.co.uk (Chris Stenton) Cc: hardware@freebsd.org Subject: Re: ncro 810 oops error In-Reply-To: ; from Chris Stenton on Nov 5, 1996 12:03:55 +0000 References: X-Mailer: Mutt 0.45 Mime-Version: 1.0 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chris Stenton writes: > > > I have recently upgraded to a Asus Pentium PRO Motherboard with their > NCR810 SCSI controller. While using the Amanda backup programme I am > getting a large number of errors from the controller. > > They are of the form. > > Nov 5 11:51:35 hawk /kernel: ncr?: scatter/gather failed (residue=493925376). A request to transfer some 500MB of data was issued to the driver. The scatter/gather table covers only 64KB, your memory perhaps 32MB or 64MB, so the call can't be satisfied :) The driver can't do anything about this, the parameters it receives are invalid. > They only seem to happen when it is backing up partitions other than > the root partition. > I have tried putting the Tape drive on a second controller but it made > no difference. I did not have this problem with my GigaByte Neptune > board using their NCR810 controller. This is not a hardware or controller specific problem (IMHO). You could have some file system corruption, that leads to this problem, or there could be a kernel problem (eg. missing lock). Please try a FSCK on your partitions first, and if you don't find anything, then build a kernel with a current version of /sys/pci/ncr.c. It contains some diagnostic code, which I thought might help find the cause of the out-of-bound parameter being passed ... Regards, STefan From owner-freebsd-hardware Fri Nov 8 15:26:21 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18118 for hardware-outgoing; Fri, 8 Nov 1996 15:26:21 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA18052 for ; Fri, 8 Nov 1996 15:25:38 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-47.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA28778 (5.67b/IDA-1.5 for ); Sat, 9 Nov 1996 00:23:19 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.2/8.6.9) id AAA06179; Sat, 9 Nov 1996 00:23:19 +0100 (MET) Message-Id: <199611082323.AAA06179@x14.mi.uni-koeln.de> Date: Sat, 9 Nov 1996 00:23:19 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: cshenton@it.hq.nasa.gov (Chris Shenton) Cc: wreynolds@kensco.net, hardware@FreeBSD.org Subject: Re: SCSI Drivers In-Reply-To: <199611061901.TAA24696@wirehead.it.hq.nasa.gov>; from Chris Shenton on Nov 6, 1996 14:01:24 -0500 References: <199611061848.NAA06196@ns.kensco.net> <199611061901.TAA24696@wirehead.it.hq.nasa.gov> X-Mailer: Mutt 0.45 Mime-Version: 1.0 Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Chris Shenton writes: > On Wed, 6 Nov 1996 13:32:25 +0000 > > I can't get at the machine, and I can't say I know what model of > Compaq it is. Here's the scanpci output though; looks like it's an NCR > 53C810 SCSI controller, which FreeBSD supports no problem. > > If anyone can identify what all this other hardware is, I'd like to > hear it. > root@breadfruit{1} scanpci > PCI says configuration type 2 > > PCI probing configuration type 1 Ahh, a Compaq! They don't care much for conformance to the PCI spec and caused me lots of trouble in the past (trying to get them probed correctly :( ) > pci bus 0x0 cardnum 0x00, vendor 0x0e11 device 0x4000 > Device unknown > STATUS 0x2200 COMMAND 0x0147 > CLASS 0x06 0x00 0x00 REVISION 0x00 > BIST 0x00 HEADER 0xff LATENCY 0x20 CACHE 0x00 > BASE0 0x00f59910 addr 0x00f59910 MEM > BASE1 0x00584fe0 addr 0x00584fe0 MEM > BASE2 0x00842030 addr 0x00842030 MEM > BASE3 0x00582020 addr 0x00582020 MEM > BASE4 0x40000e11 addr 0x40000e10 I/O > BASE5 0x22000147 addr 0x22000144 I/O > BASEROM 0x00842070 addr 0x00840000 not-decode-enabled > MAX_LAT 0x00 MIN_GNT 0x84 INT_PIN 0x20 INT_LINE 0xb0 This is one of Compaq's chip sets. They designed them for use in their systems, exclusively. No detailed information seems to be available about them. > pci bus 0x0 cardnum 0x0b, vendor 0x1022 device 0x2000 > AMD 79C970 Lance > STATUS 0x0200 COMMAND 0x0080 > CLASS 0x02 0x00 0x00 REVISION 0x02 > BASE0 0x00000001 addr 0x00000000 I/O > MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x02 INT_LINE 0xff An AMD PCInet/32 lance compatible Ethernet chip. Supported as device "lnc1" under -current. > pci bus 0x0 cardnum 0x0c, vendor 0x1000 device 0x0001 > NCR 53C810 > STATUS 0x0200 COMMAND 0x0000 > CLASS 0x01 0x00 0x00 REVISION 0x02 > BASE0 0x00000001 addr 0x00000000 I/O > MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0xff Yes, this is in fact a nice little 53c810 as supported by the NCR driver :) > pci bus 0x0 cardnum 0x0f, vendor 0x0e11 device 0x0001 > Device unknown > STATUS 0x0200 COMMAND 0x0147 > CLASS 0x06 0x02 0x00 REVISION 0x07 Antother Compaq specific chip, a PCI to EISA bridge according to the class code. > PCI probing configuration type 2 Didn't it say in the first line this was a config type 2 chip set ? Well, you see how much you can trust it on that: There is no device to be found, if you believed that claim ... Regards, STefan From owner-freebsd-hardware Fri Nov 8 17:34:50 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA26601 for hardware-outgoing; Fri, 8 Nov 1996 17:34:50 -0800 (PST) Received: from pegasus.com (pegasus.com [140.174.243.13]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA26590 for ; Fri, 8 Nov 1996 17:34:46 -0800 (PST) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id PAA12889; Fri, 8 Nov 1996 15:33:50 -1001 Date: Fri, 8 Nov 1996 15:33:50 -1001 From: richard@pegasus.com (Richard Foulk) Message-Id: <199611090134.PAA12889@pegasus.com> In-Reply-To: se@ZPR.Uni-Koeln.DE (Stefan Esser) "Re: ncro 810 oops error" (Nov 8, 11:23pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: se@ZPR.Uni-Koeln.DE (Stefan Esser), jacs@gnome.co.uk (Chris Stenton) Subject: Re: ncro 810 oops error Cc: hardware@FreeBSD.org Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk } > I have recently upgraded to a Asus Pentium PRO Motherboard with their } > NCR810 SCSI controller. While using the Amanda backup programme I am } > getting a large number of errors from the controller. } > } > They are of the form. } > } > Nov 5 11:51:35 hawk /kernel: ncr?: scatter/gather failed (residue=493925376). } } A request to transfer some 500MB of data was issued to the driver. } The scatter/gather table covers only 64KB, your memory perhaps 32MB } or 64MB, so the call can't be satisfied :) If the request is in error then the driver's scatter/gather mechanism shouldn't be noted as the source of the problem. From owner-freebsd-hardware Sat Nov 9 09:21:29 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA09920 for hardware-outgoing; Sat, 9 Nov 1996 09:21:29 -0800 (PST) Received: from In-Net.inba.fr (root@arthur.inba.fr [194.51.120.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA09910 for ; Sat, 9 Nov 1996 09:21:25 -0800 (PST) Received: from uther.inba.fr (uther.inba.fr [194.51.120.62]) by In-Net.inba.fr (8.6.12/8.6.9) with SMTP id SAA24568 for ; Sat, 9 Nov 1996 18:21:21 +0100 Message-Id: <1.5.4.16.19961109172801.22978780@mail.inba.fr> X-Sender: psc@mail.inba.fr X-Mailer: Windows Eudora Light Version 1.5.4 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 09 Nov 1996 18:28:01 +0100 To: freebsd-hardware@FreeBSD.ORG From: Philippe SCHACK Subject: Re: Micronics MotherBoard Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi ! I have found the problem about the micronics card. I only have to put a PCI VGA card and not an ISA VGA card. All works fine now. P.SCHACK >I have installed FreeBSD with a P75 on a Micronics D5CUB PCI/ISA card and have >the following problems: > After the install (wich runs ok) when a try to acces to the 3'5 floppy, the >system hangs without any messages. I only have to reset the system. > I have installed a Adaptec SCSI AHA-1542B card with a TANDBERG TDC-3800 Streamer . >When i boot on the BOOT FLOPPY, the system hangs after displaying a part of the >Tandberg TDC 3800 informations. From owner-freebsd-hardware Sat Nov 9 16:41:37 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA00852 for hardware-outgoing; Sat, 9 Nov 1996 16:41:37 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA00844 for ; Sat, 9 Nov 1996 16:41:34 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-39.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA23780 (5.67b/IDA-1.5 for ); Sun, 10 Nov 1996 01:40:49 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.2/8.6.9) id XAA00830; Sat, 9 Nov 1996 23:42:59 +0100 (MET) Message-Id: <199611092242.XAA00830@x14.mi.uni-koeln.de> Date: Sat, 9 Nov 1996 23:41:39 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: richard@pegasus.com (Richard Foulk) Cc: se@zpr.uni-koeln.de (Stefan Esser), jacs@gnome.co.uk (Chris Stenton), hardware@FreeBSD.org Subject: Re: ncro 810 oops error In-Reply-To: <199611090134.PAA12889@pegasus.com>; from Richard Foulk on Nov 8, 1996 15:33:50 -1001 References: <199611090134.PAA12889@pegasus.com> X-Mailer: Mutt 0.45 Mime-Version: 1.0 Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Richard Foulk writes: > } > I have recently upgraded to a Asus Pentium PRO Motherboard with their > } > NCR810 SCSI controller. While using the Amanda backup programme I am > } > getting a large number of errors from the controller. > } > > } > They are of the form. > } > > } > Nov 5 11:51:35 hawk /kernel: ncr?: scatter/gather failed (residue=493925376). > } > } A request to transfer some 500MB of data was issued to the driver. > } The scatter/gather table covers only 64KB, your memory perhaps 32MB > } or 64MB, so the call can't be satisfied :) > > If the request is in error then the driver's scatter/gather mechanism > shouldn't be noted as the source of the problem. The driver in -current contains an additional test for this condition. An error message containing the memory buffer address, the requested transfer length and the SCSI cmd is printed in that case. You are of course right, that the scatter/gather message does not give a good idea of what went wrong, but only of the place in the code were some invalid parameter finally caused a problem. I'll think about a message change for 2.1.6 which corrects this ... Regards, STefan