You are not logged in.
Hi there
Yesterday I've updated everything using
pacman -Suy Today after reboot got black screen after loading.
Tried nomodeset and acpi=off with no luck.
Then decided to get more logs with setting debug kernel param and by some not clear reason after that boot was successful. I've checked everything only that parameter makes it works.
The docs says debug: Enable kernel debugging (events log level).
So, at now I can only be booted normally with debug parameter.
I can't see how it might be connected but it works.
The current command in grub.cfg is
linux /boot/vmlinuz-linux-lts root=UUID=5ce52f0d-3f91-46f2-954d-1aa2e4858d24 rw debug loglevel=3 quiet module_blacklist=nouveau intel_iommu=on rd.driver.pre=vfio-pci video=vesafb:off,efifb:off vfio-pci.ids=10de:1c02,10de:10f1 I tried it without any logging params and iommu stuff i.e:
linux /boot/vmlinuz-linux-lts root=UUID=5ce52f0d-3f91-46f2-954d-1aa2e4858d24 rw and still it works only with debug
I'm confused what to do now to remove debug and get loaded normally
Any ideas?
uname -a:
Linux archpc 5.10.27-1-lts #1 SMP Tue, 30 Mar 2021 13:22:29 +0000 x86_64 GNU/LinuxLast edited by ittru (2021-04-05 07:41:37)
Offline
Sounds like the usual race condition that can happen if graphics drivers aren't loaded in time, and by enabling debug the additional log processing edges out the race so it ends up working out. Set up early KMS
Online
Would it be helpful to have a locked "Common issue of the month" sticky where mod could just put stuff that comes up over and over and over and over and over again as users update theri system?
Offline
"Common issue of the month" sticky
I'm not a mod, so I don't have a say in this (and I respect that), but imo the Arch way is to simply dustbin these with a short "search before posting", because if people are too lazy to skip their own research/troubleshooting and go straight to posting that was always the proper response.
Offline
I'm wondering what has changed that I've got that issue. My setup and config was functional for several years already with regular updates.
FYI: early KMS with specifying nvidia stuff there was not helpful. Still have to use debug kernel param to get loaded normally. Also I removed any iommu stuff to be sure that it's not connected so I don't have anything special there now.
Last edited by ittru (2021-04-05 05:34:27)
Offline
Systemd introduced race condition.
early KMS with specifying nvidia stuff there was not helpfulCan you please specify what exactly you did and the output of
lsinitcpio /boot/initramfs-linux-lts.img| grep nvidiaTried nomodeset and acpi=off with no luck.
doesn't sound like a KMS issue, though.
Can you boot the multi-user.target and what is your graphical.target and from what kernel version did you update (what was updated in general)?
Offline
Hi there
Since relying on non deterministic approach in "fixing" it by using additional logging was bad Idea and I just wanted to fix it as quick as possible to prevent any time spends in future. My goal wasn't finding out exactly what is going on there.
What I found after I wrote my last message that some modules/drivers that may introduce race condition (maybe) still was in use like vfio virtio and so on. So I removed them from modules-load.d/ and did mkinitcpio -P
Now it works without any additional debug logs.
It looks like some change was introduced in some of that drivers which led to given issue in my config (maybe). Later I will try to enable iommu and related stuff back cautiously and see what will happen
Thank you to everyone to pointing me where to look at.
Offline