nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Black Window Bug (Solutions and the way Nvidia is handling it) (http://www.nvnews.net/vbulletin/showthread.php?t=92622)

LostinSpacetime 06-03-07 05:11 AM

Black Window Bug (Solutions and the way Nvidia is handling it)
 
As the original "beryl black window bug" thread was closed http://www.nvnews.net/vbulletin/show...=84562&page=25 I thought that it would be a good idea to start a new one with a more clear formulated title. The thread helped me a lot configuring Beryl to be able to use it constructively and I believe I'm not the only one. Also for such a big bug it has to be some place where the Nvidia developers can post the status of their progress, because A LOT OF PEOPLE WHOULD LIKE TO KNOW!!!! So please start posting.

LubosD 06-03-07 09:41 AM

Re: Black Window Bug (Solutions and the way Nvidia is handling it)
 
Progress? It's done when it's done...

Opening new threads won't make them fix it faster.

netllama 06-03-07 11:17 AM

Re: Black Window Bug (Solutions and the way Nvidia is handling it)
 
NVIDIA hopes to have this bug resolved in the driver within the next few months.

LostinSpacetime 06-03-07 11:21 AM

Re: Black Window Bug (Solutions and the way Nvidia is handling it)
 
Well, since I payed for the hardware I would like Nvidia to know, that it's important for me to know if/when this bug will be solved and I think I'm not the only one. If it wont happen in the next year, I'm fine with it. I just would like to have some info. On the other hand, where when not here, can people talk about solutions and workarounds of this problem. In the original thread djdoo, Jupiter1tx and other users put a nice setup together, which made it possible for some people to use Beryl without the effects of this bug. Testing and improving of the setup was in progress and by closing the thread this progress might stop. I just don't want this. That's why I opened this thread.

LostinSpacetime 06-03-07 11:22 AM

Re: Black Window Bug (Solutions and the way Nvidia is handling it)
 
ok.. thanks :)

LostinSpacetime 06-03-07 11:31 AM

Re: Black Window Bug (Solutions and the way Nvidia is handling it)
 
hi netIIama.. I have a question. One of the "known issues" of the 100.14.06 (beta) driver is "Kernel virtual address space exhaustion on the X86 platform". Is this the bug we are talking about here, or is it a different one?

netllama 06-03-07 11:34 AM

Re: Black Window Bug (Solutions and the way Nvidia is handling it)
 
I'm not aware of any driver bugs which result in kernel virtual address space exhaustion. Perhaps you're thinking of the limitation on the kernel's default virtual address space (which is not a driver bug, and is fully documented in the driver README)?

LostinSpacetime 06-03-07 11:38 AM

Re: Black Window Bug (Solutions and the way Nvidia is handling it)
 
right..ok.. sorry, no bug :o I just wanted to know if the solutions described in the readme would help here. But since it's something different... thanks for answering

BrianzaMan 06-03-07 01:03 PM

Re: Black Window Bug (Solutions and the way Nvidia is handling it)
 
Excuse me guys, there is an OFFICIAL workaround for this bug in the meantime?

Thanks

Marcello

LostinSpacetime 06-04-07 03:36 AM

Re: Black Window Bug (Solutions and the way Nvidia is handling it)
 
The official workaround is not to use the composite extension at all.

The unofficial workaround (for Beryl) is this:

Quote:

Originally posted by djdoo

So to make a resume after your really valuable feedback kriko and all of you guys:
The suggestion finally is:

With driver 9755 and older or 9631 legacy(no info about 7185)or betas 100(03,06) under hood...

First in your xorg.conf you should have the following options in order to run beryl best:
Under "ServerLayout" section:

Option "AIGLX" "true"->(Maybe it does nothing but give it a try! If you don't notice any difference remove it! )

Under "Screen" section:

Option "NvAGP" "0" -> (terryxela's suggestion FOR PCI Express CARDS ONLY!!!!)
Option "AddARGBGLXVisuals" "True" ->(For betas 100 drivers this one is not necessary)
Option "DamageEvents" "True" ->(Jupiter1tx suggestion really helps a lot!!)
Option "TripleBuffer" "True"
Option "BackingStore" "True" ->See NOTE below...

NOTE: Use BackingStore option with CAUTION it may NOT work on all systems especially 6 series Geforce cards!!! (freezes when load beryl-manager as kriko said and other strange stuff, too low performance) but give it a try cause it helps performance when works properly otherwise PLEASE REMOVE IT!! If you get any kind of strange stuff with the settings remove this option and try again!!

Under "Extensions" section:

Option "DAMAGE" "Enable"
Option "Composite" "Enable"
Option "RENDER" "Enable"

See my xorg.conf too!!

If you have an AGP card add the following options in your modprobe.conf.local or any name this file has in your distro:

options nvidia NVreg_EnableAGPSBA=1 NVreg_EnableAGPFW=1 NVreg_EnableBrightnessControl=1 NVreg_DevicesConnected=1 NVreg_VbiosFromROM=1 NVreg_SaveVBios=1 NVreg_SoftEDIDs=0 NVreg_VideoMemoryTypeOverride=0 NVreg_NvAGP=3 NVreg_ReqAGPRate=8->(8=for 8X AGP, 4=for 4X AGP)

Also try to use kernel's agpgart module(NvAGP=2 or 3) instead of internal nvidia agp if possible.

If you have a PCI express card here are the options for you:

options nvidia NVreg_VideoMemoryTypeOverride=0 NVreg_NvAGP=0 NVreg_ReqAGPRate=0 NVreg_SoftEDIDs=0 NVreg_DevicesConnected=1 NVreg_VbiosFromROM=1 NVreg_SaveVBios=1 NVreg_EnableBrightnessControl=1

Second after rebooting or just logout->login(to reload the driver):
In Beryl's Advanced Options use the following setup:

"Texture from Pixmap" "Don't Use COW or Automatic" "force AIGLX" "XGL binding" "Indirect rendering or Automatic"

DON'T STOP HERE CONTINUE READING!!

IMPORTANT NOTE!:
For beta 100 drivers if you upgrade to one of them and have beryl-manager settings pre-setted from the previous driver as mentioned above you may face the bug!!
SOLUTION:
Just switch from "force AIGLX"(all the others leave them as above) to "force Nvidia" and then back to "force AIGLX" and everything would be as with 9755 driver.


MORE IMPORTANT NOTE!!!!:
If you are using KDE and have beryl starting automatically with the 2 links(the first straight to beryl and the second to beryl-manager at /home/****/.kde/Autostart/ folder) do the following:

PLEASE REMOVE THE ONE WHICH SHOWS STRAIGHT TO BERYL AND LEAVE THE ONE THAT LINKS TO BERYL-MANAGER!!! Cause if beryl.bin is loaded first you WILL face the bug cause it autodetects nVidia mode NOT AIGLX!!! and so it does not load our settings!! Beryl-manager is enough to load beryl automatically and with our settings on!!


ANOTHER IMPORTANT NOTE!!: (kriko's founding)
Custom kernels maybe can cause serious problems to beryl!!! Lagging, too slow or even freezes!! Be careful with those stuff for more info look here:
http://lkml.org/lkml/2007/3/9/74

jdeslip 06-04-07 07:24 PM

Re: Black Window Bug (Solutions and the way Nvidia is handling it)
 
Thanks netlama. I really appreciate hearing an estimate - even an order of magnitude one. I look forward to the fixed driver!

-Jack

Jupiter1tx 06-04-07 08:31 PM

Re: Black Window Bug (Solutions and the way Nvidia is handling it)
 
WOW
It's amazing that some people who actually were very helpful to
the community with a work around for this bug, are banned. Yet
some who offer nothing but snarky remarks are left to continue
making snarky remarks rather than help.

THANKS FOR YOUR CONTRIBUTION LubosD.

P.S. thank you netllama for that nugget of information
that we have so desperately wanted to hear for so long.


All times are GMT -5. The time now is 08:45 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.