From owner-freebsd-hardware Sun Jul 21 14:32:44 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28959 for hardware-outgoing; Sun, 21 Jul 1996 14:32:44 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-153.ut.nl.ibm.net [139.92.42.153]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA28932; Sun, 21 Jul 1996 14:32:19 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id TAA07129; Sun, 21 Jul 1996 19:08:57 +0200 (MET DST) Message-Id: <199607211708.TAA07129@vector.jhs.no_domain> To: "Rodney W. Grimes" cc: frankd@yoda.fdt.net (Frank Seltzer), freebsd-hardware@freebsd.org Subject: Re: Comments wanted on new system From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 (later) Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available In-reply-to: Your message of "Wed, 17 Jul 1996 19:57:01 PDT." <199607180257.TAA07745@GndRsh.aac.dev.com> Date: Sun, 21 Jul 1996 19:08:56 +0200 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Rod, CC Hardware, Reference: > From: "Rodney W. Grimes" > > > > > I would highly recommend _not_ getting this board, it uses the Orion > > > chipset, which is older and known to have certain bugs. ASUS is now > > One more time.... > Chip sets belowing stepping B0 have a PCI bus mastering bug that prevents Every time these pearls of wisdom come through I get a sinking feeling ! I know I'll never remember it all later when I may need it, & I doubt it all gets in the FAQ. One route to avoid some rogue hardware is to buy hardware via you :-) ... but after the European shippers & customs duties & banks have become involved, USA imports get expensive. Do you happen to keep a PC hardware notes file on the web ? If so I'd suggest an HREF to it from the FAQ hardware section, & I'd personally make a habit of keeping a local copy. :-) Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-hardware Mon Jul 22 03:32:16 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA01104 for hardware-outgoing; Mon, 22 Jul 1996 03:32:16 -0700 (PDT) Received: from magigimmix.xs4all.nl (magigimmix.xs4all.nl [194.109.6.25]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA01098 for ; Mon, 22 Jul 1996 03:32:13 -0700 (PDT) Received: from xs2.xs4all.nl (xs2.xs4all.nl [194.109.6.43]) by magigimmix.xs4all.nl (8.7.5/XS4ALL) with ESMTP id MAA17366 for ; Mon, 22 Jul 1996 12:32:05 +0200 (MET DST) Received: (from schofiel@localhost) by xs2.xs4all.nl (8.7.5/XS4ALL) id MAA27626 for hardware@freebsd.com; Mon, 22 Jul 1996 12:32:04 +0200 (MET DST) From: schofiel@xs4all.nl Message-Id: <199607221032.MAA27626@xs2.xs4all.nl> Subject: The multiple COM ports discussion To: hardware@freebsd.com Date: Mon, 22 Jul 1996 12:32:03 +0200 (MET DST) 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 Hello there everyone. Well, I have to confess, I didn't realise I would cause so much controversy regarding my questions on multiple ports. I have to admit also, that I posted in advance of performing research, which is always a serious mistke. Thanks for everyone for answering; it seems we have a case of the blind men and the elephant - everyone has got one piece of the puzzle and they are interpreting it differently. Over the weekend, I have sat down and read up on it, and I believe I now have a good picture of how things work on the hardware and on the software level. As a result, I would like to suggest that I write an article andpost it here. If anyone would like this, willyou please post and I will be glad to oblige. Note, I am not backing out here; in the most cases, people do not have to know this to operate BSD successfully. However, if theere is sufficient interest, I can supply the information. A number of points before I go, just to clear a few misapprehensions I have seen here. 1) PC/AT/ISA and EISA interrupt lines are all logic HIGH in the steady state. 2) With no devices attached to any interrupt line coming from a PIC, the level is pulled weakly high by pullups inside the PIC itself. 3) There are two versions of the PIC, the original type and the enhanced "A" variant. The original does not allow for level/edge selection, the enhanced does. The original does not allow individual IRQ operation selection (ie. all interrupt lines must operate with the same mode), te enhanced does allow individual mode selection. 4) In the PC/ISA scheme, interrupts are POSITIVE-GOING, EDGE triggered. In the EISA scheme, interrupts are by the default compatible to this, but can be configured to be ACTIVE LOW, LEVEL triggered. 5) TRistate interrupt line drivers are not neccessary in this scheme. 6) Individual interrupt lines can not be programmed "off" at the PIC, only in the calling device. 7) Multiple ISA-type interrupting devices can be placed on a single interupt line, electrically. The ISA standard (no joke, there is one) does not however closely specify how interrupt drivers should be implemented for uniformity. 8) Multiple ISA devices can also be handled on a single interrupt, but again there is no closely defined method (only "recommended good practice") for doing this. 9) It is not possible to alter the way the interrupt line works simply by programming the PIC to which it is attached, this is determined by the design of the hardware device that is interrupting. Before you all go wacko and say "What does he know!!!" or "Garbage!", I have spent the weekend reading the ISA spec and the EISA spec, plus a few books dedicated to both architectures written by hardware designers at DELL, etc. They point out that the EISA architecture was designed to address the holes left by the ISA spec, whilst moving it on to the next logical stage (32-bit). ISA, is by definition, pretty c*** on a number of pretty important issues. In summary, you can stick as many ISA devices as you like on one IRQ line, but there's: 1) No guarantee all devices on the line will use the same interrupt drive hardware 2) No guarantee that all devices will fail safe on an IRQ 3) No guarantee that even if you have a driver able to scan for multiple devices interupting on a line, that it will be able to successfully handle them 4) No guarantee that simultaneously interrupting devices will BOTH be recognised The most likely scenario of success is if all devices on a shared ISA scheme are GUARANTEED not to interrupt at the same time. Thanks for all answers, sorry this went on so long; as stated, if anyone would like me to write a definitive article on shared interrupts, then please post or send mail to me at: schofiel@xs4all.nl Rob Schofield From owner-freebsd-hardware Mon Jul 22 06:51:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA07683 for hardware-outgoing; Mon, 22 Jul 1996 06:51:42 -0700 (PDT) Received: from fire.dkrz.de (fire.dkrz.de [136.172.110.250]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA07675 for ; Mon, 22 Jul 1996 06:51:29 -0700 (PDT) Received: from racer.dkrz.de (racer.dkrz.de [136.172.110.55]) by fire.dkrz.de (8.7.5/8.7.3) with ESMTP id PAA16582; Mon, 22 Jul 1996 15:47:59 +0200 (MET DST) Received: (from gwk@localhost) by racer.dkrz.de (8.7.4/8.7.3) id PAA27901; Mon, 22 Jul 1996 15:49:12 +0200 (MET DST) Date: Mon, 22 Jul 1996 15:49:12 +0200 (MET DST) Message-Id: <199607221349.PAA27901@racer.dkrz.de> From: "Georg-W. Koltermann" To: schofiel@xs4all.nl CC: hardware@freebsd.com In-reply-to: <199607221032.MAA27626@xs2.xs4all.nl> (schofiel@xs4all.nl) Subject: Re: The multiple COM ports discussion X-Attribution: gwk Reply-to: gwk@cray.com Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk There's never enough documentation, so yes, please, post it. Maybe it could somehow get included in the FreeBSD handbook? Regards, Georg-W. Koltermann, gwk@cray.com From owner-freebsd-hardware Mon Jul 22 09:51:05 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA16144 for hardware-outgoing; Mon, 22 Jul 1996 09:51:05 -0700 (PDT) Received: from ns.frihet.com (root@frihet.bayarea.net [205.219.92.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA16137 for ; Mon, 22 Jul 1996 09:51:02 -0700 (PDT) Received: from ns.frihet.com (tweten@localhost [127.0.0.1]) by ns.frihet.com (8.7.5/8.6.12) with ESMTP id JAA01328; Mon, 22 Jul 1996 09:49:56 -0700 (PDT) Message-Id: <199607221649.JAA01328@ns.frihet.com> X-Mailer: exmh version 1.6.7 5/3/96 Reply-To: "David E. Tweten" To: schofiel@xs4all.nl cc: hardware@freebsd.com Subject: Re: The multiple COM ports discussion Date: Mon, 22 Jul 1996 09:49:55 -0700 From: "David E. Tweten" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk schofiel@xs4all.nl said: >4) In the PC/ISA scheme, interrupts are POSITIVE-GOING, EDGE triggered. > In the EISA scheme, interrupts are by the default compatible to this, > but can be configured to be ACTIVE LOW, LEVEL triggered. >5) TRistate interrupt line drivers are not neccessary in this scheme. What do you mean by "this scheme?" If you mean that "ACTIVE LOW, LEVEL triggered" is "this scheme," fine. All that is needed then is OPEN and ACTIVE LOW -- two states in ths strictest sense (though people often use "tristate" when all they really mean is that one state is OPEN). If "this scheme" is "POSITIVE-GOING, EDGE triggered," see my hardware concern below. >7) Multiple ISA-type interrupting devices can be placed on a single > interupt line, electrically. The ISA standard (no joke, there is one) > does not however closely specify how interrupt drivers should be > implemented for uniformity. Both ISA and EISA wire all interrupt "pins" on their motherboard connectors together. The only ISA standard I have any familiarity with is the 8 MHz IBM PC/AT, and the IBM-supplied boards that went with it. Those boards drove their interrupt lines with two states, ACTIVE HIGH and ACTIVE LOW. There was no OPEN state. There was no output resistor to mediate between "dualing" bus driver circuits. Therefore, there was no possibility of getting predictable results from putting two boards on the same interrupt. For each of the four combinations of two boards asserting or not asserting an interrupt you could get board-one dominance, board-two dominance, or you could get the privilege of replacing fried parts. It all depended upon the variable details of the driver circuits on both boards. Most of the time the hardware survived this kind of abuse because the board designers accounted for the possibility of people accidently installing two boards at the same interrupt. What is the mechanism used by the "ISA standard" you found, to handle the problem of dualing bus driver circuits? -- David E. Tweten | PGP Key fingerprint: | tweten@frihet.com 12141 Atrium Drive | E9 59 E7 5C 6B 88 B8 90 | tweten@and.com Saratoga, CA 95070-3162 | 65 30 2A A4 A0 BC 49 AE | (408) 446-4131 From owner-freebsd-hardware Mon Jul 22 10:10:51 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA17551 for hardware-outgoing; Mon, 22 Jul 1996 10:10:51 -0700 (PDT) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA17544 for ; Mon, 22 Jul 1996 10:10:50 -0700 (PDT) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0uiQLz-000x32C; Mon, 22 Jul 96 12:09 PDT Received: from cc:Mail by ccgate.infoworld.com id AA838055288; Mon, 22 Jul 96 10:55:55 PST Date: Mon, 22 Jul 96 10:55:55 PST From: "Brett Glass" Message-Id: <9606228380.AA838055288@ccgate.infoworld.com> To: schofiel@xs4all.nl, hardware@freebsd.com Subject: The multiple COM ports discussion Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thank you for the summary. Only one thing there that appears to be incorrect; you *can* disable interrupts at the interrupt controller. I've written software that does it. From owner-freebsd-hardware Mon Jul 22 16:50:39 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA22092 for hardware-outgoing; Mon, 22 Jul 1996 16:50:39 -0700 (PDT) Received: from relay-5.mail.demon.net (relay-5.mail.demon.net [158.152.1.48]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA21994 for ; Mon, 22 Jul 1996 16:49:27 -0700 (PDT) Received: from post.demon.co.uk by relay-5.mail.demon.net id ap18368; 23 Jul 96 0:28 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa07931; 22 Jul 96 23:45 +0100 Received: (from fhdware@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id RAA02118; Mon, 22 Jul 1996 17:26:20 GMT From: James Raynard Message-Id: <199607221726.RAA02118@jraynard.demon.co.uk> Subject: Re: The multiple COM ports discussion To: schofiel@xs4all.nl Date: Mon, 22 Jul 1996 17:26:20 +0000 () Cc: hardware@freebsd.org In-Reply-To: <199607221032.MAA27626@xs2.xs4all.nl> from "schofiel@xs4all.nl" at Jul 22, 96 12:32:03 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > As a result, I would like to suggest that I write > an article andpost it here. If anyone would like this, willyou please > post and I will be glad to oblige. Yes please! Or even better, why not convert it to SGML and submit to the Documentation Project (once everyone's managed to reach a consensus, that is :-) There are some empty slots in the Handbook that this would fit nicely into... From owner-freebsd-hardware Tue Jul 23 02:31:39 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA01502 for hardware-outgoing; Tue, 23 Jul 1996 02:31:39 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA01492 for ; Tue, 23 Jul 1996 02:31:26 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA24356; Tue, 23 Jul 1996 18:06:04 +1000 Date: Tue, 23 Jul 1996 18:06:04 +1000 From: Bruce Evans Message-Id: <199607230806.SAA24356@godzilla.zeta.org.au> To: schofiel@xs4all.nl, tweten@frihet.com Subject: Re: The multiple COM ports discussion Cc: hardware@freebsd.com Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >schofiel@xs4all.nl said: >>4) In the PC/ISA scheme, interrupts are POSITIVE-GOING, EDGE triggered. >> In the EISA scheme, interrupts are by the default compatible to this, >> but can be configured to be ACTIVE LOW, LEVEL triggered. >>5) TRistate interrupt line drivers are not neccessary in this scheme. >What do you mean by "this scheme?" If you mean that "ACTIVE LOW, LEVEL >triggered" is "this scheme," fine. All that is needed then is OPEN and >ACTIVE LOW -- two states in ths strictest sense (though people often use >"tristate" when all they really mean is that one state is OPEN). If "this >scheme" is "POSITIVE-GOING, EDGE triggered," see my hardware concern below. I think many of the points only apply to EISA. >Both ISA and EISA wire all interrupt "pins" on their motherboard connectors >together. The only ISA standard I have any familiarity with is the 8 MHz >IBM PC/AT, and the IBM-supplied boards that went with it. Those boards >drove their interrupt lines with two states, ACTIVE HIGH and ACTIVE LOW. >There was no OPEN state. There was no output resistor to mediate between >"dualing" bus driver circuits. Therefore, there was no possibility of >getting predictable results from putting two boards on the same interrupt. >For each of the four combinations of two boards asserting or not asserting >an interrupt you could get board-one dominance, board-two dominance, or you >could get the privilege of replacing fried parts. It all depended upon the >variable details of the driver circuits on both boards. Most of the time >the hardware survived this kind of abuse because the board designers >accounted for the possibility of people accidently installing two boards at >the same interrupt. I think most ISA boards do have tri-state drivers, but there is no standard for this. I'm only very familiar with (have a manual for :-() pre-AT designs. These devices in the IBM PC Technical Reference Manual gate the IRQ through a 74LS125: IBM Monochrome Display And Parallel Printer Adaptor (Logic 11 of 12) Parallel Printer Adaptor Asynchronous Communications Adaptor These devices are connected more or less directly: 5 1/4" Diskette Drive Adaptor (Logic 4 of 6) ('765 through MC3487 to bus) Now all these devices except the Monochrome display are usually in one chip, but the interface hasn't changed (:-(). There would be no point in leaving out the tri state enables which probably cost 0.1% as much as the jumper block for manual enables. Bruce From owner-freebsd-hardware Tue Jul 23 02:31:52 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA01531 for hardware-outgoing; Tue, 23 Jul 1996 02:31:52 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA01513 for ; Tue, 23 Jul 1996 02:31:42 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA24711; Tue, 23 Jul 1996 18:21:16 +1000 Date: Tue, 23 Jul 1996 18:21:16 +1000 From: Bruce Evans Message-Id: <199607230821.SAA24711@godzilla.zeta.org.au> To: hardware@freebsd.com, schofiel@xs4all.nl Subject: Re: The multiple COM ports discussion Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >3) There are two versions of the PIC, the original type and the > enhanced "A" variant. The original does not allow for level/edge > selection, the enhanced does. The original does not allow individual > IRQ operation selection (ie. all interrupt lines must operate with the > same mode), te enhanced does allow individual mode selection. The "A" variant was used in the original PC. I don't think the original version has been used in any "ISA" PC. The "A" version doesn't allow different modes for different lines either. >6) Individual interrupt lines can not be programmed "off" at the PIC, only > in the calling device. They can be masked. This is equivalent to "off" for the purpose of generating interrupts. Masked interrupts can still be detected by reading the Interrupt Request Register. Bruce From owner-freebsd-hardware Tue Jul 23 02:58:44 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA03662 for hardware-outgoing; Tue, 23 Jul 1996 02:58:44 -0700 (PDT) Received: from charon.siemens.be (charon.siemens.be [193.210.172.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA03633 for ; Tue, 23 Jul 1996 02:58:29 -0700 (PDT) Received: by charon.siemens.be (8.7.4/nsafe-1.3) id ; Tue, 23 Jul 1996 09:57:35 GMT Received: from atea.atea.be(193.210.197.11) by charon via smap (V1.3mjr) id sma022958; Tue Jul 23 11:57:31 1996 Received: from atdec1 by atea with SMTP (1.37.109.4/15.6-FW) id AA27757; Tue, 23 Jul 96 11:56:34 +0200 Received: from vnet by atdec1.atea.be (5.65/Ultrix3.0-C) id AA26962; Tue, 23 Jul 1996 11:57:27 +0200 Received: by vnet.atea.be; Tue, 23 Jul 96 11:57:41 +0200 Date: Tue, 23 Jul 96 12:58:11 WET Message-Id: X-Priority: 3 (Normal) To: From: (Rob Schofield) Subject: re: The multiple COM ports discussion X-Incognito-Sn: 319 X-Incognito-Format: VERSION=2.01a ENCRYPTED=NO Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Brett Glass" Wrote: | | Thank you for the summary. Only one thing there that | appears to be | incorrect; you *can* disable interrupts at the interrupt | controller. I've | written software that does it. | | Ooops, yes - I seem to be unable to express myself with any accuracy these days (it's the hot sun ;). What I MEANT was, you can't stop a device from interrupting by programming the PIC, but you CAN tell the PIC to stop listening... Rob -- Happiness is a smoking processor....... Rob Schofield M.Sc. AMIEE schofiel@xs4all.nl http://www.xs4all.nl/~schofiel From owner-freebsd-hardware Tue Jul 23 10:07:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26502 for hardware-outgoing; Tue, 23 Jul 1996 10:07:42 -0700 (PDT) Received: from ns.frihet.com (root@frihet.bayarea.net [205.219.92.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA26497 for ; Tue, 23 Jul 1996 10:07:39 -0700 (PDT) Received: from ns.frihet.com (tweten@localhost [127.0.0.1]) by ns.frihet.com (8.7.5/8.6.12) with ESMTP id KAA09614; Tue, 23 Jul 1996 10:06:38 -0700 (PDT) Message-Id: <199607231706.KAA09614@ns.frihet.com> X-Mailer: exmh version 1.6.7 5/3/96 Reply-To: "David E. Tweten" To: Bruce Evans cc: schofiel@xs4all.nl, hardware@freebsd.com Subject: Re: The multiple COM ports discussion Date: Tue, 23 Jul 1996 10:06:37 -0700 From: "David E. Tweten" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk bde@zeta.org.au said: >I think most ISA boards do have tri-state drivers, but there is no >standard for this. I'm only very familiar with (have a manual for >:-() pre-AT designs. These devices in the IBM PC Technical Reference >Manual gate the IRQ through a 74LS125: > IBM Monochrome Display And Parallel Printer Adaptor (Logic 11 of 12) > Parallel Printer Adaptor > Asynchronous Communications Adaptor >These devices are connected more or less directly: > 5 1/4" Diskette Drive Adaptor (Logic 4 of 6) ('765 through MC3487 to > bus) The confusion seems to have set in when IEEE came out with the P996 standard. The D2.02 draft of it that I have says (in section 2.5.1) that IRQ signals "are Active HI open collector signals." Unfortunately, as pointed out by Edward Solari in his book, "AT Bus Design" (copyright 1990, Annabooks), "The IBM AT and ISA platforms have defined the INTERRUPT signal lines' operation as unshared edge triggered; consequently, add-on cards have been designed with totem pole outputs. If these add-on cards are installed in an E-ISA platform, they must be the only interrupt resources on the line." EISA Standard version 3.12 also says (section 1.8) the following about EISA's two interrupt line modes: "Edge-triggered operation provides full compatibility with existing, interrupt-driven, ISA devices. Level-triggered operation facilitates the sharing of a single system interrupt by a number of devices. Level- triggered interrupts might be used, for example, to share a single interrupt between a number of serial ports." I no longer have access to the IBM schematics for AT era add-on boards. I did find a schematic for a Zenith parallel port board of the day. Though it used a tri-state buffer chip on the IRQ line, the tri-state control line was wired into the active state. It is evidence like this that leaves me convinced that ISA (as opposed to IEEE P996) boards cannot share interrupts. -- David E. Tweten | PGP Key fingerprint: | tweten@frihet.com 12141 Atrium Drive | E9 59 E7 5C 6B 88 B8 90 | tweten@and.com Saratoga, CA 95070-3162 | 65 30 2A A4 A0 BC 49 AE | (408) 446-4131 From owner-freebsd-hardware Tue Jul 23 19:17:52 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA03498 for hardware-outgoing; Tue, 23 Jul 1996 19:17:52 -0700 (PDT) Received: from psa.pencom.com (psa.pencom.com [204.217.199.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA03475; Tue, 23 Jul 1996 19:17:49 -0700 (PDT) Received: from brit.netcom.com (dfw-tx18-18.ix.netcom.com [204.31.249.210]) by psa.pencom.com (Hah!/nope) with SMTP id VAA17319; Tue, 23 Jul 1996 21:17:44 -0500 (CDT) Message-Id: <2.2.32.19960724022311.00757620@psa.pencom.com> X-Sender: rickt@psa.pencom.com X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 23 Jul 1996 21:23:11 -0500 To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org From: Rick Tait Subject: PCMCIA support in 2.1.5-RELEASE? Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi folks, I have 2.1.5-RELEASE working great on my Thinkpad 755CX, and I'd like to start getting my Megahertz 28.8 XJack PCMCIA modem working (if I can). Is there any form of PCMCIA support in the release I'm running? If not, how can I install and set it up? Has anyone ever successfully used such a modem with their FreeBSD installation? Thanks in advance, /rickt -- main(v,c)char**c;{for(v[c++]="Rick Tait \n)";(!!c)[ *c]&&(v--||--c&&execlp(*c,*c,c[!!c]+!!c,!c));**c=!c)write(!!*c,*c,!!**c);} From owner-freebsd-hardware Tue Jul 23 21:54:28 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA14629 for hardware-outgoing; Tue, 23 Jul 1996 21:54:28 -0700 (PDT) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA14608; Tue, 23 Jul 1996 21:54:22 -0700 (PDT) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id NAA29597; Wed, 24 Jul 1996 13:54:11 +0900 Date: Wed, 24 Jul 1996 13:54:11 +0900 Message-Id: <199607240454.NAA29597@frig.mt.cs.keio.ac.jp> To: rickt@psa.pencom.com Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org, hosokawa@mt.cs.keio.ac.jp Subject: Re: PCMCIA support in 2.1.5-RELEASE? In-Reply-To: Your message of Tue, 23 Jul 1996 21:23:11 -0500. <2.2.32.19960724022311.00757620@psa.pencom.com> 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 rickt@psa.pencom.com wrote: >> I have 2.1.5-RELEASE working great on my Thinkpad 755CX, and I'd like to >> start getting my Megahertz 28.8 XJack PCMCIA modem working (if I can). Is >> there any form of PCMCIA support in the release I'm running? If not, how >> can I install and set it up? Has anyone ever successfully used such a modem >> with their FreeBSD installation? I'm porting of PAO on 2.1.5-RELEASE. Please read http://www.mt.cs.keio.ac.jp/person/hosokawa/PAO/ for details. -- 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 Wed Jul 24 11:16:00 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA04519 for hardware-outgoing; Wed, 24 Jul 1996 11:16:00 -0700 (PDT) Received: from falcon.tioga.com (root@falcon.tioga.com [205.146.65.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA04514 for ; Wed, 24 Jul 1996 11:15:57 -0700 (PDT) Received: (from tbalfe@localhost) by falcon.tioga.com (8.7.5/8.6.12) id OAA16551; Wed, 24 Jul 1996 14:15:17 -0400 (EDT) Date: Wed, 24 Jul 1996 14:15:17 -0400 (EDT) From: Thomas J Balfe To: freebsd-hardware@freebsd.org Subject: Micropolis, again Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Save yourself the headache, that Micropolis 4.3GB that I had replaced (again) under warranty is giving problems once more. Jul 22 12:23:04 gryphon /kernel: , retries:2 Jul 22 12:23:04 gryphon /kernel: sd0(ahc0:0:0): MEDIUM ERROR info:77ab0b asc:11, 0 Unrecovered read error My ~messages is pretty full of this, and Micropolis is full of that, I will never buy anything from them again. I'm having the reseller replace that drive with a Quantum of the same capacity. ======================================================================== Thomas J Balfe tbalfe@tioga.com President http://www.tioga.com/ Tioga Communications, Inc 814-867-4770 ======================================================================== "Humanity has been compared...to a sleeper who handles matches in his sleep and wakes to find himself in flames." - H.G. Wells The World Set Free 1914 From owner-freebsd-hardware Wed Jul 24 11:53:54 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA06397 for hardware-outgoing; Wed, 24 Jul 1996 11:53:54 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA06391 for ; Wed, 24 Jul 1996 11:53:50 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id LAA23089; Wed, 24 Jul 1996 11:53:32 -0700 From: "Rodney W. Grimes" Message-Id: <199607241853.LAA23089@GndRsh.aac.dev.com> Subject: Re: Micropolis, again To: tbalfe@falcon.tioga.com (Thomas J Balfe) Date: Wed, 24 Jul 1996 11:53:32 -0700 (PDT) Cc: freebsd-hardware@freebsd.org In-Reply-To: from Thomas J Balfe at "Jul 24, 96 02:15:17 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Save yourself the headache, that Micropolis 4.3GB that I had replaced > (again) under warranty is giving problems once more. > > Jul 22 12:23:04 gryphon /kernel: , retries:2 > Jul 22 12:23:04 gryphon /kernel: sd0(ahc0:0:0): MEDIUM ERROR info:77ab0b > asc:11, 0 Unrecovered read error > > My ~messages is pretty full of this, and Micropolis is full of that, I > will never buy anything from them again. I'm having the reseller replace > that drive with a Quantum of the same capacity. What does the output of: scsi -f /dev/rsd0 -m 1 show? Black listing a vendor for having a single model number (MC3243 in this case) that was a lemon is going to leave you with no suppliers of disk drives :-(. And yes, the MC3243 seems to be a bit of a lemon, not as bad as the early Seagate Baracuda drives, but I have seen more failures in the field with this drive than I would have expected from a typical Micropolis. These drives also seem to be temperature sensitive, and I have noticed that on current Micropolis MC4421 drives a small thermal sensitive overtemp sticker has been added that shows if the drives case temp is >70 deg C. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Wed Jul 24 12:06:02 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA06929 for hardware-outgoing; Wed, 24 Jul 1996 12:06:02 -0700 (PDT) Received: from falcon.tioga.com (root@falcon.tioga.com [205.146.65.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA06923 for ; Wed, 24 Jul 1996 12:05:59 -0700 (PDT) Received: (from tbalfe@localhost) by falcon.tioga.com (8.7.5/8.6.12) id PAA16604; Wed, 24 Jul 1996 15:04:42 -0400 (EDT) Date: Wed, 24 Jul 1996 15:04:42 -0400 (EDT) From: Thomas J Balfe To: "Rodney W. Grimes" cc: freebsd-hardware@freebsd.org Subject: Re: Micropolis, again In-Reply-To: <199607241853.LAA23089@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 gryphon: {3} scsi -f /dev/rsd0 -m 1 AWRE (Auto Write Reallocation Enbld): 0 ARRE (Auto Read Reallocation Enbld): 0 TB (Transfer Block): 0 RC (Read Continuous): 0 EER (Enable Early Recovery): 0 PER (Post Error): 0 DTE (Disable Transfer on Error): 0 DCR (Disable Correction): 0 Read Retry Count: 14 Correction Span: 28 Head Offset Count: 0 Data Strobe Offset Count: 0 Write Retry Count: 50 Recovery Time Limit: 0 If that helps at all. Anyway, my friend Chris (hi, cause I know you're reading this too) has Micropolis 4.3s in his machines and has no problems, so I'll switch to those. ======================================================================== Thomas J Balfe tbalfe@tioga.com President http://www.tioga.com/ Tioga Communications, Inc 814-867-4770 ======================================================================== "Humanity has been compared...to a sleeper who handles matches in his sleep and wakes to find himself in flames." - H.G. Wells The World Set Free 1914 From owner-freebsd-hardware Wed Jul 24 12:28:40 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09086 for hardware-outgoing; Wed, 24 Jul 1996 12:28:40 -0700 (PDT) Received: from relay.hp.com (relay.hp.com [15.255.152.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA09051 for ; Wed, 24 Jul 1996 12:28:28 -0700 (PDT) Received: from srmail.sr.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA171626476; Wed, 24 Jul 1996 12:27:56 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA273706474; Wed, 24 Jul 1996 12:27:55 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA116046474; Wed, 24 Jul 1996 12:27:54 -0700 Message-Id: <199607241927.AA116046474@hpnmhjw.sr.hp.com> To: Thomas J Balfe Cc: freebsd-hardware@freebsd.org Subject: Re: Micropolis, again In-Reply-To: Your message of "Wed, 24 Jul 1996 15:04:42 EDT." Date: Wed, 24 Jul 1996 12:27:53 -0700 From: Darryl Okahata Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > gryphon: {3} scsi -f /dev/rsd0 -m 1 > AWRE (Auto Write Reallocation Enbld): 0 > ARRE (Auto Read Reallocation Enbld): 0 You might want to try enabling these. Of course, if your drive really is on the way out, enabling these will only postpone the inevitable. I once used a Fujitsu 2624FA that developed bad sectors. Enabling AWRE and ARRE helped, but more and more bad sectors appeared. I finally gave up and drop-kicked the drive. If you're interested, I've got a perl script around somewhere that reads out the table of remapped sectors from SCSI drives (assuming that AWRE and ARRE are enabled, of course). -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hardware Wed Jul 24 12:30:44 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09303 for hardware-outgoing; Wed, 24 Jul 1996 12:30:44 -0700 (PDT) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA09294 for ; Wed, 24 Jul 1996 12:30:42 -0700 (PDT) From: BRETT_GLASS@ccgate.infoworld.com Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0ujBWV-000wvRC; Wed, 24 Jul 96 14:31 PDT Received: from ccMail by ccgate.infoworld.com (SMTPLINK V2.11) id AA838236473; Wed, 24 Jul 96 13:21:17 PST Date: Wed, 24 Jul 96 13:21:17 PST Message-Id: <9606248382.AA838236473@ccgate.infoworld.com> To: Thomas J Balfe , freebsd-hardware@freebsd.org Subject: Micropolis, again Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > My ~messages is pretty full of this, and Micropolis is full of that, I > will never buy anything from them again. I'm having the reseller replace > that drive with a Quantum of the same capacity. Careful. Quantum was just bought by Seagate. From owner-freebsd-hardware Wed Jul 24 12:38:32 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10287 for hardware-outgoing; Wed, 24 Jul 1996 12:38:32 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA10277 for ; Wed, 24 Jul 1996 12:38:25 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id MAA23144; Wed, 24 Jul 1996 12:38:16 -0700 From: "Rodney W. Grimes" Message-Id: <199607241938.MAA23144@GndRsh.aac.dev.com> Subject: Re: Micropolis, again To: tbalfe@falcon.tioga.com (Thomas J Balfe) Date: Wed, 24 Jul 1996 12:38:15 -0700 (PDT) Cc: freebsd-hardware@freebsd.org In-Reply-To: from Thomas J Balfe at "Jul 24, 96 03:04:42 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > gryphon: {3} scsi -f /dev/rsd0 -m 1 > AWRE (Auto Write Reallocation Enbld): 0 Change this to 1 > ARRE (Auto Read Reallocation Enbld): 0 Change this to 1 > TB (Transfer Block): 0 > RC (Read Continuous): 0 > EER (Enable Early Recovery): 0 > PER (Post Error): 0 > DTE (Disable Transfer on Error): 0 > DCR (Disable Correction): 0 > Read Retry Count: 14 > Correction Span: 28 > Head Offset Count: 0 > Data Strobe Offset Count: 0 > Write Retry Count: 50 > Recovery Time Limit: 0 Your returning your drives to Micropolis as soon as they have a single media related failure :-(. I suggest you turn on AWRE and ARRE and then run a dd command to attempt to remap the block automagically: scsi -f /dev/rsd0 -m 1 -P 3 -e # Make the above changes with your editor, save and exit # Now scan the disk, hopefully it will be able to do retries and # recover the bad block... dd if=/dev/rsd0 of=/dev/null bs=32768 Your drive life will probably go up by an order of magnitude... > If that helps at all. Anyway, my friend Chris (hi, cause I know you're > reading this too) has Micropolis 4.3s in his machines and has no > problems, so I'll switch to those. What model drive are you using?? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Wed Jul 24 12:49:33 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA10943 for hardware-outgoing; Wed, 24 Jul 1996 12:49:33 -0700 (PDT) Received: from falcon.tioga.com (root@falcon.tioga.com [205.146.65.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA10935 for ; Wed, 24 Jul 1996 12:49:29 -0700 (PDT) Received: (from tbalfe@localhost) by falcon.tioga.com (8.7.5/8.6.12) id PAA16658; Wed, 24 Jul 1996 15:49:17 -0400 (EDT) Date: Wed, 24 Jul 1996 15:49:17 -0400 (EDT) From: Thomas J Balfe To: "Rodney W. Grimes" cc: freebsd-hardware@freebsd.org Subject: Re: Micropolis, again In-Reply-To: <199607241938.MAA23144@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 The last one completely died, it sounded like pebbles in an old coffee can and wouldn't even spin up. ======================================================================== Thomas J Balfe tbalfe@tioga.com President http://www.tioga.com/ Tioga Communications, Inc 814-867-4770 ======================================================================== "Humanity has been compared...to a sleeper who handles matches in his sleep and wakes to find himself in flames." - H.G. Wells The World Set Free 1914 From owner-freebsd-hardware Wed Jul 24 13:03:25 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11955 for hardware-outgoing; Wed, 24 Jul 1996 13:03:25 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA11950 for ; Wed, 24 Jul 1996 13:03:21 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id MAA23187; Wed, 24 Jul 1996 12:59:08 -0700 From: "Rodney W. Grimes" Message-Id: <199607241959.MAA23187@GndRsh.aac.dev.com> Subject: Re: Micropolis, again To: darrylo@hpnmhjw.sr.hp.com (Darryl Okahata) Date: Wed, 24 Jul 1996 12:59:08 -0700 (PDT) Cc: tbalfe@falcon.tioga.com, freebsd-hardware@freebsd.org In-Reply-To: <199607241927.AA116046474@hpnmhjw.sr.hp.com> from Darryl Okahata at "Jul 24, 96 12:27:53 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > gryphon: {3} scsi -f /dev/rsd0 -m 1 > > AWRE (Auto Write Reallocation Enbld): 0 > > ARRE (Auto Read Reallocation Enbld): 0 > > You might want to try enabling these. > > Of course, if your drive really is on the way out, enabling these > will only postpone the inevitable. I once used a Fujitsu 2624FA that > developed bad sectors. Enabling AWRE and ARRE helped, but more and more > bad sectors appeared. I finally gave up and drop-kicked the drive. > > If you're interested, I've got a perl script around somewhere that > reads out the table of remapped sectors from SCSI drives (assuming that > AWRE and ARRE are enabled, of course). I would like a copy of that please... it may even find it's way into the FreeBSD source tree... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Wed Jul 24 14:13:07 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16633 for hardware-outgoing; Wed, 24 Jul 1996 14:13:07 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA16626; Wed, 24 Jul 1996 14:13:02 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id XAA00724; Wed, 24 Jul 1996 23:13:02 +0200 (MET DST) To: "Rodney W. Grimes" cc: darrylo@hpnmhjw.sr.hp.com (Darryl Okahata), tbalfe@falcon.tioga.com, freebsd-hardware@FreeBSD.ORG Subject: Re: Micropolis, again In-reply-to: Your message of "Wed, 24 Jul 1996 12:59:08 PDT." <199607241959.MAA23187@GndRsh.aac.dev.com> Date: Wed, 24 Jul 1996 23:13:01 +0200 Message-ID: <722.838242781@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> If you're interested, I've got a perl script around somewhere that >> reads out the table of remapped sectors from SCSI drives (assuming that >> AWRE and ARRE are enabled, of course). > >I would like a copy of that please... it may even find it's way into >the FreeBSD source tree... > Yes, please: src/tools/tools ! -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hardware Wed Jul 24 14:13:47 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16685 for hardware-outgoing; Wed, 24 Jul 1996 14:13:47 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA16664; Wed, 24 Jul 1996 14:13:41 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id XAA00733; Wed, 24 Jul 1996 23:13:42 +0200 (MET DST) To: "Rodney W. Grimes" cc: darrylo@hpnmhjw.sr.hp.com (Darryl Okahata), tbalfe@falcon.tioga.com, freebsd-hardware@FreeBSD.ORG Subject: Re: Micropolis, again In-reply-to: Your message of "Wed, 24 Jul 1996 12:59:08 PDT." <199607241959.MAA23187@GndRsh.aac.dev.com> Date: Wed, 24 Jul 1996 23:13:41 +0200 Message-ID: <731.838242821@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Of course, if your drive really is on the way out, enabling these >> will only postpone the inevitable. I once used a Fujitsu 2624FA that >> developed bad sectors. Enabling AWRE and ARRE helped, but more and more >> bad sectors appeared. I finally gave up and drop-kicked the drive. Could we have a /etc/sysconfig option to enable AWRE and ARRE on all scsi-disks in the system ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hardware Wed Jul 24 14:21:51 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA17229 for hardware-outgoing; Wed, 24 Jul 1996 14:21:51 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA17215 for ; Wed, 24 Jul 1996 14:21:48 -0700 (PDT) Received: from srmail.sr.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA257733305; Wed, 24 Jul 1996 14:21:46 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA292143303; Wed, 24 Jul 1996 14:21:44 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA002163303; Wed, 24 Jul 1996 14:21:43 -0700 Message-Id: <199607242121.AA002163303@hpnmhjw.sr.hp.com> To: Poul-Henning Kamp Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Micropolis, again In-Reply-To: Your message of "Wed, 24 Jul 1996 23:13:41 +0200." <731.838242821@critter.tfs.com> Date: Wed, 24 Jul 1996 14:21:42 -0700 From: Darryl Okahata Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Could we have a /etc/sysconfig option to enable AWRE and ARRE on all > scsi-disks in the system ? Are we sure that there aren't any buggy SCSI disks out there? -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hardware Wed Jul 24 14:24:48 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA17495 for hardware-outgoing; Wed, 24 Jul 1996 14:24:48 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA17486; Wed, 24 Jul 1996 14:24:43 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id XAA00824; Wed, 24 Jul 1996 23:24:43 +0200 (MET DST) To: Darryl Okahata cc: freebsd-hardware@freebsd.org Subject: Re: Micropolis, again In-reply-to: Your message of "Wed, 24 Jul 1996 14:21:42 PDT." <199607242121.AA002163303@hpnmhjw.sr.hp.com> Date: Wed, 24 Jul 1996 23:24:43 +0200 Message-ID: <822.838243483@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199607242121.AA002163303@hpnmhjw.sr.hp.com>, Darryl Okahata writes: >> Could we have a /etc/sysconfig option to enable AWRE and ARRE on all >> scsi-disks in the system ? > > Are we sure that there aren't any buggy SCSI disks out there? That's why I want an >option< :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hardware Wed Jul 24 14:35:44 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18124 for hardware-outgoing; Wed, 24 Jul 1996 14:35:44 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA18118 for ; Wed, 24 Jul 1996 14:35:41 -0700 (PDT) Received: from srmail.sr.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA278014136; Wed, 24 Jul 1996 14:35:36 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA293474134; Wed, 24 Jul 1996 14:35:35 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA003034134; Wed, 24 Jul 1996 14:35:34 -0700 Message-Id: <199607242135.AA003034134@hpnmhjw.sr.hp.com> To: Poul-Henning Kamp Cc: freebsd-hardware@freebsd.org Subject: Re: Micropolis, again In-Reply-To: Your message of "Wed, 24 Jul 1996 23:24:43 +0200." <822.838243483@critter.tfs.com> Date: Wed, 24 Jul 1996 14:35:33 -0700 From: Darryl Okahata Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > In message <199607242121.AA002163303@hpnmhjw.sr.hp.com>, Darryl Okahata write > s: > >> Could we have a /etc/sysconfig option to enable AWRE and ARRE on all > >> scsi-disks in the system ? > > > > Are we sure that there aren't any buggy SCSI disks out there? > > That's why I want an >option< :-) Oh, duh. ;-) If it's an option, could we make it set AWRE/ARRE only if they aren't already set? It gives me the shivers to imagine an option that always touches the mode pages at bootup (what happens when power failures, bad SCSI cabling, bad termination, acts of God, etc. occur when setting the mode page?). -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hardware Wed Jul 24 14:39:39 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18429 for hardware-outgoing; Wed, 24 Jul 1996 14:39:39 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA18413; Wed, 24 Jul 1996 14:39:33 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id XAA00925; Wed, 24 Jul 1996 23:39:34 +0200 (MET DST) To: Darryl Okahata cc: freebsd-hardware@freebsd.org Subject: Re: Micropolis, again In-reply-to: Your message of "Wed, 24 Jul 1996 14:35:33 PDT." <199607242135.AA003034134@hpnmhjw.sr.hp.com> Date: Wed, 24 Jul 1996 23:39:34 +0200 Message-ID: <923.838244374@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199607242135.AA003034134@hpnmhjw.sr.hp.com>, Darryl Okahata writes: >> In message <199607242121.AA002163303@hpnmhjw.sr.hp.com>, Darryl Okahata writ >e >> s: >> >> Could we have a /etc/sysconfig option to enable AWRE and ARRE on all >> >> scsi-disks in the system ? >> > >> > Are we sure that there aren't any buggy SCSI disks out there? >> >> That's why I want an >option< :-) > > Oh, duh. ;-) > > If it's an option, could we make it set AWRE/ARRE only if they >aren't already set? It gives me the shivers to imagine an option that >always touches the mode pages at bootup (what happens when power >failures, bad SCSI cabling, bad termination, acts of God, etc. occur >when setting the mode page?). Sure, sounds fine with me. And a little comment above it telling why you may or may not want to :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hardware Wed Jul 24 15:44:44 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA22181 for hardware-outgoing; Wed, 24 Jul 1996 15:44:44 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA22176 for ; Wed, 24 Jul 1996 15:44:42 -0700 (PDT) Received: from srmail.sr.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA084968272; Wed, 24 Jul 1996 15:44:32 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA006148271; Wed, 24 Jul 1996 15:44:31 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA074368270; Wed, 24 Jul 1996 15:44:30 -0700 Message-Id: <199607242244.AA074368270@hpnmhjw.sr.hp.com> To: BRETT_GLASS@ccgate.infoworld.com Cc: Thomas J Balfe , freebsd-hardware@freebsd.org Subject: Re: Micropolis, again In-Reply-To: Your message of "Wed, 24 Jul 1996 13:21:17 PST." <9606248382.AA838236473@ccgate.infoworld.com> Date: Wed, 24 Jul 1996 15:44:30 -0700 From: Darryl Okahata Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > My ~messages is pretty full of this, and Micropolis is full of that, I > > will never buy anything from them again. I'm having the reseller replace > > that drive with a Quantum of the same capacity. > > Careful. Quantum was just bought by Seagate. When did this happen? Are you sure you're not thinking about Connor? Anyway, Quantum Atlas and Fireball drives seem to be pretty good. I've got both, and I'm quite happy with them. The Atlas is nice, fast, and expensive, and the Fireball is cheap and somewhat fast (sequential reads are a respectable ~4-4.5MB/sec, sustained, although seek times are a bit lacking). I'd stay away from Empire and, maybe, Capella drives. Anyway, when buying a drive, I believe that the reseller/vendor is just as important as the drive manufacturer. -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hardware Wed Jul 24 17:38:30 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA27965 for hardware-outgoing; Wed, 24 Jul 1996 17:38:30 -0700 (PDT) Received: from dympna (dympna.lgc.com [134.132.73.254]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA27960 for ; Wed, 24 Jul 1996 17:38:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by dympna (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id TAA02156; Wed, 24 Jul 1996 19:38:53 -0500 Date: Wed, 24 Jul 1996 19:38:53 -0500 (CDT) From: Rob Snow X-Sender: rsnow@dympna To: Thomas J Balfe cc: freebsd-hardware@freebsd.org Subject: Re: Micropolis, again 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 Wed, 24 Jul 1996, Thomas J Balfe wrote: > Save yourself the headache, that Micropolis 4.3GB that I had replaced > (again) under warranty is giving problems once more. > > Jul 22 12:23:04 gryphon /kernel: , retries:2 > Jul 22 12:23:04 gryphon /kernel: sd0(ahc0:0:0): MEDIUM ERROR info:77ab0b > asc:11, 0 Unrecovered read error > > My ~messages is pretty full of this, and Micropolis is full of that, I > will never buy anything from them again. I'm having the reseller replace > that drive with a Quantum of the same capacity. > Just sent another batch of drives back today. These have been collecting for a month or so. The tally: 2 X Seagate 10800 3 X Micropolis 1991 4 X Micropolis 1936 1 X Micropolis 1924 1 X IBM 2GB SGI OEM drive (stiction drive) What I see: 9GB FH 5.25 not up to snuff FH 5.25 Micropolis bad, bad, bad. I'll replace most of them with 3.5" drives in the 4GB range. (Probably Fujistu or Cudas.) BTW, has anyone done any sampling of the 9GB 3.5's? -Rob From owner-freebsd-hardware Wed Jul 24 23:32:31 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA21011 for hardware-outgoing; Wed, 24 Jul 1996 23:32:31 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA21006 for ; Wed, 24 Jul 1996 23:32:29 -0700 (PDT) Received: (from brett@localhost) by lariat.lariat.org (8.8.Alpha.4/8.8.Alpha.4) id AAA11778 for hardware@freebsd.org; Thu, 25 Jul 1996 00:29:20 -0600 (MDT) Date: Thu, 25 Jul 1996 00:29:20 -0600 (MDT) From: Brett Glass Message-Id: <199607250629.AAA11778@lariat.lariat.org> To: hardware@freebsd.org Subject: EN-2400P3 Ethernet Card: Supported? Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just tried to install FreeBSD onto a machine with an EN-2400P3 card. This card is a generic -- apparently an NE2000 clone -- with no DIP switches or jumpers. There's not even a manufacturer's name on the card, though the main chip says "Winbond W89C904AXF" and the voltage converter and hybrid say "YCL." How do I configure this beast to run under FreeBSD? Or can it be done? --Brett From owner-freebsd-hardware Thu Jul 25 00:20:09 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA23386 for hardware-outgoing; Thu, 25 Jul 1996 00:20:09 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA23381 for ; Thu, 25 Jul 1996 00:20:05 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id AAA03507; Thu, 25 Jul 1996 00:18:21 -0700 (PDT) Message-Id: <199607250718.AAA03507@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: BRETT_GLASS@ccgate.infoworld.com cc: Thomas J Balfe , freebsd-hardware@freebsd.org Subject: Re: Micropolis, again In-reply-to: Your message of Wed, 24 Jul 96 13:21:17 -0800. <9606248382.AA838236473@ccgate.infoworld.com> Date: Thu, 25 Jul 1996 00:17:53 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> My ~messages is pretty full of this, and Micropolis is full of that, I >> will never buy anything from them again. I'm having the reseller replace >> that drive with a Quantum of the same capacity. >Careful. Quantum was just bought by Seagate. You're not serious, I hope. Regardless, current Quantum drivers are not going to deteriorate just by association. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-hardware Thu Jul 25 01:05:50 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA25493 for hardware-outgoing; Thu, 25 Jul 1996 01:05:50 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA25485 for ; Thu, 25 Jul 1996 01:05:45 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id BAA20248; Thu, 25 Jul 1996 01:05:45 -0700 (PDT) Message-Id: <199607250805.BAA20248@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Brett Glass cc: hardware@FreeBSD.org Subject: Re: EN-2400P3 Ethernet Card: Supported? In-reply-to: Your message of "Thu, 25 Jul 1996 00:29:20 MDT." <199607250629.AAA11778@lariat.lariat.org> From: David Greenman Reply-To: dg@root.com Date: Thu, 25 Jul 1996 01:05:45 -0700 Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Just tried to install FreeBSD onto a machine with an EN-2400P3 >card. This card is a generic -- apparently an NE2000 clone -- with >no DIP switches or jumpers. There's not even a manufacturer's name >on the card, though the main chip says "Winbond W89C904AXF" and >the voltage converter and hybrid say "YCL." > >How do I configure this beast to run under FreeBSD? Or can it >be done? I've never heard of that particular chip, but if it is supposed to be NE2000 compatible, then the 'ed' driver would be the one to use with it. If it is soft configured, you'll have to either use the configuration program that comes with it (if you have it) or guess at it's settings. Good luck. :-) -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Thu Jul 25 01:41:25 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA27599 for hardware-outgoing; Thu, 25 Jul 1996 01:41:25 -0700 (PDT) Received: from hda.com (ip31-max1-fitch.zipnet.net [199.232.245.31]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA27593 for ; Thu, 25 Jul 1996 01:41:20 -0700 (PDT) Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id EAA01870; Thu, 25 Jul 1996 04:34:52 -0400 From: Peter Dufault Message-Id: <199607250834.EAA01870@hda.com> Subject: Re: Micropolis, again To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Thu, 25 Jul 1996 04:34:52 -0400 (EDT) Cc: tbalfe@falcon.tioga.com, freebsd-hardware@FreeBSD.ORG In-Reply-To: <199607241938.MAA23144@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Jul 24, 96 12:38:15 pm Reply-to: hdalog@zipnet.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > scsi -f /dev/rsd0 -m 1 -P 3 -e > # Make the above changes with your editor, save and exit > > # Now scan the disk, hopefully it will be able to do retries and > # recover the bad block... It was an unrecoverable read error - it won't remap. He'll have to write to that block. -- 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 Thu Jul 25 05:20:15 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA22984 for hardware-outgoing; Thu, 25 Jul 1996 05:20:15 -0700 (PDT) Received: from phil.digitaladvantage.net (phil.digitaladvantage.net [207.40.157.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA22979 for ; Thu, 25 Jul 1996 05:20:13 -0700 (PDT) Received: from pamela.digitaladvantage.net (pamela.digitaladvantage.net [207.40.157.16]) by phil.digitaladvantage.net (8.7.5/8.7.3) with SMTP id FAA26054; Thu, 25 Jul 1996 05:55:52 -0500 (CDT) From: zeeb@digitaladvantage.net (Russ Panula) To: Rob Snow Cc: freebsd-hardware@freebsd.org Subject: Re: Micropolis, again Date: Thu, 25 Jul 1996 13:27:56 GMT Organization: Digital Advantage Corporation Message-ID: <31f775a6.3584271@mail.digitaladvantage.net> References: In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Jul 1996 19:38:53 -0500 (CDT), you wrote: >On Wed, 24 Jul 1996, Thomas J Balfe wrote: >> Save yourself the headache, that Micropolis 4.3GB that I had replaced >> (again) under warranty is giving problems once more. >> >> Jul 22 12:23:04 gryphon /kernel: , retries:2 >> Jul 22 12:23:04 gryphon /kernel: sd0(ahc0:0:0): MEDIUM ERROR info:77ab0b >> asc:11, 0 Unrecovered read error >> >> My ~messages is pretty full of this, and Micropolis is full of that, I >> will never buy anything from them again. I'm having the reseller replace >> that drive with a Quantum of the same capacity. >> >Just sent another batch of drives back today. These have been collecting >for a month or so. The tally: > >2 X Seagate 10800 >3 X Micropolis 1991 >4 X Micropolis 1936 >1 X Micropolis 1924 >1 X IBM 2GB SGI OEM drive (stiction drive) > >What I see: >9GB FH 5.25 not up to snuff >FH 5.25 Micropolis bad, bad, bad. > >I'll replace most of them with 3.5" drives in the 4GB range. (Probably >Fujistu or Cudas.) BTW, has anyone done any sampling of the 9GB 3.5's? > >-Rob > > Say, just out of curiosity, what type of Adaptec card are you using? Is it one of those Ultra SCSI cards? From owner-freebsd-hardware Thu Jul 25 09:55:26 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10980 for hardware-outgoing; Thu, 25 Jul 1996 09:55:26 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA10975 for ; Thu, 25 Jul 1996 09:55:24 -0700 (PDT) Received: (from brett@localhost) by lariat.lariat.org (8.8.Alpha.4/8.8.Alpha.4) id EAA12577 for hardware@freebsd.org; Thu, 25 Jul 1996 04:54:57 -0600 (MDT) Date: Thu, 25 Jul 1996 04:54:57 -0600 (MDT) From: Brett Glass Message-Id: <199607251054.EAA12577@lariat.lariat.org> To: hardware@freebsd.org Subject: Handling of disk errors Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've just attempted to put FreeBSD on a system whose hard disk has a few weak spots. The system is reporting soft ECC errors on reads now and then. How do I map these areas out? Also, when I attempted to recompile the kernel, cc balked in the middle, saying cc: Internal compiler error: program cc1 got fatal signal 11 Sendmail also died with a sig 13. Could this be a result of the soft disk errors, or is it due to something else? --Brett From owner-freebsd-hardware Thu Jul 25 10:51:25 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA16006 for hardware-outgoing; Thu, 25 Jul 1996 10:51:25 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA16000 for ; Thu, 25 Jul 1996 10:51:23 -0700 (PDT) Received: (from brett@localhost) by lariat.lariat.org (8.8.Alpha.4/8.8.Alpha.4) id FAA12702 for hardware@freebsd.org; Thu, 25 Jul 1996 05:49:47 -0600 (MDT) Date: Thu, 25 Jul 1996 05:49:47 -0600 (MDT) From: Brett Glass Message-Id: <199607251149.FAA12702@lariat.lariat.org> To: hardware@freebsd.org Subject: More info about disk problem Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Have gotten the system to mail me (on a different machine) its bootstrap messages, which show the bad sector. They look like this (skip to the end to see the disk error): > FreeBSD 2.1.5-RELEASE #0: Wed Jul 17 03:09:31 1996 > jkh@whisker.cdrom.com:/usr/src/sys/compile/GENERIC > CPU: Cy486DLC (486-class CPU) > Origin = "Cyrix" > real memory = 4587520 (4480K bytes) > avail memory = 2732032 (2668K bytes) > pcibus_setup(1): mode1res=0xffffffff (0x80000000), mode2res=0xff (0x0e) > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: MDA/hercules <16 virtual consoles, flags=0x0> > ed0 at 0x300-0x31f irq 5 on isa > ed0: address 00:40:c7:10:61:6c, type NE1000 (8 bit) > ed1: disabled, not probed. > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > sio2: disabled, not probed. > sio3: disabled, not probed. > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > lpt1: disabled, not probed. > mse0: disabled, not probed. > psm0: disabled, not probed. > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: NEC 765 > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 124MB (255255 sectors), 1001 cyls, 15 heads, 17 S/T, 512 B/S > wdc1: disabled, not probed. > bt0: disabled, not probed. > uha0: disabled, not probed. > aha0: disabled, not probed. > aic0: disabled, not probed. > nca0: disabled, not probed. > nca1: disabled, not probed. > sea0: disabled, not probed. > wt0: disabled, not probed. > mcd0: disabled, not probed. > matcdc0: disabled, not probed. > scd0: disabled, not probed. > ie0: disabled, not probed. > ep0: disabled, not probed. > ix0: disabled, not probed. > le0: disabled, not probed. > lnc0: disabled, not probed. > ze0: disabled, not probed. > zp0: disabled, not probed. > npx0 on motherboard > npx0: 387 emulator > Device configuration finished. > Considering FFS root f/s. > Configuring root and swap devs. > configure() finished. > BIOS Geometries: > 0:03e70e11 0..999=1000 cylinders, 0..14=15 heads, 1..17=17 sectors > 1:01300311 0..304=305 cylinders, 0..3=4 heads, 1..17=17 sectors > 0 accounted for > wd0s1: type 0xa5, start 0, end = 255254, size 255255 : OK > wd0: interrupt timeout: > wd0: status 5c error 4 > wd0a: soft ecc reading fsbn 27808 of 27760-27823 (wd0 bn 27808; cn 27808 tn 0 sn 0)wd0: status 5c error 1 > wd0: interrupt timeout: > wd0: status 5c error 1 If I'm reading this correctly, the drive takes a long time to respond because it's correcting an error, but eventually gets the right data. (That *is* what the "no_dam" part means, right?) There seem to be a few utilities included in FreeBSD that might be able to correct the problem, but it's unclear how to use them or whether they will work on an IDE drive. Also, it's not clear how one determines which file(s) might have to be replaced in case they've been corrupted. Since this system is new, I'm willing to reinstall FreeBSD if I can, in the process, scan the disk for bad blocks and map them out. Is this possible? Or can I do this without reinstalling and be sure that I will not be left with anything corrupted? From owner-freebsd-hardware Thu Jul 25 11:33:51 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA19990 for hardware-outgoing; Thu, 25 Jul 1996 11:33:51 -0700 (PDT) Received: from falcon.tioga.com (root@falcon.tioga.com [205.146.65.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA19985 for ; Thu, 25 Jul 1996 11:33:47 -0700 (PDT) Received: (from tbalfe@localhost) by falcon.tioga.com (8.7.5/8.6.12) id OAA18073; Thu, 25 Jul 1996 14:33:30 -0400 (EDT) Date: Thu, 25 Jul 1996 14:33:29 -0400 (EDT) From: Thomas J Balfe To: "Rodney W. Grimes" cc: freebsd-hardware@freebsd.org Subject: Re: Micropolis, again In-Reply-To: <199607241938.MAA23144@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 Thank you for showing me that little trick, I am going to apply those changes today, I'll let you know how it went. The model # is 3243. ======================================================================== Thomas J Balfe tbalfe@tioga.com President http://www.tioga.com/ Tioga Communications, Inc 814-867-4770 ======================================================================== "Humanity has been compared...to a sleeper who handles matches in his sleep and wakes to find himself in flames." - H.G. Wells The World Set Free 1914 From owner-freebsd-hardware Thu Jul 25 12:32:51 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA24846 for hardware-outgoing; Thu, 25 Jul 1996 12:32:51 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA24795 for ; Thu, 25 Jul 1996 12:32:37 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA26642; Thu, 25 Jul 1996 12:32:02 -0700 (PDT) Received: from shrimp.whistle.com(207.76.205.74) by whistle.com via smap (V1.3) id sma026640; Thu Jul 25 12:31:54 1996 Received: (from julian@localhost) by shrimp.whistle.com (8.6.12/8.6.12) id MAA24776; Thu, 25 Jul 1996 12:31:54 -0700 From: Julian Elischer Message-Id: <199607251931.MAA24776@shrimp.whistle.com> Subject: Re: Handling of disk errors To: brett@lariat.org (Brett Glass) Date: Thu, 25 Jul 1996 12:31:53 -0700 (PDT) Cc: hardware@freebsd.org In-Reply-To: <199607251054.EAA12577@lariat.lariat.org> from "Brett Glass" at Jul 25, 96 04:54:57 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 we just had both these problems we had to change the disk to mode0.. it was to fast for the bus in mode4 (haven't tried modes 1,2,3) this resulted in bad transfers and memory faults > > I've just attempted to put FreeBSD on a system whose hard disk has a few > weak spots. The system is reporting soft ECC errors on reads now and > then. How do I map these areas out? Also, when I attempted to recompile > the kernel, cc balked in the middle, saying > > cc: Internal compiler error: program cc1 got fatal signal 11 > > Sendmail also died with a sig 13. Could this be a result of the soft > disk errors, or is it due to something else? > > --Brett > From owner-freebsd-hardware Thu Jul 25 12:45:07 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA26090 for hardware-outgoing; Thu, 25 Jul 1996 12:45:07 -0700 (PDT) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA26084 for ; Thu, 25 Jul 1996 12:45:00 -0700 (PDT) From: BRETT_GLASS@ccgate.infoworld.com Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0ujYET-000wxlC; Thu, 25 Jul 96 14:46 PDT Received: from ccMail by ccgate.infoworld.com (SMTPLINK V2.11) id AA838323713; Thu, 25 Jul 96 13:39:06 PST Date: Thu, 25 Jul 96 13:39:06 PST Message-Id: <9606258383.AA838323713@ccgate.infoworld.com> To: Darryl Okahata Cc: tbalfe@falcon.tioga.com, freebsd-hardware@freebsd.org Subject: Re: Micropolis, again Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > When did this happen? Are you sure you're not thinking about > Connor? Oops.... You're right. It's Conner. But the wave of consolidations is depressing. Fewer choices, and fewer opportunities to pay a little more for a better product. (Apparently, computer OEMs don't care about quality -- just price.) --Brett From owner-freebsd-hardware Thu Jul 25 14:48:53 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA03656 for hardware-outgoing; Thu, 25 Jul 1996 14:48:53 -0700 (PDT) Received: from cbgw1.att.com (cbgw1.att.com [192.20.239.133]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA03646 for ; Thu, 25 Jul 1996 14:48:45 -0700 (PDT) Received: from aloft by cbig1.att.att.com (SMI-8.6/EMS-1.2 sol2) id RAA11744; Thu, 25 Jul 1996 17:30:08 -0400 Received: from stargazer (stargazer.cnet.att.com) by aloft (4.1/DCS-aloft-M5.1) id AA26270; Thu, 25 Jul 96 17:35:04 EDT Received: by stargazer (4.1/DCS-aloft_client-S2.1) id AA18086; Thu, 25 Jul 96 17:35:00 EDT Date: Thu, 25 Jul 96 17:35:00 EDT From: gtc@aloft.att.com (gary.corcoran) Message-Id: <9607252135.AA18086@stargazer> To: BRETT_GLASS@ccgate.infoworld.com, darrylo@hpnmhjw.sr.hp.com Subject: Re: Micropolis, again Cc: freebsd-hardware@freebsd.org, tbalfe@falcon.tioga.com Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Oops.... You're right. It's Conner. But the wave of consolidations is >depressing. Fewer choices, and fewer opportunities to pay a little more for >a better product. (Apparently, computer OEMs don't care about quality -- >just price.) Overall, true. But some of you may be interested to know: Quantum makes at least two 4G 3.5" drives. The XP34301 and the XP34300 (Atlas). The 34301 I believe is a later model, and it is about $30 cheaper than the 34300. But I looked at the specs on these drives. The Atlas (34300) has an *order of magnitude* lower bit error rate than the cheaper drive. I decided to pay a little more and get the Atlas. But I'd bet that mass-market OEM's would use the 34301's (if they used a 4G drive)... BTW, I chose this drive after previously buying a Micropolis MC3243 which died (stopped spinning) 6 weeks after buying it. The replacement MC3243 though has been running fine for about a year. I had chosen a Micropolis drive because my Micropolis 1924 (2G 5.25" FH) drive had run flawlessly (though very very warm) for a couple of years (now over 3 years). I guess buying disk drives is like buying cars - any model may have a particular unit that is a lemon, but certain models end up having more lemons than others... Gary From owner-freebsd-hardware Thu Jul 25 15:07:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA04709 for hardware-outgoing; Thu, 25 Jul 1996 15:07:24 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA04703 for ; Thu, 25 Jul 1996 15:07:22 -0700 (PDT) Received: from srmail.sr.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA211602426; Thu, 25 Jul 1996 15:07:06 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA171932425; Thu, 25 Jul 1996 15:07:05 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA005032424; Thu, 25 Jul 1996 15:07:04 -0700 Message-Id: <199607252207.AA005032424@hpnmhjw.sr.hp.com> To: gtc@aloft.att.com (gary.corcoran) Cc: BRETT_GLASS@ccgate.infoworld.com, freebsd-hardware@freebsd.org Subject: Re: Micropolis, again In-Reply-To: Your message of "Thu, 25 Jul 1996 17:35:00 EDT." <9607252135.AA18086@stargazer> Date: Thu, 25 Jul 1996 15:07:04 -0700 From: Darryl Okahata Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >Oops.... You're right. It's Conner. But the wave of consolidations is > >depressing. Fewer choices, and fewer opportunities to pay a little more for > >a better product. (Apparently, computer OEMs don't care about quality -- > >just price.) > > Overall, true. But some of you may be interested to know: > Quantum makes at least two 4G 3.5" drives. The XP34301 and the > XP34300 (Atlas). The Atlas was, originally, a DEC design, and I believe that the 34301 (the Grand Prix) is a Quantum design. Of these two, the Atlas is the preferred drive. ;-) The Atlas II is about to hit the market, and so it's unknown if the Atlas II is as good as the Atlas. > BTW, I chose this drive after previously buying a Micropolis MC3243 > which died (stopped spinning) 6 weeks after buying it. The replacement Does anyone know if the Micropolis 4221 is a reliable drive? -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hardware Thu Jul 25 15:42:22 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA07065 for hardware-outgoing; Thu, 25 Jul 1996 15:42:22 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA07055 for ; Thu, 25 Jul 1996 15:42:19 -0700 (PDT) Received: (from brett@localhost) by lariat.lariat.org (8.8.Alpha.4/8.8.Alpha.4) id KAA13447; Thu, 25 Jul 1996 10:41:53 -0600 (MDT) Date: Thu, 25 Jul 1996 10:41:53 -0600 (MDT) From: Brett Glass Message-Id: <199607251641.KAA13447@lariat.lariat.org> To: brett@lariat.org, julian@whistle.com Subject: Re: Handling of disk errors Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The disk isn't new; it probably isn't too fast for the bus. But we clearly do have a bad sector.... Need to map it out somehow. Worse yet, since we see the error during boot, it may be where the kernel is stored. --Brett From owner-freebsd-hardware Thu Jul 25 15:51:51 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA07676 for hardware-outgoing; Thu, 25 Jul 1996 15:51:51 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA07670 for ; Thu, 25 Jul 1996 15:51:49 -0700 (PDT) Received: (from brett@localhost) by lariat.lariat.org (8.8.Alpha.4/8.8.Alpha.4) id KAA13486; Thu, 25 Jul 1996 10:51:30 -0600 (MDT) Date: Thu, 25 Jul 1996 10:51:30 -0600 (MDT) From: Brett Glass Message-Id: <199607251651.KAA13486@lariat.lariat.org> To: brett@lariat.org, julian@whistle.com Subject: Re: Handling of disk errors Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk By the way, just in case it DOES do something, how does one change the transfer mode? --Brett From owner-freebsd-hardware Thu Jul 25 16:14:20 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA09139 for hardware-outgoing; Thu, 25 Jul 1996 16:14:20 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA09123 for ; Thu, 25 Jul 1996 16:14:11 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id QAA24289; Thu, 25 Jul 1996 16:08:38 -0700 From: "Rodney W. Grimes" Message-Id: <199607252308.QAA24289@GndRsh.aac.dev.com> Subject: Re: Micropolis, again To: darrylo@hpnmhjw.sr.hp.com (Darryl Okahata) Date: Thu, 25 Jul 1996 16:08:38 -0700 (PDT) Cc: gtc@aloft.att.com, BRETT_GLASS@ccgate.infoworld.com, freebsd-hardware@freebsd.org In-Reply-To: <199607252207.AA005032424@hpnmhjw.sr.hp.com> from Darryl Okahata at "Jul 25, 96 03:07:04 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >Oops.... You're right. It's Conner. But the wave of consolidations is > > >depressing. Fewer choices, and fewer opportunities to pay a little more for > > >a better product. (Apparently, computer OEMs don't care about quality -- > > >just price.) > > > > Overall, true. But some of you may be interested to know: > > Quantum makes at least two 4G 3.5" drives. The XP34301 and the > > XP34300 (Atlas). > > The Atlas was, originally, a DEC design, and I believe that the > 34301 (the Grand Prix) is a Quantum design. That is more or less correct. The Atlas series drives are manufactured in one of the DEC plants that Quantum aquired when it bought the DEC hard drive division. I am unclear on who really designed the drives. > Of these two, the Atlas is the preferred drive. ;-) Most defanitly. > The Atlas II is about to hit the market, and so it's unknown if the > Atlas II is as good as the Atlas. Only time is going to let us know that... > > > BTW, I chose this drive after previously buying a Micropolis MC3243 > > which died (stopped spinning) 6 weeks after buying it. The replacement > > Does anyone know if the Micropolis 4221 is a reliable drive? I have not seen any problems in the field with them, do note however that the 4221 has been end of lifed and replaced with the 4421. Also as of the end of June Quantum officially end of lifed the 2G Atlas (XP32150AL-S), though units are still in the channel. It is unclear if the XP34300 has also been end of lifed :-(. Seems Quantum does EOL before the channel gets a chance to get any of the new models, double :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Fri Jul 26 07:22:30 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA28908 for hardware-outgoing; Fri, 26 Jul 1996 07:22:30 -0700 (PDT) Received: from falcon.tioga.com (root@falcon.tioga.com [205.146.65.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA28896 for ; Fri, 26 Jul 1996 07:22:26 -0700 (PDT) Received: (from tbalfe@localhost) by falcon.tioga.com (8.7.5/8.6.12) id KAA19355; Fri, 26 Jul 1996 10:22:28 -0400 (EDT) Date: Fri, 26 Jul 1996 10:22:27 -0400 (EDT) From: Thomas J Balfe To: freebsd-hardware@freebsd.org Subject: MOSIX Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone seen MOSIX? It's BSDI based, and I was wondering if anything was planned for FreeBSD that is similar. http://www.cs.huji.ac.il/mosix/ ======================================================================== Thomas J Balfe tbalfe@tioga.com President http://www.tioga.com/ Tioga Communications, Inc 814-867-4770 ======================================================================== "Humanity has been compared...to a sleeper who handles matches in his sleep and wakes to find himself in flames." - H.G. Wells The World Set Free 1914 From owner-freebsd-hardware Fri Jul 26 14:35:46 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00123 for hardware-outgoing; Fri, 26 Jul 1996 14:35:46 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA00115 for ; Fri, 26 Jul 1996 14:35:44 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.5/8.7.3) with ESMTP id OAA00472 for ; Fri, 26 Jul 1996 14:34:59 -0700 (PDT) Message-Id: <199607262134.OAA00472@austin.polstra.com> To: freebsd-hardware@freebsd.org Subject: Which inode contains a given bad block? Date: Fri, 26 Jul 1996 14:34:59 -0700 From: John Polstra Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yesterday, I had to clean up a couple of bad blocks in my /usr filesystem. Is there a utility that will help me to figure out which inodes, if any, contained the bad blocks? In the olden days, this used to be possible, with icheck's "-b" option. Unfortunately, icheck has been replaced by fsck, which doesn't have that functionality. Short of writing a program myself, is there a way to do it under FreeBSD? Thanks, John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hardware Fri Jul 26 14:38:46 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00350 for hardware-outgoing; Fri, 26 Jul 1996 14:38:46 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [206.151.208.162]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA00344 for ; Fri, 26 Jul 1996 14:38:43 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.5/8.7.3) with SMTP id QAA27228; Fri, 26 Jul 1996 16:38:37 -0500 (CDT) Date: Fri, 26 Jul 1996 16:38:36 -0500 (CDT) From: "Matthew N. Dodd" X-Sender: winter@sasami To: Thomas J Balfe cc: freebsd-hardware@freebsd.org Subject: Re: MOSIX 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 Fri, 26 Jul 1996, Thomas J Balfe wrote: > Has anyone seen MOSIX? It's BSDI based, and I was wondering if anything > was planned for FreeBSD that is similar. > > http://www.cs.huji.ac.il/mosix/ Source for MO6 is available on their page... | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-hardware Fri Jul 26 15:12:48 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA06889 for hardware-outgoing; Fri, 26 Jul 1996 15:12:48 -0700 (PDT) Received: from gallup.cia-g.com (root@gallup.cia-g.com [206.206.162.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA06836; Fri, 26 Jul 1996 15:12:37 -0700 (PDT) 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 QAA17913; Fri, 26 Jul 1996 16:13:09 -0600 Date: Fri, 26 Jul 1996 16:13:08 -0600 (MDT) From: Stephen Fisher To: hardware@freebsd.org, hackers@freebsd.org Subject: Fatal trap 12: page fault while in kernel mode Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all. Maybe you could help me figure out what's giving me these problems. On this particular computer I get these kind of errors a *lot*, almost always with the same instruction pointer. (This is running 2.1.5R, I had the same problems with 2.1R). Sometimes the machine will even "Freeze" and reboot in the middle of doing something with no warning..:] -- Fatal tral 12: page fault while in kernel mode Fault virtual address = 0xfc7 Fault code = supervisor read, page not present Instruction pointer = 0x8:0xf0181de2 Code segment = base 0x0, limit 0xfffff, type 0x1b DPL 0, pres 1, def32 1, gran 0 Processor eflags = interrupt enabled, resume, IOPL = 0 Current process = 249 (cpp) Interrupt mask = panic: page fault -- As I said it almost always happens on the same instruction pointer. The process can be anything but it usually occurs with gcc (such as when compiling the kernel, I can't even get a minute or two into the compile). Hardware: 16meg of parity ram, AMD DX4/100, SiS 85c471 chipset motherboard (ick!) with VLB bus, Adaptec 284x SCSI controller, S3 video card, etc. I will most likely be replacing the motherboard with a better one, but I would like to know if this is going to fix it? Thanks for any tips, pointers, ideas you can give me.. Forgive me if I type of message is not welcome in one or both of these mailing lists. - Steve - Systems Manager - Community Internet Access - http://www.cia-g.com From owner-freebsd-hardware Sat Jul 27 04:45:33 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03323 for hardware-outgoing; Sat, 27 Jul 1996 04:45:33 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA03298; Sat, 27 Jul 1996 04:45:28 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA21613; Sat, 27 Jul 1996 13:45:18 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA27430; Sat, 27 Jul 1996 13:45:18 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id LAA29344; Sat, 27 Jul 1996 11:52:51 +0200 (MET DST) From: J Wunsch Message-Id: <199607270952.LAA29344@uriah.heep.sax.de> Subject: Re: Fatal trap 12: page fault while in kernel mode To: lithium@cia-g.com (Stephen Fisher) Date: Sat, 27 Jul 1996 11:52:51 +0200 (MET DST) Cc: hardware@freebsd.org, hackers@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Stephen Fisher at "Jul 26, 96 04:13:08 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Stephen Fisher wrote: > Instruction pointer = 0x8:0xf0181de2 > As I said it almost always happens on the same instruction pointer. The Do a nm /kernel | sort | more and see which function above address is in. If you are a more adventurous type, you can also disassemble the function with gdb, and try to find the corresponding source line. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hardware Sat Jul 27 11:01:51 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA23195 for hardware-outgoing; Sat, 27 Jul 1996 11:01:51 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA23190 for ; Sat, 27 Jul 1996 11:01:50 -0700 (PDT) Received: (from brett@localhost) by lariat.lariat.org (8.8.Alpha.4/8.8.Alpha.4) id MAA20534 for hardware@freebsd.org; Sat, 27 Jul 1996 12:02:06 -0600 (MDT) Date: Sat, 27 Jul 1996 12:02:06 -0600 (MDT) From: Brett Glass Message-Id: <199607271802.MAA20534@lariat.lariat.org> To: hardware@freebsd.org Subject: DigiBoard driver: How to use with X/em? Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have here a brand-spanking-new DigiBoard PC/Xem intelligent serial card, plus a cable and a box with 16 RS-232 connectors. However, I can't seem to get them working with the FreeBSD DigiBoard driver. When I build and boot from a kernel with the dgb driver installed, I get: dgb0: PC/Xi 512K dgb0 at 0x204-0x207 maddr 0xfc0000 msize 524288 on isa dgb0: 2nd reset failed and the ports don't work. It looks as if the card is recognized; however, the second message suggests a hardware problem. The docs hint that there might be a problem with the card in machines with more than 15 MB of RAM, but when I cut the amount to 8 MB I got the same result. How can I find out what's wrong? --Brett From owner-freebsd-hardware Sat Jul 27 23:13:25 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA01167 for hardware-outgoing; Sat, 27 Jul 1996 23:13:25 -0700 (PDT) Received: from s29.netgate.net (s29.netgate.net [205.214.175.29]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA01161 for ; Sat, 27 Jul 1996 23:13:20 -0700 (PDT) Received: from s29.netgate.net (localhost [127.0.0.1]) by s29.netgate.net (8.6.12/8.6.12) with SMTP id XAA03084 for ; Sat, 20 Jul 1996 23:19:40 GMT Message-ID: <31F16989.41C67EA6@netgate.net> Date: Sat, 20 Jul 1996 23:19:37 +0000 From: Matt Clark X-Mailer: Mozilla 2.02 (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Good Video Card For X? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What Video card would be good for the following Application: + XFree86 3.12 (Duh!) + Netscape / Minimal-Some Image Editing + None-Minimal Video Playing I was thinking of buying the Diamond Stealth 64 (VLB, 2mb VRAM). Is there and gotcha's and or KABOOM's with this video card. I really need a new one, because my Stealth 24 does 256 colors in X. Thanks! (And I do know how annoying it can get for people to say 'What should I get?' Sorry) -matt Clark