GUI no longer starting after recent updates "VESA(0): No matching modes"
Arch Willingham
arch at tuparks.com
Wed May 7 17:32:46 UTC 2008
I didn't set the driver - its just whatever the startup chose??? As background, I had an old crap#y video card that did not work worth a hooie. I found another older card around here, stuck it in and it worked fine until the most recent updates outlined in my post.
Thanks for creating the bug thing!
Arch
-----Original Message-----
From: fedora-test-list-bounces at redhat.com [mailto:fedora-test-list-bounces at redhat.com] On Behalf Of Adam Jackson
Sent: Wednesday, May 07, 2008 1:12 PM
To: For testers of Fedora Core development releases
Subject: Re: GUI no longer starting after recent updates "VESA(0): No matching modes"
On Wed, 2008-05-07 at 11:54 -0400, Arch Willingham wrote:
> After the most recent updates to F9, one of my workstations will no
> longer boot to the GUI. It goes through the process and ends up with
> en error saying:
You seem to be using the vesa driver. Why are you not using the trident
driver?
That said, it's certainly due to a recent change in the vesa driver.
We're trying to set 24+32bpp but your card doesn't support that. We
_should_ detect that case correctly but clearly aren't.
I've created a bug for the issue:
https://bugzilla.redhat.com/show_bug.cgi?id=445566
- ajax
--
fedora-test-list mailing list
fedora-test-list at redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
More information about the fedora-test-list
mailing list