Hello all,
I am sure the bug now is fixed in Hardy and Ibex. I tried once with a new
Ubuntu and it worked properly. I will have to get a system(not at hand
currently) and come back with the information since which version it
worked.
Best Regards,
Christian
I have to say it is. My Hardy
I suggest that this become a different bug -- I thought I had fixed this
already :/
I would like to know more about your system. Do you know if you are
suing a framebuffer console? What is your BIOS?
Can you provide the versions of your related packages:
dpkg -l xserver-xorg-video-geode
webworm wrote:
Martin-Éric Racine wrote:
2.9.0-1ubuntu2 was just replaced by 2.9.0-1ubuntu3 to completely close
this issue. It's already available in my PPA and should soon be
uploaded to Hardy-proposed. For Intrepid, package 2.9.0-3 (pending
import from Debian/unstable) includes the same
Martin-Éric Racine wrote:
2.9.0-1ubuntu2 was just replaced by 2.9.0-1ubuntu3 to completely close
this issue. It's already available in my PPA and should soon be
uploaded to Hardy-proposed. For Intrepid, package 2.9.0-3 (pending
import from Debian/unstable) includes the same fixes.
I have a
On 2/13/08, Jordan Erickson [EMAIL PROTECTED] wrote:
I can confirm the fix ( https://launchpad.net/%7Eq-funk/+archive ) for
LTSP thin clients using the AMD Geode chipset, although it only allows
me to boot into X11/LDM at 800x600 with what seems to be 16 colors. I
cannot manually configure
I have seen this, as well. Thought it was a GX thing, but I guess
not. In the logs, it seems to assume the color depth of the
framebuffer. Not sure why...
-Gadi
On Jan 25, 2008 4:27 PM, Martin-Éric Racine [EMAIL PROTECTED] wrote:
As previously reported, DDC works as expected when booting the
