Bug 24794 - nvidia 418-74 + mageia prime = no graphical support
Summary: nvidia 418-74 + mageia prime = no graphical support
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-09 04:40 CEST by Adelson Oliveira
Modified: 2019-05-11 11:43 CEST (History)
7 users (show)

See Also:
Source RPM: nvidia 418-74
CVE:
Status comment:


Attachments

Description Adelson Oliveira 2019-05-09 04:40:46 CEST
After last update (nvidia drivers were updated to 418-74) I can no longer have graphical support in mageia 7 beta up to date.

The computer freezes. In recovery mode, startx returns errors and does not go.

I have mageia-prime set to install. This is a hybrid graphics laptop with integrated video card intel. However, I now have graphical support working only when I move /etc/X11/xorg.conf to /etc/X11/xorg.conf_old
Comment 1 Marja Van Waes 2019-05-09 09:45:58 CEST
(In reply to Adelson Oliveira from comment #0)
> After last update (nvidia drivers were updated to 418-74) I can no longer
> have graphical support in mageia 7 beta up to date.
> 
> The computer freezes. In recovery mode, startx returns errors and does not
> go.
> 
> I have mageia-prime set to install. This is a hybrid graphics laptop with
> integrated video card intel. However, I now have graphical support working
> only when I move /etc/X11/xorg.conf to /etc/X11/xorg.conf_old

Assigning to our kernel & drivers maintainers, CC'ing our mageia-prime and our x11-driver-video-* maintainers.

Assignee: bugsquad => kernel
CC: (none) => ghibomgx, marja11, thierry.vignaud

Comment 2 Kristoffer Grundström 2019-05-09 14:56:11 CEST
So it does not work if you boot the kernel with the flag nomodeset ?

CC: (none) => hamnisdude

Comment 3 Thomas Andrews 2019-05-09 18:12:14 CEST
Symptoms sound similar to what we nvidia340 users have been seeing since Cauldron moved to Kernel 5.1. 

Bug 24719.

CC: (none) => andrewsfarm

Comment 4 Thomas Backlund 2019-05-09 18:25:15 CEST
Nope, it means old nvidia module is in initrd causing a mismatch

If you re-create the initrd and reboot it will fix itself up.

I guess I need to add a call to always rebuild the initrd on driver update

CC: (none) => tmb

Comment 5 Thomas Backlund 2019-05-09 18:25:55 CEST
Oops, wrong bugreport
Comment 6 Adelson Oliveira 2019-05-09 20:38:37 CEST
I've not had access to the laptop yet. But everything was working fine till nvidia's drivers update to 418.74. I'm considering moving back to the last nvidia's driver to test. I'm using the latest mageia's kernel 5.1.
Comment 7 peter winterflood 2019-05-09 20:47:35 CEST
same here and after thomas's comment on qa, login to text console with control-alt-f2

mkinitrd /boot/initrd-`uname -r`.img

reboot

the clue is in the following messages in the kernel log  (/var/log/kernel/warnings.log)

May  9 15:38:03 host kernel: [   17.245695] NVRM: API mismatch: the client has the version 418.74, but
May  9 15:38:03 host kernel: [   17.245695] NVRM: this kernel module has the version 418.56.  Please
May  9 15:38:03 host kernel: [   17.245695] NVRM: make sure that this kernel module and all NVIDIA driver
May  9 15:38:03 host kernel: [   17.245695] NVRM: components have the same version.

thomas suggested : I guess I need to add a call to always rebuild the initrd on driver update


regards peter

CC: (none) => peter.winterflood

Comment 8 Adelson Oliveira 2019-05-10 02:18:18 CEST
"... So it does not work if you boot the kernel with the flag nomodeset ? ..."

I have commands to blacklist nouveau in the linux line. The flag nomodeset does not help no matter if I set it before or after blacklisting nouveau in the linux line
Comment 9 Adelson Oliveira 2019-05-10 03:07:10 CEST
Updating this bug, mageia-prime-uninstall also allows for graphical support upon rebooting.
Comment 10 Adelson Oliveira 2019-05-11 02:32:21 CEST
New kernel 5.1.0-desktop-2.mga7 solved the problem.

I suggest to close this bug.
Comment 11 Thomas Backlund 2019-05-11 11:43:09 CEST
Closing

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.