Page fault when booting an old Pentium machine
Today I installed DragonflyBSD on a old Pentium I 75Mhz with 32MB EDO RAM
to see what happens. I first installed harddisk on another machine, when
DF installation procedure ended I installed the harddisk on that old
And what happened is that it doesn't boot at all :-(
It throws a Fatal Trap 12: page fault while in kernel mode and the boot
I have uploaded some pictures to leaf so you can see more detailed
If you need some more information, let me know.
#1 Updated by wa1ter almost 10 years ago
On Fri, 7 Dec 2007, Antonio Huete wrote:
That *is* an old one. What cpu options did you build the kernel with:
BTW, I thought i386 support had been ripped out already, am I wrong
#4 Updated by wa1ter almost 10 years ago
Right. It was supposed to be named the 586 but trademark lawyers nixed
Well, no one else is asking questions yet, so I'll ask some random ones.
Have you tried booting with ACPI disabled? (See the DragonFly boot
menu.) Do you have LBA enabled in your BIOS? Does the machine have
a CDROM or even a floppy disk drive? You might try booting the install
disks from FreeBSD or NetBSD or Knoppix just to see what happens.
Oh, and did you try booting that hard disk in the original machine you
used to install DFly?
#5 Updated by tuxillo almost 10 years ago
El Fri, 07 Dec 2007 14:47:40 -0800, walt escribió:
When booting DragonFly I have tried all the options in the menu, but no
one of them succeed, I keep getting same error. This BIOS is too old, it
doesn't have LBA. Machine doesn't have neither CDRom nor floppy drive and
the BIOS doesn't leave me the choice of booting from CD.
Dragonfly booted fine on the Pentium II I installed.
If you need some more information, please let me know :)
#8 Updated by tuxillo almost 10 years ago
El Sat, 08 Dec 2007 20:46:58 +0000, Thomas E. Spanjaard escribió:
Hello again :)
That patch worked perfect for this case. Anyways, I keep receiving some
"errors" in dmesg. I have included a dmesg output and a pciconf output.
I have moved all info related this bug into another folder. You can now
access everything on:
Thank you very much for your support.