Anything get stuck on bzimage with random %
-
Hello everyone !
I’m writing this post to seek for help about an issue I can’t solve.
I use a lot the fog service to deploy images but with computer getting more modern, at some point it just wouldn’t work anymore.I search on the internet and this forum to check what was the issue and it was about network drivers. This was fixed.
But since, everytime I want to capture, deploy or register a device, it just get stuck in “bzimage…” with a random pourcentage.
I saw some related posts but none of them is working for me. I tried to add option 66 and 67 in the dhcpd.conf file but it only make things worse and it won’t boot at all on PXE (PXE-E23 client recieved tftp error)
I did a complete reinstall of the system and the issue is still there. I’m using the latest dev-branch version: 1.5.9.158 with Kernel 5.15.34 AMD/Intel 64 bits.
The test computer I’m using is a Lenovo ThinkBook 15G2 ITL (brand new).
I don’t know where to search for a solution.
Thanks in advance. -
@adriand If you can undo the changes you made to get back to the random copy percentages then lets have you update iPXE. iPXE is responsible for copying bzImage and init.xz to the target computer and starting them up.
https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe
-
Thanks you @george1421 . Unfortunatly, it didn’t work. I recompiled the ipxe files with buildipxe.sh and reruned the installfog.sh to update the file. I checked the date and it seems good.
I noticed a detail when I was trying to make it work. Sometime it can register sometime not. The last test I did, bzimage went “ok” but get stuck in “init.xz…” after a reboot it get stuck in bzImage again with a random %.
I feel like during a short period of time everything work, but suddenly, everything stop working
I have 2 network interfaces and I did shutdown the one for management and it didn’t solve the issue.
I’ll try with a different computer today.
Adrian.
-
Update :
I’ve tried on 2 different computer both in UEFI. One is a 4-5 year old MSI. Work fine.
I tried an older Lenovo too, no issues.May it be an hardware compatibility issue ? I’ll search in the bios to see if something could interfere.
Adrian.
-
Nothing changed. I disabled security paramters in the bios. Still get stuck. Sometime it pass, some it don’t. It’s weird.
-
@adriand Ok so the problem is only with the new Lenovo ThinkBook 15G2??
What iPXE boot loader are you using ipxe.efi or snp.efi? If you are using ipxe.efi, lets switch to snp.efi (or snponly.efi). The snp interface uses the nic drivers built into the network card/uefi firmware instead of the driver built into ipxe.efi. The snp driver is akin to what the undi driver is to bios. For fox pxe booting in bios mode we would send undionly.kpxe to the target computer.
The ipxe.efi and ipxe.kpxe boot loaders are a lot like linux in that they have all of the known drivers built into the kernel. If you have really new hardware these built in drivers might not be new enough to support let latest hardware.
-
@george1421 Thank you for your answer,
Do you have any documentation on how to properly switch iPXE boot loaders ? I have all the files you mantionned in /tftpboot and I don’t see any options in iPXE General Configuration on the web interface.
Adrian.
-
@adriand The switch would happen on your dhcp server for the subnet in question.
If fog is your dhcp server for your isolated imaging network then there is a configuration file that needs to be adjusted
If your main dhcp server is a windows server or something else the change needs to happen on that server, probably dhcp option 67 or if you are using profiles in that response profile.
-
@george1421 Thanks you for your answer.
I checked the DHCP configuration and changed the file name. I was already using the snponly.efi files and switched to ipxe.efi and it’s now working.
Thank you for your time and help !
Have a nice day.
Adrian. -
@adriand said in Anything get stuck on bzimage with random %:
I was already using the snponly.efi files and switched to ipxe.efi and it’s now working.
FWIW, with modern UEFI computers snp or snponly should work because these boot loaders use the snp network driver built into the uefi firmware. On older model uefi computer the snp driver was a bit flaky so the preference would be to use ipxe.efi on those models because ipxe.efi has all of the common network drivers. Sometimes is a balancing act to find the best middle ground for the boot loaders. I’m glad you have it worked out.
