|
|
#1 | |
|
Registered User
Join Date: Oct 2007
Posts: 34
|
Just downloaded and tested the 171.05 64 bit driver. VT are still unusable.
|
|
|
|
|
|
|
#2 | |
|
NVIDIA Corporation
Join Date: Aug 2002
Posts: 3,740
|
The 171.05 driver release is intended for use with Tesla S870 GPU Computing Systems, only.
|
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: Oct 2007
Posts: 34
|
Well, the problem is in how the 169+ drivers are dealing with the LCD screen. I plug in an external monitor and it works fine in the VT. Using nvidia xserver settings, adding the external monitor to the X session, and displaying the X session on both screens, when you switch back to a VT, the LCD on the laptop is out of sync but the screen on the external monitor is fine. You can enter commands and see what the results are on the external monitor.
Please tell us what we could change to get the internal LCD screens working again. Attached is the edid as seen by the 169+ drivers. Monitor section: VendorName "LPL" ModelName "LGPHILIPSLCD LCD MONITOR" UseModes "Modes[0]" DisplaySize 330 210 HorizSync 30.0 - 62.0 VertRefresh 43.0 - 60.0 Option "DPMS" |
|
|
|
|
|
#4 | |
|
Registered User
Join Date: Aug 2003
Posts: 25
|
Quote:
I don't suppose anybody could tell whether ABI 1.4 is going to be supported in near future? Fedora 9 alpha is out, and I'd like to play with it. "nv" driver works, but I'd of course like to use "nvidia". Or is there any chance the current drivers are usable with -ignoreABI? |
|
|
|
|
|
|
#5 | |
|
Registered User
Join Date: Apr 2005
Posts: 9
|
Quote:
-- Savali |
|
|
|
|
|
|
#6 | |
|
Registered User
Join Date: Sep 2007
Posts: 27
|
I dont have any problems with VT on 7300GT, maybe because im using vesafb.
|
|
|
|
|
|
|
#7 |
|
Registered User
Join Date: Oct 2007
Posts: 34
|
The issue is something that was changed between the 100 series and the 169+ dealing with how the driver handles laptop lcd screens. External monitors work fine on my laptop.
|
|
|
|
|
|
#8 |
|
Registered User
Join Date: Sep 2007
Posts: 27
|
I dont have VT problem with vesafb on any of two screens(VT works on that monitor(s), that was switched on during POST(or maybe vesafb initialization, not shure)
But I have vsync problem on left CRT monitor(connected to DVI-DSUB), and i have vsync working on right LCD monitor connect directly to DSUB), in clone mode(102x768+0+0,1024x768+0+), and one big screen(1024x768+0+0, 1024x768+1024+0) using nvidia xinerama(with disabled dyn. twinview, triple buffering enabled), compiz fusion. And screenshots looks more vsynced then left screen( wobbling window looks really strange on screenshots). I was playing with switching vsync in ccsm, nvclock, and setting __GL_SYNC_TO_VBLANK= variable , and it doesnt help. I also cannot enable Anisotrophic filtering trogh variable and nvclock(before running compiz, and games). I know 171.05 is not supported on 7300GT, but I feel like it eats much less CPU when moving wobbling window with glxgears(which runs smoothly), and cube works quicker(but maybe its caused by not working aniso, and maybe mor poor graphic). Im waiting from many relases when Xv overlay will be probably sized when using 1024x768 resolution(in 2048x768 it works great) |
|
|
|
|
|
#9 |
|
Registered User
Join Date: Oct 2007
Posts: 34
|
The problem is in one of the libraries that replace a X or Mesa library. After doing an update that included X modules, the NVidia driver loaded and the VT were fine. Reloaded the NVidia driver and then the VT were broken again, due to 1 or more libraries being replaced.
|
|
|
|
|
|
#10 |
|
Registered User
Join Date: Mar 2007
Posts: 58
|
Please look at this: http://www.nvnews.net/vbulletin/show....php?p=1797697
|
|
|
|
![]() |
| Thread Tools | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| 302.11 driver only allows native resolution settings of laptop DFP | darinmiller | NVIDIA Linux | 2 | 05-30-12 03:45 PM |