From owner-freebsd-hardware Wed May 21 17:38:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA18110 for hardware-outgoing; Wed, 21 May 1997 17:38:27 -0700 (PDT) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA18104; Wed, 21 May 1997 17:38:26 -0700 (PDT) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id RAA14120; Wed, 21 May 1997 17:38:22 -0700 Date: Wed, 21 May 1997 17:38:22 -0700 From: "Jin Guojun[ITG]" Message-Id: <199705220038.RAA14120@george.lbl.gov> To: brian@mpress.com, bugs@freebsd.org Subject: Re: ASUS P/I-P65UP5 + C-P55T2D dual Pentium MB Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Has any one successfully installed FreeBSD on an ASUS P/I-P65UP5 dual Pentium >> motherboard with C-P55T2D (two 200 MHz Pentium CPU) daughter board? >> >> I had a memory problem on this motherboard. The same memory was used for >> ASUS P/I-P55TVP4 and TX97-E single Pentium 200 MHz CPU motherboards without >> any problem. They are 60 ns non-parity SIMM. >> However, the same hareware with just a different motherboard, the page fault >> occurred when system swithed to VM mode during the installation; that is, >> when installation passed all probing and switched to graphic installation >> menu. >> Does this imply I have a defective motherboard? or are some special >> setup required for VM start up? >> More info., this motherboard does not work for other UN*X system either. > >I'm running a P65UP5 and I think the same CPU card, ok with >FreeBSD in SMP mode. It was not the motherboard's problem. It is the 2.2.2-RELEASE boot.flp bug. The problem is very strange: NCR-810 SCSI controller + 3-Quantum Fireball 3.2 GB disks causes page fault NCR-810 SCSI controller + 2-Quantum Fireball 3.2 GB disks works OK. After installation, put 3-Quantum Fireball 3.2 GB disks back on the SCSI bus, no more page fault. Also, the 2.2.2-RELEASE installation failed to set the hostname and all network info. (such as ifconfig_ed1, defaultrouter etc.) into the /etc/rc.conf. Another problem in the 2.2.2-RELEASE is that the YP (NIS) client is broken. I remember someone reported YP server is broken. So, it looks like entire YP is broken. Since I cannot make a 2.2.2 machine up, therefore, I use the regular email instead of send-pr to report all problems at this time. Thanks, -Jin