G210m Blank Laptop Display - Page 2

gnm · 11-03-09, 02:01 PM

I will post a copy of my xorg.conf this evening. I did something to the effect of setting the monitor to a (higher than 1366x768) setting which then allowed me to select the 1366x768 resolution. Just used the XFdrake to do that. Then it came right up.

-G

gnm · 11-03-09, 10:31 PM

Here is a xorg.conf which works with the vesa driver ( no accel)

Quote:

# File generated by XFdrake (rev 256990)

Section "Monitor"
Identifier "monitor1"
VendorName "Generic"
ModelName "Flat Panel 1400x1050"
HorizSync 31.5 - 65.5
VertRefresh 56.0 - 65.0
ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630
ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
ModeLine "1368x768_120" 185.67 1368 1472 1624 1880 768 769 772 823 -hsync +vsync
ModeLine "1368x768_100" 151.73 1368 1464 1616 1864 768 769 772 814 -hsync +vsync
ModeLine "1368x768_85" 125.67 1368 1456 1600 1832 768 769 772 807 -hsync +vsync
ModeLine "1368x768_75" 110.19 1368 1456 1600 1832 768 769 772 802 -hsync +vsync
ModeLine "1368x768_60" 85.86 1368 1440 1584 1800 768 769 772 795 -hsync +vsync
ModeLine "1368x768_50" 69.92 1368 1424 1568 1768 768 769 772 791 -hsync +vsync
ModeLine "1360x765_120" 182.63 1360 1456 1608 1856 765 766 769 820 -hsync +vsync
ModeLine "1360x765_100" 149.22 1360 1456 1600 1840 765 766 769 811 -hsync +vsync
ModeLine "1360x765_85" 124.65 1360 1448 1592 1824 765 766 769 804 -hsync +vsync
ModeLine "1360x765_75" 108.34 1360 1440 1584 1808 765 766 769 799 -hsync +vsync
ModeLine "1360x765_60" 84.40 1360 1424 1568 1776 765 766 769 792 -hsync +vsync
ModeLine "1360x765_50" 69.34 1360 1416 1560 1760 765 766 769 788 -hsync +vsync
ModeLine "1280x720_120" 161.56 1280 1376 1512 1744 720 721 724 772 -hsync +vsync
ModeLine "1280x720_100" 131.85 1280 1368 1504 1728 720 721 724 763 -hsync +vsync
ModeLine "1280x720_85" 110.01 1280 1360 1496 1712 720 721 724 756 -hsync +vsync
ModeLine "1280x720_75" 95.65 1280 1352 1488 1696 720 721 724 752 -hsync +vsync
ModeLine "1280x720_60" 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync
ModeLine "1280x720_50" 60.47 1280 1328 1456 1632 720 721 724 741 -hsync +vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1368x768_120" 185.67 1368 1472 1624 1880 768 769 772 823 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1368x768_100" 151.73 1368 1464 1616 1864 768 769 772 814 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1368x768_85" 125.67 1368 1456 1600 1832 768 769 772 807 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1368x768_75" 110.19 1368 1456 1600 1832 768 769 772 802 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1368x768_60" 85.86 1368 1440 1584 1800 768 769 772 795 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1368x768_50" 69.92 1368 1424 1568 1768 768 769 772 791 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1360x765_120" 182.63 1360 1456 1608 1856 765 766 769 820 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1360x765_100" 149.22 1360 1456 1600 1840 765 766 769 811 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1360x765_85" 124.65 1360 1448 1592 1824 765 766 769 804 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1360x765_75" 108.34 1360 1440 1584 1808 765 766 769 799 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1360x765_60" 84.40 1360 1424 1568 1776 765 766 769 792 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1360x765_50" 69.34 1360 1416 1560 1760 765 766 769 788 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x720_120" 161.56 1280 1376 1512 1744 720 721 724 772 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x720_100" 131.85 1280 1368 1504 1728 720 721 724 763 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x720_85" 110.01 1280 1360 1496 1712 720 721 724 756 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x720_75" 95.65 1280 1352 1488 1696 720 721 724 752 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x720_60" 74.48 1280 1336 1472 1664 720 721 724 746 -HSync +Vsync

