So I got me this Asus board with an integrated Celeron
http://www.asus.com/Motherboards/J1800IC/specifications/
and put 2G of Crucial RAM in it.

"A PC is a PC is a PC" I can hear you say,
but somehow I can't get current/i386 to run on it.

Using another current/i386 machine as an installer,
I installed current/i386 on a Samsung 250GB SATA disk
(installing onto the external sd1). Then I put this
SATA disk into the Asus board to boot from it.

Firstly, it didn't even _try_ to boot from it.
The POST screen mentioned the disk is there
(with the correct Samsung code and all),
but went straight to BIOS; in the BOOT menu,
the disk was not an option (just PXE).

That was my first encounter with the UEFI "Secure Boot" horror
- and there was no way to "disable" it, the "enabled" setting
was gray'ed out. I set the "OS type" to "Other" (as opposed to
"Windows 8", the only other option), no change. Then I deleted
the database of "keys" - that made the Secure Boot "disabled",
but it still didn't try to boot from the disk, and didn't even
present it as an option in the boot menu.

Only after upgarding to the latest BIOS
http://www.asus.com/Motherboards/J1800IC/HelpDesk_Download/
I am presented with "CMS settings" where I can somehow make
other systems (other boot loaders) allowed.
So now it finally gets to the OpenBSD boot loader.

But /bsd panics during boot, /bsd.sp and /bsd.rd panic too.
I don't know if the previous is relevant to it.

The board has a serial console, but I can't get it to work
(the manual does not specify the baud rate, I tried all
baud rates from 9600 to 115200 that I have met, but 
I never get anything after "connected"); so here are
the pictures (sorry):

/bsd
http://stare.cz/dmesg/asus-J1800IC-bsd-panic.jpg
http://stare.cz/dmesg/asus-J1800IC-bsd-trace.jpg
http://stare.cz/dmesg/asus-J1800IC-bsd-ddbcpu.jpg
(the last command just sits there)

/bsd.sp
http://stare.cz/dmesg/asus-J1800IC-bsdsp-panic.jpg
http://stare.cz/dmesg/asus-J1800IC-bsdsp-trace.jpg

/bsd.rd
http://stare.cz/dmesg/asus-J1800IC-bsdrd-panic.jpg


I don't think these newer machines are even supposed to work without ACPI
- indeed, disabling ACPI makes /bsd panic in identifycpu().
What can I do to further debug it?

                Jan

Reply via email to