leap 15.1, kde desktop hangs after yast update

Dear experts

I wanted to do the final update before I upgrade to 15.2.
I used YAST, but not selecting NVIDIA drivers. (prime laptop uefi dual boot with windows)

Now at startup I get:

 0...] ACPI BIOS Error (bug): Failure creating  _GPE..E4A], AE.ALREADY. EXISTS (2..../dswload2-316) 

 0.....] ACPI Error: AE_ALREADY EXISTS, During name lookup/catalog (2... /psobject 220) 

[0....] ACPI Error : Method parse/execution failed \., AE ALREADY.EXISTS (0... /pspdrse-516) 
 Invalid Owner Id: BBB (2.../utowneride156) AE_ALREADY_EXISTS, (SSDT: Optgabl) while loading tall 
1 table load failures, 10 successful (20...3/tbxf load-215 
bbswitch: No suitable _DSM call found. HAREM Failed to start Load Kernel Mbdules. See Hsystemal status systemdamoduleseload.service for details. 

Starting Apply Kernel Variables... 
[OK] Started Apply Hernel Varriables. 

[OK] Started udev Coldplug all Devices. Starting dracut initqueue hook... Starting Show Plymouth Boot Screen... 

Invalid zero thread count in method (2.../dsmethod)

Welcome to openSUSE Leap 15.1 Kernel 4.12.14-1p151.28.87-default (ttyl). 

I login and I run:

> systemct1 status systemdemoduleseload.service 

and get:

systemd-modules-load.service - Load Kernel Modules Loaded: loaded (usr/lib/systemd/system/systemd-modulese-load.service: static; vendor preset: desabled) 
Active: failed (Result: exit-code) since Wed 2020-12-23 04:04:42 EET; 52sec ago
Docs: man:systemd-moduleseloadeservice(8) man:modules-load.d(5) 
Main PID: 422 (code-exited, status=1/FAILURE 

What is the fault?
Can I get to the previous state?
Is there a way to unistall all yast updates using commands?

(…=numbers or text)

I managed to work around it on my own.

I checked the var/log files and found that probably it was a graphics card problem so I disabled it using modprobe. On the grub screen, I presesed “e” and in the line with ‘Linux’ I added the following at the end:

Then I selected intel instead of nvidia drivers

sudo prime-select intel

I got an error stating no screens were detected but I managed to get to plasma desktop with a 2nd reboot

The joys of hybrid graphics! :slight_smile:

I like your optimistic viewpoint ;).
Imagine though you had a deadline and your work was stalled by something like this…

Happy holidays

That’s life. I avoid hybrid graphics like the plague. :wink:

Update n2:

It was a bad idea to exclude the nvidia updates at first place.

After installing all the recommended updates and a:

prime-select nvidia

everything is back to normal

Not directly related but, it’s also advisable to check the UEFI/BIOS settings for the choice as to which graphics unit shall be used by the BIOS display at boot time –

  • Usually something like choice between “IGFX” (the Mainboard’s internal graphics module – implies the GPU integrated with a CPU) and, “PCIe” (the GPU in the Mainboard’s PCI Express slot) …

I have absolutely no idea if, the Linux Kernel makes choices based on this BIOS setting but, nothing would surprise me …