== Executive summary ==
Problem: after a (random) reboot, the resolution is loaded as XGA 1024x768 instead of SXGA+ 1400x1050; but with a 'tiling' so that the 1024x768 fills the top-left corner; and the rest of the space is filled with repeated versions of the display with some black strip separating them [sorry for vague description, I am doing this from memory and have no picture]. EDIT: see pictures below.
Suspected cause: a hardware problem (coming from the oozing glue / bubble in LCD problem that I have -- see this thread) makes EDID data to be badly read sometimes? (as it also happens in BIOS, Windows 7 and Ubuntu) Just speculating here...
Question: how do I make sure the correct EDID data is used by the OS even though sometimes it is loaded wrong? How can I use the SXGA+ resolution when it booted with XGA and SXGA+ doesn't appear as an option?
== Detailed description ==
After a reboot at some point, the screen resolution appeared as XGA 1024x768 in top-left corner with 'tiling' to fill the whole 1400x1050 space of the SXGA+ screen -- as described above. The laptop was purchased in December 2008; warranty expired Oct 2011. It is running Windows 7 x64 ultimate. I have had the same problem while changing the display configuration in the past (e.g. when rotating screen; or plugging external screen, or something like that ) -- but the problem was always resolved after a simple reboot. Whereas this time, the problem was persistent (and even appearing in the BIOS) after reboot.
Note that using an external display works fine, even though the laptop LCD looks fairly weird with tiled resolution. Another weird aspect: if I moved a bit the laptop while holding it in my hands, the laptop display would start to 'wither' (oscillate) -- pressing the rotating screen button would stops the oscillation, until I would shake it again...
After some googling, I suspected that the EDID information was misread by the hardware. I have tried a bunch of things; and the behavior of the laptop hasn't been consistent. But here are things that I have tried:
1) Re-installed the Intel driver and/or the monitor driver; with multiple reboots; and permutation of update/install/re-install. [Didn't fix it.]
2) I tried to change directly the resolution in the Windows registry (as described here). Reboot. [Didn't fix it.]
3) I tried to force Windows to use a tailored EDID loading by creating a .inf file by (somewhat) following the instructions from this page. Here, I didn't fully understand what I was doing, so I am not sure if I did everything as needed...
4) I booted in Ubuntu using a USB boot disk, and tried a few things there, including trying to generate a newmode with xrandr for the 1400x1050 mode which was missing in the auto-detect, but it answered "X Error of failed request: BadMatch (invalid parameter attributes)" while trying to load it. I am a newbie with Ubuntu, so I am not sure what other options I had to try to have a resolution which was not read from the hardware... [Didn't fix it.]
== Other background -- air bubble + oozing glue problem:
I started having the growing air bubble problem behind the LCD screen (as described in gory details in this thread) in July 2011. I tried to exchange the screen while under warranty (Lenovo said to just send the laptop to depot for a screen exchange); but as I was traveling in different countries and using the laptop every day, it took a while before I got the process started and to make a long story short, I got some problems with a service provider in France which prevented me to get the screen exchanged before the warranty expired; so I stayed stuck with it. I think around December 2011, I started to have the oozing glue problem as described in the above mentioned thread (some glue is oozing from the 'rotate screen' and the 'table options' buttons; as well as on the sides and close to the power button -- it is fairly gross, though the tablet is still usable). I understand that the screen hardware situation is not ideal and might be behind the problem that I am mentioning above. But I don't have the time nor the money right now to have the whole screen replaced. And there are no high resolution convertible tablet PCs on the market anymore (WHY NOT??? -- I just hope that the retina display iPad will push Lenovo to bring back some higher resolution tablet PCs on the market...)
== Weird auto-fixes:
I will repeat that I didn't succeed to find a consistency in the behavior of the system... After some reboot, the problem was automagically solved (the resolution was back to SXGA+) -- but this didn't seem to be caused by any of the above changes I mentioned above. In particular, the problem reappeared after another reboot (!); and I wasn't able to fix it until another time it randomly worked after a reboot. At this time, I didn't want to risk having the problem reappear anymore -- so I haven't rebooted my laptop since then (last two weeks). I am hoping that somebody could find a more systematic way to solve the problem than to pray that some random reboot will fix it...
The first time the resolution came back to normal was when I moved from the office to home (10 minutes bike ride while it was turned off). So I thought that maybe heat was the issue. But when the resolution got screwed up again, I turned it off and left it in the cold for half an hour -- the problem was still there after turning it on again, so it didn't look like heat was the systematic culprit. Because it is such a hindrance of having the resolution screwed up (in particular, I can definitively not use the input pen as the pointer appears in the XGA part where it should be had it been stretched to the whole size [so there is a proportional offset between where I put my pen and where the pointer appear]), I haven't explored more options after it got working again randomly.
Right now, I have a few windows updates which require a reboot; and some software parts started to have problems as usual (bluetooth headset; thinkpad external keyboard customizer; etc.) -- which is fairly common for Windows and would normally be solved by a reboot -- but I don't want to reboot until I have some paths of solution to this problem (e.g. backing up some correct display information so that when the problem happens again I can just force this display information to be used).
Thanks for reading so far and for any help / pointer!






