You are not logged in.
Pages: 1
Since my last update my computer refuses to boot linux.
I installed linux-lts and everything is working fine there. Even reinstalled the system and same story: linux-lts boots just fine but the regular kernel fails.
- linux-fallback shows some info on the screen and gets stuck at "running udev cleanup hook".
- linux just shows a black screen. nothing more.
i tried journalctl but those boots are not listed in --list-boots.
what can i do to find the problem?
I have a ga401 asus notebook. It contains a ryzen 5900HS and a nvidia 3060.
Offline
What was the last version of linux that worked? Which version of linux that has the issue? Can you boot to multi-user.target, rescue.target or emergency.target?
Offline
Since my last update my computer refuses to boot linux.
I installed linux-lts and everything is working fine there. Even reinstalled the system and same story: linux-lts boots just fine but the regular kernel fails.
...
I have a ga401 asus notebook. It contains a ryzen 5900HS and a nvidia 3060.
Does it happen on Wayland, or X11, or both? I am in a similar situation - linux-lts works well (with both Wayland and X), but the regular 6.6.7 only works with X11.
-----------
CPU: Intel i7-8565U (8) @ 4.600GHz
GPU: Intel WhiskeyLake-U GT2 [UHD G
GPU: NVIDIA GeForce MX150
Memory: 2101MiB / 15662MiB
Last edited by Rtqate (2023-12-23 06:31:19)
Offline
[sam@sam ~]$ uname -a
Linux sam 6.6.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 14 Dec 2023 03:45:42 +0000 x86_64 GNU/Linux
[sam@sam ~]$ echo $XDG_SESSION_TYPE
wayland
Offline
Thanks for the help guys!
[07:14 simon@simonlaptop efi :(] uname -a
Linux simonlaptop 6.1.69-1-lts #1 SMP PREEMPT_DYNAMIC Wed, 20 Dec 2023 17:23:40 +0000 x86_64 GNU/Linux
[07:15 simon@simonlaptop efi :)] echo $XDG_SESSION_TYPE
x11
changing the boot target does not change anything. I think it halts long before, that's why i dont even see logs in journalctl
This is the startup screen in linux-fallback
https://imgur.com/a/DDvjvjK
linux just doesn't even show a thing...
Offline
6.6.7 has a backlight bug w/ amdgpu
Next to the multi-user.target, also add "nomodeset" to the kernel parameters and (in doubt) remove "quiet", does that work?
Then please post any journal (from the LTS kernel is ok)
sudo journalctl -b | curl -F 'file=@-' 0x0.st
think it halts long before, that's why i dont even see logs in journalctl
Or because you're rebooting w/ the power button?
You can also try the https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
Offline
i tried to add nomodeset, and it still shows the same behavior with linux 6.6.7
here are my logs:
nomodeset:
http://0x0.st/Hg4t.txt
regular:
http://0x0.st/Hg4y.txt
Offline
Just in case it's the same issue - I updated to the new kernel (6.6.8), which loaded as usual and started Wayland successfully.
I first tried it with X, and saw a very long delay (blank gray screen, 10 or so seconds) between login at GDM and Gnome shell.
Last edited by Rtqate (2023-12-23 19:52:50)
Offline
i tried to add nomodeset, and it still shows the same behavior with linux 6.6.7
What was the last version of linux that worked? Which version of linux that has the issue?
Offline
6.6.8 fixes a backlight issue in 6.6.7 and @wannabee has the relevant HW as well, but that would rather turn off the display, not stall the boot.
@wannabee
Enable https://wiki.archlinux.org/title/NVIDIA … de_setting and on a hunch, remove the nvidia modules from the initramfs (or remove the kms hook and add amdgpu explicitly)
Offline
So with linux-lts switching to 6.6 i found myself unable to boot today.
Newer live-systems had the same issue but showed a more verbose error log on startup:
https://imgur.com/F7QSIiq
used an old live-image from ~1 year ago, downgraded linux-lts to 6.1 and linux too.
after downgrading to kernel 6.5.9-arch2-1 it boots fine.
Last edited by wannabee (2024-01-12 14:15:20)
Offline
Why are you using nouveau with a 3060?
Online
The RIP is from nouveau but not necessarily fatal.
Step one would be to install the proprietary nvidia drivers, you've an Ampere chip and can expect them to perform abysmally better.
Edit: ninja'd
Last edited by seth (2024-01-12 14:20:57)
Offline
It's a laptop with an AMDcpu and a Nvidia 3060 dedicated card.
The log provided is from the live image. In the installed system i have nvidia installed and modules loaded in the initcpio...
Offline
Can you still boot the multi-user.target, 2nd link below (in doubt along "nomodeset")?
Offline
Can you still boot the multi-user.target, 2nd link below (in doubt along "nomodeset")?
No, i tried that already an 23.12.:
changing the boot target does not change anything. I think it halts long before, that's why i dont even see logs in journalctl
also i think the live-system does not boot to a graphical target?
Offline
What kernel version is the live media using?
Offline
What kernel version is the live media using?
these are the live images:
6.2.1-arch1-1 -> works
6.6.3-arch1-1 -> doesn't work, kernel version verified with another computer
i tried these kernels on my installed system:
6.5.9.arch2 -> works
6.6.arch1 -> blank screen
6.6.1.arch1 -> blank screen
...
The nullref in nouveau also happens in the 6.2.1 live-image but it continues after that.
I don't see it in the boot-logs of my main system.
[18:03 simon@simonlaptop ~ :)] journalctl -b | grep nouveau
Jan 12 17:58:29 simonlaptop /usr/lib/gdm-x-session[1700]: (==) Matched nouveau as autoconfigured driver 1
Jan 12 17:58:29 simonlaptop /usr/lib/gdm-x-session[1700]: (II) LoadModule: "nouveau"
Jan 12 17:58:29 simonlaptop /usr/lib/gdm-x-session[1700]: (WW) Warning, couldn't open module nouveau
Jan 12 17:58:29 simonlaptop /usr/lib/gdm-x-session[1700]: (EE) Failed to load module "nouveau" (module does not exist, 0)
Jan 12 17:58:36 simonlaptop /usr/lib/gdm-x-session[2413]: (==) Matched nouveau as autoconfigured driver 1
Jan 12 17:58:36 simonlaptop /usr/lib/gdm-x-session[2413]: (II) LoadModule: "nouveau"
Jan 12 17:58:36 simonlaptop /usr/lib/gdm-x-session[2413]: (WW) Warning, couldn't open module nouveau
Jan 12 17:58:36 simonlaptop /usr/lib/gdm-x-session[2413]: (EE) Failed to load module "nouveau" (module does not exist, 0)
probably because it's not installed
Last edited by wannabee (2024-01-12 17:06:01)
Offline
So nouveau is a red herring.
Nevertheless, if you enable sshd, can you ssh into the system when booting 6.6?
Does it work if you add "module_blacklist=asus_wmi,asus_nb_wmi"?
Edit: and disable the asusd (this is all b/c of the last line in your screenshot)
Last edited by seth (2024-01-12 22:35:27)
Offline
Might also be useful to see if the issue is still present in 6.7.arch2-1 in core-testing.
Offline
Might also be useful to see if the issue is still present in 6.7.arch2-1 in core-testing.
thanks for the idea!
It does boot with 6.7! yay
[11:27 simon@simonlaptop ~ ] uname -r
6.7.0-arch2-1
so i guess i will stay with 6.1-lts until 6.7 arrives...
Offline
Pages: 1