Version 1.6.0-beta.3187 ipxe 2.0.0.x problems

[sgennadi]

Then I use latest ipxe 2.0.0.x on Lenovo M80t / M70t Gen3 keyboard not worked ,
if i change ipxe.efi to snponly.efi

sudo cp -a /tftpboot/ipxe.efi /tftpboot/ipxe.efi.backup
sudo cp -f /tftpboot/snponly.efi /tftpboot/ipxe.efi

keyboard worked but receive kernel panic:

Kernel panic - not syncing:
VFS: Unable to mount root fs on “/dev/ram0”
or unknown-block(1,0)

if I use old snponly.efi 2.0.0.0 all work

[Tom Elliott]

@sgennadi Can you try a little test for me please:

Set your bootfile from snponly.efi -> secureboot/snponly.efi please.

This may not fix the keyboad issue you’re seeing but i’m taking a guess.

I’m unable to replicate the error but all I have are VMs.

[sgennadi]

@Tom-Elliott
Fixed keyboard and kernel panic

[Tom Elliott]

@sgennadi SWEET! Thank you!

[Matthiman]

@Tom-Elliott said in Version 1.6.0-beta.3187 ipxe 2.0.0.x problems:

secureboot/snponly.efi

Nice work! I had exactly the same problem (see the other thread), and adding “secureboot” to the boot file fixed the issue (even though Secure Boot is actually disabled in the clients’ BIOS)

[Tom Elliott]

@Matthiman, @sgennadi We are workign to a processed method of allowing secureboot which (in my test env’s) has proven successful.

The nicer part is this does not require Secure boot to be enabled to work.

[Matthiman]

This post is deleted!

[sgennadi]

Are you plan secure boot fog kernel ?

[Tom Elliott]

@sgennadi It already is possible You just have to do the MOK or (use the new task type you see in working-1.6 to do all the work)

Kernels are already signed automatically.

[sgennadi]

Working