On Wed, 2010-03-10 at 13:44 -0500, Adam Jackson wrote: > On Wed, 2010-03-10 at 17:20 +0100, Michal Hlavinka wrote: > > On Wednesday 10 March 2010 17:14:41 Michał Piotrowski wrote: > > > Hi, > > > > > > I tried to install this new Goddard thing on my laptop and it seems to be > > > b0rken https://bugzilla.redhat.com/show_bug.cgi?id=572243 > > > > > > Any chance to get graphical installer with vesa driver? > > > > > > Regards, > > > Michal > > > > afaik you have to use xdriver=vesa as additional boot parameter > > He did. I took the sensible precaution of dumping /proc/cmdline in the > X log for exactly this reason. > > The real issue is that the addition of xorg.conf.d support seems to have > changed how the automatic configuration logic works, such that _only_ > the intel driver is loaded, instead of falling back to vesa. > > I'm looking into it. This sounds like it's similar to what we saw with the vboxvideo driver, right? When that failed it didn't fall back to vesa, either... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