# modeline generated by gtf(1) [handled by XFdrake]
ModeLine "1280x720_50" 60.47 1280 1328 1456 1632 720 721 724 741 -HSync +Vsync
EndSection
# File generated by XFdrake (rev 256990)

Section "Device"
Identifier "device1"
Driver "vesa"
Option "DPMS"
EndSection

Section "Screen"
Identifier "screen1"
Device "device1"
Monitor "monitor1"
DefaultColorDepth 24

Subsection "Display"
Depth 8
Modes "1366x768" "1360x765" "1280x720"
EndSubsection

Subsection "Display"
Depth 15
Modes "1366x768" "1360x765" "1280x720"
EndSubsection

Subsection "Display"
Depth 16
Modes "1366x768" "1360x765" "1280x720"
EndSubsection

Subsection "Display"
Depth 24
Modes "1366x768" "1360x765" "1280x720"
EndSubsection
EndSection
# File generated by XFdrake (rev 256990)

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder58) Tue Oct 20 21:25:04 PDT 2009

# File generated by XFdrake (rev 256990)
# ************************************************** ********************
# Refer to the xorg.conf man page for details about the format of
# this file.
# ************************************************** ********************

Section "ServerLayout"
Identifier "layout1"
InputDevice "Keyboard1" "CoreKeyboard"
InputDevice "Mouse1" "CorePointer"
InputDevice "Mouse2" "SendCoreEvents"
InputDevice "SynapticsMouse1" "SendCoreEvents"
Screen "screen1"
EndSection

Section "Module"
Disable "dri"
Load "dbe" # Double-Buffering Extension
Load "v4l" # Video for Linux
Load "extmod"
Load "glx" # 3D layer
EndSection

Section "ServerFlags"
#DontZap # disable <Ctrl><Alt><BS> (server abort)
#DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching)

# allows the server to start up even if the mouse does not work
Option "allowmouseopenfail"
EndSection

Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbOptions" "compose:rwin"
EndSection

Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "Device" "/dev/input/mice"
EndSection

Section "InputDevice"
Identifier "Mouse2"
Driver "evdev"
Option "device" "/dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse"
Option "HWheelRelativeAxisButtons" "7 6"
EndSection

Section "InputDevice"
Identifier "SynapticsMouse1"
Driver "synaptics"
Option "SHMConfig" "on"
EndSection

rohitvis · 11-04-09, 12:24 AM

thanks so much for providing a copy of your xorg file. This helped me get the display to the correct resolution.

If i stare too hard at the screen I can see that it is not super crisp. but it will do the job for now.

Thanks

egghead3 · 11-04-09, 08:57 PM

I wanted to add that I also have this problem on a Sony VPCCW with a GT230.

One interesting point I can add is that using an external monitor over HDMI works great (DFP-1). For some reason the driver will not read the EDID information from the laptop display only.

Trying to use the graphical nvidia-settings program when the external monitor is connected fails to detect the laptop screen as well.

egghead3 · 11-05-09, 08:35 AM

Is there any reason to believe extracting the EDID from windows and then forcing via xorg.conf may work?

egghead3 · 11-05-09, 08:31 PM

