The directory that does exist at that level is capitalized, “/Boot”. The GRUB menu entry has taken not changed, though oddly the YaST module shows as if the change took.
I’ve tried looking this up myself, and used LLM and both just seem to run me in circles. I’d rather not reinstall a system I’ve had working nicely for a long while. Note; I used to dualboot with Windows but as of some months ago switched to single booting and eliminated the Windows install.
You need to run sudo update-bootloader --config after making changes to the bootloader in YaST. And, let me please warn about trusting AI , I have over the past seen quite some hallucinations re. bootloaders.
The error “suse-enable-tpm failed. code 1” typically indicates a problem with enabling the Trusted Platform Module (TPM) on your SUSE system. You may need to check your BIOS settings to ensure TPM is enabled and properly configured.
I’m pretty aware. I use the bots when I run out of ideas. Then it’s typically a sort of adversarial exercise of mostly disproving them, which is useful if frustrating; but only after exhausting what I could gather on my own.
I managed to figure out how to get a result I wanted though it still doesn’t really explain the error, which is no longer occurring. In retrospect, I probably should have lead more with what I was trying to do.
I had an alternative kernel installed, and had wanted to change it so whatever current kernel-default was would be the default entry for boot. Ultimately it looked clear I couldn’t have that exact behavior so I just removed the other kernel since it had been giving me trouble enough with diminishing benefit.