Can't chainload past Fog menu (Boot hard drive) - HP zbook laptop
-
@george1421 @Sebastian-Roth Ok, now that just not fair!!!
If I ONLY have DriveRoot/EFI/BOOT/BOOTX64.efi on the USB drive and boot it with the default options, it works fine. Default options means that I am not doing any ACPI DSDT flag setting, no CPU flag setting, etc. I copied that same .efi file onto fog! So all that stuff that config.plist was supposedly fixing is now out the window since the USB just works regardless of the configuration set.
So that totally chops up both of the things I was going to investigate next. Thoughts?
-
@Szeraax Any news on this?
-
@sebastian-roth No.
My current situation is that no matter what I do when booting off USB, it boots windows fine and no kernel panic (freeze .5s after logon screen appears). And no matter what I do when booting from pxe (Fog -> Clover), windows 10 still freezes .5s after logon screen appears.
I have no idea what the cause is.
-
If you have any ideas for me to try, I do still have the hardware and can test.
-
@szeraax said in Can’t chainload past Fog menu (Boot hard drive) - HP zbook laptop:
My current situation is that no matter what I do when booting off USB, it boots windows fine and no kernel panic (freeze .5s after logon screen appears). And no matter what I do when booting from pxe (Fog -> Clover), windows 10 still freezes .5s after logon screen appears.
Just so I get this right?! If you boot straight from hard disk everything is perfectly fine. But if you boot from USB or PXE windows freezes soon after logon?
-
@sebastian-roth Nope!
If I put Clover on USB, I can chain to windows just fine.
Loading Clover via Fog causes windows to freeze on login screen.
-
Additionally, I’ve tried MANY different configurations (no options file, manually set options, use options file (can’t get Fog to load the options file)) and EVERY TIME, it has been consistant that boot from USB -> CLover -> WIndows and no panic. Boot from fog -> Clover -> Windows PANIC!.
-
@Szeraax Ah, now I get what you mean. What you wrote sounded a bit different to me.
https://www.reddit.com/r/hackintosh/comments/3t71yp/clover_freezes_if_usb_30_ports_used/ - is the USB still connected when you try PXE booting?
-
@Szeraax Maybe it’s worth/easier to get on contact with the clover people: https://sourceforge.net/p/cloverefiboot/discussion/ and http://www.insanelymac.com/forum/forum/327-clover/ (both seem active)
-
@sebastian-roth Don’t believe so, but I’ll try again to double check. I’ll check in with them. Great idea. Dunno if any of them will know the differences between booting off USB and booting off PXE. Here’s to hoping!
-
@sebastian-roth Well, I suppose that we can mark this solved at this point.
Not because it is solved, but because I will just have to wait for a magical time in the future when FOG has support for booting NVMe hard drives decently.
As a follow up from your last comment, with my test hardware (we had to get a new demo computer), clover boots to windows fine without any configuration at all. No panic/freezing. Weird I know. This is the exact same zbook model, just with different ram/hdd configuration. Also, I still cannot get the clover settings file to get loaded, so I am unable to customize the clover menu. Since by default clover lists your boot options and doesn’t have a autoboot timeout, using clover at default settings means that I would have to hit enter on each physical machine each time I boot it.
My solution for now is to make the bios boot to HDD instead of network and then configure the option “WOL boot to network” in order to be deploying.
Thanks again for all your help, and @george1421 too! Y’all are great.
-
@szeraax Thanks for the update. It’s definitely an issue that we will be seeing more and more in the next month.
Not because it is solved, but because I will just have to wait for a magical time in the future when FOG has support for booting NVMe hard drives decently.
Unfortunately those things rarely solve themselves magically. People have to work on it. In this case having the hardware at hand seems to be very crucial as your findings reveal (same zbook model showing different behavior). By the way, have you checked firmware versions?
So what I am trying to say is that it might need your work on testing these things on your devices to hopefully figure things out. But on the other hand I do understand that you/we don’t have the time and expertise to dig through this.Maybe try going back to using rEFInd plus adding the clover NVMe driver? As I understand it you should be able to add that driver by simply creating a directory
drivers_x64(EFI/boot/drivers_x64) and putting that clover driver EFI file there. rEFInd should scan that directory and load the driver.Not sure if we’d mark this solved.