hello i use a intel pen STCK1A32WFC (baytrail soc 2gb ram). i have flash the anyboot iso on usbstick
the boot start i see the icon and the haiku logo. but it stack on debug (and keyboard not work at all).
i have a image about the error. (i cant i post it on nest post)
Strange when i see the usbstick on mint partition manager efi partition is after the Haiku partition and a strange 6mb unallocated is on the start of the partition table… (debug error say : i can’t find a boot partition)
The space at the start is for the ISO9660 filesystem for legacy boot from CD.
The EFI partition is at the end because it was added later, and it was easier to put it at the end than to move everything else.
@nephele I’m not sure why you closed this. While it’s nice to ask people to report bugs, we can also reply to non-bug questions in the forum, to keep the discussions in the bugtracker to a minimum and make it easier to follow bugs there?
i try with SHIFT for enter on “rescue menu” but without success. i use a usb hub (because the intel stick have only 1port) how to “force” haiku to load the menu every boot?
i find the way for boot menu with SPACE BAR. Haiku is recognized as boot partition…
i upload another pics (sorry for shitty image… but i can’t save log on file)
@scott_puopolo18 no problem, i can understand the reason for that. i use forum in the past (and i think is the best for support and other stuff). i haven’t understand why on help we can’t post boot error… but obviusly the dev know is a bug and here isn’t possible solve it. probably need the to be updated the entire kernel? i have downloaded the latest nigthly the error change a bit but stop on 4 step (mount).
I closed it, not Pulkomandy. And I explained my reasoning above.
In the past these kinds off topics have never helped users, only people answering with unrelated suggestions rather than acknowledging a bug exists. I‘m not sire where the fear of the bugtracker comes from, but asking users to perform unrelated debugging activities isn‘t really welcome either.
Besides the bug, there were actual questions here, which I have answered now.
Also, if you have problems with how people reply to topics, I don’t think closing topics where there are no replies yet to actual questions is the right way to go. Maybe we can simply remember people that posting random speculations or suggesting random loosely related commands is goingto make things more confusing and usually not solve problems, and they should think about it before replying. They will not learn that by just locking topics…
