On Thu, Oct 29, 2015 at 10:44:10PM +0100, spakyelj wrote: > Ken Moffat schreef: > >On Wed, Oct 28, 2015 at 10:03:18PM +0100, spakyelj wrote:
> >DRM_NOUVEAU should be set (it looks like the main enabler, depends > >on various things, in menuconfig use '/DRM_NOUVEAU' if you cannot > >enable it). In fact, it looks to me as if that is the only thing > >which requires to be set to build nouveau in the kernel. > DRM_NOUVEAUis build into the kernel. > >There is also NOUVEAU_PLATFORM_DRIVER if this is a SoC (System on > >Chip) - but I guess that the RIVA TNT2 is NOT a SoC because the > >concept seems to be fairly recent. Google suggests it is Tegra and > >newer : I believe those are for ARM not x86. > > > >If DRM_NOUVEAU is enabled: is it a module ? > No. > >Beyond that, perhaps FRAMEBUFFER_CONSOLE needs to be set ? > Is set in the kernel. > > > >The only references to KMS in _my_ (ATI) config are DRM_KMS_HELPER > >and DRM_KMS_FB_HELPER - the first of those is, for me, selected > >(i.e. turned on automatically) by HAS_IOMEM && DRM, and the second > >for you would be selected by DRM_NOUVEAU. > > DRM_KMS_HELPER and DRM_KMS_FB_HELPER are set in the kernel. > > >ĸen > Can you help me to understand what "[drm] KMS not enabled" means? > Short answer: it means "something is wrong". In itself, not particularly helpful. I've just found another suggestion - perhaps a _different_ kernel framebuffer driver has grabbed the framebuffer. Almost a year ago, I was trying to get a decent-sized xorg display from qemu using the KMS driver. My memory says that I had to turn off all the other FB kernel drivers (I think vga was probably my problem). ĸen -- Il Porcupino Nil Sodomy Est! (if you will excuse my latatian) aka "The hedgehog song" -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
