-
Notifications
You must be signed in to change notification settings - Fork 27
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
GNOME fails to start after installing NVIDIA proprietary driver #1274
Comments
What version of Clear Linux and what version of the NVIDIA driver? I noticed 430.x on the Clear Linux 5.3 kernel is not working. I haven't had a chance to see if this is a Clear Linux specific issue or an upstream issue. But a workaround is Interrupt the bootloader by holding |
Sorry, I should have specified the versions. This was with the 5.3 kernel and NVIDIA Driver 430.5. I just tried the 435.21 drivers today with 5.3 and had no issues installing or booting in to GNOME after first install. The system was stable until the first reboot. After reboot I was left with a flashing cursor and was no longer able to access terminal, system was unresponsive. Reverting to a 5.2.x kernel in the meantime. |
@gmatler did the combo kernel 5.2.x + NVIDIA 430.5 get you a successful boot? |
@mrkz rolling back to 31080 with a 5.2 kernel works for me. Anything newer does not. The driver appears to build and install ok and load ok:
The X.org log is pretty generic:
The only thing that sticks out to me from journalctl are these lines. On a successful start these do not appear:
|
Another data point: I rebuilt the 5.2.17-836 kernel and booted it on Clear Linux version 31230 and the nvidia driver started working again. This indicates to me the issue is indeed somewhere in the kernel, and not another gcc/gnome change. |
Another finding that can hopefully help root cause: changing kernel parameter EDIT: |
So you say it's a kernel bug? I mean, it's a coincidence GNOME was updated at the same time? |
@puneetse any updates on this? I literally can't use Clear Linux... |
@SPAstef Sorry I don't have much of an update, but try the work around I posted above. It should at least unblock you. You can hold One more thing I was able to test: the "mainline" kernel package also has the issue, which tells me it's probably not one of the Clear Linux kernel patches causing this. Maybe it's a conflicting config or upstream bug (but I'd expect more noise if it was) |
Ok, didnt know that space interrupt thing. I have it in dual boot with Windows, hope it will work anyway. What would be the problem into shipping the kernel with that parameter you told me already set? |
Likely an issue between nvidia driver and the specific kernel version. Changing the kernel command line in this case is a negative impact for other uses though so we wouldn't be likely to make it default. |
Thanks. Another issue that I have only since latest version of GNOME: Xorg session doesent recognize external monitor (attached to GPU via Displayport), while Wayland does. (This happens with Nouveau drivers). Should I open a new issue for this? EDIT: anyway it did kinda work... While I was writing this message saying it didn't, it actually did. Took it 5 minutes to show GDM but in the end it did it... |
With the latest version it seems that even setting the intel_iommu option doesent work anymore |
@SPAstef It's still working for me on 31380 . Check
@bryteise while that is a recurring cat-and-mouse game, I don't think this particular issue is a generic NVIDIA vs Linux kernel problem. I would expect more noise from other distro users if that was the case and I tested a Fedora 30/31 system with NVIDIA drivers (5.3.6 kernel, GNOME 3.32/3.34, and with and without |
@puneetse now it works again, but the internal display isn't recognized (this might be related to the kernel option, since the internal display is connected to the Intel on-board GPU). Still hoping this will get fixed soon 😄 |
I have the same issue and it has been resolved at this time by removing I've had this issue since I installed Clear Linux last week but I was using the LTS kernel to get around the issue. This is the first time I'm seeing this so I catnt say if any changed or had an effect. |
For completely different reasons, I happened to disable Intel VT-d in the BIOS, and now everything seems to be working normally. I don't know if it is related to this... Or did you fix it silently? |
I wanted to just confirm that disabling Intel VT-d in BIOS resolved this issue for me. I had no graphical boot with the same generic failure message in my Xorg log. After disabling VT-d I booted into GDM / Gnome just fine. I did not change the |
I have this problem as well. Have followed all the steps here “Oh no! Something has gone wrong” error screen. |
My laptop doesn't either, you shouldn't need to disable it. Just follow the additional steps for Optimus laptops |
They've just been lazy writing that tutorial. Follow this: |
I found a solution. I installed sudo install lightdm and reconfigure sudo dpkg-reconfigure lightdm |
Didn't work for me for Wayland. |
The last two days I've attempted multiple (5+) times to install the latest NVIDIA proprietary driver and after installation GNOME fails to start - I'm left at a black screen with a flashing cursor. I'm able to access the system via SSH and terminal with CTRL+ALT+F2.
I've followed the tutorial here: https://docs.01.org/clearlinux/latest/tutorials/nvidia.html
My system information:
The text was updated successfully, but these errors were encountered: