doktor5000 wrote:If it really stops that early during boot, you can't. You could start failsafe/recovery mode though, to see if that boots - simply select it from bootloader in the advanced menu.
Also, did you try to disable the TPM as mentioned ?
Linares wrote:Then I have started Mageia in recovery mode, and it has started in command line, but once I have set the administrator password I do not know what I must do to return to normal boot mode with Plasma.
systemctl isolate graphical.target
journalctl -a > /tmp/journal.log
doktor5000 wrote:If you can switch to another tty, then after entering systemctl isolate graphical.target in the first one, switch to another, and in that one write the journal logs to a file as root
- Code: Select all
journalctl -a > /tmp/journal.log
and then later, upload /tmp/journal.log here as an attachment.
journalctl -ab > /tmp/journal.log
may 17 19:19:24 Mageia dkms-autorebuild.sh[1137]: nvidia-current (430.64-8.mga7.nonfree): Installing module.
may 17 19:19:24 Mageia dkms-autorebuild.sh[1137]: Kernel devel files for 5.6.6-desktop-1.mga7 not installed. Cannot install this module.
may 17 19:19:26 Mageia sddm[4087]: Starting...
may 17 19:19:26 Mageia sddm[4087]: Logind interface found
may 17 19:19:26 Mageia sddm[4087]: Adding new display on vt 1 ...
may 17 19:19:26 Mageia sddm[4087]: Loading theme configuration from ""
may 17 19:19:26 Mageia sddm[4087]: Display server starting...
may 17 19:19:26 Mageia sddm[4087]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{8c476d62-cc1d-4525-a932-4e2902167467} -background none -noreset -displayfd 17 -seat seat0 vt1
[...]
may 17 19:19:26 Mageia sddm[4087]: Failed to read display number from pipe
may 17 19:19:26 Mageia sddm[4087]: Display server failed to start. Exiting
may 17 19:19:26 Mageia audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sddm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
may 17 19:19:26 Mageia systemd[1]: sddm.service: Main process exited, code=dumped, status=6/ABRT
may 17 19:19:26 Mageia systemd[1]: sddm.service: Failed with result 'core-dump'.
urpmi kernel-desktop-devel-latest
Linares wrote:But I have a problem with kernels and by doing this I could definitely lose all access to Mageia.
Linares wrote:At startup I had 4 kernels. Two working properly. The other two do not, with these problems that we are seeing. (Go to viewtopic.php?f=7&t=13456&p=79017#p78820)
rpm -qa | grep kernel | sort
doktor5000 wrote:Please provide the output of
- Code: Select all
rpm -qa | grep kernel | sort
systemctl start network.service
urpmi.update -a
kernel-desktop-5.1.14-1.mga7-1-1.mga7
kernel-desktop-5.3.11-1.mga7-1-1.mga7
kernel-desktop-5.5.15-3.mga7-1-1.mga7
kernel-desktop-5.6.6-1.mga7-1-1.mga7
kernel-desktop-devel-5.3.11-1.mga7-1-1.mga7
kernel-desktop-devel-5.6.13-5.mga7-1-1.mga7
kernel-desktop-devel-latest-5.6.13-5.mga7
kernel-desktop-latest-5.5.15-3.mga7
kernel-firmware-20190603-1.mga7
kernel-firmware-nonfree-20200316-1.mga7.nonfree
kernel-userspace-headers-5.5.15-3.mga7
virtualbox-kernel-5.3.11-desktop-1.mga7-6.0.14-6.mga7
virtualbox-kernel-5.5.15-desktop-3.mga7-6.0.20-1.mga7
virtualbox-kernel-5.6.6-desktop-1.mga7-6.0.20-2.mga7
virtualbox-kernel-desktop-latest-6.0.20-2.mga7
Users browsing this forum: No registered users and 1 guest