carnbot :
Wrathlon69 :
OK mine arrived, I have the similar screen crap going on but its on everything.
When I plug the original screen in, it works fine.
Considering the guy in that thread did it with a laptop that shares the exact same panels Id really love to know why its having issues.
I'm still waiting for my LCD cable to arrive. Did you double check that the screen was attached properly?
Is it an LG screen like the original?
This is a setback as we can't confirm if anyone has managed to upgrade this model yet.
I double, triple and quadruple checked. I'm confident I know exactly what the problem is:
In the older NB500 series it has a low level hardware control to initialise the screen properly at 1366x768 whereas our model doesnt. All is not lost however, as this means its purely a signal output problem.
Evidence pointing to this:
1) I found a thread of a guy who was replacing the LP101WSA screen (Our factory panel) with a LP101WH1 (The panel we are trying to use) in a different laptop. One person solved it by extracting the graphics module from the BIOS of a different laptop and imported it into the BIOS for his laptop and got it going as it now contained the profile needed to run that panel correctly.
2) In another thread, a guy doing the same thing managed to resolve the problem by compiling a new intel graphics driver with custom signal settings to override the defaults. This made the panel work perfectly in Windows but didnt resolve the issues outside of windows obviously as its a driver fix. This doesnt matter as the signal, although bad, is more than adequate for BIOS and setup, etc.
The first finding points to it being a BIOS limitation, the second points to that limitation being able to be compensated for in the graphics driver.
I actually have some experience in this - my desktop runs a Radeon 5970 and I use an old FW900 24" Widescreen CRT. The problem is ATi drivers cant custom res simply like nVidia ones can and the monitor supports well beyond its official resolutions. I made a custom monitor INF that overrides the EDID detection and tells the graphic card specifically what signal to output and it works. I have a monitor that officially supports 2304x1440@60hz outputting 2560x1600@72hz.
I tried the same trick on the netbook with the new panel and it seems the 6250/6290 accepts this override just fine as I went from bad signal to no signal at all but still had backlight control indicating the panel was just out of range. When I plugged the default panel it, it tried to draw 1366x768 but cut it off because the panel isnt that big and it had a green artifact at the bottom meaning that it did, in fact, modify the graphics card output.
I have documentation of both panels with their signalling info and they are VERY different panels, hence why it doesnt work properly. Given what I've found, what others have solved with and from my limited testing so far, I should be able to make a custom driver to enable the panel to work correctly just need a bit of time to play around and experiment.
Dont lose hope just yet because I'm about 90% confident I can fix this.