From owner-freebsd-questions Sun Jul 13 23:35:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03506 for questions-outgoing; Sun, 13 Jul 1997 23:35:46 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA03501 for ; Sun, 13 Jul 1997 23:35:39 -0700 (PDT) Received: (from smap@localhost) by gatekeeper.barcode.co.il (8.8.5/8.6.12) id JAA23570; Mon, 14 Jul 1997 09:33:16 +0300 (IDT) X-Authentication-Warning: gatekeeper.barcode.co.il: smap set sender to using -f Received: from localhost.barcode.co.il(127.0.0.1) by gatekeeper.barcode.co.il via smap (V1.3) id sma023566; Mon Jul 14 09:32:41 1997 Message-ID: <33C9C80E.2D80@barcode.co.il> Date: Mon, 14 Jul 1997 09:32:47 +0300 From: Nadav Eiron X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.5 sun4m) MIME-Version: 1.0 To: E Lakin CC: Doug White , questions@FreeBSD.ORG Subject: Re: upgrading 2.2.1->2.2.2 problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk E Lakin wrote: > > On Sun, 13 Jul 1997, Doug White wrote: > > On Sun, 13 Jul 1997, E Lakin wrote: > > > While trying to upgrade my machine to 2.2.2, i ran into a problem early- > > > my machine won't boot from any of the 2.2.2 media! I've tried making a > > > boot disk from the boot.flp on the cdrom, and also booting to dos and > > > running install.bat from the cd-rom. > > > > > > symptoms: freebsd probes all of my hardware, and then gets a double > > > fault. > > > > Ack! > > > > We'll need the panic output before we can isolate what's going on. > > Unfortunately, there's no panic output. Here's what it says when > booting from a floppy disk: > > ...various HW probes... > changing root device to fd0c > panic: double fault > > syncing disks... > > Then, the machine freezes. The same thing happens when booting from > the cdrom from dos, sans the "changing root device" line. > > --eric lakin Well, it's a well-known bug... It seems that: Some AMD motherboards will not boot the 2.2.2 floppies, while yet other machines (I happeed to run across DEC Ventirus FXs) won't boot later 2.2-RELENG boot floppies. The cause for all this is still unknown. The best cure available at the moment is to use the older floppy to install the newer version (use the options section to change the name of the distribution). You may have to do a little fixing afterwards, but once you get the correct version installed you can run sysinstall and do most things. Nadav