This page contains information about the FreeBSD/i386 platform. FreeBSD/i386 should support any CPU compatible with the Intel(T) 80486 or better in 32-bit mode, although almost every recent AMD(T) and Intel(T) CPU will also be capable of running in 64-bit mode using the FreeBSD/amd64 port.
FreeBSD/i386 Project
FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.www.freebsd.org
Oh, I definitely try an other USB Stick!
Thanks for the tip!
OP says he tried (post 22). At least with usb-stick.Have you tried with an i386 12.4-RELEASE CD or USB?
If that works, you'll have a supported version until the end of this year (if the EOL date doesn't move again), giving you time to update.
Oops! Duplicate above.This page contains information about the FreeBSD/i386 platform. FreeBSD/i386 should support any CPU compatible with the Intel(T) 80486 or better in 32-bit mode...
dd
image such as this one: FreeBSD-13.1-RELEASE-i386-memstick.img to usb key and you are set.One of the possibilities is that grub2 is switching to protected mode and bypassing BIOS for this. You could test this with something that uses grub (e.g. RedHat 7.x or some older debians).I cannot understand why debian Linux is booting fine.
BTX halted on int 6, UD - invalid opcode. That would be consistent with the memory full of 0xff where loader jumped.
Bad RAM doesn't have one particular pattern. This could be anything, really. From stale info in RAM to bad read and anything in between.'full of 0xff' could very well smell like bad RAM, and it could be bad just in one section.
Bad RAM doesn't have one particular pattern. This could be anything, really. From stale info in RAM to bad read and anything in between.
While it never hurts to check RAM I think this is sw issue, not hw one.
He's able to boot Linux successfully on that machine too.
It's a nice one. I like these. It makes it even more interesting issue if legacy grub boots there just fine.Maybe, but it's s strange one