Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#44040 - [nvidia] [nvidia-340xx] [nvidia-304xx] Add a message after upgrading nvidia driver
Attached to Project:
Arch Linux
Opened by Jiulun Du (dujiulun2006) - Wednesday, 04 March 2015, 05:43 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 10 May 2015, 17:37 GMT
Opened by Jiulun Du (dujiulun2006) - Wednesday, 04 March 2015, 05:43 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 10 May 2015, 17:37 GMT
|
DetailsDescription:
After user upgrades nvidia driver, a message should be displayed (with .install file - post_upgrade) to tell user to reboot or at least remove+modprobe kernel module. Otherwise some apps (like Qt Creator) may silently break. After a upgrade of nvidia driver from 346.35 to 346.47, Qt Creator won't open (it hangs a while and quits silently; if started from console, it gives "core dump"). It took me a while to find out about why. Additional info: * package version(s) nvidia - 346.47-3, qtcreator - 3.3.1-1 * config and/or log files etc. 3月 04 13:26:15 xiaodulabpc gdm-Xorg-:0[343]: (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display 3月 04 13:26:15 xiaodulabpc gdm-Xorg-:0[343]: (**) NVIDIA(0): device HP 23fi (DFP-0) (Using EDID frequencies has been 3月 04 13:26:15 xiaodulabpc gdm-Xorg-:0[343]: (**) NVIDIA(0): enabled on all display devices.) 3月 04 13:26:15 xiaodulabpc gdm-Xorg-:0[343]: (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display 3月 04 13:26:15 xiaodulabpc gdm-Xorg-:0[343]: (**) NVIDIA(0): device HP 23fi (DFP-0) (Using EDID frequencies has been 3月 04 13:26:15 xiaodulabpc gdm-Xorg-:0[343]: (**) NVIDIA(0): enabled on all display devices.) 3月 04 13:26:15 xiaodulabpc kernel: NVRM: API mismatch: the client has the version 346.47, but NVRM: this kernel module has the version 346.35. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. 3月 04 13:26:15 xiaodulabpc kernel: NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22 3月 04 13:26:15 xiaodulabpc kernel: NVRM: API mismatch: the client has the version 346.47, but NVRM: this kernel module has the version 346.35. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. 3月 04 13:26:15 xiaodulabpc kernel: NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22 3月 04 13:26:15 xiaodulabpc kernel: QSGRenderThread[8369]: segfault at 30 ip 00007f63e5e07c98 sp 00007f62df2c4988 error 4 in libc-2.21.so[7f63e5cce000+199000] 3月 04 13:26:21 xiaodulabpc systemd-coredump[8370]: Coredump of 8343 (qtcreator-bin) is larger than configured processing limit, refusing. 3月 04 13:26:22 xiaodulabpc systemd-coredump[8370]: Process 8343 (qtcreator-bin) of user 1000 dumped core. Steps to reproduce: 1. Install nvidia 346.35 & qt creator. 2. Make sure 346.35 kernel module is loaded. 3. Upgrade nvidia to 346.47. 4. Start qt creator. It won't start. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Sunday, 10 May 2015, 17:37 GMT
Reason for closing: Implemented
Sunday, 10 May 2015, 17:37 GMT
Reason for closing: Implemented
What's next, add such messages to firefox because it could be running during an update?
In that case, no information in .install files has any value.
> Also, logfiles give enough information about what's wrong in this case.
Well... It does. I just think a message will make users' lives easier.
> What's next, add such messages to firefox because it could be running during an update?
Firefox is not to be compared with nvidia driver, because it won't break a lot of other applications. In my case, (and after digging back a year's log through journalctl,) quite many other apps were broken by previous nvidia updates without rebooting.
Since there is no mechanism for automatically reloading updated modules, and there are not so many drivers that contains such "powerful" kernel modules, I think adding one when we spot one is an acceptable solution.