[Solved] Booting Issue

askreceive · 2022-03-01 09:10:24

Greetings. Several days ago, I returned to my PC with 98 outdated packages on my system, including zen kernel and nvidia drivers updates after a week of inactivity. Since I returned, my system has been behaving peculiarly and sometimes it freezes after the "starting arch" message and only shows the blinking bar or underscore letter after; Keyboard caps lock light doesn't work, and everything else cease to function when this happens. I can only force reboot from here, and my temporary workaround is to quickly press the tty command (CTRL + SHIFT + F2) after the "starting arch" message shows up, and then it will boot to the login screen/lightdm.

The system works fine after, but since I'm new to Arch, I prefer to fix it as soon as possible and be alarmed about it, even though it seems like the issue is minor. I presume this is either hardware issue or update/kernel issue or both. I mentioned the former because my PC would also shutdown on its own right (then on again) before the bios screen multiple times and after multiple force reboot or shutdowns, it will boot to grub and finally the aforementioned issue will occur. If the shutdown issue does not occur, then the system will boot fine for some reason without needing the tty command.

I've checked through journalctl -b -l, and it seems like there's no error there, or I could just missed something. There are some yellow texts, and my search led me to this post:
https://bbs.archlinux.org/viewtopic.php?id=273447

I really hope I can find quick solution to all of this. I can't exactly pinpoint why this is happening: hardware or the operating system. The circumstances make me believe that it's hardware-related, but I want to make sure.

Can anyone help or does anyone have a suggestion on why this is happening?

Thank you.

Last edited by askreceive (2022-03-05 11:35:11)

MartinX3 · 2022-03-01 14:25:36

Boot from a usb stick to exclude hardware issues.

Maybe your nvidia driver wasn't installed successful.
I personally use `nvidia-dkms`.

Last edited by MartinX3 (2022-03-01 14:25:46)

V1del · 2022-03-01 14:50:07

This can be caused by an early boot race between whether your display manager starts before the graphics device is actually ready, can generally be alleviated by setting up early KMS: https://wiki.archlinux.org/title/NVIDIA … de_setting do the initramfs and the pacman hook, take note that the Target= line(s) need to reference the actual nvidia package name you're using this can generally happen on fast boot disks where graphical target is reached quickly enough before the graphics device is fully ready.

Last edited by V1del (2022-03-01 14:51:54)

askreceive · 2022-03-01 20:25:14

The hardware/shutdown issue still persists afterall, but I managed to boot through USB Arch Installation Medium after and then booted into the system without the freezing issue; Can't be sure if it's coincidence or USB boot somehow temporarily solves the issue. But I think I can determine that this is more likely hardware issue instead of Arch issue.

And deepest apologies, but it looks like I'm illiterate and couldn't find what files to configure to add those modules to the initrafs. I'm not sure if mkinitcpio is the right file either. Could you give me a TL; DR?

V1del · 2022-03-01 20:52:07

For the plain functionality test, add

MODULES=( nvidia nvidia_modeset nvidia_uvm nvidia_drm )

to your /etc/mkinitcpio.conf (or if you want to be "more correct" uncomment the existing commented line and then run

mkinitcpio -P

to regenerate the images, note that this will possibly significantly increase the size of your initramfs be wary of that if your /boot partition is small.

FWIW if you wanted to check the journal of the previous boot for errors you'd look at

journalctl -b -1 #The number, not the letter

to get the previous boot, in doubt post that after rebooting from reproducing the issue.

askreceive · 2022-03-01 21:04:56

I couldn't find the nvidia.hook file. I assume I have to create it in the directory as wiki states, and since I'm using linux zen, I assume the target is linux-zen for zen kernel, but what about the exec? The comment says change exec line if a different kernel is used,

Example:
[Trigger]
Operation=Install
Operation=Upgrade
Operation=Remove
Type=Package
Target=nvidia-dkms
Target=linux-zen
# Change the linux part above and in the Exec line if a different kernel is used

[Action]
Description=Update Nvidia module in initcpio
Depends=mkinitcpio
When=PostTransaction
NeedsTargets
Exec=/bin/sh -c 'while read -r trg; do case $trg in linux) exit 0; esac; done; /usr/bin/mkinitcpio -P'

Edit:
I've checked the logs. There are some yellow lines such as data leak for SMT/CPU-related, but no red line or obvious errors so far.

Last edited by askreceive (2022-03-01 21:06:19)

V1del · 2022-03-01 21:18:18

Many errors and problematic constellation are not necessarily logged as errors, chinese whispering doesn't really help, post the output so other people can look.

You can ignore the pacman hook for a simple test but yes that would generally be the case that you change the linux in the exec line to linux-zen as well.

askreceive · 2022-03-01 21:25:11

Here you go as requested:
https://pastebin.com/a3efJLZW
This is the output from journalctl -b -1 > log.txt

Edit: I fixed the output/link. I apologize.

Last edited by askreceive (2022-03-02 03:47:35)

askreceive · 2022-03-02 03:47:10

I'd like to add that this issue happens only if I leave the PC off for a period of time (i.e hours). If I manage to boot into the system, and then turn off for a minute and then turn on again, the PC will boot with no issues.

The workaround v1del gave me did not work, and the issue occurred again this morning. I managed to login by force shutdown or reboot twice.

Last edited by askreceive (2022-03-02 03:50:36)

seth · 2022-03-02 06:50:14

Mar 02 10:39:03 toastedvessel kernel: NVRM: Xid (PCI:0000:01:00): 62, pid=552, 0a7b(16d0) 00000000 00000000

https://docs.nvidia.com/deploy/xid-errors/index.html wrote:

62: Internal micro-controller halt

The conditions of #9 kinda point towards a hardware issue - maybe power supply related, maybe bad seating.
Does the issue happen w/ the 470xx series? ( https://aur.archlinux.org/packages/nvidia-470xx-dkms & https://aur.archlinux.org/packages/nvidia-470xx-utils )

askreceive · 2022-03-02 06:56:21

I'm not certain if the issue happens before or after the update. I'll try checking the PSU later.

askreceive · 2022-03-05 11:37:30

I tag this as solved-ish. I currently have a workaround that works, but not a solution as of yet. I did a fresh install of Arch recently, but the issue still persists. I at least know now that this issue seems to be related to my hardware and not the OS itself. Thanks everyone for the suggestions.

Arch Linux

#1 2022-03-01 09:10:24

[Solved] Booting Issue

#2 2022-03-01 14:25:36

Re: [Solved] Booting Issue

#3 2022-03-01 14:50:07

Re: [Solved] Booting Issue

#4 2022-03-01 20:25:14

Re: [Solved] Booting Issue

#5 2022-03-01 20:52:07

Re: [Solved] Booting Issue

#6 2022-03-01 21:04:56

Re: [Solved] Booting Issue

#7 2022-03-01 21:18:18

Re: [Solved] Booting Issue

#8 2022-03-01 21:25:11

Re: [Solved] Booting Issue

#9 2022-03-02 03:47:10

Re: [Solved] Booting Issue

#10 2022-03-02 06:50:14

Re: [Solved] Booting Issue

#11 2022-03-02 06:56:21

Re: [Solved] Booting Issue

#12 2022-03-05 11:37:30

Re: [Solved] Booting Issue

Board footer