You are not logged in.
Hi!
As you can tell, it's my first post here. For that reason, I apologize in advance if I overlooked some log file or command output. I've been using Arch and Linux for a few years now, but I'm struggling to debug this error.
What happened: I simply ran the regular "pacman -Syu" as usual and I didn't notice anything wrong at first. When I rebooted my system, I reached what looks like the login screen, but the system hangs at "Starting systemd-udevd version 252.3-1-arch". I cannot change tty and I'm not sent to some kind of emergency shell. For the info, I login directly in the tty and start xorg from the command line.
What I've tried:
- disabling unecessary systemd services
- comparing systemd journal with a successful arch boot on my laptop, but couldn't spot the key difference
- reinstalling the kernel (linux, linux-firmware)
- reinstalling and setting up grub
- boot with linux-lts
- downgrading kernel, but it seemed like a lot of packages needed to be downgraded. I also tried using Arch Linux Archive with pacman to downgrade, but it gave me an error and since it would temporary, I didn't bother to look into it
Using a bootable Arch drive, I "chrooted" into my Arch installation and looked at journalctl, but I couldn't find what is causing the bug. I feel like it's not directly related to the booting of the system (I think it gets past initramfs), it may be due to systemd? Here is the systemd log
https://0x0.st/o5HZ.txt
and here is the pacman log of the update that went wrong
https://0x0.st/o5HH.txt
It's difficult for me to figure out the solution because I don't know what's going wrong. I didn't think I'd one day post here, but I feel lost.
Thank you for your help!
Last edited by rd99 (2022-12-20 03:51:26)
Offline
Online
Thanks for the reply. So I:
- set MODULES=(nouveau) in my mkinitcpio.conf and removed kms from HOOKS.
- ran "mkinitcpio -P"
- rebooted
Now I get a little further in the booting process as I see that fsck is ran (says "/dev/sda2 clean" etc.). However, still no login prompt/tty. Looking at journalctl,
https://0x0.st/o5Pv.txt
it looks like getty was ran successfully? Could it be that I chose the wrong graphics driver? I thought I was using nvidia's driver but mkinitcpio says that "nvidia", "nvidia_modeset", "nvidia_uvm" and "nvidia_drm" modules are not found when I try to use them. I have tried using both arch packages "nvidia" and "nvidia-dkms". Also I saw in the log that nouveau was called.
It kinda looks like black magic as I don't understand why setting up the graphics driver in the initramfs makes a difference.
Offline
I think the suggestion was 'to give i915 a headstart' as in the other thread, since you also have hybrid graphics. So the suggestion would be to try just i915 in the MODULES array and to delete kms from HOOKS.
Edit: I don't know if 'hybrid' is the correct term as I'm not sure of all the different variations, but you have both integrated Intel graphics and a Nvidia graphics card.
Dec 19 09:29:09 arch-simon kernel: Console: switching to colour frame buffer device 200x56
Dec 19 09:29:09 arch-simon kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer deviceLast edited by cfr (2022-12-19 15:16:33)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
set MODULES=(nouveau) in my mkinitcpio.conf and removed kms from HOOKS.
That's completely wrong. The module to add there would be i915.
The new journal shows the lts kernel, neither nouveau (blacklisted by nvidia-utils) nor nvidia (lacking nvidia-lts) are loaded.
For nvidia-dkms you'd need the linux-*headers packages, but there are nvidia and nvidia-lts w/ prebuilt modules for those kernels.
Online
Ok so the idea is to startup i915 because I'm using both my graphics card and my motherboard's graphics?
I've tried using MODULES=(i915) in mkinitcpio.conf, but it didn't seem to make a difference. Here's the log using that: https://0x0.st/o5q4.txt . That's why I tried using nvidia and nouveau. When using nouveau, I get a little further as I mentioned in my previous post, but maybe I cannot conclude from seeing fsck's output that this was actually progress.
EDIT: It turns out that it's working with this modification, thank you for the help again! Here's what happened for reference: my main monitor is plugged into my graphics card and my secondary monitor is plugged into my motherboard. My login screen was on my main screen previously, but it now appears on my second screen (which was closed...). I guess it's because I'm loading i915 first.
Last edited by rd99 (2022-12-20 03:52:26)
Offline
My login screen was on my main screen previously, but it now appears on my second screen (which was closed...). I guess it's because I'm loading i915 first.
Yes, though it's irritating that if you ended up w/ the fb console on the nvidia GPU, it would not show up there still.
You can try to contorl the order a bit if you don't like the current situation, https://raw.githubusercontent.com/torva … /fbcon.rst
Look for "fbcon=map"
Online