Bug 13617

Summary: nvidia driver is not usable with Card:NVIDIA GeForce 8100 to GeForce 360: NVIDIA Corporation|C77 [GeForce 8200] [DISPLAY_VGA] (rev: a2)
Product: Mageia Reporter: Thomas Spuhler <thomas>
Component: RPM PackagesAssignee: Thomas Backlund <tmb>
Status: RESOLVED OLD QA Contact:
Severity: critical    
Priority: Normal CC: tmb
Version: 4   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: x11-driver-video-nvidia-current-331.79-1.mga4.nonfree CVE:
Status comment:
Attachments: lspcidrake -v

Description Thomas Spuhler 2014-06-30 02:44:21 CEST
Description of problem:
When using the proprietary nvidia driver in mga4, the sceen gets a few flickers and then remains black. I had to change to the vesa driver or the nouveau driver

Version-Release number of selected component (if applicable):
331.79-1.mga4

How reproducible:
every time

Steps to Reproduce:
1. configure the box to use the propriatary nvidia driver 
2. restart the box
3. I get nothin but flicker after confirming the login (using KDE)

BTW, there wasn't any problem with mga3, may be an xorg problem


Reproducible: 

Steps to Reproduce:
Comment 1 Thomas Backlund 2014-06-30 10:22:06 CEST
Is it a system with oth intel and nVidia GPU ?

please attach output of lspcidrake -v

CC: (none) => tmb

Comment 2 Thomas Spuhler 2014-06-30 16:34:07 CEST
Created attachment 5223 [details]
lspcidrake -v
Comment 3 Thomas Spuhler 2015-01-10 19:47:49 CET
I tried again today. The display starts to flicker about 1 minute after the booting completes and doesn't take any inputs anymore from the keyboard. Need to do a power-off and use the nouveau driver.
Comment 4 Thomas Spuhler 2015-01-11 02:12:04 CET
There is quite a bit in the forums, archlinux, debian and 
MSI interrupts can be disabled via the NVIDIA kernel module parameter "NVreg_EnableMSI=0". This can be set on the command line when loading the module, or more appropriately via your distribution's kernel module configuration files (such as those under /etc/modprobe.d/).

But I cannot get this to work
Comment 5 Thomas Spuhler 2015-01-11 18:38:34 CET
Here is another post:
https://bbs.archlinux.org/viewtopic.php?id=168040

Assigning it to tmb (maybe wrong)

Assignee: bugsquad => tmb

Comment 6 claire robinson 2015-01-12 10:58:39 CET
Shouldn't GeForce 8200 be using nvidia304 ?
Comment 7 Samuel Verschelde 2015-09-21 13:19:04 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 8 Marja Van Waes 2015-10-27 06:56:31 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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