Bug 9223 - The name of the module generated conflicts with x11 auto configuration
Summary: The name of the module generated conflicts with x11 auto configuration
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker major
Target Milestone: Mageia 3
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2013-03-01 14:37 CET by Alejandro Vargas
Modified: 2013-03-01 20:16 CET (History)
2 users (show)

See Also:
Source RPM: vidia304-304.64-4.mga3.nonfree.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Alejandro Vargas 2013-03-01 14:37:47 CET 
Description of problem:

Can't use nvidia propietary driver in X11. The module is loaded but some program thinks it isn't and swithcs to nouveau.

How reproducible:

Just install Mageia 3 (cauldron) with a nvidia card.

Solution:

# cd /lib/modules/3.8.0-desktop-3.mga3/dkms-binary/drivers/char/drm
# ln -s nvidia304.ko.xz nvidia.ko.xz
# depmod -a

This gets it working but a kernel update will brake X11 again. 




Reproducible: 

Steps to Reproduce:
Alejandro Vargas 2013-03-01 14:39:45 CET

Priority: Normal => release_blocker

Alejandro Vargas 2013-03-01 14:39:57 CET

Target Milestone: --- => Mageia 3

Alejandro Vargas 2013-03-01 14:42:52 CET

Keywords: (none) => PATCH

Sander Lepik 2013-03-01 14:49:55 CET

CC: (none) => sander.lepik, thierry.vignaud
Assignee: bugsquad => tmb

Comment 1 Thomas Backlund 2013-03-01 15:57:15 CET 
Nope, the nvidia modules are ok, something else is broken in your setup as noted in #9216

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

Comment 2 Alejandro Vargas 2013-03-01 17:24:06 CET 
My setup is a completely clean, fresh ans updated mageia 3. Just install, boot the system and the problem is there.

Status: RESOLVED => REOPENED
Resolution: INVALID => (none)

Comment 3 Thomas Backlund 2013-03-01 20:16:49 CET 
it has _nothing_ to do with the naming of the nvidia modules.

Status: REOPENED => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.