SUCCESS!! (happy b/c I don't have to return my laptop)

Extracting the edid from windows works great. You just have to add the following lines to the device section of a minimal xorg.conf.

Code:

Option  "ConnectedMonitor"  "DFP-0"
Option  "CustomEDID"         "DFP-0:/path/to/edid.bin"

Where the path is to your edid.bin file that you extracted from within windows. I used the program softMCCS to extract the edid. Make you you save it as binary (.bin). I can attach the EDID I got for the VPCCW tomorrow when I have the laptop set up (I am posting this from another computer).

The only quick so far is that when you quit X the console is not restored for some reason.

edited to add my full xorg.conf for clarity. I am using HAL to autodetect most hardware, so it is minimal:

Code:

Section "Device"
   Identifier         "Device0"
   Driver              "nvidia"
   VendorName    "NVIDIA Corporation"
   Option            "ConnectedMonitor"   "DFP-0"
   Option            "CustomEDID"          "DFP-0:/etc/X11/sonyedid.bin"
EndSection

andrei123 · 11-05-09, 08:41 PM

Quote:

Originally Posted by egghead3

SUCCESS!! (happy b/c I don't have to return my laptop)

Extracting the edid from windows works great. You just have to add the following lines to the device section of a minimal xorg.conf.

Code:

Option  "ConnectedMonitor"  "DFP-0"
Option  "CustomEDID"         "DFP-0:/path/to/edid.bin"

Where the path is to your edid.bin file that you extracted from within windows. I used the program softMCCS to extract the edid. Make you you save it as binary (.bin). I can attach the EDID I got for the VPCCW tomorrow when I have the laptop set up (I am posting this from another computer).

The only quick so far is that when you quit X the console is not restored for some reason.

Congratulations! Could you post a mini how-to-setup-nvidia-driver, including that last step that everyone was waiting for? I have a Sony Vaio VPCCW with GT230M, Ubuntu 9.10.
Did you manage to get the native screen resolution?

Can't wait to hear more from you. Again, congratulations!

egghead3 · 11-06-09, 07:05 AM

Yes I have native screen resolution running with the nvidia driver (including acceleration with compiz). I also have the VPCCW with GT230M. I am running archlinux - so I am not entirely familiar with how Ubuntu uses xorg.conf these days. I imagine it is probably similar, but if you are still using a full xorg.conf instead of using a minimal xorg.conf with HAL then I'm not sure if you have to do anything else. What I posted in my previous post is my full xorg.conf.

I will post a more in depth how to this evening when I get home from the lab, including a brief explanation of how I extracted the EDID from windows.

andrei123 · 11-06-09, 03:33 PM

Using windows's EDID worked for me! Egghead3, you are a genius. I am so happy. I was afraid that I will have to return my vaio, because of this bug in nvidia driver. Your solution is a rock-solid walkaround! Thank you again.

Ubuntu 9.10 (and maybe older versions, too) uses minimal xorg.conf. I just added two lines, as you suggested. Now my tuxracer is flying again :-) plus, I can now work on my VR projects. Before Ubuntu, I tried fc-11, opensuse 11.1 -- all the same, the screen goes blank after installing nvidia 190.42 driver.

I still think it's worth writing up a mini tutorial on this subject. There will be more people with the same problem. Vaio CW seems to be very good, so it deserves a decent OS like linux, right? (-:

egghead3 · 11-06-09, 04:47 PM

Here is a basic walkthrough for anyone encountering this problem. I am currently using driver version 190.42. If a newer driver is available when you read this, try that first as the work around may no longer be necessary. This walkthrough assumes you are using a minimal xorg.conf, but can probably be easily adapted to a full xorg.conf.

The Problem

For some reason, the current nvidia driver does not auto-detect that a display is attached to an internal digital port. Even if you force the driver to assume a display is attached, it is still unable to read the EDID information from the display. It is this information which tells the driver how to drive the display. Starting X yields just a blank screen. I encountered this problem on a Sony Vaio VPCCW with a GT230M card. I am running Archlinux.

The Workaround

The EDID information is detected fine in windows, so we can extract it from there. We then edit xorg.conf to tell the driver that a display is connected to DFP-0 (the internal port) and to use use the EDID we extracted intead of probing the monitor for it.

Please note: I am just a user and take no responsibility for any problems that may occur as a result of this workaround. Make sure you understand the purpose of each step and proceed at your own risk.

Extract the EDID file from within windows. I used the program softMCCS which can be found here. Open the program and go to file -> Save EDID as. The filename you choose doesn't matter, but make sure use the binary (bin) format. Put this on a memory stick or use some other method to copy it to your linux filesystem.
Boot into linux and put the EDID file in your /etx/X11 folder (it could actually go anywhere, but I found this to be convenient).
Code:
```
sudo mv /path/to/your/edid.bin /etc/X11/.
```
Backup your current xorg.conf file (if you have one).
Code:
```
sudo mv xorg.conf xorg.conf_backup
```
Create a new minimal xorg.conf file. Alternately, you can choose just to add to your existing one.
Code:
```
sudo touch /etc/X11/xorg.conf
```
Edit xorg.conf and create a simple device section containing the following:
Code:
```
Section "Device"
   Identifier          "Device0"
   Driver              "nvidia"
   VendorName         "NVIDIA Corporation"
   Option             "ConnectedMonitor"   "DFP-0"
   Option             "CustomEDID"          "DFP-0:/etc/X11/youredid.bin"
EndSection
```
Replace "youredid.bin" with whatever you named your EDID file. The two Option lines are what does the trick. The first tells the driver you have a display connected on the internal DFP-0 port. The second tells it not to probe for an EDID, but rather to use the one you are providing.
Restart X and you should see the NVIDIA logo flashing right at you.

When the driver is next updated, try commenting out the two option lines to see if the bug is fixed.

andrei123 · 11-06-09, 05:58 PM

One remaining issue is to be able to get text console by pressing Cntrl + Alt + Fn from X. Now, I still see a blank screen. But it's a really minor issue.

rohitvis · 11-06-09, 06:41 PM

egghead3 thanx a bunch for your solution.

11-03-09, 02:01 PM	#13
gnm Registered User Join Date: Nov 2009 Posts: 3	Re: G210m Blank Laptop Display I will post a copy of my xorg.conf this evening. I did something to the effect of setting the monitor to a (higher than 1366x768) setting which then allowed me to select the 1366x768 resolution. Just used the XFdrake to do that. Then it came right up. -G

11-04-09, 12:24 AM	#15
rohitvis Registered User Join Date: Nov 2009 Posts: 8	Re: G210m Blank Laptop Display thanks so much for providing a copy of your xorg file. This helped me get the display to the correct resolution. If i stare too hard at the screen I can see that it is not super crisp. but it will do the job for now. Thanks

11-04-09, 08:57 PM	#16
egghead3 Registered User Join Date: Jan 2008 Posts: 11	Re: G210m Blank Laptop Display I wanted to add that I also have this problem on a Sony VPCCW with a GT230. One interesting point I can add is that using an external monitor over HDMI works great (DFP-1). For some reason the driver will not read the EDID information from the laptop display only. Trying to use the graphical nvidia-settings program when the external monitor is connected fails to detect the laptop screen as well.

11-05-09, 08:35 AM	#17
egghead3 Registered User Join Date: Jan 2008 Posts: 11	Re: G210m Blank Laptop Display Is there any reason to believe extracting the EDID from windows and then forcing via xorg.conf may work?

11-05-09, 08:31 PM	#18
egghead3 Registered User Join Date: Jan 2008 Posts: 11	Re: G210m Blank Laptop Display SUCCESS!! (happy b/c I don't have to return my laptop) Extracting the edid from windows works great. You just have to add the following lines to the device section of a minimal xorg.conf. Code: Option "ConnectedMonitor" "DFP-0" Option "CustomEDID" "DFP-0:/path/to/edid.bin" Where the path is to your edid.bin file that you extracted from within windows. I used the program softMCCS to extract the edid. Make you you save it as binary (.bin). I can attach the EDID I got for the VPCCW tomorrow when I have the laptop set up (I am posting this from another computer). The only quick so far is that when you quit X the console is not restored for some reason. edited to add my full xorg.conf for clarity. I am using HAL to autodetect most hardware, so it is minimal: Code: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" Option "ConnectedMonitor" "DFP-0" Option "CustomEDID" "DFP-0:/etc/X11/sonyedid.bin" EndSection

11-06-09, 07:05 AM	#20
egghead3 Registered User Join Date: Jan 2008 Posts: 11	Re: G210m Blank Laptop Display Yes I have native screen resolution running with the nvidia driver (including acceleration with compiz). I also have the VPCCW with GT230M. I am running archlinux - so I am not entirely familiar with how Ubuntu uses xorg.conf these days. I imagine it is probably similar, but if you are still using a full xorg.conf instead of using a minimal xorg.conf with HAL then I'm not sure if you have to do anything else. What I posted in my previous post is my full xorg.conf. I will post a more in depth how to this evening when I get home from the lab, including a brief explanation of how I extracted the EDID from windows.

11-06-09, 03:33 PM	#21
andrei123 Registered User Join Date: Nov 2009 Posts: 3	Re: G210m Blank Laptop Display Using windows's EDID worked for me! Egghead3, you are a genius. I am so happy. I was afraid that I will have to return my vaio, because of this bug in nvidia driver. Your solution is a rock-solid walkaround! Thank you again. Ubuntu 9.10 (and maybe older versions, too) uses minimal xorg.conf. I just added two lines, as you suggested. Now my tuxracer is flying again :-) plus, I can now work on my VR projects. Before Ubuntu, I tried fc-11, opensuse 11.1 -- all the same, the screen goes blank after installing nvidia 190.42 driver. I still think it's worth writing up a mini tutorial on this subject. There will be more people with the same problem. Vaio CW seems to be very good, so it deserves a decent OS like linux, right? (-:

11-06-09, 04:47 PM	#22
egghead3 Registered User Join Date: Jan 2008 Posts: 11	Re: G210m Blank Laptop Display Here is a basic walkthrough for anyone encountering this problem. I am currently using driver version 190.42. If a newer driver is available when you read this, try that first as the work around may no longer be necessary. This walkthrough assumes you are using a minimal xorg.conf, but can probably be easily adapted to a full xorg.conf. The Problem For some reason, the current nvidia driver does not auto-detect that a display is attached to an internal digital port. Even if you force the driver to assume a display is attached, it is still unable to read the EDID information from the display. It is this information which tells the driver how to drive the display. Starting X yields just a blank screen. I encountered this problem on a Sony Vaio VPCCW with a GT230M card. I am running Archlinux. The Workaround The EDID information is detected fine in windows, so we can extract it from there. We then edit xorg.conf to tell the driver that a display is connected to DFP-0 (the internal port) and to use use the EDID we extracted intead of probing the monitor for it. Please note: I am just a user and take no responsibility for any problems that may occur as a result of this workaround. Make sure you understand the purpose of each step and proceed at your own risk. Extract the EDID file from within windows. I used the program softMCCS which can be found here. Open the program and go to file -> Save EDID as. The filename you choose doesn't matter, but make sure use the binary (bin) format. Put this on a memory stick or use some other method to copy it to your linux filesystem. Boot into linux and put the EDID file in your /etx/X11 folder (it could actually go anywhere, but I found this to be convenient). Code: sudo mv /path/to/your/edid.bin /etc/X11/. Backup your current xorg.conf file (if you have one). Code: sudo mv xorg.conf xorg.conf_backup Create a new minimal xorg.conf file. Alternately, you can choose just to add to your existing one. Code: sudo touch /etc/X11/xorg.conf Edit xorg.conf and create a simple device section containing the following: Code: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" Option "ConnectedMonitor" "DFP-0" Option "CustomEDID" "DFP-0:/etc/X11/youredid.bin" EndSection Replace "youredid.bin" with whatever you named your EDID file. The two Option lines are what does the trick. The first tells the driver you have a display connected on the internal DFP-0 port. The second tells it not to probe for an EDID, but rather to use the one you are providing. Restart X and you should see the NVIDIA logo flashing right at you. When the driver is next updated, try commenting out the two option lines to see if the bug is fixed.

11-06-09, 05:58 PM	#23
andrei123 Registered User Join Date: Nov 2009 Posts: 3	Re: G210m Blank Laptop Display One remaining issue is to be able to get text console by pressing Cntrl + Alt + Fn from X. Now, I still see a blank screen. But it's a really minor issue.

11-06-09, 06:41 PM	#24
rohitvis Registered User Join Date: Nov 2009 Posts: 8	Re: G210m Blank Laptop Display egghead3 thanx a bunch for your solution.