| Summary: | Failed to initialize the GLX module | ||
|---|---|---|---|
| Product: | Fedora | Reporter: | Me <linuxguy123> |
| Component: | xorg-x11-drv-nvidia | Assignee: | Stewart Adam <s.adam> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | kwizart, michalng |
| Priority: | P5 | ||
| Version: | 10 | ||
| Hardware: | All | ||
| OS: | GNU/Linux | ||
| namespace: | |||
|
Description
Me
2008-11-28 17:35:39 CET
I first reported this bug on the Redhat bugzilla. https://bugzilla.redhat.com/show_bug.cgi?id=473329 There is more background information there if you need it. This xorg.conf doesn't look like our tweaked version
as it should be:
...
Section "Files"
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules"
EndSection
...
Tweaking the xorg.conf file as you suggested fixed the problem. a) How would a user know to use your tweaked version ? b) This xorg.conf file was created by the livna xorg config tool. It should create conf files that work, not ones that need to be debugged or hand edited. I suggest that this application be modified to reflect these needs. I suggest this bug be reopened and further action be taken. Thanks for your help. General comment: a lot of people seems to run into issues like this, hence we IMHO really need a FAQ that explains this and the reasons why we use a special extension dir. further: (In reply to comment #2) > This xorg.conf doesn't look like our tweaked version Well, it afaics was created with nvidia-xconfig, which is what a lot of howtos on the net suggest. If it creates configs that don't work with our packages then it either needs to be - fixed - not shipped at all - or wrapped by a script that adds a big fat warning "this tool will break your config" ======================================================== it either needs to be - fixed - not shipped at all - or wrapped by a script that adds a big fat warning "this tool will break your config" ======================================================= I am very happy to hear you say that. I spent (wasted?) about 3 hours messing around with this issue and I am not a Linux newbie. This is also the first time that I heard of a special xorg.conf file being needed for a certain nvidia driver. I am going to post a warning to the fedora-users list so that others are aware of this. Thanks for listening and helping me. I/we appreciate your efforts. As Thorsten mentioned, nvidia-xconfig is used in a lot of online tutorials so I don't think removing it would be a good idea but wrapping it is certainly possible. Just for some background info on the problem, the nVidia drivers that you obtain directly from nvidia.com will overwrite some of Xorg's libraries and this can cause some problems later. As a work-around, we package the drivers in a non-standard location and configure xorg.conf automatically, but if you modify xorg.conf of your own accord (say with nvidia-xconfig for example) then livna-config-display might bail out and stop making further changes since it assumes that the user is managing xorg.conf on their own. If you were following a guide that was specifically written for Fedora, you may wish to notify the author about this and perhaps include a link to this bug. New to Linux and first time Fedora user (gnome with nvidia)
Currently my xorg.conf file have a section
Section "Files"
FontPath "/usr/share/fonts/default/Type1"
EndSection
Does that means I've to over-ride this section with
Section "Files"
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules"
EndSection
or just add insert
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules"
into the section?
Googling shows that there are many user that's still in the dark on this bug.
Add these two lines to the existing section:
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules"
When you are done, it should look like this:
Section "Files"
FontPath "/usr/share/fonts/default/Type1"
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules"
EndSection
(In reply to comment #8) > Add these two lines to the existing section: > > ModulePath "/usr/lib/xorg/modules/extensions/nvidia" > ModulePath "/usr/lib/xorg/modules" You normally should never have to modify the xorg.conf manually -- the package do that automatically on install. If that doesn't happen due to some stupid bug or if the xorg.conf was overwritten just disable and enable the drivers properly again: nvidia-config-display disable nvidia-config-display enable That will do everything that is needed. > You normally should never have to modify the xorg.conf manually -- the package > do that automatically on install. If that doesn't happen due to some stupid bug > or if the xorg.conf was overwritten just disable and enable the drivers > properly again: > > nvidia-config-display disable > nvidia-config-display enable > > That will do everything that is needed. > Thanks to you and linuxguy123 for the clarification. Does that mean that whoever uses nvidia-settings and gets into this problem can just do a > nvidia-config-display disable > nvidia-config-display enable and the system will self cure and no need to manually edit xorg.conf? Or if I installed using > yum intall akmod-nvidia and didn't use nvidia-settings to over-ride the default settings, then everything should be fine? Both may not believe but I've spend the past 2 days googling for answers for this simple fix. Yup - The drivers autoconfigure your xorg.conf automatically. If you configured it manually, then the disable/enable sequence of commands will reapply the automatic configuration for you. I think this bug should be closed as INVALID as the doc is rather clear of how to proceed: http://rpmfusion.org/Howto/nVidia. (you need to reboot in order for the changes to take effect). Later nvidia tools improvement should handle better this kind of behaviour. (understand, when users deviate from our docs). |