ok tried that .. to reduce the data spew I added: set pager=1 and set debug=all lines to the first grub menu selection .. this turns debugging on only if this menu is selected .. and although we got lots of output .. boot was normal .. if these lines were removed boot failed again .. this the Debug code is enclosing an essential bit in the menu processing section .. which becomes available when debug is turned on ..
In my first test .. I added the debug lines in the initial part of grub.cfg .. this also booted normally after all the data spew.. So the debug code encloses and essential line .. check recent changes there is a bad oops.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954566 Title: jammy-proposed grub-efi-amd64-signed 1.175+2.06 2ubuntu2fails to find or load kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1954566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
