🚀 go-pugleaf

In article <1992Oct30.010919.470@prim> dave@prim.demon.co.uk (Dave Griffiths) writes:
>
>I've just installed release 3.0 and it panics with the following messages:
>
>Oct 29 16:08:48 localhost mach: unexpected kernel page fault failure
>Oct 29 16:08:48 localhost mach: panic: (Cpu 0) MMU invalid descriptor during table walk
>
>The 3.0 installation seemed to work fine. The panic occurs a few seconds
>after the "reboot complete" message. The disk I'm using is a brand new
>Fujitsu 2624. Prior to the installation, I did a /usr/etc/builddisk on
>this new disk. I'm running 2.0 on a 24MB 25MHz Cube. My default boot disk
>is still my old 2.0 disk, so to boot from the 3.0 disk I interrupt the
>boot and type "bsd -a" and then "sd1" when prompted for the boot disk. The
>/etc/fstab has been set up OK. There's 150 MB free on the new disk.
>

OK, I found the problem. It worked fine when I did a "bsd(1,0,0)sdmach
rootdev=sd1", so the problem was related to booting via "bsd -a". Presumably
it's related to using the wrong boot program. Strange that it got so far though.

First impressions of 3.0: cooool. Seems quite fast too. Don't know if this is
the new disk or lack of fragmentation though.

Dave Griffiths