|
|
#1 | |
|
Registered User
Join Date: Oct 2009
Posts: 8
|
I just recently got a Sony Vaio laptop which has a G210M graphics card.
After installing various versions of the driver, both production (185.18.36) and the latest beta I could find (190.42), and setting up X to use the 'nvidia' driver, the laptop display goes blank and actually turns off when X starts. After a few hours of googling and trying things, I believe that it's incorrectly detecting that no monitors are attached and it's trying to display through the vga port. Including Option "ConnectedMonitor" "DFP" causes the screen to come on at least, but it's just grey and back lines. I would guess that it's a resolution problem at that point but I'm not sure where to go from there. I've tried generating some mode lines but I can't even get one for the native resolution (1366x768) and 1280x720 didn't work either. Any ideas? |
|
|
|
|
|
|
#2 | |
|
NVIDIA Corporation
Join Date: Mar 2005
Posts: 2,487
|
Please see the forum sticky posts about how to generate an nvidia-bug-report.log.gz file.
|
|
|
|
|
|
|
#3 |
|
Registered User
Join Date: Oct 2009
Posts: 8
|
The report is now attached. I generated this with the 190.42 driver with the most basic options possible.
xorg.conf is as follows: Code:
Section "Device" Identifier "Configured Video Device" Driver "nvidia" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" EndSection |
|
|
|
|
|
#4 | |
|
NVIDIA Corporation
Join Date: Mar 2005
Posts: 2,487
|
Hmm, that's very strange. The driver indeed doesn't seem to think that there are any monitors connected. I'll need to see if I can find one of these laptops to reproduce the problem.
|
|
|
|
|
|
|
#5 |
|
Registered User
Join Date: Oct 2009
Posts: 8
|
Ok thanks. My laptop is a Sony Vaio VPCCW17FX but I believe most of the VPCC series is similar.
|
|
|
|
|
|
#6 | |
|
NVIDIA Corporation
Join Date: Mar 2005
Posts: 2,487
|
Thank you for reporting this problem. I tracked down the laptop in question, reproduced the problem, and filed a bug.
|
|
|
|
|
|
|
#7 |
|
Registered User
Join Date: Sep 2009
Posts: 2
|
I have the same problem with Acer Aspire 5739G.
Installing 190.42 on Ubuntu 9.10 causes black screen, caps lock flushing and rebooting in a few minutes. Aaron, please, see at my nvidia-bug-report. Hope you can help me. Thank you in advance. Alex |
|
|
|
|
|
#8 |
|
Registered User
Join Date: Nov 2009
Posts: 8
|
I have the same problem. Does anyone have any creative solution?
I have been using the vesa driver but its blurry and does not set the resolution correctly. My laptop is also a Sony Vaio VPCCW17FX |
|
|
|
|
|
#9 |
|
Registered User
Join Date: Nov 2009
Posts: 2
|
For the time being I would recommend using the 'nv' driver instead of the vesa driver. I have the same laptop and this will at least provide you with proper resolution. The nv drivers lacks any 3d acceleration so compositing will not function but you will at least you will have a functional machine until the official driver gets sorted out.
|
|
|
|
|
|
#10 |
|
Registered User
Join Date: Nov 2009
Posts: 8
|
Can you post your xorg.conf file?
I'm having no luck with any of the drivers. I tried using nv but not luck. When I use nv, the laptop behaves the same way i.e. screen goes black. Thanks |
|
|
|
|
|
#11 |
|
Registered User
Join Date: Nov 2009
Posts: 3
|
I also have the Sony - same thing - blank screen. The vesa driver works (using mandriva 2009.1) but of course I have no hardware acceleration. Eagerly awating any patches!
-Brian |
|
|
|
|
|
#12 |
|
Registered User
Join Date: Nov 2009
Posts: 8
|
What did you have to do to get the vesa driver to work. I'm using Fedora 11 64bit. I logged into runlevel 3 and did an Xorg -configure followed by copying the xorg.conf to the /etc/X11/ dir. Then I updated the Driver string to say "vesa". Also I tried using the system-config-display.
Both of them work fine in that they display a GUI but not at the correct resolution. On Mandriva or any other distro -- what did y'all have to do to get the vesa driver to display at the correct resolution? |
|
|
|
![]() |
| Thread Tools | |
|
|