- There is no recent UEFI Bios available.
- I am not using plymouth.
I have installed kernel 6.12.11 again and I am testing.
Could you please post the output(s) of any command(s) used; as you use them? Knowing if the commands were error-free will probably be useful for others wishing to help.
Regards.
3 Likes
I have installed the kernel with the Manjaro settings manager.
What I have done first: I have installed kernel 6.12.11 and then the computer did not boot to login manager sddm.
Removing quiet from the grub command line did not lead to any error messages. Since I could nor reproduce the boot failure.
Now, I have reinstalled the kernel (with Manjaro settings manager) and I am testing.
Mod Edit:- Minor formatting.
ran update today, Feb 8, was on kernel 6.11, 6.12 installed, rebooted to black screen with error message (No Signal HDMI, your device is going into standby mode) seems 6.11 was deleted.
had same issue after using kernel setting manager to install 6.12 kernel, was able to reboot with present 6.11 kernel
What I have also observed: the logo between sddm and desktop is not displayed.
Did you try switching to X11 while you using Kernel 6.6 and then you may try 6.12?
From my understanding you need additional parameters adjustments if you want to boot into a newer Kernel (with a nvidia card), in combination Wayland + above Kernel 6.6
I have tried to use X11 before and the desktop falters.
What has happend: I installed kernel 6.12.11, the next boot was successful.
The boot the after next boot stops.
I have - very, very rare - situations where the system was hanging after a kenel upgrade - usually I can fix it using REISUB - but that needs to be configured beforehand.
To troubleshoot the system, first step is to be sure to reach the grub menu.
If you are not seeing it - you can force display by holding shift-key while booting.
When it displays - press e on the item you want to boot and add the number 3 to kernel commandline.
This should allow you to reach a working system without graphical interface.
Then disable the login manager until you have worked out what causes the issue.
sudo systemctl disable sddm
To further test what is causing - you can use the --test-mode parameter and watch the output
sddm-greeter --test-mode
If needed you can move between TTY using Alt←/→ which can be handy when you want to kill the greeter because it becomes unresponsive.
To identify the process started use
pgrep sddm
Then kill the id(s) returned from the command
When you have found the cause and corrected - you want to re-enable sddm
sudo systemctl enable sddm
Should you need to supply log content or command output to aid in getting troubleshooting help you can still make use of online pastebins - even if you have not graphical tool available.
See this topic → [HowTo] Use public command-line pastebin services without installing anything!
Just one minute ago, the computer did not boot to sddm.
This happens suddenly.
What I have done first: I have removed quiet from /etc/default/grub.
Now, I am waiting for the next boot failure with kernel 6.12.11.
I have removed quiet from boot command line and I see nothing, since the screen goes black in this moment.
The boot failure happens occasionally.
You need to remove splash as well.
Also remove plymouth from your mkinitcpio.conf hooks.
Then rebuild
sudo mkinitcpio -P
sudo grub-mkconfig -o /boot/grub/grub.cfg
Boot splash is also disabled and at the time, when the computer freezes, the screen goes black.
Now, I have executed the two commands.
Three lines are displayed and then the screen goes black.
After that, the boot sequence is displayed.
Which three lines?
I am not sure what you mean by
If you are able to edit the configuration and rebuild init and grub configuration - I assume you are able to start the system - and succesfully reach the console.
Did you disable sddm as suggested above?
If it is a kernel regression - the boot failure would be consistent - since it is not, it points more in direction of a hardware error.
Where the error is located - it is impossible to say - but since we do not know if you can reach a working console system - it is difficult to point at the GPU in use as the possible source.
The following three lines are displayed:
running early hook [udev)
running hook [udev]
triggering uevents
then the screen goes black on every boot.
The computer crashes in this moment.
When the boot is successful, the computer boots further.
Kernel 6.12.17-1 boots to no desktop sometimes.
Theses three lines are displayed:
running early hook [udev)
running hook [udev]
triggering uevents
And then the monitor goes to standby.
This happens 1 of 20 boot sequences.
This problem still exists with kernel 6.12.19.
Please provide the output of;
cat /etc/mkinitcpio.conf