PDA

View Full Version : FreeBSD 6.1-STABLE & nvidia-driver: A couple of issues.


klr
09-02-06, 03:37 PM
Hi all,

I've been facing two annoying problems that regard the usage of nvidia-driver.

Before anything else, I'm using

nvidia0: <GeForce 7800 GT> port 0xe800-0xe87f mem 0xcf000000-0xcfffffff,0xd0000000-0xdfffffff,0xce000000-0xceffffff irq 16 at device 0.0 on pci4

The first problem is a very odd one. It is related to my Logitech G5 USB mouse. Prior to acquiring this mouse, I had never faced what I'm about to describe.

When I'm playing any 3D game that I care to play (rtcw, rtcw:et, warsow), give or take 10 minutes the same will happen most of the times; The mouse freaks in the game, the keyboard input gets corrupted (I can't type anything, either no output or wrong character output), and the mouse either stops responding (the lights are still on) or only accepts some input (like mouse2 but not mouse1).

I am describing this because this condition only happens while playing games. I can be using the mouse on the desktop for days and days and it will NEVER happen. This leads me to believe it's at least related to the nvidia driver.

This problem led me to update to 6.1-STABLE (I was on 6.0-RELEASE) yesterday, and after all the compiling and slashing, an even more interesting problem popped up.


My monitor is an Acer ALI1916W (19" widescreen). Prior to the update, the 1600x1024 resolution was fitting perfectly. However, after doing the upgrade (which included nvidia-driver), the display was unusable. About 20% of the graphical environment was invisible, because the image was too on the left. I spent hours and hours recompiling xorg, nvidia-driver, even rebuilding the kernel and trying different NvAGP values. At this point, trying to run any 3D game would result in Xorg dying and the box locking up on the console.

The resolution for the above problem was quite simple (so simple I didn't try it until after 8h :)). Downgrading to nvidia-driver-1.0-8178 from December 2005 did the trick. (which was what I was using before)

What I would like to know is if it is a known problem (afterwards, I tried two more recent versions and on both my display was misaligned, only 1.0-8178 worked). I find it highly unlikely that all the latest revisions on the driver will fail on any widescreen at 1600x1024, because it's not so uncommon these days..

The mouse problem (that's most likely related to OpenGL) will be a tough one to kill, and I'm not very optimistic about someone having had the same problem and somehow fixing it. But I'd like to get some feedback about why my display on 19" widescreen @ 1600x1024 with any revision newer than 1.0-8178 doesn't work.

zander
09-03-06, 09:23 AM
I'm not sure what could be causing the input problems you describe, but I highly doubt that the NVIDIA FreeBSD graphics driver is involved in any way, since it isn't involved in X's input event processing. Maybe there's a problem with DGA mouse input or with low-level input event processing.

As to the display problem, it'd be good if you could start X with the -logverbose 6 option with 1.0-8774 and attach the /var/log/Xorg.0.log file generated. Recent NVIDIA UNIX graphics driver releases rely more heavily on informationn provided by the monitor via its EDID data, which is sometimes inaccurate/incorrect. You may want to experiment with the EDID related NVIDIA X driver options (UseEDID, etc., see http://download.nvidia.com/freebsd/1.0-8774/README/appendix-d.html).

klr
09-03-06, 02:26 PM
Ok, I will attach the logfile tonight and experiment with the EDID options later on.

I will update the thread soon.

klr
09-03-06, 04:55 PM
Xorg.0.log with -logverbose 6 follows cat be found at:

http://67.19.182.100/Xorg.0.log

klr
09-03-06, 04:56 PM
-

klr
09-03-06, 08:26 PM
I've tried the latest driver revision with UseEDID "FALSE".

The display is aligned, but it also reverts back to 1024x768, which is too low to properly use on this monitor..

Since it works with 1.0-8178, it must have been something that changed from that revision up that causes this. I've tried two more driver versions (the latest and the one prior to the latest), and they both caused my display to be misaligned.

What do you suggest to trace back the issue ?

zander
09-04-06, 07:27 AM
Please start X with 1.0-8774 and the above command line parameter and the UseEDID option set to false, as well as with 1.0-8178 (i.e. the working configuration); the comparison of these files may help identify what changed.

klr
09-04-06, 11:30 AM
The Xorg.0.log I posted above is from 1.0-8178 (working) by the way. I will post later on with 1.0-8774 and -logverbose 6

klr
09-04-06, 08:15 PM
1.0-8774 with UseEDID "FALSE" and -logverbose 6 at:

http://67.19.182.100/Xorg.0.log-8774-edid-false

zander
09-05-06, 06:49 PM
It looks like the problem is the 1600x1024 mode you're requesting, the two drivers fall back to different modes. Does 1.0-8774 work better if you comment out the UseEDID option and change the X configuration file to request 1280x1024 (the mode set with 1.0-8178)?

RulerOfHeck
09-06-06, 01:06 PM
Why are you trying to use 1600x1024 with that monitor? I have the same monitor, the correct resolution is 1440x900: I had to make a "custom resolution" with the nVidia drivers to be able to set it. Mind you, this was in Windows.

I would try changing the resolution to the one specified by the monitor.

klr
09-07-06, 12:42 PM
Setting 1280x1024 did the trick and X now launches correctly.

However, I play my games at 800x600 (in order to have a decent framerate), and with 1.0-8774, the upper corner and right corner of the screen are black, and the game appears on the left corner, too small to be played. Setting r_mode 8 solves this, but I'd like to be able to play at 800x600, as I could with 1.0-8178.

zander
09-07-06, 01:56 PM
Make sure 800x600 is in the list of modes specified in the appropriate Screen section.