From owner-freebsd-hardware Sun Sep 7 03:16:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA12200 for hardware-outgoing; Sun, 7 Sep 1997 03:16:32 -0700 (PDT) Received: from shadows.aeon.net (bsdhw@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA12130 for ; Sun, 7 Sep 1997 03:15:47 -0700 (PDT) Received: (from bsdhw@localhost) by shadows.aeon.net (8.8.7/8.8.3) id NAA28715; Sun, 7 Sep 1997 13:08:56 +0300 (EET DST) From: mika ruohotie Message-Id: <199709071008.NAA28715@shadows.aeon.net> Subject: Re: Mixing DIMMS and SIMMS In-Reply-To: from Greg Pavelcak at "Aug 30, 97 00:46:14 am" To: gpavelcak@philos.umass.edu (Greg Pavelcak) Date: Sun, 7 Sep 1997 13:08:56 +0300 (EET DST) Cc: freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm about to get a new motherboard, and I'd like to survey people > about the possibility of mixing DIMMS and SIMMS. I know the Asus > web-site advises against it, but the specs for the Gigabyte TX > motherboard say it can be done. Although it says to be sure to follow > the manual's instructions for the proper combinations. > > Opinions? you can do it, even safely, if you use DIMMS that can use 5V, it seems to me that all those mb's i've seen so far (asus, abit, chaintech, shuttle and few otherse) will "force" the 5V to DIMM sockets too when SIMMs are used... *shrug* i wouldnt suggest testing it though. =) general question, your board, does it support over 66MHz buss speeds? how about running few tests with it? (below) dd if=/dev/zero of=/dev/null bs=1m count=1000 dd if=/dev/zero of=/dev/null bs=128k count=8000 at least the older Gigabytes were faster than about all other boards with the 66MHz bus, so if the TX is too... mickey From owner-freebsd-hardware Sun Sep 7 06:20:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA17726 for hardware-outgoing; Sun, 7 Sep 1997 06:20:51 -0700 (PDT) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA17721 for ; Sun, 7 Sep 1997 06:20:45 -0700 (PDT) Received: (from arg@localhost) by arg1.demon.co.uk (8.8.5/8.8.5) id OAA14410; Sun, 7 Sep 1997 14:21:37 +0100 (BST) Date: Sun, 7 Sep 1997 14:21:36 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Chris Dillon cc: freebsd-hardware@FreeBSD.ORG Subject: RE: Problems with 16650 UARTs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 5 Sep 1997, Chris Dillon wrote: > > On 06-Sep-97 Andrew Gordon wrote: > > [16650 problems] > > Bingo... I have been plagued with this same problem for some time, but > thought it was just my lousy, clueless ISP at the root of it all (uses NT > of all things... and Telebit Netblazer term servers. Are those any good?). > > I run 2.2-STABLE (recently cvsupped and made world) with userland ppp on an > internal USR Sportster 33k6 with the port locked at 115200 using hardware > flow control. I can be chatting on IRC, browsing web pages, and downloading > some mail when all incoming data comes to a halt (even sometimes when just > doing nothing). The only fix seems to be to kill the ppp session and dial > in again (I usually just 'quit' and then run userland ppp all over again). > I know that outgoing packets still work because anything I type in an IRC > channel makes it out into the world.. I just don't get anything back. I don't think your problem is related to what I am seeing. My problem only appears with 16_6_50 UARTs, which your Sportster internal is unlikely to have; also, my problem is so severe that you would probably consider your ISP connection unusable if you had the same problem. I think your first diagnosis (flaky ISP) was probably correct. From owner-freebsd-hardware Sun Sep 7 07:38:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA20580 for hardware-outgoing; Sun, 7 Sep 1997 07:38:50 -0700 (PDT) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA20574 for ; Sun, 7 Sep 1997 07:38:48 -0700 (PDT) Received: from [207.3.81.149] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id ra267401 for ; Sun, 7 Sep 1997 09:39:07 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 07 Sep 1997 09:34:29 -0000 (GMT) From: Chris Dillon To: Andrew Gordon Subject: RE: Problems with 16650 UARTs Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 07-Sep-97 Andrew Gordon wrote: >On Fri, 5 Sep 1997, Chris Dillon wrote: >> >> On 06-Sep-97 Andrew Gordon wrote: >> > [16650 problems] >I think your first diagnosis (flaky ISP) was probably correct. Apparently I missed the part about you using 16650's. The 16550 in my Sportster is emulated and not discrete, and probably flawed in some way or another. Needless to say, the problem I have is still annoying. :) (annoying enough I've considered starting my own ISP...) Funny how the exact same symptoms occur. --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet ---- (http://www.freebsd.org) From owner-freebsd-hardware Sun Sep 7 17:55:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA22582 for hardware-outgoing; Sun, 7 Sep 1997 17:55:56 -0700 (PDT) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA22573 for ; Sun, 7 Sep 1997 17:55:51 -0700 (PDT) Received: from [207.3.81.149] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id la267577 for ; Sun, 7 Sep 1997 19:55:44 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 07 Sep 1997 19:25:07 -0000 (GMT) From: Chris Dillon To: freebsd-hardware@freebsd.org Subject: Adding new tape geometries to ft... Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok, just to make sure I'm not barking up the wrong tree before I embark on adding new geometries to the floppy-tape driver, let me show you all what happens when I throw a DC2120XL tape in my Colorado Jumbo 350. I'm doing this now because I have had a better look at the source, and it looks as if it should have detected this as a type of tape it wouldn't be able to handle: /* Look up geometry in the table */ for (i = 1; i < NGEOM; i++) if (ftgtbl[i].g_fmtno == fmt && ftgtbl[i].g_lenno == len) break; if (i == NGEOM) { printf("ft%d: unknown tape geometry\n", ftu); ftg = NULL; return(-1); } ftg = &ftgtbl[i]; if (!ftg->g_trktape) { printf("ft%d: unsupported format %s w/len %s\n", ftu, ftg->g_fmtdesc, ftg->g_lendesc); ftg = NULL; return(-1); } However, rather than an immediate error, it begins to work, UNTIL it reaches the end of the first track.. It then reverses direction, and the tape continues to advance at about 1cm every second (short bursts). Here's exactly what I did (console error output included): tar cf - /usr/ports/distfiles/ | ft "test" (works fine until it hits the end of the first tape track...) ft0: unrecoverable write error on block 3200 (I yank the tape out of the drive now... its been about 5 minutes) ft0: unrecoverable write error on block 3201 ft0: unrecoverable write error on block 3202 ft0: unrecoverable write error on block 3203 ft0: unrecoverable write error on block 3204 (and so on.. each one in succession about every 30 seconds) It now requires a system restart to stop the messages, as ft is unkillable. Of course, the drive works fine in DOS (do backups/restores there all the time). Is this what SHOULD happen when an unknown tape is inserted in the drive, or is it supposed to detect that first-hand and not even begin the operation? If this is a drive firmware problem (could only be the drive itself, since I've gone through three different floppy controllers with the same problem), i may just have to bite the bank account and go buy a SCSI based drive. (though a Conner TR4 SCSI drive is only $90 from CorpSys.. I can't argue with that price, but how good is it?)  --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet ---- (http://www.freebsd.org) From owner-freebsd-hardware Sun Sep 7 21:29:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA03367 for hardware-outgoing; Sun, 7 Sep 1997 21:29:00 -0700 (PDT) Received: from bsd7.cs.sunysb.edu (bsd7.cs.sunysb.edu [130.245.1.197]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA03359 for ; Sun, 7 Sep 1997 21:28:52 -0700 (PDT) Received: (from uucp@localhost) by bsd7.cs.sunysb.edu (8.8.5/8.8.5) with UUCP id AAA25619; Mon, 8 Sep 1997 00:28:09 -0400 (EDT) Received: (from gene@localhost) by starkhome.cs.sunysb.edu (8.8.5/8.8.5) id AAA01759; Mon, 8 Sep 1997 00:23:04 -0400 (EDT) Date: Mon, 8 Sep 1997 00:23:04 -0400 (EDT) From: Gene Stark Message-Id: <199709080423.AAA01759@starkhome.cs.sunysb.edu> To: Chris Dillon Cc: freebsd-hardware@FreeBSD.ORG In-reply-to: Chris Dillon's message of Sun, 07 Sep 1997 19:25:07 -0000 (GMT) Subject: Adding new tape geometries to ft... References: Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > However, rather than an immediate error, it begins to work, UNTIL >it reaches the end of the first track.. It then reverses direction, and >the tape continues to advance at about 1cm every second (short bursts). >Here's exactly what I did (console error output included): > > tar cf - /usr/ports/distfiles/ | ft "test" >(works fine until it hits the end of the first tape track...) > ft0: unrecoverable write error on block 3200 >(I yank the tape out of the drive now... its been about 5 minutes) > ft0: unrecoverable write error on block 3201 > ft0: unrecoverable write error on block 3202 > ft0: unrecoverable write error on block 3203 The ft driver has some serious race condition problems, which for me began to show up when I upgraded from a 486/33 to a P133. I have a Colorado Jumbo 250. In my case, the problems occurred just after starting to write. The driver would use up all its internal write buffers and then deadlock with symptoms such as you describe. As the write error recovery code in the driver is commented out or not enabled, it goes into a loop trying over and over again to write without failing out. I have submitted at least one or two bug reports on this (search the bugs list for "stark"), with some fixes that at least for me mostly worked around the problem enough so that I could use the tape. The driver is complicated, and besides not having the proper documentation on the ft device, I didn't spend enough time on it to fully understand what might be going wrong. There doesn't seem to be anyone in the FreeBSD group who seems very interested in the driver at this point. Although my Jumbo 250 is still installed, I have quit using it because I have been experiencing serious problems with lack of stability of the media (i.e. my tapes all go bad in an avalanche of failures after two years or so). I can't afford to run DOS for the many hours it would take to reformat the tapes, even if it helped, which it usually doesn't. The tapes are way too expensive to keep buying new ones all the time. Basically I no longer trust the tapes, which makes them pretty useless for backup purposes. Also, although the 120MB (native) capacity was OK back when my system had one 340MB and one 540MB drive, it is no longer very useful for dealing with the multi-gigabyte drives I now have. - Gene Stark From owner-freebsd-hardware Mon Sep 8 02:07:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA19600 for hardware-outgoing; Mon, 8 Sep 1997 02:07:53 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA19594 for ; Mon, 8 Sep 1997 02:07:50 -0700 (PDT) Received: from soda (jwm@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with ESMTP id CAA02523; Mon, 8 Sep 1997 02:07:42 -0700 Message-Id: <199709080907.CAA02523@soda.CSUA.Berkeley.EDU> To: hardware@freebsd.org cc: daemons@meeko.eecs.Berkeley.EDU Subject: Open Hardware Reply-to: jwm@CSUA.Berkeley.EDU Date: Mon, 08 Sep 1997 02:02:26 -0700 From: John Milford Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Someone pointed me to this webpage today, and although it is being run and backed by the Linux camp it seems to be something that could be quite important to the FreeBSD effort, basically a certification that the manufacturer is willing to provide documentation on the interface to their hardware free of charge and without NDA or other such restictions. http://www.debian.org/OpenHardware/ --John From owner-freebsd-hardware Mon Sep 8 10:40:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA15008 for hardware-outgoing; Mon, 8 Sep 1997 10:40:41 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA14997 for ; Mon, 8 Sep 1997 10:40:37 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA26945; Mon, 8 Sep 1997 10:35:08 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd026942; Mon Sep 8 17:35:01 1997 Message-ID: <3414372A.33590565@whistle.com> Date: Mon, 08 Sep 1997 10:34:35 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: jwm@CSUA.Berkeley.EDU CC: hardware@FreeBSD.ORG, daemons@meeko.eecs.Berkeley.EDU Subject: Re: Open Hardware References: <199709080907.CAA02523@soda.CSUA.Berkeley.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Milford wrote: > > Someone pointed me to this webpage today, and although it is > being run and backed by the Linux camp it seems to be something that > could be quite important to the FreeBSD effort, basically a > certification that the manufacturer is willing to provide > documentation on the interface to their hardware free of charge and > without NDA or other such restictions. > > http://www.debian.org/OpenHardware/ > > --John definitly something we should support. From owner-freebsd-hardware Mon Sep 8 20:00:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA27184 for hardware-outgoing; Mon, 8 Sep 1997 20:00:21 -0700 (PDT) Received: from bob.tri-lakes.net ([207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA27179 for ; Mon, 8 Sep 1997 20:00:19 -0700 (PDT) Received: from [207.3.81.134] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id la268643 for ; Mon, 8 Sep 1997 22:00:06 -0500 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709080423.AAA01759@starkhome.cs.sunysb.edu> Date: Mon, 08 Sep 1997 21:14:34 -0000 (GMT) From: Chris Dillon To: Gene Stark Subject: RE: Adding new tape geometries to ft... Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 08-Sep-97 Gene Stark wrote: >The ft driver has some serious race condition problems, which for me >began to show up when I upgraded from a 486/33 to a P133. I have a >Colorado Jumbo 250. In my case, the problems occurred just after starting >to write. The driver would use up all its internal write buffers and >then >deadlock with symptoms such as you describe. As the write error recovery >code in the driver is commented out or not enabled, it goes into a loop >trying over and over again to write without failing out. The first time I ever tried it was on my AMD 486DX2-80, which apparently was fast enough to cause the problems as you describe them. I am now ruuning an AMD 5x86-133 overclocked to 150.. Quite a bit faster than the 80 MHz machine I had before this. Hmmm.. Maybe I'll put that turbo-button to some use. ;-) >I have submitted at least one or two bug reports on this (search the bugs >list for "stark"), with some fixes that at least for me mostly worked >around >the problem enough so that I could use the tape. The driver is >complicated, >and besides not having the proper documentation on the ft device, I >didn't >spend enough time on it to fully understand what might be going wrong. >There doesn't seem to be anyone in the FreeBSD group who seems very >interested >in the driver at this point. I'll try and track down your fixes so that I can get the last dying breaths (of obsolescence) out of this drive. I've only got about 20 or so tapes for it, so no humungous loss when I go run and get a new and better drive. >Although my Jumbo 250 is still installed, I have quit using it because >I have been experiencing serious problems with lack of stability of >the media (i.e. my tapes all go bad in an avalanche of failures after >two years or so). I can't afford to run DOS for the many hours it >would take to reformat the tapes, even if it helped, which it usually >doesn't. The tapes are way too expensive to keep buying new ones all >the time. Basically I no longer trust the tapes, which makes them >pretty useless for backup purposes. Also, although the 120MB (native) >capacity was OK back when my system had one 340MB and one 540MB drive, >it is no longer very useful for dealing with the multi-gigabyte drives >I now have. Space on the tapes is definately a consideration now. I've revised my backup strategies now so as to only backup what would take me too long to get back normally, and not the entire system. So far my tapes have stayed flawless (knock on wood), but I did spend the extra few bucks and bought the higher quality tapes (Colorado and 3M tapes, which I think are the same thing anyway). --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best free OS on the planet ---- (http://www.freebsd.org) From owner-freebsd-hardware Mon Sep 8 21:05:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA00398 for hardware-outgoing; Mon, 8 Sep 1997 21:05:39 -0700 (PDT) Received: from unreal.gatekeep.net (root@unreal.gatekeep.net [208.219.170.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA00393 for ; Mon, 8 Sep 1997 21:05:35 -0700 (PDT) Received: from bhicks ([208.219.170.6]) by unreal.gatekeep.net (8.8.5/8.8.5) with SMTP id TAA00294 for ; Mon, 8 Sep 1997 19:05:29 -0500 (CDT) From: "Brandon Hicks" To: Subject: hmmm.... Can This Be done??? Date: Mon, 8 Sep 1997 22:57:54 -0500 Message-ID: <01bcbcd4$8d692c60$06aadbd0@bhicks> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0034_01BCBCAA.A4932460" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1108.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1108.0 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0034_01BCBCAA.A4932460 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable How can I use Two Monitors (each showing something different) with out = installing AccelX??? (Like Just with different Vir. Terminals = (Desktops). And Is it Possible to have 2 mice, and 2 keyboards, one for = each??? If NOT when will computers be able to do this??? ------=_NextPart_000_0034_01BCBCAA.A4932460 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
How can I use Two = Monitors (each=20 showing something different) with out installing AccelX??? (Like Just = with=20 different Vir. Terminals (Desktops).  And Is it Possible to have 2 = mice,=20 and 2 keyboards, one for each??? If NOT when will computers be able to = do=20 this???
------=_NextPart_000_0034_01BCBCAA.A4932460-- From owner-freebsd-hardware Mon Sep 8 23:39:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07944 for hardware-outgoing; Mon, 8 Sep 1997 23:39:08 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA07921 for ; Mon, 8 Sep 1997 23:39:04 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id XAA05255; Mon, 8 Sep 1997 23:38:53 -0700 (PDT) Message-ID: <19970908233853.18847@hydrogen.nike.efn.org> Date: Mon, 8 Sep 1997 23:38:53 -0700 From: John-Mark Gurney To: Brandon Hicks Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: hmmm.... Can This Be done??? References: <01bcbcd4$8d692c60$06aadbd0@bhicks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <01bcbcd4$8d692c60$06aadbd0@bhicks>; from Brandon Hicks on Mon, Sep 08, 1997 at 10:57:54PM -0500 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brandon Hicks scribbled this message on Sep 8: > How can I use Two Monitors (each showing something different) with out installing AccelX??? (Like Just with different Vir. Terminals (Desktops). And Is it Possible to have 2 mice, and 2 keyboards, one for each??? If NOT when will computers be able to do this??? nope.. right now there is no way to do this sort of thing... but I am about to start working on a set of device drivers that will allow this... so it might not be to far off... you can already have the two mice.. just connect 'em up.. the question is how you use them both at the same time.. :) ttyl.. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hardware Tue Sep 9 04:58:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA03780 for hardware-outgoing; Tue, 9 Sep 1997 04:58:10 -0700 (PDT) Received: from arthur.rosario.de (www.rosario.de [194.77.189.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA03772 for ; Tue, 9 Sep 1997 04:58:06 -0700 (PDT) Received: from marvin.rosario.de by arthur.rosario.de (8.8.5/8.7.3) with SMTP id NAA22034 for ; Tue, 9 Sep 1997 13:57:57 +0200 (MET DST) Received: from zaphod.rosario.de by marvin.rosario.de (NX5.67f2/NX3.0M) id AA09624; Tue, 9 Sep 97 14:03:07 +0200 Message-Id: <9709091203.AA09624@marvin.rosario.de> Received: by zaphod.rosario.de (NX5.67e/NX3.0X) id AA05405; Tue, 9 Sep 97 13:58:08 +0200 Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Carl Christian Wulff Date: Tue, 9 Sep 97 13:58:06 +0200 To: freebsd-hardware@freebsd.org Subject: four-port ethernet - adaptec ANA-6944A/TX Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hi, today I tried to boot a FreeBSD machine (RELENG_2_2 of Aug 14, GENERIC kernel) with a adaptec ANA-6944A/TX (former Cogent ?) 4-port ethernet (10/100 Mb) card with four digital 21140-AE (c) Dec 1996 without luck. The kernel reported the following: [...] de0 rev 35 int a irq 11 on pci0:12 de0: 21040 [10Mb/s] pass 2.3 de0: address 00:00:92:90:70:eb de0: enabling BNC/AUI port Probing for devices on PCI bus 1: de1 rev 34 int a irq 9 on pci1:4 de1: 21140A [10-100Mb/s] pass 2.2 de1: address 00:00:92:a7:09:dc de1: enabling 10baseT port de2 rev 34 int a irq 11 on pci1:5 de2: can't read ENET ROM (why=-3) (ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff de2: 21140A [10-100Mb/s] pass 2.2 de2: address unknown de3 rev 34 int a irq 10 on pci1:6 de3: can't read ENET ROM (why=-3) (ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff de3: 21140A [10-100Mb/s] pass 2.2 de3: address unknown de4 rev 34 int a irq 12 on pci1:7 de4: can't read ENET ROM (why=-3) (ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff de4: 21140A [10-100Mb/s] pass 2.2 de4: address unknown Probing for devices on the ISA bus: [...] is it my fault, or do I have to wait for some kernel updates ? thanks, Christian From owner-freebsd-hardware Tue Sep 9 05:28:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA05156 for hardware-outgoing; Tue, 9 Sep 1997 05:28:26 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA05151 for ; Tue, 9 Sep 1997 05:28:24 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id FAA00708; Tue, 9 Sep 1997 05:28:16 -0700 (PDT) To: Carl Christian Wulff cc: freebsd-hardware@FreeBSD.ORG Subject: Re: four-port ethernet - adaptec ANA-6944A/TX In-reply-to: Your message of "Tue, 09 Sep 1997 13:58:06 +0200." <9709091203.AA09624@marvin.rosario.de> Date: Tue, 09 Sep 1997 05:28:16 -0700 Message-ID: <705.873808096@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Can you tell us if you have any better luck with: http://www.3am-software.com/de-970703.tar.gz We're trying to evaluate that driver now for possible inclusion with the next FreeBSD release(s). Jordan From owner-freebsd-hardware Tue Sep 9 05:30:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA05327 for hardware-outgoing; Tue, 9 Sep 1997 05:30:39 -0700 (PDT) Received: from godzilla.lazerlink.com (godzilla.lazerlink.com [206.98.28.230]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA05321 for ; Tue, 9 Sep 1997 05:30:36 -0700 (PDT) Received: from godzilla.lazerlink.com (dave@godzilla.lazerlink.com [206.98.28.230]) by godzilla.lazerlink.com (8.8.5/8.7.3) with SMTP id MAA06584 for ; Tue, 9 Sep 1997 12:31:20 GMT Date: Tue, 9 Sep 1997 08:31:20 -0400 (EDT) From: "David W. Stevens" To: freebsd-hardware@freebsd.org Subject: Supermicro P6DLH with i960 IO chip? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone know if FreeBSD takes advantage of this i960 IO chip on the Supermicro board? I'm interested in purchasing one. Thanks, Dave David W. Stevens Director of Internet Operations Lazerpro Video Productions, Inc Lazerlink dave@lazerlink.com From owner-freebsd-hardware Tue Sep 9 10:26:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA21823 for hardware-outgoing; Tue, 9 Sep 1997 10:26:47 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA21809 for ; Tue, 9 Sep 1997 10:26:42 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id KAA02502; Tue, 9 Sep 1997 10:23:11 -0700 (PDT) Date: Tue, 9 Sep 1997 10:23:11 -0700 (PDT) From: Jim Shankland Message-Id: <199709091723.KAA02502@biggusdiskus.flyingfox.com> To: jkh@time.cdrom.com Subject: Re: four-port ethernet - adaptec ANA-6944A/TX Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan writes: > http://www.3am-software.com/de-970703.tar.gz > > We're trying to evaluate that driver now for possible inclusion > with the next FreeBSD release(s). Note that that version of the driver has a fairly serious bug in FreeBSD: it mallocs the tulip_softc structure, which has grown to > 4 KB in size. At the end of the tulip_softc structure are arrays of receive and transmit descriptors that must be physically contiguous. Since the structure spans a page boundary, they may not turn out to be contiguous. Matt's suggested solution was to reduce TULIP_TXDESCS (the number of transmit descriptors) from 128 to 32; this shrinks the tulip_softc structure back under 4 KB. Alternatively, the receive and transmit descriptor arrays can be allocated separately, rather then embedded in the tulip_softc structure. As long as the tulip_softc structure happens to be mapped to physically contiguous memory, everything works. But completely unrelated kernel changes can cause this to break; symptoms are that the driver wedges after transmitting about 100 packets. Jim Shankland From owner-freebsd-hardware Tue Sep 9 19:56:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA28972 for hardware-outgoing; Tue, 9 Sep 1997 19:56:13 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA28967 for ; Tue, 9 Sep 1997 19:56:03 -0700 (PDT) Received: from word.smith.net.au (lot.atrad.adelaide.edu.au [203.20.121.21]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id MAA03392 for ; Wed, 10 Sep 1997 12:25:57 +0930 (CST) Received: from word.smith.net.au (localhost.atrad.adelaide.edu.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id MAA00805; Wed, 10 Sep 1997 12:22:25 +1000 (EST) Message-Id: <199709100222.MAA00805@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "David W. Stevens" cc: freebsd-hardware@freebsd.org Subject: Re: Supermicro P6DLH with i960 IO chip? In-reply-to: Your message of "Tue, 09 Sep 1997 08:31:20 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Sep 1997 12:22:25 +1000 From: Mike Smith Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Anyone know if FreeBSD takes advantage of this i960 IO chip on the > Supermicro board? I'm interested in purchasing one. No. This is an I2O board, and despite the recent leak of the I2O document, there is no substantial support for I2O in any of the free operating systems at this time. mike From owner-freebsd-hardware Tue Sep 9 20:48:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02347 for hardware-outgoing; Tue, 9 Sep 1997 20:48:08 -0700 (PDT) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [141.39.224.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02340 for ; Tue, 9 Sep 1997 20:48:03 -0700 (PDT) Received: from robkaos.ruhr.de (admin@localhost) by mail.ruhrgebiet.individual.net (8.8.5-r-beta/8.8.5) with UUCP id XAA12600 for freebsd.org!hardware; Tue, 9 Sep 1997 23:33:12 +0200 (MET DST) Received: by robkaos.ruhr.de (Smail-3.2 1996-Jul-4 #1) id ; Tue, 9 Sep 1997 23:31:50 +0200 (MET DST) Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: 'make world' on P6 system takes 3 h To: hardware@freebsd.org Date: Tue, 9 Sep 1997 23:31:50 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have the impression that there is something wrong with my P6 system. 'make world' (3.0-current) takes 3 hours! The hardware is: Asus P6NP5 motherboard with 64 MB EDO, 200 MHz PentiumPro (256k). Asus SC-200 SCSI host adapter 4 GB IBM DCAS hard disk (this is where /usr/src and /usr obj reside). There is no other activity when the 'world is made'. No X server is running. Here are the essential options from /etc/make.conf: CFLAGS= -O2 -m486 -pipe NOPROFILE= true HAVE_FPU= yes Swap space is 70 MB, the root (and boot) drive is an IDE drive (850 MB Conner). I think the usual time for 'make world' is 1 hour an 30 minutes. So, where does my system spend its time? TIA Robert From owner-freebsd-hardware Tue Sep 9 22:03:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA05796 for hardware-outgoing; Tue, 9 Sep 1997 22:03:48 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA05790 for ; Tue, 9 Sep 1997 22:03:44 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA02544; Tue, 9 Sep 1997 22:06:25 -0700 (PDT) Message-Id: <199709100506.WAA02544@implode.root.com> To: robsch@robkaos.ruhr.de (Robert Schien) cc: hardware@FreeBSD.ORG Subject: Re: 'make world' on P6 system takes 3 h In-reply-to: Your message of "Tue, 09 Sep 1997 23:31:50 +0200." From: David Greenman Reply-To: dg@root.com Date: Tue, 09 Sep 1997 22:06:25 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Here are the essential options from /etc/make.conf: > > >CFLAGS= -O2 -m486 -pipe Make that "-O" and kill the -m486. The -O2 nearly doubles the compile time and provides almost no measurable improvement in most cases. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Wed Sep 10 05:12:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA26665 for hardware-outgoing; Wed, 10 Sep 1997 05:12:58 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA26660 for ; Wed, 10 Sep 1997 05:12:53 -0700 (PDT) Received: from nospam.hiwaay.net (max4-123.HiWAAY.net [208.147.145.123]) by fly.HiWAAY.net (8.8.6/8.8.6) with ESMTP id HAA26416; Wed, 10 Sep 1997 07:12:44 -0500 (CDT) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.7/8.8.4) with ESMTP id HAA05906; Wed, 10 Sep 1997 07:12:42 -0500 (CDT) Message-Id: <199709101212.HAA05906@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: robsch@robkaos.ruhr.de (Robert Schien) cc: hardware@FreeBSD.ORG From: dkelly@hiwaay.net Subject: Re: 'make world' on P6 system takes 3 h In-reply-to: Message from robsch@robkaos.ruhr.de (Robert Schien) of "Tue, 09 Sep 1997 23:31:50 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Sep 1997 07:12:41 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Robert Schien writes: > > I have the impression that there is something wrong with my > P6 system. 'make world' (3.0-current) takes 3 hours! > > The hardware is: > Asus P6NP5 motherboard with 64 MB EDO, 200 MHz PentiumPro (256k). > Asus SC-200 SCSI host adapter > 4 GB IBM DCAS hard disk (this is where /usr/src and /usr obj reside). I have a PPro 166 with 512k cache, 32M FP RAM, 2G Barracuda, 2940. "make world" for 2.2.2 (recent cvsup) takes 2:47. Mounting /usr with "-o async" drops that time to 2:15. It was interesting to note "time" reported almost exactly the same amount of time in CPU for both. dg@root.com said: > >CFLAGS= -O2 -m486 -pipe > Make that "-O" and kill the -m486. The -O2 nearly doubles the > compile time and provides almost no measurable improvement in most > cases. Was -O the default at some time during 2.x's life? I remember my old MB could "make world" in 5 hours or so once, and was up to 9 hours by the time I replaced it. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-hardware Wed Sep 10 05:30:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA27601 for hardware-outgoing; Wed, 10 Sep 1997 05:30:34 -0700 (PDT) Received: from gw.rinet.ru (gw.rinet.ru [195.54.192.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA27587 for ; Wed, 10 Sep 1997 05:30:27 -0700 (PDT) Received: by gw.rinet.ru id QAA06386; (8.6.11/vak/1.9) Wed, 10 Sep 1997 16:27:40 +0400 From: marck@gw.rinet.ru (Dmitry Morozovsky) Message-Id: <199709101227.QAA06386@gw.rinet.ru> Subject: IBM/Cyrix PR200+ To: freebsd-hardware@freebsd.org Date: Wed, 10 Sep 1997 16:27:40 +0400 (MSD) X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi there, Yesterday i've set up 2.2.2-R on IBM (Cyrix) PR200+ and was very surprized when it were recognized as 486DX (rather quick, though -- kernel compile in less than 3.5 mins on IDE :) So, my question: is there any "red points" in guidelines for setting up FreeBSD on such system? (MB is ASUS T2P4, PIO4 IDE disk) Please CC answer to my email. Thanx for cooperation. Happy FreeBSDing :))) D.Marck ======================================================================== === D.Marck --- Dmitry Morozovsky --- marck@rinet.ru --- Wild Woozle === ======================================================================== From owner-freebsd-hardware Wed Sep 10 05:34:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA27849 for hardware-outgoing; Wed, 10 Sep 1997 05:34:36 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA27844 for ; Wed, 10 Sep 1997 05:34:34 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id FAA06597; Wed, 10 Sep 1997 05:37:09 -0700 (PDT) Message-Id: <199709101237.FAA06597@implode.root.com> To: dkelly@hiwaay.net cc: robsch@robkaos.ruhr.de (Robert Schien), hardware@FreeBSD.ORG Subject: Re: 'make world' on P6 system takes 3 h In-reply-to: Your message of "Wed, 10 Sep 1997 07:12:41 CDT." <199709101212.HAA05906@nospam.hiwaay.net> From: David Greenman Reply-To: dg@root.com Date: Wed, 10 Sep 1997 05:37:09 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Robert Schien writes: >> >> I have the impression that there is something wrong with my >> P6 system. 'make world' (3.0-current) takes 3 hours! >> >> The hardware is: >> Asus P6NP5 motherboard with 64 MB EDO, 200 MHz PentiumPro (256k). >> Asus SC-200 SCSI host adapter >> 4 GB IBM DCAS hard disk (this is where /usr/src and /usr obj reside). > >I have a PPro 166 with 512k cache, 32M FP RAM, 2G Barracuda, 2940. "make >world" for 2.2.2 (recent cvsup) takes 2:47. Mounting /usr with "-o async" >drops that time to 2:15. It was interesting to note "time" reported >almost exactly the same amount of time in CPU for both. > >dg@root.com said: >> >CFLAGS= -O2 -m486 -pipe >> Make that "-O" and kill the -m486. The -O2 nearly doubles the >> compile time and provides almost no measurable improvement in most >> cases. > >Was -O the default at some time during 2.x's life? I remember my old MB >could "make world" in 5 hours or so once, and was up to 9 hours by the >time I replaced it. -O is still the default. The commented out CFLAGS in make.conf should probably be changed to more closely match the default - the main reason it there is to remind people about the -pipe option (which, with memory prices the way they are, should probably be made the default). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Wed Sep 10 05:46:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA28550 for hardware-outgoing; Wed, 10 Sep 1997 05:46:49 -0700 (PDT) Received: from tyree.iii.co.uk (tyree.iii.co.uk [193.117.77.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA28542 for ; Wed, 10 Sep 1997 05:46:45 -0700 (PDT) Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.4/8.8.4) with ESMTP id NAA12886; Wed, 10 Sep 1997 13:43:47 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id NAA01757; Wed, 10 Sep 1997 13:49:17 +0100 (BST) Message-ID: <19970910134915.23493@strand.iii.co.uk> Date: Wed, 10 Sep 1997 13:49:15 +0100 From: nik@iii.co.uk To: dg@root.com Cc: Robert Schien , hardware@FreeBSD.ORG Subject: Re: 'make world' on P6 system takes 3 h References: <199709100506.WAA02544@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76e In-Reply-To: <199709100506.WAA02544@implode.root.com>; from David Greenman on Tue, Sep 09, 1997 at 10:06:25PM -0700 Organization: interactive investor Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Sep 09, 1997 at 10:06:25PM -0700, David Greenman wrote: [Robert Schien wrote] > >Here are the essential options from /etc/make.conf: > > > > > >CFLAGS= -O2 -m486 -pipe > > Make that "-O" and kill the -m486. The -O2 nearly doubles the compile time > and provides almost no measurable improvement in most cases. Could someone update the entry in /etc/make.conf? I've just looked at it on a -current system (admittedly, on the UK server, so it may not be bang up to date, it's version 1.49) and it has two entries that look appropriate: [...] # One, and probably the most common, use could be: # #CFLAGS= -O2 -m486 -pipe [...] # To compile the kernel with special optimisations, you can use this: # #COPTFLAGS= -O -pipe As you can see, COPTFLAGS is as you suggest, CFLAGS is exactly as Robert quoted. N -- --+==[ Nik Clayton is Just Another Perl Hacker at Interactive Investor ]==+-- Diana, the roadkill formally known as Princess, 1961-1997 NC5-RIPE From owner-freebsd-hardware Wed Sep 10 06:36:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA02052 for hardware-outgoing; Wed, 10 Sep 1997 06:36:26 -0700 (PDT) Received: from myname.my.domain (oppringt-28.uib.no [129.177.138.47]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA02046 for ; Wed, 10 Sep 1997 06:36:18 -0700 (PDT) Received: (from secrj@localhost) by myname.my.domain (8.8.5/8.8.5) id PAA11562; Wed, 10 Sep 1997 15:38:08 +0200 (CEST) Message-ID: <19970910153802.17922@econ.uib.no> Date: Wed, 10 Sep 1997 15:38:02 +0200 From: Ronny Jordalen To: Dmitry Morozovsky Cc: freebsd-hardware@freebsd.org Subject: Re: IBM/Cyrix PR200+ References: <199709101227.QAA06386@gw.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79e In-Reply-To: <199709101227.QAA06386@gw.rinet.ru>; from Dmitry Morozovsky on Wed, Sep 10, 1997 at 04:27:40PM +0400 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, Sep 10, 1997 at 04:27:40PM +0400, Dmitry Morozovsky wrote: > Hi there, > > Yesterday i've set up 2.2.2-R on IBM (Cyrix) PR200+ and was very surprized > when it were recognized as 486DX (rather quick, though -- kernel compile in > less than 3.5 mins on IDE :) > That's strange... I myself just installed FreeBSD on a machine running the same CPU, and FreeBSD identified it as Pentium Pro class processor. I first tried setting Cpu to 486-type too, as Windows does infact recognize it as a 486. But then kernel would panic. > So, my question: is there any "red points" in guidelines for setting up > FreeBSD on such system? (MB is ASUS T2P4, PIO4 IDE disk) > Don't really know. My installation went flawlessly, apart from the above mentioned problem. I have the 2,5x66 version of the CPU btw, running off an Asus TX97-E MB. And running 2.2.2 as well. > Please CC answer to my email. Thanx for cooperation. > > Happy FreeBSDing :))) Aren't we always? :-) > D.Marck > ======================================================================== > === D.Marck --- Dmitry Morozovsky --- marck@rinet.ru --- Wild Woozle === > ======================================================================== > -- --Ronny From owner-freebsd-hardware Wed Sep 10 10:29:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14878 for hardware-outgoing; Wed, 10 Sep 1997 10:29:28 -0700 (PDT) Received: from gw.rinet.ru (gw.rinet.ru [195.54.192.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA14869 for ; Wed, 10 Sep 1997 10:29:17 -0700 (PDT) Received: by gw.rinet.ru id VAA15030; (8.6.11/vak/1.9) Wed, 10 Sep 1997 21:26:54 +0400 Date: Wed, 10 Sep 1997 21:26:54 +0400 From: marck@gw.rinet.ru (Dmitry Morozovsky) Message-Id: <199709101726.VAA15030@gw.rinet.ru> To: secrj@econ.uib.no (Ronny Jordalen) CC: freebsd-hardware@freebsd.org Subject: Re: IBM/Cyrix PR200+ Newsgroups: freebsd.hardware X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article you wrote: > > Yesterday i've set up 2.2.2-R on IBM (Cyrix) PR200+ and was very surprized > > when it were recognized as 486DX (rather quick, though -- kernel compile in > > less than 3.5 mins on IDE :) > > > That's strange... I myself just installed FreeBSD on a machine running the > same CPU, and FreeBSD identified it as Pentium Pro class processor. I first > tried setting Cpu to 486-type too, as Windows does infact recognize it as > a 486. But then kernel would panic. Strange for me too -- but that's it, 486DX with clock rate over 1GHz :) > > So, my question: is there any "red points" in guidelines for setting up > > FreeBSD on such system? (MB is ASUS T2P4, PIO4 IDE disk) > Don't really know. My installation went flawlessly, apart from the above > mentioned problem. I have the 2,5x66 version of the CPU btw, running off > an Asus TX97-E MB. And running 2.2.2 as well. My too -- however, i suppose that Pentium-oriented copy/zero block procedures don't work. > > Happy FreeBSDing :))) > Aren't we always? :-) I feel high hopes to that ;-) -- Sincerely, D.Marck ======================================================================== === D.Marck --- Dmitry Morozovsky --- marck@rinet.ru --- Wild Woozle === ======================================================================== From owner-freebsd-hardware Wed Sep 10 11:18:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA17501 for hardware-outgoing; Wed, 10 Sep 1997 11:18:53 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA17491 for ; Wed, 10 Sep 1997 11:18:50 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id LAA04362; Wed, 10 Sep 1997 11:18:13 -0700 (PDT) Date: Wed, 10 Sep 1997 11:18:12 -0700 (PDT) From: Howard Lew To: Ronny Jordalen cc: Dmitry Morozovsky , freebsd-hardware@FreeBSD.ORG Subject: Re: IBM/Cyrix PR200+ In-Reply-To: <19970910153802.17922@econ.uib.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 10 Sep 1997, Ronny Jordalen wrote: > On Wed, Sep 10, 1997 at 04:27:40PM +0400, Dmitry Morozovsky wrote: > > Hi there, > > > > Yesterday i've set up 2.2.2-R on IBM (Cyrix) PR200+ and was very surprized > > when it were recognized as 486DX (rather quick, though -- kernel compile in > > less than 3.5 mins on IDE :) > > > That's strange... I myself just installed FreeBSD on a machine running the > same CPU, and FreeBSD identified it as Pentium Pro class processor. I first > tried setting Cpu to 486-type too, as Windows does infact recognize it as > a 486. But then kernel would panic. > I think the cpu types are now different for anything above 2.2.2R (correct me if I am wrong though)... This only is important if you recompile the kernel. 2.2.2R Cyrix 6x86/L - 486 Cyrix 6x86MX - 586 AMD K5 - 586 AMD K6 - 586 2.2.2 SNAP (i.e. 8/31/97 or newer) Cyrix 6x86/L - 686 (as reported) Cyrix 6x86MX - 686 AMD K5 - 586 (?) AMD K6 - 686 (?) ? = I did not test it. > > So, my question: is there any "red points" in guidelines for setting up > > FreeBSD on such system? (MB is ASUS T2P4, PIO4 IDE disk) > > > Don't really know. My installation went flawlessly, apart from the above > mentioned problem. I have the 2,5x66 version of the CPU btw, running off > an Asus TX97-E MB. And running 2.2.2 as well. > > > Please CC answer to my email. Thanx for cooperation. > > > > Happy FreeBSDing :))) > > Aren't we always? :-) > > > D.Marck > > ======================================================================== > > === D.Marck --- Dmitry Morozovsky --- marck@rinet.ru --- Wild Woozle === > > ======================================================================== > > > > -- > > --Ronny > --------------------------------------------------------------------------- Shoppers Network (Support) AMD K5/K6s, Cyrix 6x86, Intel Pentiums/Pro Phone: (415) 759-8584 Email: howard@shoppersnet.com ==============================> WWW - http://www.shoppersnet.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-freebsd-hardware Wed Sep 10 13:11:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA23987 for hardware-outgoing; Wed, 10 Sep 1997 13:11:31 -0700 (PDT) Received: from MindBender.serv.net (mindbender.serv.net [205.153.153.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA23809 for ; Wed, 10 Sep 1997 13:08:15 -0700 (PDT) Received: from localhost.HeadCandy.com (localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.8.6/8.7.3) with SMTP id NAA12617; Wed, 10 Sep 1997 13:06:23 -0700 (PDT) Message-Id: <199709102006.NAA12617@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Howard Lew cc: Ronny Jordalen , Dmitry Morozovsky , freebsd-hardware@freebsd.org Subject: Re: IBM/Cyrix PR200+ In-reply-to: Your message of Wed, 10 Sep 97 11:18:12 -0700. Date: Wed, 10 Sep 1997 13:06:22 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I think the cpu types are now different for anything above 2.2.2R >(correct me if I am wrong though)... This only is important if you >recompile the kernel. > >2.2.2R >Cyrix 6x86/L - 486 >Cyrix 6x86MX - 586 >AMD K5 - 586 >AMD K6 - 586 > >2.2.2 SNAP (i.e. 8/31/97 or newer) >Cyrix 6x86/L - 686 (as reported) ^^^ This is wrong -- the 6x86/L (i.e. M1) is a Pentium-class (586) processor. The 6x86MX (i.e. M2) is a 686-class chip. >Cyrix 6x86MX - 686 >AMD K5 - 586 (?) >AMD K6 - 686 (?) [...] ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net Contract software development for Windows NT, Windows 95 and Unix. Windows NT and Unix server development in C++ and C. --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hardware Wed Sep 10 19:00:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA15009 for hardware-outgoing; Wed, 10 Sep 1997 19:00:17 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA14998 for ; Wed, 10 Sep 1997 19:00:10 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id SAA21218; Wed, 10 Sep 1997 18:58:24 -0700 (PDT) Date: Wed, 10 Sep 1997 18:58:22 -0700 (PDT) From: Howard Lew To: "Michael L. VanLoon -- HeadCandy.com" cc: Ronny Jordalen , Dmitry Morozovsky , freebsd-hardware@FreeBSD.ORG Subject: Re: IBM/Cyrix PR200+ In-Reply-To: <199709102006.NAA12617@MindBender.serv.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 10 Sep 1997, Michael L. VanLoon -- HeadCandy.com wrote: > > >I think the cpu types are now different for anything above 2.2.2R > >(correct me if I am wrong though)... This only is important if you > >recompile the kernel. > > > >2.2.2R > >Cyrix 6x86/L - 486 > >Cyrix 6x86MX - 586 > >AMD K5 - 586 > >AMD K6 - 586 > > > >2.2.2 SNAP (i.e. 8/31/97 or newer) > >Cyrix 6x86/L - 686 (as reported) > ^^^ > > This is wrong -- the 6x86/L (i.e. M1) is a Pentium-class (586) > processor. The 6x86MX (i.e. M2) is a 686-class chip. Michael, you are correct. However, I think the newer 2.2.2 snapshots (post 2.2.2R) are using the 686 compile settings for the M1 as someone reported... I haven't tested this myself, but someone earlier in this message thread I think said it was probed as a 686 class cpu and setting it to 486 cpu settings would cause a panic. (I agree that the 6x86/L should be properly labeled as a 586 class cpu despite its name). It comes down to whether choosing the cpu type depends on x86 instruction set compatibility, cpu speed class, or cpu name. I believe it used to be based primarily on instruction set (i.e. 6x86/L was 486); now it seems the compile settings are based on cpu speed. > > >Cyrix 6x86MX - 686 > >AMD K5 - 586 (?) > >AMD K6 - 686 (?) > [...] > > ----------------------------------------------------------------------------- > Michael L. VanLoon michaelv@MindBender.serv.net > Contract software development for Windows NT, Windows 95 and Unix. > Windows NT and Unix server development in C++ and C. > > --< 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... > ----------------------------------------------------------------------------- > --------------------------------------------------------------------------- Shoppers Network (Support) AMD K5/K6s, Cyrix 6x86, Intel Pentiums/Pro Phone: (415) 759-8584 Email: howard@shoppersnet.com ==============================> WWW - http://www.shoppersnet.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-freebsd-hardware Thu Sep 11 14:33:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA21814 for hardware-outgoing; Thu, 11 Sep 1997 14:33:01 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA21783 for ; Thu, 11 Sep 1997 14:32:50 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id XAA21502 for ; Thu, 11 Sep 1997 23:32:23 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id XAA06795 for freebsd-hardware@FreeBSD.ORG; Thu, 11 Sep 1997 23:32:09 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-uucp-2.10/nospam) id WAA09779; Thu, 11 Sep 1997 22:16:42 +0200 (CEST) Message-ID: <19970911221642.45617@keltia.freenix.fr> Date: Thu, 11 Sep 1997 22:16:42 +0200 From: Ollivier Robert To: freebsd-hardware@FreeBSD.ORG Subject: Re: IBM/Cyrix PR200+ References: <199709101726.VAA15030@gw.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199709101726.VAA15030@gw.rinet.ru>; from Dmitry Morozovsky on Wed, Sep 10, 1997 at 09:26:54PM +0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3634 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Dmitry Morozovsky: > My too -- however, i suppose that Pentium-oriented copy/zero block > procedures don't work. Oh they do but much slower then the regular ones. Always use "flags 0x7" for npx0 in your config. file for both Cyrix and AMD's processors. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Sat Sep 6 21:58:17 CEST 1997 From owner-freebsd-hardware Thu Sep 11 15:35:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA27277 for hardware-outgoing; Thu, 11 Sep 1997 15:35:56 -0700 (PDT) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA27271 for ; Thu, 11 Sep 1997 15:35:52 -0700 (PDT) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id QAA27663; Thu, 11 Sep 1997 16:35:13 -0600 (MDT) Date: Thu, 11 Sep 1997 16:35:13 -0600 (MDT) From: Doug Russell To: Ollivier Robert cc: freebsd-hardware@FreeBSD.ORG Subject: Re: IBM/Cyrix PR200+ In-Reply-To: <19970911221642.45617@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 11 Sep 1997, Ollivier Robert wrote: > Always use "flags 0x7" for npx0 in your config. file for both Cyrix and > AMD's processors. Is there a good, complete, list of processor options, flags that should be set, speedup code, etc. for the various processors anywhere? I always see little bits here and there, but I don't ever remember running into a proper list when I have been searching for specific stuff in the archives, etc. If one doesn't exist, perhaps I will begin compiling one. Later...... From owner-freebsd-hardware Thu Sep 11 20:22:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA24906 for hardware-outgoing; Thu, 11 Sep 1997 20:22:04 -0700 (PDT) Received: from iago.ienet.com (iago.ienet.com [207.78.32.53]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA24900 for ; Thu, 11 Sep 1997 20:22:00 -0700 (PDT) Received: from iago.ienet.com (localhost.ienet.com [127.0.0.1]) by iago.ienet.com (8.8.5/8.8.5) with ESMTP id UAA25833 Thu, 11 Sep 1997 20:21:33 -0700 (PDT) Message-Id: <199709120321.UAA25833@iago.ienet.com> From: Pius Fischer To: Doug Russell Cc: freebsd-hardware@FreeBSD.ORG, terryl@ienet.com, robert@ienet.com Subject: Re: wdunwedge failed Date: Thu, 11 Sep 1997 20:21:33 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sorry, for the very late reply ... On Thu, 21 Aug 1997, drussell@saturn-tech.com wrote: >On Thu, 21 Aug 1997, Mike Smith wrote: > >>> It flickers. For example, a screen full of these "wdunwedge failed" error >>> messages appears for a second or two and then the screen completely blanks >>> out for a second. Then the error messages are visible again briefly, then >>> the screen goes blank, and so no. Sort of like someone quickly turning the >>> monitor on and off. >> >> It's possibly (as Brett suggested) that some delays in the wd code are >> magically synchronising with something in the display driver, but I'd > ... > > I'd guess either the error messages are just scrolling fast, and end up > flickering, or, especially by the way he describes it, that the video > signal is actually interrupted. > > It may not be the problem, but I would take a multimeter and check out the > +12 volt supply while the machine is in this failed state. The hard drive > most likely uses the 12 volt for spindle motor, etc., and most VGA cards > use the +12 and -12 supplies for the RAMDAC. If the 12 volt line is > really funky (might need a scope to see if it is fluctuating, poorly > filtered due to a dead filter capacitor or something, etc.), the power > supply is the suspect. > > Method B, of course, is to swap in a known good supply, and see if the > problem happens again. :) > > You'd be surprised how many strange problems are caused by a flakey power > supply. Don't ever buy one of those cheapo $30 mini-tower (or whatever) > case deals. The power supply in a $30 case probably isn't too wonderful. > Getting better built cases is an added bonus, too. :) Yes, the power supply was indeed the problem! The voltmeter reading across the bad machine's power supply was a very unsteady 13 - 13.5 volts (if I remember correctly). On a good machine standing next to it, the voltmeter gave a rock solid 12.3 volt reading. We then got a slightly fancier chassis with a new power supply and we haven't seen this wdunwedge/flickering monitor problem again. Another theory suggested that the error messages were scrolling by so quickly that they caused the monitor to flicker. But, in fact, they were coming in relatively slowly, about 1 bright 3-line message every 10-15 seconds (at one point we had the monitor plugged-in when the messages started coming). Also, it seemed unlikely that it was a problem with the monitor itself because the monitor was mostly plugged into another very similar machine, and never exhibited any problems except when plugged into the bad machine when that bad machine was dying. And the flickering already began before the entire screen was filled with bright text. In fact, as soon as the first wdunwedge message came, the flickering began (with most of the monitor still showing dim text). Anyways, thanks very much for all your help and suggestions. Pius From owner-freebsd-hardware Thu Sep 11 21:32:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA00348 for hardware-outgoing; Thu, 11 Sep 1997 21:32:15 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca11-23.ix.netcom.com [199.35.209.183]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA00343 for ; Thu, 11 Sep 1997 21:32:11 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id VAA28321; Thu, 11 Sep 1997 21:31:50 -0700 (PDT) Date: Thu, 11 Sep 1997 21:31:50 -0700 (PDT) Message-Id: <199709120431.VAA28321@silvia.HIP.Berkeley.EDU> To: roberto@keltia.freenix.fr CC: freebsd-hardware@FreeBSD.ORG In-reply-to: <19970911221642.45617@keltia.freenix.fr> (message from Ollivier Robert on Thu, 11 Sep 1997 22:16:42 +0200) Subject: Re: IBM/Cyrix PR200+ From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * > My too -- however, i suppose that Pentium-oriented copy/zero block * > procedures don't work. * * Oh they do but much slower then the regular ones. * * Always use "flags 0x7" for npx0 in your config. file for both Cyrix and * AMD's processors. Speaking of which, can anyone with an *MX processor check the gus mmx extension PR (filed under "gnu", I think) and try and see if copying through the mmx registers instead of FP would be faster for some of the CPU's? Satoshi From owner-freebsd-hardware Thu Sep 11 23:05:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07384 for hardware-outgoing; Thu, 11 Sep 1997 23:05:20 -0700 (PDT) Received: from nemesis.idirect.com (root@nemesis.idirect.com [207.136.80.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA07362; Thu, 11 Sep 1997 23:05:15 -0700 (PDT) Received: from thor.idirect.com (jlixfeld@thor.idirect.com [207.136.80.105]) by nemesis.idirect.com (8.8.5/8.8.4) with SMTP id CAA17243; Fri, 12 Sep 1997 02:05:11 -0400 (EDT) Received: from localhost (jlixfeld@localhost) by thor.idirect.com (8.6.12/8.6.12) with SMTP id CAA04455; Fri, 12 Sep 1997 02:05:10 -0400 X-Authentication-Warning: thor.idirect.com: jlixfeld owned process doing -bs Date: Fri, 12 Sep 1997 02:05:10 -0400 (EDT) From: Jason Lixfeld To: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: PCI DLink DFE500-TX 10/100MB DEC Tulip 21140AE REV2-C Chipset Ethernet Card Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is their support for this card? It did not have the drivers for it when I attempted to use this card when doing an FTP install. I used a 3Com 3C509B 10MB ISA. BSD/OS and Linux both had problems or driver incompatibilities when 21140AC REV1-B updated to 21140AE REV2-C. I'm wondering if FreeBSD 2.2.2 has the same incompatibility, and is their a driver that will support the new chipset, and where do I find it to compile it into a new kernel?! Thanks in Advance, Jason Lixfeld From owner-freebsd-hardware Fri Sep 12 00:12:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA11857 for hardware-outgoing; Fri, 12 Sep 1997 00:12:49 -0700 (PDT) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA11851 for ; Fri, 12 Sep 1997 00:12:44 -0700 (PDT) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id BAA08083; Fri, 12 Sep 1997 01:12:31 -0600 (MDT) Date: Fri, 12 Sep 1997 01:12:31 -0600 (MDT) From: Doug Russell To: Pius Fischer cc: freebsd-hardware@FreeBSD.ORG, terryl@ienet.com, robert@ienet.com Subject: Re: wdunwedge failed In-Reply-To: <199709120321.UAA25833@iago.ienet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 11 Sep 1997, Pius Fischer wrote: > Sorry, for the very late reply ... Hehe.... Happens to the best of us. :) > On Thu, 21 Aug 1997, drussell@saturn-tech.com wrote: > >On Thu, 21 Aug 1997, Mike Smith wrote: > > It may not be the problem, but I would take a multimeter and check out the > > +12 volt supply while the machine is in this failed state. The hard drive > > most likely uses the 12 volt for spindle motor, etc., and most VGA cards > > use the +12 and -12 supplies for the RAMDAC. If the 12 volt line is > > really funky (might need a scope to see if it is fluctuating, poorly > > filtered due to a dead filter capacitor or something, etc.), the power > > supply is the suspect. > > > > Method B, of course, is to swap in a known good supply, and see if the > > problem happens again. :) > > > > You'd be surprised how many strange problems are caused by a flakey power > > supply. Don't ever buy one of those cheapo $30 mini-tower (or whatever) > > case deals. The power supply in a $30 case probably isn't too wonderful. > > Getting better built cases is an added bonus, too. :) > > Yes, the power supply was indeed the problem! The voltmeter reading > across the bad machine's power supply was a very unsteady 13 - 13.5 > volts (if I remember correctly). On a good machine standing next to > it, the voltmeter gave a rock solid 12.3 volt reading. We then got a > slightly fancier chassis with a new power supply and we haven't seen > this wdunwedge/flickering monitor problem again. People probably don't suspect the P/S as often as they should. Testing it out or swapping in another one for strange crashing problems, etc. is often a good idea. There is no substitute for good hardware, folks, and that includes things like like the power supply. Later...... From owner-freebsd-hardware Fri Sep 12 06:09:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA01729 for hardware-outgoing; Fri, 12 Sep 1997 06:09:22 -0700 (PDT) Received: from stevenson.cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA01723 for ; Fri, 12 Sep 1997 06:09:14 -0700 (PDT) Received: (from richard@localhost) by stevenson.cogsci.ed.ac.uk (8.8.5/8.8.5) id OAA23133 for freebsd-hardware@freebsd.org; Fri, 12 Sep 1997 14:09:11 +0100 (BST) Date: Fri, 12 Sep 1997 14:09:11 +0100 (BST) From: Richard Tobin Message-Id: <199709121309.OAA23133@stevenson.cogsci.ed.ac.uk> To: freebsd-hardware@freebsd.org Subject: CD recorder recommendations? Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [I originally sent this to multimedia, but was advised to try hardware instead.] Can anyone [dis]recommend a CD-R drive for FreeBSD? The HP 6020 is reasonably priced, but my recent experiences with other HP hardware are discouraging. -- Richard From owner-freebsd-hardware Fri Sep 12 07:53:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA08298 for hardware-outgoing; Fri, 12 Sep 1997 07:53:46 -0700 (PDT) Received: from www.xinetron.com (www.xinetron.com [206.86.215.68]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA08271; Fri, 12 Sep 1997 07:53:40 -0700 (PDT) Received: from pop.xinetron.com (pop.xinetron.com [206.86.215.82]) by www.xinetron.com (8.7.5/8.7.3) with ESMTP id HAA00851; Fri, 12 Sep 1997 07:53:03 -0700 (PDT) Received: from jason.xinetron.com (jason.xinetron.com [206.86.215.94]) by pop.xinetron.com (8.7.5/8.7.3) with ESMTP id HAA01666; Fri, 12 Sep 1997 07:53:03 -0700 (PDT) Message-ID: <34195761.2FEBB195@xinetron.com> Date: Fri, 12 Sep 1997 07:53:21 -0700 From: Jason Liao Organization: Xinetron, Inc. X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Failed to install on WD WDC33100H HDD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I tried to install FreeBSD 2.2.1 and 2.2.2 to a Western Digital WDC33100H IDE HDD (3.1G). The kernel booted off the floppy and detected the correct model and size of the HDD. However, it hung after displaying `/stand/sysinstall running as init on vty0'. Pressing Alt+F3 made the computer scream and only a hard reset could stop it. Installing to other HDDs is OK. Then I hooked the WDC33100H as a slave disk to an existing FreeBSD 2.2.1 system. When I tried to fdisk, fdisk reported wrong geometry and the kernel gave out lots of error messages: wd1s1c: hard error reading fsbn 1wd1: status 59 error 10 I connected the HDD back to a new system as the only HDD and booted with a kernel from a floppy diskette. I issued the following command: dd if=/dev/rwd0c of=/dev/null bs=1b count=512 I got the error message: wd0s1c: wdstart: timeout waiting to give command reading fsbn 1wd0: status 0 error 0 wd0s1c: wdstart: timeout waiting to give command reading fsbn 1wd0: status 0 error 1 The error messages repeated and the system hung. Any hints? Your help is appreciated. P.S. I tried this HDD on different computers ( Pentium and Pentium PRO), the same result. The HDD is OK in DOS environment. I heard of someone else encountered this problem on WD HDDs about 1 or 2 months ago. -- --------------------- Jason Liao --------------------- From owner-freebsd-hardware Fri Sep 12 09:34:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA15455 for hardware-outgoing; Fri, 12 Sep 1997 09:34:35 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA15440 for ; Fri, 12 Sep 1997 09:34:28 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id SAA23735 for ; Fri, 12 Sep 1997 18:34:23 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id SAA08509 for freebsd-hardware@FreeBSD.ORG; Fri, 12 Sep 1997 18:33:55 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-uucp-2.10/nospam) id HAA12207; Fri, 12 Sep 1997 07:58:33 +0200 (CEST) Message-ID: <19970912075832.59214@keltia.freenix.fr> Date: Fri, 12 Sep 1997 07:58:32 +0200 From: Ollivier Robert To: freebsd-hardware@FreeBSD.ORG Subject: Re: IBM/Cyrix PR200+ References: <19970911221642.45617@keltia.freenix.fr> <199709120431.VAA28321@silvia.HIP.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199709120431.VAA28321@silvia.HIP.Berkeley.EDU>; from Satoshi Asami on Thu, Sep 11, 1997 at 09:31:50PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3634 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Satoshi Asami: > Speaking of which, can anyone with an *MX processor check the gus mmx > extension PR (filed under "gnu", I think) and try and see if copying > through the mmx registers instead of FP would be faster for some of > the CPU's? I don't expect it to be faster with the MMX registers because they're shared with the FPU ones... (like the Intel MMX registers). I've not made any test though. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Sat Sep 6 21:58:17 CEST 1997 From owner-freebsd-hardware Fri Sep 12 09:42:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA16332 for hardware-outgoing; Fri, 12 Sep 1997 09:42:27 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA16326 for ; Fri, 12 Sep 1997 09:42:24 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id JAA16957; Fri, 12 Sep 1997 09:42:03 -0700 (PDT) Date: Fri, 12 Sep 1997 09:42:03 -0700 (PDT) From: Howard Lew To: Satoshi Asami cc: roberto@keltia.freenix.fr, freebsd-hardware@FreeBSD.ORG Subject: Re: IBM/Cyrix PR200+ In-Reply-To: <199709120431.VAA28321@silvia.HIP.Berkeley.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 11 Sep 1997, Satoshi Asami wrote: > * > My too -- however, i suppose that Pentium-oriented copy/zero block > * > procedures don't work. > * > * Oh they do but much slower then the regular ones. > * > * Always use "flags 0x7" for npx0 in your config. file for both Cyrix and > * AMD's processors. > > Speaking of which, can anyone with an *MX processor check the gus mmx > extension PR (filed under "gnu", I think) and try and see if copying > through the mmx registers instead of FP would be faster for some of > the CPU's? > > Satoshi > Didn't find the PR, but the flags do help a Cyrix 6x86MX get quite a bit more MB/sec with dd. From owner-freebsd-hardware Fri Sep 12 09:49:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA16847 for hardware-outgoing; Fri, 12 Sep 1997 09:49:04 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [209.83.205.48]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA16822 for ; Fri, 12 Sep 1997 09:48:36 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.7/8.8.5) with ESMTP id LAA17464; Fri, 12 Sep 1997 11:47:08 -0500 (CDT) Message-Id: <199709121647.LAA17464@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: John-Mark Gurney cc: Brandon Hicks , freebsd-hardware@FreeBSD.ORG Subject: Re: hmmm.... Can This Be done??? In-reply-to: Your message of "Mon, 08 Sep 1997 23:38:53 PDT." <19970908233853.18847@hydrogen.nike.efn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Sep 1997 11:46:52 -0500 From: Wm Brian McCane Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Actually, I have seen serial keyboards that have all the function keys et al. It should be possible to add the capability to accept input from a serially connected keyboard. Then, if you have 2 mice, and 2 monitors, you have a 2 user X machine 8). brian From owner-freebsd-hardware Fri Sep 12 09:53:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA17266 for hardware-outgoing; Fri, 12 Sep 1997 09:53:13 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA17254; Fri, 12 Sep 1997 09:53:03 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id JAA20660; Fri, 12 Sep 1997 09:52:01 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709121652.JAA20660@GndRsh.aac.dev.com> Subject: Re: PCI DLink DFE500-TX 10/100MB DEC Tulip 21140AE REV2-C Chipset Ethernet Card In-Reply-To: from Jason Lixfeld at "Sep 12, 97 02:05:10 am" To: jlixfeld@idirect.com (Jason Lixfeld) Date: Fri, 12 Sep 1997 09:51:26 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is their support for this card? It did not have the drivers for it when I > attempted to use this card when doing an FTP install. I used a 3Com > 3C509B 10MB ISA. BSD/OS and Linux both had problems or driver > incompatibilities when 21140AC REV1-B updated to 21140AE REV2-C. I'm > wondering if FreeBSD 2.2.2 has the same incompatibility, and is their a > driver that will support the new chipset, and where do I find it to > compile it into a new kernel?! http://www.3am-software.com, thats Matt Thomas' site who is the author of the BSD drivers. The latest revision of his driver code should support this card. If you do install this driver could you give me an ack or nack on if it worked correctly or not, especially if you can test in both 10MB and 100MB modes. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hardware Fri Sep 12 10:02:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA18091 for hardware-outgoing; Fri, 12 Sep 1997 10:02:10 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA18084 for ; Fri, 12 Sep 1997 10:02:03 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id TAA23766 for ; Fri, 12 Sep 1997 19:01:53 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id TAA09416 for hardware@FreeBSD.ORG; Fri, 12 Sep 1997 19:01:36 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-uucp-2.10/nospam) id SAA14354; Fri, 12 Sep 1997 18:58:12 +0200 (CEST) Message-ID: <19970912185812.33524@keltia.freenix.fr> Date: Fri, 12 Sep 1997 18:58:12 +0200 From: Ollivier Robert To: "hardware@freebsd.org" Subject: Re: Fwd: K6 Linux Re-Compile Issue References: <199708281700.KAA16401@dragon.awen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199708281700.KAA16401@dragon.awen.com>; from Mike Burgett on Thu, Aug 28, 1997 at 10:00:39AM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3634 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Mike Burgett: > FWIW, I just got the following from AMD tech support, regarding the > problems I had reported with my initial K6 and running 'make world' I also got news from AMD. They told me they will swap my K6 for a new and fixed one in the near future (3 or 4 weeks). More details later. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Sat Sep 6 21:58:17 CEST 1997 From owner-freebsd-hardware Fri Sep 12 10:20:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA19972 for hardware-outgoing; Fri, 12 Sep 1997 10:20:48 -0700 (PDT) Received: from nemesis.idirect.com (root@nemesis.idirect.com [207.136.80.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA19924; Fri, 12 Sep 1997 10:20:26 -0700 (PDT) Received: from thor.idirect.com (jlixfeld@thor.idirect.com [207.136.80.105]) by nemesis.idirect.com (8.8.5/8.8.4) with SMTP id NAA10215; Fri, 12 Sep 1997 13:20:13 -0400 (EDT) Received: from localhost (jlixfeld@localhost) by thor.idirect.com (8.6.12/8.6.12) with SMTP id NAA09591; Fri, 12 Sep 1997 13:20:13 -0400 X-Authentication-Warning: thor.idirect.com: jlixfeld owned process doing -bs Date: Fri, 12 Sep 1997 13:20:13 -0400 (EDT) From: Jason Lixfeld To: Narvi cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: PCI DLink DFE500-TX 10/100MB DEC Tulip 21140AE REV2-C Chipset Ethernet Card In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm going to grab the driver off the site. I need the practise compiling kernels on BSD! :) I'm a linux expert, but due to it's limitations that our organization is quickly discovering, a switch to FreeBSD seems prudent at this point! On Fri, 12 Sep 1997, Narvi wrote: > > On Fri, 12 Sep 1997, Jason Lixfeld wrote: > > > Is their support for this card? It did not have the drivers for it when I > > attempted to use this card when doing an FTP install. I used a 3Com > > 3C509B 10MB ISA. BSD/OS and Linux both had problems or driver > > incompatibilities when 21140AC REV1-B updated to 21140AE REV2-C. I'm > > wondering if FreeBSD 2.2.2 has the same incompatibility, and is their a > > driver that will support the new chipset, and where do I find it to > > compile it into a new kernel?! > > > > Thanks in Advance, > > > > Jason Lixfeld > > > > > > Such driver exists and is available, look at www.3am-software.com. I can > mail the tar files to you aswell. It is a drop-in replacement. > > Sander > > There is no love, no good, no happiness and no future - > all these are just illusions. > > > From owner-freebsd-hardware Fri Sep 12 10:25:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA20493 for hardware-outgoing; Fri, 12 Sep 1997 10:25:07 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA20359; Fri, 12 Sep 1997 10:23:55 -0700 (PDT) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.6/8.8.4) with SMTP id UAA03637; Fri, 12 Sep 1997 20:04:53 +0300 (EEST) Date: Fri, 12 Sep 1997 20:04:53 +0300 (EEST) From: Narvi To: Jason Lixfeld cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: PCI DLink DFE500-TX 10/100MB DEC Tulip 21140AE REV2-C Chipset Ethernet Card In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 12 Sep 1997, Jason Lixfeld wrote: > Is their support for this card? It did not have the drivers for it when I > attempted to use this card when doing an FTP install. I used a 3Com > 3C509B 10MB ISA. BSD/OS and Linux both had problems or driver > incompatibilities when 21140AC REV1-B updated to 21140AE REV2-C. I'm > wondering if FreeBSD 2.2.2 has the same incompatibility, and is their a > driver that will support the new chipset, and where do I find it to > compile it into a new kernel?! > > Thanks in Advance, > > Jason Lixfeld > > Such driver exists and is available, look at www.3am-software.com. I can mail the tar files to you aswell. It is a drop-in replacement. Sander There is no love, no good, no happiness and no future - all these are just illusions. From owner-freebsd-hardware Fri Sep 12 11:15:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25139 for hardware-outgoing; Fri, 12 Sep 1997 11:15:42 -0700 (PDT) Received: from gw.rinet.ru (gw.rinet.ru [195.54.192.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA25126 for ; Fri, 12 Sep 1997 11:15:33 -0700 (PDT) Received: by gw.rinet.ru id WAA28568; (8.6.11/vak/1.9) Fri, 12 Sep 1997 22:13:32 +0400 From: marck@gw.rinet.ru (Dmitry Morozovsky) Message-Id: <199709121813.WAA28568@gw.rinet.ru> Subject: Cyrix/IBM 200+ memory speed To: freebsd-hardware@freebsd.org Date: Fri, 12 Sep 1997 22:13:32 +0400 (MSD) X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi there, according to previous discussion here is memory speed determined via dd /dev/null (CPU still recognized as 486) Results are very similar with clocks 60x2.5 and 75x2 (BTW, my ASUS T2P4 need to be set up as 60x3 (!) to be 60x2.5 indeed) Block size 4k 16k 128k 512k 1m 2m dd mem speed 135 113 140 113 50 44 By the way, which tag should I use to cvsup last 2.2 line current source tree? Sincerely, D.Marck ======================================================================== === D.Marck --- Dmitry Morozovsky --- marck@rinet.ru --- Wild Woozle === ======================================================================== From owner-freebsd-hardware Fri Sep 12 11:24:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25902 for hardware-outgoing; Fri, 12 Sep 1997 11:24:40 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA25882 for ; Fri, 12 Sep 1997 11:24:33 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id LAA04279; Fri, 12 Sep 1997 11:23:28 -0700 (PDT) Message-ID: <19970912112328.48238@hydrogen.nike.efn.org> Date: Fri, 12 Sep 1997 11:23:28 -0700 From: John-Mark Gurney To: Wm Brian McCane Cc: Brandon Hicks , freebsd-hardware@FreeBSD.ORG Subject: Re: hmmm.... Can This Be done??? References: <19970908233853.18847@hydrogen.nike.efn.org> <199709121647.LAA17464@bmccane.uit.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199709121647.LAA17464@bmccane.uit.net>; from Wm Brian McCane on Fri, Sep 12, 1997 at 11:46:52AM -0500 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wm Brian McCane scribbled this message on Sep 12: > Actually, I have seen serial keyboards that have all the function keys et al. > It should be possible to add the capability to accept input from a serially > connected keyboard. Then, if you have 2 mice, and 2 monitors, you have a 2 > user X machine 8). well.. you could probably contact Xig and see if they support taking input from your serial keyboard... I do know that some of their X servers support multi-headed operation... ttyl.. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hardware Fri Sep 12 11:25:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA26022 for hardware-outgoing; Fri, 12 Sep 1997 11:25:43 -0700 (PDT) Received: from lariat.lariat.org (ppp0.lariat.org@[129.72.251.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA26013 for ; Fri, 12 Sep 1997 11:25:38 -0700 (PDT) Received: from solo ([129.72.251.10] (may be forged)) by lariat.lariat.org (8.8.6/8.8.6) with SMTP id MAA27857; Fri, 12 Sep 1997 12:21:08 -0600 (MDT) Message-Id: <3.0.3.32.19970912122501.009588b0@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 12 Sep 1997 12:25:01 -0600 To: roberto@keltia.freenix.fr, freebsd-hardware@FreeBSD.ORG From: Brett Glass Subject: Re: IBM/Cyrix PR200+ In-Reply-To: <88256510.00608242.00@IWNS2.infoworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If the FPU attempts to normalize or convert the number, or otherwise do something with the remaining 16 bits of the 80-bit internal register, it might be slower. I've wondered about this but haven't tested yet. --Brett Glass At 07:58 AM 9/12/97 +0200, roberto@keltia.freenix.fr wrote: >I don't expect it to be faster with the MMX registers because they're >shared with the FPU ones... (like the Intel MMX registers). I've not made >any test though. >-- >Ollivier ROBERT -=- FreeBSD: There are no limits -=- >roberto@keltia.freenix.fr >FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Sat Sep 6 21:58:17 CEST 1997 > > > > From owner-freebsd-hardware Fri Sep 12 12:11:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA00427 for hardware-outgoing; Fri, 12 Sep 1997 12:11:53 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA00167; Fri, 12 Sep 1997 12:07:44 -0700 (PDT) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.6/8.8.4) with SMTP id VAA04215; Fri, 12 Sep 1997 21:47:01 +0300 (EEST) Date: Fri, 12 Sep 1997 21:47:01 +0300 (EEST) From: Narvi To: Jason Lixfeld cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: PCI DLink DFE500-TX 10/100MB DEC Tulip 21140AE REV2-C Chipset Ethernet Card In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 12 Sep 1997, Jason Lixfeld wrote: > I'm going to grab the driver off the site. I need the practise compiling > kernels on BSD! :) I'm a linux expert, but due to it's limitations that > our organization is quickly discovering, a switch to FreeBSD seems prudent > at this point! > You may (I cant confirm this, as I always do it just in case) have to recompile the ifconfig program aswell. Just untar the the tarballs into the right places. Sander There is no love, no good, no happiness and no future - all these are just illusions. From owner-freebsd-hardware Fri Sep 12 12:45:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA02885 for hardware-outgoing; Fri, 12 Sep 1997 12:45:28 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA02491; Fri, 12 Sep 1997 12:40:26 -0700 (PDT) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.6/8.8.4) with SMTP id VAA04287; Fri, 12 Sep 1997 21:56:38 +0300 (EEST) Date: Fri, 12 Sep 1997 21:56:38 +0300 (EEST) From: Narvi To: "Rodney W. Grimes" cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: PCI DLink DFE500-TX 10/100MB DEC Tulip 21140AE REV2-C Chipset Ethernet Card In-Reply-To: <199709121652.JAA20660@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 12 Sep 1997, Rodney W. Grimes wrote: > > Is their support for this card? It did not have the drivers for it when I > > attempted to use this card when doing an FTP install. I used a 3Com > > 3C509B 10MB ISA. BSD/OS and Linux both had problems or driver > > incompatibilities when 21140AC REV1-B updated to 21140AE REV2-C. I'm > > wondering if FreeBSD 2.2.2 has the same incompatibility, and is their a > > driver that will support the new chipset, and where do I find it to > > compile it into a new kernel?! > > http://www.3am-software.com, thats Matt Thomas' site who is the author > of the BSD drivers. The latest revision of his driver code should support > this card. If you do install this driver could you give me an ack or nack > on if it worked correctly or not, especially if you can test in both > 10MB and 100MB modes. > I have used these cards for some time now and have seen zero problems. They do, however, work only in 100Mb mode - I have no way of testing them in 10Mb setting (=no 10Mb hub, 10Mb is thinnet only). Sander There is no love, no good, no happiness and no future - all these are just illusions. > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation, Inc. Reliable computers for FreeBSD > From owner-freebsd-hardware Fri Sep 12 13:41:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA07244 for hardware-outgoing; Fri, 12 Sep 1997 13:41:17 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA06841 for ; Fri, 12 Sep 1997 13:35:49 -0700 (PDT) Received: (from bsdhack@localhost) by shadows.aeon.net (8.8.7/8.8.3) id WAA26322; Fri, 12 Sep 1997 22:52:55 +0300 (EET DST) From: mika ruohotie Message-Id: <199709121952.WAA26322@shadows.aeon.net> Subject: Re: Important: -O flag crashes cc in libncurses In-Reply-To: <3.0.3.32.19970911100641.006992ec@giovannelli.it> from Gianmarco Giovannelli at "Sep 11, 97 10:06:41 am" To: gmarco@giovannelli.it (Gianmarco Giovannelli) Date: Fri, 12 Sep 1997 22:52:55 +0300 (EET DST) Cc: hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > first of all this is my configuration : Mb Asus Tx97-e, Pentium 233, 64mb overclocked? if yes, this reply applies. if not, it still might be true... > (edo ram), 2 hd 4 giga wide scsi quantum, 2940uw, a dec 21141 ethernet > cc: Internal compiler error: program cc1 got fatal signal 10 > cc: Internal compiler error: program cc1 got fatal signal 10 > cc: Internal compiler error: program cc1 got fatal signal 6 > cc: Internal compiler error: program cc1 got fatal signal 10 even tho you get it to work with -O2 and -O3, i'd say you crash your cc coz of the memory or coz of your cpu. those just cant keep up, or something. at least i've gotten those coz of memory, slownig ram or changing it to better (quolity and/or faster) have always fixed those for me. or just the cpu, cool it more. my cpu gives me those whenever i try to overclock it, i have better coolers waiting my next shutdown. with proper cooling we run our dns at work now on 250mhz mmx. =)))))))) (which model you have anyway? black? those cool better...) and i believe this belongs to the hardware@freebsd.org mickey From owner-freebsd-hardware Sat Sep 13 10:36:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA15298 for hardware-outgoing; Sat, 13 Sep 1997 10:36:28 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA15293 for ; Sat, 13 Sep 1997 10:36:25 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id KAA14021; Sat, 13 Sep 1997 10:36:04 -0700 (PDT) Date: Sat, 13 Sep 1997 10:36:04 -0700 (PDT) From: Howard Lew To: Dmitry Morozovsky cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Cyrix/IBM 200+ memory speed In-Reply-To: <199709121813.WAA28568@gw.rinet.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 12 Sep 1997, Dmitry Morozovsky wrote: > Hi there, > > according to previous discussion > > here is memory speed determined via dd /dev/null > (CPU still recognized as 486) > > Results are very similar with clocks 60x2.5 and 75x2 (BTW, my ASUS T2P4 need > to be set up as 60x3 (!) to be 60x2.5 indeed) > > Block size 4k 16k 128k 512k 1m 2m > > dd mem speed 135 113 140 113 50 44 > Hmmm... Shouldn't 75x2 give much better memory speed than with a 60MHz bus? Cyrix 6x86MX-PR166 (66x2), PC Chips M560 ALI Alladin IV+ Block size 4k 16k 32k 64k 128k 512k 1m 2m dd mem speed 180 323 282 220 135 117 76 73 Average values are a little higher if shut down X and use a vty (i.e. 1m is 82) From owner-freebsd-hardware Sat Sep 13 10:40:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA15458 for hardware-outgoing; Sat, 13 Sep 1997 10:40:25 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA15437; Sat, 13 Sep 1997 10:40:18 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id NAA09598; Sat, 13 Sep 1997 13:43:31 -0400 (EDT) Date: Sat, 13 Sep 1997 13:43:31 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709131743.NAA09598@sabre.goldsword.com> To: freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jasonl@xinetron.com Subject: Re: Failed to install on WD WDC33100H HDD Cc: jfarmer@goldsword.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 12 Sep 1997 07:53:21 -0700 Jason Liao said: >I tried to install FreeBSD 2.2.1 and 2.2.2 to a Western Digital >WDC33100H IDE HDD (3.1G). The kernel booted off the floppy and detected >the correct model and size of the HDD. However, it hung after >displaying `/stand/sysinstall running as init on vty0'. Pressing Alt+F3 >made the computer scream and only a hard reset could stop it. >Installing to other HDDs is OK. > >Then I hooked the WDC33100H as a slave disk to an existing FreeBSD 2.2.1 >system. When I tried to fdisk, fdisk reported wrong geometry and the >kernel gave out lots of error messages: >wd1s1c: hard error reading fsbn 1wd1: status 59 >error 10 > >I connected the HDD back to a new system as the only HDD and booted with >a kernel from a floppy diskette. I issued the following command: >dd if=/dev/rwd0c of=/dev/null bs=1b count=512 >I got the error message: >wd0s1c: wdstart: timeout waiting to give command reading fsbn 1wd0: >status 0 error 0 >wd0s1c: wdstart: timeout waiting to give command reading fsbn 1wd0: >status 0 error 1 >The error messages repeated and the system hung. > >Any hints? Your help is appreciated. > >P.S. I tried this HDD on different computers ( Pentium and Pentium >PRO), the same result. The HDD is OK in DOS environment. I heard of >someone else encountered this problem on WD HDDs about 1 or 2 months >ago. I don't recall seeing the thread on WD drives, but I use the WD cavier drives (EIDE) models for all my clients' Win/Dos, etc. workstations AND for low end mail servers & routers. Matter of fact, I have one with the 2.1gb drive running on the build/burn-in bench now... What type of motherboard/controller are you using with the drive? It sounds like a BIOS/LBA type conflict, though the drive should be detectable. When you boot the board, what does the BIOS tell you? Is it auto-detecting the drive? Setting up any weird mappings? Are you setting the disk up to be used by both WinDos and FreeBSD? John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-hardware Sat Sep 13 10:45:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA15719 for hardware-outgoing; Sat, 13 Sep 1997 10:45:13 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA15714 for ; Sat, 13 Sep 1997 10:45:09 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id NAA09633; Sat, 13 Sep 1997 13:48:44 -0400 (EDT) Date: Sat, 13 Sep 1997 13:48:44 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709131748.NAA09633@sabre.goldsword.com> To: hardware@FreeBSD.ORG, roberto@keltia.freenix.fr Subject: Re: Fwd: K6 Linux Re-Compile Issue Cc: jfarmer@goldsword.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 12 Sep 1997 18:58:12 +0200 Ollivier Robert said: >According to Mike Burgett: >> FWIW, I just got the following from AMD tech support, regarding the >> problems I had reported with my initial K6 and running 'make world' > >I also got news from AMD. They told me they will swap my K6 for a new and >fixed one in the near future (3 or 4 weeks). More details later. >-- When you get yours & verify that the problem is fixed, _please_ forward details such as rev. numbers & stepping so that we can be sure to get the new ones... John (Who has more than once had a distributor pass off old stock as new...) ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-hardware Sat Sep 13 12:13:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA21356 for hardware-outgoing; Sat, 13 Sep 1997 12:13:30 -0700 (PDT) Received: from gw.rinet.ru (gw.rinet.ru [195.54.192.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA21351 for ; Sat, 13 Sep 1997 12:13:23 -0700 (PDT) Received: by gw.rinet.ru id XAA09441; (8.6.11/vak/1.9) Sat, 13 Sep 1997 23:03:03 +0400 From: marck@gw.rinet.ru (Dmitry Morozovsky) Message-Id: <199709131903.XAA09441@gw.rinet.ru> Subject: Re: Cyrix/IBM 200+ memory speed To: hlew@www2.shoppersnet.com (Howard Lew) Date: Sat, 13 Sep 1997 23:03:02 +0400 (MSD) Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: from "Howard Lew" at Sep 13, 97 10:36:04 am X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi there, > > here is memory speed determined via dd /dev/null > > (CPU still recognized as 486) > > > > Results are very similar with clocks 60x2.5 and 75x2 (BTW, my ASUS T2P4 need > > to be set up as 60x3 (!) to be 60x2.5 indeed) > > > > Block size 4k 16k 128k 512k 1m 2m > > dd mem speed 135 113 140 113 50 44 > > Hmmm... Shouldn't 75x2 give much better memory speed than with a 60MHz bus? > Cyrix 6x86MX-PR166 (66x2), PC Chips M560 ALI Alladin IV+ ~~~~~ > Block size 4k 16k 32k 64k 128k 512k 1m 2m > dd mem speed 180 323 282 220 135 117 76 73 > > Average values are a little higher if shut down X and use a vty (i.e. 1m > is 82) Howard, look twice at underlined statement. My CPU is 8x86/L-PR200+ (not MMX) However, results are *independent* of bus speed -- and that's strange for me too. If I use 60x3 (not x2.5! -- then BIOS reported CPU as 150+) results are the same (differences may be kept inside 1-2%) as for 75x2. Misterious. Sincerely, D.Marck ======================================================================== === D.Marck --- Dmitry Morozovsky --- marck@rinet.ru --- Wild Woozle === ======================================================================== From owner-freebsd-hardware Sat Sep 13 12:38:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA22349 for hardware-outgoing; Sat, 13 Sep 1997 12:38:01 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA22341 for ; Sat, 13 Sep 1997 12:37:56 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.7/8.7.3) id OAA00848; Sat, 13 Sep 1997 14:37:22 -0500 (CDT) Message-ID: <19970913143722.25435@my.domain> Date: Sat, 13 Sep 1997 14:37:22 -0500 From: Tom Jackson To: freebsd-hardware@freebsd.org Subject: Micropolis Runs Too HOT! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, Just started using a Micropolis Tomahawk, 7200 rpm 4.5 gb hard disk about a week ago. All was well until yesterday when starting getting scb messages and system froze. Killed system (no shutdown,turn power off) and when trying to startup again, the scsi bios did not see the disk at scsi id 0. Took case off and the disk was hot to very hot to the touch. Cooled it off with a fan and turned air conditioning on. The long and short of it is now I am running my computer with the case off and a fan blowing on the hard disk bay. The hot mic is the bottom one in the bay. There is a drive space before the next drive, also a Micropolis 2 gig, 5400 rpm drive (it runs cool). Has anyone seen a problem like this and do you have any suggestions. I have contacted the Micropolis web site but have not heard anything back yet. The warranty is like a catch 22: "If you run the disk too hot, we will void your warranty" Anyone, please Tom From owner-freebsd-hardware Sat Sep 13 13:33:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA27874 for hardware-outgoing; Sat, 13 Sep 1997 13:33:56 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA27863 for ; Sat, 13 Sep 1997 13:33:52 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x9yoF-0003HU-00; Sat, 13 Sep 1997 13:28:51 -0700 Date: Sat, 13 Sep 1997 13:28:50 -0700 (PDT) From: Tom To: Tom Jackson cc: freebsd-hardware@freebsd.org Subject: Re: Micropolis Runs Too HOT! In-Reply-To: <19970913143722.25435@my.domain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 13 Sep 1997, Tom Jackson wrote: > Hi all, > > Just started using a Micropolis Tomahawk, 7200 rpm 4.5 gb > hard disk about a week ago. All was well until yesterday > when starting getting scb messages and system froze. > Killed system (no shutdown,turn power off) and when trying > to startup again, the scsi bios did not see the disk at > scsi id 0. Took case off and the disk was hot to very hot > to the touch. Cooled it off with a fan and turned air > conditioning on. > > The long and short of it is now I am running my computer > with the case off and a fan blowing on the hard disk bay. > The hot mic is the bottom one in the bay. There is a drive > space before the next drive, also a Micropolis 2 gig, 5400 > rpm drive (it runs cool). > > Has anyone seen a problem like this and do you have any > suggestions. I have contacted the Micropolis web site but > have not heard anything back yet. > > The warranty is like a catch 22: "If you run the disk too > hot, we will void your warranty" > > Anyone, please > > Tom Microcopolis drives suck. You will need to mount a fan near the drive. I have two Micropolis 3243 drives. I eventually mounted two 50 CFM fans on the case, which kept the drives at room temperate. This worked well, but then one of the drives begain to develop bad sectors. I turned auto-remapping on, and the problem disappeared for a while, and then returned presumably because the spare area was full. This same drive started to hang on a weekly basis, and require a power cycle to be properly detected by the controller (same situation as your drive). Was definitely not heat related, as the drives are *well* cooled. Seems to be a software problem. I also have some more Microcrapolis horror stories involving a 24GB drive array. Microcrapolis engineers actually came onsite for this one, and did firmware upgrades, twice. After a year, the entire thing was sent back for full credit. Unless you like to punish yourself, DON'T get Micropolis drives. Tom From owner-freebsd-hardware Sat Sep 13 16:41:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA06377 for hardware-outgoing; Sat, 13 Sep 1997 16:41:50 -0700 (PDT) Received: from pegasus.com (pegasus.com [206.127.225.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA06372 for ; Sat, 13 Sep 1997 16:41:44 -0700 (PDT) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id NAA23393; Sat, 13 Sep 1997 13:41:23 -1000 Date: Sat, 13 Sep 1997 13:41:23 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199709132341.NAA23393@pegasus.com> In-Reply-To: Tom "Re: Micropolis Runs Too HOT!" (Sep 13, 1:28pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-hardware@FreeBSD.ORG Subject: Re: Micropolis Runs Too HOT! Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk } } Microcopolis drives suck. You will need to mount a fan near the drive. } } I have two Micropolis 3243 drives. I eventually mounted two 50 CFM fans } on the case, which kept the drives at room temperate. This worked well, } but then one of the drives begain to develop bad sectors. I turned } auto-remapping on, and the problem disappeared for a while, and then } returned presumably because the spare area was full. This same drive } started to hang on a weekly basis, and require a power cycle to be } properly detected by the controller (same situation as your drive). Was } definitely not heat related, as the drives are *well* cooled. Seems to be } a software problem. } } I also have some more Microcrapolis horror stories involving a 24GB } drive array. Microcrapolis engineers actually came onsite for this one, } and did firmware upgrades, twice. After a year, the entire thing was sent } back for full credit. } } Unless you like to punish yourself, DON'T get Micropolis drives. } Micropolis has a reputation for poor quality control going back many years. I know of three vendors that swore them off at various stages -- mostly due to multiple DOAs. They tend to have more bad sectors when new than many of their competitors. Richard