From owner-freebsd-questions Sun Mar 10 14:19:54 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA23598 for questions-outgoing; Sun, 10 Mar 1996 14:19:54 -0800 (PST) Received: from wormhole (root@wormhole.map.com [204.71.19.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA23577 for ; Sun, 10 Mar 1996 14:19:43 -0800 (PST) From: Received: by localhost (IBM OS/2 SENDMAIL VERSION 1.3.14/2.12um) id AA0023; Sun, 10 Mar 96 05:48:10 -0500 Message-Id: <9603101048.AA0023@localhost> Mime-Version: 1.0 Date: Sun, 10 Mar 96 05:44:00 -0500 To: "FreeBSD Questions" Reply-To: jay@map.com Cc: "Carey Nairn" Subject: Re: problem installing 2.1R on Acer Pentium 75 X-Mailer: Ultimedia Mail/2 Lite, IBM T. J. Watson Research Center Content-Id: <16_75_4_826454640> Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I guess it had to happen some time. After *many* trouble-free > > > installations in the past I am now having trouble installing 2.1R on a > > > pentium 75 Acer machine. The system boots with the boot.flp and goes > > > through the normal messages until it has displayed the device probe > > > messages for PCI bus devices and then just hangs. I have tried both > > > atapi.flp and boot.flp with the same results. > > > > > > The machine configuration is as follows: > > > > > > Pentium 75 cpu > > > 16 MB RAM > > > ne2000 ethernet card (detected OK) > > > sony ATAPI CDROM (detected OK with atapi.flp) > > > quantum fireball 1222 MB IDE HDD > > > > I pulled the NE2000 card out and rebooted and the install menu came up > > fine. I put a different NE2000 card (which I had lying around) in and > > things stopped working again. I guess my question now is if I put in a > > different (non-NE2000) ethernet card in will my problems go away? > > drove to work and got an old 8-bit SMC card and plugged it in. > Everything is now OK. Chances are the problematic NE2000 card is set to an IRQ or IO port address that conflicts with something else in the machine. Find out what where the other hardware is at, then configure the card correctly. Had a similar problem with an Adaptec SCSI card - somehow the IRQ was set to the same one as the primary HD controller. Not good, since the machine wouldn't even boot enough to set the card to a different IRQ. // Roland Jay Roberts - Team OS/2 - // Internet: jay@map.com // FidoNet: Roland Roberts @ 1:321/305.5