From owner-freebsd-hardware Sun Dec 31 06:28:54 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA05060 for hardware-outgoing; Sun, 31 Dec 1995 06:28:54 -0800 (PST) Received: from server.id.net (root@server.id.net [199.125.1.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA05055 for ; Sun, 31 Dec 1995 06:28:52 -0800 (PST) Received: (from rls@localhost) by server.id.net (8.7.1/8.7.1) id JAA01229; Sun, 31 Dec 1995 09:28:44 -0500 (EST) From: Robert Shady Message-Id: <199512311428.JAA01229@server.id.net> Subject: Re: Majordomo results To: gestur@islandia.is (Gestur A. Grjetarsson) Date: Sun, 31 Dec 1995 09:28:44 -0500 (EST) Cc: freebsd-hardware@freebsd.org, admin@islandia.is In-Reply-To: from "Gestur A. Grjetarsson" at Dec 29, 95 08:19:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org Precedence: bulk > I'd like to ask you, if someone knew that DTC-SCSI-2 VLB hdd controller > is supported by FreeBSD, I currently use 2.0.5 on my system here and I > can't find anything about this controller in the Handbook. > > If it's not supported by 2.0.5 ,,, does 2.1 approve it ? > > I have one DTC (data technology corporation) controller wich I would > like to put in use :) Correct me if I'm wrong, but I believe that the DTC VLB controller's emulate Adaptec 1542 cards, in which case, yes it would be supported by FreeBSD. I vaguely seem to remember pulling one of these cards out of one of our FreeBSD workstations recently... -- Rob === _/_/_/_/_/ _/_/_/_/ _/_/ _/ _/_/_/_/_/ _/_/_/_/_/ _/ _/ _/ _/_/_/ _/ _/ _/ _/_/_/_/ _/ _/_/_/_/_/ _/_/_/_/ _/ _/ _/_/_/_/_/ _/ Innovative Data Services Serving South-Eastern Michigan Internet Service Provider / Hardware Sales / Consulting Services Voice: (810)855-0404 / Fax: (810)855-3268 / Web: http://www.id.net From owner-freebsd-hardware Sun Dec 31 07:42:53 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA11029 for hardware-outgoing; Sun, 31 Dec 1995 07:42:53 -0800 (PST) Received: from hda.com (hda.com [199.232.40.182]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA11019 for ; Sun, 31 Dec 1995 07:42:48 -0800 (PST) Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id KAA25436; Sun, 31 Dec 1995 10:51:39 -0500 From: Peter Dufault Message-Id: <199512311551.KAA25436@hda.com> Subject: Re: Majordomo results To: rls@kilroy.id.net (Robert Shady) Date: Sun, 31 Dec 1995 10:51:38 -0500 (EST) Cc: gestur@islandia.is, freebsd-hardware@FreeBSD.ORG, admin@islandia.is In-Reply-To: <199512311428.JAA01229@server.id.net> from "Robert Shady" at Dec 31, 95 09:28:44 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@FreeBSD.ORG Precedence: bulk > > Correct me if I'm wrong, but I believe that the DTC VLB controller's > emulate Adaptec 1542 cards, in which case, yes it would be supported > by FreeBSD. I vaguely seem to remember pulling one of these cards out > of one of our FreeBSD workstations recently... > > -- Rob It might emulate a 1542, but that would limit you to 16MB without bounce buffers or a custom driver since the 1542 programming interface is 3 byte addresses. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-hardware Sun Dec 31 09:32:17 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA14306 for hardware-outgoing; Sun, 31 Dec 1995 09:32:17 -0800 (PST) Received: from jthome.jthome.com (jthome.jthome.com [199.232.37.49]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA14301 for ; Sun, 31 Dec 1995 09:32:08 -0800 (PST) Received: (from jeff@localhost) by jthome.jthome.com (8.6.11/8.6.6) id MAA01539 for hardware@freebsd.org; Sun, 31 Dec 1995 12:32:04 -0500 From: Jeff Tyler Message-Id: <199512311732.MAA01539@jthome.jthome.com> Subject: Problems with a DX4/100 in a Micronics JX30WB VL/ISA mb To: hardware@freebsd.org Date: Sun, 31 Dec 1995 12:32:03 -0500 (EST) Organization: Never touch the stuff ... Location: Eight miles from the rude bridge that arched the flow ... Phone: (508)-440-8624 System: FreeBSD jthome.jthome.com 2.0.5-RELEASE X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@freebsd.org Precedence: bulk Hi, I just upgraded to a dx4/100 on a Micronics JX30WB vl/isa motherboard and I've had some problems getting the system to stabilize. At first I couldn't even get the board to stay up long enough to let me into the CMOS setup utility, it was locking up right and left. A bit of checking showed that the clock speed jumper (w10) was in the 33Mhz position so I moved it to the 25Mhz strapping. Things got a bit better after that but I was still getting lockups and crashes under both DOS and Freebsd. Cooking the board overnight seems to have helped quite a bit, I've only had one crash this morning but I did have that one. The error msg is something like: I/O card parity interrupt at F000:FFF0 right after the panic message. The I get a line offering me the choice of S or R where S turns of the NMI and r reboots but the machine is locked up tight at that point forcing a power cycle. I only have an adaptec 1542CF, a 16bit ethernet card and an old ISA vga card in this puppy and I can't seem to find any interrupt or DMA conflicts (all cards set the same way that they were in the old 386 I upgraded from). Another very strange thing, after stepping the speed down to 25 Mhz, the CMOS setup reports a dx4/75 ! Not a 4dx/100. Very strange. I have checked cpu select jumpers, they seem to be ok for a dx4. So I'm very confused at this point, any help or suggestions will be gratefully received here :-) dmsg output follows: FreeBSD 2.0.5-RELEASE #0: Sat Dec 30 16:18:06 EST 1995 root@:/usr/src/sys/compile/JTHOME CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 33161216 (8096 pages) avail memory = 30683136 (7491 pages) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:a5:59:5b, type WD8013EPC (16 bit) bpf: ed0 attached ed1 not probed due to maddr conflict with ed0 at 0xd8000 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 not found at 0x3e8 sio3 not found at 0x2e8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found at 0xffffffff lpt2 not found at 0xffffffff fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 wdc1 not found at 0x170 bt0 not found at 0x330 uha0 not found at 0x330 ahc1 not found ahb0 not found aha0: AHA-1542CF BIOS v2.01-VB.0, enabling mailbox, enabling residuals aha0: reading board settings, dma=5 int=11 (bus speed defaulted) aha0 at 0x330-0x333 irq 11 drq 5 on isa aha0 waiting for scsi devices to settle (aha0:0:0): "SEAGATE ST31200N 8648" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 1006MB (2061108 512 byte sectors) (aha0:1:0): "SEAGATE ST31230N 0170" type 0 fixed SCSI 2 sd1(aha0:1:0): Direct-Access 1010MB (2069860 512 byte sectors) (aha0:2:0): "QUANTUM FIREBALL1080S 1Q09" type 0 fixed SCSI 2 sd2(aha0:2:0): Direct-Access 1042MB (2134305 512 byte sectors) (aha0:3:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1 st0(aha0:3:0): Sequential-Access st0: Archive Viper 150 is a known rogue density code 0x0, drive empty (aha0:4:0): "DEC RRD42 (C) DEC 4.3d" type 5 removable SCSI 2 cd0(aha0:4:0): CD-ROM cd present.[1057708 x 512 byte records] aic0 not found at 0x340 nca0 not found at 0x1f88 nca1 not found at 0x350 sea0 not found scd0 not found at 0x230 ie0 not found at 0x360 ep0 not found at 0x300 ix0 not found at 0x300 le0: no board found at 0x300 le0 not found at 0x300 lnc0 not probed due to I/O address conflict with ed0 at 0x280 lnc1 not found at 0x300 ze0 not probed due to maddr conflict with ed0 at 0xd8000 zp0 not probed due to maddr conflict with ed0 at 0xd8000 npx0 on motherboard npx0: INT 16 interface bpf: lo0 attached bpf: sl0 attached bpf: tun0 attached -- ======================================================================== |Jeff S. Tyler Pencom System Administration| |PSA all the way ! [At Digital] 508-486-5369 | |jeff@jthome.com [Home phone/fax] 508-440-8624/8625 | |jtyler@pencom.com [Pager] 1-800-759-8888 249-5568 | | -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | |Tis better to have hacked and crashed than never to have hacked at all| ======================================================================== From owner-freebsd-hardware Sun Dec 31 16:38:06 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA28445 for hardware-outgoing; Sun, 31 Dec 1995 16:38:06 -0800 (PST) Received: from else (root@else.net [204.92.4.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA28421 Sun, 31 Dec 1995 16:37:48 -0800 (PST) Received: by else (Smail3.1.29.1 #3) id m0tWYHA-000MFTC; Sun, 31 Dec 95 19:38 EST Date: Sun, 31 Dec 1995 19:38:56 -0500 (EST) From: James FitzGibbon To: questions@freebsd.org cc: hardware@freebsd.org Subject: Support for a Cabletron E20xx adapter? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org Precedence: bulk Has anyone got support for a Cabletron E20xx adapter working under 2.1? I've got it to work under Win95, however the card is salvage from a used PC, so i'm not sure whether it supports a more generic interface like NE2000. If I try to configure it as NE2000, it locks the system bootup. j.