Hallo Mick. Thank you very much - it helped. Removing 'video=vesafb:ywrap,mtrr:3 vga=792' from kernel boot options, and framebuffer-related stuff in kernel config, especially:
# CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set # CONFIG_FB_BACKLIGHT is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # CONFIG_FB_VESA is not set # CONFIG_FB_RADEON is not set # CONFIG_DISPLAY_SUPPORT is not set # CONFIG_VGACON_SOFT_SCROLLBACK is not set # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set (not all the options were removed by hand, it is just diff of the configs, and maybe, some of them could be enabled without causing problems). Now, there are much more 'drm'-related messages in 'dmesg', and also X.org uses the drm correctly. The 'glxinfo' returns: ... OpenGL vendor string: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on RV370 OpenGL version string: 2.1 Mesa 7.9 OpenGL shading language version string: 1.20 ... It looks good now. Thank you very much for your advice again. Dan On Sunday 16 January 2011 16:52:30 Mick wrote: > On Sunday 16 January 2011 15:18:50 Daniel Tihelka wrote: > > And the kernel seems to use them (when started with boot options > > > 'video=vesafb:ywrap,mtrr:3 vga=792'): > Dan, try removing uvesa/vesa/radeon/etc. framebuffer modules from your > kernel and the above line too from grub when you boot and see if your KMS > radeon driver can now work on its own.
