Hi,
I’ve tried to install the latest anyboot nightly build.
all these attempt were in BIOS mode.
on the ASRock, I’ve first tried the USB CD:
it reached the graphic screen with 5 icons.
It then was partially covered by something similar to this:
PANIC: did not find any boot partitions !
Welcome to kernel Debugger Land …
Thread 16 “main2” running on CPU 0
Stack trace for thread 16 "main2"
kernel stack: 0x02e36000 to 0x82e3d000
Frame coller function + offset
0 082e39af8 (t32) 0012599a <kernel_x86> arch_debug_stack_trace() + 0x0012
9 082e39fb4 (t48) 8007a0cc <kernel_x86> common_thread_entry_Fpr()+0x000
kdebug>
I found this to be a 3 years old bug
https://dev.haiku-os.org/ticket/9176
the USB Stick stopped on a grub-like menu text mode screen
saying it could not find a boot partition.
I then tried the USB Stick on my samsung laptop: it stopped on the same menu.
I will try the USB CD on the samsung tonight.
Unfortunately, these are the only computers I have around.
I have an empty HD to which I could copy an image to.
(I didn’t find yet the explanations on how to proceed though).
Is there anything I can do to make this work ?
thanks
Hi chafporte,
first of all i would suggest using nightly image. It has many advantages e.g. the posibility to update your system and also the HaikuDepot wich is essential for all the apps, wich are out there. And since the websites BeOS and Haiku Alpha4 software where taken offline this is the best choice if you want to do more then just simply look at the os :-D.
http://download.haiku-os.org/nightly-images/x86_gcc2_hybrid/
So build a usb stick out of this. 
If you boot and it fails (with nightly or alpha 4)
try pressing Shift during the boot process, there you can choos differnt
Options to make Haiku boot also if there are problems
I would suggest enableing Safe Mode. for the beginning.
For more details see here:
https://www.haiku-os.org/docs/userguide/en/bootloader.html
If you have any further problems just ask 
You can use the anyboot image on an HDD as well, just copy it to the drive with DD like you would do for an USB stick (assuming the way you did it for the USB stick is correct). For example on Linux:
dd if=haiku.anyboot of=/dev/sdX bs=1M
(replace haiku.anyboot with the image file name, and /dev/sdX with the path to your hdd or usb device). The “bs=1M” parameter is not required, but speeds up the process a lot.
[quote=PulkoMandy]You can use the anyboot image on an HDD as well, just copy it to the drive with DD like you would do for an USB stick (assuming the way you did it for the USB stick is correct). For example on Linux:
dd if=haiku.anyboot of=/dev/sdX bs=1M
(replace haiku.anyboot with the image file name, and /dev/sdX with the path to your hdd or usb device). The “bs=1M” parameter is not required, but speeds up the process a lot.[/quote]
IIRC last time I did this I also needed to use makebootabletiny to make the partition bootable, is that correct?
I remember now there was the same problem with this board on freebsd. and they solved it.
I don’t know how to get the right person to look into this,
but here is the actual issue:
Intel Baytrail-M NUC(DN2820FYKH) does not able to boot FreeBSD-CURRENT/amd64, because of its buggy ACPI table.
It has two incorrect parameters on MADT:
Type=Local APIC NMI
ACPI CPU=1
LINT Pin=60
Flags={Polarity=active-hi, Trigger=0x2} <-- trigger value is incorrect. 2 is reserved
Type=Local APIC NMI
ACPI CPU=2
LINT Pin=61
Flags={Polarity=0x2, Trigger=level} <-- polarity value is incorrect. 2 is reserved
Because of this, interrupt_trigger() panics with “Bogus Interrupt Trigger Mode”.
Also interrupt_polarity() panics with “Bogus Interrupt Polarity”.
I think this is BIOS bug, but we can do some workaround for the machine.
Fix: Linux uses level trigger and low polarity if the value is 0x2(reserved).
http://lxr.linux.no/linux+v3.13.5/arch/x86/kernel/acpi/boot.c#L1094
We can do similar workaround, but with warning message.
Patch attached with submission follows:
How-To-Repeat: Boot -CURRENT on NUC.