On Fri, 2010-03-05 at 06:24 -0500, Jeff Garzik wrote: > On 03/04/2010 05:59 PM, Adam Jackson wrote: > > in which you merely remove the nouveau userspace component, and in which > > I can't tell if you built nouveau into the kernel or not, but I assume > > you didn't based on your previous post. The X server does only try the > > one driver before falling back to vesa, which is a bug in the fallback > > logic I suppose. I've (blindly) fixed that for F13 now. > > Thanks. Can this be put into F12 too?
Sure, why not. > > - you didn't try writing an xorg.conf fragment > > - you did, and it didn't work anyway > > > > The latter case is entirely plausible, as nv is not the sort of driver > > that gets a lot of love, but I'm not aware of any open bugs about gf9800 > > in particular in nv. > > The latter... would modeset in grub interfere, perhaps? It's not going to do anything if you didn't build a KMS driver. It's just a kcmdline option like any other; if there's no module to honor it, then it doesn't do anything. grub doesn't have any particular KMS awareness. I'm really going to have to see an X log and dmesg from the failure mode when actually using nv to diagnose this any further. - ajax
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
-- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
