From owner-freebsd-hardware Sun Sep 28 05:47:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA29765 for hardware-outgoing; Sun, 28 Sep 1997 05:47:47 -0700 (PDT) Received: from david.siemens.de (david.siemens.de [139.23.36.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA29760 for ; Sun, 28 Sep 1997 05:47:44 -0700 (PDT) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.7/8.8.5) with ESMTP id OAA11261 for ; Sun, 28 Sep 1997 14:47:42 +0200 (MDT) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.7/8.8.5) with ESMTP id OAA24130 for ; Sun, 28 Sep 1997 14:47:41 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.7/8.8.7) id OAA28654 for ; Sun, 28 Sep 1997 14:47:42 +0200 (MET DST) From: Andre Albsmeier Message-Id: <199709281247.OAA05256@curry.mchp.siemens.de> Subject: This K6 works well also To: freebsd-hardware@freebsd.org Date: Sun, 28 Sep 1997 14:47:39 +0200 (CEST) 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 JFYI, this one works great: This is a Revision C chip: AMD-K6-200ALR 2.9V CORE/3.3V I/O C 9736AJKW Board Chaintech 5IFM1 with 64MB Speedup compared to P5-200 (bytebench). int 1.88 float 0.92 dhry2reg 1.45 kernel make all 1.35 -Andre From owner-freebsd-hardware Sun Sep 28 15:18:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA26423 for hardware-outgoing; Sun, 28 Sep 1997 15:18:19 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA26415 for ; Sun, 28 Sep 1997 15:18:16 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id PAA01633; Sun, 28 Sep 1997 15:17:28 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id SAA20327; Sun, 28 Sep 1997 18:17:25 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id SAA17180; Sun, 28 Sep 1997 18:17:25 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.7/8.7.3) id RAA23164; Sun, 28 Sep 1997 17:21:22 -0500 (CDT) Date: Sun, 28 Sep 1997 17:21:22 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199709282221.RAA23164@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn To: michaelv@MindBender.serv.net Cc: toj@gorilla.net, freebsd-hardware@freefall.freebsd.org Subject: Re: supermicro p6sns/p6sas References: <19970927224110.13321@my.domain> <199709280516.WAA04321@MindBender.serv.net> X-Mailer: VM 6.33 under 19.14 XEmacs Lucid Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Quoth Michael L. VanLoon -- HeadCandy.com on Sat, 27 September: : Socket 8 indeed appears to have been a limited detour. Slot 1 may in : time be superceeded by something better. IIRC, Intel plans to phase out slot 1 during the coming year. : Socket 7 has a very limited future. It simply doesn't have any way of : coping with some of the new technology that will be necessary to make : any sort of performance boosts possible beyond 300MHz. The supporting argument is insufficient for the conclusion. AMD and Cyrix are actively engaged in providing alternate paths to cache. One proposed solution is to make a low-profile Socket 7 module with an on-board cache controller, making the Socket 7 interface effectively a point-to-point bus -- analogous to Slot 1. : AMD and Cyrix may indeed be able to perpetuate several years more of : Socket 7 chipsets, in the secondary market. But it will be a typical : AMD/Cyrix market, where performance is secondary, and low-cost is : king. K6 and P-II numbers are within a few months of each other, so I can't agree with the implication that it will therefore not be possible to maintain a Socket 7 system with competetive performance. I do believe that it is quite clear that Socket 7 has superior life expectancy to both Socket 8 (already hard to find many P6 parts) and Slot 1 (Intel-planned short lifespan, to be replaced by Slot 2 in 98). When Slot 2 systems are available, the situation may change, but Intel will have very little reason to repent of its planned motherboard obsolence policy unless the competitors produce a non-proprietary competetive alternative. From owner-freebsd-hardware Sun Sep 28 20:00:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA10657 for hardware-outgoing; Sun, 28 Sep 1997 20:00:37 -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 UAA10646 for ; Sun, 28 Sep 1997 20:00:32 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xFW2E-0000jy-00; Sun, 28 Sep 1997 19:58:10 -0700 Date: Sun, 28 Sep 1997 19:58:04 -0700 (PDT) From: Tom To: Tony Kimball cc: michaelv@MindBender.serv.net, toj@gorilla.net, freebsd-hardware@freefall.freebsd.org Subject: Re: supermicro p6sns/p6sas In-Reply-To: <199709282221.RAA23164@compound.east.sun.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 Sun, 28 Sep 1997, Tony Kimball wrote: > Quoth Michael L. VanLoon -- HeadCandy.com on Sat, 27 September: > : Socket 8 indeed appears to have been a limited detour. Slot 1 may in > : time be superceeded by something better. > > IIRC, Intel plans to phase out slot 1 during the coming year. > > : Socket 7 has a very limited future. It simply doesn't have any way of > : coping with some of the new technology that will be necessary to make > : any sort of performance boosts possible beyond 300MHz. > > The supporting argument is insufficient for the conclusion. AMD and > Cyrix are actively engaged in providing alternate paths to cache. One > proposed solution is to make a low-profile Socket 7 module with an > on-board cache controller, making the Socket 7 interface effectively > a point-to-point bus -- analogous to Slot 1. None of these methods exist yet. I'm little dubious about how well AMD can make it work. K6, due to bugs, was unable to run FreeBSD reliably up until a few weeks ago (see archives about which stepping are known to work, and which are not). > : AMD and Cyrix may indeed be able to perpetuate several years more of > : Socket 7 chipsets, in the secondary market. But it will be a typical > : AMD/Cyrix market, where performance is secondary, and low-cost is > : king. > > K6 and P-II numbers are within a few months of each other, so I can't > agree with the implication that it will therefore not be possible to > maintain a Socket 7 system with competetive performance. Is CPU performance measured in months now? :) > I do believe that it is quite clear that Socket 7 has superior life > expectancy to both Socket 8 (already hard to find many P6 parts) and > Slot 1 (Intel-planned short lifespan, to be replaced by Slot 2 in 98). I don't find it hard to find socket 8 parts (motherboards and CPUs). Everyone has them, and lots of stock. Why is it clear that socket 7 has superior life expentency to socket 8? Socket 8 is better (better bandwidth) than socket 7, so why doesn't AMD just make socket 8 processors rather than messing around trying to sqeeze more out of socket 7? I agree with Michael. AMD/Cyrix is targetting the secondary market, otherwise they'd be cranking out processors to use with the faster socket 8. Also, you can use socket 8 processors in a slot 1 with an adapter. I have no idea why AMD isn't exploiting this to put CPUs onto slot 1 motherboards now. Tom From owner-freebsd-hardware Sun Sep 28 20:50:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA13298 for hardware-outgoing; Sun, 28 Sep 1997 20:50:32 -0700 (PDT) Received: from umr.edu (hermes.cc.umr.edu [131.151.1.68]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA13290 for ; Sun, 28 Sep 1997 20:50:21 -0700 (PDT) Received: from this.umr.edu (dialup-pkr-3-16.network.umr.edu [131.151.253.51]) via SMTP by hermes.cc.umr.edu (8.8.7/R.4.20) id WAA22570; Sun, 28 Sep 1997 22:50:14 -0500 (CDT) Message-Id: <3.0.1.32.19970928224949.006a229c@pop3.umr.edu> X-Sender: bbryan@pop3.umr.edu X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Sun, 28 Sep 1997 22:49:49 -0500 To: hardware@freebsd.org From: Ben Bryan Subject: Re: supermicro p6sns/p6sas In-Reply-To: References: <199709282221.RAA23164@compound.east.sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 19:58 28-09-97 -0700, you wrote: > >On Sun, 28 Sep 1997, Tony Kimball wrote: > >> Quoth Michael L. VanLoon -- HeadCandy.com on Sat, 27 September: >> : Socket 8 indeed appears to have been a limited detour. Slot 1 may in >> : time be superceeded by something better. >> >> IIRC, Intel plans to phase out slot 1 during the coming year. >> >> : Socket 7 has a very limited future. It simply doesn't have any way of >> : coping with some of the new technology that will be necessary to make >> : any sort of performance boosts possible beyond 300MHz. >> >> The supporting argument is insufficient for the conclusion. AMD and >> Cyrix are actively engaged in providing alternate paths to cache. One >> proposed solution is to make a low-profile Socket 7 module with an >> on-board cache controller, making the Socket 7 interface effectively >> a point-to-point bus -- analogous to Slot 1. > > None of these methods exist yet. I'm little dubious about how well AMD >can make it work. K6, due to bugs, was unable to run FreeBSD reliably up >until a few weeks ago (see archives about which stepping are known to >work, and which are not). Actually, the on chip cache controller does exist, sorta. The Cyrix MediaGX line of processors have an on chip memory controller and run without L2 cache yet perform almost identically to the 6x86 line. > >> : AMD and Cyrix may indeed be able to perpetuate several years more of >> : Socket 7 chipsets, in the secondary market. But it will be a typical >> : AMD/Cyrix market, where performance is secondary, and low-cost is >> : king. >> >> K6 and P-II numbers are within a few months of each other, so I can't >> agree with the implication that it will therefore not be possible to >> maintain a Socket 7 system with competetive performance. > > Is CPU performance measured in months now? :) > >> I do believe that it is quite clear that Socket 7 has superior life >> expectancy to both Socket 8 (already hard to find many P6 parts) and >> Slot 1 (Intel-planned short lifespan, to be replaced by Slot 2 in 98). > > I don't find it hard to find socket 8 parts (motherboards and CPUs). >Everyone has them, and lots of stock. > > Why is it clear that socket 7 has superior life expentency to socket 8? >Socket 8 is better (better bandwidth) than socket 7, so why doesn't AMD >just make socket 8 processors rather than messing around trying to sqeeze >more out of socket 7? I agree with Michael. AMD/Cyrix is targetting the >secondary market, otherwise they'd be cranking out processors to use with >the faster socket 8. > > Also, you can use socket 8 processors in a slot 1 with an adapter. >I have no idea why AMD isn't exploiting this to put CPUs onto slot 1 >motherboards now. > >Tom Why don't they use socket 8? Simple. Intel patented it just as they did slot 1. Slot 1 will be dead by next July. Socket seven will be in use by AMD and Cyrix for the next year at least. After then they will announce some new socket/slot design for the K7/7x86 or whatever they're going to call the next generation. And given the performance of a Cyrix chip at 225Mhz (winstone w/in a point of a PII 266) I'm pretty sure most users will be happy with a Cyrix chip at 300Mhz. And those who want more FP power can get one of the new K6+ chips that are due to be announced next month. Or they could just go buy a 21264 Alpha... Ben Ben Bryan ME/CS University of Missouri-Rolla Listen to KMNR, you fools. 89.7fm http://www.umr.edu/~kmnr From owner-freebsd-hardware Sun Sep 28 22:58:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA19422 for hardware-outgoing; Sun, 28 Sep 1997 22:58:39 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA19416 for ; Sun, 28 Sep 1997 22:58:31 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.7/8.7.3) id AAA12420; Mon, 29 Sep 1997 00:58:36 -0500 (CDT) Message-ID: <19970929005835.01396@my.domain> Date: Mon, 29 Sep 1997 00:58:35 -0500 From: Tom Jackson To: hardware@FreeBSD.ORG Subject: Re: K6 Update & AMD Statement References: <342A79F5.41C67EA6@prima.ruhr.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <342A79F5.41C67EA6@prima.ruhr.de>; from Philipp Reichmuth on Thu, Sep 25, 1997 at 04:49:25PM +0200 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Sep 25, 1997 at 04:49:25PM +0200, Philipp Reichmuth wrote: > Hi folks! > > Good news for the K6: I just got mine swapped by my dealer; it was a > revision 9721 chip, and he swapped it for a 9735 chip. It now works > fine. I'll redo the make world for a couple of times the next weeks and > see what I'll get. > > Second good news: I wrote to AMD about it, and they seem genuinely > concerned with it, or so I gather from their mail. Here's what they > wrote (follows) > > Philipp > > ==================> begin AMD mail <============ > > Dear Philipp, > > 1. We believe you are encountering Erratum 2.6.2 that is fully > documented > in the AMD-K6 MMX Enhanced Processor Revision Guide posted on our > website, > www.amd.com. Due to the long list of rare conditions necessary for this > erratum to occur, the issue does not effect general users in a DOS or > Windows environment. It appears to be limited to a special cases as in > the > Linux kernal re-compile. > > 2. A design change that fixes the erratum has been identified and is > currently being implemented in a future revision of the AMD-K6 > processor. > > 3. AMD stands behind its products and wants you to be fully satisfied > with > your choice. > To this end, we are offering to replace your processor as the new > revision > becomes available. > > 4 To replace your processor we need the following information. We will > contact you in about 3 weeks with more specifics on when and how the > processor will be replaced. > > - Name > > - Address > > - Phone Number > > - Type of System or Motherboard > > - Processor Frequency > > Kind Regards > Tvrtko > AMD Hotline / Technical Support. > > =========================> End AMD Stuff <========================= > > (but please don't post all this into the wide world - it's a bit touchy > with personal email) > Have you ask him to contact David G to get a replacement to him so the evaluation results can be known to all of us? Tom From owner-freebsd-hardware Mon Sep 29 08:05:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA15469 for hardware-outgoing; Mon, 29 Sep 1997 08:05:30 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA15464 for ; Mon, 29 Sep 1997 08:05:19 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id IAA14866; Mon, 29 Sep 1997 08:00:58 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id LAA11127; Mon, 29 Sep 1997 11:00:55 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id LAA11372; Mon, 29 Sep 1997 11:00:53 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.7/8.7.3) id KAA25150; Mon, 29 Sep 1997 10:05:02 -0500 (CDT) Date: Mon, 29 Sep 1997 10:05:02 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199709291505.KAA25150@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn To: tom@sdf.com Cc: Anthony.Kimball@East.Sun.COM, michaelv@MindBender.serv.net, toj@gorilla.net, freebsd-hardware@freefall.freebsd.org Subject: Re: supermicro p6sns/p6sas References: <199709282221.RAA23164@compound.east.sun.com> X-Mailer: VM 6.33 under 19.14 XEmacs Lucid Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Quoth Tom on Sun, 28 September: : > The supporting argument is insufficient for the conclusion. AMD and : > Cyrix are actively engaged in providing alternate paths to cache. One : > proposed solution is to make a low-profile Socket 7 module with an : > on-board cache controller, making the Socket 7 interface effectively : > a point-to-point bus -- analogous to Slot 1. : : None of these methods exist yet. Compare the MediaGX. "Proposed" in the sense of proposed for industry standardization. : Is CPU performance measured in months now? :) I was not thinking about CPUs, but CPU development paths. To my mind, the performance comparison of different development paths (application-based, rather than feature-based -- so this principle can apply equally well to comparing Alpha to clone-86 or name-your-poison) is best done, not in terms of raw performance of the best exemplar at any given moment, but rather, by how long a given performance point of one development path (i.e. performance of best exemplar, or perhaps best exemplar at a given cost-benefit-point, depending on the planning purposes of the metric) lags behind the equivalent point in the development cycle of another path. This approach is much more useful for purposes of technology management (e.g. in an enterprise) than is raw benchmarking -- and I see no reason why I should not apply the same rationale to my personal purchase planning, on a smaller scale. But for some people/situations, all that matters is what runs make world fastest within your budget, or whatever. We can all read the benchmarks, eh? : I'm little dubious about how well AMD : can make it work. K6, due to bugs, was unable to run FreeBSD reliably up : until a few weeks ago (see archives about which stepping are known to : work, and which are not). And we all know that Intel has had no major Pentium or PPro bugs? (BIG smiley face on that one.) Frankly I don't see any reasonable argument to the effect that AMD or Cyrix are less technically competent than Intel -- quite the contrary, given track records (and the fact that the AMD/Cyrix task is much more difficult than the Intel task). : Also, you can use socket 8 processors in a slot 1 with an adapter. Where can I learn about this? From owner-freebsd-hardware Mon Sep 29 10:49:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA25627 for hardware-outgoing; Mon, 29 Sep 1997 10:49:52 -0700 (PDT) Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.219]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA25606; Mon, 29 Sep 1997 10:49:46 -0700 (PDT) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id KAA03060; Mon, 29 Sep 1997 10:49:34 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA175415373; Mon, 29 Sep 1997 10:49:33 -0700 Received: from mina.sr.hp.com by mina.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA280885372; Mon, 29 Sep 1997 10:49:32 -0700 Message-Id: <199709291749.AA280885372@mina.sr.hp.com> To: hardware@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: K6 Update & AMD Statement Reply-To: darrylo@sr.hp.com In-Reply-To: Your message of "Sat, 27 Sep 1997 12:43:35 EDT." <199709271643.MAA17859@sabre.goldsword.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Mon, 29 Sep 1997 10:49:32 -0700 From: Darryl Okahata Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "John T. Farmer" wrote: > On Sat, 27 Sep 1997 18:04:53 +0200 Poul-Henning Kamp said: > >I have a K6/233 here which has by now completed 50 or more make worlds, > >no complaints. > > > >It is marked: > > AMD-K6-233ANR > > 3.2V CORE / 3.3V I/O > > B 9731EJBW > ^^^^^^^^ > > This is what I'm told is the important part. The stepping must be 9731 or > later. This looks like a date code (when the IC was manufactured), and not a stepping. If it is a date code, "9731" would be the 31st week of 1997, which is the last week in July. -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hardware Mon Sep 29 10:58:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA26228 for hardware-outgoing; Mon, 29 Sep 1997 10:58:52 -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 KAA26221 for ; Mon, 29 Sep 1997 10:58:48 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xFk3S-00018A-00; Mon, 29 Sep 1997 10:56:22 -0700 Date: Mon, 29 Sep 1997 10:56:06 -0700 (PDT) From: Tom To: Tony Kimball cc: michaelv@MindBender.serv.net, toj@gorilla.net, freebsd-hardware@freefall.freebsd.org Subject: Re: supermicro p6sns/p6sas In-Reply-To: <199709291505.KAA25150@compound.east.sun.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 Mon, 29 Sep 1997, Tony Kimball wrote: ... > : I'm little dubious about how well AMD > : can make it work. K6, due to bugs, was unable to run FreeBSD reliably up > : until a few weeks ago (see archives about which stepping are known to > : work, and which are not). > > And we all know that Intel has had no major Pentium or PPro bugs? Nothing that affected FreeBSD anyhow, and FreeBSD uses a wide variety of features. > (BIG smiley face on that one.) Frankly I don't see any reasonable > argument to the effect that AMD or Cyrix are less technically > competent than Intel -- quite the contrary, given track records (and > the fact that the AMD/Cyrix task is much more difficult than the > Intel task). Intel's real competition is not AMD and Cyrix, but DEC, Sparc (Sun), MIPS (SGI), and Motorola/IBM. > : Also, you can use socket 8 processors in a slot 1 with an adapter. > > Where can I learn about this? I'm not sure. I've seen pictures of it, and the PII motherboards I've seen have instructions for installing and using the socket 8 -> slot 1 adapter. Tom From owner-freebsd-hardware Mon Sep 29 11:10:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA27196 for hardware-outgoing; Mon, 29 Sep 1997 11:10:40 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA27174; Mon, 29 Sep 1997 11:10:30 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id LAA02227; Mon, 29 Sep 1997 11:09:56 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id OAA03610; Mon, 29 Sep 1997 14:09:52 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id OAA18167; Mon, 29 Sep 1997 14:09:52 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.7/8.7.3) id NAA25663; Mon, 29 Sep 1997 13:14:04 -0500 (CDT) Date: Mon, 29 Sep 1997 13:14:04 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199709291814.NAA25663@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn To: tom@sdf.com Cc: Anthony.Kimball@East.Sun.COM, michaelv@MindBender.serv.net, freebsd-chat@freefall.freebsd.org Subject: Re: supermicro p6sns/p6sas References: <199709291505.KAA25150@compound.east.sun.com> X-Mailer: VM 6.33 under 19.14 XEmacs Lucid Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Quoth Tom on Mon, 29 September: : > And we all know that Intel has had no major Pentium or PPro bugs? : : Nothing that affected FreeBSD anyhow, and FreeBSD uses a wide variety of : features. Well, a lot of FreeBSD systems are used to perform division, for example. I'd call that a much more serious problem than occasional make world failures. More likely to kill someone, for example. But this should probably go to chat. From owner-freebsd-hardware Mon Sep 29 11:31:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28639 for hardware-outgoing; Mon, 29 Sep 1997 11:31:22 -0700 (PDT) Received: from gw1.asacomputers.com (root@gw1.asacomputers.com [204.69.220.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28634; Mon, 29 Sep 1997 11:31:19 -0700 (PDT) Received: by gw1.asacomputers.com id IAA01111; Mon, 29 Sep 1997 08:30:53 -0700 (PDT) Message-Id: <2.2.32.19970929182805.0147e094@gw1> X-Sender: rajadnya@gw1 X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 29 Sep 1997 11:28:05 -0700 To: Anthony.Kimball@East.Sun.COM From: Kedar Subject: Re: supermicro p6sns/p6sas Cc: freebsd-hardware@freefall.freebsd.org, freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The socket 8 to slot 1 adaptor is like a daughter card. The socket is located on the card that slips into the slot. Tyan has a "riser card" you can refer to. The M2020. http://www.tyan.com/html/products.html Good day, Kedar. At 10:05 AM 9/29/97 -0500, you wrote: >: Also, you can use socket 8 processors in a slot 1 with an adapter. > >Where can I learn about this? From owner-freebsd-hardware Mon Sep 29 11:36:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA29056 for hardware-outgoing; Mon, 29 Sep 1997 11:36:17 -0700 (PDT) Received: from In-Net.inba.fr (arthur.inba.fr [194.51.120.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA29050 for ; Mon, 29 Sep 1997 11:36:12 -0700 (PDT) Received: from uther.inba.fr (uther.inba.fr [194.51.120.62]) by In-Net.inba.fr (8.8.5/8.8.5) with SMTP id UAA17248 for ; Mon, 29 Sep 1997 20:40:36 +0200 (MET DST) Message-Id: <3.0.1.32.19970929203931.00921480@mail.inba.fr> X-Sender: psc@mail.inba.fr X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Demo [F] Date: Mon, 29 Sep 1997 20:39:31 +0200 To: freebsd-hardware@freebsd.org From: Philippe SCHACK Subject: Seagate TapeStor Backup Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA29052 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Is there anybody here who has make the following hardware working on FreeBSD 2.2.2 ? : Seagate TapeStor Backup drive on the floppy controller ? It uses Travan 2 or 3 tapes I tried some things like modifing the config file and add 'flag 0x1' in the controller line for the fdc0 I tried to comment and uncomment the line with 'tape ft0 at fdc0 drive 2'. Nothing wokrs. Thank's for your help. -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Vous cherchez un bien immobilier ? consultez http://www.ImmoSearch.inba.fr/ *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Philippe SCHÄCK IN'NET BORDEAUX-AQUITAINE Tél. : + 33 57.24.18.11 Chauveau - CD 239 Fax : + 33 57.24.18.28 33420 ESPIET E-mail : phschack@inba.fr *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* From owner-freebsd-hardware Mon Sep 29 12:44:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03381 for hardware-outgoing; Mon, 29 Sep 1997 12:44:13 -0700 (PDT) Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.238.120.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA03246 for ; Mon, 29 Sep 1997 12:42:16 -0700 (PDT) Received: from localhost (paulo@localhost) by mirage.nlink.com.br (8.8.5/8.8.5) with SMTP id QAA03530 for ; Mon, 29 Sep 1997 16:46:26 -0300 (EST) Date: Mon, 29 Sep 1997 16:46:25 -0300 (EST) From: Paulo Fragoso To: freebsd-hardware@FreeBSD.ORG Subject: TV Video Boards 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 Hi, I live in Brazil and I would like to install a TV Board in my FreeBSD 2.2.2 box. Here uses PAL-M in Network TV system, are there any TV/Vidoe borad that work this system in FBSD? Many Thanks, Paulo. From owner-freebsd-hardware Mon Sep 29 13:09:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA05096 for hardware-outgoing; Mon, 29 Sep 1997 13:09:26 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA05086 for ; Mon, 29 Sep 1997 13:09:23 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id NAA26393 for ; Mon, 29 Sep 1997 13:08:44 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id QAA19194; Mon, 29 Sep 1997 16:08:42 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id QAA22526; Mon, 29 Sep 1997 16:08:41 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.7/8.7.3) id PAA26054; Mon, 29 Sep 1997 15:12:58 -0500 (CDT) Date: Mon, 29 Sep 1997 15:12:58 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199709292012.PAA26054@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn To: freebsd-hardware@freefall.freebsd.org Subject: VIA-VP2 and UltraDMA X-Mailer: VM 6.33 under 19.14 XEmacs Lucid Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Will -current support UltraDMA with the VIA-VP2 chipset? VIA-VP3? From owner-freebsd-hardware Mon Sep 29 18:03:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA22194 for hardware-outgoing; Mon, 29 Sep 1997 18:03:51 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA22175 for ; Mon, 29 Sep 1997 18:03:40 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.7/8.7.3) id UAA00358; Mon, 29 Sep 1997 20:03:28 -0500 (CDT) Message-ID: <19970929200318.41520@my.domain> Date: Mon, 29 Sep 1997 20:03:18 -0500 From: Tom Jackson To: freebsd-hardware@FreeBSD.ORG Subject: Re: Problems with 16650 UARTs References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Chris Dillon on Fri, Sep 05, 1997 at 08:49:58PM -0000 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Sep 05, 1997 at 08:49:58PM -0000, Chris Dillon wrote: > > On 06-Sep-97 Andrew Gordon wrote: > >I have a card with Startech 16C650CJ UARTs which is behaving rather > >oddly. > > > >Initially, I was testing with stock 2.2.2-R, assuming that these beasts > >were 16550-compatible by default. I later tried 2.2.2-STABLE, and > >the latter with the explicit 16650 support from -current merged into > >sio.c > >(resulting in a sio.c which is the same as -current apart from some > >stuff to do with COMCONSOLE). All give the same result. > > > >The behaviour is that the ports initially work OK, and will transmit > >or receive continuously without problems, but after a short burst of > >simultaneous transmission and reception, the receiver locks up > >such that all received characters are lost silently (Tx continues to work > >OK). Closing and re-opening the device unlocks it temporarily. > >Most of my testing was at 115200, but it failed just as easily at 19200. > >The problem occurs whether or not the port is configured for RTS/CTS > >flow control. > > > >My initial test was with pppd on both ends (the other machine having > >a conventional 16550). I then wrote a trivial dumb-terminal program > >for testing (hacked to transmit 1000 copies of each character I > >typed to generate enough traffic). > > > >While this could obviously be a faulty card, the fault is identical > >on both ports (and the card has two separate 16C650CJ chips, plus > >a minimal amount of TTL for address decode) so this seems unlikely. > > > > > >Besides ideas for fixes, I would be interested in any pointers to > >16650 datasheets (Altavista offers me several companies called > >Startech that don't make UARTs, and lots of places that sell cards > >with 16650s on them, but not the manufacturer!). > > > > 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 know if this means much, but it almost ALWAYS happens when I get > my mail, as this initially made me think it was just some anomaly > between my ISP's mail server and the terminal server. It happened most > often with Netscape's POP3 client and with popclient, but almost never with > XFMail's POP3 client. > > > --- Chris Dillon > --- cdillon@tri-lakes.net > --- Powered by FreeBSD, the best free OS on the planet > ---- (http://www.freebsd.org) You know, there really should be group for fbsd'ers calling in to NT isp's:) Ever since earlier this year, I have been having problems getting reliable connections to my isp (him running nt40, me running 30current).My problems come in two varieties: (1) The connection will go dead, my ext usrSportster cd light will stay on but the isp will not respond and nothing will work. Whatever was running at the time, mail, news, you name it, will die. The connection will have to be killed and restarted. I have a ping alias to uu.net just to test the line to see if it's still active. This problem is still unsolved. (2) The carrier will drop and the connection lost. Conversing with Brian Sommers and trying just about everything. Have learned this, with nt you should disable pred1 and vjcomp compression, and have dropped the speed back to 38400. Will increase this as long as connection remains reliable. Checked the uart and modem cable with Norton's ndiags in dos; says the line is good up to 115200. Crawled under my house and soldered a phone-line splice just in case. I am really wondering about USR's Sportster. Have heard that they are really not too good; that the courier is a better choice (ofcourse if k56flex wins the 56k war, then ...) This problem seems to be improving. Like you said, probably flaky isp. Would really like to try a unix or better yet, a fbsd isp!! Tom ps Sorry to just barge in From owner-freebsd-hardware Mon Sep 29 18:19:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA22823 for hardware-outgoing; Mon, 29 Sep 1997 18:19:26 -0700 (PDT) Received: from smoke.marlboro.vt.us (smoke.marlboro.vt.us [198.206.215.91]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA22815 for ; Mon, 29 Sep 1997 18:19:17 -0700 (PDT) Received: (from cgull@localhost) by smoke.marlboro.vt.us (8.8.7/8.8.7/cgull) id UAA00499; Mon, 29 Sep 1997 20:30:38 -0400 (EDT) Date: Mon, 29 Sep 1997 20:30:38 -0400 (EDT) Message-Id: <199709300030.UAA00499@smoke.marlboro.vt.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: cgull+usenet-875579134@smoke.marlboro.vt.us (john hood) To: Anthony.Kimball@East.Sun.COM Cc: freebsd-hardware@freefall.freebsd.org Subject: VIA-VP2 and UltraDMA In-Reply-To: <199709292012.PAA26054@compound.east.sun.com> References: <199709292012.PAA26054@compound.east.sun.com> X-Mailer: VM 6.31 under Emacs 19.34.2 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tony Kimball writes: > Will -current support UltraDMA with the VIA-VP2 chipset? > VIA-VP3? It will if somebody writes and tests the code for it :) (It should work just fine in multiword DMA modes, and the difference in performance will be small for current drives.) I'd be happy to write the code, I just don't have a way to test it. If you have a system and you're willing to help some, we can probably get it going. --jh -- Mr. Belliveau said, "the difference was the wise, John Hood, cgull intelligent look on the face of the cow." He was @ *so* right. --Ofer Inbar smoke.marlboro.vt.us From owner-freebsd-hardware Mon Sep 29 18:29:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA23258 for hardware-outgoing; Mon, 29 Sep 1997 18:29:42 -0700 (PDT) Received: from jimi.danodom.com (jimi.danodom.com [205.153.247.99]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA23251 for ; Mon, 29 Sep 1997 18:29:34 -0700 (PDT) Received: (from daniel@localhost) by jimi.danodom.com (8.8.3/8.8.3) id BAA02166; Tue, 30 Sep 1997 01:28:53 GMT Date: Tue, 30 Sep 1997 01:28:53 GMT Message-Id: <199709300128.BAA02166@jimi.danodom.com> From: Dan Odom MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-hardware@freebsd.org Subject: Multiple serial ports X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am interested in using a FreeBSD box as a PPP/PAP server. I can't find any information about supported multiport serial cards. We are currently using Digiboard products (PC/Xem) under BSDI 2.1. Any ideas? -- Daniel Odom, software engineer http://www.danodom.com/ "Whatever you do will be insignificant, but it is very important that you do it." --Mahatma Gandhi From owner-freebsd-hardware Mon Sep 29 19:15:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA25479 for hardware-outgoing; Mon, 29 Sep 1997 19:15:27 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA25471 for ; Mon, 29 Sep 1997 19:15:21 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id MAA10225; Tue, 30 Sep 1997 12:14:55 +1000 (EST) Date: Tue, 30 Sep 1997 12:14:53 +1000 (EST) From: "Daniel O'Callaghan" To: Dan Odom cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Multiple serial ports In-Reply-To: <199709300128.BAA02166@jimi.danodom.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 Tue, 30 Sep 1997, Dan Odom wrote: > I am interested in using a FreeBSD box as a PPP/PAP server. I can't > find any information about supported multiport serial cards. We are > currently using Digiboard products (PC/Xem) under BSDI 2.1. Hmm, strange. You can't be looking in the right places. I'm sure there is info on the web site, and in HARDWARE.TXT in the distributions (see section 3 - LINT - other configurations). Supported cards are: Digi, Cyclades, Boca, Stallion, AST. RocketPort drivers have been committed to -current recently. I have used Cyclades, AST and a Boca-8 type called the TC-800. FreeBSD does not make use of the special port register of the TC-800, and I found that when running mpd (multilink ppp daemon) on a TC-800 the second channel was starved of interrupt servicing, presumably because mpd synchronises the data it transmits on each channel, and channel 1 was always serviced by the shared interrupt, and channel 2 not. TC-800 is fine for light use customers. AST/4 clones I have work fine with mpd under high load. Cyclades is pretty good; I use ISA version myself; the ISA driver is more reliable than the PCI, I have heard. Danny From owner-freebsd-hardware Mon Sep 29 22:51:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA04708 for hardware-outgoing; Mon, 29 Sep 1997 22:51:55 -0700 (PDT) Received: from wall.jhs.no_domain (vector.muc.ditec.de [194.120.126.35]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA04698; Mon, 29 Sep 1997 22:51:36 -0700 (PDT) Received: from flip.jhs.no_domain (localhost [127.0.0.1]) by flip.jhs.no_domain (8.8.5/8.8.5) with ESMTP id TAA24022; Sun, 28 Sep 1997 19:16:30 +0200 (MET DST) Message-Id: <199709281716.TAA24022@flip.jhs.no_domain> To: richard@pegasus.com (Richard Foulk) Cc: freebsd-hardware@freebsd.org, Mark Mayo Subject: Re: My monitor's got the Shakes... From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" X-Email: Home: Work: X-address: Holz Strasse 27d, 80469 Munich, Germany X-web: http://www.freebsd.org/~jhs/ (including PGP key) X-address: Holz Strasse 27d, 80469 Munich, Germany X-tel: Work: +49.89.607.29788 Home: +49.89.268616 X-fax: Work: +49.89.607.32158 Home: +49.89.2608126 X-data-coms: Home: ISDN +49.89.26023276 X-company: Vector Systems Ltd, Unix & Internet Consultants. X-mailer: EXMH 1.6.9 on FreeBSD (Unix) In-reply-to: Your message of "Mon, 22 Sep 1997 00:24:45 -1001." <199709221025.AAA03297@pegasus.com> Date: Sun, 28 Sep 1997 19:16:29 +0200 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Reference: > From: richard@pegasus.com (Richard Foulk) > Date: Mon, 22 Sep 1997 00:24:45 -1001 > Message-id: <199709221025.AAA03297@pegasus.com> Hi, Richard Foulk wrote: > > You might try opening it up and cleaning all the dust away with a soft > brush. Dust can make in run hot and encourage arcing. > > Don't get zapped by the high voltage. Unplug the monitor for a while > before opening it. _If_ you really must open the monitor ... Be aware some capacitors recharge on their own, without needing to be connected to a supply ! As I recall that's electrolytics, but it may apply to the tube as well, which is also a capacitor in its own right (think Leyden Jars & look in old Physics books etc :-) Look to see if the heat has cracked the discharge resistors that are usually strapped for safety across inbuilt (or even stored-in-a-drawer) high voltage capacitors. If they're cracked they should be replaced, but you must think about what voltage is on them first, even unplugged. Fiddling with the back of televisions & monitors can kill you if you get it wrong ... do a lot of thinking ... never use sweaty hands bear in mind your blood conducts a lot better than your skin ... so avoid being punctured by solder spikes ... never touch anything dubious with the inside of your hand, 'cos of tendency to reflex grip it, if you must touch, use outside of hand, dont even think of touching the HT section, & the big thick cable out of the side of the monitor. DC will electrocute you better than AC from the outlet, High voltages obviously more so too :-) ... best way to kill yourself ? .. current up one arm, throught the heart ... down the other arm ... try to avoid that scenario: Think rubber mats & shoes, have wooden sticks to prod with, not screwdrivers, keep one hand behind your back (not leaning on the table) If in doubt ... don't ! don't even think of it ! PS I spent a minute or 2 in the High Voltage lab at Leeds University years ago scared in the extreme ... in pitch dark, with about half a MegV or something ridiculous in the room, powered up .. some idiot's idea of a prank, I've also worked on the back of live colour TVs ... neither experiences are ones to relish ... I love 5V TTL & the feeling I'll blow the CPU, not me :-) "Take care" seems the best form of parting salutation ;-) Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-hardware Mon Sep 29 23:05:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA05160 for hardware-outgoing; Mon, 29 Sep 1997 23:05:54 -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 XAA05149 for ; Mon, 29 Sep 1997 23:05:43 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id CAA24770; Tue, 30 Sep 1997 02:08:26 -0400 (EDT) Date: Tue, 30 Sep 1997 02:08:26 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709300608.CAA24770@sabre.goldsword.com> To: freebsd-hardware@freefall.freebsd.org Subject: Re: supermicro p6sns/p6sas Cc: jfarmer@goldsword.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 28 Sep 1997 19:58:04 -0700 (PDT) Tom said: [stuff deleted] > Why is it clear that socket 7 has superior life expentency to socket 8? >Socket 8 is better (better bandwidth) than socket 7, so why doesn't AMD >just make socket 8 processors rather than messing around trying to sqeeze >more out of socket 7? I agree with Michael. AMD/Cyrix is targetting the >secondary market, otherwise they'd be cranking out processors to use with >the faster socket 8. > > Also, you can use socket 8 processors in a slot 1 with an adapter. >I have no idea why AMD isn't exploiting this to put CPUs onto slot 1 >motherboards now. The reason for AMD & Cyrix _not_ making a slot-1 is the same reason that they don't make socket-8 cpu's, namely, patents. Intel holds patents on both socket-8 and slot-1. Want to bet that they have/will have a patent on the slot-2 architecture also? Ah, for the days when socket formats/designs were open, set by industry coalitions or organizations. When manufactours designed a "closed" socket & watched their design-in wins drop... 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 Mon Sep 29 23:50:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07192 for hardware-outgoing; Mon, 29 Sep 1997 23:50:10 -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 XAA07187 for ; Mon, 29 Sep 1997 23:50:06 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xFw7f-0001QA-00; Mon, 29 Sep 1997 23:49:31 -0700 Date: Mon, 29 Sep 1997 23:49:28 -0700 (PDT) From: Tom To: "John T. Farmer" cc: freebsd-hardware@freefall.freebsd.org, jfarmer@goldsword.com Subject: Re: supermicro p6sns/p6sas In-Reply-To: <199709300608.CAA24770@sabre.goldsword.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 Tue, 30 Sep 1997, John T. Farmer wrote: > The reason for AMD & Cyrix _not_ making a slot-1 is the same reason that > they don't make socket-8 cpu's, namely, patents. Intel holds patents > on both socket-8 and slot-1. Want to bet that they have/will have a > patent on the slot-2 architecture also? Which is probably what everyone has been doing already. What kind of socket does the Alpha 21164 use? How about the PowerPC 750? How about the UltraSparc? How about the R10000? How many of these socket types are patented? > Ah, for the days when socket formats/designs were open, set by industry > coalitions or organizations. When manufactours designed a "closed" > socket & watched their design-in wins drop... Huh? For CPU sockets? Manufactures always just built what they need. Besides CPU design has changed a lot. I agree with Intel's motivation to go to a SEC. It provides a package which is easier to cool for a start. Is there a "standard" SEC style design that Intel could have used instead of coming up with slot 1? > 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 Tue Sep 30 00:36:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA09845 for hardware-outgoing; Tue, 30 Sep 1997 00:36:46 -0700 (PDT) Received: from 586quick166.saturn-tech.com ([207.229.19.32]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA09837 for ; Tue, 30 Sep 1997 00:36:42 -0700 (PDT) Received: from localhost (drussell@localhost) by 586quick166.saturn-tech.com (8.8.7/8.8.4) with SMTP id BAA03945; Tue, 30 Sep 1997 01:35:41 -0600 (MDT) X-Authentication-Warning: 586quick166.saturn-tech.com: drussell owned process doing -bs Date: Tue, 30 Sep 1997 01:35:40 -0600 (MDT) From: Doug Russell To: Tom cc: "John T. Farmer" , freebsd-hardware@freefall.freebsd.org, jfarmer@goldsword.com Subject: Re: supermicro p6sns/p6sas 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 Mon, 29 Sep 1997, Tom wrote: > Huh? For CPU sockets? Manufactures always just built what they need. > Besides CPU design has changed a lot. I agree with Intel's motivation to > go to a SEC. It provides a package which is easier to cool for a start. > Is there a "standard" SEC style design that Intel could have used instead > of coming up with slot 1? They could have made it available for use by others, but instead they patented it to make it more difficult for the competition. Of course, the competition would probably do the same thing in their place, but... :) Of course, there is always the risk of a backfire. Come up with a better design than Intel's, patent IT, and only give the rights to your non-Intel buddies. :) Later...... go Non-Intels! :) From owner-freebsd-hardware Tue Sep 30 04:56:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA21418 for hardware-outgoing; Tue, 30 Sep 1997 04:56:23 -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 EAA21413 for ; Tue, 30 Sep 1997 04:56:21 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id HAA25232; Tue, 30 Sep 1997 07:57:12 -0400 (EDT) Date: Tue, 30 Sep 1997 07:57:12 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709301157.HAA25232@sabre.goldsword.com> To: darrylo@sr.hp.com, hardware@FreeBSD.ORG Subject: Re: K6 Update & AMD Statement Cc: jfarmer@goldsword.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Sep 1997 10:49:32 -0700 Darryl Okahata said: >"John T. Farmer" wrote: >> On Sat, 27 Sep 1997 18:04:53 +0200 Poul-Henning Kamp said: >> >I have a K6/233 here which has by now completed 50 or more make worlds, >> >no complaints. >> > >> >It is marked: >> > AMD-K6-233ANR >> > 3.2V CORE / 3.3V I/O >> > B 9731EJBW >> ^^^^^^^^ >> >> This is what I'm told is the important part. The stepping must be 9731 or >> later. > > This looks like a date code (when the IC was manufactured), and not >a stepping. If it is a date code, "9731" would be the 31st week of >1997, which is the last week in July. > Actually, it is a date code, not a "standard" stepping code. My understanding (Always suspect!) is that AMD made the correction as a running change in production without a specific stepping assigned to it. It would have been easiler to id the desired chips if they had, but at least they _did_ "step up to the plate" and admit to the problem _and_ fix it when it was brought to their attention... 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 Tue Sep 30 05:55:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA23781 for hardware-outgoing; Tue, 30 Sep 1997 05:55:07 -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 FAA23776 for ; Tue, 30 Sep 1997 05:55:02 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id IAA25348; Tue, 30 Sep 1997 08:57:49 -0400 (EDT) Date: Tue, 30 Sep 1997 08:57:49 -0400 (EDT) From: "John T. Farmer" Message-Id: <199709301257.IAA25348@sabre.goldsword.com> To: tom@sdf.com Subject: Re: supermicro p6sns/p6sas Cc: freebsd-hardware@freefall.freebsd.org, jfarmer@goldsword.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Sep 1997 23:49:28 -0700 (PDT) Tom said: >On Tue, 30 Sep 1997, John T. Farmer wrote: > >> The reason for AMD & Cyrix _not_ making a slot-1 is the same reason that >> they don't make socket-8 cpu's, namely, patents. Intel holds patents >> on both socket-8 and slot-1. Want to bet that they have/will have a >> patent on the slot-2 architecture also? > > Which is probably what everyone has been doing already. What kind of >socket does the Alpha 21164 use? How about the PowerPC 750? How about >the UltraSparc? How about the R10000? How many of these socket types are >patented? That I don't know off the top of my head. I suspect that you're correct & they all are using patented sockets. >> Ah, for the days when socket formats/designs were open, set by industry >> coalitions or organizations. When manufactours designed a "closed" >> socket & watched their design-in wins drop... > > Huh? For CPU sockets? Manufactures always just built what they need. >Besides CPU design has changed a lot. I agree with Intel's motivation to >go to a SEC. It provides a package which is easier to cool for a start. >Is there a "standard" SEC style design that Intel could have used instead >of coming up with slot 1? Well actually, no. Digging, you find that the SOJ & pin-grid sockets originally used were either standard (JEDEC, etc.) or were "opened" by the original vendor in hopes of winning more design-ins. Most chip (& cpu's qualifies as chips) vendors that went their own way in socket formats disappeared or rapidly changed their tune. Look at markets for embedded microprocessors, for example. The cpu market there is a "commodity market" with high volume users going to SMT components & almost everybody else going with more standard chip carriers. Intel _does_not_ want the PC/workstation/desktop, etc. market to turn into a commodity market, which is what the socket-7 market has turned into. Intel does want fat profit margins, not tiny ones. They are not the first to do this, even in the computer biz. Read up on IBM and the PCM vendors (Plug-Compatible Manufacturer) during the late '60's and '70's. It took many lawsuits and megadollars of marketing & support for the PCM's to complete. What made the most difference though was the paradigm shift to the distributed PC & network environment. As to Intel's reasoning for going to the Slot-1 SEC format, I agree there're _alot_ of good technical reasons for it. There're also alot of marketing/legal issues for it. John (Who spent too much time reading Electronics & other rags in the 70's & early 80's) ------------------------------------------------------------------------- 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 Tue Sep 30 08:53:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03056 for hardware-outgoing; Tue, 30 Sep 1997 08:53:58 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA03025; Tue, 30 Sep 1997 08:53:46 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id IAA01973; Tue, 30 Sep 1997 08:53:23 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id LAA28972; Tue, 30 Sep 1997 11:53:10 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id LAA12163; Tue, 30 Sep 1997 11:53:10 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.7/8.7.3) id KAA29056; Tue, 30 Sep 1997 10:57:42 -0500 (CDT) Date: Tue, 30 Sep 1997 10:57:42 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199709301557.KAA29056@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn To: jfarmer@sabre.goldsword.com Cc: freebsd-chat@freefall.freebsd.org Subject: Re: supermicro p6sns/p6sas References: <199709301257.IAA25348@sabre.goldsword.com> X-Mailer: VM 6.33 under 19.14 XEmacs Lucid Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Quoth John T. Farmer on Tue, 30 September: : : That I don't know off the top of my head. I suspect that you're : correct & they all are using patented sockets. [moved to chat] The fault for that would lie squarely on the shoulders of the patent office. Obviousness is *supposed* to be a prima facie criterion for denial of patent. From owner-freebsd-hardware Tue Sep 30 11:03:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA10425 for hardware-outgoing; Tue, 30 Sep 1997 11:03:12 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA10420 for ; Tue, 30 Sep 1997 11:03:03 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.7/8.7.3) id MAA17795; Tue, 30 Sep 1997 12:52:51 -0500 (CDT) Message-ID: <19970930125250.01095@my.domain> Date: Tue, 30 Sep 1997 12:52:50 -0500 From: Tom Jackson To: freebsd-hardware@FreeBSD.ORG Subject: Re: Opinions please Was: Micropolis Runs Too HOT! References: <199709132341.NAA23393@pegasus.com> <19970920131634.08085@my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19970920131634.08085@my.domain>; from Tom Jackson on Sat, Sep 20, 1997 at 01:16:34PM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Sep 20, 1997 at 01:16:34PM -0500, Tom Jackson wrote: > In my previous post I disCussed the heating situation with this 7200rpm scsi > Micropolis drive. I now have two 4-1/2in cooling fans on the midi case, one > blowing over the Mic located in two 5-1/4 in bays and one sucking out at the > back of the case. Although I have return approval for a Fujitsu M2954S, many > claim it will run just hot as the Micropolis. I have run iozone on all of my > drives trying to decide if I should exchange. Although the Mic seems to write > at a good rate the read specs don't look good at all. Would anyone with good > knowledge of this please comment. I need to decide soon. > > iozone single results: > --------------------------------------------------------- > In the three runs, done separately, the disk cache sized to 11 megabytes. > sd0 is a Micropolis 4421 2.1gb 5400rpm scsi, sd1 is a Micropolis 4345 4.5gb > 7200rpm scsi, and sd2 is a Fujitsu M1606sau 1.08gb 5400rpm scsi. > > IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94) > By Bill Norcott > > Operating System: FreeBSD 2.x -- using fsync() > > Send comments to: b_norcott@xway.com > > IOZONE writes a 44 Megabyte sequential file consisting of > 5632 records which are each 8192 bytes in length. > It then reads the file. It prints the bytes-per-second > rate at which the computer can read and write files. > > > Writing the 44 Megabyte file, '/usr/ports/iozone.tmp'...11.265625 seconds > Reading the file...7.914062 seconds on sd0 > > IOZONE performance measurements: > 4095409 bytes/second for writing the file > 5829792 bytes/second for reading the file > <--- > > Writing the 44 Megabyte file, '/usr/iozone.tmp'...6.625000 seconds > Reading the file...6.257812 seconds on sd1 > > IOZONE performance measurements: > 6964127 bytes/second for writing the file > 7372759 bytes/second for reading the file > <--- > > Writing the 44 Megabyte file, '/mnt1/iozone.tmp'...6.335938 seconds > Reading the file...5.953125 seconds on sd2 > > IOZONE performance measurements: > 7281849 bytes/second for writing the file > 7750105 bytes/second for reading the file > ----------------------------------------------------------- > iozone concurrent results: > > Concurrent run to all three drives. Disk cache sized itself to 11mb. > > IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94) > By Bill Norcott > > Operating System: FreeBSD 2.x -- using fsync() > > Send comments to: b_norcott@xway.com > > IOZONE writes a 44 Megabyte sequential file consisting of > 5632 records which are each 8192 bytes in length. > It then reads the file. It prints the bytes-per-second > rate at which the computer can read and write files. > > > Writing the 44 Megabyte file, '/usr/ports/iozone.tmp'...11.250000 seconds > Reading the file...7.453125 seconds on sd0 (MC4421) > > IOZONE performance measurements: > 4101097 bytes/second for writing the file > 6190335 bytes/second for reading the file > <--- > > Writing the 44 Megabyte file, '/usr/iozone.tmp'...6.585938 seconds > Reading the file...6.304688 seconds on sd1 (MC4345NS) > > IOZONE performance measurements: > 7005433 bytes/second for writing the file > 7317943 bytes/second for reading the file > <--- > > Writing the 44 Megabyte file, '/mnt1/iozone.tmp'...6.359375 seconds > Reading the file...5.867188 seconds on sd2 (Fuj M1606S) > > IOZONE performance measurements: > 7255012 bytes/second for writing the file > 7863621 bytes/second for reading the file > > > I can't tell if this bad performance or the disk might be damaged > > Tom > --- > > Well no one commented but I did exchange the drive for a Fujitsu M2954S. Here's the iozone for it: Writing the 44 Megabyte file, '/usr/iozone.tmp'...6.078125 seconds Reading the file...7.281250 seconds IOZONE performance measurements: for sd1 (Fujitsu M2954S) 7590719 bytes/second for writing the file 6336459 bytes/second for reading the file As you can see, much much better! Boy am I glad I swapped. Tom From owner-freebsd-hardware Tue Sep 30 11:42:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA12780 for hardware-outgoing; Tue, 30 Sep 1997 11:42:37 -0700 (PDT) Received: from jimi.danodom.com (jimi.danodom.com [205.153.247.99]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA12775 for ; Tue, 30 Sep 1997 11:42:31 -0700 (PDT) Received: (from daniel@localhost) by jimi.danodom.com (8.8.3/8.8.3) id SAA03454; Tue, 30 Sep 1997 18:41:21 GMT Date: Tue, 30 Sep 1997 18:41:21 GMT Message-Id: <199709301841.SAA03454@jimi.danodom.com> From: Dan Odom MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Daniel O'Callaghan" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Multiple serial ports In-Reply-To: References: <199709300128.BAA02166@jimi.danodom.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well, I've checked the handbook, if that's what you mean. Most of what it lists is out of production or non-intelligent and very expensive (for example, the Digi 570/i cards that it lists cost a LOT compared to more modern cards -- $528 for a 2-port, or about $265 per modem, while the Xem 32-port only costs about $1,300, or about $40.00 per modem). The Boca cards all say "does not support modems," my supplier has never heard of ARNET, AST, SDL, or Cyclades (and neither have I -- isn't ARNET a large ISP and AST a manufacturer of cheap PC clones?). When I search the archives for information about using Digiboards, all I find are comments about what a pain it is and how nobody can figure it out. Most generic multi-port serial cards out there are plug and play, ruling them out for FreeBSD. Speaking of plug and play, I am having an impossible time finding hardware for my FreeBSD and BSDI boxes. Nothing out there has jumpers any more, not even network cards. Where the heck does everyone find supplies in this era of Windows NT? Daniel O'Callaghan writes: > > On Tue, 30 Sep 1997, Dan Odom wrote: > > > I am interested in using a FreeBSD box as a PPP/PAP server. I can't > > find any information about supported multiport serial cards. We are > > currently using Digiboard products (PC/Xem) under BSDI 2.1. > > Hmm, strange. You can't be looking in the right places. I'm sure there > is info on the web site, and in HARDWARE.TXT in the distributions (see > section 3 - LINT - other configurations). > > Supported cards are: Digi, Cyclades, Boca, Stallion, AST. RocketPort > drivers have been committed to -current recently. > I have used Cyclades, AST and a Boca-8 type called the TC-800. FreeBSD > does not make use of the special port register of the TC-800, and I found > that when running mpd (multilink ppp daemon) on a TC-800 the second > channel was starved of interrupt servicing, presumably because mpd > synchronises the data it transmits on each channel, and channel 1 was > always serviced by the shared interrupt, and channel 2 not. TC-800 is > fine for light use customers. > > AST/4 clones I have work fine with mpd under high load. > Cyclades is pretty good; I use ISA version myself; the ISA driver is more > reliable than the PCI, I have heard. > > Danny From owner-freebsd-hardware Tue Sep 30 13:03:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA18194 for hardware-outgoing; Tue, 30 Sep 1997 13:03:14 -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 NAA18172 for ; Tue, 30 Sep 1997 13:03:09 -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 XAA01963; Tue, 30 Sep 1997 23:02:21 +0300 (EEST) Date: Tue, 30 Sep 1997 23:02:21 +0300 (EEST) From: Narvi To: Tom cc: "John T. Farmer" , freebsd-hardware@freefall.freebsd.org, jfarmer@goldsword.com Subject: Re: supermicro p6sns/p6sas 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 Mon, 29 Sep 1997, Tom wrote: > > On Tue, 30 Sep 1997, John T. Farmer wrote: > > > The reason for AMD & Cyrix _not_ making a slot-1 is the same reason that > > they don't make socket-8 cpu's, namely, patents. Intel holds patents > > on both socket-8 and slot-1. Want to bet that they have/will have a > > patent on the slot-2 architecture also? > > Which is probably what everyone has been doing already. What kind of > socket does the Alpha 21164 use? How about the PowerPC 750? How about > the UltraSparc? How about the R10000? How many of these socket types are > patented? There is no such thing as powerpc socket. The pinout (well, in most cases, ballout, PPC uses mostly BGA) is freely available. It is mostly your business how you stick it to the motherboard is mostly your business, I don't think there is one standard between any of the PPC motherboard makers for the processor daughtercard. Sander There is no love, no good, no happiness and no future - all these are just illusions. > > > Ah, for the days when socket formats/designs were open, set by industry > > coalitions or organizations. When manufactours designed a "closed" > > socket & watched their design-in wins drop... > > Huh? For CPU sockets? Manufactures always just built what they need. > Besides CPU design has changed a lot. I agree with Intel's motivation to > go to a SEC. It provides a package which is easier to cool for a start. > Is there a "standard" SEC style design that Intel could have used instead > of coming up with slot 1? > > > 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 Tue Sep 30 13:26:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA19895 for hardware-outgoing; Tue, 30 Sep 1997 13:26:36 -0700 (PDT) Received: from In-Net.inba.fr (arthur.inba.fr [194.51.120.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA19887 for ; Tue, 30 Sep 1997 13:26:30 -0700 (PDT) Received: from uther.inba.fr (uther.inba.fr [194.51.120.62]) by In-Net.inba.fr (8.8.5/8.8.5) with SMTP id WAA21437 for ; Tue, 30 Sep 1997 22:31:11 +0200 (MET DST) Message-Id: <3.0.1.32.19970930222955.0098bb30@mail.inba.fr> X-Sender: psc@mail.inba.fr X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Demo [F] Date: Tue, 30 Sep 1997 22:29:55 +0200 To: freebsd-hardware@freebsd.org From: Philippe SCHACK Subject: Seagate TapeStor Backup Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA19891 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Excuse me, but I send this message one again because I was not in this and I though I was. If someone has always send an answer to this message, can he send it to my personnal address. Thank's again. Now I am in this list. Begin of the message ------------ Is there anybody here who has make the following hardware working on FreeBSD 2.2.2 ? : Seagate TapeStor Backup drive on the floppy controller ? It uses Travan 2 or 3 tapes I tried some things like modifing the config file and add 'flag 0x1' in the controller line for the fdc0 I tried to comment and uncomment the line with 'tape ft0 at fdc0 drive 2'. Nothing wokrs. Thank's for your help. -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Vous cherchez un bien immobilier ? consultez http://www.ImmoSearch.inba.fr/ *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Philippe SCHÄCK IN'NET BORDEAUX-AQUITAINE Tél. : + 33 57.24.18.11 Chauveau - CD 239 Fax : + 33 57.24.18.28 33420 ESPIET E-mail : phschack@inba.fr *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* From owner-freebsd-hardware Tue Sep 30 13:45:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA20969 for hardware-outgoing; Tue, 30 Sep 1997 13:45:42 -0700 (PDT) Received: from jimi.danodom.com (jimi.danodom.com [205.153.247.99]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA20955 for ; Tue, 30 Sep 1997 13:45:20 -0700 (PDT) Received: (from daniel@localhost) by jimi.danodom.com (8.8.3/8.8.3) id UAA03689; Tue, 30 Sep 1997 20:44:03 GMT Date: Tue, 30 Sep 1997 20:44:03 GMT Message-Id: <199709302044.UAA03689@jimi.danodom.com> From: Dan Odom MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Randy Berndt Cc: freebsd-hardware@freebsd.org Subject: Re: Multiple serial ports In-Reply-To: <3.0.3.32.19970930150358.00732b2c@nething.com> References: <199709300128.BAA02166@jimi.danodom.com> <199709301841.SAA03454@jimi.danodom.com> <3.0.3.32.19970930150358.00732b2c@nething.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Randy Berndt writes: > At 06:41 PM 9/30/97 GMT, you wrote: > >The Boca cards all say "does not support modems," > > Actually, the Boca-4 and Boca-8 do not support modems. The Boca-6 (never > seen one) and the Boca-16 DO support modems. The -16 uses a weird 10-pin > RJ-45 connection (cables available from Boca). I do not use modems on them, > but I have them null modem-ed to a mini-computer that thinks they are > modems, and everything seems to work ok. > > One BIG warning: The higher ports tend to lock up (even when all are at > 9600 baud). I ended up putting in two -16s and just using the bottom 8. I > think (emphasize THINK) the problem is buffer overflows on the upper ports. > I have patched the kernel to set the 16550 trigger to 8 from 14 to allow > more time, but have not yet hooked up the higher ports again. > > As always, your mileage may vary :) > > Randy Berndt > ---------------------------------- > AOS/VS, Win95, FreeBSD, WinNT, DOS, Win311: > I'm caught in a twisty little maze of operating systems, all different. From owner-freebsd-hardware Tue Sep 30 13:45:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA20993 for hardware-outgoing; Tue, 30 Sep 1997 13:45:47 -0700 (PDT) Received: from jimi.danodom.com (jimi.danodom.com [205.153.247.99]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA20975 for ; Tue, 30 Sep 1997 13:45:42 -0700 (PDT) Received: (from daniel@localhost) by jimi.danodom.com (8.8.3/8.8.3) id UAA03692; Tue, 30 Sep 1997 20:44:44 GMT Date: Tue, 30 Sep 1997 20:44:44 GMT Message-Id: <199709302044.UAA03692@jimi.danodom.com> From: Dan Odom MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Randy Berndt Cc: freebsd-hardware@freebsd.org Subject: Re: Multiple serial ports In-Reply-To: <3.0.3.32.19970930150358.00732b2c@nething.com> References: <199709300128.BAA02166@jimi.danodom.com> <199709301841.SAA03454@jimi.danodom.com> <3.0.3.32.19970930150358.00732b2c@nething.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for your help guys, you've been great. I think, however, that I'll spend the extra $500 or so and just buy a terminal server. It's easier. :-) Randy Berndt writes: > At 06:41 PM 9/30/97 GMT, you wrote: > >The Boca cards all say "does not support modems," > > Actually, the Boca-4 and Boca-8 do not support modems. The Boca-6 (never > seen one) and the Boca-16 DO support modems. The -16 uses a weird 10-pin > RJ-45 connection (cables available from Boca). I do not use modems on them, > but I have them null modem-ed to a mini-computer that thinks they are > modems, and everything seems to work ok. > > One BIG warning: The higher ports tend to lock up (even when all are at > 9600 baud). I ended up putting in two -16s and just using the bottom 8. I > think (emphasize THINK) the problem is buffer overflows on the upper ports. > I have patched the kernel to set the 16550 trigger to 8 from 14 to allow > more time, but have not yet hooked up the higher ports again. > > As always, your mileage may vary :) > > Randy Berndt > ---------------------------------- > AOS/VS, Win95, FreeBSD, WinNT, DOS, Win311: > I'm caught in a twisty little maze of operating systems, all different. -- Daniel Odom, software engineer http://www.danodom.com/ "Whatever you do will be insignificant, but it is very important that you do it." --Mahatma Gandhi From owner-freebsd-hardware Tue Sep 30 13:58:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA21695 for hardware-outgoing; Tue, 30 Sep 1997 13:58:57 -0700 (PDT) Received: from merit.edu (merit.edu [198.108.1.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA21687 for ; Tue, 30 Sep 1997 13:58:52 -0700 (PDT) Received: from ohm.merit.edu (ohm.merit.edu [198.108.60.65]) by merit.edu (8.8.7/8.8.5) with ESMTP id QAA06292 for ; Tue, 30 Sep 1997 16:58:49 -0400 (EDT) From: William Bulley Received: (web@localhost) by ohm.merit.edu (8.6.9/8.6.5) id QAA15156 for freebsd-hardware@FreeBSD.ORG; Tue, 30 Sep 1997 16:58:50 -0400 Message-Id: <199709302058.QAA15156@ohm.merit.edu> Subject: old versus new IBM PC keyboards To: freebsd-hardware@FreeBSD.ORG Date: Tue, 30 Sep 1997 16:58:50 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] 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 Please bear with me on this one: :-) I have several perfectly functional original IBM PC keyboards which are pre-AT (even pre-XT for that matter) which I would dearly like to use with some modern PC clone motherboards. I have had people tell me to buy a new keyboard. I have read in the various PC hardware FAQs that the interface is different. I really hate to buy new (el cheapo) keyboards when I know these older stalwarts work just fine (with their older style computers). Has anyone ever faced this issue? It seems like a terrible waste to throw away perfectly useable hardware. Besides, I really, really like the touch and feel of these older keyboards. There were built extremely well. :-) Since they (directly) plug into the large five pin DIN connectors which come standard on many (all?) PC clone motherboards, it is very tempting to try one of these with one of those motherboards. But I know it is doomed to failure... :-( Does any BIOS vendor support this old style keyboard or is it baked into firmware (or gate array logic) on the various support chip sets? Any ideas at all, besides: 1) toss the keyboard, 2) write your own BIOS keyboard support? Thanks. Regards, web... -- William Bulley, N8NXN Senior Systems Research Programmer Merit Network, Inc. Email: web@merit.edu 4251 Plymouth Road, Suite C Phone: (313) 764-9993 Ann Arbor, Michigan 48105-2785 Fax: (313) 647-3185 [ What's all this fuss over the end of the century and mission critial ] [ programs failing due to dates? If people simply started using Roman ] [ Numerials, the problem goes away! MCM = 1900 MIM = 1999 MM = 2000 ] From owner-freebsd-hardware Tue Sep 30 14:30:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA23173 for hardware-outgoing; Tue, 30 Sep 1997 14:30:13 -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 OAA23100 for ; Tue, 30 Sep 1997 14:28:57 -0700 (PDT) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id LAA29237; Tue, 30 Sep 1997 11:27:38 -1000 Date: Tue, 30 Sep 1997 11:27:38 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199709302127.LAA29237@pegasus.com> In-Reply-To: Dan Odom "Re: Multiple serial ports" (Sep 30, 8:44pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Dan Odom Subject: Re: Multiple serial ports Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk } } Thanks for your help guys, you've been great. I think, however, } that I'll spend the extra $500 or so and just buy a terminal server. } It's easier. :-) Yikes. I doubt you'll find a decent terminal server for that cheap. Try four times that. Richard From owner-freebsd-hardware Tue Sep 30 15:52:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA28360 for hardware-outgoing; Tue, 30 Sep 1997 15:52:20 -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 PAA28346 for ; Tue, 30 Sep 1997 15:52:12 -0700 (PDT) Received: (from arg@localhost) by arg1.demon.co.uk (8.8.5/8.8.5) id XAA20619; Tue, 30 Sep 1997 23:51:34 +0100 (BST) Date: Tue, 30 Sep 1997 23:51:33 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Dan Odom cc: freebsd-hardware@freebsd.org Subject: Re: Multiple serial ports In-Reply-To: <199709301841.SAA03454@jimi.danodom.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 Tue, 30 Sep 1997, Dan Odom wrote: > Speaking of plug and play, I am having an impossible time finding > hardware for my FreeBSD and BSDI boxes. Nothing out there has jumpers > any more, not even network cards. Where the heck does everyone find > supplies in this era of Windows NT? Just because they have no jumpers, that doesn't mean you are forced to use PnP. Certainly most ISA Ethernet cards can be configured by EEPROM to reside at a fixed address rather than being PnP (usually by use of a DOS utility). In some cases, this option is not clearly documented (SMC EtherEZ for example - there is a command-line option to the EZSETUP program to disable PnP, but if you go into the menu-driven version you don't get that option). Sound cards are the one category where PnP has become almost mandatory. BTW, note that Windows NT 4.0 doesn't do PnP either - perhaps you meant "this era of Windows 95" in the above? From owner-freebsd-hardware Tue Sep 30 17:15:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA02554 for hardware-outgoing; Tue, 30 Sep 1997 17:15:55 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA02545 for ; Tue, 30 Sep 1997 17:15:49 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id JAA02478; Wed, 1 Oct 1997 09:41:17 +0930 (CST) Message-Id: <199710010011.JAA02478@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: William Bulley cc: freebsd-hardware@FreeBSD.ORG Subject: Re: old versus new IBM PC keyboards In-reply-to: Your message of "Tue, 30 Sep 1997 16:58:50 -0400." <199709302058.QAA15156@ohm.merit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 09:41:13 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have several perfectly functional original IBM PC keyboards > which are pre-AT (even pre-XT for that matter) which I would > dearly like to use with some modern PC clone motherboards. Oh dear. > I have had people tell me to buy a new keyboard. I have read > in the various PC hardware FAQs that the interface is different. > I really hate to buy new (el cheapo) keyboards when I know these > older stalwarts work just fine (with their older style computers). That's where they should be used. > Does any BIOS vendor support this old style keyboard or is it baked > into firmware (or gate array logic) on the various support chip sets? The communications protocol used by original PC keyboard is sufficiently incompatible with that used by the PC/AT keyboard that you have no significant hope of using the former with a modern system. > Any ideas at all, besides: 1) toss the keyboard, 2) write your own > BIOS keyboard support? Thanks. Go looking for any of the AT-compatible clones built using the same mechanism. You should also investigate a secondhand PC/AT keyboard, or a genuine PS/2 keyboard, both of which are similiarly constructed and compatible with modern hardware. mike From owner-freebsd-hardware Tue Sep 30 17:18:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA02730 for hardware-outgoing; Tue, 30 Sep 1997 17:18:32 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA02716 for ; Tue, 30 Sep 1997 17:18:27 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id JAA02515; Wed, 1 Oct 1997 09:45:38 +0930 (CST) Message-Id: <199710010015.JAA02515@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Philippe SCHACK cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Seagate TapeStor Backup In-reply-to: Your message of "Tue, 30 Sep 1997 22:29:55 +0200." <3.0.1.32.19970930222955.0098bb30@mail.inba.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Wed, 01 Oct 1997 09:45:35 +0930 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA02723 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is there anybody here who has make the following hardware working on > FreeBSD 2.2.2 ? : > > Seagate TapeStor Backup drive on the floppy controller ? > It uses Travan 2 or 3 tapes No. The floppytape support is very limited, and large, bogus devices like the Travan floppytapes are definitely not supported. If you want a serious backup device, SCSI is the only way to go at the moment. mike From owner-freebsd-hardware Tue Sep 30 18:00:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA05373 for hardware-outgoing; Tue, 30 Sep 1997 18:00:09 -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 SAA05361 for ; Tue, 30 Sep 1997 18:00:04 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xGD7p-0001p2-00; Tue, 30 Sep 1997 17:58:49 -0700 Date: Tue, 30 Sep 1997 17:58:42 -0700 (PDT) From: Tom To: Dan Odom cc: "Daniel O'Callaghan" , freebsd-hardware@freebsd.org Subject: Re: Multiple serial ports In-Reply-To: <199709301841.SAA03454@jimi.danodom.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 Tue, 30 Sep 1997, Dan Odom wrote: > Speaking of plug and play, I am having an impossible time finding > hardware for my FreeBSD and BSDI boxes. Nothing out there has jumpers > any more, not even network cards. Where the heck does everyone find > supplies in this era of Windows NT? Use PCI cards for everything. I don't know of any PCI sound cards, but the sound code can setup some PnP cards. Tom From owner-freebsd-hardware Tue Sep 30 23:46:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22846 for hardware-outgoing; Tue, 30 Sep 1997 23:46:07 -0700 (PDT) Received: from cockatiel.aus.org (hendrix77@cockatiel.aus.org [199.166.246.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA22833 for ; Tue, 30 Sep 1997 23:45:56 -0700 (PDT) Received: from localhost (hendrix77@localhost) by cockatiel.aus.org (8.8.6/8.8.5) with SMTP id CAA00212; Wed, 1 Oct 1997 02:44:05 -0400 (EDT) Date: Wed, 1 Oct 1997 02:44:01 -0400 (EDT) From: "hendrix77@" To: Andrew Gordon cc: Dan Odom , freebsd-hardware@FreeBSD.ORG Subject: Re: Multiple serial ports 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 Tue, 30 Sep 1997, Andrew Gordon wrote: > > Speaking of plug and play, I am having an impossible time finding > > hardware for my FreeBSD and BSDI boxes. Nothing out there has jumpers > > any more, not even network cards. Where the heck does everyone find > > supplies in this era of Windows NT? > > Just because they have no jumpers, that doesn't mean you are forced > to use PnP. Certainly most ISA Ethernet cards can be configured by EEPROM > to reside at a fixed address rather than being PnP (usually by use of > a DOS utility). In some cases, this option is not clearly documented > (SMC EtherEZ for example - there is a command-line option to the > EZSETUP program to disable PnP, but if you go into the menu-driven > version you don't get that option). > We are home users of FreeBSD, we dont have windows 3.1 or 95 and find it annoying about cards that have no jumpers, I suppose we ideally should be harassing the hardware vendors for drivers. But it genuinely sucks that we went out and bought a SB16 compa tible soundcard and had to scrap it for a real SB or buy OSS to make it run since we dont have windows to run PnP config programs. I wonder is there no way to interface the pnp bios to do stuff or do you have to write code for each individual pnp card/dev ice ? Luke ` From owner-freebsd-hardware Wed Oct 1 00:18:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA24545 for hardware-outgoing; Wed, 1 Oct 1997 00:18:59 -0700 (PDT) Received: from tower.my.domain (nscs21p1.remote.umass.edu [128.119.179.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA24535; Wed, 1 Oct 1997 00:18:52 -0700 (PDT) Received: from tower.my.domain (localhost [127.0.0.1]) by tower.my.domain (8.8.7/8.8.7) with ESMTP id CAA00340; Wed, 1 Oct 1997 02:35:00 -0400 (EDT) Date: Wed, 1 Oct 1997 02:35:00 -0400 (EDT) From: User Gp Message-Id: <199710010635.CAA00340@tower.my.domain> X-Mailer: exmh version 2.0zeta 7/24/97 To: questions@FreeBSD.ORG cc: hardware@FreeBSD.ORG Subject: ppbus problem Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mime Version: 1.0 Content Type: Text Plain Date: Wed, 01 Oct 1997 02:35:00 -0400 From: User Gp I 'm trying to install the ppbus stuff for my parallel port zip drive. The kernel compiled OK, and it has a lot to say about the drive, but fdisk and mount produce no results. Here's dmesg. Any ideas. Thanks. Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Wed Oct 1 01:55:48 EDT 1997 gp@tower.my.domain:/usr/src/sys/compile/GPKERNEL CPU: Cyrix 6x86 (486-class CPU) Origin = "CyrixInstead" Device ID = 0x2231 Stepping=2 Revision=2 real memory = 50331648 (49152K bytes) avail memory = 46845952 (45748K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> lpt1 at 0x378-0x37f irq 12 on isa lpt1: Interrupt-driven port lp1: TCP/IP capable interface sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A sio3 not found at 0x2e8 wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, dma, iordy wcd0: 2062Kb/sec, 120Kb cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm data disc loaded, unlocked fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 flags 0x7 on motherboard npx0: INT 16 interface ppc0 at 0x278 irq 7 on isa ppc0: Generic chipset in PS/2 mode plip0: on ppbus 0 ppi0: on ppbus 0 vpo0: on ppbus 0 scbus0 at vpo0 bus 0 sd0 at scbus0 target 6 lun 0 sd0: type 0 removable SCSI 2 sd0: Direct-Access sd0: UNIT ATTENTION asc:28,0 sd0: Not ready to ready transition, medium may have changed 862MB (196608 4592 byte sectors) vpo0: on ppbus 0 scbus1 at vpo0 bus 0 sd1 at scbus1 target 6 lun 0 sd1: type 0 removable SCSI 2 sd1: Direct-Access sd1: ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd1 could not mode sense (4). Using ficticious geometry 96MB (196608 512 byte sectors) From owner-freebsd-hardware Wed Oct 1 01:16:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA27743 for hardware-outgoing; Wed, 1 Oct 1997 01:16:44 -0700 (PDT) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA27738; Wed, 1 Oct 1997 01:16:38 -0700 (PDT) Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id RAA01249; Wed, 1 Oct 1997 17:44:14 +0930 (CST) Message-Id: <199710010814.RAA01249@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: User Gp cc: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: ppbus problem In-reply-to: Your message of "Wed, 01 Oct 1997 02:35:00 -0400." <199710010635.CAA00340@tower.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 17:44:14 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Mime Version: 1.0 > Content Type: Text Plain > Date: Wed, 01 Oct 1997 02:35:00 -0400 > From: User Gp > > I 'm trying to install the ppbus stuff for my parallel port > zip drive. The kernel compiled OK, and it has a lot to say > about the drive, but fdisk and mount produce no results. > Here's dmesg. Any ideas. Can you be more specific about "no results"? Error messages? System lockup? > ppc0 at 0x278 irq 7 on isa > ppc0: Generic chipset in PS/2 mode > plip0: on ppbus 0 > ppi0: on ppbus 0 > vpo0: on ppbus 0 > scbus0 at vpo0 bus 0 > sd0 at scbus0 target 6 lun 0 > sd0: type 0 removable SCSI 2 > sd0: Direct-Access > sd0: UNIT ATTENTION asc:28,0 > sd0: Not ready to ready transition, medium may have changed > 862MB (196608 4592 byte sectors) > vpo0: on ppbus 0 > scbus1 at vpo0 bus 0 > sd1 at scbus1 target 6 lun 0 > sd1: type 0 removable SCSI 2 > sd1: Direct-Access > sd1: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > sd1 could not mode sense (4). Using ficticious geometry > 96MB (196608 512 byte sectors) Actually, this looks pretty ugly; you appear to have detected the vpo0 device twice. Do you have one Zip or two connected? mike From owner-freebsd-hardware Wed Oct 1 01:47:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA29249 for hardware-outgoing; Wed, 1 Oct 1997 01:47:53 -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 BAA29238 for ; Wed, 1 Oct 1997 01:47:46 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id BAA09018; Wed, 1 Oct 1997 01:45:43 -0700 (PDT) Message-ID: <19971001014543.46152@hydrogen.nike.efn.org> Date: Wed, 1 Oct 1997 01:45:43 -0700 From: John-Mark Gurney To: "hendrix77@" Cc: Andrew Gordon , Dan Odom , freebsd-hardware@FreeBSD.ORG Subject: Re: Multiple serial ports References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from hendrix77@ on Wed, Oct 01, 1997 at 02:44:01AM -0400 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 hendrix77@ scribbled this message on Oct 1: > On Tue, 30 Sep 1997, Andrew Gordon wrote: > > > > Speaking of plug and play, I am having an impossible time finding > > > hardware for my FreeBSD and BSDI boxes. Nothing out there has jumpers > > > any more, not even network cards. Where the heck does everyone find > > > supplies in this era of Windows NT? > > > > Just because they have no jumpers, that doesn't mean you are forced > > to use PnP. Certainly most ISA Ethernet cards can be configured by EEPROM > > to reside at a fixed address rather than being PnP (usually by use of > > a DOS utility). In some cases, this option is not clearly documented > > (SMC EtherEZ for example - there is a command-line option to the > > EZSETUP program to disable PnP, but if you go into the menu-driven > > version you don't get that option). > > > We are home users of FreeBSD, we dont have windows 3.1 or 95 and find it annoying about cards that have no jumpers, I suppose we ideally should be harassing the hardware vendors for drivers. But it genuinely sucks that we went out and bought a SB16 compa > tible soundcard and had to scrap it for a real SB or buy OSS to make it run since we dont have windows to run PnP config programs. I wonder is there no way to interface the pnp bios to do stuff or do you have to write code for each individual pnp card/dev > ice ? In current, we have code that will allow you to configure PnP devices, and it lets me use my cs4237b (juperless) sound card on a non-PnP motherboard... works like a charm (and I found that the cs4237b does 48k)... of course I'm also using Luigi's drivers, but that shouldn't matter.. plus you even have access to pnpinfo which will obtain a ton of info from the card about possible configurations of the card... of course nothing is more helpful than a data sheet for documenting what each LDN does.. :) also, this code doesn't get writen if people like you actually go out and work on it... thanks to Luigi Rizzo for actually completeing the work.. and enticing me to import the code by supporting my sound card.. :) he also has a package that will get you support for PnP on 2.2... his page is at http://www.iet.unipi.it/~luigi/... 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 Wed Oct 1 02:36:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA02082 for hardware-outgoing; Wed, 1 Oct 1997 02:36:19 -0700 (PDT) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA02076; Wed, 1 Oct 1997 02:36:12 -0700 (PDT) Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id TAA01489; Wed, 1 Oct 1997 19:03:35 +0930 (CST) Message-Id: <199710010933.TAA01489@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike Smith cc: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: ppbus problem In-reply-to: Your message of "Wed, 01 Oct 1997 17:44:14 +0930." <199710010814.RAA01249@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 19:03:34 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Mime Version: 1.0 > > Content Type: Text Plain > > Date: Wed, 01 Oct 1997 02:35:00 -0400 > > From: User Gp I hope you're subscribed to one or both of these lists; that's not a valid mail address. > > ppc0 at 0x278 irq 7 on isa > > ppc0: Generic chipset in PS/2 mode > > plip0: on ppbus 0 > > ppi0: on ppbus 0 > > vpo0: on ppbus 0 > > scbus0 at vpo0 bus 0 > > sd0 at scbus0 target 6 lun 0 > > sd0: type 0 removable SCSI 2 > > sd0: Direct-Access > > sd0: UNIT ATTENTION asc:28,0 > > sd0: Not ready to ready transition, medium may have changed > > 862MB (196608 4592 byte sectors) > > vpo0: on ppbus 0 > > scbus1 at vpo0 bus 0 > > sd1 at scbus1 target 6 lun 0 > > sd1: type 0 removable SCSI 2 > > sd1: Direct-Access > > sd1: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > sd1 could not mode sense (4). Using ficticious geometry > > 96MB (196608 512 byte sectors) > > Actually, this looks pretty ugly; you appear to have detected the vpo0 > device twice. Do you have one Zip or two connected? I've been trying to work out how you could actually have achieved this at all. Are you using the ppbus code in -current, or a patched 2.2? (Sorry, I nuked your previous message 8( ) mike From owner-freebsd-hardware Wed Oct 1 02:45:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA02633 for hardware-outgoing; Wed, 1 Oct 1997 02:45:17 -0700 (PDT) Received: from mithy.blueberry.co.uk (mithy.blueberry.co.uk [195.129.9.100]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA02624 for ; Wed, 1 Oct 1997 02:45:12 -0700 (PDT) Received: (from keith@localhost) by mithy.blueberry.co.uk (8.8.5/8.8.5) id KAA06575; Wed, 1 Oct 1997 10:45:06 +0100 (BST) Message-ID: <19971001104505.42587@blueberry.co.uk> Date: Wed, 1 Oct 1997 10:45:05 +0100 From: Keith Jones To: hardware@FreeBSD.ORG Subject: Re: de0: abnormal interrupt: receive process stopped References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: ; from Michael Beckmann on Sun, Aug 24, 1997 at 12:56:01AM +0200 Organization: Blueberry New Media Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Aug 24, 1997 at 12:56:01AM +0200, Michael Beckmann wrote: > de0: abnormal interrupt: receive process stopped > > I have this message on one server in dmesg since a few days. Has anyone > else seen this before ? I've exchanged the Ethernet card (SMC Etherpower > 10) with a new one already, it didn't help. This never occurred before with > the same card. Is something going wrong with the mainboard ? I'm running > 2.2-RELENG. I'm getting the same on bootup (running 2.1-STABLE on a Pentium Pro 200, also with a SMC Etherpower card). On our P133 with the same Ethernet card and OS, this doesn't occur, on bootup or at any other time. The mainboard on our Pentium Pro 200 is an ASUSTek P6NP5 - if anyone is aware of any problems with this mainboard and SMC Etherpower cards, please let me know, either here or by email. Keith -- v Keith Jones Systems Manager, Blueberry New Media Ltd. v | Postal Mail: 2/10 Harbour Yard, Chelsea Harbour, LONDON, UK. SW10 0XD | | Telephone: +44 (0)171 351 3313 Fax: +44 (0)171 351 2476 | ^ Email: Keith.Jones@blueberry.co.uk WWW: http://www.blueberry.co.uk/ ^ From owner-freebsd-hardware Wed Oct 1 03:14:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA04117 for hardware-outgoing; Wed, 1 Oct 1997 03:14:08 -0700 (PDT) Received: from DonaldBurr.dyn.ml.org (dburr@[206.18.115.71]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA04110; Wed, 1 Oct 1997 03:14:01 -0700 (PDT) Received: (from dburr@localhost) by DonaldBurr.dyn.ml.org (8.8.5/8.8.5) id DAA01071; Wed, 1 Oct 1997 03:13:08 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Wed, 01 Oct 1997 03:00:52 -0700 (PDT) Organization: Starfleet Command From: Donald Burr To: AIC7xxx List , FreeBSD SCSI , FreeBSD Hardware Subject: Odd behavior of Wangtek 5525ES SCSI tape drive under 2.2.2 and A Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- I am the proud owner of a (ahc0:4:0): "WANGTEK 5525ES SCSI 73R1" type 1 removable SCSI 2 st0(ahc0:4:0): Sequential-Access density code 0x0, drive empty Wangtek 5525ES SCSI-2 tape drive (525MB QIC-525 drive). It's connected to my brand-new Adaptec AHA-2940AU PCI SCSI controller (aic7860), on my FreeBSD 2.2.2-RELEASE system. This setup works pretty well. I've already done several successful dumps to this device, and have created more tar tapes than I can shake a stick at. The weirdness comes with the `mt' command. Basically, any "mt" command that causes the tape drive to spin (weof, retension, fsf, etc.) SOMETIMES (probably 1 in 10 times) causes the system to "soft hang". Processes keep running, I can switch to another VC and login, or telnet to the machine over the network, etc. BUT the mt process is hung -- I can't exit with Ctrl-C, or kill (even kill -KILL) it. Ctrl-Z fails to suspend the thing, and the process fails to die on a reboot/shutdown (this results in the "syncing disks...giving up" message). And the tape drive don't spin. BUT, other commands that access the tape drive (tar, dump, even dd) work fine!!! unix% tar cv /some/dir /some/dir/a /some/dir/a/file /some/dir/b/dir /some/dir/c/file2 ...tape drive chugs away, and finishes successfully unix% dump 0auf /dev/rst0 / DUMP: .... [successful dump] unix% dd if=/dev/rst0 of=/dev/zero ...blahblahblah unix% mt retension [ oops - hung. Big Red Button time. ] I have tried the usual remedies -- checking cables and termination, disconnecting all SCSI devices EXCEPT the tape drive, etc. Nothing helps. As stated above, I run 2.2.2-RELEASE. I have tried one of the RELENG kernels (970913 I think), with the same behavior. Unfortunately I'm not man enough to try CURRENT. :) My controller is an Adaptec AHA-2940AU PCI SCSI controller (aic7860). The controller works great, and all of my other devices (JAZ, cd-rom, etc.) work flawlessly. Any ideas? dmesg output follows: Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.2-RELEASE #0: Mon Sep 15 01:19:35 PDT 1997 root@DonaldBurr.DonaldBurr.dyn.ml.org:/usr/src/sys/compile/DONALDBURR CPU: AMD Am5x86 Write-Back (486-class CPU) Origin = "AuthenticAMD" Id = 0x4f4 Stepping=4 Features=0x1 real memory = 33554432 (32768K bytes) avail memory = 30396416 (29684K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:5 vga0 rev 71 on pci0:11 ahc0 rev 1 int a irq 11 on pci0:13 ahc0: aic7860 Single Channel, SCSI Id=7, 3 SCBs ahc0 waiting for scsi devices to settle (ahc0:1:0): "NEC CD-ROM DRIVE:462 1.16" type 5 removable SCSI 2 cd0(ahc0:1:0): CD-ROM can't get the size (ahc0:2:0): "iomega jaz 1GB H.72" type 0 removable SCSI 2 sd0(ahc0:2:0): Direct-Access sd0(ahc0:2:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd0 could not mode sense (4). Using ficticious geometry 1021MB (2091050 512 byte sectors) sd0(ahc0:2:0): with 1021 cyls, 64 heads, and an average 32 sectors/track (ahc0:4:0): "WANGTEK 5525ES SCSI 73R1" type 1 removable SCSI 2 st0(ahc0:4:0): Sequential-Access density code 0x0, drive empty ed0 rev 0 int a irq 9 on pci0:15 ed0: address 00:00:b4:5a:4e:71, type NE2000 (16 bit) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <12 virtual consoles, flags=0x0> lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-32 wd0: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0x80ff80ff on isa wdc1: unit 0 (wd2): , 32-bit, multi-block-32 wd2: 234MB (479632 sectors), 967 cyls, 16 heads, 31 S/T, 512 B/S fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 10 drq 1 on isa sb0: opl0 at 0x388 on isa opl0: sctarg0(noadapter::): Processor Target Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNDIiMvjpixuAwagxAQG2OwQArwrX8X64kdcoH4IyyBFNG4Z8odYXNia3 eRgNWLgurrLdqHDCe3X9fF6wEsMHhVYC341NhjbgIFOtcuHXxWZzYBccdVyxWbE4 CZ0O762RdASE9ezNnnDvNnTysYl7c0hh2efti8HZdUbhorpByx98p/IhLn/8QhLs KDdzQ9vGqcA= =E/1T -----END PGP SIGNATURE----- From owner-freebsd-hardware Wed Oct 1 05:58:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA11568 for hardware-outgoing; Wed, 1 Oct 1997 05:58:14 -0700 (PDT) Received: from tower.my.domain (nscs22p16.remote.umass.edu [128.119.179.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA11557; Wed, 1 Oct 1997 05:58:08 -0700 (PDT) Received: from tower.my.domain (localhost [127.0.0.1]) by tower.my.domain (8.8.7/8.8.7) with ESMTP id IAA00667; Wed, 1 Oct 1997 08:55:11 -0400 (EDT) Message-Id: <199710011255.IAA00667@tower.my.domain> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike Smith cc: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: ppbus problem In-reply-to: Your message of "Wed, 01 Oct 1997 17:44:14 +0930." <199710010814.RAA01249@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 08:55:11 -0400 From: User Gp Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Mime Version: 1.0 > > Content Type: Text Plain > > Date: Wed, 01 Oct 1997 02:35:00 -0400 > > From: User Gp > > > > I 'm trying to install the ppbus stuff for my parallel port > > zip drive. The kernel compiled OK, and it has a lot to say > > about the drive, but fdisk and mount produce no results. > > Here's dmesg. Any ideas. > > Can you be more specific about "no results"? Error messages? System > lockup? No error messages, it just sits doing nothing, i.e. no indication (sound or lights of disk activity in the zip. I bring my prompt back with ^C. > > > ppc0 at 0x278 irq 7 on isa > > ppc0: Generic chipset in PS/2 mode > > plip0: on ppbus 0 > > ppi0: on ppbus 0 > > vpo0: on ppbus 0 > > scbus0 at vpo0 bus 0 > > sd0 at scbus0 target 6 lun 0 > > sd0: type 0 removable SCSI 2 > > sd0: Direct-Access > > sd0: UNIT ATTENTION asc:28,0 > > sd0: Not ready to ready transition, medium may have changed > > 862MB (196608 4592 byte sectors) > > vpo0: on ppbus 0 > > scbus1 at vpo0 bus 0 > > sd1 at scbus1 target 6 lun 0 > > sd1: type 0 removable SCSI 2 > > sd1: Direct-Access > > sd1: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > sd1 could not mode sense (4). Using ficticious geometry > > 96MB (196608 512 byte sectors) > > Actually, this looks pretty ugly; you appear to have detected the vpo0 > device twice. Do you have one Zip or two connected? > > mike > Just one. Greg From owner-freebsd-hardware Wed Oct 1 06:44:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA13901 for hardware-outgoing; Wed, 1 Oct 1997 06:44:11 -0700 (PDT) Received: from anise.csv.warwick.ac.uk (csubl@anise.csv.warwick.ac.uk [137.205.192.106]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA13854; Wed, 1 Oct 1997 06:43:24 -0700 (PDT) From: Mr M P Searle Message-Id: <1996.199710011340@anise.csv.warwick.ac.uk> Received: by anise.csv.warwick.ac.uk id OAA01996; Wed, 1 Oct 1997 14:40:04 +0100 (BST) Subject: Re: Odd behavior of Wangtek 5525ES SCSI tape drive under 2.2.2 and A In-Reply-To: from Donald Burr at "Oct 1, 97 03:00:52 am" To: dburr@poboxes.com (Donald Burr) Date: Wed, 1 Oct 1997 14:39:54 +0100 (BST) Cc: aic7xxx@freebsd.org, freebsd-scsi@freebsd.org, 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 -- Start of PGP signed section. > I am the proud owner of a > > (ahc0:4:0): "WANGTEK 5525ES SCSI 73R1" type 1 removable SCSI 2 > st0(ahc0:4:0): Sequential-Access density code 0x0, drive empty > > Wangtek 5525ES SCSI-2 tape drive (525MB QIC-525 drive). It's connected to > my brand-new Adaptec AHA-2940AU PCI SCSI controller (aic7860), on my > FreeBSD 2.2.2-RELEASE system. > > This setup works pretty well. I've already done several successful dumps > to this device, and have created more tar tapes than I can shake a stick > at. > > The weirdness comes with the `mt' command. Basically, any "mt" command > that causes the tape drive to spin (weof, retension, fsf, etc.) SOMETIMES > (probably 1 in 10 times) causes the system to "soft hang". Processes keep > running, I can switch to another VC and login, or telnet to the machine > over the network, etc. BUT the mt process is hung -- I can't exit with > Ctrl-C, or kill (even kill -KILL) it. Ctrl-Z fails to suspend the thing, > and the process fails to die on a reboot/shutdown (this results in the > "syncing disks...giving up" message). And the tape drive don't spin. > > BUT, other commands that access the tape drive (tar, dump, even dd) work > fine!!! > > unix% tar cv /some/dir > /some/dir/a > /some/dir/a/file > /some/dir/b/dir > /some/dir/c/file2 > ...tape drive chugs away, and finishes successfully > unix% dump 0auf /dev/rst0 / > DUMP: .... > [successful dump] > unix% dd if=/dev/rst0 of=/dev/zero > ...blahblahblah > unix% mt retension > [ oops - hung. Big Red Button time. ] > > I have tried the usual remedies -- checking cables and termination, > disconnecting all SCSI devices EXCEPT the tape drive, etc. Nothing helps. > > As stated above, I run 2.2.2-RELEASE. I have tried one of the RELENG > kernels (970913 I think), with the same behavior. Unfortunately I'm not > man enough to try CURRENT. :) > > My controller is an Adaptec AHA-2940AU PCI SCSI controller (aic7860). The > controller works great, and all of my other devices (JAZ, cd-rom, etc.) > work flawlessly. > > Any ideas? > Well, no, but you're not the only one. I've got a Tandberg 250MB QIC-250 drive, on an NCR controller. 'mt fsf' will often cause SCSI errors on all devices, a SCSI reset, or a completely hung system (not just that process). 'cat /dev/nrst0 > /dev/null' has no problems, even though it is doing the same thing. I'm not sure that my problem is the same as yours (this drive is generally dodgy - hangs and SCSI errors also happen if I don't wait for one command to complete before running another, or if I try to read two files without rewinding and moving back again between them...), but it looks similar. Anyway, I've worked round it by replacing all the mt commands (mostly fsf) with things like the 'cat /dev/nrst0 > /dev/null' to move forward a file, and anything with /dev/rst0 to rewind. You could probably do the same for a lot of the other mt commands as well. You could also try the 'wait for tape to stop clunking before next command' fix in case mine isn't the only drive in the world to do this. (or put big sleeps in scripts) This is with 2.1.0, so it may be the same thing despite the different errors. From owner-freebsd-hardware Wed Oct 1 07:02:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14886 for hardware-outgoing; Wed, 1 Oct 1997 07:02:59 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA14872; Wed, 1 Oct 1997 07:02:46 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id IAA12415; Wed, 1 Oct 1997 08:02:37 -0600 (MDT) Message-Id: <199710011402.IAA12415@pluto.plutotech.com> To: Donald Burr cc: AIC7xxx List , FreeBSD SCSI , FreeBSD Hardware Subject: Re: Odd behavior of Wangtek 5525ES SCSI tape drive under 2.2.2 and A In-reply-to: Your message of "Wed, 01 Oct 1997 03:00:52 PDT." Date: Wed, 01 Oct 1997 08:02:10 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >-----BEGIN PGP SIGNED MESSAGE----- > >I am the proud owner of a > >(ahc0:4:0): "WANGTEK 5525ES SCSI 73R1" type 1 removable SCSI 2 >st0(ahc0:4:0): Sequential-Access density code 0x0, drive empty > >Wangtek 5525ES SCSI-2 tape drive (525MB QIC-525 drive). It's connected to >my brand-new Adaptec AHA-2940AU PCI SCSI controller (aic7860), on my >FreeBSD 2.2.2-RELEASE system. Set the termination setting on your 2940AU explicitly. Do not use "Auto Termination". You should also upgrade to the latest version of the aic7xxx driver from 2.2-stable. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Wed Oct 1 07:39:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA17103 for hardware-outgoing; Wed, 1 Oct 1997 07:39:57 -0700 (PDT) Received: from rfd1.oit.umass.edu (mailhub.oit.umass.edu [128.119.175.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA17096; Wed, 1 Oct 1997 07:39:52 -0700 (PDT) Received: from wilde.oit.umass.edu by rfd1.oit.umass.edu (PMDF V5.1-10 #20973) with ESMTP id <0EHD005O7NEAQM@rfd1.oit.umass.edu>; Wed, 1 Oct 1997 10:39:46 -0400 (EDT) Received: from localhost (gp@localhost) by wilde.oit.umass.edu (8.8.3/8.8.6) with SMTP id KAA06757; Wed, 01 Oct 1997 10:39:45 -0400 (EDT) Date: Wed, 01 Oct 1997 10:39:45 -0400 (EDT) From: Greg Pavelcak Subject: Re: ppbus problem In-reply-to: <199710011255.IAA00667@tower.my.domain> To: hardware@FreeBSD.ORG Cc: questions@FreeBSD.ORG 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 > > > From: User Gp > > > > > > I 'm trying to install the ppbus stuff for my parallel port > > > zip drive. The kernel compiled OK, and it has a lot to say > > > about the drive, but fdisk and mount produce no results. > > > Here's dmesg. Any ideas. > > > > Can you be more specific about "no results"? Error messages? System > > lockup? > > No error messages, it just sits doing nothing, i.e. no indication (sound or > lights of disk activity in the zip. I bring my prompt back with ^C. > > > > > > ppc0 at 0x278 irq 7 on isa > > > ppc0: Generic chipset in PS/2 mode > > > plip0: on ppbus 0 > > > ppi0: on ppbus 0 > > > vpo0: on ppbus 0 > > > scbus0 at vpo0 bus 0 > > > sd0 at scbus0 target 6 lun 0 > > > sd0: type 0 removable SCSI 2 > > > sd0: Direct-Access > > > sd0: UNIT ATTENTION asc:28,0 > > > sd0: Not ready to ready transition, medium may have changed > > > 862MB (196608 4592 byte sectors) > > > vpo0: on ppbus 0 > > > scbus1 at vpo0 bus 0 > > > sd1 at scbus1 target 6 lun 0 > > > sd1: type 0 removable SCSI 2 > > > sd1: Direct-Access > > > sd1: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > sd1 could not mode sense (4). Using ficticious geometry > > > 96MB (196608 512 byte sectors) > > > > Actually, this looks pretty ugly; you appear to have detected the vpo0 > > device twice. Do you have one Zip or two connected? > > > > mike > > To follow up, I have one zip, but I had vpo.c in both /sys/conf/files and /sys/i386/conf/files.i386 and their related directories (DOn't ask me how.). Now I only have vpo.c in /sys/i386/conf/files.i386, and there's some improvement. Now I only get the probe results for the 96MB Zip. fdisk still hangs though. Should I be using some of those flags in my kernel? I don't quite understand those. Thanks. Greg From owner-freebsd-hardware Wed Oct 1 08:17:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA19138 for hardware-outgoing; Wed, 1 Oct 1997 08:17:14 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA19113; Wed, 1 Oct 1997 08:17:05 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA00686; Thu, 2 Oct 1997 00:44:42 +0930 (CST) Message-Id: <199710011514.AAA00686@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: hardware@FreeBSD.ORG cc: questions@FreeBSD.ORG Subject: Re: ppbus problem In-reply-to: Your message of "Wed, 01 Oct 1997 08:55:11 -0400." <199710011255.IAA00667@tower.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 00:44:40 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I 'm trying to install the ppbus stuff for my parallel port > > > zip drive. The kernel compiled OK, and it has a lot to say > > > about the drive, but fdisk and mount produce no results. > > > Here's dmesg. Any ideas. > > > > Can you be more specific about "no results"? Error messages? System > > lockup? > > No error messages, it just sits doing nothing, i.e. no indication (sound or > lights of disk activity in the zip. I bring my prompt back with ^C. OK, command freeze. You might eventually get an error message. > > Actually, this looks pretty ugly; you appear to have detected the vpo0 > > device twice. Do you have one Zip or two connected? > > Just one. OK, 2.2 or -current? Can you send a copy of the relevant parts of your kernel config? Have you tried it with a fresh kernel source tree? (In particular I am wondering if you've managed to get two copies of the vpo driver into your kernel.) mike From owner-freebsd-hardware Wed Oct 1 08:30:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA20022 for hardware-outgoing; Wed, 1 Oct 1997 08:30:47 -0700 (PDT) Received: from tower.my.domain (nscs29p11.remote.umass.edu [128.119.179.180]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA20014; Wed, 1 Oct 1997 08:30:43 -0700 (PDT) Received: from tower.my.domain (localhost [127.0.0.1]) by tower.my.domain (8.8.7/8.8.7) with ESMTP id JAA00693; Wed, 1 Oct 1997 09:02:33 -0400 (EDT) Message-Id: <199710011302.JAA00693@tower.my.domain> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike Smith cc: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: ppbus problem In-reply-to: Your message of "Wed, 01 Oct 1997 19:03:34 +0930." <199710010933.TAA01489@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 09:02:33 -0400 From: User Gp Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I hope you're subscribed to one or both of these lists; that's not a > valid mail address. > Yeah, I'm on the list. Sorry about the messed up posts. I just started using exmh at home and I obviously don't have it set up completely yet > > > > ppc0 at 0x278 irq 7 on isa > > > ppc0: Generic chipset in PS/2 mode > > > plip0: on ppbus 0 > > > ppi0: on ppbus 0 > > > vpo0: on ppbus 0 > > > scbus0 at vpo0 bus 0 > > > sd0 at scbus0 target 6 lun 0 > > > sd0: type 0 removable SCSI 2 > > > sd0: Direct-Access > > > sd0: UNIT ATTENTION asc:28,0 > > > sd0: Not ready to ready transition, medium may have changed > > > 862MB (196608 4592 byte sectors) > > > vpo0: on ppbus 0 > > > scbus1 at vpo0 bus 0 > > > sd1 at scbus1 target 6 lun 0 > > > sd1: type 0 removable SCSI 2 > > > sd1: Direct-Access > > > sd1: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > sd1 could not mode sense (4). Using ficticious geometry > > > 96MB (196608 512 byte sectors) > > > > Actually, this looks pretty ugly; you appear to have detected the vpo0 > > device twice. Do you have one Zip or two connected? > > I've been trying to work out how you could actually have achieved this > at all. Are you using the ppbus code in -current, or a patched 2.2? > (Sorry, I nuked your previous message 8( ) > > mike > > Now that you mention it, I got the stuff from Nicholas Souchu's (sp) page before I realized it was in -current (which I'm using) already. I'll bet I messed up one of the files that the installation instructions tell me to edit. I'll have to retrace my steps. Thanks. Greg From owner-freebsd-hardware Wed Oct 1 11:29:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA29166 for hardware-outgoing; Wed, 1 Oct 1997 11:29:45 -0700 (PDT) Received: from jimi.danodom.com (jimi.danodom.com [205.153.247.99]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA29161 for ; Wed, 1 Oct 1997 11:29:40 -0700 (PDT) Received: (from daniel@localhost) by jimi.danodom.com (8.8.3/8.8.3) id SAA00197; Wed, 1 Oct 1997 18:27:29 GMT Date: Wed, 1 Oct 1997 18:27:29 GMT Message-Id: <199710011827.SAA00197@jimi.danodom.com> From: Dan Odom MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: richard@pegasus.com (Richard Foulk) Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Multiple serial ports In-Reply-To: <199709302127.LAA29237@pegasus.com> References: <199709302127.LAA29237@pegasus.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ugh. Nope. We're paying $1,200 for a good 16-port terminal server and we can add up to an additional 48 ports at $450 per 16 ports. A Computone PowerRack. It does all the good stuff (PPP/PAP/CHAP, SNMP, and so on) at a low cost. Richard Foulk writes: > } > } Thanks for your help guys, you've been great. I think, however, > } that I'll spend the extra $500 or so and just buy a terminal server. > } It's easier. :-) > > Yikes. I doubt you'll find a decent terminal server for that cheap. > Try four times that. > > > Richard -- Daniel Odom, software engineer http://www.danodom.com/ "Whatever you do will be insignificant, but it is very important that you do it." --Mahatma Gandhi From owner-freebsd-hardware Wed Oct 1 11:33:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA29366 for hardware-outgoing; Wed, 1 Oct 1997 11:33:18 -0700 (PDT) Received: from jimi.danodom.com (jimi.danodom.com [205.153.247.99]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA29334 for ; Wed, 1 Oct 1997 11:32:38 -0700 (PDT) Received: (from daniel@localhost) by jimi.danodom.com (8.8.3/8.8.3) id SAA00203; Wed, 1 Oct 1997 18:31:41 GMT Date: Wed, 1 Oct 1997 18:31:41 GMT Message-Id: <199710011831.SAA00203@jimi.danodom.com> From: Dan Odom MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andrew Gordon Cc: freebsd-hardware@freebsd.org Subject: Re: Multiple serial ports In-Reply-To: References: <199709301841.SAA03454@jimi.danodom.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Obvious problem: what does one do if one does not have MS-DOS anywhere? Adaptec, for example, includes the software in the card BIOS accesible via a hotkey during boot. I love their cards. If I can only change the numbers using a DOS utility, I can't change them at all. This is a straight BSD office (BSDI 2.1, BSDI 3.0, FreeBSD 2.7.1, and FreeBSD 2.2.2). Andrew Gordon writes: > On Tue, 30 Sep 1997, Dan Odom wrote: > > Speaking of plug and play, I am having an impossible time finding > > hardware for my FreeBSD and BSDI boxes. Nothing out there has jumpers > > any more, not even network cards. Where the heck does everyone find > > supplies in this era of Windows NT? > > Just because they have no jumpers, that doesn't mean you are forced > to use PnP. Certainly most ISA Ethernet cards can be configured by EEPROM > to reside at a fixed address rather than being PnP (usually by use of > a DOS utility). In some cases, this option is not clearly documented > (SMC EtherEZ for example - there is a command-line option to the > EZSETUP program to disable PnP, but if you go into the menu-driven > version you don't get that option). > > Sound cards are the one category where PnP has become almost mandatory. > > BTW, note that Windows NT 4.0 doesn't do PnP either - perhaps you meant > "this era of Windows 95" in the above? -- Daniel Odom, software engineer http://www.danodom.com/ "Whatever you do will be insignificant, but it is very important that you do it." --Mahatma Gandhi From owner-freebsd-hardware Wed Oct 1 13:22:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA05339 for hardware-outgoing; Wed, 1 Oct 1997 13:22:20 -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 NAA05332 for ; Wed, 1 Oct 1997 13:22:14 -0700 (PDT) Received: (from arg@localhost) by arg1.demon.co.uk (8.8.5/8.8.5) id VAA22558; Wed, 1 Oct 1997 21:21:08 +0100 (BST) Date: Wed, 1 Oct 1997 21:21:08 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Dan Odom cc: freebsd-hardware@freebsd.org Subject: Re: Multiple serial ports In-Reply-To: <199710011831.SAA00203@jimi.danodom.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 Wed, 1 Oct 1997, Dan Odom wrote: > Obvious problem: what does one do if one does not have MS-DOS > anywhere? Adaptec, for example, includes the software in the card > BIOS accesible via a hotkey during boot. I love their cards. If I > can only change the numbers using a DOS utility, I can't change them > at all. You keep a bootable DOS floppy with a selection of card utilities in your toolbox. More indispensible than a screwdriver when it comes to working with PC hardware, IMHO. From owner-freebsd-hardware Wed Oct 1 13:49:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA06970 for hardware-outgoing; Wed, 1 Oct 1997 13:49:57 -0700 (PDT) Received: from mph124.rh.psu.edu (hunt@MPH124.rh.psu.edu [128.118.126.83]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA06954 for ; Wed, 1 Oct 1997 13:49:47 -0700 (PDT) Received: (from hunt@localhost) by mph124.rh.psu.edu (8.8.7/8.8.7) id QAA10620; Wed, 1 Oct 1997 16:48:22 -0400 (EDT) Message-ID: <19971001164821.40569@mph124.rh.psu.edu> Date: Wed, 1 Oct 1997 16:48:21 -0400 From: Matthew Hunt To: Dan Odom Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Multiple serial ports Reply-To: Matthew Hunt References: <199709301841.SAA03454@jimi.danodom.com> <199710011831.SAA00203@jimi.danodom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199710011831.SAA00203@jimi.danodom.com>; from Dan Odom on Wed, Oct 01, 1997 at 06:31:41PM +0000 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Oct 01, 1997 at 06:31:41PM +0000, Dan Odom wrote: > Obvious problem: what does one do if one does not have MS-DOS > anywhere? Adaptec, for example, includes the software in the card My solution is to keep an OpenDOS boot floppy around. It's not from MS, and it's free software, so I don't have any moral problems having it about. Visit http://www.caldera.com/ for details. -- Matthew Hunt * Think locally, act globally. finger hunt@mph124.rh.psu.edu for PGP public key. From owner-freebsd-hardware Wed Oct 1 16:02:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA15004 for hardware-outgoing; Wed, 1 Oct 1997 16:02:20 -0700 (PDT) Received: from tower.my.domain (nscs23p6.remote.umass.edu [128.119.179.49]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA14996; Wed, 1 Oct 1997 16:02:09 -0700 (PDT) Received: from tower.my.domain (localhost [127.0.0.1]) by tower.my.domain (8.8.7/8.8.7) with ESMTP id SAA00554; Wed, 1 Oct 1997 18:59:32 -0400 (EDT) Message-Id: <199710012259.SAA00554@tower.my.domain> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-questions@FreeBSD.ORG cc: freebsd-hardware@FreeBSD.ORG Subject: Problems with ppbus and ||-port zip Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 18:59:32 -0400 From: User Gp Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am still having trouble with my ||-port zip, though looking better now than before. My problem is if I try fdisk /dev/sd0 or mount /dev/sd0, the machine just hangs. I waited 15 minutes for an error message but got nothing. I was able to get my prompt back with ^C. Here is part of dmesg and, as suggested by a responder to an earlier post, part of my kernel file. The 01 flag was just an experiment, I also booted a kernel without it and had the same problem. I thought I read something about going with "Nibble Mode" so I put it in. I'd appreciate any advice. Thanks. Greg (I know my return address is screwed up, I just don't know how to fix it. I am on questions and hardware. My address is gpavelcak@philos.umass.edu) ppc0 at 0x278 irq 12 flags 0x1 on isa ppc0: Generic chipset in NIBBLE mode plip0: on ppbus 0 nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 vpo0: on ppbus 0 scbus0 at vpo0 bus 0 sd0 at scbus0 target 6 lun 0 sd0: type 0 removable SCSI 2 sd0: Direct-Access sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd0 could not mode sense (4). Using ficticious geometry 96MB (196608 512 byte sectors) controller scbus0 device sd0 controller ppbus0 # ppbus stuff controller vpo0 at ppbus0 device nlpt0 at ppbus0 device ppi0 at ppbus0 device plip0 at ppbus0 controller ppc0 at isa? port 0x278 irq 12 flags 0x1 vector ppcintr #device lpt0 at isa? port "IO_LPT2" tty irq 12 vector lptintr device lpt1 at isa? port "IO_LPT1" tty irq 7 vector lptintr -- --------------------------------------------------------------------------- From owner-freebsd-hardware Wed Oct 1 20:53:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA29116 for hardware-outgoing; Wed, 1 Oct 1997 20:53:21 -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 UAA29110 for ; Wed, 1 Oct 1997 20:53:16 -0700 (PDT) Received: (from uucp@localhost) by bsd7.cs.sunysb.edu (8.8.5/8.8.5) with UUCP id XAA02905 for hardware@freebsd.org; Wed, 1 Oct 1997 23:52:11 -0400 (EDT) Received: (from gene@localhost) by starkhome.cs.sunysb.edu (8.8.5/8.8.5) id XAA02311; Wed, 1 Oct 1997 23:51:45 -0400 (EDT) Date: Wed, 1 Oct 1997 23:51:45 -0400 (EDT) From: Gene Stark Message-Id: <199710020351.XAA02311@starkhome.cs.sunysb.edu> To: hardware@freebsd.org In-reply-to: Dan Odom's message of Tue, 30 Sep 1997 20:44:03 GMT Subject: Re: Multiple serial ports References: <199709300128.BAA02166@jimi.danodom.com> <199709301841.SAA03454@jimi.danodom.com> <3.0.3.32.19970930150358.00732b2c@nething.com> <60rpq1$lea@starkhome.cs.sunysb.edu> Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dan Odom writes: > Randy Berndt writes: > > At 06:41 PM 9/30/97 GMT, you wrote: > > >The Boca cards all say "does not support modems," > > > > Actually, the Boca-4 and Boca-8 do not support modems. The Boca-6 (never > > seen one) and the Boca-16 DO support modems. The -16 uses a weird 10-pin > > RJ-45 connection (cables available from Boca). I do not use modems on them, > > but I have them null modem-ed to a mini-computer that thinks they are > > modems, and everything seems to work ok. The Boca-16 (BB 8016?) cards are hard to get these days. I believe they might have been discontinued by Boca -- not sure. The Boca-8 (BB 1008) cards do not support modems -- I have one of those and it works fine other than that limitation. The Boca-6 (IOAT/66) card *does* support modems. I have several of these, and have used modems on them. I have been buying the IOAT/66 cards from http://www.trucost.com for $75 (bought two in the last 6 weeks). I have also been buying the cables that go with them from them for $14 for a 2-pack. You can put two IOAT/66's on one system (replacing the normal COM1 and COM2), so the cost for 12 modem-compatible ports built in this way is: 2 x $75 = $150 for the cards 6 x $14 = $ 84 for the cables Total: $234 + S+H. - Gene Stark From owner-freebsd-hardware Wed Oct 1 21:57:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA02723 for hardware-outgoing; Wed, 1 Oct 1997 21:57:40 -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 VAA02718 for ; Wed, 1 Oct 1997 21:57:35 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id BAA01869; Thu, 2 Oct 1997 01:00:06 -0400 (EDT) Date: Thu, 2 Oct 1997 01:00:06 -0400 (EDT) From: "John T. Farmer" Message-Id: <199710020500.BAA01869@sabre.goldsword.com> To: daniel@jimi.danodom.com, richard@pegasus.com Subject: Re: Multiple serial ports Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Sep 1997 11:27:38 -1000 (Richard Foulk) said: >} Thanks for your help guys, you've been great. I think, however, >} that I'll spend the extra $500 or so and just buy a terminal server. >} It's easier. :-) > >Yikes. I doubt you'll find a decent terminal server for that cheap. >Try four times that. Actually, there are several vendors of terminal servers that will do 4 to 16 serial ports in the <$1500 range (some much less than that!). The downside is the number of control lines available, sometimes the maximin port speed, and some of the "routing" type features. Check out Lantronix, Equinox, Chase, Stallion, some of the cheaper DEC boxes, etc. Remember, to handle terminals, printers, or to act as front ends for machines doesn't require modem control lines, 900kbps ports, RIP, radius, ppp, and all the neat features we need/want to handle modem banks. I once designed & installed a distributed system that tied 300+ serial devices at four plants 10 miles apart using "dumb" terminal servers, and T-1 bridges to tie the sites together. Lots of telnet packets flying around... 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 Wed Oct 1 21:58:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA02755 for hardware-outgoing; Wed, 1 Oct 1997 21:58:37 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA02750 for ; Wed, 1 Oct 1997 21:58:31 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id OAA00351; Thu, 2 Oct 1997 14:25:34 +0930 (CST) Message-Id: <199710020455.OAA00351@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Dan Odom cc: Andrew Gordon , freebsd-hardware@FreeBSD.ORG Subject: Re: Multiple serial ports In-reply-to: Your message of "Wed, 01 Oct 1997 18:31:41 GMT." <199710011831.SAA00203@jimi.danodom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 14:25:33 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Obvious problem: what does one do if one does not have MS-DOS > anywhere? Adaptec, for example, includes the software in the card > BIOS accesible via a hotkey during boot. I love their cards. If I > can only change the numbers using a DOS utility, I can't change them > at all. Run doscmd or pcemu with I/O access enabled. Don't try to run any of the interrupt-generating tests, and preferably do it on a quiet machine, but this has worked OK before for me. mike From owner-freebsd-hardware Wed Oct 1 22:20:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA03838 for hardware-outgoing; Wed, 1 Oct 1997 22:20:10 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA03641 for ; Wed, 1 Oct 1997 22:16:34 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id PAA22551 for freebsd-hardware@freefall.freebsd.org; Thu, 2 Oct 1997 15:16:17 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with ESMTP id PAA17600 for ; Thu, 2 Oct 1997 15:17:05 +1000 (EST) Received: from bard.dtir.qld.gov.au (bard.dtir.qld.gov.au [167.123.10.12]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id PAA17429 for ; Thu, 2 Oct 1997 15:17:04 +1000 (EST) Received: (from syspmc@localhost) by bard.dtir.qld.gov.au (8.8.5/8.7.3) id PAA03772; Thu, 2 Oct 1997 15:17:03 +1000 (EST) Date: Thu, 2 Oct 1997 15:17:03 +1000 (EST) From: Phil Chadwick Message-Id: <199710020517.PAA03772@bard.dtir.qld.gov.au> To: freebsd-hardware@freefall.freebsd.org Subject: 440LX Chipset Motherboards X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Does FreeBSD run on Intel 440LX chipset motherboards such as the Asus P2L97-DS? Thanks... Phil -- Phil Chadwick Email: syspmc@dtir.qld.gov.au ,-_|\ Supervisor, UNIX Support Phone: +61 7 3247 9239 / * Department of Training Fax: +61 7 3247 9111 \_,-._/ and Industrial Relations v From owner-freebsd-hardware Wed Oct 1 23:41:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07823 for hardware-outgoing; Wed, 1 Oct 1997 23:41:01 -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 XAA07818 for ; Wed, 1 Oct 1997 23:40:57 -0700 (PDT) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id UAA04547; Wed, 1 Oct 1997 20:40:35 -1000 Date: Wed, 1 Oct 1997 20:40:35 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199710020640.UAA04547@pegasus.com> In-Reply-To: "John T. Farmer" "Re: Multiple serial ports" (Oct 2, 1:00am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-hardware@FreeBSD.ORG Subject: Re: Multiple serial ports Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk } Actually, there are several vendors of terminal servers that will do } 4 to 16 serial ports in the <$1500 range (some much less than that!). } The downside is the number of control lines available, sometimes the } maximin port speed, and some of the "routing" type features. Check out } Lantronix, Equinox, Chase, Stallion, some of the cheaper DEC boxes, etc. } Quirky and slow. I've tested the Stallions and sent them back, and heard others doing the same with other cheap boxes. They may be able to run one port at a reasonable speed, say 9600 or 19200. More than that and they bog down and get jerky and slow. Just one printer connection and a single interactive telnet session at the same time becomes unbearable. And, do any of them have modem control? Richard From owner-freebsd-hardware Thu Oct 2 01:03:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA11456 for hardware-outgoing; Thu, 2 Oct 1997 01:03:19 -0700 (PDT) Received: from sinbin.demos.su (sinbin.demos.su [194.87.0.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA11447 for ; Thu, 2 Oct 1997 01:02:55 -0700 (PDT) Received: by sinbin.demos.su id MAA13442; (8.6.12/D) Thu, 2 Oct 1997 12:01:54 +0400 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199710020801.MAA13442@sinbin.demos.su> Subject: Re: 440LX Chipset Motherboards In-Reply-To: <199710020517.PAA03772@bard.dtir.qld.gov.au> from "Phil Chadwick" at "Oct 2, 97 03:17:03 pm" X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: hardware@freebsd.org Date: Thu, 2 Oct 1997 12:01:54 +0400 (MSD) X-Mailer: ELM [version 2.4ME+ PL32 (25)] Content-Type: text Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does FreeBSD run on Intel 440LX chipset motherboards such as > the Asus P2L97-DS? and what about new intel motherboards like DK440LX with adaptec 7895 and dual pII ... ^^^^^^^^^^^^^^^^^ does fbsd/smp run on it? Alex. > > Thanks... > > > Phil > -- Phil Chadwick > Email: syspmc@dtir.qld.gov.au ,-_|\ Supervisor, UNIX Support > Phone: +61 7 3247 9239 / * Department of Training > Fax: +61 7 3247 9111 \_,-._/ and Industrial Relations > v > From owner-freebsd-hardware Thu Oct 2 04:56:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA20857 for hardware-outgoing; Thu, 2 Oct 1997 04:56:14 -0700 (PDT) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA20847 for ; Thu, 2 Oct 1997 04:56:04 -0700 (PDT) Received: from cezanne.prism.uvsq.fr (rtc102.reseau.uvsq.fr [193.51.24.18]) by soleil.uvsq.fr (8.8.6/jtpda-5.2) with ESMTP id NAA26594 for ; Thu, 2 Oct 1997 13:55:28 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.8.5/8.8.5) id NAA00324; Thu, 2 Oct 1997 13:34:32 GMT Message-ID: <19971002133432.18047@coreff.prism.uvsq.fr> Date: Thu, 2 Oct 1997 13:34:32 +0000 From: Nicolas Souchu To: hardware@FreeBSD.ORG Subject: Re: ppbus problem References: <199710011255.IAA00667@tower.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Greg Pavelcak on Wed, Oct 01, 1997 at 10:39:45AM -0400 X-Operating-System: FreeBSD coreff 2.2.1-RELEASE FreeBSD 2.2.1-RELEASE Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Oct 01, 1997 at 10:39:45AM -0400, Greg Pavelcak wrote: >> > > From: User Gp >> > > >> > > I 'm trying to install the ppbus stuff for my parallel port >> > > zip drive. The kernel compiled OK, and it has a lot to say >> > > about the drive, but fdisk and mount produce no results. >> > > Here's dmesg. Any ideas. >> > >> > Can you be more specific about "no results"? Error messages? System >> > lockup? >> >> No error messages, it just sits doing nothing, i.e. no indication (sound or >> lights of disk activity in the zip. I bring my prompt back with ^C. Then, you do not have the message "device not configured" from sd0 driver? >To follow up, I have one zip, but I had vpo.c in both >/sys/conf/files and /sys/i386/conf/files.i386 and their related >directories (DOn't ask me how.). >Now I only have vpo.c in /sys/i386/conf/files.i386, and >there's some improvement. Now I only get the probe results for the >96MB Zip. fdisk still hangs though. Should I be using some of those >flags in my kernel? I don't quite understand those. > Ok, is there a way for you to get the name of your parallel port chipset? Which release of ppbus-dist did you get? September's? You may try to set boot flags to 0x1 to get NIBBLE operating mode. -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PC's into workstations - http://www.FreeBSD.org From owner-freebsd-hardware Thu Oct 2 05:39:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA22980 for hardware-outgoing; Thu, 2 Oct 1997 05:39:47 -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 FAA22975 for ; Thu, 2 Oct 1997 05:39:44 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id IAA02582; Thu, 2 Oct 1997 08:42:25 -0400 (EDT) Date: Thu, 2 Oct 1997 08:42:25 -0400 (EDT) From: "John T. Farmer" Message-Id: <199710021242.IAA02582@sabre.goldsword.com> To: freebsd-hardware@FreeBSD.ORG, richard@pegasus.com Subject: Re: Multiple serial ports Cc: jfarmer@goldsword.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 1 Oct 1997 20:40:35 -1000 (Richard Foulk) said: > [I said...] >} Actually, there are several vendors of terminal servers that will do >} 4 to 16 serial ports in the <$1500 range (some much less than that!). >} The downside is the number of control lines available, sometimes the >} maximin port speed, and some of the "routing" type features. Check out >} Lantronix, Equinox, Chase, Stallion, some of the cheaper DEC boxes, etc. >} > >Quirky and slow. I've tested the Stallions and sent them back, and heard >others doing the same with other cheap boxes. > >They may be able to run one port at a reasonable speed, say 9600 >or 19200. More than that and they bog down and get jerky and slow. >Just one printer connection and a single interactive telnet session at >the same time becomes unbearable. > >And, do any of them have modem control? > Uh, actually, I've had good success with with several different brands for multiple terminals/printers/front-end system consoles all active at the same time. Granted, I don't try to run the ports at greater than 56kbps. Frankly, you don't need to. As to quirky, I'm not sure what you mean. Their command syntax is different from Livingston or Cisco, most resemble the older DEC terminal servers. Livingston & Co. are relative newcomers to the field. (I was buying & selling DEC terminal servers during the early '80's & they weren't new product then...) Most of the lower cost boxes that I've tested would allow _either_ hardware flow control or modem control. I've noticed that several of these vendors (Digi, Stallion, etc.) have upgraded the boxes to supply both hardware flow & modem control. Again, it comes down to what are you trying to do, what do you have to do it with, and what works for you. If you have older gear laying around (Livingston, Cisco, etc.) that _you're_ comfortable with, then use it if you want. Other's may choose differently. For this application (connecting to local &/or remote serial consoles) I _don't_ want a box that is dependant on Radius servers, high-speed links, or anything _other_ than hauling bytes back & forth. If an $800 box will do it, then I'm not going to spend $2k for one. If the requirements or imposed limitations changed, then I might make a diferent choice. For example, if I'm dealing with system consoles for a group of PC servers (a web farm for example), I'm as likely to use cheap ISA video cards & a "switch box" approach (smart or dumb switches). Example: 4 servers tied to a display/KB/mouse in the next room. A monitor, keyboard & mouse, 4 ISA cards, Cabling & switching gear, tied from a server room to an operations room next to it will have a total cost of least than $500. 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 Thu Oct 2 05:46:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA23303 for hardware-outgoing; Thu, 2 Oct 1997 05:46:14 -0700 (PDT) Received: from caliban.dihelix.com (caliban.dihelix.com [198.180.136.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA23298 for ; Thu, 2 Oct 1997 05:46:10 -0700 (PDT) Received: (from langfod@localhost) by caliban.dihelix.com (8.8.7/8.8.3) id CAA01731; Thu, 2 Oct 1997 02:44:21 -1000 (HST) Message-Id: <199710021244.CAA01731@caliban.dihelix.com> Subject: Re: ppbus problem In-Reply-To: <19971002133432.18047@coreff.prism.uvsq.fr> from Nicolas Souchu at "Oct 2, 97 01:34:32 pm" To: Nicolas.Souchu@prism.uvsq.fr (Nicolas Souchu) Date: Thu, 2 Oct 1997 02:44:21 -1000 (HST) Cc: hardware@FreeBSD.ORG From: "David Langford" X-blank-line: This space intentionaly left blank. 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 Couple of quick things I learned when doing this on a current system recently. 1) Be sure you BIOS is set to EPP and NOT ECP. - for me everything looked fine but it didnt probe the drive 2) dont forget to have sd in your kernel - ditto (actually it took me awhile to figure this out) 3) be sure ppc is ENABLED in the kernel not disabled :) - Doh!(TM) >>> > > I 'm trying to install the ppbus stuff for my parallel port >>> > > zip drive. The kernel compiled OK, and it has a lot to say >>> > > about the drive, but fdisk and mount produce no results. >>> > > Here's dmesg. Any ideas. From owner-freebsd-hardware Thu Oct 2 08:39:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA02881 for hardware-outgoing; Thu, 2 Oct 1997 08:39:50 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA02871; Thu, 2 Oct 1997 08:39:44 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id BAA00683; Fri, 3 Oct 1997 01:07:14 +0930 (CST) Message-Id: <199710021537.BAA00683@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: User Gp cc: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Problems with ppbus and ||-port zip In-reply-to: Your message of "Wed, 01 Oct 1997 18:59:32 -0400." <199710012259.SAA00554@tower.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Oct 1997 01:07:13 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I am still having trouble with my ||-port zip, though looking better > now than before. My problem is if I try fdisk > /dev/sd0 or mount /dev/sd0, the machine just hangs. I waited 15 > minutes for an error message but got nothing. I was able to get my > prompt back with ^C. Try : # stty status ^T # disklabel -rwB sd0 auto If the disklabel command hangs, hit ^T and you should see something like: load: 0.47 cmd: disklabel 29432 [vnread] 0.00u 0.00s 0% 20k It would be very useful to know what the word in [] is in your case. > controller ppbus0 # ppbus stuff > controller vpo0 at ppbus0 > device nlpt0 at ppbus0 > device ppi0 at ppbus0 > device plip0 at ppbus0 > > controller ppc0 at isa? port 0x278 irq 12 flags 0x1 vector ppcintr > > > #device lpt0 at isa? port "IO_LPT2" tty irq 12 vector lptintr > device lpt1 at isa? port "IO_LPT1" tty irq 7 vector lptintr I suspect that it would be a Very Bad Idea to have the lpt driver in your kernel at the same time as the ppbus code. Also, are you sure about IRQ 12 for the first port? mike From owner-freebsd-hardware Thu Oct 2 10:02:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08811 for hardware-outgoing; Thu, 2 Oct 1997 10:02:47 -0700 (PDT) Received: from tower.my.domain (nscs29p5.remote.umass.edu [128.119.179.174]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08779; Thu, 2 Oct 1997 10:02:32 -0700 (PDT) Received: from tower.my.domain (localhost [127.0.0.1]) by tower.my.domain (8.8.7/8.8.7) with ESMTP id MAA00290; Thu, 2 Oct 1997 12:59:35 -0400 (EDT) Message-Id: <199710021659.MAA00290@tower.my.domain> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nicolas.Souchu@prism.uvsq.fr cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: ppbus problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 12:59:35 -0400 From: User Gp Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Oct 01, 1997 at 10:39:45AM -0400, Greg Pavelcak wrote: >> > > From: User Gp >> > > >> > > I 'm trying to install the ppbus stuff for my parallel port >> > > zip drive. The kernel compiled OK, and it has a lot to say >> > > about the drive, but fdisk and mount produce no results. >> > > Here's dmesg. Any ideas. >> > >> > Can you be more specific about "no results"? Error messages? System >> > lockup? >> >> No error messages, it just sits doing nothing, i.e. no indication (sound or >> lights of disk activity in the zip. I bring my prompt back with ^C. >Then, you do not have the message "device not configured" from sd0 driver? Nope. I waited about 15 minutes for something to show. >Ok, is there a way for you to get the name of your parallel port chipset? >Which release of ppbus-dist did you get? September's? >You may try to set boot flags to 0x1 to get NIBBLE operating mode. I have no qualms about opening the box, I just wouldn't know what to look for. I noted ALi M5235 PAI 980 75ccktt because it's close to my parallel port and WINBOND W83877F WINBOND W25P022AF6 708AC265117302 and 721AB2712575031E because my isa io card has winbond stuff on it so I thought it might be relevant. The board is a M-Tech R534F, if that helps I started over. Got ppb970923.tgz, unzipped and followed installation instructions. Recompiled my kernel with 0x1 flag. Still hangs with fdisk or mount. Here are parts of my latest kernel file and dmesg. I really appreciate your attention to this problem. Greg ppc0 at 0x278 irq 12 flags 0x1 on isa ppc0: Generic chipset in NIBBLE mode plip0: on ppbus 0 nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 vpo0: on ppbus 0 scbus0 at vpo0 bus 0 sd0 at scbus0 target 6 lun 0 sd0: type 0 removable SCSI 2 sd0: Direct-Access sd0: UNIT ATTENTION asc:28,0 sd0: Not ready to ready transition, medium may have changed 862MB (196608 4592 byte sectors) controller scbus0 device sd0 controller ppbus0 # ppbus stuff controller vpo0 at ppbus0 device new_lpt0 at ppbus0 device ppi0 at ppbus0 device plip0 at ppbus0 controller ppc0 at isa? port 0x278 irq 12 flags 0x1 vector ppcintr #device lpt0 at isa? port "IO_LPT2" tty irq 12 vector lptintr device lpt1 at isa? port "IO_LPT1" tty irq 7 vector lptintr From owner-freebsd-hardware Thu Oct 2 10:03:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08845 for hardware-outgoing; Thu, 2 Oct 1997 10:03:18 -0700 (PDT) Received: from leaf.lumiere.net (j@leaf.lumiere.net [204.188.120.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08836 for ; Thu, 2 Oct 1997 10:03:10 -0700 (PDT) Received: from localhost (j@localhost) by leaf.lumiere.net (8.8.7/8.8.5) with SMTP id KAA21324 for ; Thu, 2 Oct 1997 10:03:00 -0700 (PDT) Date: Thu, 2 Oct 1997 10:03:00 -0700 (PDT) From: Jesse To: freebsd-hardware@freebsd.org Subject: Changing motherboard & ram, any warnings? 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 Hi, In a week or so I'm going to be switching some hardware around in my FreeBSD 2.2.2-RELEASE system. I'm going to be changing the motherboard from an Intel Triton III (VX chipset) motherboard to a Megatrends HX83 (HX chipset) motherboard. I'll also be changing from the 1 32MB SDRAM DIMM I have right now to 2 32MB EDO SIMMs. Are there any changes I need to make in preparation or things I should worry about, either because of the new motherboard or the increase from 32 to 64MBs of RAM? Thanks a lot. --- Jesse http://www.lumiere.net/ From owner-freebsd-hardware Thu Oct 2 10:36:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA10733 for hardware-outgoing; Thu, 2 Oct 1997 10:36:44 -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 KAA10725 for ; Thu, 2 Oct 1997 10:36:40 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xGpAD-0002xP-00; Thu, 2 Oct 1997 10:35:49 -0700 Date: Thu, 2 Oct 1997 10:35:47 -0700 (PDT) From: Tom To: Richard Foulk cc: freebsd-hardware@freebsd.org Subject: Re: Multiple serial ports In-Reply-To: <199710020640.UAA04547@pegasus.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 Wed, 1 Oct 1997, Richard Foulk wrote: > } Actually, there are several vendors of terminal servers that will do > } 4 to 16 serial ports in the <$1500 range (some much less than that!). > } The downside is the number of control lines available, sometimes the > } maximin port speed, and some of the "routing" type features. Check out > } Lantronix, Equinox, Chase, Stallion, some of the cheaper DEC boxes, etc. > > Quirky and slow. I've tested the Stallions and sent them back, and heard > others doing the same with other cheap boxes. > > They may be able to run one port at a reasonable speed, say 9600 > or 19200. More than that and they bog down and get jerky and slow. > Just one printer connection and a single interactive telnet session at > the same time becomes unbearable. > > And, do any of them have modem control? Ugh... why bother with this stuff? You can get a used Livingston PM2e/30 with 30 RS-232 serial ports (full control lines), full PPP/SLIP (including auto-detection of PPP) and routing capabilities (including OSPF) for $1500. They can run all 30 ports at 115200 simultaneously. > Richard Tom From owner-freebsd-hardware Thu Oct 2 10:47:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA11375 for hardware-outgoing; Thu, 2 Oct 1997 10:47:32 -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 KAA11369 for ; Thu, 2 Oct 1997 10:47:28 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.71 #1) id 0xGpKq-0002xj-00; Thu, 2 Oct 1997 10:46:48 -0700 Date: Thu, 2 Oct 1997 10:46:46 -0700 (PDT) From: Tom To: "John T. Farmer" cc: freebsd-hardware@freebsd.org, richard@pegasus.com, jfarmer@goldsword.com Subject: Re: Multiple serial ports In-Reply-To: <199710021242.IAA02582@sabre.goldsword.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, 2 Oct 1997, John T. Farmer wrote: > servers. Livingston & Co. are relative newcomers to the field. (I was > buying & selling DEC terminal servers during the early '80's & they > weren't new product then...) The Livingston PM-11 (no longer made) came out in '82. You can get them used for $300 now. > I _don't_ want a box that is dependant on Radius servers, high-speed Who is? Livingston stuff certainly isn't. IF you define a RADIUS server, it is checked AFTER the local user table. Tom From owner-freebsd-hardware Thu Oct 2 10:52:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA11719 for hardware-outgoing; Thu, 2 Oct 1997 10:52:18 -0700 (PDT) Received: from tower.my.domain (nscs27p17.remote.umass.edu [128.119.179.144]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA11697; Thu, 2 Oct 1997 10:52:06 -0700 (PDT) Received: from tower.my.domain (localhost [127.0.0.1]) by tower.my.domain (8.8.7/8.8.7) with ESMTP id NAA00231; Thu, 2 Oct 1997 13:49:20 -0400 (EDT) Message-Id: <199710021749.NAA00231@tower.my.domain> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike Smith cc: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Problems with ppbus and ||-port zip In-reply-to: Your message of "Fri, 03 Oct 1997 01:07:13 +0930." <199710021537.BAA00683@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 13:49:20 -0400 From: User Gp Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > I am still having trouble with my ||-port zip, though looking better > > now than before. My problem is if I try fdisk > > /dev/sd0 or mount /dev/sd0, the machine just hangs. I waited 15 > > minutes for an error message but got nothing. I was able to get my > > prompt back with ^C. > > Try : > > # stty status ^T > # disklabel -rwB sd0 auto > > If the disklabel command hangs, hit ^T and you should see something > like: > > load: 0.47 cmd: disklabel 29432 [vnread] 0.00u 0.00s 0% 20k > > It would be very useful to know what the word in [] is in your case. > > > controller ppbus0 # ppbus stuff > > controller vpo0 at ppbus0 > > device nlpt0 at ppbus0 > > device ppi0 at ppbus0 > > device plip0 at ppbus0 > > > > controller ppc0 at isa? port 0x278 irq 12 flags 0x1 vector ppcintr > > > > > > #device lpt0 at isa? port "IO_LPT2" tty irq 12 vector lptintr > > device lpt1 at isa? port "IO_LPT1" tty irq 7 vector lptintr > > I suspect that it would be a Very Bad Idea to have the lpt driver in > your kernel at the same time as the ppbus code. Also, are you sure > about IRQ 12 for the first port? > > mike > > OK. I commented out lpt1 also. Taking a cue from the BIOS, which gives me 0x278 irq 5 and 0x378 irq 7 as options for on board ||, I rewrote ppc0 at the latter. As you probably guessed from my kernel, I was trying to have two || ports, but I took the other i/o card out so as not to confuse the issue. Still no results with fdisk or mount. Disklabel hangs also. Output at ^T: load: 0.07 cmd disklabel 664 [ppbreq] 0.00u 0.00s 0% 148k Thanks for your help with this. Greg From owner-freebsd-hardware Thu Oct 2 11:00:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA12198 for hardware-outgoing; Thu, 2 Oct 1997 11:00:29 -0700 (PDT) Received: from po7.andrew.cmu.edu (PO7.ANDREW.CMU.EDU [128.2.10.107]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA12192 for ; Thu, 2 Oct 1997 11:00:25 -0700 (PDT) Received: (from postman@localhost) by po7.andrew.cmu.edu (8.8.5/8.8.2) id OAA20177 for freebsd-hardware@freebsd.org; Thu, 2 Oct 1997 14:00:22 -0400 (EDT) Received: via switchmail; Thu, 2 Oct 1997 14:00:22 -0400 (EDT) Received: from chamonix.weh.andrew.cmu.edu via qmail ID ; Thu, 2 Oct 1997 13:59:37 -0400 (EDT) Received: from chamonix.weh.andrew.cmu.edu via qmail ID ; Thu, 2 Oct 1997 13:59:36 -0400 (EDT) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.chamonix.weh.andrew.cmu.edu.sun4x.55 via MS.5.6.chamonix.weh.andrew.cmu.edu.sun4_51; Thu, 2 Oct 1997 13:59:36 -0400 (EDT) Message-ID: Date: Thu, 2 Oct 1997 13:59:36 -0400 (EDT) From: Timothy J Kniveton To: freebsd-hardware@freebsd.org Subject: HW Sources Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. After running FreeBSD on my 486/66 for 4 years, I am looking to put together a new system. I'm soliciting comments or suggestions from anyone as to how they think this system will work w/FBSD, or how I could improve it. I would like to get the ASUS TX97-XE mainboard with an AMD K6 200MHz (worth $100 more for the 233MHz?), half-height ATX tower, 32M EDO RAM, Matrox Mystique 220 w/ 4M, Quantum 3.2G IDE(DMA33), floppy, 24x IDE CD-ROM, mouse/kb. I will either continue to use the Viewsonic 7 17" monitor I have, or more likely, get a new one (suggestions on a cheap 17"?). I'll also keep the SMC ISA 10bT ethernet card. Although I was running SCSI on my old system, it is an EISA adapter so I will not be able to use it on the new one. I might get PCI SCSI later, but I think IDE (on the mainboard) will suit me for now. I was thinking of going with Treasure Chest computers since they allow a totally customizable system, but at $1100 (sans monitor), their prices don't seem all that competitive, so I'm willing to consider alternatives. I have no qualms about putting together the parts if I could find them cheaper, but I am interested in having at least a 3-yr warrantee on them (which TC offers). Please send me any helpful info or comments you have. Thanks for reading all this! -Tim From owner-freebsd-hardware Thu Oct 2 16:11:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA00130 for hardware-outgoing; Thu, 2 Oct 1997 16:11:37 -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 QAA00114 for ; Thu, 2 Oct 1997 16:11:29 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id TAA04538; Thu, 2 Oct 1997 19:14:03 -0400 (EDT) Date: Thu, 2 Oct 1997 19:14:03 -0400 (EDT) From: "John T. Farmer" Message-Id: <199710022314.TAA04538@sabre.goldsword.com> To: jfarmer@sabre.goldsword.com, tom@sdf.com Subject: Re: Multiple serial ports Cc: freebsd-hardware@FreeBSD.ORG, jfarmer@goldsword.com, richard@pegasus.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Oct 1997 10:46:46 -0700 (PDT) Tom said: >On Thu, 2 Oct 1997, John T. Farmer wrote: >> servers. Livingston & Co. are relative newcomers to the field. (I was >> buying & selling DEC terminal servers during the early '80's & they >> weren't new product then...) > > The Livingston PM-11 (no longer made) came out in '82. You can get them >used for $300 now. Yes, I know. At the time, it was a _very_ unknown company/device. I view it as a "well done!" for Livingston to have taken such a major share of the market in 15 years. >> I _don't_ want a box that is dependant on Radius servers, high-speed > > Who is? Livingston stuff certainly isn't. IF you define a RADIUS >server, it is checked AFTER the local user table. For this type of application, I would design it as a totally seperate network from any publicly accessible network. As such, I usually setup ports to auto-connect, and don't setup any user tables unless it's required. The major points I was making are: 1. If you have more expensive older gear that you want to use, use it. 2. If there anen't any requirements for the features of the more expensive boxes, then look at cheaper, easiler solutions. 3. Sometimes using the same equipment everywhere is better than saving money. Sometimes different is better, sometimes worse. 4. No ruleset will give the correct answer every time. YMMV. 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 Thu Oct 2 18:54:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA08481 for hardware-outgoing; Thu, 2 Oct 1997 18:54:59 -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 SAA08472 for ; Thu, 2 Oct 1997 18:54:54 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id SAA21290; Thu, 2 Oct 1997 18:54:13 -0700 (PDT) Message-ID: <19971002185413.04394@hydrogen.nike.efn.org> Date: Thu, 2 Oct 1997 18:54:13 -0700 From: John-Mark Gurney To: "John T. Farmer" Cc: freebsd-hardware@FreeBSD.ORG, richard@pegasus.com, jfarmer@goldsword.com Subject: Re: Multiple serial ports References: <199710021242.IAA02582@sabre.goldsword.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199710021242.IAA02582@sabre.goldsword.com>; from John T. Farmer on Thu, Oct 02, 1997 at 08:42:25AM -0400 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 John T. Farmer scribbled this message on Oct 2: > Uh, actually, I've had good success with with several different brands > for multiple terminals/printers/front-end system consoles all active at > the same time. Granted, I don't try to run the ports at greater than > 56kbps. Frankly, you don't need to. why exactly?? a friend was dialed into my machine (using a 14.4k internal!!) and we were sending some text down the line.. and he was able to get 8kbytes/sec+ over the link.. and this is with a zoom 14.4k, and a zoom 28.8k modem... if I wasn't running the zoom at 115.2kbps, we wouldn't of been able to do that... and instead would of slowed a 14.4kbps call... (think if it was a 28.8k??) plus also, there is a MAJOR reduction in the latency of a connection when you run the speed faster.. for example, when another friend upgraded to a Supra 288kbps modem, and I was still on my Supra 14.4k modem.. the latency dropped 50ms JUST because his modem->computer rate increased... and then when I went to 28.8k also (both of these are external), we dropped another 70-100ms in latency... this also brings up that kernel ppp (pppd) is usually much lower latency than iij-ppp... the friend with his internal 14.4k (first example) and my extern zoom 28.8k, we were able to knock off at least 20ms off ping times because he went from iij-ppp over to ppp... the last time we had the connection up (he's moved, and much better connected) we were able to do 140ms ping times over the 14.4k connection... these may not seem much, but when your used to do typing of a wireless ricochet modem, when at BEST will give you 350ms, mostly 400-450ms, you REALLY becom aware of the problems with latency... of course, then you just need to go FR or ISDN, and it'll be much better.. 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 Thu Oct 2 20:55:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA14090 for hardware-outgoing; Thu, 2 Oct 1997 20:55:42 -0700 (PDT) Received: from gforce.bellsouth.net (host-32-96-78-142.msy.bellsouth.net [32.96.78.142]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA14082 for ; Thu, 2 Oct 1997 20:55:38 -0700 (PDT) Received: from gforce (localhost [127.0.0.1]) by gforce.bellsouth.net (8.8.7/8.8.5) with ESMTP id WAA02394 for ; Thu, 2 Oct 1997 22:54:35 -0500 (CDT) Message-Id: <199710030354.WAA02394@gforce.bellsouth.net> X-Mailer: exmh version 2.0zeta 7/24/97 From: Glenn Johnson To: freebsd-hardware@freebsd.org Subject: AMD and Cyrix chips Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Oct 1997 22:54:32 -0500 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am planning on replacing my AMD K5-75 chip with either an AMD K6-166 or a Cyrix 6x86MX P200 running at 166 MHz. Does anyone have any recommendations on which one I should upgrade to? I know there were some problems with the K6 that seem to have been resolved. Are there any issues with the Cyrix chip? Thanks. -- Glenn Johnson gljohns@bellsouth.net From owner-freebsd-hardware Thu Oct 2 23:29:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22795 for hardware-outgoing; Thu, 2 Oct 1997 23:29:22 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca14-03.ix.netcom.com [204.32.168.67]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA22786 for ; Thu, 2 Oct 1997 23:29:18 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id XAA12554; Thu, 2 Oct 1997 23:29:11 -0700 (PDT) Date: Thu, 2 Oct 1997 23:29:11 -0700 (PDT) Message-Id: <199710030629.XAA12554@silvia.HIP.Berkeley.EDU> To: j@lumiere.net CC: freebsd-hardware@freebsd.org In-reply-to: (message from Jesse on Thu, 2 Oct 1997 10:03:00 -0700 (PDT)) Subject: Re: Changing motherboard & ram, any warnings? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * In a week or so I'm going to be switching some hardware around in my * FreeBSD 2.2.2-RELEASE system. I'm going to be changing the motherboard * from an Intel Triton III (VX chipset) motherboard to a Megatrends HX83 (HX * chipset) motherboard. I'll also be changing from the 1 32MB SDRAM DIMM I * have right now to 2 32MB EDO SIMMs. * * Are there any changes I need to make in preparation or things I should * worry about, either because of the new motherboard or the increase from 32 * to 64MBs of RAM? Yes. Your games may run faster. Be careful not to be shot down by klingons. Satoshi From owner-freebsd-hardware Fri Oct 3 04:36:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA08292 for hardware-outgoing; Fri, 3 Oct 1997 04:36:40 -0700 (PDT) Received: from zeus.gel.usherb.ca (zeus.gel.usherb.ca [132.210.70.7]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA08283 for ; Fri, 3 Oct 1997 04:36:34 -0700 (PDT) Received: from castor.gel.usherb.ca by zeus.gel.usherb.ca (4.1/SMI-4.1) id AA12627; Fri, 3 Oct 97 07:36:26 EDT Received: by castor.gel.usherb.ca (SMI-8.6/SMI-SVR4) id HAA21847; Fri, 3 Oct 1997 07:36:26 -0400 Date: Fri, 3 Oct 1997 07:36:25 -0400 (EDT) From: "Alex.Boisvert" To: Glenn Johnson Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: AMD and Cyrix chips In-Reply-To: <199710030354.WAA02394@gforce.bellsouth.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 Thu, 2 Oct 1997, Glenn Johnson wrote: > I am planning on replacing my AMD K5-75 chip with either an AMD K6-166 or a > Cyrix 6x86MX P200 running at 166 MHz. Does anyone have any recommendations on > which one I should upgrade to? I know there were some problems with the K6 > that seem to have been resolved. Are there any issues with the Cyrix chip? I run a few systems here with a IBM/Cyrix 6x86L P200+. The Cyrix P200+, when run at 2x75 MHz is *very* fast but, with a data bus speed of 75 MHz it's very picky about which memory/cards work well. You'll want to have SDRAM at this speed and maybe avoid early Adaptec 2940 PCI controllers since they have problems at this speed. As you said, you can set the speed to 2x66 MHz which will give you good performance still, and avoid speed problems altogether. I have overclocked a CPU here at 3x60 MHz and it's very fast on computation (but i/o is not comparable to 75 MHz). The boards we use are Matsonic MS-5120 (see www.eurone.com). Don't have any experience with AMD. Regards, Alex Boisvert --- FreeBSD: Decouvrez la puissance de votre ordinateur - www.freebsd.org From owner-freebsd-hardware Fri Oct 3 07:19:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA16265 for hardware-outgoing; Fri, 3 Oct 1997 07:19:50 -0700 (PDT) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA16202 for ; Fri, 3 Oct 1997 07:19:31 -0700 (PDT) Received: from cezanne.prism.uvsq.fr (rtc105.reseau.uvsq.fr [193.51.24.21]) by soleil.uvsq.fr (8.8.6/jtpda-5.2) with ESMTP id QAA21590 ; Fri, 3 Oct 1997 16:14:45 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.8.5/8.8.5) id KAA00255; Fri, 3 Oct 1997 10:35:40 GMT Message-ID: <19971003103539.63667@coreff.prism.uvsq.fr> Date: Fri, 3 Oct 1997 10:35:39 +0000 From: Nicolas Souchu To: David Langford Cc: hardware@FreeBSD.ORG Subject: Re: ppbus problem References: <19971002133432.18047@coreff.prism.uvsq.fr> <199710021244.CAA01731@caliban.dihelix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199710021244.CAA01731@caliban.dihelix.com>; from David Langford on Thu, Oct 02, 1997 at 02:44:21AM -1000 X-Operating-System: FreeBSD coreff 2.2.1-RELEASE FreeBSD 2.2.1-RELEASE Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Oct 02, 1997 at 02:44:21AM -1000, David Langford wrote: >Couple of quick things I learned when doing this on a current >system recently. > >1) Be sure you BIOS is set to EPP and NOT ECP. > - for me everything looked fine but it didnt probe the drive It didn't probe NIBBLE or PS2 mode either? Did the ppc driver say "ppc: port not present at ...". If not, the answer is 3) then. Otherwise, even in ECP mode, ppc should have found something. >2) dont forget to have sd in your kernel > - ditto (actually it took me awhile to figure this out) >3) be sure ppc is ENABLED in the kernel not disabled :) > - Doh!(TM) -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PC's into workstations - http://www.FreeBSD.org From owner-freebsd-hardware Fri Oct 3 08:30:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA21105 for hardware-outgoing; Fri, 3 Oct 1997 08:30:22 -0700 (PDT) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA21075; Fri, 3 Oct 1997 08:30:11 -0700 (PDT) Received: from cezanne.prism.uvsq.fr (rtc105.reseau.uvsq.fr [193.51.24.21]) by soleil.uvsq.fr (8.8.6/jtpda-5.2) with ESMTP id RAA23688 ; Fri, 3 Oct 1997 17:08:36 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.8.5/8.8.5) id RAA00595; Fri, 3 Oct 1997 17:09:15 GMT Message-ID: <19971003170915.44659@coreff.prism.uvsq.fr> Date: Fri, 3 Oct 1997 17:09:15 +0000 From: Nicolas Souchu To: Greg Cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: ppbus problems References: <199710021659.MAA00290@tower.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199710021659.MAA00290@tower.my.domain>; from User Gp on Thu, Oct 02, 1997 at 12:59:35PM -0400 X-Operating-System: FreeBSD coreff 2.2.1-RELEASE FreeBSD 2.2.1-RELEASE Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Oct 02, 1997 at 12:59:35PM -0400, User Gp wrote: >because it's close to my parallel port and > > WINBOND W83877F WINBOND W25P022AF6 ^^^^^^^ here it is! I'm working on w83877 detection/configuration. Yet, try to force EPP mode with flag 0x3... this may avoid some timing problems. > >ppc0 at 0x278 irq 12 flags 0x1 on isa >ppc0: Generic chipset in NIBBLE mode >plip0: on ppbus 0 >nlpt0: on ppbus 0 >nlpt0: Interrupt-driven port >ppi0: on ppbus 0 >vpo0: on ppbus 0 >scbus0 at vpo0 bus 0 >sd0 at scbus0 target 6 lun 0 >sd0: type 0 removable SCSI 2 >sd0: Direct-Access >sd0: UNIT ATTENTION asc:28,0 >sd0: Not ready to ready transition, medium may have changed >862MB (196608 4592 byte sectors) I suspect data corruption... Please, try without any disk inside the drive during boot. Try fdisk once the system is started (without any disk either), you should get "medium not present" error. Then try with a disk inserted. I've noticed in one of your other mails that vpo driver hangs when it requests the ppbus (I remember [ppbreq])... I'm working on some ioctls that would allow us to query the state of the bus and debug it more efficiently. -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PC's into workstations - http://www.FreeBSD.org From owner-freebsd-hardware Fri Oct 3 08:58:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA23150 for hardware-outgoing; Fri, 3 Oct 1997 08:58:22 -0700 (PDT) Received: from solist. ([193.219.246.204]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id IAA23144 for ; Fri, 3 Oct 1997 08:58:17 -0700 (PDT) Received: from partitur.se by solist. (SMI-8.6/SMI-SVR4) id RAA00882; Fri, 3 Oct 1997 17:56:54 +0200 Message-ID: <343515C6.7B742E8E@partitur.se> Date: Fri, 03 Oct 1997 17:56:54 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.5.1 sun4u) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: IDE CD changer TEAC CD C68-R, any hope? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Is it possible to get an IDE CD changer to work w/ FreeBSD? In my case the brand is a TEAC C68-R. I read about the NEC that works in "single mode", and about the SCSI ch device. Just wondering if there's any hope to get the IDE to work? Regards, Palle From owner-freebsd-hardware Fri Oct 3 09:50:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA26964 for hardware-outgoing; Fri, 3 Oct 1997 09:50:07 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA26853 for ; Fri, 3 Oct 1997 09:49:35 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id SAA03686; Fri, 3 Oct 1997 18:49:24 +0200 (MEST) From: Søren Schmidt Message-Id: <199710031649.SAA03686@sos.freebsd.dk> Subject: Re: IDE CD changer TEAC CD C68-R, any hope? In-Reply-To: <343515C6.7B742E8E@partitur.se> from Palle Girgensohn at "Oct 3, 97 05:56:54 pm" To: girgen@partitur.se (Palle Girgensohn) Date: Fri, 3 Oct 1997 18:49:24 +0200 (MEST) Cc: freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Palle Girgensohn who wrote: > Hi, > > Is it possible to get an IDE CD changer to work w/ FreeBSD? In my case > the brand is a TEAC C68-R. I read about the NEC that works in "single > mode", and about the SCSI ch device. Just wondering if there's any hope > to get the IDE to work? It should work with just one CD in the drive. If you want to use all 6 CD's in the changer, I'll have to a drive to do the development on... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hardware Fri Oct 3 10:02:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA27921 for hardware-outgoing; Fri, 3 Oct 1997 10:02:46 -0700 (PDT) Received: from mexico.brainstorm.eu.org (mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA27898 for ; Fri, 3 Oct 1997 10:02:31 -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 TAA13528 for ; Fri, 3 Oct 1997 19:01:47 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id TAA22797 for freebsd-hardware@FreeBSD.ORG; Fri, 3 Oct 1997 19:01:33 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id SAA08689; Fri, 3 Oct 1997 18:59:46 +0200 (CEST) Message-ID: <19971003185946.48439@keltia.freenix.fr> Date: Fri, 3 Oct 1997 18:59:46 +0200 From: Ollivier Robert To: freebsd-hardware@FreeBSD.ORG Subject: Re: AMD and Cyrix chips References: <199710030354.WAA02394@gforce.bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Alex.Boisvert on Fri, Oct 03, 1997 at 07:36:25AM -0400 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Alex.Boisvert: > I run a few systems here with a IBM/Cyrix 6x86L P200+. The Cyrix P200+, > when run at 2x75 MHz is *very* fast but, with a data bus speed of 75 MHz > it's very picky about which memory/cards work well. You'll want to have > SDRAM at this speed and maybe avoid early Adaptec 2940 PCI controllers It really depends on the motherboard... My ASUS T2P4 is happily running at 83 MHz and all PCI cards (Millenium, PCI-875 & SC-200) have no problem with it. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997 From owner-freebsd-hardware Fri Oct 3 10:58:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA01489 for hardware-outgoing; Fri, 3 Oct 1997 10:58:04 -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 KAA01468; Fri, 3 Oct 1997 10:57:55 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA03678; Fri, 3 Oct 1997 10:46:43 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd003675; Fri Oct 3 17:46:38 1997 Message-ID: <34352F41.237C228A@whistle.com> Date: Fri, 03 Oct 1997 10:45:37 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Nicolas Souchu CC: Greg , hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: ppbus problems References: <199710021659.MAA00290@tower.my.domain> <19971003170915.44659@coreff.prism.uvsq.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nicolas Souchu wrote: > > On Thu, Oct 02, 1997 at 12:59:35PM -0400, User Gp wrote: > >because it's close to my parallel port and > > > > WINBOND W83877F WINBOND W25P022AF6 > ^^^^^^^ > here it is! > > I'm working on w83877 detection/configuration. Yet, try to > force EPP mode with flag 0x3... this may avoid some timing > problems. I have the manual for this chip becasue we use it in our product. do you need any help? There is a way to detect for this chip.. > > > > >ppc0 at 0x278 irq 12 flags 0x1 on isa > >ppc0: Generic chipset in NIBBLE mode > >plip0: on ppbus 0 > >nlpt0: on ppbus 0 > >nlpt0: Interrupt-driven port > >ppi0: on ppbus 0 > >vpo0: on ppbus 0 > >scbus0 at vpo0 bus 0 > >sd0 at scbus0 target 6 lun 0 > >sd0: type 0 removable SCSI 2 > >sd0: Direct-Access > >sd0: UNIT ATTENTION asc:28,0 > >sd0: Not ready to ready transition, medium may have changed > >862MB (196608 4592 byte sectors) > > I suspect data corruption... Please, try without any disk inside the drive > during boot. Try fdisk once the system is started (without any disk either), > you should get "medium not present" error. Then try with a disk inserted. > > I've noticed in one of your other mails that vpo driver hangs when it requests > the ppbus (I remember [ppbreq])... I'm working on some ioctls that would > allow us to query the state of the bus and debug it more efficiently. > > -- > Nicolas.Souchu@prism.uvsq.fr > FreeBSD - Turning PC's into workstations - http://www.FreeBSD.org From owner-freebsd-hardware Fri Oct 3 11:21:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA03041 for hardware-outgoing; Fri, 3 Oct 1997 11:21:39 -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 LAA03031 for ; Fri, 3 Oct 1997 11:21:34 -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 OAA04935 for ; Fri, 3 Oct 1997 14:21:31 -0400 (EDT) Received: from localhost (jlixfeld@localhost) by thor.idirect.com (8.6.12/8.6.12) with SMTP id OAA05076 for ; Fri, 3 Oct 1997 14:21:30 -0400 X-Authentication-Warning: thor.idirect.com: jlixfeld owned process doing -bs Date: Fri, 3 Oct 1997 14:21:30 -0400 (EDT) From: Jason Lixfeld To: freebsd-hardware@freebsd.org Subject: 2.2.2 & Pentium II 233Mhz 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 any alterante kernel compile options needed to support this CPU or is it automatic? TiA! From owner-freebsd-hardware Fri Oct 3 14:31:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA13857 for hardware-outgoing; Fri, 3 Oct 1997 14:31:21 -0700 (PDT) Received: from rfd1.oit.umass.edu (mailhub.oit.umass.edu [128.119.175.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA13852; Fri, 3 Oct 1997 14:31:16 -0700 (PDT) Received: from lessing.oit.umass.edu by rfd1.oit.umass.edu (PMDF V5.1-10 #20973) with ESMTP id <0EHH00590VRTQM@rfd1.oit.umass.edu>; Fri, 3 Oct 1997 17:31:06 -0400 (EDT) Received: from localhost (gp@localhost) by lessing.oit.umass.edu (8.8.3/8.8.6) with SMTP id RAA19557; Fri, 03 Oct 1997 17:31:04 -0400 (EDT) Date: Fri, 03 Oct 1997 17:31:03 -0400 (EDT) From: Greg Pavelcak Subject: Re: ppbus problems In-reply-to: <34352F41.237C228A@whistle.com> To: Nicolas Souchu Cc: Nicolas Souchu , Greg , hardware@FreeBSD.ORG, questions@FreeBSD.ORG 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 ppbus problem update edited by me (Greg) informing Mr. Souchu of results. Using ppbus, I got this dmesg and system would just hang when I tried fdisk. ppc0 at 0x278 irq 12 flags 0x1 on isa ppc0: Generic chipset in NIBBLE mode plip0: on ppbus 0 nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 vpo0: on ppbus 0 scbus0 at vpo0 bus 0 sd0 at scbus0 target 6 lun 0 sd0: type 0 removable SCSI 2 sd0: Direct-Access sd0: UNIT ATTENTION asc:28,0 sd0: Not ready to ready transition, medium may have changed 862MB (196608 4592 byte sectors) >Nicolas Souchu wrote: > > I suspect data corruption... Please, try without any disk inside the drive > during boot. Try fdisk once the system is started (without any disk either), > you should get "medium not present" error. Then try with a disk inserted. > > -- > Nicolas.Souchu@prism.uvsq.fr > FreeBSD - Turning PC's into workstations - http://www.FreeBSD.org > I tried this. I don't remeber the boot message when I booted without the disk, but fdisk still hung. I did not get "medium not present". I've since built a kernel with ppa3. I'm having better luck with that. Of four disks, I was able to fdisk all of them, mount and ls 2 of them (the other 2 I could apparently mount, but they showed nothing on ls and I know there's stuff there) and copied some stuff from one to my hard drive. These were all msdos formatted. I couldn't disklabel any of them. Something about no available space. Anyway thanks for all the help. I'm willing to keep trying with ppbus, if you have any other ideas. Greg From owner-freebsd-hardware Fri Oct 3 14:33:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA13857 for hardware-outgoing; Fri, 3 Oct 1997 14:31:21 -0700 (PDT) Received: from rfd1.oit.umass.edu (mailhub.oit.umass.edu [128.119.175.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA13852; Fri, 3 Oct 1997 14:31:16 -0700 (PDT) Received: from lessing.oit.umass.edu by rfd1.oit.umass.edu (PMDF V5.1-10 #20973) with ESMTP id <0EHH00590VRTQM@rfd1.oit.umass.edu>; Fri, 3 Oct 1997 17:31:06 -0400 (EDT) Received: from localhost (gp@localhost) by lessing.oit.umass.edu (8.8.3/8.8.6) with SMTP id RAA19557; Fri, 03 Oct 1997 17:31:04 -0400 (EDT) Date: Fri, 03 Oct 1997 17:31:03 -0400 (EDT) From: Greg Pavelcak Subject: Re: ppbus problems In-reply-to: <34352F41.237C228A@whistle.com> To: Nicolas Souchu Cc: Nicolas Souchu , Greg , hardware@FreeBSD.ORG, questions@FreeBSD.ORG 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 ppbus problem update edited by me (Greg) informing Mr. Souchu of results. Using ppbus, I got this dmesg and system would just hang when I tried fdisk. ppc0 at 0x278 irq 12 flags 0x1 on isa ppc0: Generic chipset in NIBBLE mode plip0: on ppbus 0 nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 vpo0: on ppbus 0 scbus0 at vpo0 bus 0 sd0 at scbus0 target 6 lun 0 sd0: type 0 removable SCSI 2 sd0: Direct-Access sd0: UNIT ATTENTION asc:28,0 sd0: Not ready to ready transition, medium may have changed 862MB (196608 4592 byte sectors) >Nicolas Souchu wrote: > > I suspect data corruption... Please, try without any disk inside the drive > during boot. Try fdisk once the system is started (without any disk either), > you should get "medium not present" error. Then try with a disk inserted. > > -- > Nicolas.Souchu@prism.uvsq.fr > FreeBSD - Turning PC's into workstations - http://www.FreeBSD.org > I tried this. I don't remeber the boot message when I booted without the disk, but fdisk still hung. I did not get "medium not present". I've since built a kernel with ppa3. I'm having better luck with that. Of four disks, I was able to fdisk all of them, mount and ls 2 of them (the other 2 I could apparently mount, but they showed nothing on ls and I know there's stuff there) and copied some stuff from one to my hard drive. These were all msdos formatted. I couldn't disklabel any of them. Something about no available space. Anyway thanks for all the help. I'm willing to keep trying with ppbus, if you have any other ideas. Greg From owner-freebsd-hardware Fri Oct 3 18:13:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA24906 for hardware-outgoing; Fri, 3 Oct 1997 18:13:58 -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 SAA24900 for ; Fri, 3 Oct 1997 18:13:55 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id VAA07559; Fri, 3 Oct 1997 21:16:22 -0400 (EDT) Date: Fri, 3 Oct 1997 21:16:22 -0400 (EDT) From: "John T. Farmer" Message-Id: <199710040116.VAA07559@sabre.goldsword.com> To: gurney_j@resnet.uoregon.edu Subject: Re: Multiple serial ports Cc: freebsd-hardware@freebsd.org, jfarmer@goldsword.com Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Oct 1997 18:54:13 -0700 John-Mark Gurney said: >John T. Farmer scribbled this message on Oct 2: >> Uh, actually, I've had good success with with several different brands >> for multiple terminals/printers/front-end system consoles all active at >> the same time. Granted, I don't try to run the ports at greater than >> 56kbps. Frankly, you don't need to. > >why exactly?? a friend was dialed into my machine (using a 14.4k >internal!!) and we were sending some text down the line.. and he was >able to get 8kbytes/sec+ over the link.. and this is with a zoom 14.4k, >and a zoom 28.8k modem... if I wasn't running the zoom at 115.2kbps, we >wouldn't of been able to do that... and instead would of slowed a >14.4kbps call... (think if it was a 28.8k??) > >plus also, there is a MAJOR reduction in the latency of a connection >when you run the speed faster.. for example, when another friend >upgraded to a Supra 288kbps modem, and I was still on my Supra 14.4k >modem.. the latency dropped 50ms JUST because his modem->computer rate >increased... and then when I went to 28.8k also (both of these are >external), we dropped another 70-100ms in latency... Ah, increasing the line speed does not necessarily mean that latency will go down. The latency of a 32k synchronous digital link (FR connection, for example) is usually less than the latency of a 33.6k analog modem connection. A lot of the latency reduction in your example is due to difference between 14.4 & 28.8 modems. Modem brnad will also play a factor, not to mention the effect of flow control on each leg... >this also brings up that kernel ppp (pppd) is usually much lower latency >than iij-ppp... the friend with his internal 14.4k (first example) and >my extern zoom 28.8k, we were able to knock off at least 20ms off ping >times because he went from iij-ppp over to ppp... the last time we had >the connection up (he's moved, and much better connected) we were able >to do 140ms ping times over the 14.4k connection... Yes, this is a known factor that can be accounted for & tuned for. >these may not seem much, but when your used to do typing of a wireless >ricochet modem, when at BEST will give you 350ms, mostly 400-450ms, you >REALLY becom aware of the problems with latency... > >of course, then you just need to go FR or ISDN, and it'll be much >better.. > Which brings me to this question: To whit, What the devil does any of this have to do with the issue/problem that was being discussed? The issue was dealng with multiple consoles on servers, routers, etc. located locally and/or remotely. The basic "plug a terminal into the console serial port" of your cisco(s), but for multiple devices. Anyway, this discussion has wandered far, far afield of freebsd-related hardware issues. I propose to declare it buried... 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 Fri Oct 3 18:20:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA25138 for hardware-outgoing; Fri, 3 Oct 1997 18:20:38 -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 SAA25133 for ; Fri, 3 Oct 1997 18:20:34 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.7/8.7.3) id VAA07590; Fri, 3 Oct 1997 21:23:10 -0400 (EDT) Date: Fri, 3 Oct 1997 21:23:10 -0400 (EDT) From: "John T. Farmer" Message-Id: <199710040123.VAA07590@sabre.goldsword.com> To: freebsd-hardware@FreeBSD.ORG, gljohns@bellsouth.net Subject: Re: AMD and Cyrix chips Cc: jfarmer@goldsword.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 02 Oct 1997 22:54:32 -0500 Glenn Johnson said: >I am planning on replacing my AMD K5-75 chip with either an AMD K6-166 or a >Cyrix 6x86MX P200 running at 166 MHz. Does anyone have any recommendations on >which one I should upgrade to? I know there were some problems with the K6 >that seem to have been resolved. Are there any issues with the Cyrix chip? >Thanks. It's a bit early to declare it solved, but it appears that AMD did indeed find the problem in the K6 and more recent chips are operating fine under FreeBSD. Several people with new, corrected, chips have reported to be able to "make worlds" all day long... Next week I'm probably going to order a K6 to do back-to-back testing against a Cyrix 6x86MX chip. 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 Fri Oct 3 19:02:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA26588 for hardware-outgoing; Fri, 3 Oct 1997 19:02:21 -0700 (PDT) Received: from terror.hungry.com (fn@terror.hungry.com [169.131.1.215]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26581 for ; Fri, 3 Oct 1997 19:02:17 -0700 (PDT) Received: (from fn@localhost) by terror.hungry.com (8.8.7/8.8.7) id TAA03893; Fri, 3 Oct 1997 19:02:16 -0700 (PDT) To: freebsd-hardware@freebsd.org Subject: Re: VIA-VP2 References: <199709292012.PAA26054@compound.east.sun.com> From: Faried Nawaz Date: 03 Oct 1997 19:02:15 -0700 In-Reply-To: Anthony.Kimball@East.Sun.COM's message of 29 Sep 1997 13:47:53 -0700 Message-ID: Lines: 2 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does FreeBSD 2.2.x support VIA-VP2 (specifically, VIA 590VP2) at all? From owner-freebsd-hardware Fri Oct 3 19:42:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA28230 for hardware-outgoing; Fri, 3 Oct 1997 19:42:51 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA28221 for ; Fri, 3 Oct 1997 19:42:40 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id MAA04826; Sat, 4 Oct 1997 12:42:21 +1000 (EST) Date: Sat, 4 Oct 1997 12:42:20 +1000 (EST) From: "Daniel O'Callaghan" To: Faried Nawaz cc: freebsd-hardware@FreeBSD.ORG Subject: Re: VIA-VP2 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 3 Oct 1997, Faried Nawaz wrote: > Does FreeBSD 2.2.x support VIA-VP2 (specifically, VIA 590VP2) at all? I have had no problems running on VP1 "VIA VT82C580VP" and I would not expect any running on a VP2 or VP3 motherboard. Danny /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-hardware Fri Oct 3 23:29:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA00419 for hardware-outgoing; Fri, 3 Oct 1997 23:29:37 -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 XAA00413 for ; Fri, 3 Oct 1997 23:29:34 -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 WAA00758; Fri, 3 Oct 1997 22:46:14 -0700 (PDT) Message-Id: <199710040546.WAA00758@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "John T. Farmer" cc: gurney_j@resnet.uoregon.edu, freebsd-hardware@freebsd.org, jfarmer@goldsword.com Subject: Re: Multiple serial ports In-reply-to: Your message of Fri, 03 Oct 97 21:16:22 -0400. <199710040116.VAA07559@sabre.goldsword.com> Date: Fri, 03 Oct 1997 22:46:13 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >On Thu, 2 Oct 1997 18:54:13 -0700 John-Mark Gurney said: >>John T. Farmer scribbled this message on Oct 2: >>> Uh, actually, I've had good success with with several different brands >>> for multiple terminals/printers/front-end system consoles all active at >>> the same time. Granted, I don't try to run the ports at greater than >>> 56kbps. Frankly, you don't need to. >>why exactly?? a friend was dialed into my machine (using a 14.4k >>internal!!) and we were sending some text down the line.. and he was >>able to get 8kbytes/sec+ over the link.. and this is with a zoom 14.4k, >>and a zoom 28.8k modem... if I wasn't running the zoom at 115.2kbps, we >>wouldn't of been able to do that... and instead would of slowed a >>14.4kbps call... (think if it was a 28.8k??) > > Ah, increasing the line speed does not necessarily mean that > latency will go down. The latency of a 32k synchronous digital > link (FR connection, for example) is usually less than the > latency of a 33.6k analog modem connection. A lot of the > latency reduction in your example is due to difference between > 14.4 & 28.8 modems. Modem brnad will also play a factor, not > to mention the effect of flow control on each leg... However, this doesn't disprove the fact that you need to run your ports much faster than 56Kbps if you expect to get any compression at all out of your 33.6-56K modem. Remember, the ports need to run as fast as the _uncompressed_ data, going in and/or coming out, or else compression is going to do nothing for you but add latency. I. e. if you want to be able to stream data through a 28.8K modem, with full 4x compression, you need to be running your serial ports at least as fast as 4x28.8K, or 113.2Kbps. Granted, there isn't very much out there except plain text that is this compressible. But, 2x isn't hard to do with generic network traffic, and one of the most popular things to do right now (surf the web) is comprised of large amounts of plain text (combined with alread-compressed graphics, of course). The graphics will come over mostly at native modem speed, since they're already compressed. But your text won't come over any faster if you don't run your serial ports faster. ----------------------------------------------------------------------------- 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 Sat Oct 4 03:00:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA09448 for hardware-outgoing; Sat, 4 Oct 1997 03:00:49 -0700 (PDT) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA09411; Sat, 4 Oct 1997 03:00:37 -0700 (PDT) Received: from cezanne.prism.uvsq.fr (rtc105.reseau.uvsq.fr [193.51.24.21]) by soleil.uvsq.fr (8.8.6/jtpda-5.2) with ESMTP id LAA23367 ; Sat, 4 Oct 1997 11:45:27 +0200 (METDST) Received: (from son@localhost) by cezanne.prism.uvsq.fr (8.8.5/8.8.5) id LAA00309; Sat, 4 Oct 1997 11:31:10 GMT Message-ID: <19971004113110.17593@coreff.prism.uvsq.fr> Date: Sat, 4 Oct 1997 11:31:10 +0000 From: Nicolas Souchu To: Greg Pavelcak Cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: ppbus problems References: <34352F41.237C228A@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Greg Pavelcak on Fri, Oct 03, 1997 at 05:31:03PM -0400 X-Operating-System: FreeBSD coreff 2.2.1-RELEASE FreeBSD 2.2.1-RELEASE Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Your mailer seems to be perfectly configured! :) On Fri, Oct 03, 1997 at 05:31:03PM -0400, Greg Pavelcak wrote: >Anyway thanks for all the help. I'm willing to keep trying with ppbus, >if you have any other ideas. Ok, as private mail. I'll tell soon you to grab a new ppbus release which will help us in debugging. Thanks. -- Nicolas.Souchu@prism.uvsq.fr FreeBSD - Turning PC's into workstations - http://www.FreeBSD.org From owner-freebsd-hardware Sat Oct 4 05:05:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA14173 for hardware-outgoing; Sat, 4 Oct 1997 05:05:18 -0700 (PDT) Received: from vega.BlazeNet.net (vega.BlazeNet.net [24.104.0.36]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA14168 for ; Sat, 4 Oct 1997 05:05:12 -0700 (PDT) Received: from [24.104.1.37] by vega.BlazeNet.net (Netscape Mail Server v2.0) with ESMTP id AAA16504 for ; Sat, 4 Oct 1997 08:01:40 -0400 Message-Id: In-Reply-To: References: Anthony.Kimball@East.Sun.COM's message of 29 Sep 1997 13:47:53 -0700 <199709292012.PAA26054@compound.east.sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 4 Oct 1997 08:07:11 -0400 To: freebsd-hardware@FreeBSD.ORG From: dweikert@blazenet.net (Daniel L. Weikert) Subject: Re: VIA-VP2 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Does FreeBSD 2.2.x support VIA-VP2 (specifically, VIA 590VP2) at all? For the last couple weeks I've been running FreeBSD (2.2.2-Release) on a VIA VP2/97 chipset (FIC PA-2007 motherboard w/Cyrix 6x86MX PR200). I admit that I'm a bit of a newbie with FreeBSD so I haven't exactly been giving it much of a workout, but I have had to make a few kernels and I use XFree86 and it seems just as stable as the old 486dx33 that I was using, just a lot faster. :-) Dan Dweikert@blazenet.net From owner-freebsd-hardware Sat Oct 4 05:13:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA14350 for hardware-outgoing; Sat, 4 Oct 1997 05:13:40 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA14343 for ; Sat, 4 Oct 1997 05:13:32 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA20279 (5.67b/IDA-1.5 for ); Sat, 4 Oct 1997 14:13:24 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id LAA00769; Sat, 4 Oct 1997 11:02:20 +0200 (CEST) X-Face: " Date: Sat, 4 Oct 1997 11:02:19 +0200 From: Stefan Esser To: Faried Nawaz Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: VIA-VP2 References: <199709292012.PAA26054@compound.east.sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Faried Nawaz on Fri, Oct 03, 1997 at 07:02:15PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 1997-10-03 19:02 -0700, Faried Nawaz wrote: > Does FreeBSD 2.2.x support VIA-VP2 (specifically, VIA 590VP2) at all? Only PCI chip sets that don't comply to the PCI standard need special support, and the VIA chip sets don't seem to fall into that category. (Some PPro chip sets do ...) But there may be no support of Bus-Master EIDE transfers for those chip sets (I don't use EIDE myself and do not know how hard it would be to add support for DMA to some new chip set.) Regards, STefan From owner-freebsd-hardware Sat Oct 4 14:32:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA07640 for hardware-outgoing; Sat, 4 Oct 1997 14:32:42 -0700 (PDT) Received: from seraph.wspout.com (seraph.wspout.com [206.230.5.48]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA07633 for ; Sat, 4 Oct 1997 14:32:37 -0700 (PDT) Received: (from csg@localhost) by seraph.wspout.com (8.8.5/8.8.4) id QAA03691; Sat, 4 Oct 1997 16:32:35 -0500 (EST) Message-ID: <19971004163235.GA06050@wspout.com> Date: Sat, 4 Oct 1997 16:32:35 -0500 From: csg@wspout.com (C. Stephen Gunn) To: freebsd-hardware@freebsd.org Subject: Re: AMD and Cyrix chips References: <199710040123.VAA07590@sabre.goldsword.com> X-Mailer: Mutt 0.59 Mime-Version: 1.0 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It's a bit early to declare it solved, but it appears that AMD did > indeed find the problem in the K6 and more recent chips are operating > fine under FreeBSD. Several people with new, corrected, chips have > reported to be able to "make worlds" all day long... We just brought up a K6-200 machine (ASUS P55T2P4 w/K6-200) and it is working like a charm. Darned Fast thing too for $375. :-) - Steve -- C. Stephen Gunn csg@wspout.com WaterSpout Communications, Inc 765.775.4169