From owner-freebsd-smp Mon Jun 15 19:17:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10113 for freebsd-smp-outgoing; Mon, 15 Jun 1998 19:17:02 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA10107 for ; Mon, 15 Jun 1998 19:17:00 -0700 (PDT) (envelope-from seth@pengar.com) Received: from ([192.168.0.2]) [166.70.2.35] by mail.xmission.com with esmtp (Exim 1.82 #2) id 0yllIu-00025a-00; Mon, 15 Jun 1998 20:16:56 -0600 X-Sender: seth-pc@hobbiton.shire.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 15 Jun 1998 20:19:52 +0100 To: freebsd-smp@FreeBSD.ORG From: Seth Leigh Subject: Temp. Monitoring Software for Intel Providence mobo? Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all. I know a few people have bought Intel PR440FX Providence dual PPro motherboards recently, as have I. My machine is up and running just great now. I want to be able to monitor the temperatures of my two PPro cpus. Does anyone know if there is any software available already that can talk to the motherboard's temp. sensing hardware? If not, does anyone know where I would look to find out what I would need to know to write a simple program for this myself? If I successfully write or find some temp. software for this motherboard, I will of course share it with anyone else who wants it. I am running the FreeBSD 3.0-980311-SNAP. Seth Leigh seth@pengar.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Jun 15 21:43:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06400 for freebsd-smp-outgoing; Mon, 15 Jun 1998 21:43:48 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from jsackett.slip.rtd.com (root@jsackett.slip.rtd.com [198.102.68.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06376 for ; Mon, 15 Jun 1998 21:43:44 -0700 (PDT) (envelope-from jsackett@jsackett.slip.rtd.com) Received: from jsackett.slip.rtd.com (jsackett@jsackett.slip.rtd.com [198.102.68.45]) by jsackett.slip.rtd.com (8.8.7/8.8.7) with ESMTP id VAA26171; Mon, 15 Jun 1998 21:43:09 -0700 (MST) (envelope-from jsackett@jsackett.slip.rtd.com) Message-ID: <3585F7DC.5102A9E2@jsackett.slip.rtd.com> Date: Mon, 15 Jun 1998 21:43:09 -0700 From: "John L. Sackett III" Organization: Sackett Enterprises X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: "freebsd-smp@freebsd.org" CC: jsackett@rtd.com Subject: Re: Temp. Monitoring Software for Intel Providence mobo? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Seth Leigh wrote: > Hi all. > I know a few people have bought Intel PR440FX Providence dual PPro > motherboards recently, as have I. My machine is up and running just great > now. I want to be able to monitor the temperatures of my two PPro cpus. > Does anyone know if there is any software available already that can talk > to the motherboard's temp. sensing hardware? If not, does anyone know > where I would look to find out what I would need to know to write a simple > program for this myself? > > If I successfully write or find some temp. software for this motherboard, I > will of course share it with anyone else who wants it. I am running the > FreeBSD 3.0-980311-SNAP. > > Seth Leigh > seth@pengar.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message Hi Seth: good to hear someone else is up and running on a fresh PR440FX install. I bought a micronics li-6 because I got so frustrated trying to run NT on an IDE drive-Freebsd on SCSI. Everytime (once every 3 days) I booted it (NT)I got a BSOD. Even with SP3. Well the PPro's just keep getting more affordable and i built a new box with old harddrive, new case, cdrom, etc. My question is - where did you find a VRM for the second proc? They are hard to come by. I want to go 3.0 on my Micronics board, but am having difficulty finding a VRM. Someone Quoted $52.00 from a manufacturer, but that seems insane when you can find the whole board for 65-70, with the second VRM mind you. If you have a good source let me know. I have been up on FreeBSD 3.0-980520-SNAP for about a week and a half now, just slicing away. Man the kernel rebuilds are speedy! John Sackett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Jun 15 22:21:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14992 for freebsd-smp-outgoing; Mon, 15 Jun 1998 22:21:03 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from pozo.com (pozo.pozo.com [207.201.8.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14963 for ; Mon, 15 Jun 1998 22:20:56 -0700 (PDT) (envelope-from mantar@netcom.com) Received: from dual (DUAL [192.168.0.2]) by pozo.com (8.8.8/8.8.8) with SMTP id WAA08321; Mon, 15 Jun 1998 22:20:38 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <199806160520.WAA08321@pozo.com> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Mon, 15 Jun 1998 22:20:38 -0700 To: "John L. Sackett III" , "freebsd-smp@freebsd.org" From: Manfred Antar Subject: Re: Temp. Monitoring Software for Intel Providence mobo? Cc: jsackett@rtd.com In-Reply-To: <3585F7DC.5102A9E2@jsackett.slip.rtd.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 09:43 PM 6/15/98 -0700, John L. Sackett III wrote: >Seth Leigh wrote: > >> Hi all. >> I know a few people have bought Intel PR440FX Providence dual PPro >> motherboards recently, as have I. My machine is up and running just great >> now. I want to be able to monitor the temperatures of my two PPro cpus. >> Does anyone know if there is any software available already that can talk >> to the motherboard's temp. sensing hardware? If not, does anyone know >> where I would look to find out what I would need to know to write a simple >> program for this myself? >> >> If I successfully write or find some temp. software for this motherboard, I >> will of course share it with anyone else who wants it. I am running the >> FreeBSD 3.0-980311-SNAP. >> >> Seth Leigh >> seth@pengar.com >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-smp" in the body of the message > > Hi Seth: >good to hear someone else is up and running on a fresh PR440FX install. I >bought a >micronics li-6 because I got so frustrated trying to run NT on an IDE >drive-Freebsd on SCSI. Everytime >(once every 3 days) I booted it (NT)I got a BSOD. Even with SP3. Well the >PPro's just keep getting more affordable and i built a new box with old >harddrive, new case, cdrom, etc. >My question is - where did you find a VRM for the second proc? They are hard >to come by. I want to go 3.0 on my Micronics board, but am having difficulty >finding a VRM. Someone Quoted $52.00 from a manufacturer, but that seems >insane when you can find the whole board for 65-70, with the second VRM mind >you. If you have a >good source let me know. I have been up on FreeBSD 3.0-980520-SNAP for about >a week and a half now, just slicing away. Man the kernel rebuilds are speedy! > I just bought 3 of these boards that came with the VRM's for $94 each. I didn't know they came with them, so i called INTEL and they sent me to this page http://developer.intel.com/design/pentiumii/components/ It's for pentium II but there is a section on VRM's and the people listed there probably can help you. The prices might be high though Manfred ============================== || mantar@netcom.com || || pozo@infinex.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 16 00:02:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06246 for freebsd-smp-outgoing; Tue, 16 Jun 1998 00:02:41 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06235 for ; Tue, 16 Jun 1998 00:02:37 -0700 (PDT) (envelope-from luoqi@lor.watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id DAA24257; Tue, 16 Jun 1998 03:02:06 -0400 (EDT) (envelope-from luoqi) Date: Tue, 16 Jun 1998 03:02:06 -0400 (EDT) From: Luoqi Chen Message-Id: <199806160702.DAA24257@lor.watermarkgroup.com> To: freebsd-smp@FreeBSD.ORG, jsackett@jsackett.slip.rtd.com Subject: Re: Temp. Monitoring Software for Intel Providence mobo? Cc: jsackett@rtd.com Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > My question is - where did you find a VRM for the second proc? They are hard > to come by. I want to go 3.0 on my Micronics board, but am having difficulty > finding a VRM. Someone Quoted $52.00 from a manufacturer, but that seems > insane when you can find the whole board for 65-70, with the second VRM mind > you. If you have a > good source let me know. I have been up on FreeBSD 3.0-980520-SNAP for about > a week and a half now, just slicing away. Man the kernel rebuilds are speedy! > > John Sackett > You should be able to get one at $30+. Do a search on ComputerESP and look for voltage, you should see VRMs for AMI's Merlin and Goalith motherboard, they are in fact VXI (www.vxie.com) PPro VRMs repackaged by AMI, and should work on any dual-PPro board. Hope this helps. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 17 06:31:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22528 for freebsd-smp-outgoing; Wed, 17 Jun 1998 06:31:29 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from soran.pacific.net.sg (soran.pacific.net.sg [203.120.90.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22516 for ; Wed, 17 Jun 1998 06:31:24 -0700 (PDT) (envelope-from aguiquin@pacific.net.sg) Received: from pop1.pacific.net.sg (pop1.pacific.net.sg [203.120.90.85]) by soran.pacific.net.sg with ESMTP id VAA00903 for ; Wed, 17 Jun 1998 21:31:16 +0800 (SGT) Received: from windowsu (dyn241ppp130.pacific.net.sg [210.24.241.130]) by pop1.pacific.net.sg with SMTP id VAA26259 for ; Wed, 17 Jun 1998 21:31:14 +0800 (SGT) Message-Id: <3.0.3.32.19980617213650.007b0b80@pacific.net.sg> X-Sender: aguiquin@pacific.net.sg X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Wed, 17 Jun 1998 21:36:50 +0800 To: freebsd-smp@FreeBSD.ORG From: "Anthony A. Guiquin" Subject: free bsd copy Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org greetings !!! may i ask you where i can get a free bsd operating system i am just interested in learning the use of the unix system deeper thank you, anthony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 17 08:31:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08992 for freebsd-smp-outgoing; Wed, 17 Jun 1998 08:31:26 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08964; Wed, 17 Jun 1998 08:31:21 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id JAA03977; Wed, 17 Jun 1998 09:31:03 -0600 (MDT) Message-Id: <199806171531.JAA03977@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Atipa cc: Andrew Gallatin , Doug Junkins , freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: 440BX based SMP systems In-reply-to: Your message of "Thu, 11 Jun 1998 11:54:14 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Jun 1998 09:31:03 -0600 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > > The ASUS DS should work well, but will require the CAM driver for the > onboard SCSI. It uses AIC-7890. > > Great board though; I'd recommend PC100/ECC DIMMS for best reliability. > > Single P2-400's are fast as hell. If I am not mistaken, we sent one of > these boards to Steve Passe (smp@csn.net), who does much of the SMP > development. If it didn't work, he probably would have returned it. For the record, the last board I got from atipa was an ASUS P2L97DS. I tried a Gigabyte GA-686DL2 but it wasn't stable so I returned it. The P2L97DS is running an smp snap from about 1 month ago, works GREAT! I do intend to get a Asus P2B-DS, but will probably wait till 450s are available. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 17 11:41:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09922 for freebsd-smp-outgoing; Wed, 17 Jun 1998 11:41:14 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa3-01.ix.netcom.com [206.214.137.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09907 for ; Wed, 17 Jun 1998 11:41:10 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id LAA00435; Wed, 17 Jun 1998 11:41:00 -0700 (PDT) (envelope-from tomdean) Date: Wed, 17 Jun 1998 11:41:00 -0700 (PDT) Message-Id: <199806171841.LAA00435@ix.netcom.com> From: Thomas Dean To: aguiquin@pacific.net.sg CC: freebsd-smp@FreeBSD.ORG In-reply-to: <3.0.3.32.19980617213650.007b0b80@pacific.net.sg> (aguiquin@pacific.net.sg) Subject: Re: free bsd copy Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Look at http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 18 06:21:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00654 for freebsd-smp-outgoing; Thu, 18 Jun 1998 06:21:00 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from charon.fmi.com (uucp@charon.fmi.com [157.33.227.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00637 for ; Thu, 18 Jun 1998 06:20:55 -0700 (PDT) (envelope-from Brendon_Meyer@fmi.com) Received: (from uucp@localhost) by charon.fmi.com (8.8.5/8.6.12) id NAA02924 for ; Thu, 18 Jun 1998 13:20:51 GMT Received: from babylon.nola.fmi.com(157.33.3.49) by charon.fmi.com via smap (V1.3) id xma002918; Thu, 18 Jun 98 13:20:36 GMT Received: from ficrns.crns.fmi.com (ficrns.crns.fmi.com [157.49.1.4]) by babylon.nola.fmi.com (8.6.9/8.6.12) with SMTP id IAA22034 for ; Thu, 18 Jun 1998 08:20:29 -0500 Received: from exsysadm.tpra.fmi.com by ficrns.crns.fmi.com with SMTP id AA07884 (5.65c+/IDA-1.4.4 for ); Thu, 18 Jun 1998 23:23:23 +1000 Received: from fmi.com (localhost.jkta.fmi.com [127.0.0.1]) by exsysadm.tpra.fmi.com (8.8.8/8.8.8) with ESMTP id XAA03944 for ; Thu, 18 Jun 1998 23:21:11 +1000 (EST) (envelope-from Brendon_Meyer@fmi.com) Message-Id: <35891444.453D8CE7@fmi.com> Date: Thu, 18 Jun 1998 23:21:08 +1000 From: Brendon Meyer Organization: PT Mineserve International X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) Mime-Version: 1.0 To: freebsd-smp@FreeBSD.ORG Subject: AMI Goliath Board Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Fellas, An addition to your SMP page. We now have two (2) systems based on the AMI Goliath board ( n <= 4 PentiumPro 200) up and running Under FreeBSD 3.0-Snapshot (October 97) A note though. You can't leave the 'mptable' kernel entries default (i.e. NCPU, etc) if you want SMP to work reliably. YOu have to uncomment them. Here is the output from the MPTABLE command for this system. / 103# mptable =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000faf20 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0x9a mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x0009fd00 signature: 'PCMP' base table length: 292 version: 1.4 checksum: 0xc8 OEM ID: 'AMI ' Product ID: 'GOLIATH ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 25 local APIC address: 0xfee00000 extended table length: 144 extended table checksum: 167 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 3 0x11 BSP, usable 6 1 9 0xfbff 0 0x11 AP, usable 6 1 9 0xfbff 1 0x11 AP, usable 6 1 9 0xfbff 2 0x11 AP, usable 6 1 9 0xfbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 EISA -- I/O APICs: APIC ID Version State Address 14 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# INT conforms conforms 2 1 14 1 INT conforms conforms 2 0 14 2 INT conforms conforms 2 3 14 3 INT conforms conforms 2 4 14 4 INT conforms conforms 2 5 14 5 INT conforms conforms 2 6 14 6 INT conforms conforms 2 7 14 7 INT conforms conforms 2 8 14 8 INT conforms conforms 2 9 14 9 INT conforms conforms 2 10 14 10 INT conforms conforms 2 11 14 11 INT conforms conforms 2 12 14 12 INT conforms conforms 2 13 14 13 INT conforms conforms 2 14 14 14 INT conforms conforms 2 15 14 15 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: -- bus ID: 0 address type: memory address address base: 0x0 address range: 0xfeb00000 -- bus ID: 0 address type: memory address address base: 0xfec00000 address range: 0x1400000 -- bus ID: 1 address type: memory address address base: 0xfeb00000 address range: 0x100000 -- bus ID: 0 address type: I/O address address base: 0x0 address range: 0xe000 -- bus ID: 0 address type: I/O address address base: 0xf000 address range: 0x1000 -- bus ID: 1 address type: I/O address address base: 0xe000 address range: 0x1000 -- bus ID: 2 bus info: 0x01 parent bus ID: 0-- bus ID: 0 address modifier: add predefined range: 0x00000000-- bus ID: 0 address modifier: add predefined range: 0x00000001 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=4 # number of CPUs #options NBUS=3 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs =============================================================================== Enjoy. Brendon Meyer (Brendon_Meyer@fmi.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 18 23:59:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09319 for freebsd-smp-outgoing; Thu, 18 Jun 1998 23:59:03 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09281; Thu, 18 Jun 1998 23:58:58 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id IAA00397; Fri, 19 Jun 1998 08:58:59 +0200 (CEST) (envelope-from sos) Message-Id: <199806190658.IAA00397@sos.freebsd.dk> Subject: TYAN 1668 anyone ?? To: smp@FreeBSD.ORG, hackers@FreeBSD.ORG (FreeBSD hackers) Date: Fri, 19 Jun 1998 08:58:59 +0200 (CEST) From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have this most odd problem with at least 3 of these boards (TYAN 1668 dual P6). The problem is that those boards can lock up totally given a set of specific events: Run in a high res graphics mode, that uses linear addressing. Use the mouse together with disk activity. This can be done in either X, win95 or winNT with the same sad result, a total lockup of the system. If I use the mouse in a textmode, or in a graphics mode that uses banking, the problem doesn't appear. We have tried anything here, we have the problem in 3 machines all of them have had their motherboards changed several times, we have tried different videocards, mouses, tried SCSI vs IDE, you name it, everytime with the same result. They can all "make world" for days in an xterm, given that you dont touch the mouse, if you do move the mouse and hit a bottom that will hang the machin solid in 80% of the cases. I have a TYAN 1662 board which is allmost the same just AT instead of ATX, and it doesn't show this behavior, even with the same parts put into the machine.... Any ideas, I'm totally at a loss here.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 19 06:58:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17514 for freebsd-smp-outgoing; Fri, 19 Jun 1998 06:58:15 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17381; Fri, 19 Jun 1998 06:58:04 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id IAA12645; Fri, 19 Jun 1998 08:56:19 -0400 (EDT) Date: Fri, 19 Jun 1998 08:56:19 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: =?iso-8859-1?Q?S=F8ren_Schmidt?= cc: smp@FreeBSD.ORG, FreeBSD hackers Subject: Re: TYAN 1668 anyone ?? In-Reply-To: <199806190658.IAA00397@sos.freebsd.dk> Message-ID: 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 GAA17495 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 19 Jun 1998, Søren Schmidt wrote: > > I have this most odd problem with at least 3 of these boards > (TYAN 1668 dual P6). > > The problem is that those boards can lock up totally given a set > of specific events: > > Run in a high res graphics mode, that uses linear addressing. > Use the mouse together with disk activity. > > This can be done in either X, win95 or winNT with the same sad > result, a total lockup of the system. > > If I use the mouse in a textmode, or in a graphics mode that > uses banking, the problem doesn't appear. > > We have tried anything here, we have the problem in 3 machines > all of them have had their motherboards changed several times, > we have tried different videocards, mouses, tried SCSI vs IDE, > you name it, everytime with the same result. > > They can all "make world" for days in an xterm, given that you > dont touch the mouse, if you do move the mouse and hit a bottom > that will hang the machin solid in 80% of the cases. > > I have a TYAN 1662 board which is allmost the same just AT instead > of ATX, and it doesn't show this behavior, even with the same > parts put into the machine.... > > Any ideas, I'm totally at a loss here.... I have a 1662 with 2 PPro 166/512's here, running with a Cirrus 5436 card, doing 1024X1280. 64 megs memory, and just as stable as a rock. Done many hundreds of buildworlds, only once have I ever had a panic. Using Option "linear" in my XF86Config file. Toss a test at me if you want. I'm not using softupdates or CAM, tho, and I only use a mouse in X. I often do the buildworlds while I'm screwing around with something else, even netscape. I have 4 G of disk, with 192M of swap. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 19 11:12:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05986 for freebsd-smp-outgoing; Fri, 19 Jun 1998 11:12:36 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from gw2.asacomputers.com (gw1.asacomputers.com [204.69.220.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05849; Fri, 19 Jun 1998 11:11:44 -0700 (PDT) (envelope-from kedar@asacomputers.com) Received: from kedar.asacomputers.com (alan.asacomputers.com [204.153.176.86]) by gw2.asacomputers.com (8.8.8/8.8.8) with SMTP id LAA04113; Fri, 19 Jun 1998 11:11:37 -0700 (PDT) (envelope-from kedar@asacomputers.com) Message-Id: <2.2.32.19980619180827.014fad94@gw1> X-Sender: rajadnya@gw1 X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 19 Jun 1998 11:08:27 -0700 To: sos@FreeBSD.ORG From: Kedar Rajadnya Subject: Re: TYAN 1668 anyone ?? Cc: smp@FreeBSD.ORG Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA05896 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We had that happen to us with NT systems and the 1668. Sometimes, it had to do with memory. We found that we had to use *very* specific SIMMS. Specially if they are 64MB SIMMS or above. They tended not to like EDO simms and preferred parity. Above 192MB, they almost always cause problems. It might be one of the reasons? Regards, Kedar. At 08:58 AM 6/19/98 +0200, you wrote: > >I have this most odd problem with at least 3 of these boards >(TYAN 1668 dual P6). > >The problem is that those boards can lock up totally given a set >of specific events: > >Run in a high res graphics mode, that uses linear addressing. >Use the mouse together with disk activity. > >This can be done in either X, win95 or winNT with the same sad >result, a total lockup of the system. > >If I use the mouse in a textmode, or in a graphics mode that >uses banking, the problem doesn't appear. > >We have tried anything here, we have the problem in 3 machines >all of them have had their motherboards changed several times, >we have tried different videocards, mouses, tried SCSI vs IDE, >you name it, everytime with the same result. > >They can all "make world" for days in an xterm, given that you >dont touch the mouse, if you do move the mouse and hit a bottom >that will hang the machin solid in 80% of the cases. > >I have a TYAN 1662 board which is allmost the same just AT instead >of ATX, and it doesn't show this behavior, even with the same >parts put into the machine.... > >Any ideas, I'm totally at a loss here.... > >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? >.. > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-smp" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 19 12:07:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16079 for freebsd-smp-outgoing; Fri, 19 Jun 1998 12:07:08 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15960; Fri, 19 Jun 1998 12:06:22 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id VAA01877; Fri, 19 Jun 1998 21:06:05 +0200 (CEST) (envelope-from sos) Message-Id: <199806191906.VAA01877@sos.freebsd.dk> Subject: Re: TYAN 1668 anyone ?? In-Reply-To: <2.2.32.19980619180827.014fad94@gw1> from Kedar Rajadnya at "Jun 19, 98 11:08:27 am" To: kedar@asacomputers.com (Kedar Rajadnya) Date: Fri, 19 Jun 1998 21:06:05 +0200 (CEST) Cc: sos@FreeBSD.ORG, smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to Kedar Rajadnya who wrote: > We had that happen to us with NT systems and the 1668. Sometimes, it had to > do with memory. We found that we had to use *very* specific SIMMS. > Specially if they are 64MB SIMMS or above. They tended not to like EDO > simms and preferred parity. Above 192MB, they almost always cause problems. > > It might be one of the reasons? Hmm, I doubt it, I use only prime quality RAM here (because of exactly that reason), and the same RAM works just fine in a 1662 board, which is just as picky... I have just changed the videocard once again in one of those machines to an old Diamond Viper PRO video (P9100 based) and it hasn't failed yet, in fact I'm writing this in a xterm on it.... I have a wierd feeling that these boards don't like S3 cards, all the others we've tried where different vinatage S3 boards. Well we'll see what happens, but it hasn't that stable with any of the other cards... Anybody else seen problems with S3 cards ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 19 13:00:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23725 for freebsd-smp-outgoing; Fri, 19 Jun 1998 13:00:20 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from corona.jcmax.com (corona.jcmax.com [204.69.248.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA22579 for ; Fri, 19 Jun 1998 12:56:01 -0700 (PDT) (envelope-from cr@jcmax.com) Received: by corona.jcmax.com (5.65/2.58G/4.1.3_U1) id AA19235; Fri, 19 Jun 98 15:52:56 -0400 Date: Fri, 19 Jun 98 15:52:56 -0400 From: cr@jcmax.com (Cyrus Rahman) Message-Id: <9806191952.AA19235@corona.jcmax.com> To: smp@FreeBSD.ORG Subject: Re: S3 video cards Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have just changed the videocard once again in one of those machines to > an old Diamond Viper PRO video (P9100 based) and it hasn't failed yet, in > fact I'm writing this in a xterm on it.... > I have a wierd feeling that these boards don't like S3 cards, all the > others we've tried where different vinatage S3 boards. > Well we'll see what happens, but it hasn't that stable with any of the > other cards... > Anybody else seen problems with S3 cards ?? After extensive testing, we concluded that S3 cards (and all derived chipsets, at least as of one year ago) don't address memory over 64mbytes correctly. So they do trash your os if you install them and use X. We tried all sorts of variants last year, and called the manufacturers of various S3 cards to see if they had new bios's for their boards to fix the problem. They advised us that it wasn't their fault, because the chips themselves were defective and they couldn't work around it. The problem was not confined to FreeBSD - it occurred on SCO as well. Perhaps Windows95 and NT have some workaround like a bounce buffer, but then again it sounds as if it didn't work on those platforms for you. And the card manufacturers wouldn't have already known about the problem anyway unless it occurred on Microsoft OS's. The cards will perform quite reliably if you keep less than 64mbytes on the board. And I doubt the problem has anything to do with the motherboard. Since that time we've avoided S3 chips. There are plenty of cheap alternatives that work well. So the moral of the story is: Using an S3 card with more than 64mbytes of memory will crash your system as soon as you start DMA'ing memory around by raising and lowering windows in X. Those funny looking areas that should have been solid black are kernel pages, and your buffer cache is now black with a 10 point Courier font (actually, we never saw file corruption, but we worried about it during testing). Let me know if this sounds like it could be your problem. Cyrus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 19 13:03:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24415 for freebsd-smp-outgoing; Fri, 19 Jun 1998 13:03:11 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from kaori.communique.net (kaori.communique.net [204.27.67.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24348; Fri, 19 Jun 1998 13:02:50 -0700 (PDT) (envelope-from tjohnson@verio.net) Received: by KAORI with Internet Mail Service (5.0.1458.49) id ; Fri, 19 Jun 1998 14:45:30 -0500 Message-ID: From: Tony Johnson To: "'Chuck Robey'" , =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: smp@FreeBSD.ORG, FreeBSD hackers Subject: RE: TYAN 1668 anyone ?? Date: Fri, 19 Jun 1998 14:45:28 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: multipart/mixed; boundary="---- =_NextPart_000_01BD9B90.E8266C30" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------ =_NextPart_000_01BD9B90.E8266C30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I got a few lockups when I had dram refresh queue and I think the other option is fast dram leadoff turned on in chipset options of my = bios.(awd 5.01) The bios defaults turns them on I think. Turning them off fixed my lockup problems. They would happen to me when I had heavy disk access and I moved the mouse and noticed the pc locked up. I have a Tyan 1668 -----Original Message----- From: Chuck Robey [mailto:chuckr@glue.umd.edu] Sent: Friday, June 19, 1998 7:56 AM To: S=F8ren Schmidt Cc: smp@FreeBSD.ORG; FreeBSD hackers Subject: Re: TYAN 1668 anyone ?? On Fri, 19 Jun 1998, S=F8ren Schmidt wrote: >=20 > I have this most odd problem with at least 3 of these boards > (TYAN 1668 dual P6). >=20 > The problem is that those boards can lock up totally given a set > of specific events: >=20 > Run in a high res graphics mode, that uses linear addressing. > Use the mouse together with disk activity. >=20 > This can be done in either X, win95 or winNT with the same sad > result, a total lockup of the system. >=20 > If I use the mouse in a textmode, or in a graphics mode that > uses banking, the problem doesn't appear. >=20 > We have tried anything here, we have the problem in 3 machines > all of them have had their motherboards changed several times, > we have tried different videocards, mouses, tried SCSI vs IDE, > you name it, everytime with the same result. >=20 > They can all "make world" for days in an xterm, given that you > dont touch the mouse, if you do move the mouse and hit a bottom > that will hang the machin solid in 80% of the cases. >=20 > I have a TYAN 1662 board which is allmost the same just AT instead > of ATX, and it doesn't show this behavior, even with the same > parts put into the machine.... >=20 > Any ideas, I'm totally at a loss here.... I have a 1662 with 2 PPro 166/512's here, running with a Cirrus 5436 card, doing 1024X1280. 64 megs memory, and just as stable as a rock. Done many hundreds of buildworlds, only once have I ever had a panic. Using Option "linear" in my XF86Config file. Toss a test at me if you want. I'm not using softupdates or CAM, tho, and I only use a mouse in X. I often do the buildworlds while I'm screwing around with something else, even netscape. I have 4 G of = disk, with 192M of swap. >=20 > -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D- > S=F8ren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message >=20 >=20 ----------------------------+-------------------------------------------= ---- Chuck Robey | Interests include any kind of voice or data=20 chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+-------------------------------------------= ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message ------ =_NextPart_000_01BD9B90.E8266C30 Content-Type: application/octet-stream; name="Tony Johnson.vcf" Content-Disposition: attachment; filename="Tony Johnson.vcf" BEGIN:VCARD VERSION:2.1 N:Johnson;Greg FN:Tony Johnson EMAIL;PREF;INTERNET:tjohnson@gulfsouth.verio.net REV:19980326T195655Z END:VCARD ------ =_NextPart_000_01BD9B90.E8266C30-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 19 14:31:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09821 for freebsd-smp-outgoing; Fri, 19 Jun 1998 14:31:58 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from adsdevelop2.autodebit.com (adsdevelop2.autodebit.com [204.50.245.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09801 for ; Fri, 19 Jun 1998 14:31:36 -0700 (PDT) (envelope-from davidg@autodebit.com) Received: by adsdevelop2.autodebit.com with Internet Mail Service (5.0.1460.8) id ; Fri, 19 Jun 1998 14:33:00 -0700 Message-ID: <71D507C37988D11182ED0000F80462AC0EE44D@adsdevelop2.autodebit.com> From: David Green-Seed To: "'cr@jcmax.com'" , smp@FreeBSD.ORG Subject: RE: S3 video cards Date: Fri, 19 Jun 1998 14:32:58 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't know if this is related, but I've noticed that my S3 Virge DX based video card tends to have intermittant problems - it appears as if fonts get corrupted. I haven't been able to determine what causes it. This occurs under Windows 95, NT and FreeBSD (far less often with FreeBSD) and appears to be fixable by switching video modes. The symptom exists with both 64MB and 128MB. (It's a 4MB card) Any insights would be appreciated. Dave. _________________________ David Green-Seed davidg@autodebit.com Automated Debit Systems > -----Original Message----- > From: cr@jcmax.com [SMTP:cr@jcmax.com] > Sent: Friday, June 19, 1998 12:53 PM > To: smp@FreeBSD.ORG > Subject: Re: S3 video cards > > > I have just changed the videocard once again in one of those machines to > > an old Diamond Viper PRO video (P9100 based) and it hasn't failed yet, > in > > fact I'm writing this in a xterm on it.... > > I have a wierd feeling that these boards don't like S3 cards, all the > > others we've tried where different vinatage S3 boards. > > Well we'll see what happens, but it hasn't that stable with any of the > > other cards... > > Anybody else seen problems with S3 cards ?? > > After extensive testing, we concluded that S3 cards (and all derived > chipsets, at least as of one year ago) don't address memory over 64mbytes > correctly. So they do trash your os if you install them and use X. > > We tried all sorts of variants last year, and called the manufacturers of > various S3 cards to see if they had new bios's for their boards to fix the > problem. They advised us that it wasn't their fault, because the chips > themselves were defective and they couldn't work around it. > > The problem was not confined to FreeBSD - it occurred on SCO as well. > Perhaps Windows95 and NT have some workaround like a bounce buffer, but > then > again it sounds as if it didn't work on those platforms for you. And the > card manufacturers wouldn't have already known about the problem anyway > unless it occurred on Microsoft OS's. > > The cards will perform quite reliably if you keep less than 64mbytes on > the > board. And I doubt the problem has anything to do with the motherboard. > > Since that time we've avoided S3 chips. There are plenty of cheap > alternatives that work well. > > So the moral of the story is: > > Using an S3 card with more than 64mbytes of memory will crash your system > as > soon as you start DMA'ing memory around by raising and lowering windows in > X. > > Those funny looking areas that should have been solid black are kernel > pages, and your buffer cache is now black with a 10 point Courier font > (actually, we never saw file corruption, but we worried about it during > testing). > > Let me know if this sounds like it could be your problem. > > Cyrus > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 20 00:27:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22664 for freebsd-smp-outgoing; Sat, 20 Jun 1998 00:27:59 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22659 for ; Sat, 20 Jun 1998 00:27:57 -0700 (PDT) (envelope-from fullermd@shell.futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id CAA17997; Sat, 20 Jun 1998 02:27:53 -0500 (CDT) Message-ID: <19980620022753.09201@futuresouth.com> Date: Sat, 20 Jun 1998 02:27:53 -0500 From: "Matthew D. Fuller" To: Cyrus Rahman Cc: smp@FreeBSD.ORG Subject: Re: S3 video cards References: <9806191952.AA19235@corona.jcmax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <9806191952.AA19235@corona.jcmax.com>; from Cyrus Rahman on Fri, Jun 19, 1998 at 03:52:56PM -0400 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jun 19, 1998 at 03:52:56PM -0400, Cyrus Rahman woke me up to tell me: > > I have just changed the videocard once again in one of those machines to > > an old Diamond Viper PRO video (P9100 based) and it hasn't failed yet, in > > fact I'm writing this in a xterm on it.... > > I have a wierd feeling that these boards don't like S3 cards, all the > > others we've tried where different vinatage S3 boards. > > Well we'll see what happens, but it hasn't that stable with any of the > > other cards... > > Anybody else seen problems with S3 cards ?? > > After extensive testing, we concluded that S3 cards (and all derived > chipsets, at least as of one year ago) don't address memory over 64mbytes > correctly. So they do trash your os if you install them and use X. > > We tried all sorts of variants last year, and called the manufacturers of > various S3 cards to see if they had new bios's for their boards to fix the > problem. They advised us that it wasn't their fault, because the chips > themselves were defective and they couldn't work around it. I don't think so. This machine has 72 megs of RAM and a S3 video card, and I'm raising and lowering no less than 23 windows at the moment... *mutter* Silly Compaq that it is.... *mutter* This machine was on closeout in August '96, so it falls under that one year ago. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 20 02:13:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01112 for freebsd-smp-outgoing; Sat, 20 Jun 1998 02:13:57 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01107 for ; Sat, 20 Jun 1998 02:13:54 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id LAA05181; Sat, 20 Jun 1998 11:13:43 +0200 (CEST) (envelope-from sos) Message-Id: <199806200913.LAA05181@sos.freebsd.dk> Subject: Re: S3 video cards In-Reply-To: <9806191952.AA19235@corona.jcmax.com> from Cyrus Rahman at "Jun 19, 98 03:52:56 pm" To: cr@jcmax.com (Cyrus Rahman) Date: Sat, 20 Jun 1998 11:13:43 +0200 (CEST) Cc: smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to Cyrus Rahman who wrote: > > I have just changed the videocard once again in one of those machines to > > an old Diamond Viper PRO video (P9100 based) and it hasn't failed yet, in > > fact I'm writing this in a xterm on it.... > > I have a wierd feeling that these boards don't like S3 cards, all the > > others we've tried where different vinatage S3 boards. > > Well we'll see what happens, but it hasn't that stable with any of the > > other cards... > > Anybody else seen problems with S3 cards ?? > > After extensive testing, we concluded that S3 cards (and all derived > chipsets, at least as of one year ago) don't address memory over 64mbytes > correctly. So they do trash your os if you install them and use X. > > So the moral of the story is: > > Using an S3 card with more than 64mbytes of memory will crash your system as > soon as you start DMA'ing memory around by raising and lowering windows in X. > > Those funny looking areas that should have been solid black are kernel > pages, and your buffer cache is now black with a 10 point Courier font > (actually, we never saw file corruption, but we worried about it during > testing). > > Let me know if this sounds like it could be your problem. Hmm, I'm not so sure about your findings, I run a S3ViRGE/DX 4M cards in my other box (also a TYAN but the 1662 AT formfactor board) with 256M memory and I've NEVER seen it fail. The exact same S3 board fails horribly in the 1668 (ATX form factor) even with 32M memory, so it doesn't fit you description.... BTW the machine has now been up for 24+hours with the P9100 card, so the video card has something to do with the problem... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 20 02:16:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01324 for freebsd-smp-outgoing; Sat, 20 Jun 1998 02:16:37 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01318 for ; Sat, 20 Jun 1998 02:16:35 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id LAA05190; Sat, 20 Jun 1998 11:16:14 +0200 (CEST) (envelope-from sos) Message-Id: <199806200916.LAA05190@sos.freebsd.dk> Subject: Re: S3 video cards In-Reply-To: <71D507C37988D11182ED0000F80462AC0EE44D@adsdevelop2.autodebit.com> from David Green-Seed at "Jun 19, 98 02:32:58 pm" To: davidg@autodebit.com (David Green-Seed) Date: Sat, 20 Jun 1998 11:16:14 +0200 (CEST) Cc: cr@jcmax.com, smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to David Green-Seed who wrote: > I don't know if this is related, but I've noticed that my S3 Virge DX based > video card tends to have intermittant problems - it appears as if fonts get > corrupted. I haven't been able to determine what causes it. > This occurs under Windows 95, NT and FreeBSD (far less often with FreeBSD) > and appears to be fixable by switching video modes. The symptom exists with > both 64MB and 128MB. (It's a 4MB card) > > Any insights would be appreciated. I think that might be driver problems, XFree86 at least have had problems with the ViRGE/DX cards, and I've seen a lot of bad win95 drivers too. The latest 3.3.2 XfreeBSD SV3 server seems pretty stable here, only a wee bit pixel errors now and then if I move things too fast around. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 20 02:18:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01561 for freebsd-smp-outgoing; Sat, 20 Jun 1998 02:18:25 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01502; Sat, 20 Jun 1998 02:18:18 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id LAA05196; Sat, 20 Jun 1998 11:17:49 +0200 (CEST) (envelope-from sos) Message-Id: <199806200917.LAA05196@sos.freebsd.dk> Subject: Re: TYAN 1668 anyone ?? In-Reply-To: from Tony Johnson at "Jun 19, 98 02:45:28 pm" To: tjohnson@verio.net (Tony Johnson) Date: Sat, 20 Jun 1998 11:17:49 +0200 (CEST) Cc: chuckr@glue.umd.edu, sos@FreeBSD.ORG, smp@FreeBSD.ORG, hackers@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to Tony Johnson who wrote: > I got a few lockups when I had dram refresh queue and I think the other > option is fast dram leadoff turned on in chipset options of my bios.(awd > 5.01) The bios defaults turns them on I think. Turning them off fixed > my lockup problems. They would happen to me when I had heavy disk > access and I moved the mouse and noticed the pc locked up. > > I have a Tyan 1668 Will try that out, I think I have the fast dram leadoff on, that might be it ... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 20 03:53:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09935 for freebsd-smp-outgoing; Sat, 20 Jun 1998 03:53:44 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from styx.aic.net (Styx.AIC.NET [195.250.64.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09929; Sat, 20 Jun 1998 03:53:32 -0700 (PDT) (envelope-from ran@styx.aic.net) Received: (from ran@localhost) by styx.aic.net (8.9.0/8.9.0) id PAA14600; Sat, 20 Jun 1998 15:53:22 +0500 ( AMT ) Message-Id: <199806201053.PAA14600@styx.aic.net> Subject: Re: S3 video cards In-Reply-To: <199806200916.LAA05190@sos.freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Jun 20, 98 11:16:14 am" To: sos@FreeBSD.ORG Date: Sat, 20 Jun 1998 15:53:22 +0500 ( AMT ) Cc: davidg@autodebit.com, cr@jcmax.com, smp@FreeBSD.ORG From: ran@ran.am Reply-To: ran@ran.am X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In reply to David Green-Seed who wrote: > > I don't know if this is related, but I've noticed that my S3 Virge DX based > > video card tends to have intermittant problems - it appears as if fonts get > > corrupted. I haven't been able to determine what causes it. > > This occurs under Windows 95, NT and FreeBSD (far less often with FreeBSD) > > and appears to be fixable by switching video modes. The symptom exists with > > both 64MB and 128MB. (It's a 4MB card) > > > > Any insights would be appreciated. > > I think that might be driver problems, XFree86 at least have had problems > with the ViRGE/DX cards, and I've seen a lot of bad win95 drivers too. > The latest 3.3.2 XfreeBSD SV3 server seems pretty stable here, only > a wee bit pixel errors now and then if I move things too fast around. > Don't try to use S3V driver with xdm. In this case, sometimes when you logout, system completely hang. With SVGA driver my ViRGE/DX work fine about 2 month. > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end? > .. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message -- Ran d'Adi ran@ran.am ran@styx.aic.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 20 09:49:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08474 for freebsd-smp-outgoing; Sat, 20 Jun 1998 09:49:03 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from base486.home.org (imdave@imdave.pr.mcs.net [205.164.3.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08464 for ; Sat, 20 Jun 1998 09:48:54 -0700 (PDT) (envelope-from imdave@mcs.net) Received: (from imdave@localhost) by base486.home.org (8.8.8/8.8.8) id LAA10688; Sat, 20 Jun 1998 11:47:34 -0500 (CDT) Date: Sat, 20 Jun 1998 11:47:34 -0500 (CDT) From: Dave Bodenstab Message-Id: <199806201647.LAA10688@base486.home.org> To: freebsd-smp@FreeBSD.ORG Subject: Equium 6200M successfull install Cc: darrylo@sr.hp.com Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have successfully installed the 5/20 snap on a dual-ppro Toshiba Equium 6200m (pr440fx mb). I had to upgrade the fw on the Micropolis disks, but that's all. Previously, Darryl Okahata had noted: > * Unfortunately, Toshiba's link doesn't seem to mention some important > facts about adding a second processor. See the PR440FX FAQ: > > http://developer.intel.com/design/motherbd/pr/pr_inst.htm > > In particular, see: > > http://developer.intel.com/design/motherbd/pr/pr_inst.htm#1A > > It appears that a BIOS upgrade may be necessary (one newer than that > available from Toshiba). However, unless I haven't exercised the system enough, it seems to be running OK... except I did get a complete lockup at the instant I used 'Alt-F1' to switch vty's -- two ``make -j10''s were running at the time. Of course, I'd switched back and forth many times before. Since I'm now new to SMP, a few questions: 1. I got the BIOS upgrade from the intel support site, but when I tried it, it gave me an error about a failure to initialize the flash memory and the upgrade aborted. Anyone have a clue about this? Was I about to screw up but was miraculously saved? Considering that the SMP kernel boots, is a BIOS upgrade likely necessary? 2. I've just subscribed to freebsd-current, so I've obviously missed anything from 5/20 on that might relate to the current snap. Searching the smp mail archives for ``freeze'' and/or ``lockup'' didn't get anything that seemed applicable. Is there a way to access the complete smp mail archive from 5/20 on? 3. Should problems be reported via send-pr or via this mailing list? 4. X11 seems to work for me, but I thought I had seen a previous message that there might be a problem. Is there anything I need to be aware of? Dave Bodenstab imdave@mcs.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 20 21:43:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01215 for freebsd-smp-outgoing; Sat, 20 Jun 1998 21:43:08 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01209; Sat, 20 Jun 1998 21:43:04 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id VAA23919; Sat, 20 Jun 1998 21:43:16 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: sos@FreeBSD.ORG cc: kedar@asacomputers.com (Kedar Rajadnya), smp@FreeBSD.ORG Subject: Re: TYAN 1668 anyone ?? In-reply-to: Your message of "Fri, 19 Jun 1998 21:06:05 +0200." <199806191906.VAA01877@sos.freebsd.dk> Date: Sat, 20 Jun 1998 21:43:16 -0700 Message-ID: <23915.898404196@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hmm, I doubt it, I use only prime quality RAM here (because of exactly > that reason), and the same RAM works just fine in a 1662 board, which > is just as picky... Actually, and just to note it for the audience, it's easily possible to create memory failures using "prime quality" RAM that has been tested on a different motherboard. Mixing RAM from different manufacturers, using RAM of the wrong speed or at the wrong voltage (in motherboards which allow that degree of configuration), all would be possible while meeting the above criteria and all have been reported to us as the causes of mysterious hangs, crashes, resets, you name it. Once the RAM was simply swapped or the misconfiguration issues dealt with, the system has become a rock of gibraltar in each case. I'm using several 1668 mobos myself, and they work very nicely with Matrox cards (yep, there's another variable for you! ;) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message