You are not logged in.
Pages: 1
Hello,
I have issue after installation. Everything works file, but I have to boot it in failback mode.
So, autodetect hook doesn't detect all needed modules.
Is there a way, how can I find, which modules are needed and not detected by autodetect hook?
So, I can add them into /etc/mkinitcpio.conf.
I have Dell latitude 5400 and I already tried intel modules and workarounds from archwiki, and it still boots only in failback mode and gets frozen in black screen in normal mode.
Offline
gets frozen in black screen in normal mode.
It's very hard to distinguish between a kernel module that hasn't finished initialising and a missing kernel module.
Are you booting to a display manager (like gdm , sddm etc) ?
Please post the journal from a failed boot using journalctl -b some-negative-number
( -1 will show the journal from the previous boot)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
It seems there is no such journalctl log from failed boot.
journalctl -b -1 returns me previous boot, but in failback mode and in previous time.
journalctl -b returns me current boot with failback mode.
I think, there is maybe log from dmesg, but I have to get it in chroot after failed boot. Should I get it? Will it help?
Offline
Pages: 1