-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot boot with 6.6 kernels #97
Comments
This is useful thank you. We're trying to wait out getting to the 6.11 kernels built for both the inits and the kernels of course. Thanks for the feedback and information. |
That's interesting, I have the exact same setup and don't get this issue. I do get that EFI Stub message but it still boots. |
@maxcarpone I know it has been a while but we have a new experimental kernel version 6.6.69 out now that should fix this issue. Would you be able to test this release and let us know if this works for you please? |
Hello, I received a notification by email but I forgot to come back here. I update my server right away and I'll let you know. |
Failed! Tried this time with Proxmox 8.3.3 (VM type : Windows 10 UEFI) and Fog 1.5.10.1634 (last kernel 6.6.69) but I have exactly the same problem as before. As soon as I revert kernels back, it goes further. Thanks for your work guys. Cheers! |
@maxcarpone It's interesting that the 6.6.69 kernel didn't work for you. I also use proxmox, and it works for me on 8.2.4 and 8.3.3. Can you please share the VM hardware settings? Just in case there is something weird that I could find. |
@maxcarpone Well the only thing that I see is different is the |
Hello! This is really weird, I tried to image with settings Q35-8.1 and it worked. I switched back to Q35-9.0 and it also worked.... So, it looks like the kernel isn't faulty but it's something else. BTW, when it worked twice, I didn't see the problematic line : I'll upgrade the FOG server and try again several kernels 6.6.xx series |
Well, I upgraded my FOG server and again, imaging is stuck with the following message (which is different this time) : Maybe it has something to do with the upgrade task?! |
Forget it! It works like a charm, when I upgraded this time, kernels loaded were still 6.6.49 so obviously it didn't work but as soon as I replaced it with those experimentals, it went further. I'm pretty sure it wasn't working before with your experimental kernels but I'm starting to doubt. Anyway, thanks for the fix 👍 |
Hey there,
Today, I updated our trunk version 1.5.10.17 to the very last one 1.5.10.1615. It switched our existing kernels to 6.6.49 but I am unable to deploy anything with these kernels, computer (Proxmox 8.2.4 VM) is stuck at line "EFI Stub: measured initrd data into PCR 9"
I also tried kernels 6.6.44 and 6.6.34 but they have the same behavior so I switched back to 6.1.89 kernels and it works flawlessly with those.
I thought it might be useful for you to have that kind of feedback. Thanks
Max
The text was updated successfully, but these errors were encountered: