Few glitches with 8178 on FC5 Test2

[sambo57u]

I just installed the new nvidia drivers + patch on my EM64T system
running Fedora Core 5 Test2. I can report two problems I encountered:

1. I used "nvidia-installer" from the extracted package to do the installation
and for some reason the ncurses screens were completely garbled and
fonts had no spaces between words. I managed to get through by
bliindly choosing yes and hitting enter.

2. After the install I noticed that the libXvMCNVIDIA libraries were under
/usr/X11R6/lib64 directory. This should be under /usr/lib64 for modular X.
Everything else was installed under /usr/lib64 or /usr/lib.

Thanks

[netllama]

Both of these issues are known bugs.

The first issue is bug 207742.
The 2nd issue is bug 198751.

Thanks,
Lonni

[nagini]

Those 'issues' are pretty easy to work around for now. I did this after patching:

./nvidia-installer -n --ui=none --x-prefix=/usr/lib64 --x-module-path=/usr/lib64/xorg/modules

This appears to put things where they belong (nvidia confirm this please?)

However, I get the following failure when trying to start X

dlopen: /usr/lib64/xorg/modules/extensions/libglx.so: cannot enable executable stack as shared object requires: Permission denied
(EE) Failed to load /usr/lib64/xorg/modules/extensions/libglx.so
(EE) Failed to load module "glx" (loader failed, 7)
dlopen: /usr/lib64/xorg/modules/drivers/nvidia_drv.so.so: cannot enable executable stack as shared object requires: Permission denied
(EE) Failed to load /usr/lib64/xorg/modules/drivers/nvidia_drv.so
(EE) Failed to load module "nvidia" (loader failed, 7)
(EE) No drivers available

link issue? SELinux issue?

Should this be submitted as a bug?

[netllama]

Yes, that's an SELinux issue. You can work around it by running "setenforce 0" as root before installing the driver, and then "setenforce 1" afterwards.

Thanks,
Lonni

[nagini]

Hmm, definitely SElinux.

setenforce 0 and install as above.

startx works

setenforce 1 followed by startx does not - same error as before.

[netllama]

Yes, I'm seeing the same problem now. It looks like SELinux needs to be disabled for X to start. I've opened bug 207999 for this issue.

Thanks,
Lonni

[nagini]

Is there a place for me to track this on your bug system or is that internal to nvidia? If it's internal would you mind posting back here after you guys have a chance to look at this?

Thanks

[netllama]

The bug tracking system is not publicly acessible. You're welcome to post here or email linux-bugs@nvidia.com if you'd like a status update on this bug.

Thanks,
Lonni

[drluiscuellar]

I am posting this message mostly for my own "future reference".

I have had this problem twice, and thanks to the clues above, I was able to fix my problem.

My solution: create symbolic links for the drivers from /usr/X11R6/lib64/modules/drivers/ to /usr/lib64/xorg/modules/drivers

Voilà!

To compiled the driver, I had to install the "kernel-devel" and be sure that the NVIDIA "package...run" could find them. Obviously, a "bug" in the building of the driver utility.

Now for the dual-heads...

edit the /etc/X11/xorg.conf file to load the correct driver for the second screen (the gtk-util added "nv" for some reason)..
(pirate) http://www.nvnews.net/vbulletin/imag...es/pirate1.gif
(pirate)

[netllama]

Creating symlinks is unneccesary, and are not a result of any bugs. Please see:
http://www.nvnews.net/vbulletin/showthread.php?t=68681

Thanks,
Lonni