This system has hybrid Intel/NVIDIA GPUs. During installation of Tumbleweed I had to add nomodeset to the launch parameters to fix a black screen. I’ve installed the proprietary NVIDIA driver following the Automated Installation instructions and it seems that they’re installed. I haven’t removed nomodeset yet, and from what I can glean from the wiki, I don’t think I’m supposed to for these drivers.
Anyway, my built-in display is a 4k display. I know this from its previous life as a Windows dev machine. However, Tumbleweed’s display manager has it locked to 1280x1024 and claims that this is the only resolution it supports. Why isn’t it detecting the full capabilities of the monitor?
I’m using GRUB2 BLS, so I don’t have a file at /etc/default/grub. Where do I find the launch command to remove the nomodeset? Do I need to run a different command to rebuild my initrd too?
No. It only changes /etc/kernel/cmdline and you still need to invoke update-bootloader --config to apply the changes (which will internally call sdbootutil update-all-entries.
But you are right, update-bootloader is the openSUSE way to change bootloader configuration without knowing the underlying implementation. I am just tired explaining it all these years and still seeing the grub2-mkconfig offered as alternative to the YaST Bootloader module.
Hmm, concerning output. I have another thread going where I’m getting help troubleshooting TPM support. It seems I’ll need to get that resolved first before I can continue here.
Should I revert my edits to /etc/kernel/cmdline and re-run this command to attempt to restore prior bootloader state or just rely on the last snapshot?
adam@localhost:~> sudo sdbootutil update-all-entries
[sudo] password for root:
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Garbage after device path end, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Garbage after device path end, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Garbage after device path end, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Device path size does not match, ignoring.
Garbage after device path end, ignoring.
WARNING:esys:src/tss2-esys/api/Esys_PolicyOR.c:286:Esys_PolicyOR_Finish() Received TPM Error
ERROR:esys:src/tss2-esys/api/Esys_PolicyOR.c:100:Esys_PolicyOR() Esys Finish ErrorCode (0x000001c4)
Failed to add OR policy to TPM: tpm:parameter(1):value is out of range or is not correct for the context
Failed to submit super PCR policy: State not recoverable
Error creating the systemd-pcrlock policy!
The error has nothing to do with nomodeset. It simply means that the current state of TPM (PCR values) does not match the state expected by the policy, so sdbootutil (strictly speaking, systemd-pcrlock) cannot update the policy automatically. If you mean that your root is encrypted and is not unlocked automatically - yes, it has the same reason.
Just to put a line under this, after fixing my TPM issue in the other thread, I re-ran sdbootutil update-all-entries just in case something didn’t apply correctly on the first attempt. I was then able to reboot with no FDE PW prompts and my built-in display is now showing a full range of supported resolutions. Thank you to everyone who replied!