From owner-freebsd-hardware Sun Mar 17 16:01:36 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA15953 for hardware-outgoing; Sun, 17 Mar 1996 16:01:36 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA15927 Sun, 17 Mar 1996 16:01:31 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id SAA25321; Sun, 17 Mar 1996 18:00:15 -0600 From: Joe Greco Message-Id: <199603180000.SAA25321@brasil.moneng.mei.com> Subject: Re: comtrol rocketports To: michael@memra.com (Michael Dillon) Date: Sun, 17 Mar 1996 18:00:15 -0600 (CST) Cc: jgreco@brasil.moneng.mei.com, erich@basenet.com, freebsd-hardware@FreeBSD.org, freebsd-isp@FreeBSD.org In-Reply-To: from "Michael Dillon" at Mar 16, 96 11:39:35 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > And what's wrong with building special-purpose terminal servers out of > Linux boxes and using FreeBSD for all the other servers? After all, Linux > is UNIX too and all a terminal server needs to do is run a bunch of serial > ports and maybe a few rlogins to a FreeBSD shell server. In a word: "reliability". ... JG From owner-freebsd-hardware Sun Mar 17 20:41:29 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA28138 for hardware-outgoing; Sun, 17 Mar 1996 20:41:29 -0800 (PST) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA28119 Sun, 17 Mar 1996 20:41:21 -0800 (PST) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id NAA05905; Mon, 18 Mar 1996 13:41:08 +0900 Date: Mon, 18 Mar 1996 13:41:08 +0900 Message-Id: <199603180441.NAA05905@frig.mt.cs.keio.ac.jp> To: hackers@freebsd.org, hardware@freebsd.org Reply-To: hackers@freebsd.org Subject: [PCMCIA] pccard-test-960318 is now available (bug-fix) From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We release pccard-test-960318 package for FreeBSD 2.1.0-RELEASE and 2.2-960303-SNAP. You can find it at, Anonymous FTP: "ftp://bash.cc.keio.ac.jp/pub/os/FreeBSD/alpha-test/pccard/pccard-test-960318.tar.gz" or WWW page: "http://www.mt.cs.keio.ac.jp/person/hosokawa/freebsd-pcmcia/" pccard-test-960314 has some minor problems with installation documents and /etc stuffs, and it also has some careless bugs because it's the first release based on FreeBSD 2.2-SNAP. pccard-test-960318 is bug-fix release of pccard-test-960314. The diffs relative to 960314 are in the subdirectory upgrade-from-960314. But I've not made upgrade-patches of /etc stuffs. Please install them in ordinary way. -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan From owner-freebsd-hardware Mon Mar 18 01:35:44 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA12138 for hardware-outgoing; Mon, 18 Mar 1996 01:35:44 -0800 (PST) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA12131 Mon, 18 Mar 1996 01:35:40 -0800 (PST) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id SAA09335; Mon, 18 Mar 1996 18:35:32 +0900 Date: Mon, 18 Mar 1996 18:35:32 +0900 Message-Id: <199603180935.SAA09335@frig.mt.cs.keio.ac.jp> To: hackers@freebsd.org Cc: hardware@freebsd.org Subject: Re: [PCMCIA] pccard-test-960318 is now available (bug-fix) In-Reply-To: Your message of Mon, 18 Mar 1996 13:41:08 +0900. <199603180441.NAA05905@frig.mt.cs.keio.ac.jp> From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199603180441.NAA05905@frig.mt.cs.keio.ac.jp> hosokawa@mt.cs.keio.ac.jp writes: I found some bugs were still remained in README's, so I fixed it now. The package of bash.cc.keio.ac.jp are replaced with the newer one, and If you have already got this package, new README's can be read at WWW page of this package. The URL is, >> "http://www.mt.cs.keio.ac.jp/person/hosokawa/freebsd-pcmcia/" I'll put the package at freefall later. -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan From owner-freebsd-hardware Mon Mar 18 05:33:04 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA21907 for hardware-outgoing; Mon, 18 Mar 1996 05:33:04 -0800 (PST) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA21902 for ; Mon, 18 Mar 1996 05:33:02 -0800 (PST) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id IAA04463; Mon, 18 Mar 1996 08:32:31 -0500 Date: Mon, 18 Mar 1996 08:32:31 -0500 (EST) From: "Ron G. Minnich" To: hardware@freebsd.org Subject: support for dell latitude or new gateway or micron? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk anybody tried freebsd on any of these? dell reviews show very good battery life. Gateway reviews show good battery life and nice multimedia features. Micron was recommended to me by a friend. Anybody have access to one of these guys? I assume the thinkpad 760 is out since the modem is a dsp, and i don't expect any free drivers to be floating around ... thanks to all who responded. ron Ron Minnich |" Microsoft Word: It does so little and it does rminnich@sarnoff.com | it so slowly" -- Maya Gokhale (609)-734-3120 | ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html From owner-freebsd-hardware Mon Mar 18 07:56:13 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA01210 for hardware-outgoing; Mon, 18 Mar 1996 07:56:13 -0800 (PST) Received: from psiint.com (vv.psiint.com [204.189.53.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA01192 for ; Mon, 18 Mar 1996 07:56:08 -0800 (PST) Received: by psiint.com (8.6.12/4.03) id HAA42067; Mon, 18 Mar 1996 07:55:34 -0800 Date: Mon, 18 Mar 1996 07:55:34 -0800 (PST) From: Dave Walton To: "Rodney W. Grimes" cc: Fred Cawthorne , freebsd-hardware@freebsd.org Subject: Re: Intel Apache Motherboard???? In-Reply-To: <199603160049.QAA17299@GndRsh.aac.dev.com> 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 Fri, 15 Mar 1996, Rodney W. Grimes wrote: > > What is the Pentium Pro board of choice now? > > NONE! The Orion chip set is seriously flawed in several design aspects, > and even the B0 stepping will not fix these flaws. Until the second > generation P6 chip sets come out of Intel my advice on Pentium Pro is > simply _don't_ do it. On a related note, what is the Pentium board of choice now? Dave ========================================================================== David Walton Unix Programmer PSI INTERNATIONAL, Inc. email: dwalton@psiint.com 190 South Orchard #C200 Fax :(707)451-6484 Vacaville, CA 95688 Phone:(707)451-3503 ========================================================================== From owner-freebsd-hardware Mon Mar 18 07:56:54 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA01303 for hardware-outgoing; Mon, 18 Mar 1996 07:56:54 -0800 (PST) Received: from bacall.lodgenet.com ([205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA01262 Mon, 18 Mar 1996 07:56:37 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id JAA07629; Mon, 18 Mar 1996 09:51:49 -0600 Received: from tserv.lodgenet.com(204.124.120.10) by bacall via smap (V1.3) id sma007627; Mon Mar 18 09:51:40 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id IAA26905; Mon, 18 Mar 1996 08:52:09 -0600 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.4/8.6.12) with SMTP id JAA04029; Mon, 18 Mar 1996 09:04:13 -0600 (CST) Message-Id: <199603181504.JAA04029@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Joe Greco cc: erich@basenet.com (Eric Hester), freebsd-hardware@FreeBSD.org, freebsd-isp@FreeBSD.org Subject: Re: comtrol rocketports In-reply-to: Your message of "Sat, 16 Mar 1996 09:45:46 CST." <199603161545.JAA24201@brasil.moneng.mei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Mar 1996 09:04:13 -0600 From: "Eric L. Hernes" Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk We've been bombarded by serial vendors in the last 4 months or so. We are currently buying digi pc/8e's; we buy between 75 - 100 cards a month for our systems. We're in the process of migrating from SCO to FreeBSD. We've talked to digi, stallion, equinox, and comtrol, and maybe others. The salesman from comtrol was really excited about his card and wanted to send an engineer up to visit us and really show off their cards, I told him that he'd do better to get me a FreeBSD driver before he sent an engineer here; we haven't heard from him since :( At any rate I've personally seen the following intelligent serial cards work: Digi: PC/8e -- works quite well from what I've seen; a little more cpu intensive under FBSD than SCO, but works good. I've used both 64k and 8k windowed cards. Stallion: EasyConnect AT and PCI -- works very well, driver is actively worked on by a stallion employee! I'm gonna push for a switch to this one when we finally make the switch to FBSD. These support up to 32 ports from one isa/pci slot. EasyIO -- This is the moderately intelligent card based on the Cirrus CD1440 chip. The card is very similar to the Cyclades 8Y, RJ12's off the back (probably available in db{9,25} too). this card is cheap $200/8ports. Cyclades: 8Y -- I've seen it work. Didn't really beat on it, but it works. It's in the $200 price range. I've seen a few messages regarding the comtrol cards. Someone (julian?) indicated that comtrol isn't too bad a company to work with as far as getting programming specs and sample sources. Getting a working driver should only be a 2-3 week project provided one is a driver hacker, and has access to hardware and docs; oh yea and has that much free time. ;-) eric. -- erich@lodgenet.com erich@rrnet.com From owner-freebsd-hardware Mon Mar 18 08:40:31 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA04799 for hardware-outgoing; Mon, 18 Mar 1996 08:40:31 -0800 (PST) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA04781 Mon, 18 Mar 1996 08:40:22 -0800 (PST) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id BAA11624; Tue, 19 Mar 1996 01:40:14 +0900 Date: Tue, 19 Mar 1996 01:40:14 +0900 Message-Id: <199603181640.BAA11624@frig.mt.cs.keio.ac.jp> To: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: [PCMCIA] pccard-test-960318 is now available (bug-fix) In-Reply-To: Your message of Mon, 18 Mar 1996 18:35:32 +0900. <199603180935.SAA09335@frig.mt.cs.keio.ac.jp> From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I'll put the package at freefall later. Done. ftp://freefall.freebsd.org/incoming/pccard-test-960318.tar.gz -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan From owner-freebsd-hardware Mon Mar 18 09:06:29 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA06317 for hardware-outgoing; Mon, 18 Mar 1996 09:06:29 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA06310 for ; Mon, 18 Mar 1996 09:06:26 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id JAA20110; Mon, 18 Mar 1996 09:05:57 -0800 From: "Rodney W. Grimes" Message-Id: <199603181705.JAA20110@GndRsh.aac.dev.com> Subject: Re: Intel Apache Motherboard???? To: dwalton@psiint.com (Dave Walton) Date: Mon, 18 Mar 1996 09:05:57 -0800 (PST) Cc: fcawth@jjarray.umd.edu, freebsd-hardware@freebsd.org In-Reply-To: from "Dave Walton" at Mar 18, 96 07:55:34 am 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 X-Loop: FreeBSD.org Precedence: bulk > > On Fri, 15 Mar 1996, Rodney W. Grimes wrote: > > > > What is the Pentium Pro board of choice now? > > > > NONE! The Orion chip set is seriously flawed in several design aspects, > > and even the B0 stepping will not fix these flaws. Until the second > > generation P6 chip sets come out of Intel my advice on Pentium Pro is > > simply _don't_ do it. > > On a related note, what is the Pentium board of choice now? I am currently using either the ASUS PCI/I-P55TP4XEG or the PCI/I-P55TP4N for production runs. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Mon Mar 18 13:56:44 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA26491 for hardware-outgoing; Mon, 18 Mar 1996 13:56:44 -0800 (PST) Received: from distortion.eng.umd.edu (distortion.eng.umd.edu [129.2.98.6]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA26470 for ; Mon, 18 Mar 1996 13:56:37 -0800 (PST) Received: from gilligan.eng.umd.edu (gilligan.eng.umd.edu [129.2.98.205]) by distortion.eng.umd.edu (8.7.5/8.7.3) with ESMTP id QAA23286; Mon, 18 Mar 1996 16:55:58 -0500 (EST) Received: (from chuckr@localhost) by gilligan.eng.umd.edu (8.7.5/8.7.3) id QAA00278; Mon, 18 Mar 1996 16:55:58 -0500 (EST) Date: Mon, 18 Mar 1996 16:55:58 -0500 (EST) From: Chuck Robey X-Sender: chuckr@gilligan.eng.umd.edu To: "Rodney W. Grimes" cc: Dave Walton , fcawth@jjarray.umd.edu, freebsd-hardware@FreeBSD.org Subject: Re: Intel Apache Motherboard???? In-Reply-To: <199603181705.JAA20110@GndRsh.aac.dev.com> 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 Mon, 18 Mar 1996, Rodney W. Grimes wrote: > > > > On Fri, 15 Mar 1996, Rodney W. Grimes wrote: > > > > > > What is the Pentium Pro board of choice now? > > > > > > NONE! The Orion chip set is seriously flawed in several design aspects, > > > and even the B0 stepping will not fix these flaws. Until the second > > > generation P6 chip sets come out of Intel my advice on Pentium Pro is > > > simply _don't_ do it. > > > > On a related note, what is the Pentium board of choice now? > > I am currently using either the ASUS PCI/I-P55TP4XEG or the PCI/I-P55TP4N > for production runs. Out of curiosity (and future upgrade budgeting) what speed memories do those buys need? > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Reliable computers for FreeBSD > ========================================================================== Chuck Robey chuckr@eng.umd.edu, I run FreeBSD-current on n3lxx + Journey2 Three Accounts for the Super-users in the sky, Seven for the Operators in their halls of fame, Nine for Ordinary Users doomed to crie, One for the Illegal Cracker with his evil game In the Domains of Internet where the data lie. One Account to rule them all, One Account to watch them, One Account to make them all and in the network bind them. From owner-freebsd-hardware Mon Mar 18 14:11:04 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA29665 for hardware-outgoing; Mon, 18 Mar 1996 14:11:04 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA29646 for ; Mon, 18 Mar 1996 14:11:00 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id OAA20449; Mon, 18 Mar 1996 14:08:50 -0800 From: "Rodney W. Grimes" Message-Id: <199603182208.OAA20449@GndRsh.aac.dev.com> Subject: Re: Intel Apache Motherboard???? To: chuckr@Glue.umd.edu (Chuck Robey) Date: Mon, 18 Mar 1996 14:08:49 -0800 (PST) Cc: dwalton@psiint.com, fcawth@jjarray.umd.edu, freebsd-hardware@FreeBSD.org In-Reply-To: from "Chuck Robey" at Mar 18, 96 04:55: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 X-Loop: FreeBSD.org Precedence: bulk > > On Mon, 18 Mar 1996, Rodney W. Grimes wrote: > > > > > > > On Fri, 15 Mar 1996, Rodney W. Grimes wrote: > > > > > > > > What is the Pentium Pro board of choice now? > > > > > > > > NONE! The Orion chip set is seriously flawed in several design aspects, > > > > and even the B0 stepping will not fix these flaws. Until the second > > > > generation P6 chip sets come out of Intel my advice on Pentium Pro is > > > > simply _don't_ do it. > > > > > > On a related note, what is the Pentium board of choice now? > > > > I am currently using either the ASUS PCI/I-P55TP4XEG or the PCI/I-P55TP4N > > for production runs. > > Out of curiosity (and future upgrade budgeting) what speed memories do > those buys need? This depends upon which CPU you use, if the external clock of the CPU is 60MHz or less (ie, 75, 90, 120, 150MHz CPU) they require 70nS memory. If the exteral clock is 66MHz (ie, 100, 133, 166MHz CPU) they require 60nS memory. Given the very small delta between 60 and 70nS memory I don't even sell 70nS memory anymore. If you wish to carry your memory to your next machine and you are buying a substantial amount of memory I would suggest spending the money to put x36 parts in now. Quite often when you upgrade it is a MB/CPU/Memory type upgrade and spending money now may not be such a great idea depending on how soon you plan to upgrade. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Tue Mar 19 01:01:34 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA15698 for hardware-outgoing; Tue, 19 Mar 1996 01:01:34 -0800 (PST) Received: from aztec.co.za (aztec.co.za [196.7.70.131]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA15658 for ; Tue, 19 Mar 1996 01:01:17 -0800 (PST) Received: from pcmgate.pcm.co.za [196.3.254.241] by aztec.co.za with smtp (Smail3.1.29.1 #2) id m0tyxG3-000aoFC; Tue, 19 Mar 96 10:59 EET Received: from IRVINEP5 (irvinep5.pcm.co.za [196.3.226.90]) by pcmgate.pcm.co.za (8.6.12/8.6.12) with SMTP id KAA17859 for ; Tue, 19 Mar 1996 10:55:00 +0200 Message-Id: <199603190855.KAA17859@pcmgate.pcm.co.za> Comments: Authenticated sender is From: "Irvine Short" Organization: Professional Computer Manufacturers To: hardware@freebsd.org Date: Tue, 19 Mar 1996 10:58:16 +2 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Need Docs on Arnet Multiport X-Confirm-Reading-To: "Irvine Short" X-pmrqc: 1 Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi All I have inherited an ARNET Multiport On the PCB it says MULTI-4 REV.2 and Copyright 1986. It was tested at the factory on 2-20-89 It has the following: 4 x 8250 a daughterboard that has another 4 x 8250 A break-out box with 8 female DB-25's labeled P1 to P8 S1 5 DIP sw S2 7 DIP sw S3 6 DIP sw and a jumper that has two positions, A and B The break-out box has loads of jumpers that are duplicated for each port. Each port has jumpers labelled: T/R RTS/CTS DTR/DSR RI/DCD I guess I can remove the 8250's and replace them with 16550's OK? TIA Regards, Irvine Short http://www.pcm.co.za/homepage/ishort/irv_home.html Technical Support Professional Computer Manufacturers Cape Town, South Africa Tel: ++27-21-235084 Fax ++27-21-235089 From owner-freebsd-hardware Tue Mar 19 01:42:48 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA17450 for hardware-outgoing; Tue, 19 Mar 1996 01:42:48 -0800 (PST) Received: from chaini.sita.kiev.ua (sita-carrier.sita.kiev.ua [193.124.50.33]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA17433 for ; Tue, 19 Mar 1996 01:42:19 -0800 (PST) Received: from tav.kiev.ua (tav-sita.tav.kiev.ua [194.135.250.33]) by chaini.sita.kiev.ua (Sendmail 8.who.cares/5) with ESMTP id LAA12420; Tue, 19 Mar 1996 11:39:26 +0200 Received: (from root@localhost) by tav.kiev.ua (8.6.12/5) id LAA02903; Tue, 19 Mar 1996 11:26:57 +0200 Date: Tue, 19 Mar 1996 11:26:57 +0200 From: Oleg N Panashchenko Message-Id: <199603190926.LAA02903@tav.kiev.ua> To: erich@lodgenet.com (Eric L. Hernes) Cc: freebsd-hardware@freebsd.org Subject: Re: comtrol rocketports Organization: Maxis Labs X-Newsreader: TIN [version 1.2 PL2] Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199603181504.JAA04029@jake.lodgenet.com> you wrote: : At any rate I've personally seen the following intelligent serial : cards work: : Digi: : PC/8e -- works quite well from what I've seen; a little more cpu : intensive under FBSD than SCO, but works good. I've used : both 64k and 8k windowed cards. 2.1R, -current and -stable have 'alpha quality' driver for Digi PC/Xe family. It has problems on overloaded channels. I've tried to fix it ( and make it less cpu intensive too) - you can find a version at ftp.cdrom.com/pub/FreeBSD/incoming/dgb_helg-Feb19.tgz I was reported that this version is working fine until you don't have more than one Digi board in the box. I tried to fix this problem, but still not have a responce from those, who is testing it. Does anybody want to test it? Oleg From owner-freebsd-hardware Tue Mar 19 06:48:33 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA04965 for hardware-outgoing; Tue, 19 Mar 1996 06:48:33 -0800 (PST) Received: from aztec.co.za (aztec.co.za [196.7.70.131]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA04953 for ; Tue, 19 Mar 1996 06:48:18 -0800 (PST) Received: from pcmgate.pcm.co.za [196.3.254.241] by aztec.co.za with smtp (Smail3.1.29.1 #2) id m0tz2gF-000arFC; Tue, 19 Mar 96 16:46 EET Received: from IRVINEP5 (irvinep5.pcm.co.za [196.3.226.90]) by pcmgate.pcm.co.za (8.6.12/8.6.12) with SMTP id QAA18445; Tue, 19 Mar 1996 16:42:21 +0200 Message-Id: <199603191442.QAA18445@pcmgate.pcm.co.za> Comments: Authenticated sender is From: "Irvine Short" Organization: Professional Computer Manufacturers To: Glen Foster Date: Tue, 19 Mar 1996 16:45:32 +2 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Need Docs on Arnet Multiport CC: hardware@freebsd.org X-Confirm-Reading-To: "Irvine Short" X-pmrqc: 1 Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Glen and All Thanks for the reply... > A client of mine has a "StarGate 8" (ARNET and StarGate are the same > company) and it works fine with FreeBSD 2.1R. When I was putting it > into his machine I talked to an engineer at the factory who said that > all their boards are "driver compatible" with AST's so yours should > work with FreeBSD too. Good to hear. It is actually listed in the list of compatible devices, so I feel quite safe. > He had the factory upgrade the board to 16550's (before I got my hands > on it) and I don't think they changed anything else on the board. His > is a newer board than your, circa 1989, yours may be harder to > integrate. It's worth a try anyway. Basically, I just compiled up a > kernel with COM_MULTIPORT and the right settings for the sio devices > and it came right up. Well, I intend doing the 16550 upgrade myself, so it should be the same effect. I do need the DIP switch settings though so I can set the right settings for the sio driver. . > You should have one more UART on the board than you describe below, > one for each serial port and the one that talks back to the PC. This > may have to be upgraded also unless they are using some other scheme > to interface with the PC. Are you sure? One of my subjects at colledge was digital electronics and I don't really see how 4 UARTS interface to 1... Enlighten me! Thanks again, Regards, Irvine Short http://www.pcm.co.za/homepage/ishort/irv_home.html Technical Support Professional Computer Manufacturers Cape Town, South Africa Tel: ++27-21-235084 Fax ++27-21-235089 From owner-freebsd-hardware Tue Mar 19 07:11:35 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA07091 for hardware-outgoing; Tue, 19 Mar 1996 07:11:35 -0800 (PST) Received: from bacall.lodgenet.com ([205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA07071 for ; Tue, 19 Mar 1996 07:11:31 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id JAA00059 for ; Tue, 19 Mar 1996 09:06:32 -0600 Received: from tserv.lodgenet.com(204.124.120.10) by bacall via smap (V1.3) id sma000052; Tue Mar 19 09:06:26 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id IAA05000; Tue, 19 Mar 1996 08:33:27 -0600 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.4/8.6.12) with SMTP id IAA06784; Tue, 19 Mar 1996 08:45:30 -0600 (CST) Message-Id: <199603191445.IAA06784@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Oleg N Panashchenko cc: erich@lodgenet.com (Eric L. Hernes), freebsd-hardware@freebsd.org Subject: Re: comtrol rocketports In-reply-to: Your message of "Tue, 19 Mar 1996 11:26:57 +0200." <199603190926.LAA02903@tav.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Mar 1996 08:45:30 -0600 From: "Eric L. Hernes" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Oleg N Panashchenko writes: >In article <199603181504.JAA04029@jake.lodgenet.com> you wrote: > >: At any rate I've personally seen the following intelligent serial >: cards work: > >: Digi: >: PC/8e -- works quite well from what I've seen; a little more cpu >: intensive under FBSD than SCO, but works good. I've used >: both 64k and 8k windowed cards. > >2.1R, -current and -stable have 'alpha quality' driver for Digi PC/Xe family. >It has problems on overloaded channels. > >I've tried to fix it ( and make it less cpu intensive too) - you can find >a version at ftp.cdrom.com/pub/FreeBSD/incoming/dgb_helg-Feb19.tgz > I've still got your post to -hackers in my inbox, haven't had a chance to look at it yet. I've just finished, well as finished as a driver ever is, a driver for one of our proprietary boards which is based on a digi, I've got a pretty good idea of how the card works. Maybe I'll have a look at it, when I get a chance. >I was reported that this version is working fine until you don't have >more than one Digi board in the box. I tried to fix this problem, but still >not have a responce from those, who is testing it. Does anybody want to >test it? Am I reading that correctly-- that your driver works with more than one card, but not with only one card? > >Oleg eric. -- erich@lodgenet.com erich@rrnet.com From owner-freebsd-hardware Tue Mar 19 09:41:17 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA17742 for hardware-outgoing; Tue, 19 Mar 1996 09:41:17 -0800 (PST) Received: from chaini.sita.kiev.ua (sita-carrier.sita.kiev.ua [193.124.50.33]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA17710 for ; Tue, 19 Mar 1996 09:40:48 -0800 (PST) Received: from tav.kiev.ua (tav-sita.tav.kiev.ua [194.135.250.33]) by chaini.sita.kiev.ua (Sendmail 8.who.cares/5) with ESMTP id TAA03587; Tue, 19 Mar 1996 19:40:03 +0200 Received: (from helg@localhost) by tav.kiev.ua (8.6.12/5) id TAA16120; Tue, 19 Mar 1996 19:28:10 +0200 To: erich@lodgenet.com Cc: freebsd-hardware@freebsd.org References: <199603191445.IAA06784@jake.lodgenet.com> From: Oleg N Panashchenko Organization: Maxis Labs Date: Tue, 19 Mar 96 19:28:09 +0200 Message-Id: Subject: Re: comtrol rocketports X-Mailer: BML [UNIX Beauty Mail v.1.39] Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Oleg N Panashchenko writes: > >In article <199603181504.JAA04029@jake.lodgenet.com> you wrote: > > >I was reported that this version is working fine until you don't have > >more than one Digi board in the box. I tried to fix this problem, but still > >not have a responce from those, who is testing it. Does anybody want to > >test it? > > Am I reading that correctly-- that your driver works with more than one > card, but not with only one card? dgb_helg-Feb19.tgz works fine with one card. It does not work with two cards. I will send corrected version to anybody, who want to test it. Unfortunately it is impossible to test it here, because I don't have two cards. > eric. > -- > erich@lodgenet.com > erich@rrnet.com Oleg From owner-freebsd-hardware Tue Mar 19 22:19:10 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA06512 for hardware-outgoing; Tue, 19 Mar 1996 22:19:10 -0800 (PST) Received: from optim.ism.net (optim.ism.net [205.199.12.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA06507 for ; Tue, 19 Mar 1996 22:19:05 -0800 (PST) Received: from [205.199.12.47] (slip7.ism.net [205.199.12.47]) by optim.ism.net (8.6.12/8.6.12) with SMTP id XAA16428 for ; Tue, 19 Mar 1996 23:20:57 -0700 X-Sender: russ@ism.net (Unverified) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 18 Mar 1996 23:21:08 -0600 To: freebsd-hardware@freebsd.org From: russ@ism.net (Russ Pagenkopf) Subject: help with new motherboard Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Feedback please, I'm getting desperate. Equipment Intel Atlantis Pentium 100 motherboard 32 meg RAM Buslogic 545c 3Com 3C509B ethernet card Mitsumi 4X cd-rom The problem: Using either the boot.flp or the atapi.flp disk the install will go through uncompressing the kernel, go to bold white with CPU:, start probing and gets to (I think, the bloody thing goes too fast to keep up) probing the ISA bus, resets and locks up (clears the screen and freezes, puts the monitor in energy-saving mode, only a power off/on or reset will bring it back). In desperation I've pulled the Buslogic Card, the 3Com, the CD-ROM, it's down to just the floppy and no joy, same thing everytime. Am I screwed? TIA rus ps. no conflicts that I can find, besides pulling stuff should eliminate that, and yes it all works fine in DOS :-( Russ Pagenkopf (russ@ism.net) From owner-freebsd-hardware Tue Mar 19 23:23:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA09802 for hardware-outgoing; Tue, 19 Mar 1996 23:23:42 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA09796 for ; Tue, 19 Mar 1996 23:23:36 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id SAA06342; Wed, 20 Mar 1996 18:07:21 +1030 From: Michael Smith Message-Id: <199603200737.SAA06342@genesis.atrad.adelaide.edu.au> Subject: Re: help with new motherboard To: russ@ism.net (Russ Pagenkopf) Date: Wed, 20 Mar 1996 18:07:21 +1030 (CST) Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: from "Russ Pagenkopf" at Mar 18, 96 11:21: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 Russ Pagenkopf stands accused of saying: > > Feedback please, I'm getting desperate. ... > Using either the boot.flp or the atapi.flp disk the install will go through > uncompressing the kernel, go to bold white with CPU:, start probing and > gets to (I think, the bloody thing goes too fast to keep up) probing the > ISA bus, resets and locks up (clears the screen and freezes, puts the > monitor in energy-saving mode, only a power off/on or reset will bring it > back). You don't say what video card; my guess is you have a Mach64 in there somewhere. > Russ Pagenkopf (russ@ism.net) -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Wed Mar 20 06:27:53 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA04777 for hardware-outgoing; Wed, 20 Mar 1996 06:27:53 -0800 (PST) Received: from gallup.cia-g.com (root@gallup.cia-g.com [206.206.162.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA04772 for ; Wed, 20 Mar 1996 06:27:51 -0800 (PST) Received: from gallup.cia-g.com (gallup.cia-g.com [206.206.162.10]) by gallup.cia-g.com (8.6.11/8.6.9) with SMTP id HAA23883; Wed, 20 Mar 1996 07:28:35 -0700 Date: Wed, 20 Mar 1996 07:28:35 -0700 (MST) From: Stephen Fisher To: Russ Pagenkopf cc: freebsd-hardware@freebsd.org Subject: Re: help with new motherboard 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 I had this problem with my new server, When it says boot: type -c and let it load the kernel off of the boot disk, then type "visual" and go through and disable everything you don't need.. and it should get by fine. Make sure you don't disable the system console driver though =) On Mon, 18 Mar 1996, Russ Pagenkopf wrote: > Feedback please, I'm getting desperate. > ... > > The problem: > > Using either the boot.flp or the atapi.flp disk the install will go through > uncompressing the kernel, go to bold white with CPU:, start probing and > gets to (I think, the bloody thing goes too fast to keep up) probing the > ISA bus, resets and locks up (clears the screen and freezes, puts the > monitor in energy-saving mode, only a power off/on or reset will bring it > back). > > In desperation I've pulled the Buslogic Card, the 3Com, the CD-ROM, it's > down to just the floppy and no joy, same thing everytime. Am I screwed? > > TIA > rus > > ps. no conflicts that I can find, besides pulling stuff should eliminate > that, and yes it all works fine in DOS :-( > > > Russ Pagenkopf (russ@ism.net) > > From owner-freebsd-hardware Wed Mar 20 07:06:19 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA07188 for hardware-outgoing; Wed, 20 Mar 1996 07:06:19 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [199.93.252.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA07167 Wed, 20 Mar 1996 07:06:10 -0800 (PST) Received: (from owensc@localhost) by itsdsv1.enc.edu (8.6.11/8.6.9) id KAA05394; Wed, 20 Mar 1996 10:04:58 -0500 Date: Wed, 20 Mar 1996 10:04:58 -0500 (EST) From: Charles Owens To: Dan Polivy cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: -stable and NCR problems? 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, 19 Mar 1996, Dan Polivy wrote: > Hey, > > I just got -stable working, and have had a few odd problems with my ncr0 > PCI scsi controller...It seemed to work fine for 2.1-RELEASE...what has > changed in the ncr driver from release->stable? I can try and give you > more info if you need it...lemme go look in the logs.....Well, just > seeing if anyone else has had this problem? Thanks! What are you seeing? I'm seeing this sorta stuff: Mar 17 12:59:39 dingo /kernel: ncr0:0: ERROR (0:140) (40-67-4) (8/13) @ (abc:008c0064). Mar 17 12:59:42 dingo /kernel: script cmd = c0000001 Mar 17 12:59:42 dingo /kernel: reg: da 10 c0 13 47 08 00 0f a4 40 80 67 00 00 07 00. Mar 17 12:59:42 dingo /kernel: ncr0: have to clear fifos. Mar 17 12:59:42 dingo /kernel: ncr0: handshake timeout Mar 17 12:59:42 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0aede00. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0ad6600. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): UNIT ATTENTION asc:29,0 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 Mar 17 12:59:43 dingo /kernel: , retries:3 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Mar 17 12:59:43 dingo /kernel: ncr0:0: ERROR (80:100) (8-2a-0) (8/13) @ (544:900b0000). Mar 17 12:59:43 dingo /kernel: script cmd = 910a0000 Mar 17 12:59:43 dingo /kernel: reg: da 10 80 13 47 08 00 0f 01 08 00 2a 80 00 02 00. Mar 17 12:59:43 dingo /kernel: ncr0: handshake timeout Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0aede00. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0ad6600. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0ad6800. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): UNIT ATTENTION asc:29,0 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 Mar 17 12:59:43 dingo /kernel: , retries:1 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Mar 17 12:59:43 dingo /kernel: cd0(ncr0:2:0): UNIT ATTENTION asc:29,0 Mar 17 12:59:43 dingo /kernel: cd0(ncr0:2:0): Power on, reset, or bus device reset occurred Usually, after a brief delay, it picks up where it left off with no problem, but I have had a few reboots that could be related. Is this similar to what you're seeing? Should I suspect the driver, my SCSI cable/termination or something else? thanks, --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-hardware Wed Mar 20 07:09:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA07395 for hardware-outgoing; Wed, 20 Mar 1996 07:09:24 -0800 (PST) Received: from optim.ism.net (optim.ism.net [205.199.12.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA07390 for ; Wed, 20 Mar 1996 07:09:18 -0800 (PST) Received: from [205.199.12.48] (slip8.ism.net [205.199.12.48]) by optim.ism.net (8.6.12/8.6.12) with SMTP id IAA29616; Wed, 20 Mar 1996 08:10:57 -0700 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 19 Mar 1996 08:11:05 -0600 To: Stephen Fisher , Russ Pagenkopf From: russ@ism.net (Russ Pagenkopf) Subject: Re: help with new motherboard Cc: freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wrote: >> Using either the boot.flp or the atapi.flp disk the install will go through >> uncompressing the kernel, go to bold white with CPU:, start probing and >> gets to (I think, the bloody thing goes too fast to keep up) probing the >> ISA bus, resets and locks up (clears the screen and freezes, puts the >> monitor in energy-saving mode, only a power off/on or reset will bring it >> back). Then at 7:28 AM 3/20/96, Stephen Fisher wrote: >When it says boot: type -c and let it load the kernel off of the boot >disk, then type "visual" and go through and disable everything you don't >need.. and it should get by fine. Make sure you don't disable the system >console driver though =) Well, this gets me a little further, I can now at least get through the loading of the kernel and the manual configuration, but I'm back to where I started. When I exit and save the visual configuration it goes to probing for devices on the ISA bus (I think, again it just flashes up there) and repeats the lockup problem. But both Michael Smith and Stephen Hocking asked: >You don't say what video card; my guess is you have a Mach64 in there >somewhere. Which is correct, the motherboard manual says it's a Mach64-CT SVGA graphics controller. Is this the problem? Stephen Hocking also asked: >...do you have com3 and/or com4? No, just com1 and com2. TIA rus Russ Pagenkopf (russ@ism.net) From owner-freebsd-hardware Wed Mar 20 11:01:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA24988 for hardware-outgoing; Wed, 20 Mar 1996 11:01:42 -0800 (PST) Received: from psiint.com (vv.psiint.com [204.189.53.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA24981 Wed, 20 Mar 1996 11:01:35 -0800 (PST) Received: by psiint.com (8.6.12/4.03) id LAA64865; Wed, 20 Mar 1996 11:01:29 -0800 Date: Wed, 20 Mar 1996 11:01:29 -0800 (PST) From: Dave Walton To: freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Strange lockup problem 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 I'm having an annoying lockup problem on a new Dell Pentium system running 2.1R. Kernel: GENERIC Hardware: S3-Trio64+, PS/2 mouse, EIDE, ATAPI CD-ROM, 3Com 3C509 (Everything is on the motherboard. All slots empty.) Boot config: fdc0, wdc0, lpt0, sio0, sio1, sc0 (Everything else disabled) Switching from one vty to another frequently causes a lockup. It can happen the first time after boot, or it might take a dozen or so switches. It's very repeatable. All I need to do is boot up and sit at the login prompt hitting Alt-F1 and Alt-F2 (or any other ones) and sooner or later the system locks up. I believe that it's just the keyboard locking up, but have no way of testing this theory. On a possibly related note, I built a new kernel to enable the CD and mouse. The only changes were to comment out I386_CPU and I496_CPU, change the ident, and add options ATAPI, device wcd0, and device psm0. When I enable psm0, the system boots fine, but with the keyboard locked up. Disabling psm0 eliminates the problem. Anyone have any brilliant ideas of what might be going on here? Thanks, Dave ========================================================================== David Walton Unix Programmer PSI INTERNATIONAL, Inc. email: dwalton@psiint.com 190 South Orchard #C200 Fax :(707)451-6484 Vacaville, CA 95688 Phone:(707)451-3503 ========================================================================== From owner-freebsd-hardware Wed Mar 20 13:19:27 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA04577 for hardware-outgoing; Wed, 20 Mar 1996 13:19:27 -0800 (PST) Received: from mail.jrihealth.com (mail.jrihealth.com [204.249.32.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA04570 Wed, 20 Mar 1996 13:19:21 -0800 (PST) Received: from carebase3.jri.org (danp@carebase3.jri.org [204.249.32.9]) by mail.jrihealth.com (8.3/8.6.6.Beta9) with SMTP id QAA01578; Wed, 20 Mar 1996 16:24:28 -0500 Date: Wed, 20 Mar 1996 16:24:42 -0500 (EST) From: Dan Polivy To: Charles Owens cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: -stable and NCR problems? 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 Charles, On Wed, 20 Mar 1996, Charles Owens wrote: > What are you seeing? I'm seeing this sorta stuff: I don't have a log handy..sorry...when I get it, though I will post it.. > Mar 17 12:59:42 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0aede00. > Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0ad6600. I get a few of these....I/O errors too trying to access file.. BUT, this only occurs every once in a while. It ran flawlessly for 2.1-RELEASE, as far as I know....So maybe we can go back to the old driver? Or were there problems with that? > Usually, after a brief delay, it picks up where it left off with no > problem, but I have had a few reboots that could be related. Hmm..I have to reboot to fix it... > Should I suspect the driver, my SCSI cable/termination or something else? I think it may be the driver...But maybe not. I get a bunch of the COMMAND FAILED notices...but keep in mine I have been running -STABLE for less than two days...so I haven't got much to go on...but I couldn't even boot the 2.2-SNAP disk - the ncr driver gave meproblems there, too... Dan +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ | JRI HIS MIS Systems Administrator/Tech Support | |////////////////////////////////////////////////////////////////| | danp@busstop.org dpolivy@jri.org danp@library.pride.net | |\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\| | Check out JRI's Homepage at http://www.jri.org | |////////////////////////////////////////////////////////////////| | For More Info about JRI Health, call 617.457.8150, | | EMail health@jri.org or check out http://www.jri.org/jrihealth | |\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\| | Check out my NEW [Moving] WWW page (still under construction) | | currently located at: http://server1.pride.net/~danp | +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+ From owner-freebsd-hardware Wed Mar 20 15:28:29 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA13871 for hardware-outgoing; Wed, 20 Mar 1996 15:28:29 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA13864 for ; Wed, 20 Mar 1996 15:28:26 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA08708; Thu, 21 Mar 1996 10:10:22 +1030 From: Michael Smith Message-Id: <199603202340.KAA08708@genesis.atrad.adelaide.edu.au> Subject: Re: help with new motherboard To: russ@ism.net (Russ Pagenkopf) Date: Thu, 21 Mar 1996 10:10:21 +1030 (CST) Cc: lithium@cia-g.com, russ@ism.net, freebsd-hardware@FreeBSD.org In-Reply-To: from "Russ Pagenkopf" at Mar 19, 96 08:11:05 am 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 Russ Pagenkopf stands accused of saying: > > But both Michael Smith and Stephen Hocking > asked: > > >You don't say what video card; my guess is you have a Mach64 in there > >somewhere. > > Which is correct, the motherboard manual says it's a Mach64-CT SVGA > graphics controller. Is this the problem? Yes. The Mach64 has a bug in that it is sensitive to the way that FreeBSD attempts to disable com4. It's necessary to do that to be able to probe com2 successfully if com4 is sharing an interrupt with it, but the Mach64 (incorrectly) responds to this operation. Your machine isn't actually hanging, the mach64 is. The short-term fix is to disable _all_ of the 'sio' devices. Make sure you install the kernel source when you do your install. Once you're installed OK, go to /sys/i386/isa, edit sio.c and remove the last number from the definition of 'likely_com_ports' and recompile your kernel as per the handbook. This will stop your '64 from hanging. > Russ Pagenkopf (russ@ism.net) -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Wed Mar 20 16:04:16 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA15466 for hardware-outgoing; Wed, 20 Mar 1996 16:04:16 -0800 (PST) Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA15348 for ; Wed, 20 Mar 1996 16:02:35 -0800 (PST) Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au id <28532-0@bunyip.cc.uq.oz.au>; Thu, 21 Mar 1996 10:01:28 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id JAA04935; Thu, 21 Mar 1996 09:50:27 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id XAA01662; Wed, 20 Mar 1996 23:53:38 GMT Message-Id: <199603202353.XAA01662@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: russ@ism.net (Russ Pagenkopf) cc: freebsd-hardware@freebsd.org Subject: Re: help with new motherboard In-reply-to: Your message of "Tue, 19 Mar 1996 08:11:05 CST." X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Mar 1996 09:53:36 +1000 From: Stephen Hocking Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Stephen Hocking also asked: > >...do you have com3 and/or com4? > > No, just com1 and com2. > Try disabling what ever serial ports you are not using (definitly com3/com4, maybe com2) and see what happens then. Stephen -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-hardware Wed Mar 20 22:05:18 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA25605 for hardware-outgoing; Wed, 20 Mar 1996 22:05:18 -0800 (PST) Received: from sierra.zyzzyva.com (root@ppp0.zyzzyva.com [198.183.2.50]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA25599 Wed, 20 Mar 1996 22:05:13 -0800 (PST) Received: from zyzzyva.com (randy@localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.4/8.6.11) with ESMTP id AAA19619; Thu, 21 Mar 1996 00:05:09 -0600 (CST) Message-Id: <199603210605.AAA19619@sierra.zyzzyva.com> To: freebsd-install@freebsd.org, freebsd-hardware@freebsd.org Subject: 3c509 install fails to probe X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Mar 1996 00:05:09 -0600 From: Randy Terbush Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Looking through the mail archives, this seems to be an known problem. Since I am attempting my first FreeBSD install, I am not in the position to build a kernel. Is there a known to work kernel available that has wd and ep0 drivers? Help appreciated. I don't have that many floppies.... From owner-freebsd-hardware Thu Mar 21 00:05:50 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA05989 for hardware-outgoing; Thu, 21 Mar 1996 00:05:50 -0800 (PST) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA05983 Thu, 21 Mar 1996 00:05:47 -0800 (PST) Received: from npc.haplink.co.cn ([202.96.192.53]) by mail.barrnet.net (8.7.4/MAIL-RELAY-LEN) with SMTP id AAA22552; Thu, 21 Mar 1996 00:05:06 -0800 (PST) Received: (from xiyuan@localhost) by npc.haplink.co.cn (8.6.11/8.6.9) id QAA07635; Thu, 21 Mar 1996 16:09:39 GMT Date: Thu, 21 Mar 1996 16:09:39 GMT From: xiyuan qian Message-Id: <199603211609.QAA07635@npc.haplink.co.cn> To: freebsd-hardware@freebsd.org, freebsd-install@freebsd.org, randy@zyzzyva.com Subject: Re: 3c509 install fails to probe Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, boot -c, config port ep0 0x300, IRQ 10 , maybe will through. Good luck! --xiyuan From owner-freebsd-hardware Thu Mar 21 07:44:30 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA07187 for hardware-outgoing; Thu, 21 Mar 1996 07:44:30 -0800 (PST) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.125.68.131]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA06583 for ; Thu, 21 Mar 1996 07:42:37 -0800 (PST) Received: from sivka.carrier.kiev.ua (root@sivka.carrier.kiev.ua [193.125.68.130]) by burka.carrier.kiev.ua (Sendmail 8.who.cares/5) with ESMTP id LAA19224 for ; Thu, 21 Mar 1996 11:31:03 +0200 Received: from elvisti.kiev.ua (uucp@localhost) by sivka.carrier.kiev.ua (Sendmail 8.who.cares/5) with UUCP id LAA08682 for hardware@freebsd.org; Thu, 21 Mar 1996 11:11:02 +0200 Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.33]) by spider2.elvisti.kiev.ua (8.6.12/8.ElVisti) with ESMTP id KAA15475 for ; Thu, 21 Mar 1996 10:30:06 +0200 Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id KAA27764; Thu, 21 Mar 1996 10:30:06 +0200 From: "Andrew V. Stesin" Message-Id: <199603210830.KAA27764@office.elvisti.kiev.ua> Subject: Re: Strange lockup problem To: dwalton@psiint.com (Dave Walton) Date: Thu, 21 Mar 1996 10:30:05 +0200 (EET) Cc: hardware@freebsd.org In-Reply-To: from "Dave Walton" at Mar 20, 96 11:01:29 am X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk # Switching from one vty to another frequently causes a lockup. It can If you still can do telnet to your box (or come into it via modem port), that's a situation I've seen several times before -- lockup (or better to say synchronization problem) of onboard kbd controller, or keyboard itself. Sometimes re-plugging of kbd jack cures it (dangerous!) or a command kbdcontrol -r fast < /dev/ttyv0 (issued after coming into the box via telnet). # happen the first time after boot, or it might take a dozen or so # switches. It's very repeatable. All I need to do is boot up and sit at # the login prompt hitting Alt-F1 and Alt-F2 (or any other ones) and sooner # or later the system locks up. I believe that it's just the keyboard # locking up, but have no way of testing this theory. Yes, smells pretty similar to what I've seen. Try the above action. # mouse. The only changes were to comment out I386_CPU and I496_CPU, # change the ident, and add options ATAPI, device wcd0, and device psm0. # When I enable psm0, the system boots fine, but with the keyboard locked # up. Disabling psm0 eliminates the problem. No idea on this. -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1. From owner-freebsd-hardware Thu Mar 21 10:59:32 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA18921 for hardware-outgoing; Thu, 21 Mar 1996 10:59:32 -0800 (PST) Received: from psiint.com (vv.psiint.com [204.189.53.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA18916 for ; Thu, 21 Mar 1996 10:59:29 -0800 (PST) Received: by psiint.com (8.6.12/4.03) id KAA63965; Thu, 21 Mar 1996 10:58:43 -0800 Date: Thu, 21 Mar 1996 10:58:43 -0800 (PST) From: Dave Walton To: "Andrew V. Stesin" cc: hardware@FreeBSD.ORG Subject: Re: Strange lockup problem In-Reply-To: <199603210830.KAA27764@office.elvisti.kiev.ua> 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 Thu, 21 Mar 1996, Andrew V. Stesin wrote: > If you still can do telnet to your box (or come into it It's not a matter of 'still'. This particular box is set up to be stand-alone. The network stuff has never been configured. > via modem port), that's a situation I've seen several > times before -- lockup (or better to say synchronization > problem) of onboard kbd controller, or keyboard itself. Any idea what the underlying problem is, and what the cure might be? > Sometimes re-plugging of kbd jack cures it (dangerous!) > or a command kbdcontrol -r fast < /dev/ttyv0 (issued > after coming into the box via telnet). I'll try these, but all they will do is FIX the problem. I need to AVOID it. > # mouse. The only changes were to comment out I386_CPU and I496_CPU, > # change the ident, and add options ATAPI, device wcd0, and device psm0. > # When I enable psm0, the system boots fine, but with the keyboard locked > # up. Disabling psm0 eliminates the problem. > > No idea on this. Since it's the keyboard, I suspect there is some relation between the two problems. This is actually the more important of the two, since it prevents me from running X. Dave ========================================================================== David Walton Unix Programmer PSI INTERNATIONAL, Inc. email: dwalton@psiint.com 190 South Orchard #C200 Fax :(707)451-6484 Vacaville, CA 95688 Phone:(707)451-3503 ========================================================================== From owner-freebsd-hardware Thu Mar 21 12:08:13 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA21640 for hardware-outgoing; Thu, 21 Mar 1996 12:08:13 -0800 (PST) Received: from snake.hut.fi (root@snake.hut.fi [193.167.6.99]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA21635 for ; Thu, 21 Mar 1996 12:08:10 -0800 (PST) Received: from lk-hp-20.hut.fi (lk-hp-20.hut.fi [130.233.247.33]) by snake.hut.fi (8.7.3/8.7.3) with ESMTP id WAA05507 for ; Thu, 21 Mar 1996 22:07:35 +0200 (EET) From: Juha Inkari Received: (inkari@localhost) by lk-hp-20.hut.fi (8.6.12/8.6.7) id WAA19271 for freebsd-hardware@freebsd.org; Thu, 21 Mar 1996 22:07:34 +0200 Message-Id: <199603212007.WAA19271@lk-hp-20.hut.fi> Subject: 3c590 To: freebsd-hardware@freebsd.org Date: Thu, 21 Mar 1996 22:07:34 +0200 (EET) X-Mailer: ELM [version 2.4 PL25] 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 tried a PCI version of 3com's Etherlink III (3c590). I found it to loose packets, when pinging with bigger than 64 byte packet size. Packet lossage would typically be 7% with 128 byte sized packets, up to 60% with 256 byte sized packets, and nothing comes through with 1k packets. I have a version of the card, which the vx driver complains about ("Warning! Defective early revision adapter!"). The source describes first revision of the adapters having "receive overrun anomaly". Can anyone elaborate on this? Also what arguments I might use to prove that the card does not work when returning this piece (I'll go for SMC-8432 - now I have as a temporary fix a 3c509 which does seem to work). From owner-freebsd-hardware Thu Mar 21 12:16:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA22276 for hardware-outgoing; Thu, 21 Mar 1996 12:16:24 -0800 (PST) Received: from psiint.com (vv.psiint.com [204.189.53.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA22263 for ; Thu, 21 Mar 1996 12:16:21 -0800 (PST) Received: by psiint.com (8.6.12/4.03) id MAA43455; Thu, 21 Mar 1996 12:12:13 -0800 Date: Thu, 21 Mar 1996 12:12:13 -0800 (PST) From: Dave Walton To: "Andrew V. Stesin" cc: hardware@FreeBSD.ORG Subject: Re: Strange lockup problem In-Reply-To: <199603210830.KAA27764@office.elvisti.kiev.ua> 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 Thu, 21 Mar 1996, Andrew V. Stesin wrote: > # Switching from one vty to another frequently causes a lockup. It can > > If you still can do telnet to your box (or come into it > via modem port), that's a situation I've seen several > times before -- lockup (or better to say synchronization > problem) of onboard kbd controller, or keyboard itself. > Sometimes re-plugging of kbd jack cures it (dangerous!) > or a command kbdcontrol -r fast < /dev/ttyv0 (issued > after coming into the box via telnet). Since I don't have network access, I put an entry in /etc/crontab that runs "kbdcontrol -r normal < /dev/ttyv0" every minute. It's a cheap hack, but at least it means that I only have to wait <1 minute if it locks, instead of rebooting. > # mouse. The only changes were to comment out I386_CPU and I496_CPU, > # change the ident, and add options ATAPI, device wcd0, and device psm0. > # When I enable psm0, the system boots fine, but with the keyboard locked > # up. Disabling psm0 eliminates the problem. > > No idea on this. I re-enabled psm0, and it clears right up as soon as cron runs a minute after boot. So now I can run X. Thanks for the work-around. Now... Can anyone tell me WHY this is happening? Dave ========================================================================== David Walton Unix Programmer PSI INTERNATIONAL, Inc. email: dwalton@psiint.com 190 South Orchard #C200 Fax :(707)451-6484 Vacaville, CA 95688 Phone:(707)451-3503 ========================================================================== From owner-freebsd-hardware Fri Mar 22 01:41:45 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA26418 for hardware-outgoing; Fri, 22 Mar 1996 01:41:45 -0800 (PST) Received: from snake.hut.fi (root@snake.hut.fi [193.167.6.99]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id BAA26413 for ; Fri, 22 Mar 1996 01:41:39 -0800 (PST) Received: from lk-hp-20.hut.fi (lk-hp-20.hut.fi [130.233.247.33]) by snake.hut.fi (8.7.3/8.7.3) with ESMTP id LAA10376; Fri, 22 Mar 1996 11:41:26 +0200 (EET) From: Juha Inkari Received: (inkari@localhost) by lk-hp-20.hut.fi (8.6.12/8.6.7) id LAA23453; Fri, 22 Mar 1996 11:41:27 +0200 Message-Id: <199603220941.LAA23453@lk-hp-20.hut.fi> Subject: Re: 3c590 To: lyndon@orthanc.com (Lyndon Nerenberg VE7TCP) Date: Fri, 22 Mar 1996 11:41:27 +0200 (EET) Cc: freebsd-hardware@freebsd.org In-Reply-To: <199603220002.QAA17067@multivac.orthanc.com> from "Lyndon Nerenberg VE7TCP" at Mar 21, 96 04:02:12 pm X-Mailer: ELM [version 2.4 PL25] 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 > have the problem. (Anything after revision A boards should be fine. > Mine are revision C.) > The bug is documented in the _PCI/EISA Bus-Master Adapter Driver > Technical Reference_ (3COM part number 09-0681-001A). Thanks. My card says it's: 3C590C ^ 03-0046-001 REV D ^^^ ^ The ^ marked are handwritten. Would this actually be a bug in the vx driver, then ? From owner-freebsd-hardware Fri Mar 22 05:37:16 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA06034 for hardware-outgoing; Fri, 22 Mar 1996 05:37:16 -0800 (PST) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.125.68.131]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA06026 for ; Fri, 22 Mar 1996 05:36:56 -0800 (PST) Received: from sivka.carrier.kiev.ua (root@sivka.carrier.kiev.ua [193.125.68.130]) by burka.carrier.kiev.ua (Sendmail 8.who.cares/5) with ESMTP id MAA12434 for ; Fri, 22 Mar 1996 12:29:44 +0200 Received: from elvisti.kiev.ua (uucp@localhost) by sivka.carrier.kiev.ua (Sendmail 8.who.cares/5) with UUCP id AAA08856 for hardware@freebsd.org; Fri, 22 Mar 1996 00:31:30 +0200 Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.33]) by spider2.elvisti.kiev.ua (8.6.12/8.ElVisti) with ESMTP id XAA07259 for ; Thu, 21 Mar 1996 23:08:26 +0200 Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id XAA03313; Thu, 21 Mar 1996 23:08:24 +0200 From: "Andrew V. Stesin" Message-Id: <199603212108.XAA03313@office.elvisti.kiev.ua> Subject: Re: Strange lockup problem To: dwalton@psiint.com (Dave Walton) Date: Thu, 21 Mar 1996 23:08:23 +0200 (EET) Cc: hardware@freebsd.org, sos@freebsd.org In-Reply-To: from "Dave Walton" at Mar 21, 96 10:58:43 am X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, [... kbd lockup when switching consoles ...] # > If you still can do telnet to your box (or come into it # # It's not a matter of 'still'. This particular box is set up to be # stand-alone. The network stuff has never been configured. Pity. # Any idea what the underlying problem is, and what the cure might be? Strange hardware. I remember the rumours this has something to do with updating the state of kbd "status" LED indicators, and some brand of kbd controller chips on the MB which has problems with this. Another source of strange problems often is hidden in a slightly misconfigured BIOS. Probably the author of the driver can tell you more detais, I'm sending the copy to him. # > Sometimes re-plugging of kbd jack cures it (dangerous!) # > or a command kbdcontrol -r fast < /dev/ttyv0 (issued # > after coming into the box via telnet). # # I'll try these, but all they will do is FIX the problem. I need to AVOID it. Please remember, FreeBSD is a _volunteer_ project. :-) No warranties, only the good will of the FreeBSD people and probably some patience can help. Don't be afraid, though -- I have had probably all possible kinds of hardware problems since Nov. 1993, because we here are often using a low quality parts; all problems were solved, some sooner, some later. Several times I found that it's much easier to replace a "strange" piece of hardware with a more standard item, and beleive me -- I never was sorry in a long run. The first thing you can try is simply increase all the timeouts in /sys/i386/isa/syscons.c, some three times up or even more. But that's another "fix" (read: kludge), not a real solution. Let's wait what the author of keyboard driver will tell us. # > # mouse. The only changes were to comment out I386_CPU and I496_CPU, # > # change the ident, and add options ATAPI, device wcd0, and device psm0. # > # When I enable psm0, the system boots fine, but with the keyboard locked # > # up. Disabling psm0 eliminates the problem. # > # > No idea on this. # # Since it's the keyboard, I suspect there is some relation between the two # problems. This is actually the more important of the two, since it # prevents me from running X. Sorry, David, I have no experience with bus mice and their possible interaction with kbd controller, still no ideas. I think that the _exact_ specs of your motherboard (manufacturer, model name, chipset, output of dmesg(8) after booting with '-v' switch to the loader) may give some helpful hints. # # Dave # # ========================================================================== # David Walton Unix Programmer # PSI INTERNATIONAL, Inc. email: dwalton@psiint.com # 190 South Orchard #C200 Fax :(707)451-6484 # Vacaville, CA 95688 Phone:(707)451-3503 # ========================================================================== # # -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1. From owner-freebsd-hardware Fri Mar 22 07:56:37 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA12725 for hardware-outgoing; Fri, 22 Mar 1996 07:56:37 -0800 (PST) Received: from psiint.com (vv.psiint.com [204.189.53.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA12720 Fri, 22 Mar 1996 07:56:25 -0800 (PST) Received: by psiint.com (8.6.12/4.03) id HAA57444; Fri, 22 Mar 1996 07:53:21 -0800 Date: Fri, 22 Mar 1996 07:53:21 -0800 (PST) From: Dave Walton To: "Andrew V. Stesin" cc: hardware@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: Strange lockup problem In-Reply-To: <199603212108.XAA03313@office.elvisti.kiev.ua> 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 Thu, 21 Mar 1996, Andrew V. Stesin wrote: > [... kbd lockup when switching consoles ...] > > # Any idea what the underlying problem is, and what the cure might be? > > Strange hardware. I remember the rumours this has something > to do with updating the state of kbd "status" LED indicators, > and some brand of kbd controller chips on the MB which has > problems with this. Who would know what brand that is? > Another source of strange problems > often is hidden in a slightly misconfigured BIOS. Ah, I wish this were it. Too bad this system has a Phoenix BIOS, which is barely configurable in the first place. Nothing like AMI... > Probably the author of the driver can tell you more detais, > I'm sending the copy to him. Great, thanks! > # I'll try these, but all they will do is FIX the problem. I need to AVOID it. > > Please remember, FreeBSD is a _volunteer_ project. :-) You bet. And it's an incredibly professional bunch of volunteers, too. I feel better with an operating system where I can actually chat with the people that wrote the code, rather than one where I have to make a toll call to talk to some support flunkie who probably doesn't even know how the system works inside. > Let's wait what the author of keyboard driver will tell us. Good idea. Standing by... Dave ========================================================================== David Walton Unix Programmer PSI INTERNATIONAL, Inc. email: dwalton@psiint.com 190 South Orchard #C200 Fax :(707)451-6484 Vacaville, CA 95688 Phone:(707)451-3503 ========================================================================== From owner-freebsd-hardware Fri Mar 22 08:10:45 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA13138 for hardware-outgoing; Fri, 22 Mar 1996 08:10:45 -0800 (PST) Received: from boom.vars.com (boom.BSDI.COM [205.230.226.129]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA13132 for ; Fri, 22 Mar 1996 08:10:40 -0800 (PST) Received: from boom.vars.com (localhost.vars.com [127.0.0.1]) by boom.vars.com (8.7.3/8.6.5) with ESMTP id IAA07807; Fri, 22 Mar 1996 08:57:43 -0700 (MST) Message-Id: <199603221557.IAA07807@boom.vars.com> To: Juha Inkari Cc: lyndon@orthanc.com (Lyndon Nerenberg VE7TCP), freebsd-hardware@freebsd.org Subject: Re: 3c590 In-Reply-To: Your message of "Fri, 22 Mar 1996 11:41:27 +0200." <199603220941.LAA23453@lk-hp-20.hut.fi> Mime-Version: 1.0 Content-Type: application/pgp; format=mime; x-action=signclear; x-originator=05448C39 Content-Transfer-Encoding: 7bit Date: Fri, 22 Mar 1996 08:57:33 -0700 From: Eric Varsanyi Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Content-Type: text/plain; charset=us-ascii > >> have the problem. (Anything after revision A boards should be fine. >> Mine are revision C.) > >> The bug is documented in the _PCI/EISA Bus-Master Adapter Driver >> Technical Reference_ (3COM part number 09-0681-001A). > >Thanks. My card says it's: >3C590C > ^ >03-0046-001 REV D > ^^^ ^ > >The ^ marked are handwritten. Would this actually be a bug in the vx >driver, then ? 3COM changed their minds on this (after producing the tech manual)... the new party line is that you should install their S/W workaround. As far as I can tell they have no plans to fix this bug, no one I've heard of has a fixed card. The problem is that on 10mbit nets rx packets that overrun the FIFO may be silently corrupted (instead of dropped). Their recommended solution is quite complex but it basically keeps track of how full the FIFO has gotten and drops all packets that may have overrun the end. I implemented a simpler version of their fix in our driver, it was only a few lines of code. In general the size of the FIFO's on the broken cards is at least 32K so it doesn't hurt to reserve the top 6K for 'overrun protection'. - -Eric -----BEGIN PGP SIGNATURE----- Version: 2.6 iQCVAgUBMVLN7DxFdSMFRIw5AQH2HAQAkS8xU6xwosKUoTFdT1x4IfSRA5cojkuT 8xB6Vvw4qkvlaRwzI3Mcs0/rlhTS7zh1LBeGLzx3Fafhce89Fgi/bnDswTmowo3H TFDpOGbfil4+kKB663UG5WdwTd7NQSWJtwbBq7UMK7e3LO+saatHNFLdIrJ7fyMI CscgHcXSYV4= =BC2s -----END PGP SIGNATURE----- From owner-freebsd-hardware Fri Mar 22 10:36:41 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA20262 for hardware-outgoing; Fri, 22 Mar 1996 10:36:41 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA20256 for ; Fri, 22 Mar 1996 10:36:39 -0800 (PST) Received: from multivac.orthanc.com (root@multivac.orthanc.com [206.12.238.2]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id KAA03577 for ; Fri, 22 Mar 1996 10:34:26 -0800 Received: from localhost (lyndon@localhost) by multivac.orthanc.com (8.7.3/8.7.3) with SMTP id KAA27509; Fri, 22 Mar 1996 10:21:42 -0800 (PST) Message-Id: <199603221821.KAA27509@multivac.orthanc.com> From: Lyndon Nerenberg VE7TCP To: Juha Inkari cc: freebsd-hardware@freebsd.org Subject: Re: 3c590 In-reply-to: Your message of "Fri, 22 Mar 1996 11:41:27 +0200." <199603220941.LAA23453@lk-hp-20.hut.fi> Date: Fri, 22 Mar 1996 10:21:40 -0800 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "Juha" == Juha Inkari writes: >> have the problem. (Anything after revision A boards should be >> fine. Mine are revision C.) >> The bug is documented in the _PCI/EISA Bus-Master Adapter >> Driver Technical Reference_ (3COM part number 09-0681-001A). Juha> Thanks. My card says it's: 3C590C ^ 03-0046-001 REV D ^^^ ^ I have the 3C595, assy # 03-0027-001 rev C. I have a different card which explains the version number differences. Juha> The ^ marked are handwritten. Would this actually be a bug Juha> in the vx driver, then ? I doubt it. There is an EEPROM bit used to flag the bug. If the bit is 0 the bug exists. If the bit is set to 1 it means the bug has been fixed. Unless the driver totally botched the test the message should be valid. (I haven't looked at that specific part of the driver code ...) --lyndon From owner-freebsd-hardware Fri Mar 22 12:15:53 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA26606 for hardware-outgoing; Fri, 22 Mar 1996 12:15:53 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA26595 Fri, 22 Mar 1996 12:15:48 -0800 (PST) Received: by Sisyphos id AA02130 (5.67b/IDA-1.5); Fri, 22 Mar 1996 21:14:24 +0100 Message-Id: <199603222014.AA02130@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Fri, 22 Mar 1996 21:14:23 +0100 In-Reply-To: Charles Owens "Re: -stable and NCR problems?" (Mar 20, 10:04) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Charles Owens Subject: Re: -stable and NCR problems? Cc: reebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 20, 10:04, Charles Owens wrote: } Subject: Re: -stable and NCR problems? } On Tue, 19 Mar 1996, Dan Polivy wrote: } } > Hey, } > } > I just got -stable working, and have had a few odd problems with my ncr0 } > PCI scsi controller...It seemed to work fine for 2.1-RELEASE...what has } > changed in the ncr driver from release->stable? I can try and give you } > more info if you need it...lemme go look in the logs.....Well, just } > seeing if anyone else has had this problem? Thanks! } } What are you seeing? I'm seeing this sorta stuff: } } Mar 17 12:59:39 dingo /kernel: ncr0:0: ERROR (0:140) (40-67-4) (8/13) @ (abc:008c0064). That's the infamous handshake timeout ... This feature seems to do more harm than good, and I'll apply the following patch to -stable (it has been in current for some time already): Index: /sys/pci/ncr.c =================================================================== RCS file: /usr/cvs/src/sys/pci/ncr.c,v retrieving revision 1.37.4.6 diff -C2 -r1.37.4.6 ncr.c *** ncr.c 1996/03/11 19:59:46 1.37.4.6 --- ncr.c 1996/03/22 20:12:58 *************** *** 4441,4445 **** OUTB (nc_stest2, EXT ); /* Extended Sreq/Sack filtering */ OUTB (nc_stest3, TE ); /* TolerANT enable */ ! OUTB (nc_stime0, 0xfb ); /* HTH = 1.6sec STO = 0.1 sec. */ /* --- 4441,4445 ---- OUTB (nc_stest2, EXT ); /* Extended Sreq/Sack filtering */ OUTB (nc_stest3, TE ); /* TolerANT enable */ ! OUTB (nc_stime0, 0x0b ); /* HTH = disabled, STO = 0.1 sec. */ /* } Should I suspect the driver, my SCSI cable/termination or something else? The handshake timeout occurs, when there has been no ACK, 1.6 seconds after a REQ. This may be caused by a lost pulse, but it may also be caused by termal recal or ECC error recovery making the drive unresponsive for such an amount of time ... Please let me know, whether the patch does help. (I'll be on a vacation, so don't expect a reply before the second week of April.) Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-hardware Sat Mar 23 10:45:55 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA02416 for hardware-outgoing; Sat, 23 Mar 1996 10:45:55 -0800 (PST) Received: from sol.we.lc.ehu.es (sol.we.lc.ehu.es [158.227.6.42]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA02408 for ; Sat, 23 Mar 1996 10:45:46 -0800 (PST) Received: from aldebaran.we.lc.ehu.es by sol.we.lc.ehu.es (5.x/SMI-SVR4) id AA15806; Sat, 23 Mar 1996 19:44:32 +0100 From: borjam@we.lc.ehu.es (Borja Marcos) Message-Id: <9603231844.AA15806@sol.we.lc.ehu.es> Subject: Magneto-optical disks To: freebsdelm@we.lc.ehu.es, freebsd-hardware@freebsd.org Date: Sat, 23 Mar 1996 19:45:34 +0100 (MET) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, Does FreeBSD 2.1 (RELEASE) support Fujitsu DynaMO 230 drives? If not... does it support any magneto-optical or WORM drive? Thanks, Borja. -- ******************************************************************* Borja Marcos | Preferred: borjam@we.lc.ehu.es Alangoeta, 11, 1. izq. | Others: borjamar@mx.sarenet.es 48990 - Algorta (Vizcaya) | 100015.3502@compuserve.com SPAIN | CIS: 100015,3502 ****************************************************************** (c)1995 by the author. This message cannot be transferred to the Microsoft(tm) Network. From owner-freebsd-hardware Sat Mar 23 13:19:15 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA11803 for hardware-outgoing; Sat, 23 Mar 1996 13:19:15 -0800 (PST) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.125.68.131]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA11705 for ; Sat, 23 Mar 1996 13:17:49 -0800 (PST) Received: from sivka.carrier.kiev.ua (root@sivka.carrier.kiev.ua [193.125.68.130]) by burka.carrier.kiev.ua (Sendmail 8.who.cares/5) with ESMTP id XAA11165 for ; Sat, 23 Mar 1996 23:19:31 +0200 Received: from elvisti.kiev.ua (uucp@localhost) by sivka.carrier.kiev.ua (Sendmail 8.who.cares/5) with UUCP id XAA14672 for hardware@freebsd.org; Sat, 23 Mar 1996 23:10:08 +0200 Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.33]) by spider2.elvisti.kiev.ua (8.6.12/8.ElVisti) with ESMTP id WAA08829 for ; Sat, 23 Mar 1996 22:42:43 +0200 Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id WAA08802; Sat, 23 Mar 1996 22:42:42 +0200 From: "Andrew V. Stesin" Message-Id: <199603232042.WAA08802@office.elvisti.kiev.ua> Subject: Re: -stable and NCR problems? To: se@ZPR.Uni-Koeln.DE (Stefan Esser) Date: Sat, 23 Mar 1996 22:42:42 +0200 (EET) Cc: owensc@enc.edu, stable@freebsd.org, hardware@freebsd.org In-Reply-To: <199603222014.AA02130@Sisyphos> from "Stefan Esser" at Mar 22, 96 09:14:23 pm X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, # } What are you seeing? I'm seeing this sorta stuff: # } # } Mar 17 12:59:39 dingo /kernel: ncr0:0: ERROR (0:140) (40-67-4) (8/13) @ (abc:008c0064). I didn't see the above errors, there was another story -- 2.1R kernel was fine on one of the boxes, after installing a -stable kernel as of 960318 it won't boot, going asleep right after the last kernel printf at the moment when NCR first time touches the disk and fsck should be started. # That's the infamous handshake timeout ... # This feature seems to do more harm than good, # and I'll apply the following patch to -stable # (it has been in current for some time already): [...] I confirm that the patch cured the situation at least for me. BTW the drive is the affected box is 1.08Gb IBM DPES 31080S, a bunch of those drives are happy with NCRs and non-patched -stable kernels here; a failure was a single case out of 6. I'm going to upgrade kernels on other boxes soon, too. -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1.