Bug 607701

Created attachment 426616 [details]
The X configuration file

The xconf file I am using

Additionally, the output of dmesg does not show anything indicative (to me at least) but, the bits that talk about NVIDIA are as follows:


nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
nvidia 0000:01:00.0: enabling device (0002 -> 0003)
nvidia 0000:01:00.0: PCI INT A -> GSI 48 (level, low) -> IRQ 48
nvidia 0000:01:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
nvidia 0000:02:00.0: enabling device (0002 -> 0003)
nvidia 0000:02:00.0: PCI INT A -> GSI 52 (level, low) -> IRQ 52
nvidia 0000:02:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=none
nvidia 0000:08:00.0: PCI INT A -> GSI 30 (level, low) -> IRQ 30
nvidia 0000:08:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:08:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86_64 Kernel Module  256.35  Wed Jun 16 18:42:44 PDT 2010
type=1400 audit(1277364628.694:5): avc:  denied  { mmap_zero } for  pid=827 comm="vbetool" scontext=system_u:system_r:vbetool_t:s0-s0:c0.c1023 tcontext=system_u:system_r:vbetool_t:s0-s0:c0.c1023 tclass=memprotect
type=1400 audit(1277364628.694:4): avc:  denied  { mmap_zero } for  pid=853 comm="vbetool" scontext=system_u:system_r:vbetool_t:s0-s0:c0.c1023 tcontext=system_u:system_r:vbetool_t:s0-s0:c0.c1023 tclass=memprotect
type=1400 audit(1277364628.694:6): avc:  denied  { mmap_zero } for  pid=828 comm="vbetool" scontext=system_u:system_r:vbetool_t:s0-s0:c0.c1023 tcontext=system_u:system_r:vbetool_t:s0-s0:c0.c1023 tclass=memprotect

Thanks for the report. We are sorry that we cannot help you with your problem, but we are not able to support binary-only drivers. If you would be able to reproduce this issue using only open source software, please, reopen this bug with the additional information, but in meantime I have no choice than to close this bug as CANTFIX (because we really cannot fix it).

The open source 'nouveau' driver (in package xorg-x11-drv-nouveau) is the recommended alternative for users of Nvidia graphic chips.  It is used by default in Fedora 11 and later if you remove any customizations that explicitly set the video driver.  The older "nv" driver may be needed in some cases.  It is also available in older Fedora releases.  Install the packages xorg-x11-drv-nouveau or xorg-x11-drv-nv and override the X server's default choice if necessary.  See https://fedoraproject.org/wiki/Features/NouveauAsDefault for more information.

If you used a non-packaged version of the driver from the Nvidia website please clean your system from additional libraries and software it installed. For users who are experiencing problems installing, configuring, or using the unsupported 3rd party proprietary "nvidia" video driver, Nvidia provides indirect customer support via an online web based support forum.  Nvidia monitors these web forums for commonly reported problems and passes them on to Nvidia engineers for investigation.  Once they've isolated a particular problem, it is often fixed in a future video driver update.

The NVNews Nvidia Linux driver forum is located at:

	http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14

Once you have reported this issue in the Nvidia web forums, others who may have experienced the particular problem may be able to assist.  If there is a real bug occuring, Nvidia will be able to determine this, and will likely resolve the issue in a future driver update for the operating system releases that they officially support.

While we does not support the proprietary nvidia driver, users requiring technical support may also find the various X.Org, XFree86, and Red Hat/Fedora mailing lists helpful in finding assistance:

X.Org mailing lists:
	http://www.freedesktop.org/XOrg/XorgMailingLists

XFree86 mailing lists:
	http://www.xfree86.org/sos/lists.html

Red Hat/Fedora mailing lists:
	https://listman.redhat.com/mailman/listinfo

So I found out what the problem was. It was a manifestation of this issue:
http://bugs.freedesktop.org/show_bug.cgi?id=24986

updating to fedora 13 rawhide x11-server sort of fixed it. I say sort of because I am fighting more issues with instability and graphical artifacts. 

I honestly would use the nouveau driver if it worked properly on my setup.

(In reply to comment #4)
> I honestly would use the nouveau driver if it worked properly on my setup.    

There is no bad will on my part for you using the nvidia blob. I can understand that noveuau might have troubles to run configurations like yours (did you try?) but the point is that we really cannot help you.

Of course there is no bad will Matej, I develop open source software too. Mine is more along the lines of HPC computing though.

Anyways, yes I did try the nouveau drivers, the issue I get from them is a system freeze when the cursor crosses a screen. If you looked at the link I sent though, you will see the problem was not the nvidia driver, it was X11. The fix went in here:
http://lists.freedesktop.org/archives/xorg/2010-April/050031.html

So in case somebody gets this error among the dozen or or so multi-monitor users, the simplest fix is to upgrade X11 to rawhide X11.

Now I have to go back and fight with gpk-application. It does not ask me about the root password anymore but tells me authentication failed.

Thanks for looking at this though. It is nice to know somebody cares :)

(In reply to comment #7)
> Thanks for looking at this though. It is nice to know somebody cares :)    

It's my job to care ;)

Anyway, have you filed a bug on that issue in comment 6?

No not yet. I am trying to get more info and found a few related bugs that might resolve it. At least I'll have something to do over lunch.

Regards
Yaakoub

I found the original bug report of this bug but with different symptoms so I am marking this as duplicate of.

*** This bug has been marked as a duplicate of bug 567835 ***