Bug 679227

Summary: Xorg does not prefer a module path set in xorg.conf.d/00-nvidia.conf
Product: [Fedora] Fedora Reporter: Gérard Milmeister <gemi>
Component: xorg-x11-serverAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: bpedman, mcepl, misek, skr, xgl-maint
Target Milestone: ---Keywords: Reopened, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 12:02:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ls conf files
none
xorg log with error
none
dmesg output
none
system messages none

Description Gérard Milmeister 2011-02-21 23:46:26 UTC
The RPMFusion nvidia package installs a configuration 00-nvidia.conf, which adds the module path /usr/lib64/xorg/modules/extensions/nvidia to search for the libglx.so module. In the recent version 1.9.4, the module is not loaded, unless I move the original (non-NVIDIA) libglx.so away. This behaviour seems to be new to 1.9.4, since previously it did work as expected.
The content of 00-nvidia.conf is:
Section "Files"
        ModulePath   "/usr/lib64/xorg/modules/extensions/nvidia"
        ModulePath   "/usr/lib64/xorg/modules"
EndSection

I tried to change the order, alas to no effect.

Comment 1 Matěj Cepl 2011-02-22 08:02:17 UTC
I am sorry but I have to close this bug as NOTABUG, i.e., this is not a bug in software provided by the Fedora project. rpmfusion was created specifically for things we cannot have anything to do with, so we cannot deal with configuration problems of nvidia binary driver. Please, file a bug in https://bugzilla.rpmfusion.org/ for your issue.

I am sorry I cannot help you more.

Comment 2 Gérard Milmeister 2011-02-22 17:49:34 UTC
(In reply to comment #1)
> I am sorry but I have to close this bug as NOTABUG, i.e., this is not a bug in
> software provided by the Fedora project. rpmfusion was created specifically for
> things we cannot have anything to do with, so we cannot deal with configuration
> problems of nvidia binary driver.
I think you are wrong. This is not about rpmfusion or nvidia, but about a configuration option the behaviour of which seems to have changed without notice. This may be a bug or not, in any case it is an issue.

Comment 3 Matěj Cepl 2011-02-24 15:07:25 UTC
(In reply to comment #2)
> (In reply to comment #1)
> I think you are wrong. This is not about rpmfusion or nvidia, but about a
> configuration option the behaviour of which seems to have changed without
> notice. This may be a bug or not, in any case it is an issue.

Yes, I am. I will investigate this bug further.

Comment 4 Matěj Cepl 2011-03-02 14:56:54 UTC
Isn't this just a problem of nvidia being blocked by nouveau kernel module? See whether instructions in http://www.giuseppecoviello.net/2010/02/using-nvidia-drivers-on-fedora-12-with-dkms/ would help you (of course, I suggest using packaged nvidia driver and some of the work with overcoming nouveau's defiance could be done for you).

Thank you for helping us to make Fedora better.

Comment 5 Gérard Milmeister 2011-03-02 16:40:58 UTC
I don't think so. I do use the packaged driver. Everything worked as it should until after the upgrade of the X server.

Comment 6 Matěj Cepl 2011-03-06 08:40:49 UTC
Passing the bug to developers, I cannot find much about order in which two modules of the same name are to be loaded. However, for further debugging of the problem, please attach the following log files

* output of ls -lR /etc/X11/*conf* and any files present in /etc/X11/xorg.conf.d/
* X server log file (/var/log/Xorg.*.log),
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

Thanks in advance.

Comment 7 Brandon 2012-03-28 17:56:06 UTC
Created attachment 573411 [details]
ls conf files

Comment 8 Brandon 2012-03-28 17:56:29 UTC
Created attachment 573412 [details]
xorg log with error

Comment 9 Brandon 2012-03-28 17:56:43 UTC
Created attachment 573413 [details]
dmesg output

Comment 10 Brandon 2012-03-28 17:56:56 UTC
Created attachment 573414 [details]
system messages

Comment 11 Brandon 2012-03-28 17:57:38 UTC
I am having the same issue, attached requested log files from comment #6

Comment 12 Fedora End Of Life 2012-08-16 12:02:12 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping