You are not logged in.
So, I got this new laptop Acer Nitro 5 2021 edition and booted archiso 2022.01.01 and installed arch following this video and the arch wiki. I successfully installed arch linux and installed grub making my installation bootable, I rebooted into the installation then installed my drivers, the display manager, login manger and desktop environment and now it came time to restart my computer. I rebooted the computer but now it seemed to be stuck at the "checking /dev/'root partation' " part and the Caps Lock indicator was blinking repeatedly but no errors were showing it was just stuck at that checking part.
I waited for a while but still nothing was showing up so I just hold the power button and forced shutdown the computer, thinking I broke something during the installation I again followed the installation process and again installed my drivers, display manager, login manager and desktop environment, again i rebooted my system and again it seemed to be stuck at that checking process with the Caps Lock indicator blinking, I forced shutdown the laptop and went into the bios to see if something was up, i remembered disabling secure boot and fast boot but that time i looked in the bios the fast boot option was enabled so i just disabled it. Now, i tried to boot and it booted properly, i was in my desktop environment after the login process, i then installed programs i needed and rebooted to finalize the installation but again i was at that state again where the Caps Lock was blinking but now i saw some error message showing up, unfortunately i didn't take any pictures but at the end of that long error that filled my screen was something that informed me that it was a kernel panic. I forced shutdown the system and called it a day.
Today i tried booting and i was in. With the help of the wiki I was following the General recommendations and when looking at the journal log it returned this
$ journalctl -p 3 -b
Jan 25 23:45:06 AN5-15-45-R6Y8 kernel: mt7921e 0000:04:00.0: ASIC revision: 79610010
Jan 25 23:45:06 AN5-15-45-R6Y8 kernel:
Jan 25 23:45:06 AN5-15-45-R6Y8 kernel: mt7921e 0000:04:00.0: Firmware init done
Jan 25 23:45:10 AN5-15-45-R6Y8 wpa_supplicant[643]: bgscan simple: Failed to enable signal strength monitoringi then tried shutting down (hoping that would fix the problem in log) and starting my computer after having those problems with restarts and to check if that happens when i shutdown with $systemctl poweroff and started using the power button. And this time i booted without any problems but the journal log were still the same.
And this error message also shows up during shutdown or restart i think this might also be an issue
sd-umount[9540]: Failed to unmount /oldroot: Device or resource busy
sd-umount[9541]: Failed to unmount /oldroot/sys: Device or resource busy
shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy
shutdown[1]: Failed to finalize file systems, DM devices, ignoring.SUMMARY:
1. Kernel PANIC only when specifically restarting does not happen when shutdown and start.
2.
$ journalctl -p 3 -b
Jan 25 23:45:06 AN5-15-45-R6Y8 kernel: mt7921e 0000:04:00.0: ASIC revision: 79610010
Jan 25 23:45:06 AN5-15-45-R6Y8 kernel:
Jan 25 23:45:06 AN5-15-45-R6Y8 kernel: mt7921e 0000:04:00.0: Firmware init done
Jan 25 23:45:10 AN5-15-45-R6Y8 wpa_supplicant[643]: bgscan simple: Failed to enable signal strength monitoring3. During shutdown:
sd-umount[9540]: Failed to unmount /oldroot: Device or resource busy
sd-umount[9541]: Failed to unmount /oldroot/sys: Device or resource busy
shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy
shutdown[1]: Failed to finalize file systems, DM devices, ignoring.4. Fast boot option on BIOS always seems to automatically enable itself after a shutdown or reboot.
5. This laptop has a NVIDIA GeForce GTX 1650 Mobile / Max-Q, and I know nvidia as a company is a big pain for linux users so i though this info might help.
Last edited by FosRex (2024-11-15 05:37:28)
Offline
are you sure that you saved the settings when disabling fast boot? if you did then It might be a problem with your CMOS battery or IDK.
Offline
are you sure that you saved the settings when disabling fast boot? if you did then It might be a problem with your CMOS battery or IDK.
Thank you for your suggestion! The main issue—kernel panic and restarts—was actually resolved a while ago with a kernel update. I forgot to mark the thread as solved, so apologies for any confusion or wasted time.
As for the Fast Boot settings, I've decided to keep it enabled since my system runs smoothly with it on, and I haven’t encountered any problems because of it.
Offline