From owner-freebsd-questions Sat Aug 23 18:12:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA26227 for questions-outgoing; Sat, 23 Aug 1997 18:12:39 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts9-line7.uoregon.edu [128.223.150.88]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA26222 for ; Sat, 23 Aug 1997 18:12:35 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id SAA00488; Sat, 23 Aug 1997 18:12:29 -0700 (PDT) Date: Sat, 23 Aug 1997 18:12:29 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Bill Clark cc: freebsd-questions@FreeBSD.ORG Subject: Re: [Fwd: New Problems] In-Reply-To: <33FC3466.425B9469@xoom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Argh! Could you find a way to not add so many attachments? It messes up Pine so I don't get the message text quoted properly. On Thu, 21 Aug 1997, Bill Clark wrote: >First off, let me correct a mixup I made in describing my system: > The primary SCSI controller is the AHA2940, and the secondary > (controlling the RAID) is the NCR53C875. Okay. You may need a newer version of FreeBSD to pick up the 875. I think we mentioned that already tho :) > I gave up on trying to get the RAID to work (for now), but am faced > with an even more annoying problem: > FreeBSD has random problems upon installation. That's not right. > Sometimes, after an install the mouse will not work. Sometimes, X > will not work. Every single time, the network configuration is lost > upon reboot, and /stand/sysinstall (when it even manages to load) has > major curses problems, especially on the network configuration screen > (for ftp'ing packages) -- and always locks up if I try to enter the > information in again. What release are you working with? Could you post some of the error messages you're getting? Note that you *should*not* attempt to reinstall over a failed install -- it will only screw things up further. Blow it up with DOS FDISK and start over. I bet you're working with 2.2.2-- there are some serious bugs in 2.2.2 that can cause corruption in /etc/rc.conf. In this case, stay away from sysinstall once the system is actually copied over, ie don't do any post-install configuration. In this case, quit when it's finished copying, boot up the system, edit /etc/rc.conf and customize as you need. It's well commented so you should be able to get everything going. If you don't feel comfortable doing that or you can't even get _that_ far, contact releng22.freebsd.org and try installing that version (2.2-STABLE). It should fix the bugs you're seeing. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo