Date: Fri, 17 Feb 2006 08:35:53 -0300 From: Alejandro Pulver <alejandro@varnet.biz> To: Alex Zbyslaw <xfb52@dial.pipex.com> Cc: freebsd-questions@freebsd.org Subject: Re: NVidia GeForce 6600 problems Message-ID: <20060217083553.377940db@phobos.mars.bsd> In-Reply-To: <20060215131241.6dc50af5@phobos.mars.bsd> References: <20060201150621.11234c17@phobos.mars.bsd> <20060201151953.2ef2f011@phobos.mars.bsd> <43E1F57A.80804@dial.pipex.com> <20060202113919.233c1adc@phobos.mars.bsd> <20060215131241.6dc50af5@phobos.mars.bsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 15 Feb 2006 13:12:41 -0300 Alejandro Pulver <alejandro@varnet.biz> wrote: > On Thu, 2 Feb 2006 11:39:19 -0300 > Alejandro Pulver <alejandro@varnet.biz> wrote: > > > On Thu, 02 Feb 2006 12:05:14 +0000 > > Alex Zbyslaw <xfb52@dial.pipex.com> wrote: > > > > > Alejandro Pulver wrote: > > > > > > >On Wed, 1 Feb 2006 15:06:21 -0300 > > > >Alejandro Pulver <alejandro@varnet.biz> wrote: > > > > > > > > > > > > > > > >>Hello, > > > >> > > > >>I have recently bought a GeForce 6600 video card, and sometimes > > > >>(not very often) I experience the following problem: > > > >> > > > >>A little after starting X11 (for example when I start > > > >>downloading e-mails), the screen freezes a few seconds, after > > > >>that the screen looks like if widgets (buttons, text, etc.) > > > >>aren't drawn, and the white background of Sylpheed-Claws covers > > > >>the screen. Then I am forced to switch to the 1st console > > > >>(Ctrl+Alt+F1), which takes around 30 seconds, and then kill X11. > > > >> > > > >>I have FreeBSD 5.4 release, Xorg 6.8.2 and nvidia-driver > > > >>1.0.8178. > > > >> > > > >> > > > I have a 6600 with FreeBSD 5.4 XOrg 6.8.2 but still > > > nvidia-driver-1.0.7676_1. I have an occasional problem where the > > > whole screen is shifted left on startup, but exiting and > > > restarting X fixes it. You could try downgrading to an older > > > nvidia-driver and see if it helps. Portdowngrade should do that, > > > but I've never used it myself. > > > > > > You may have more luck if you try the nvidia support forum. > > > Definitely slower than this mailing list but someone from nvidia > > > was reading it, last time I used it. > > > > > > http://www.nvnews.net/vbulletin/forumdisplay.php?f=47 > > > > > > --Alex > > > > > > > Hello, > > > > Thank you for your reply. > > > > I have recently (started yesterday, and finishing yoday) upgraded my > > ports (including Xorg -> 6.9). If the problems persist I will try > > the old dirver and post information about the error in the NVidia > > forums. > > > > Best Regards, > > Ale > > Hello again, > > I have discovered the problem: the lock of the AGP slot wasn't on > (when I changed the video card I forgot the lock isn't automatic as > the one in the memory slots). > > I noticed this when the card was disconnected completely (it has a > cooler, so I guess the vibration did it). Once I rebooted and the > screen was black (the integrated video card was used instead of the > NVidia). Other time I saw the kernel message indicating the card was > detached and instantly detected again. > > Best Regards, > Ale Well, that was part of the problem, but I still have errors with one OpenGL application (I have tested others like Doom III and Enemy Territory and didn't cause this): a Quake II engine called QuDos. Sometimes I get the following: Program output (QuDos): Received signal 11, exiting... X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 135 (XFree86-VidModeExtension) Minor opcode of failed request: 10 (XF86VidModeSwitchToMode) Value in failed request: 0x1200002 Serial number of failed request: 35768 Current serial number in output stream: 35771 NVidia kernel module output: NVRM: Xid: 8, Channel 00000002 NVRM: Xid: 27, L1 -> L0 Best Regards, Ale
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060217083553.377940db>