[SOLVED] My two computers won't boot after update

[flavianoep]

Help! After the last update, both my computers won't boot. They fall at starting systemd-modules-load.service. It's all I know.

[doktor5000]

Hi there, some more information would be necessary.
What Mageia release do you use and from what medium did you install ? Also, what graphics cards do those boxes have ?

[flavianoep]

Thanks for the answer

I got one of them to boot after choosing kernel 6.5.13-desktop-6.mga9. The other one has only kernel 6.5.14. I used the "remove old kernels" tool some times, and "urpme --auto-orphans" on the one that has no other kernels. The graphics cards on both machines are Intel. There was a Mesa update before they stopped working.

The install media was Mageia 9 beta 1 live iso.

[morgano]

Regarding the one that now boots, make sure to run updates again.
Recently we released kernel 6.6.14.

For the one not booting, can you in boot menu select "recovery mode", give root password, issue telinit 3 (enables network), log in as root, and issue "urpmi --auto-up" ?.

* Always make sure to have at least two kernels installed... *

[flavianoep]

Sorry. I should have said that recovery mode doesn't work. The prompt to insert a user then the password doesn't appear at all. I'll try using chroot from the live media.

[canadaist]

Recovery mode is offered as an option for boot, not after login.


Also just interjecting because it was sited as a command to possibly use to move toward recovery, but

Code: Select all

urpme --auto-orphans

Is not a command to solve any problem. It removes some files, and the files removed may actually reduce functionality, unless you have prepared.

I don't think it should be offered as command so blithely by urpmi.

[pmr]

Hi,

Help! After the last update, both my computers won't boot. They fall at starting systemd-modules-load.service. It's all I know.

I also encountered a similar problem. I have 3 computers with Mga9. They have different hardware but I attempt to maintain them in a similar state (read: perform frequent updates at similar timepoints).

One of them stopped booting after the last update - from 6.5.13-desktop-6.mga9 to 6.6.14-desktop-2.mga9.

There are 3 kernels currently installed on it:
6.5.11-desktop-5.mga9
6.5.13-desktop-6.mga9
6.6.14-desktop-2.mga9

6.6.14-desktop-2.mga9 does not boot (a "boiling cauldron" appears, no reaction apart from Ctrl-Alt-Prtscr-B), the remaining two work flawlessly.
After some keystroke combination I could also remark once that ~"failed to start systemd-modules-load.service".

The other two computers do not have this problem.

Code: Select all

[root@pmr etc]# inxi -v1
System:
  Host: pmr Kernel: 6.5.13-desktop-6.mga9 arch: x86_64 bits: 64
    Desktop: KDE Plasma v: 5.27.5 Distro: Mageia 9
CPU:
  Info: quad core Intel Core i7-4771 [MT MCP] speed (MHz): avg: 1163
    min/max: 800/3900
Graphics:
  Device-1: NVIDIA GK110B [GeForce GTX 780 Ti] driver: nvidia v: 470.223.02
  Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
    loaded: nvidia,v4l gpu: nvidia resolution: 1: 1920x1200~60Hz
    2: 1200x1920~60Hz
  API: OpenGL v: 4.6.0 NVIDIA 470.223.02 renderer: NVIDIA GeForce GTX 780
    Ti/PCIe/SSE2
Drives:
  Local Storage: total: 2.05 TiB used: 800.91 GiB (38.1%)
Info:
  Processes: 305 Uptime: 33m Memory: 31.29 GiB used: 3.37 GiB (10.8%)
  Shell: Bash inxi: 3.3.26


[morgano]

Please open a bug for this issue.
https://wiki.mageia.org/en/How_to_report_a_bug_properly

Also please attach compressed journal log of the failed boot.

[katnatek]

From the kernel 6.5 as root

Verify if you have the kernel-desktop-devel in version 6.6.14

urpmi kernel-desktop-devel

dracut --regenerate-all -f

Kernel 6.6.14 in desktop and linus flavors may don't boot if dkms-anbox is present if you have this module, try install kernel-server and kernel-server-devel boot server kernel in grub's advanced options to see if works.

Also in near future updates to mesa packages will arrive , perhaps you can try again after that

[flavianoep]

I got into the machine that doesn't work at all using chroot through a live media. Is there a way to downgrade the kernel?

[papoteur]

You don't need to uninstall it. You have only to select a working kernel to boot, no?

[katnatek]

I got into the machine that doesn't work at all using chroot through a live media. Is there a way to downgrade the kernel?

Try install kernel-desktop-6.5.13-6 and kernel-desktop-devel-6.5.13-6

In grub advanced options of your system, did you have kernel 6.5? If so , boot that option

[morgano]

Same problem reported on MLO
https://www.mageialinux-online.org/foru ... 6-6-14.php

[flavianoep]

I got into the machine that doesn't work at all using chroot through a live media. Is there a way to downgrade the kernel?

Try install kernel-desktop-6.5.13-6 and kernel-desktop-devel-6.5.13-6

How can I do that? I tried the --downgrade flag, yet urpmi complained that I already had kernel-desktop-6.6.14 installed.

[katnatek]

I got into the machine that doesn't work at all using chroot through a live media. Is there a way to downgrade the kernel?

Try install kernel-desktop-6.5.13-6 and kernel-desktop-devel-6.5.13-6

How can I do that? I tried the --downgrade flag, yet urpmi complained that I already had kernel-desktop-6.6.14 installed.

try download the rpms and installl with rpm -i

As last option I don't know if you use dkms-anbox so try to add this modprobe.blacklist=ashmem_linux or modprobe.blacklist=ashmem_linux,binder_linux (just to be sure the last one) to kernel options of kernel 6.6

[flavianoep]

Removing dkms-anbox solved it! Since I couldn't get waydroid to work, I won't miss it. Thank to all of you for your help