-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
screen frozen linux6.6 and 6.7 #48473
Comments
What troubleshooting steps have you taken? From the description, it sounds like you're using What happens if you boot with |
The problem happens both when nouveau is installed or not installed. I tried blacklisting nouveau in /etc/modprobe.d/blacklist.conf I tried booting with nomodset=1 with nouveau both installed and uninstalled |
nouveau can't be not installed, it's a kernel module |
I mean xf86-video-nouveau, I just shortened it to nouveau |
I experienced this issue on my Core 2 Duo machine with no GPU on linux6.6.11 as well |
I had this problem a month-ish ago and it was due to I was able to solve this by booting from the latest ISO, installing the system from local packages, blacklisting |
I'm having a similar -- if not the same -- issue on my install as well. This issue does not occur on Kernels 6.5.5_2, 6.5.12_1, and 6.1.29_1. It does occur on the 6.6.8, 6.6.11, and 6.6.16. At least from my testing. doing My system information is as follows:
I included the CPU as it does not include integrated graphics, IIRC. Using the Proprietary Nvidia drivers does work, but I ran into the issue because sway won't start with them it seems, so I wanted to switch to the Nouveau ones to try out sway. |
Hi guys, Experienced the same issue. I ran the live image, mounted my partitions and installed an older kernel series (6.5) Then ran
This solved the problem by chance. Maybe the kernel installation did some clever trick?! Anyway, void now also boots with new kernels; tested with |
I have the same issue when installing/running Void, so I'm stuck on the 6.5.13 kernel for now (NVIDIA GTX 1060 3G). I did manage to login to the "frozen" machine via ssh and take a look at the log. I'll post the trace below from booting the 6.8.1 kernel, I get the same error from the 6.6.22 kernel:
Perhaps someone else can confirm the same error on their machine, it seems to be something related to firmware loading? |
@thomasxg I no longer have it but when I faced this issue months ago it had a very similar trace to what you just posted. The issue is definitely GPU-related, and doesn't happen on proprietary drivers, only nouveau. With the release of the new live image on March 14 however the problem has become worse and could impact adoption. With the previous live image, you could boot into live Void without any issues, install the OS to disk using local packages, reboot then blacklist nouveau right before performing an update. That's what I did to get Void working on my Nvidia machine (2080 Ti). However, the new live image rolls in the regression, meaning you cannot even reach a terminal after GRUB without explicitly blacklisting the nouveau driver and modeset through kernel flags when launching the live image. I had to do this recently when I reinstalled Void, which is practically simple but difficult to figure out when you don't even have logs or any output telling you what's erroring. |
Had the same problem hanging at "loading initial ramdisk". My solution was to install the mainline kernel and the nvidia non-free driver. When I installed only the mainline the problem went down to nouveau, so the nvidia driver fixed it completely. |
Is this a new report?
Yes
System Info
Void 6.6.11_1 x86_64 musl
Package(s) Affected
linux6.6 linux6.7
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
I turn on my computer (alienware m15 r4 i7-10870H rtx3060)
void boots like normal
Actual behaviour
I am permanently stuck on this screen after grub.
Booting from 6.5.13 works normal.
Booting from 6.7.2 is broken.
Steps to reproduce
Install void using either chroot or void-installer (I did both)
sign in as root
xbps-install -Suy xbps
xbps-install -Suy
reboot
and I am now stuck. (Literally no other commands, just those)
The text was updated successfully, but these errors were encountered: