Unable to boot with UEFI (BM & VM)

Good day,

I just upgraded my box from ryzen 1600 (will be a server soon) to a ryzen 5700G on Gigabyte B450 mobo.

I wasn’t able to boot Haiku’s install USB with UEFI, nor the beta nor the nightly. Tried with all safe mode opts and still not a chance.

Finally installed in CSM mode, though I installed the UEFI way, but still no way. booting in UEFI just stalls Haiku before any boot icon turns on, and only way to get out of there is by reboot.

Will add a bug report lately.

Any hint will be appreciated.

Regards ,
RR

When you hold the shift key during the early boot process, you should enter the boot loader menu. From there you can try to enable several safe mode options that may help you booting Haiku. In any case, there is no general reason why it shouldn’t work on a 5700G (I happen to own one myself).

The Shift key won’t work in the UEFI boot. Instead one has to press quickly the Spacebar several times.

Just to double-check, you tried the “Disable local APIC” option, right? Asking because, Haiku is unable to boot VMware in UEFI mode, with symptoms similar to yours (no boot icon turns on), but the “Disable local APIC” option allows it to start.

1 Like

Good day @VoloDroid,

Well, I had tried all options, so no, no boot in UEFI mode. I tried you “trick” also in VMWare Workstation 17 and no chance to boot in UEFI neither, even with the “Disable Local APIC” option.
No luck here.

Thanks though.

Regards,
RR

I boot my primary Haiku partition using UEFI on both bare metal and within VMware, but…

I’m avoiding updating my copy of VMware workstation because I couldn’t get UEFI to work with anything above 17.0.2 (it’s actually 17.0.2 build-21581411)

I also have to use a custom build of Haiku because I run into this problem with FPU states in VMware.

That’s interesting. You boot 64-bit version of Haiku, right? Can you share the EFI64.ROM and EFI20-64.ROM files from your C:\Program Files (x86)\VMware\VMware Workstation\x64\ folder? Those are UEFI firmware used by VMware (depending on your VM hardware version one or another is used). It’d be interesting to check if I can boot my Haiku VM in the UEFI mode with the firmware file that works for you.

Yes, I have multiple Haiku VMs, but the UEFI partition is 64 bit. The rom files are in a different location on Linux :stuck_out_tongue_winking_eye: I’ll send you a private message with those two files.

Thanks! I have no idea, why I thought you were using Windows =)
Surprisingly, one of the files EFI20-64.ROM worked and allowed Haiku to boot in UEFI mode on my VMware Fusion. There’s quite a noticeable delay before the icons start to light up, but other than that it works. You can give it a try on the latest VMware Workstation by putting the firmware next to your Haiku VM .vmx file and adding the following line to the latter:

efi64.filename="EFI20-64.ROM"

@roiredxsoto you can also try it out if you’re interested in running Haiku in UEFI under VMware (though there’s no big reason of doing it on a virtual machine).

Good day @VoloDroid ,

the reason for UEFI booting is display resolution. Can’t get display resolution nor in VM nor BM. With UEFI booting would use the framebuffer driver which will hopefully get me full native resolution.

Regards,
RR

You can use VirtualBox instead of VMware and add a custom video mode to it. It’s described in the VirtualBox documentation: 2.7. Advanced Display Configuration

For example:

VBoxManage setextradata "<haiku-vm-name>" CustomVideoMode1 "3840x2160x32"
VBoxManage setextradata "<haiku-vm-name>" CustomVideoMode2 "2880x1800x32"

With that one you won’t need UEFI booting, even though VirtualBox boots Haiku in UEFI mode without an issue.

Not without an issue… :rofl: Running latest beta fullscreen at native resolution not in UEFI renders Haiku unusable. Total system lock. :cold_face:
If I run it windowed, no issue…

Might be my all AMD HW… :rofl:

Regards,
RR

I’ve just checked and I don’t have that issue on macOS host either with or without UEFI. If you use VirtualBox 7.x try to use 6.1.50 instead (and don’t forget to install VirtualBox Extension Pack, VB is semi-usable without it).

In VMware with the tools package installed on Haiku, the screenmode command in Haiku should allow setting custom video resolutions.

Good day @axeld ,

Apologies… I hadn´t noticed your post until now. Yes, I find it quite strange that it doesn´t boot in UEFI on BM. The laptop I got 2nd hand (Lenovo P14) with a 4750 didn´t have any issue to boot UEFI (lots of other issues though).

Anyway, I tried with all safe mode options without any luck, I mean on BM.

Virtualized, I finally got it working with Virtualbox, at full 2560x1440, adding the vbox extension pack as @VoloDroid pointed out. Though still no luck in full screen, as Haiku becomes unresponsive. Full screen works on VMWare, but only at 1920x1440… which is a pain in the butt.

@waddlesplash, tried in VMWare Workstation 17 with the tools package installed, and the screenmode doesn´t do anything. Basically it says that the 2560x1440x32 is not listed and not supported. So out of luck here too (does not matter BIOS or UEFI).
I wonder if the Virtual Machine issues have anything to do with having a dual screen setup, running on Arch, and one display is in vertical mode.

Will keep testing. Eventually I´ll get it working.

Thanks all for your assistance!
Regards,
RR

Could you try to apply this patch Added support for 1366x768 ("HD") and 2560x1440 ("2K") resolutions by sarahemm · Pull Request #40 · HaikuArchives/VMwareAddons · GitHub and see if that works?

What version of VirtualBox do you use? Is it 7.x or 6.x? Those are two parallel version lines, so you can try to switch between them and see if it helps.

Good day @axeld ,

BM:
Looks like out of luck with the bare metal install and run. I tried all safe mode options and even touched the BIOS to see if some ‘combination’ would allow me to boot UEFI on the 5700G and after testing and testing I think the issue is with the chipset. This box has a Gigabyte Aorus B450M miniITX motherboard, updated to the latest BIOS, and no luck. I tried with an old MSI B350M Bazooka I have repurposed, also updated to the latest BIOS version and the MSI one boots UEFI without issues.

So my guess is that this issue is related to the chipset.

I can´t even get the boot debugger to show any info on the screen when I select the safe mode options and debug options before booting. It doesn´t abide any ‘order’, and instead of showing the debug messages, the haiku logo with the icons appear on the screen. So no chance to see anything.

I’ll file a bug with the syslogs later if there is any difference between the syslogs. Because I just think that Haiku just stucks there before even trying to boot, and maybe no syslog is even triggered.

Will update in case any changes are noticed.

VM:
@Diver , checked that patch but seems that with the screenmode command should suffice.

@VoloDroid, I’m using VirtualBox 7.1.4, and with that I can set full display resolution adding the virtualbox extras package. Problem is that when I set the vm to full screen, Haiku stalls and have to return to windowed mode.

Thanks you all for your assistance.

Regards,
RR

Good day,

So these days I’ve been trying to boot the MSI from the USB drive using different releases to try to install Haiku in UEFI mode. No success at all:

Beta5: stucks itself in the booting icons. None turns on. Stays there forever. It doesn’t matter what safe mode options I trigger, nothing different happens.

Now with the nightlies, something different happens:

  • From hrev58291 to hrev58340: same behavior as with the beta5
  • With hrev58344 and hrev58352: same base behavior as with the beta5, but when selecting safe mode options, there is a change: selecting al safe mode options ends up in KDL:

I’m beginning to think that this may have something to do with me updating the BIOS to support the R5700G.

Will add the Bug Report in a moment.

Regards,
RR