FS#69800 - X11 fails to start after upgrade to 460.56-1 (NVidia Quadro K1200)

Attached to Project: Arch Linux
Opened by Christian Cwienk (dr1fter) - Friday, 26 February 2021, 17:02 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 26 February 2021, 19:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After upgrading to 460.56-1 (and rebooting), X11 failed to start (the intial error was failure of lightdm to start).

After downgrading to 460.39-8, it worked again.

Apart from this particular downgrade, all packages are in sync w/ stable


Additional info:
* package version(s)

460.56-1


* config and/or log files etc.

X-log:
```
5.781] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
5.781] (EE) NVIDIA: system's kernel log for additional error messages and
```

lspci:
```
07:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro K1200] (rev a2)
```

* link to upstream bug report, if any

Steps to reproduce:

- install nvidia 460.56-1
- reboot
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 26 February 2021, 19:20 GMT
Reason for closing:  Not a bug
Comment by Adler Jonas Gross (Betal) - Friday, 26 February 2021, 17:31 GMT
Are you running linux (5.11.1.arch1-1)?
Do it fail using linux-lts (5.10.18-1) and nvidia-lts (460.56-1) too?

With the given info it looks a partial upgrade, you say "upgrading" and "downgrading" only "nvidia" without mention "linux", but we have by [1]:
nvidia 460.39-8 for linux 5.10.16.arch1-1
nvidia 460.56-1 for linux 5.11.1.arch1-1

[1] https://github.com/archlinux/svntogit-packages/commits/packages/nvidia/trunk
Comment by Christian Cwienk (dr1fter) - Friday, 26 February 2021, 18:01 GMT
> Are you running linux (5.11.1.arch1-1)?
yes - I always keep all installed packages in sync w/ stable (pacman -Syu), no exceptions (until today)

> Do it fail using linux-lts (5.10.18-1) and nvidia-lts (460.56-1) too?
that I did not check. After downgrading packages nvidia (and nvidia-utils) it worked again, so I stopped further investigations.

> With the given info it looks a partial upgrade, you say "upgrading" and "downgrading" only "nvidia" without mention "linux", but we have by [1]:
to repair my machine, I looked into /var/cache/pacman/pkg, and looked for the greatest nvidia(-utils) packages before the broken one I received today. This happened to be 460.39-8.

with "upgrading to 460.56-1", I did not mean I upgraded this single package. It happened to be part of an update I received from my daily `pacman -Syu`. Sorry for the confusion.


Will try linux-lts
Comment by Doug Newgard (Scimmia) - Friday, 26 February 2021, 18:44 GMT
Are you loading the module in the initramfs? If so, did you rebuild it?
Comment by Christian Cwienk (dr1fter) - Friday, 26 February 2021, 19:00 GMT
> Are you loading the module in the initramfs? If so, did you rebuild it?

not sure. If this is not the "default" behaviour, probably now. I did not explicitly rebuild the initramfs, though. How can I check this?

For the past ~2y, I basically ran (almost) daily full system-upgrades w/o any issues, so I did not yet spend that much time with those details (for the initial installation, I mostly followed the recommendations from arch-wiki).
Comment by Doug Newgard (Scimmia) - Friday, 26 February 2021, 19:06 GMT
See /etc/mkinitcpio.conf. If you put any of the nvidia modules in the modules array, you have to regenerate the initramfs after nvidia updates. If there's a kernel update, this happens automatically. If there's not, you either have to do it manually or you have to set up your own hook.
Comment by Christian Cwienk (dr1fter) - Friday, 26 February 2021, 19:11 GMT
now I remember - I indeed _did_ put `MODULES=(nvidia nvidia_modeset nvidia_drm)` sometime back to fix a similar issue (maybe the same) :-(
will check / test right away. So probably, there is no issue w/ the package, but I forgot to add the initramfs-hook
Comment by Christian Cwienk (dr1fter) - Friday, 26 February 2021, 19:18 GMT
update: I just added an update-hook + updated again to latest nvidia-pkg (triggering the mkinitcpio-hook) + rebooted. Works w/o issues. So this bug could be closed. Thank you so much for your help!

Loading...