I'm testing an ultra-mobile laptop based on AMD Geode LX 800 and cannot get X to display on the laptop panel, only on the external monitor, when using the amd driver, which I fetched with git. With the vesa driver from Xorg 7.2 (ubuntu feisty) I get both outputs working, although other, more recent, versions of Xorg (the ones in ubuntu gutsy and fedora 7) the vesa driver crashes with "A2 ILLEGAL EXTENDED X86 OPCODE". With the amd driver, the log reports "no dcon is present" and output "panel: no". I'm interested in the geode platforms for several reasons, and this is my first experience with them, so I'm willing to learn and help.
Created attachment 11843 [details] Log from broken system
Created attachment 11844 [details] Conf from broken system
The driver is broken with X server 1.3 or newer because it uses x86emu whereas all previous X servers used vm86. It affects BIOS polling in a number of ways.
Note that driver version 2.7.7.5 introduced basic OLPC support. Please test this release on your laptop and report on your results.
This should work with AMD driver 2.7.7.6 and an X server patched with https://bugs.freedesktop.org/show_bug.cgi?id=14332 Can you please confirm this?
Try the noDDC option described at https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amd/+bug/195846 and see if it helps.
I'm sorry for not getting back regarding this laptop. At the time, I managed to get a working solution with a custom gdm script and ddcprobe to switch between X server layouts, although I could never acess the console (with ctrl-alt-f*), it always returned a white screen. Following Martin-Éric's advice (comment #5), I upgraded to xserver-xorg-video-amd_2.7.7.6-1ubuntu2_i386 and xserver-xorg-core_1.3.0.0.dfsg-12ubuntu12_i386 (from ppa.launchpad.net/q-funk). Both the output to panel and external monitor work now, with the amd driver, and switching to console and back also works, so I guess this means it's fixed.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.