From owner-freebsd-hardware Sun Jun 14 13:11:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22193 for freebsd-hardware-outgoing; Sun, 14 Jun 1998 13:11:28 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from hotmail.com (f144.hotmail.com [207.82.251.23]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA22178 for ; Sun, 14 Jun 1998 13:11:23 -0700 (PDT) (envelope-from siriusbontea@hotmail.com) Received: (qmail 9129 invoked by uid 0); 14 Jun 1998 20:10:49 -0000 Message-ID: <19980614201049.9128.qmail@hotmail.com> Received: from 131.30.176.55 by www.hotmail.com with HTTP; Sun, 14 Jun 1998 13:10:49 PDT X-Originating-IP: [131.30.176.55] From: "Sirius Bontea" To: FreeBSD-Hardware@FreeBSD.ORG Subject: Diamond V330 AGP question Content-Type: text/plain Date: Sun, 14 Jun 1998 20:10:49 GMT Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings everyone, I'm looking to purchase a new computer soon and wondered if the Diamond V330 AGP video card worked on a FreeBSD platform. I managed to find out that the PCI version of the card worked. If possible, I rather get the AGP version. Can anyone offer any advice? Peace and long life, ~Sirius ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 15 01:02:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27377 for freebsd-hardware-outgoing; Mon, 15 Jun 1998 01:02:45 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from home.shvetc.zp.ua (home.shvetc.zp.ua [193.193.219.185]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27138; Mon, 15 Jun 1998 01:01:47 -0700 (PDT) (envelope-from eugene@shvetc.zp.ua) Received: from wints (wints.shvetc.zp.ua [193.193.219.186]) by home.shvetc.zp.ua (8.8.8/8.8.7) with SMTP id KAA19818; Mon, 15 Jun 1998 10:50:14 +0300 (EEST) (envelope-from eugene@shvetc.zp.ua) Message-ID: <005301bd9832$3c779aa0$badbc1c1@wints.shvetc.zp.ua> From: "Eugene Shvetc" To: Cc: , Subject: Fw: RAID controller Date: Mon, 15 Jun 1998 10:50:13 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >i have: > - onboard 7880 UWSCSI + raid port on motherboard > - ARO1130 PCI + raid port with AHA7810 > RAID coprocessor >and: > - Mylex DAC960 doublechannel > How i can find drivers for FreeBSD, and does it is exist ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 15 07:31:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20703 for freebsd-hardware-outgoing; Mon, 15 Jun 1998 07:31:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20659 for ; Mon, 15 Jun 1998 07:31:10 -0700 (PDT) (envelope-from hinman@us.networkcs.com) Received: from us.networkcs.com (us.networkcs.com [137.66.11.15]) by marcos.networkcs.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id JAA01950 for ; Mon, 15 Jun 1998 09:31:06 -0500 (CDT) Received: (from hinman@localhost) by us.networkcs.com (8.8.7/8.8.7) id JAA08497 for freebsd-hardware@FreeBSD.ORG; Mon, 15 Jun 1998 09:31:05 -0500 (CDT) From: "Lee E. Hinman" Message-Id: <199806151431.JAA08497@us.networkcs.com> Subject: RAID5 with FreeBSD? To: freebsd-hardware@FreeBSD.ORG Date: Mon, 15 Jun 1998 09:31:05 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Does anyone have any recommendation on hardware/software to get RAID5 (stripping + parity) on FreeBSD. I looked at the cdd driver but it doesn't support parity yet (as of 2.2.5). We want to put together a kick ass NFS/SMB file server and I really want FreeBSD as the OS. Thanks. Lee -- _________________________________________________________________ | Lee E. Hinman | Email: hinman@networkcs.com | | Network Computing Services Inc. | Phone: 612-337-3442 | | Network & System Admin Group | Pager: 612-538-0835 | | 1200 Washington Ave S. | Fax: 612-337-3400 | | Minneapolis, MN 55415 | Web: www.networkcs.com | ----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 15 08:22:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27325 for freebsd-hardware-outgoing; Mon, 15 Jun 1998 08:22:35 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27253 for ; Mon, 15 Jun 1998 08:22:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id HAA00313; Mon, 15 Jun 1998 07:16:30 -0700 (PDT) Message-Id: <199806151416.HAA00313@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Lee E. Hinman" cc: freebsd-hardware@FreeBSD.ORG Subject: Re: RAID5 with FreeBSD? In-reply-to: Your message of "Mon, 15 Jun 1998 09:31:05 CDT." <199806151431.JAA08497@us.networkcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Jun 1998 07:16:30 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Does anyone have any recommendation on hardware/software to get > RAID5 (stripping + parity) on FreeBSD. I looked at the cdd driver > but it doesn't support parity yet (as of 2.2.5). We want to put > together a kick ass NFS/SMB file server and I really want FreeBSD > as the OS. Thanks. Either a DPT controller or a CMD SCSI-SCSI RAID unit. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 16 00:34:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12137 for freebsd-hardware-outgoing; Tue, 16 Jun 1998 00:34:58 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from golem.belabm.by (root@golem.belabm.by [194.226.122.185]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12124 for ; Tue, 16 Jun 1998 00:34:48 -0700 (PDT) (envelope-from scaner@belabm.by) Received: from belabm.by (saint.belabm.by [194.226.122.183]) by golem.belabm.by (8.8.7/8.8.4) with ESMTP id KAA08821; Tue, 16 Jun 1998 10:34:10 +0300 Message-ID: <35861E8E.BA6A25D2@belabm.by> Date: Tue, 16 Jun 1998 10:28:14 +0300 From: Eugene Vedistchev Reply-To: scaner@belabm.by Organization: Global One in Belarus X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: "freebsd-hardware@FreeBSD.ORG" , "Lee E. Hinman" Subject: Re:RAID5 with FreeBSD Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Also Compaq RAID Array Controllers (SMART,SMART-2,2SL) supported by ida driver, available at http://www.dcs.qmw.ac.uk/~md/ida/ Mike Smith wrote: > > > Does anyone have any recommendation on hardware/software to get > > RAID5 (stripping + parity) on FreeBSD. I looked at the cdd driver > > but it doesn't support parity yet (as of 2.2.5). We want to put > > together a kick ass NFS/SMB file server and I really want FreeBSD > > as the OS. Thanks. > > Either a DPT controller or a CMD SCSI-SCSI RAID unit. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 16 10:47:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17849 for freebsd-hardware-outgoing; Tue, 16 Jun 1998 10:47:35 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17844 for ; Tue, 16 Jun 1998 10:47:32 -0700 (PDT) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id KAA06801 for hardware@freebsd.org; Tue, 16 Jun 1998 10:47:33 -0700 (PDT) (envelope-from sef) Date: Tue, 16 Jun 1998 10:47:33 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199806161747.KAA06801@kithrup.com> To: hardware@FreeBSD.ORG Subject: scsi disk question Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I posted about this to -stable this morning, but now it's a hardware question I think :). I've got an IBM DCAS 3216W (2G UW drive) as my root disk, sd0. After a power failure, /var/news/history.pag contained a non-recoverable bad block -- the kernel would try four or five times to access it, and then would fail, resulting in an I/O failure. This persisted after a reboot. After I found the file with the bad block, I removed it, and recreated it; this went well, and, so far, the system has continued to function. My question is: will the disk now ignore this bad block? Normally, I'd assume it would (it being an intelligent, scsi disk with Read-Write Error Recovery enabled), but, well, it didn't before :(. I'm currently planning on getting a new disk today, but I'd prefer not to if possible, obviously :). Anyone know for sure? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 16 13:21:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16076 for freebsd-hardware-outgoing; Tue, 16 Jun 1998 13:21:19 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pegasus.com (pegasus.com [206.127.225.31]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA16070 for ; Tue, 16 Jun 1998 13:21:17 -0700 (PDT) (envelope-from richard@pegasus.com) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id KAA15243; Tue, 16 Jun 1998 10:20:35 -1000 Date: Tue, 16 Jun 1998 10:20:35 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199806162020.KAA15243@pegasus.com> In-Reply-To: Sean Eric Fagan "scsi disk question" (Jun 16, 10:47am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Sean Eric Fagan , hardware@FreeBSD.ORG Subject: Re: scsi disk question Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org } } I posted about this to -stable this morning, but now it's a hardware question } I think :). } } I've got an IBM DCAS 3216W (2G UW drive) as my root disk, sd0. After a power } failure, /var/news/history.pag contained a non-recoverable bad block -- the } kernel would try four or five times to access it, and then would fail, } resulting in an I/O failure. This persisted after a reboot. } } After I found the file with the bad block, I removed it, and recreated it; } this went well, and, so far, the system has continued to function. It would have been better to rename it to something like .bad-blocks. } } My question is: will the disk now ignore this bad block? Normally, I'd } assume it would (it being an intelligent, scsi disk with Read-Write Error } Recovery enabled), but, well, it didn't before :(. The drive knows nothing of filesystem file creation and deletion. You need to reformat the disk. By deleting the file you've put the bad block back into play. It will probably surface elsewhere. If you're not ready to reformat then you might fill the remaining free space on the disk with small files until the bad block resurfaces, and stash it out of the way. } } I'm currently planning on getting a new disk today, but I'd prefer not to if } possible, obviously :). } } Anyone know for sure? } Dunno. New bad blocks is a bad sign. Reformat and exercise (verify) the drive heavily to see if it will remain stable now. Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 16 15:33:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08838 for freebsd-hardware-outgoing; Tue, 16 Jun 1998 15:33:50 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08803; Tue, 16 Jun 1998 15:33:11 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id AAA18365; Wed, 17 Jun 1998 00:33:02 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id AAA01181; Wed, 17 Jun 1998 00:04:25 +0200 (CEST) X-Face: " Date: Wed, 17 Jun 1998 00:04:24 +0200 From: Stefan Esser To: Sean Eric Fagan , hardware@FreeBSD.ORG Cc: Stefan Esser Subject: Re: scsi disk question References: <199806161747.KAA06801@kithrup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199806161747.KAA06801@kithrup.com>; from Sean Eric Fagan on Tue, Jun 16, 1998 at 10:47:33AM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1998-06-16 10:47 -0700, Sean Eric Fagan wrote: > I posted about this to -stable this morning, but now it's a hardware question > I think :). Well, I don't know how long ago "this morning" has been in your part of the world, but I wrote a reply to your mail to -stable just a few minutes ago ;-) > I've got an IBM DCAS 3216W (2G UW drive) as my root disk, sd0. After a power > failure, /var/news/history.pag contained a non-recoverable bad block -- the > kernel would try four or five times to access it, and then would fail, > resulting in an I/O failure. This persisted after a reboot. Yes, it surely is a bad sector, which must be written to, to be recovered. But I'm quite convinced that the drive has not been physically damaged and need not be replaced. > After I found the file with the bad block, I removed it, and recreated it; > this went well, and, so far, the system has continued to function. Great! > My question is: will the disk now ignore this bad block? Normally, I'd > assume it would (it being an intelligent, scsi disk with Read-Write Error > Recovery enabled), but, well, it didn't before :(. I guess that sector was just incompletely written when the power failed, and the next write will just create a consistent sector (data + ECC) again. There is no need to re-map the sector, in that case. > I'm currently planning on getting a new disk today, but I'd prefer not to if > possible, obviously :). Guess I can understand that ;-) > Anyone know for sure? *You* can easily find out what the current state is: Just dd the complete surface of the disk to /dev/null. If you get another read error, then the sector has not yet received new contents and ECC. You may try to force a write to that sector by filling each and every sector of the disk (dd /dev/zero into a file as root). If this does not work, then you may try to write to each sector on the disk via the raw device (you can write back the original contents). Use a fixit floppy, if necessary. (You could try booting to single-user mode and do the dd from the raw device back to itself even for a root partition, I assume.) That should fix it. Be sure to backup your data before you proceed, whatever you try ! Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 16 17:10:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25544 for freebsd-hardware-outgoing; Tue, 16 Jun 1998 17:10:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from papillon.lemis.com (rider.dunham.org [207.170.123.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25434 for ; Tue, 16 Jun 1998 17:10:13 -0700 (PDT) (envelope-from grog@lemis.com) Received: (grog@localhost) by papillon.lemis.com (8.8.8/8.6.12) id SAA02365; Tue, 16 Jun 1998 18:39:42 -0500 (CDT) Message-ID: <19980616183940.64052@papillon.lemis.com> Date: Tue, 16 Jun 1998 18:39:40 -0500 From: Greg Lehey To: "Lee E. Hinman" , freebsd-hardware@FreeBSD.ORG Subject: Re: RAID5 with FreeBSD? References: <199806151431.JAA08497@us.networkcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199806151431.JAA08497@us.networkcs.com>; from Lee E. Hinman on Mon, Jun 15, 1998 at 09:31:05AM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 15 June 1998 at 9:31:05 -0500, Lee E. Hinman wrote: > Hi, > > Does anyone have any recommendation on hardware/software to get > RAID5 (stripping + parity) on FreeBSD. I looked at the cdd driver > but it doesn't support parity yet (as of 2.2.5). We want to put > together a kick ass NFS/SMB file server and I really want FreeBSD > as the OS. Thanks. Check out http://www.lemis.com/vinum.html Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 16 22:32:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11088 for freebsd-hardware-outgoing; Tue, 16 Jun 1998 22:32:44 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from bubble.didi.com (nor-la4-23.ix.netcom.com [204.31.237.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11077 for ; Tue, 16 Jun 1998 22:32:37 -0700 (PDT) (envelope-from asami@sunrise.cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.8.8/8.8.8) id AAA07780; Wed, 17 Jun 1998 00:32:19 -0500 (CDT) (envelope-from asami) Date: Wed, 17 Jun 1998 00:32:19 -0500 (CDT) Message-Id: <199806170532.AAA07780@bubble.didi.com> To: richard@pegasus.com CC: sef@kithrup.com, hardware@FreeBSD.ORG In-reply-to: <199806162020.KAA15243@pegasus.com> (richard@pegasus.com) Subject: Re: scsi disk question From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * The drive knows nothing of filesystem file creation and deletion. You * need to reformat the disk. The latter doesn't follow from the former. :) * By deleting the file you've put the bad block back into play. It will * probably surface elsewhere. Yes, but when the block is allocated again to a file, it will first being written to, at which time the drive will reallocate it. The reason why it initially gave you errors was because the disk cannot pretend nothing bad happened when you have read errors. It can do that for write errors (assuming you haven't run out of spare blocks). Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 16 22:36:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11490 for freebsd-hardware-outgoing; Tue, 16 Jun 1998 22:36:22 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11483; Tue, 16 Jun 1998 22:36:18 -0700 (PDT) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id WAA29283; Tue, 16 Jun 1998 22:36:19 -0700 (PDT) (envelope-from sef) Date: Tue, 16 Jun 1998 22:36:19 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199806170536.WAA29283@kithrup.com> To: asami@FreeBSD.ORG, richard@pegasus.com Subject: Re: scsi disk question Cc: hardware@FreeBSD.ORG In-Reply-To: <199806170532.AAA07780@bubble.didi.com> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org First, thank you everyone for your responses. Even if they were rather contradictory ;). I went out and bought a new disk today (and an APC SmartUPS). When I got home, I did a bunch of dd's on the disk... and I no longer got the errors. se@freebsd.org (not to be confused with sef@freebsd.org ;)) first made the suggestion about writing the block fixing it, and I am, at this point, thinking that is what did it. I hope so, anyway. :) Thanks all, again :). Sean. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 16 23:15:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15936 for freebsd-hardware-outgoing; Tue, 16 Jun 1998 23:15:08 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from feral.com (mjacob@gw100.feral.com [192.67.166.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15929; Tue, 16 Jun 1998 23:15:05 -0700 (PDT) (envelope-from mjacob@feral.com) Received: (from mjacob@localhost) by feral.com (8.8.6/8.8.6) id XAA06056; Tue, 16 Jun 1998 23:14:59 -0700 Date: Tue, 16 Jun 1998 23:14:59 -0700 From: Matthew Jacob Message-Id: <199806170614.XAA06056@feral.com> To: asami@FreeBSD.ORG, richard@pegasus.com, sef@kithrup.com Subject: Re: scsi disk question Cc: hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >se@freebsd.org (not to be confused with sef@freebsd.org ;)) first made the >suggestion about writing the block fixing it, and I am, at this point, >thinking that is what did it. I hope so, anyway. :) Rewriting sectors often fixes spurious and transient ECC errors. If this happens a lot for you, check your power supply && drive grounding - sometimes static buildup can cause this. Or at least used to. I haven't seen this kind of stuff for quite some time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jun 17 22:04:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17823 for freebsd-hardware-outgoing; Wed, 17 Jun 1998 22:04:02 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17789 for ; Wed, 17 Jun 1998 22:03:59 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id AAA02416; Thu, 18 Jun 1998 00:03:51 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 18 Jun 1998 00:03:50 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Greg Lehey cc: Duncan Barclay , freebsd-hardware@FreeBSD.ORG Subject: Re: PS/2 Mouse resolution. In-Reply-To: <19980612155802.25601@papillon.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 12 Jun 1998, Greg Lehey wrote: > On Thu, 11 June 1998 at 18:34:38 -0500, Chris Dillon wrote: > > On Thu, 11 Jun 1998, Duncan Barclay wrote: > > > >> Just upgraded my motherboard to one with a PS/2 port on it (FIC PT-2007, 430TX). > >> > >> I moved my mouse (Logicitech MouseMan) from sio0 to the PS/2 port and it is now > >> "slower" and a pain to use under X. I guess the resolution has increased, can > >> moused be used to fake it back top where it was before? > >> > >> I've tried upping the X acceleration but don't really like it, feels wrong. > >> > >> I don't want to go back the serial port, I want it for the console of > >> my (new) crash box. > > > > I noticed something similar when I bought this new trackball, which sits > > on the PS/2 port. The cursor zips across the screen fast enough, but > > selecting text in an xterm is a whole different story. It used to be that > > when I clicked/dragged to select text the "reverse" selection followed the > > cursor perfectly. Now it lags behind the cursor and updates in bursts. > > Weird, eh? Anyone know why this happens? > > Interesting. The "updates in bursts" looks like an interrupt problem. > I've had similar problems, but I hadn't associated them with the > change from serial to PS/2. I'm currently using a MouseMan on a > serial port on my laptop, and it works fine, but I've been having real > problems on my "real" machine with a PS/2 port. I thought it was the > screen resolution (1600x1200) which was causing the problems, but now > I'll investigate more carefully. > If it were an interrupt problem, wouldn't the cursor itself move jumpily and not just the inverse selection? It moves even more fluidly than with my serial mouse (of course, it was a cheap low-res mouse). -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 18 10:31:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11934 for freebsd-hardware-outgoing; Thu, 18 Jun 1998 10:31:20 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA11867 for ; Thu, 18 Jun 1998 10:30:57 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: from (ragnet.demon.co.uk) [158.152.46.40] by post.mail.demon.net with smtp (Exim 1.82 #2) id 0ymiWO-0007N1-00; Thu, 18 Jun 1998 17:30:49 +0000 Received: from dmlb by ragnet.demon.co.uk with local (Exim 1.82 #1) id 0ymYYI-00067C-00; Thu, 18 Jun 1998 07:52:06 +0100 Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 18 Jun 1998 07:52:06 +0100 (BST) From: Duncan Barclay To: Chris Dillon Subject: Re: PS/2 Mouse resolution. Cc: freebsd-hardware@FreeBSD.ORG, Greg Lehey Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 18-Jun-98 Chris Dillon wrote: > On Fri, 12 Jun 1998, Greg Lehey wrote: > >> On Thu, 11 June 1998 at 18:34:38 -0500, Chris Dillon wrote: >> > On Thu, 11 Jun 1998, Duncan Barclay wrote: >> > >> >> Just upgraded my motherboard to one with a PS/2 port on it (FIC PT-2007, >> >> 430TX). >> >> >> >> I moved my mouse (Logicitech MouseMan) from sio0 to the PS/2 port and it >> >> is now >> >> "slower" and a pain to use under X. I guess the resolution has increased, >> >> can >> >> moused be used to fake it back top where it was before? >> >> >> >> I've tried upping the X acceleration but don't really like it, feels >> >> wrong. >> >> >> >> I don't want to go back the serial port, I want it for the console of >> >> my (new) crash box. >> > >> > I noticed something similar when I bought this new trackball, which sits >> > on the PS/2 port. The cursor zips across the screen fast enough, but >> > selecting text in an xterm is a whole different story. It used to be that >> > when I clicked/dragged to select text the "reverse" selection followed the >> > cursor perfectly. Now it lags behind the cursor and updates in bursts. >> > Weird, eh? Anyone know why this happens? >> >> Interesting. The "updates in bursts" looks like an interrupt problem. >> I've had similar problems, but I hadn't associated them with the >> change from serial to PS/2. I'm currently using a MouseMan on a >> serial port on my laptop, and it works fine, but I've been having real >> problems on my "real" machine with a PS/2 port. I thought it was the >> screen resolution (1600x1200) which was causing the problems, but now >> I'll investigate more carefully. >> > > If it were an interrupt problem, wouldn't the cursor itself move jumpily > and not just the inverse selection? It moves even more fluidly than with > my serial mouse (of course, it was a cheap low-res mouse). > > > -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net > /* FreeBSD: The fastest and most stable server OS on the planet. > For Intel x86 and compatibles (SPARC and Alpha under development) > (http://www.freebsd.org) */ > > Well I managed to find my slowness the problem after RTFM, it appears that when my mouse is used as a PS/2 device it's resolution is lower than it is when used as a serial device. Found the -r flag to moused to be useful! Duncan --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. ________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 18 14:12:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15291 for freebsd-hardware-outgoing; Thu, 18 Jun 1998 14:12:43 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from elephants.dyn.ml.org (root@mki3-pl-ri11.kos.net [206.186.40.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15252; Thu, 18 Jun 1998 14:12:32 -0700 (PDT) (envelope-from jake@checker.org) Received: from checker.org (jake@elephants.dyn.ml.org [127.0.0.1]) by elephants.dyn.ml.org (8.8.8/8.8.8) with ESMTP id RAA17043; Thu, 18 Jun 1998 17:14:25 -0400 (EDT) (envelope-from jake@checker.org) Message-Id: <199806182114.RAA17043@elephants.dyn.ml.org> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG, hardware@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: agp video: matrox G100 or i740 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Jun 1998 17:14:24 -0400 From: Jake Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Can someone tell me if AGP cards based on the i740 chipset, or the Matrox productiva G100 are supported by XFree86 and FreeBSD? I'm kind of looking for an 8mb alternative to the Riva 128. Thanks -- http://www.checker.org/~jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 19 03:16:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07161 for freebsd-hardware-outgoing; Fri, 19 Jun 1998 03:16:14 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mailhub1.liv.ac.uk (exim@mailhub1.liv.ac.uk [138.253.100.94]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA07150 for ; Fri, 19 Jun 1998 03:16:12 -0700 (PDT) (envelope-from dave.tyson@liverpool.ac.uk) Received: from uxa.liv.ac.uk [138.253.100.79] by mailhub1.liv.ac.uk with esmtp (Exim 1.73 #2) id 0ymyD7-0000oA-00; Fri, 19 Jun 1998 11:15:57 +0100 Received: (from dtyson@localhost) by uxa.liv.ac.uk (8.8.7/ajt5) id LAA15120; Fri, 19 Jun 1998 11:15:57 +0100 (BST) Date: Fri, 19 Jun 1998 11:15:56 +0100 (BST) From: "Mr G.D. Tyson" X-Sender: dtyson@uxa.liv.ac.uk To: port-i386@netbsd.org, freebsd-hardware@FreeBSD.ORG Subject: O/S Support for large [512Mb] PC systems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We need to assemble and put into service a couple of large machines to act as a web cache (using the squid software). The choice is either SUN systems running slowaris or large PC's running either NetBSD or FreeBSD. The management are inclined to the former, but may be willing to entertain the latter if I can convince them it will work, hence need I need a bit of feedback from people who run PC's with large amounts of memory and SCSI disk. My first stab at a system would use a Pentium II board with 512Mb Memory and a 333Mhz processor. The system would boot from the on-board EIDE controller via a 2Gb system disk. The cache area would be two strings of 4 fast wide 9Gb SCSI II disks plugged into an Adaptek 3940 ultra controller. We would probably use an Intel Express 10/100 Ethernet adaptor (or two) as the network connection. Although I have used NetBSD & FreeBSD for a while, its mainly on small systems with pathetically small disks ! Questions: 1) Ideally I would like the 9Gb disks to have a single large filesystem + some swap. However I think the max size of a filesystem is limited to 2Gb - Is this still true ? [I cannot find any reference to this in the man pages or FAQ's - though off_t seems to be 64 bits which implies > 2Gb files] 2) Will 512Mb of memory break anything ? (I know I will have to tell the kernel the true memory size) 3) Has anyone any experience of a machine with this sort of configuration ? 4) Has anyone used any of the Supermicro boards e.g. P6DBS with the builtin Adaptec Dual Channel UWSCSI ? or got suggestions for other suitable motherboards (preferably ones with will take up to 1Gb RAM) I should point out that 'the management' would REALLY like to use a commercially available box rather than me build one out of bits ! Cheer, Dave -- ===================================================================== Dave Tyson Phone: 0151-794-3731 Computing Services Dept Fax: 0151-794-3759 The University of Liverpool Email: dtyson@liv.ac.uk Chadwick Building Web: http://www.liv.ac.uk/~dtyson Peach Street Liverpool L69 7ZF Why not use a real OS like NetBSD ? United Kingdom ===================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 19 04:41:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA22240 for freebsd-hardware-outgoing; Fri, 19 Jun 1998 04:41:39 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from brig.com (c593490-a.plstn1.sfba.home.com [24.1.82.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22195 for ; Fri, 19 Jun 1998 04:41:19 -0700 (PDT) (envelope-from brb@brig.com) Received: (from brb@localhost) by brig.com id EAA13290; Fri, 19 Jun 1998 04:41:11 -0700 (PDT) Date: Fri, 19 Jun 1998 04:41:11 -0700 (PDT) Message-Id: <199806191141.EAA13290@brig.com> From: Brian Baird MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Mr G.D. Tyson" Cc: port-i386@netbsd.org, freebsd-hardware@FreeBSD.ORG Subject: Re: O/S Support for large [512Mb] PC systems References: Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 1) Ideally I would like the 9Gb disks to have a single large filesystem + > some swap. However I think the max size of a filesystem is limited to > 2Gb - Is this still true ? I've built large file servers using NetBSD for some years now. NetBSD has no problems with 9GB file systems (other than running fsck on them can take some time). You could even run ccd on a number of these drives to get a really massive filesystem. I have a NetBSD 1.2 based system with two Adaptec 2940 PCI controllers and 13 9GB Seagate Elite disks (and a 48GB DAT changer). It's been solid as a rock for several years. > 2) Will 512Mb of memory break anything ? (I know I will have to tell the > kernel the true memory size) Recent (1.3 or later) versions of NetBSD correctly autodetect how much memory is in your machine. In earlier versions you had to config a special kernel to tell it if you had more than 64MB of memory. I've had lots of NetBSD machines with 256MB of memory. I've never gone to 512MB because I've never needed to for the applications I was running. You'll probably want to config a kernel that tunes NMBCLUSTERS to 2048 (for a busy network server) and NBUF and BUFPAGES so that they use more than 10% of memory. > 3) Has anyone any experience of a machine with this sort of configuration ? See above :-) > 4) Has anyone used any of the Supermicro boards e.g. P6DBS with the builtin > Adaptec Dual Channel UWSCSI ? or got suggestions for other suitable > motherboards (preferably ones with will take up to 1Gb RAM) I should > point out that 'the management' would REALLY like to use a commercially > available box rather than me build one out of bits ! I've always stuck with Asus or Tyan motherboards with PCI card SCSI controllers. I think some of the earlier on-board SCSI controllers were less capable than the PCI cards (due to fewer SCBs? my memory is kind of fuzzy about this). I have little experience with FreeBSD, but I'm sure it's capable as well. Just read ftp://ftp.cdrom.com/archive-info/wcarchive.txt for a description of a monster machine. -- Brian Baird Brig Systems, Pleasanton CA brb@brig.com +1 925 484 2457 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 19 05:05:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25997 for freebsd-hardware-outgoing; Fri, 19 Jun 1998 05:05:00 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from herd.plethora.net (root@herd.plethora.net [205.166.146.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25959 for ; Fri, 19 Jun 1998 05:04:39 -0700 (PDT) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (root@guild.plethora.net [205.166.146.8]) by herd.plethora.net (8.8.5/8.8.5) with ESMTP id HAA15561; Fri, 19 Jun 1998 07:04:34 -0500 (CDT) Received: from guild.plethora.net (seebs@localhost.Berkeley.EDU [127.0.0.1]) by guild.plethora.net (8.8.5/8.8.5) with ESMTP id HAA25823; Fri, 19 Jun 1998 07:04:33 -0500 (CDT) Message-Id: <199806191204.HAA25823@guild.plethora.net> From: seebs@plethora.net Reply-To: seebs@plethora.net To: "Mr G.D. Tyson" cc: port-i386@netbsd.org, freebsd-hardware@FreeBSD.ORG Subject: Re: O/S Support for large [512Mb] PC systems In-reply-to: Your message of "Fri, 19 Jun 1998 11:15:56 BST." Date: Fri, 19 Jun 1998 07:04:32 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , "Mr G.D. T yson" writes: >1) Ideally I would like the 9Gb disks to have a single large filesystem + > some swap. However I think the max size of a filesystem is limited to > 2Gb - Is this still true ? No, it hasn't been true in a long time. I do not believe there exist enough bytes to create a maximal filesystem. >4) Has anyone used any of the Supermicro boards e.g. P6DBS with the builtin > Adaptec Dual Channel UWSCSI ? or got suggestions for other suitable > motherboards (preferably ones with will take up to 1Gb RAM) I should > point out that 'the management' would REALLY like to use a commercially > available box rather than me build one out of bits ! While it's pretty much theoretical at the moment, there's some discussion of building a NetBSD support organization; if this happens, we will be happy to build systems, I suspect. And remember, it's commercial as long as someone else tightens the screws. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 19 05:14:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26925 for freebsd-hardware-outgoing; Fri, 19 Jun 1998 05:14:09 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pc1.whooppee.com (pc1.whooppee.com [205.162.63.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26858 for ; Fri, 19 Jun 1998 05:14:00 -0700 (PDT) (envelope-from paul@whooppee.com) Received: (from paul@localhost) by pc1.whooppee.com (8.8.8/8.8.8) id FAA12945; Fri, 19 Jun 1998 05:13:53 -0700 (PDT) Date: Fri, 19 Jun 1998 05:13:53 -0700 (PDT) From: Paul Goyette To: seebs@plethora.net cc: "Mr G.D. Tyson" , port-i386@NetBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: O/S Support for large [512Mb] PC systems In-Reply-To: <199806191204.HAA25823@guild.plethora.net> Message-ID: X-Secure: Never MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 19 Jun 1998 seebs@plethora.net wrote: > While it's pretty much theoretical at the moment, there's some discussion of > building a NetBSD support organization; Really? Which list is this discussion on? :) > if this happens, we will be happy to > build systems, I suspect. And remember, it's commercial as long as someone > else tightens the screws. Not really. But "it's commercial" as long as someone else _gets paid to_ tighten the screws. :) Last time I checked, "commerce" required an exchange of services/value... ----------------------------------------------------------------------------- | Paul Goyette | Public Key fingerprint: | E-mail addresses: | | Network Engineer | 0E 40 D2 FC 2A 13 74 A0 | paul@whooppee.com | | and kernel hacker | E4 69 D5 BE 65 E4 56 C6 | paul.goyette@ascend.com | ----------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 19 05:21:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28067 for freebsd-hardware-outgoing; Fri, 19 Jun 1998 05:21:08 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from herd.plethora.net (root@herd.plethora.net [205.166.146.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28037 for ; Fri, 19 Jun 1998 05:21:00 -0700 (PDT) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (root@guild.plethora.net [205.166.146.8]) by herd.plethora.net (8.8.5/8.8.5) with ESMTP id HAA15617; Fri, 19 Jun 1998 07:20:56 -0500 (CDT) Received: from guild.plethora.net (seebs@localhost.Berkeley.EDU [127.0.0.1]) by guild.plethora.net (8.8.5/8.8.5) with ESMTP id HAA27215; Fri, 19 Jun 1998 07:20:55 -0500 (CDT) Message-Id: <199806191220.HAA27215@guild.plethora.net> From: seebs@plethora.net Reply-To: seebs@plethora.net To: Paul Goyette cc: "Mr G.D. Tyson" , port-i386@netbsd.org, freebsd-hardware@FreeBSD.ORG Subject: Re: O/S Support for large [512Mb] PC systems In-reply-to: Your message of "Fri, 19 Jun 1998 05:13:53 PDT." Date: Fri, 19 Jun 1998 07:20:50 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Paul Go yette writes: >Really? Which list is this discussion on? :) I mentioned it on current-users@netbsd.org. >Not really. But "it's commercial" as long as someone else _gets paid to_ >tighten the screws. :) Last time I checked, "commerce" required an >exchange of services/value... Heh. Close enough. Anyway, at this point, I'm looking fairly seriously at trying to start supporting NetBSD, including hardware sales; I even got the sales&use tax paperwork for MN, so we could certainly build and sell systems, at this point. I don't quite have the rest of the details, I'm afraid; in an optimistic case, we might be able to have a viable support group available within a week or two. The main issue is logistics and billing; there's plenty of competent support techs. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 19 08:03:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27333 for freebsd-hardware-outgoing; Fri, 19 Jun 1998 08:03:32 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27322 for ; Fri, 19 Jun 1998 08:03:28 -0700 (PDT) (envelope-from marc@bowtie.nl) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.8.8/1.63) with IAEhv.nl; pid 17348 on Fri, 19 Jun 1998 15:03:22 GMT; id PAA17348 efrom: marc@bowtie.nl; eto: UNKNOWN Received: from localhost (localhost [127.0.0.1]) by nietzsche.intra.bowtie.nl (8.8.8/8.8.8) with ESMTP id RAA23985; Fri, 19 Jun 1998 17:05:03 +0200 (CEST) (envelope-from marc@bowtie.nl) Message-Id: <199806191505.RAA23985@nietzsche.intra.bowtie.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: "Mr G.D. Tyson" cc: port-i386@netbsd.org, freebsd-hardware@FreeBSD.ORG Subject: Re: O/S Support for large [512Mb] PC systems In-reply-to: Dave.Tyson's message of Fri, 19 Jun 1998 11:15:56 +0100. Reply-to: marc@bowtie.nl Date: Fri, 19 Jun 1998 17:05:03 +0200 From: Marc van Kempen Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 4) Has anyone used any of the Supermicro boards e.g. P6DBS with the builtin > Adaptec Dual Channel UWSCSI ? or got suggestions for other suitable > motherboards (preferably ones with will take up to 1Gb RAM) I should > point out that 'the management' would REALLY like to use a commercially > available box rather than me build one out of bits ! > See http://www.freebsd.org/commercial/hardware.html ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 19 10:16:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23717 for freebsd-hardware-outgoing; Fri, 19 Jun 1998 10:16:49 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antioche.lip6.fr (antioche.lip6.fr [132.227.61.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23656 for ; Fri, 19 Jun 1998 10:16:29 -0700 (PDT) (envelope-from bouyer@antioche.lip6.fr) Received: from antifer.ipv6.lip6.fr (antifer.ipv6.lip6.fr [132.227.61.34]) by antioche.lip6.fr (8.8.8/8.8.5) with ESMTP id TAA00899; Fri, 19 Jun 1998 19:11:13 +0200 (MEST) Received: (bouyer@localhost) by antifer.ipv6.lip6.fr (8.8.8/8.6.4) id TAA08792; Fri, 19 Jun 1998 19:11:13 +0200 (MEST) Message-ID: <19980619191113.10952@antioche.lip6.fr> Date: Fri, 19 Jun 1998 19:11:13 +0200 From: Manuel Bouyer To: "Mr G.D. Tyson" Cc: port-i386@NetBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: O/S Support for large [512Mb] PC systems References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76e In-Reply-To: ; from Mr G.D. Tyson on Fri, Jun 19, 1998 at 11:15:56AM +0100 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Jun 19, Mr G.D. Tyson wrote > [...] > ultra controller. We would probably use an Intel Express 10/100 Ethernet > adaptor (or two) as the network connection. > Beware, I'm not sure all Intel's boards are supported under NetBSD yet. I would recommend boards based on the DEC 21{0,1}14{0,1} or Texas Intruments' ThunderLAN chip (this last one is really fast, for a small amount of CPU use. It seems the de driver ises a bit more CPU). There are a lot of board based on DEC's chips. For TI's chip the only one I know are build by Compaq (ick) and are codenamed Netelligent. I have a few here (single and dual 10/100 ports) and I'm very happy with them. -- Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 19 10:54:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01713 for freebsd-hardware-outgoing; Fri, 19 Jun 1998 10:54:01 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from clifford.inch.com (omar@clifford.inch.com [207.240.140.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01582 for ; Fri, 19 Jun 1998 10:53:05 -0700 (PDT) (envelope-from omar@clifford.inch.com) Received: (from omar@localhost) by clifford.inch.com (8.8.5/8.8.5) id NAA21685; Fri, 19 Jun 1998 13:46:36 -0400 Message-ID: <19980619134635.A21640@clifford.inch.com> Date: Fri, 19 Jun 1998 13:46:35 -0400 From: Omar Thameen To: freebsd-hardware@FreeBSD.ORG Subject: 64M SIMM differences Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In addition to all the parity/nonparity, EDO issues, I've been made aware that there are 2 types of 64M SIMMs - one has 8 chips on it and the other has 32 chips. Is there a difference in performance for these two types? The fact that the 32 chip 64M SIMM is half the price of the 8 chip version indicates one thing, but OTOH I called Kingston and their tech support told me that the SIMMs perform the same. Omar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 20 13:38:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05992 for freebsd-hardware-outgoing; Sat, 20 Jun 1998 13:38:02 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05952 for ; Sat, 20 Jun 1998 13:37:59 -0700 (PDT) (envelope-from anxiety@usr06.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id NAA15474 for ; Sat, 20 Jun 1998 13:37:58 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpd015459; Sat Jun 20 13:37:52 1998 Received: (from anxiety@localhost) by usr06.primenet.com (8.8.5/8.8.5) id NAA14378 for freebsd-hardware@freebsd.org; Sat, 20 Jun 1998 13:37:52 -0700 (MST) From: Micah Mayo Message-Id: <199806202037.NAA14378@usr06.primenet.com> Subject: DVD-Rom To: freebsd-hardware@FreeBSD.ORG Date: Sat, 20 Jun 1998 20:37:52 +0000 (GMT) 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 Precedence: bulk X-Loop: FreeBSD.org I'm considering getting a DVD-Rom instead of a CD(Hey, they're the future aren't they?) on a computer I'm building.. will fbsd run these yet? Is a driver even being developed? If so, what is the status of it? Wouldn't it just recognize it as an ide or scsi cd-rom drive? Also, does anyone out there have an opinion on micropolist scsi drives? Thanks for any info.. Micah To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 20 14:13:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10109 for freebsd-hardware-outgoing; Sat, 20 Jun 1998 14:13:39 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from lucy.bedford.net (lucy.bedford.net [206.99.145.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10103 for ; Sat, 20 Jun 1998 14:13:37 -0700 (PDT) (envelope-from listread@lucy.bedford.net) Received: (from listread@localhost) by lucy.bedford.net (8.8.8/8.8.8) id RAA12686; Sat, 20 Jun 1998 17:13:32 -0400 (EDT) (envelope-from listread) Message-Id: <199806202113.RAA12686@lucy.bedford.net> Subject: Re: DVD-Rom In-Reply-To: <199806202037.NAA14378@usr06.primenet.com> from Micah Mayo at "Jun 20, 98 08:37:52 pm" To: anxiety@primenet.com (Micah Mayo) Date: Sat, 20 Jun 1998 17:13:32 -0400 (EDT) Cc: freebsd-hardware@FreeBSD.ORG X-no-archive: yes Reply-to: djv@bedford.net From: CyberPeasant X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Micah Mayo wrote: > Also, does anyone out there have an opinion on micropolist scsi drives? > Thanks for any info.. > Micropolis is bankrupt, and was not bought up by anyone, and has vanished from the face of the planet, as far as I can tell. I own two Micropolis drives, one died within the first 100 hours of operation, the other still works. Avoid them unless you are able to get them for 1/4 the price of a drive from a manufacturer that is still in business. IOmega is on the verge of bankruptcy, too. dave -- http://www.microsoft.com/security: `Microsoft Windows NT Server is the most secure network operating system available.' Don Quixote: `You are mistaken, Sancho.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 20 17:24:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01677 for freebsd-hardware-outgoing; Sat, 20 Jun 1998 17:24:43 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from papillon.lemis.com (rider.dunham.org [207.170.123.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01672 for ; Sat, 20 Jun 1998 17:24:37 -0700 (PDT) (envelope-from grog@lemis.com) Received: (grog@localhost) by papillon.lemis.com (8.8.8/8.6.12) id SAA00219; Thu, 18 Jun 1998 18:30:48 -0500 (CDT) Message-ID: <19980618183046.40637@papillon.lemis.com> Date: Thu, 18 Jun 1998 18:30:46 -0500 From: Greg Lehey To: Chris Dillon Cc: Duncan Barclay , freebsd-hardware@FreeBSD.ORG Subject: Re: PS/2 Mouse resolution. References: <19980612155802.25601@papillon.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Chris Dillon on Thu, Jun 18, 1998 at 12:03:50AM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 18 June 1998 at 0:03:50 -0500, Chris Dillon wrote: > On Fri, 12 Jun 1998, Greg Lehey wrote: > >> On Thu, 11 June 1998 at 18:34:38 -0500, Chris Dillon wrote: >>> On Thu, 11 Jun 1998, Duncan Barclay wrote: >>> >>>> Just upgraded my motherboard to one with a PS/2 port on it (FIC PT-2007, 430TX). >>>> >>>> I moved my mouse (Logicitech MouseMan) from sio0 to the PS/2 port and it is now >>>> "slower" and a pain to use under X. I guess the resolution has increased, can >>>> moused be used to fake it back top where it was before? >>>> >>>> I've tried upping the X acceleration but don't really like it, feels wrong. >>>> >>>> I don't want to go back the serial port, I want it for the console of >>>> my (new) crash box. >>> >>> I noticed something similar when I bought this new trackball, which sits >>> on the PS/2 port. The cursor zips across the screen fast enough, but >>> selecting text in an xterm is a whole different story. It used to be that >>> when I clicked/dragged to select text the "reverse" selection followed the >>> cursor perfectly. Now it lags behind the cursor and updates in bursts. >>> Weird, eh? Anyone know why this happens? >> >> Interesting. The "updates in bursts" looks like an interrupt problem. >> I've had similar problems, but I hadn't associated them with the >> change from serial to PS/2. I'm currently using a MouseMan on a >> serial port on my laptop, and it works fine, but I've been having real >> problems on my "real" machine with a PS/2 port. I thought it was the >> screen resolution (1600x1200) which was causing the problems, but now >> I'll investigate more carefully. > > If it were an interrupt problem, wouldn't the cursor itself move jumpily > and not just the inverse selection? Yes. That's what comes of not reading the message carefully. Of course, it could still be a conflict with disk access. > It moves even more fluidly than with my serial mouse (of course, it > was a cheap low-res mouse). My impression is that the same mouse (convertible) is smoother on a serial connection than on the PS/2 connector. As I said, I'll try this out when I get home. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 20 18:59:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11849 for freebsd-hardware-outgoing; Sat, 20 Jun 1998 18:59:19 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from shell6.ba.best.com (jkb@shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11843 for ; Sat, 20 Jun 1998 18:59:16 -0700 (PDT) (envelope-from jkb@best.com) Received: from localhost (jkb@localhost) by shell6.ba.best.com (8.8.8/8.8.BEST) with SMTP id SAA05615; Sat, 20 Jun 1998 18:58:26 -0700 (PDT) X-Authentication-Warning: shell6.ba.best.com: jkb owned process doing -bs Date: Sat, 20 Jun 1998 18:58:26 -0700 (PDT) From: "Jan B. Koum " X-Sender: jkb@shell6.ba.best.com To: "Mr G.D. Tyson" cc: port-i386@netbsd.org, freebsd-hardware@FreeBSD.ORG Subject: Re: O/S Support for large [512Mb] PC systems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Point your management to www.yahoo.com and www.best.com -- both of these companies relay on FreeBSD. Yahoo! is public and Best Internet just filed for IPO. Make your conclusions. To NetBSD people: please let me know of any large projects like the two above which involve NetBSD. I would like to add them to my argument when people tell me how NT is about to make our lives better. -- Yan Jan Koum jkb@best.com | "Turn up the lights; I don't want www.FreeBSD.org -- The Power to Serve | to go home in the dark." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 20 19:23:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14863 for freebsd-hardware-outgoing; Sat, 20 Jun 1998 19:23:41 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14850 for ; Sat, 20 Jun 1998 19:23:38 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id VAA12426; Sat, 20 Jun 1998 21:23:29 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Sat, 20 Jun 1998 21:23:29 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Greg Lehey cc: Duncan Barclay , freebsd-hardware@FreeBSD.ORG Subject: Re: PS/2 Mouse resolution. In-Reply-To: <19980618183046.40637@papillon.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 18 Jun 1998, Greg Lehey wrote: [...snip...] > >> Interesting. The "updates in bursts" looks like an interrupt problem. > >> I've had similar problems, but I hadn't associated them with the > >> change from serial to PS/2. I'm currently using a MouseMan on a > >> serial port on my laptop, and it works fine, but I've been having real > >> problems on my "real" machine with a PS/2 port. I thought it was the > >> screen resolution (1600x1200) which was causing the problems, but now > >> I'll investigate more carefully. > > > > If it were an interrupt problem, wouldn't the cursor itself move jumpily > > and not just the inverse selection? > > Yes. That's what comes of not reading the message carefully. Of > course, it could still be a conflict with disk access. Hmm, nothing I ever would have thought of.. :-) I've noticed it with absolutely no disk access occurring, and it doesn't update in random bursts. > > It moves even more fluidly than with my serial mouse (of course, it > > was a cheap low-res mouse). > > My impression is that the same mouse (convertible) is smoother on a > serial connection than on the PS/2 connector. As I said, I'll try > this out when I get home. I'll have to try this out myself with the trackball instead of my old mouse. > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 20 19:57:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19436 for freebsd-hardware-outgoing; Sat, 20 Jun 1998 19:57:30 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from feral.com (root@gw100.feral.com [192.67.166.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19408 for ; Sat, 20 Jun 1998 19:57:25 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral-gw (mjacob@gw100.feral.com [192.67.166.129]) by feral.com (8.8.6/8.8.6) with SMTP id TAA16942; Sat, 20 Jun 1998 19:56:23 -0700 Message-ID: <358C7656.39B08E3@feral.com> Date: Sat, 20 Jun 1998 19:56:23 -0700 From: Matthew Jacob Organization: Feral Software X-Mailer: Mozilla 3.04 (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: "Jan B. Koum" CC: "Mr G.D. Tyson" , port-i386@netbsd.org, freebsd-hardware@FreeBSD.ORG Subject: Re: O/S Support for large [512Mb] PC systems References: Content-Type: multipart/mixed; boundary="------------63A555FF39591B2864454D00" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------63A555FF39591B2864454D00 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jan B. Koum wrote: > To NetBSD people: please let me know of any large projects > like the two above which involve NetBSD. I would like to add them to > my argument when people tell me how NT is about to make our lives > better. I dunno if I consider myself exclusively a "NetBSD" person, but I can give you some numbers. For i386, See attachment #1. For alpha, See attachments #2 and #3. #2 is a large memory system. #3 is a medium large disk system (0.75TB).The latter could be an i386 - in fact we've had that (we're just using the alpha 4000s for there PCI speed for thruput on a HIPPI network). Note also the data rate for writes on the ccd for the latter as well. Not too shabby. I only attach the alphas 'coz I think they're cool. With a 4-8 banger PPro, you could start seeing 'PCs' in this class too. -matt --------------63A555FF39591B2864454D00 Content-Type: text/plain; charset=us-ascii; name="I386_MESSAGES" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="I386_MESSAGES" Copyright (c) 1996, 1997 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD NAStore_(1.3_ALPHA) (MSS3) #51: Tue Jun 16 02:44:59 PDT 1998 root@caves:/usr/src/sys/arch/i386/compile/MSS3 cpu0: family 6 model 1 step 7 cpu0: Intel Pentium Pro (686-class) real mem = 67694592 avail mem = 61071360 using 851 buffers containing 3485696 bytes of memory mainbus0 (root) pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 pchb0: Intel 82441FX PCI and Memory Controller (PMC) (rev. 0x02) pcib0 at pci0 dev 1 function 0 pcib0: Intel 82371SB PCI-to-ISA Bridge (PIIX3) (rev. 0x01) Intel 82371SB IDE Interface (PIIX3) (IDE mass storage, interface 0x80) at pci0 dev 1 function 1 not configured ppb0 at pci0 dev 9 function 0: Digital Equipment DECchip 21152 PCI-PCI Bridge (rev. 0x01) pci1 at ppb0 bus 1 ahc0 at pci1 dev 4 function 0 ahc0: interrupting at irq 9 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16 SCBs scsibus0 at ahc0 channel 0: 16 targets ahc0: target 0 using 16Bit transfers ahc0: target 0 synchronous at 10.0MHz, offset = 0x8 sd0 at scsibus0 targ 0 lun 0: SCSI2 0/direct fixed sd0: 8683MB, 5268 cyl, 20 head, 168 sec, 512 bytes/sect x 17783112 sectors ahc1 at pci1 dev 5 function 0 ahc1: interrupting at irq 11 ahc1: aic7880 Wide Channel B, SCSI Id=7, 16 SCBs scsibus1 at ahc1 channel 0: 16 targets ahc1: target 1 using 16Bit transfers ahc1: target 1 synchronous at 10.0MHz, offset = 0x8 sd1 at scsibus1 targ 1 lun 0: SCSI2 0/direct fixed sd1: 8683MB, 5268 cyl, 20 head, 168 sec, 512 bytes/sect x 17783112 sectors de0 at pci0 dev 11 function 0 de0: interrupting at irq 10 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:c0:6a:a3:ef ppb1 at pci0 dev 12 function 0: Digital Equipment DECchip 21050 PCI-PCI Bridge (rev. 0x02) pci2 at ppb1 bus 2 ahc2 at pci2 dev 4 function 0 ahc2: interrupting at irq 11 ahc2: aic7880 Wide Channel A, SCSI Id=7, 16 SCBs scsibus2 at ahc2 channel 0: 16 targets ahc2: target 2 using 16Bit transfers ahc2: target 2 synchronous at 10.0MHz, offset = 0x8 sd2 at scsibus2 targ 2 lun 0: SCSI2 0/direct fixed sd2: 8683MB, 5268 cyl, 20 head, 168 sec, 512 bytes/sect x 17783112 sectors ahc3 at pci2 dev 5 function 0 ahc3: interrupting at irq 10 ahc3: aic7880 Wide Channel B, SCSI Id=7, 16 SCBs scsibus3 at ahc3 channel 0: 16 targets ahc3: target 3 using 16Bit transfers ahc3: target 3 synchronous at 10.0MHz, offset = 0x8 sd3 at scsibus3 targ 3 lun 0: SCSI2 0/direct fixed sd3: 8683MB, 5268 cyl, 20 head, 168 sec, 512 bytes/sect x 17783112 sectors ppb2 at pci0 dev 13 function 0: Digital Equipment DECchip 21050 PCI-PCI Bridge (rev. 0x02) pci3 at ppb2 bus 3 ahc4 at pci3 dev 4 function 0 ahc4: interrupting at irq 9 ahc4: aic7880 Wide Channel A, SCSI Id=7, 16 SCBs scsibus4 at ahc4 channel 0: 16 targets ahc4: target 2 using 16Bit transfers ahc4: target 2 synchronous at 10.0MHz, offset = 0x8 sd4 at scsibus4 targ 2 lun 0: SCSI2 0/direct fixed sd4: 4148MB, 5172 cyl, 10 head, 164 sec, 512 bytes/sect x 8496884 sectors ahc4: target 3 using 16Bit transfers ahc4: target 3 synchronous at 10.0MHz, offset = 0x8 sd5 at scsibus4 targ 3 lun 0: SCSI2 0/direct fixed sd5: 4148MB, 5172 cyl, 10 head, 164 sec, 512 bytes/sect x 8496884 sectors ahc4: target 4 using 16Bit transfers ahc4: target 4 synchronous at 10.0MHz, offset = 0x8 sd6 at scsibus4 targ 4 lun 0: SCSI2 0/direct fixed sd6: 4148MB, 5172 cyl, 10 head, 164 sec, 512 bytes/sect x 8496884 sectors ahc4: target 5 using 16Bit transfers ahc4: target 5 synchronous at 10.0MHz, offset = 0x8 sd7 at scsibus4 targ 5 lun 0: SCSI2 0/direct fixed sd7: 4148MB, 5172 cyl, 10 head, 164 sec, 512 bytes/sect x 8496884 sectors ahc4: target 6 using 16Bit transfers ahc4: target 6 synchronous at 10.0MHz, offset = 0x8 sd8 at scsibus4 targ 6 lun 0: SCSI2 0/direct fixed sd8: 4148MB, 5172 cyl, 10 head, 164 sec, 512 bytes/sect x 8496884 sectors ahc4: target 8 using 16Bit transfers ahc4: target 8 synchronous at 10.0MHz, offset = 0x8 sd9 at scsibus4 targ 8 lun 0: SCSI2 0/direct fixed sd9: 4148MB, 5172 cyl, 10 head, 164 sec, 512 bytes/sect x 8496884 sectors ahc4: target 9 using 16Bit transfers ahc4: target 9 synchronous at 10.0MHz, offset = 0x8 sd10 at scsibus4 targ 9 lun 0: SCSI2 0/direct fixed sd10: 4148MB, 5172 cyl, 10 head, 164 sec, 512 bytes/sect x 8496884 sectors ahc5 at pci3 dev 5 function 0 ahc5: interrupting at irq 11 ahc5: aic7880 Wide Channel B, SCSI Id=7, 16 SCBs scsibus5 at ahc5 channel 0: 16 targets isa0 at pcib0 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo lpt0 at isa0 port 0x378-0x37b irq 7 npx0 at isa0 port 0xf0-0xff: using exception 16 vt0 at isa0 port 0x60-0x6f irq 1 vt0: unknown cirrus, 80 col, color, 8 scr, mf2-kbd, [R3.32] spkr0 at vt0 port 0x61 vt0: console fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec fd1 at fdc0 drive 1: density unknown apm0 at mainbus0: Power Management spec V1.1 apm0: A/C state: on apm0: battery charge state: no battery biomask e40 netmask e40 ttymask ec2 boot device: sd0 root on sd0a dumps on sd0b root file system type: ffs --------------63A555FF39591B2864454D00 Content-Type: text/plain; charset=us-ascii; name="LARGE_MEMORY_ALPHA" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="LARGE_MEMORY_ALPHA" Copyright (c) 1996, 1997 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD NAStore_(1.3_ALPHA) (MSS3) #55: Tue Jun 16 04:53:23 PDT 1998 root@jules.nas.nasa.gov:/space/NetBSD-mss3/src/sys/arch/alpha/compile/MSS3 AlphaServer 8400, 436MHz 8192 byte page size, 2 processors. real mem = 2147483648 (2629632 reserved for PROM, 2144854016 used by NetBSD) avail mem = 1874231296 using 26182 buffers containing 214482944 bytes of memory mainbus0 (root) cpu0 at mainbus0: ID 8 (primary), 21164A (pass 2) cpu1 at mainbus0: ID 9, 21164A (pass 2) tlsb0 at mainbus0 tlsb0 node 4: Dual CPU, 4MB cache, VID 8 -> cpu gbus0 at tlsb0 node 4: Dual CPU, 4MB cache mcclock0 at gbus0: mc146818 or compatible tlsbmem0 at tlsb0 node 5: MS7CC Memory Module kft0 at tlsb0 node 8: KFTIA I/O interface dwlpx0 at kft0 hose 0: PCIA rev. 0, STD I/O not present, Direct DMA maps. pci0 at dwlpx0 bus 0 isp0 at pci0 dev 0 function 0 isp0: Board Revision 1020, loaded F/W Revision 2.10 isp0: Differential Mode isp0: devparm, W=wide, S=sync, T=Tag isp0: interrupting at kn8ae irq 14 vector 0x8400 PCI Interrupt Pin A scsibus0 at isp0: 16 targets isp1 at pci0 dev 1 function 0 isp1: Board Revision 1020, loaded F/W Revision 2.10 isp1: Differential Mode isp1: devparm, W=wide, S=sync, T=Tag isp1: interrupting at kn8ae irq 14 vector 0x8401 PCI Interrupt Pin A scsibus1 at isp1: 16 targets de0 at pci0 dev 2 function 0 de0: interrupting at kn8ae irq 14 vector 0x8402 PCI Interrupt Pin A de0: DEC 21040 [10Mb/s] pass 2.4 de0: address 00:00:f8:24:ce:e1 de0: enabling 10baseT port fpa0 at pci0 dev 3 function 0: DEC DEFPA PCI FDDI SAS Controller fpa0: FDDI address 08:00:2b:b9:f7:5a, FW=3.10, HW=1, SMT V7.2 fpa0: FDDI Port = S (PMD = ANSI Multi-Mode) fpa0: interrupting at kn8ae irq 14 vector 0x8403 PCI Interrupt Pin A isp2 at pci0 dev 4 function 0 isp2: Board Revision 1020, loaded F/W Revision 2.10 isp2: Differential Mode isp2: devparm, W=wide, S=sync, T=Tag isp2: interrupting at kn8ae irq 14 vector 0x8404 PCI Interrupt Pin A scsibus2 at isp2: 16 targets isp3 at pci0 dev 5 function 0 isp3: Board Revision 1020, loaded F/W Revision 2.10 isp3: Differential Mode isp3: devparm, W=wide, S=sync, T=Tag isp3: interrupting at kn8ae irq 14 vector 0x8405 PCI Interrupt Pin A scsibus3 at isp3: 16 targets sd0 at scsibus3 targ 0 lun 0: SCSI2 0/direct fixed sd0: 2007MB, 3045 cyl, 16 head, 84 sec, 512 bytes/sect x 4110480 sectors sd1 at scsibus3 targ 1 lun 0: SCSI2 0/direct fixed sd1: 4091MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors sd2 at scsibus3 targ 2 lun 0: SCSI2 0/direct fixed sd2: 4091MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors sd3 at scsibus3 targ 3 lun 0: SCSI2 0/direct fixed sd3: 4091MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors cd0 at scsibus3 targ 4 lun 0: SCSI2 5/cdrom removable sd4 at scsibus3 targ 5 lun 0: SCSI2 0/direct fixed sd4: 4091MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors de1 at pci0 dev 6 function 0 de1: interrupting at kn8ae irq 14 vector 0x8406 PCI Interrupt Pin A de1: DEC 21040 [10Mb/s] pass 2.4 de1: address 00:00:f8:24:9f:2f de1: enabling 10baseT port kft1 at tlsb0 node 7: KFTHA I/O interface dwlpx1 at kft1 hose 2: PCIA rev. 1, STD I/O not present, Direct DMA maps. pci1 at dwlpx1 bus 0 de2 at pci1 dev 0 function 0 de2: interrupting at kn8ae irq 14 vector 0x8320 PCI Interrupt Pin A de2: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de2: address 00:00:c0:7f:a1:ef de2: enabling 100baseTX port esh0 at pci1 dev 4 function 0: RoadRunner HIPPI esh0: interrupting at kn8ae irq 14 vector 0x8324 PCI Interrupt Pin A esh1 at pci1 dev 8 function 0: RoadRunner HIPPI esh1: interrupting at kn8ae irq 14 vector 0x8328 PCI Interrupt Pin A kft2 at tlsb0 node 6: KFTHA I/O interface root on sd1a dumps on sd1b root file system type: ffs de0: link down: cable problem? de1: link down: cable problem? de2: link down: cable problem? de2: enabling Full Duplex 100baseTX port fpa0: Link Unavailable esh0: startup runcode version 2.0.19, options 28 esh0: firmware up esh0: startup runcode version 2.0.19, options 28 fpa0: Link Available esh0: firmware up esh0: link up --------------63A555FF39591B2864454D00 Content-Type: text/plain; charset=us-ascii; name="ALPHA_LARGE_FAST_CCD" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ALPHA_LARGE_FAST_CCD" DMESG: Copyright (c) 1996, 1997 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD NAStore_(1.3_ALPHA) (MSS3) #56: Wed Jun 17 04:53:20 PDT 1998 root@jules.nas.nasa.gov:/space/NetBSD-mss3/src/sys/arch/alpha/compile/MSS3 8192 byte page size, 1 processor. real mem = 536870912 (2113536 reserved for PROM, 534757376 used by NetBSD) avail mem = 463519744 using 6527 buffers containing 53469184 bytes of memory mainbus0 (root) cpu0 at mainbus0: ID 0 (primary), 21164A (pass 2) mcbus0 at mainbus0 mcmem0 at mcbus0 mid 1: Memory mcpcia0 at mcbus0 mid 5: PCI Bridge mcpcia0: Horse Revision 3, Left Handed Saddle Revision 3, CAP Revision 2 pci0 at mcpcia0 bus 0 ncr0 at pci0 dev 1 function 0: ncr 53c810 fast10 scsi ncr0: interrupting at kn300 irq 16 PCI Interrupt Pin A ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr0: single-ended, open drain IRQ driver ncr0: restart (scsi reset). scsibus0 at ncr0: 8 targets cd0 at scsibus0 targ 5 lun 0: SCSI2 5/cdrom removable probe(ncr0:5:1): 10.0 MB/s (100 ns, offset 8) ppb0 at pci0 dev 2 function 0: Digital Equipment DECchip 21050 PCI-PCI Bridge (rev. 0x02) pci1 at ppb0 bus 2 isp0 at pci1 dev 0 function 0 isp0: Board Revision 1020, loaded F/W Revision 2.10 isp0: devparm, W=wide, S=sync, T=Tag isp0: interrupting at kn300 irq 0 PCI Interrupt Pin A scsibus1 at isp0: 16 targets sd0 at scsibus1 targ 0 lun 0: SCSI2 0/direct fixed sd0: 4091MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors de0 at pci0 dev 4 function 0 de0: interrupting at kn300 irq 8 PCI Interrupt Pin A de0: DEC DE500-AA 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:f8:1e:e2:2f esh0 at pci0 dev 5 function 0: RoadRunner HIPPI esh0: interrupting at kn300 irq 12 PCI Interrupt Pin A mcpcia1 at mcbus0 mid 4: PCI Bridge mcpcia1: Horse Revision 3, Left Handed Saddle Revision 3, CAP Revision 2 pci2 at mcpcia1 bus 0 pceb0 at pci2 dev 1 function 0: Intel 82375EB/SB PCI-EISA Bridge (PCEB) (rev. 0x15) isp1 at pci2 dev 2 function 0 isp1: Board Revision 1040B, loaded F/W Revision 2.10 isp1: devparm, W=wide, S=sync, T=Tag isp1: interrupting at kn300 irq 0 PCI Interrupt Pin A scsibus2 at isp1: 16 targets sd1 at scsibus2 targ 4 lun 1: SCSI2 0/direct fixed sd1: 156260MB, 12594 cyl, 64 head, 141 sec, 512 bytes/sect x 320020992 sectors S3 Trio32/64 (VGA display, revision 0x54) at pci2 dev 3 function 0 not configured isp2 at pci2 dev 4 function 0 isp2: Board Revision 1040B, loaded F/W Revision 2.10 isp2: devparm, W=wide, S=sync, T=Tag isp2: interrupting at kn300 irq 8 PCI Interrupt Pin A scsibus3 at isp2: 16 targets sd2 at scsibus3 targ 5 lun 0: SCSI2 0/direct fixed sd2: 156260MB, 25188 cyl, 64 head, 32 sec, 512 bytes/sect x 320020992 sectors eisa0 at pceb0 isa0 at pceb0 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo com0: console com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo mcclock0 at isa0 port 0x70-0x71: mc146818 or compatible mcpcia2 at mcbus0 mid 7: PCI Bridge mcpcia2: Horse Revision 3, Right Handed Saddle Revision 0, CAP Revision 2 pci3 at mcpcia2 bus 0 isp3 at pci3 dev 2 function 0 isp3: Board Revision 1040B, loaded F/W Revision 2.10 isp3: devparm, W=wide, S=sync, T=Tag isp3: interrupting at kn300 irq 0 PCI Interrupt Pin A scsibus4 at isp3: 16 targets sd3 at scsibus4 targ 5 lun 0: SCSI2 0/direct fixed sd3: 156260MB, 25188 cyl, 64 head, 32 sec, 512 bytes/sect x 320020992 sectors sd4 at scsibus4 targ 5 lun 1: SCSI2 0/direct fixed sd4: 156260MB, 12594 cyl, 64 head, 141 sec, 512 bytes/sect x 320020992 sectors esh1 at pci3 dev 4 function 0: RoadRunner HIPPI esh1: interrupting at kn300 irq 8 PCI Interrupt Pin A mcpcia3 at mcbus0 mid 6: PCI Bridge mcpcia3: Horse Revision 3, Right Handed Saddle Revision 0, CAP Revision 2 pci4 at mcpcia3 bus 0 isp4 at pci4 dev 2 function 0 isp4: Board Revision 1040B, loaded F/W Revision 2.10 isp4: devparm, W=wide, S=sync, T=Tag isp4: interrupting at kn300 irq 0 PCI Interrupt Pin A scsibus5 at isp4: 16 targets sd5 at scsibus5 targ 4 lun 0: SCSI2 0/direct fixed sd5: 156260MB, 12594 cyl, 64 head, 141 sec, 512 bytes/sect x 320020992 sectors sd6 at scsibus5 targ 4 lun 1: SCSI2 0/direct fixed sd6: 156260MB, 12594 cyl, 64 head, 141 sec, 512 bytes/sect x 320020992 sectors isp5 at pci4 dev 3 function 0 isp5: Board Revision 1040B, loaded F/W Revision 2.10 isp5: devparm, W=wide, S=sync, T=Tag isp5: interrupting at kn300 irq 4 PCI Interrupt Pin A scsibus6 at isp5: 16 targets sd7 at scsibus6 targ 5 lun 0: SCSI2 0/direct fixed sd7: 156260MB, 12594 cyl, 64 head, 141 sec, 512 bytes/sect x 320020992 sectors sd8 at scsibus6 targ 5 lun 1: SCSI2 0/direct fixed sd8: 156260MB, 12594 cyl, 64 head, 141 sec, 512 bytes/sect x 320020992 sectors isp6 at pci4 dev 4 function 0 isp6: Board Revision 1040B, loaded F/W Revision 2.10 isp6: devparm, W=wide, S=sync, T=Tag isp6: interrupting at kn300 irq 8 PCI Interrupt Pin A scsibus7 at isp6: 16 targets stray mcbus0 mid 4 PCI Slot 2 PCI Interrupt Pin A irq 0 stray mcbus0 mid 5 PCI Slot 1 PCI Interrupt Pin A irq 16 stray mcbus0 mid 6 PCI Slot 2 PCI Interrupt Pin A irq 0 stray mcbus0 mid 7 PCI Slot 2 PCI Interrupt Pin A irq 0 root on sd0a dumps on sd0b root file system type: ffs de0: enabling Full Duplex 100baseTX port esh0: startup runcode version 2.0.19, options 28 esh0: firmware up esh0: startup runcode version 2.0.19, options 28 esh0: firmware up esh0: link up SHELL STUFF: Script started on Sat Jun 20 19:50:42 1998 isaac.nas.nasa.gov > df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0a 3550961 470015 2903397 14% / mfs:146 96655 7 91815 0% /tmp caves:/home 3985477 2903754 882449 77% /home jules:/usr/src 4152880 873440 3071792 22% /usr/src /dev/ccd0b 796843696 8 757001496 0% /mnt isaac.nas.nasa.gov > root lmdd of=/mnt/file bs=64k count=5000 312.50 MB in 5.11 seconds (61.1845 MB/sec) isaac.nas.nasa.gov > ^50^550 root lmdd of=/mnt/file bs=64k count=55000 3437.50 MB in 52.77 seconds (65.1443 MB/sec) isaac.nas.nasa.gov > exit exit Script done on Sat Jun 20 19:52:13 1998 --------------63A555FF39591B2864454D00-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 20 19:59:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19766 for freebsd-hardware-outgoing; Sat, 20 Jun 1998 19:59:27 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19759 for ; Sat, 20 Jun 1998 19:59:25 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id UAA20389; Sat, 20 Jun 1998 20:59:22 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199806210259.UAA20389@panzer.plutotech.com> Subject: Re: 64M SIMM differences In-Reply-To: <19980619134635.A21640@clifford.inch.com> from Omar Thameen at "Jun 19, 98 01:46:35 pm" To: omar@clifford.inch.com (Omar Thameen) Date: Sat, 20 Jun 1998 20:59:22 -0600 (MDT) Cc: freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Omar Thameen wrote... > In addition to all the parity/nonparity, EDO issues, I've been made > aware that there are 2 types of 64M SIMMs - one has 8 chips on it and > the other has 32 chips. > > Is there a difference in performance for these two types? The fact > that the 32 chip 64M SIMM is half the price of the 8 chip version > indicates one thing, but OTOH I called Kingston and their tech > support told me that the SIMMs perform the same. I think the performance will be the same for the two types of SIMMs, but the thing to remember is that some motherboards can't take the ones with more chips. In particular, most ASUS boards need SIMMs with 25 chips or less each. So, if you've got an ASUS board or if your manufacturer says something about it, get the SIMMs with the lower chip count. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 20 20:43:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24589 for freebsd-hardware-outgoing; Sat, 20 Jun 1998 20:43:01 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from feral.com (root@gw100.feral.com [192.67.166.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24583 for ; Sat, 20 Jun 1998 20:42:55 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral-gw (mjacob@gw100.feral.com [192.67.166.129]) by feral.com (8.8.6/8.8.6) with SMTP id UAA17078; Sat, 20 Jun 1998 20:42:41 -0700 Message-ID: <358C8131.4DBD2F89@feral.com> Date: Sat, 20 Jun 1998 20:42:41 -0700 From: Matthew Jacob Organization: Feral Software X-Mailer: Mozilla 3.04 (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: "Jan B. Koum" , "Mr G.D. Tyson" , port-i386@netbsd.org, freebsd-hardware@FreeBSD.ORG Subject: Re: O/S Support for large [512Mb] PC systems References: <358C7656.39B08E3@feral.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Excuse me! I was stupid! The i386 isn't showing the actual amount of memory it usually runs with! It had 512MB installed... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message