UEFI Initializing devices.
-
Hello again! I am ipxeing my UEFI computer to download my image which I was finally able to get upload with the help from the lovely people in these forums. I was able to download it to another computer perfectly. Now I am having trouble with an HP 4300 it will just get stuck on Initializing devices or if i change my boot file to one i found in my fog folders such as intel.efi it will go further then BAM right to no bootable drive (I just replaced the hard drive with a Solid State.) I was also able to get to an ipxe command prompt with intel7156.efi. I tried all the efi i could find in that folder and either it froze at initializing devices or to no bootable after it downloaded the TFTP file. I did check wireshark and it is always getting the tftp file. Any thoughts where I should go from here? Thanks in advance.
-
@hammett131 Do the compatibility checks on the fog boot menu, see what they say.
-
@Wayne-Workman I never get to fogs boot menu.
-
@wayne-workman I did get it to boot to fog with undionly.kpxe and ran the compatibility check it passed for disk and network but I am looking to get it to UEFI.
-
@wayne-workman Alright I found a work around. I pxe boot with undionly.kpxe then pushed out my UEFI image to the machine. After the reboot I turned back on UEFI and disabled legacy and BOOM UEFI windows.
-
@hammett131 That is one way. While it does work, it does not scale. Going to ask if @george1421 or @Sebastian-Roth can take a look at this thread.
-
@hammett131 said in UEFI Initializing devices.:
HP 4300
Is it just with the above model?
Just for confirmation we are talking about this model? https://support.hp.com/us-en/document/c03403843Have you ensured you have the latest firmware installed on this device?
How many of these devices do you have on your campus?
What version of FOG are you running?
Where its getting hung up is booting the iPXE kernel, its hanging up on initializing the hardware. We have seen this with some crappy uefi firmware implementations. Usually a firmware update fixes the issue.
-
@george1421 It is that model. And I am using 1.4.4 Fog (noticed there is 1.5) I honestly spaced checking the firmware I did see a 2013 date for it though which might be the issue. I work for a small company it is just a clients computer so I may see one again I may not kind of thing. If I get another one I will have to check the firmware I think you probably on to something. Thanks for the help again @george1421
