Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Can anyone help with this?
The XFree86 trident driver has always had a problem with the Thinkpad 365XD
Trident TGUI 9320 "Cyber" chipset interacting with IBM's DSTN 800x600 LCD.
On startup, the screen would only display two horizontal orange lines and
"burn" the LCD, physically damaging the display - with some recovery over
time, as if each section of the dual scan display had lost the vertical scan
The traditional work-around has been to press Fn and F7, the
LCD/external-monitor switching function, after the X server is started. The
result would be a normal display after a few second delay. This was
possible with the XFree86 SVGA driver version 3.3.6 at least.
The new Xorg trident driver still shows the same problem with the burning
orange lines, but the "Fn and F7" hack has a problem - the system freezes /
crashes instantly. The laptop must be powered down to recover.
Now, the reason I'm sending this to linux-fbdev-devel is that the kernel
trident framebuffer driver seems to have exactly the same problem. The file
says "much inspired by the XFree86 4.x Trident driver sources by Alan
Hourihan". The problem started with XFree86 4.0, with the change XFree86 3
to XFree86 4. Xorg has inherited these driver problems, which have never
been fixed in XFree86. The kernel trident framebuffer driver also seems to
have inherited whatever is causing this problem.
Anyone familiar with the XFree86 3 -> 4 changes?