Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#61230 - [linux]Nouveau driver stop working with Linux 4.20

Attached to Project: Arch Linux
Opened by Obs (obspm) - Tuesday, 01 January 2019, 13:59 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 12:51 GMT
Task Type Bug Report
Category Kernel
Status Assigned
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

Description:

After upgrade to linux 4.20 my Xorg session does not start, or to be more precise it's start bug almost no image on the screen. Just some random color.
I'm not sure if it's related to the https://bugs.archlinux.org/task/61216 or not.

What I'm sure is after downgrade to linux 4.19-12 everything work fine.

I'm not sure if the problem is with xf86-video-nouveau, I just notice no upgrade of xf86-video-nouveau after upgrade to 4.20

Additional info:
* package version(s)
xf86-video-nouveau : 1.0.15-3
* config and/or log files etc.


Steps to reproduce:

After upgrade the kernel, no X11 (launch by gdm)

This task depends upon

Comment by Obs (obspm) - Tuesday, 01 January 2019, 17:22 GMT
Forget to say the GPU is a old Nvidia Quadro 2000
Comment by loqs (loqs) - Tuesday, 01 January 2019, 20:28 GMT
Please post the Xorg.log from before and after the upgrade (as gdm is launching X it will be in the system journal)
Is modesetting also affected?
Comment by Vinux (vinux) - Tuesday, 01 January 2019, 21:26 GMT
Same problem for me.
Note that I was able to get Xorg session working by appending 'single' to grub kernel command line and then as root restoring default: systemctl default
Comment by Олег (Xpom8) - Wednesday, 02 January 2019, 09:09 GMT
With proprietary the same story? If not, then it is worth trying to install proprietary, it can help.
sudo pacman -Syy
sudo pacman -S nvidia
reboot
Comment by Obs (obspm) - Wednesday, 02 January 2019, 09:30 GMT
Well It's weirder than I imagine.

Yesterday after you request the Xorg.log, because I want to able to have a session, I disable gdm (systemctl disable gdm), I make the upgrade and reboot.

After the reboot I log in the console and launch a systemctl start gdm...and it's works. So I re-enable gdm and reboot, and...it still working.

This morning I start the PC and...nothing work same problem as at the beginning, just some unstable weird colors on the screen (still on automatic launch gdm), I get the /var/log/Xorg.log.0 and disable the gdm at start and reboot. Launch gdm with systemctl and...it's working....

Regards
   Xorg.0.log (66.1 KiB)
Comment by Vinux (vinux) - Wednesday, 02 January 2019, 09:37 GMT
Here are the 2 logs.
Working use 'single' in kernel command line, and then I'm returning to normal mode using 'systemctl default': Display is then working nicely.
Failing use the default command line, and display is vertically misaligned.

Not so much difference in the logs from my point of view. Working goes a bit further in modeset step.

I will try the nvidia driver. Thanks for your support!
   Xorg.0.log.working (43.8 KiB)
   Xorg.0.log.failing (42.5 KiB)
Comment by Vinux (vinux) - Wednesday, 02 January 2019, 11:26 GMT
Installing nvidia-340xx worked around the problem for me (Nvidia GT218).
Thanks
Comment by Vinux (vinux) - Wednesday, 02 January 2019, 13:44 GMT
Comment by Paul Hentschel (hpmachining) - Friday, 04 January 2019, 22:11 GMT
I have this same issue in Arch linux with gdm service enabled. I get to the login screen, but after entering password system hangs. I can switch to TTY but it is very slow in responding. If I disable gdm and login to terminal and start gdm manually, gnome starts fine. Downgrading to linux 4.19.12 also fixes it. In case it matters, I am not using Wayland. I have attached a journalctl log from boot with gdm enabled and 4.20 kernel. I also attached the results of lspci -vnn and lsmod (after downgrading to 4.19.12). My processor is Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz. Let me know if there is anything else I can provide.

**EDIT**
Blacklisting nouveau or installing nvidia package works around the issue. I did not have to blacklist nouveau with kernel 4.19
   journalctl.log (330 KiB)
   lspci.log (11.7 KiB)
   lsmod.log (6.4 KiB)
Comment by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 12:50 GMT
Is this still an issue?

Loading...