I made the mistake of running an Nvidia routine on my fresh update to Leap 42.3
and now the system, if I leave it to boot automatically, only gets to the console and waits for a login.
If I boot from the most recent snapshot then the full graphic interface is restored as normal.
What might be my options to restore a normal unattended boot sequence?
I understand your main problem (the solution might be to roll back to that snapshot, but wait for more advice on this), but I do not understand what you mean with “boot automatically” and “normal unattended boot sequence”. Do you mean the same with both expressions?
And when yes, do you mean this contrary to now where it boots only in the CLI (console, no X)?
Hi, to clarify:
If I leave the machine to restart without user participation it gets to the “opensuse Leap 42.3” default option, runs this automatically and I end up in the console no X.
If I navigate to the third option (after opensuse with advanced options) “Other” then I get a list of bootable snapshots. I select the first and this boots into a regular Gnome environment. The first is what I meant by unattended booting, the second requires user intervention.
I’ll do some reading on rollback, thanks for the suggestion.
Determining which snapshot to rollback should not be difficult if you want to rollback to something recent.
Just remember the general rules when snapshots are created
On each boot
Before each installation
If you need more info, there are snapper commands to inspect the contents of snapshots and compare, but to date I’ve not had to use those.
As always,
There are good sources of info for snapper, starting with the help, MAN pages and the ArchWiki.
I found the drm-kmp-default file in Yast, but it won’t let me do anything to it since I am in a snapshot and this locks down various parts of the system.
Error message is: Subprocess failed. Error: RPM failed: error: can’t create transaction lock on /var/lib/rpm/.rpm.lock (Read-only file system)
Rollback is complete and seems to have worked well.
Unattended boot now works as expected, with automatic start of the graphical interface.
The drm-kmp-default package is still in place, so it may be that this package is not pertinent in this case; I will keep it in mind for future.