On Sun, 2010-03-07 at 16:13 +0100, Brice Goglin wrote: > Michel Dänzer wrote: > > On Sun, 2010-03-07 at 13:46 +0100, Alexey Feldgendler wrote: > > > >> On Sun, 07 Mar 2010 10:14:17 +0100, Brice Goglin > >> <brice.gog...@ens-lyon.org> wrote: > >> > >> > >>> You probably should enable KMS in your kernel. > >>> > >> Tried this now by passing radeon.modeset=1 to the kernel. This resulted in > >> > >> the following failure in the X.org log: > >> > >> (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version > >> mismatch. > >> [dri] This chipset requires a kernel module version of 1.17.0, > >> [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy > >> modesetting, upgrade your kernel. > >> [dri] If using kernel modesetting, make sure your module is > >> [dri] loaded prior to starting X, and that this driver was built > >> [dri] with support for KMS. > >> [dri] Disabling DRI. > >> > > > > Looks like the driver wasn't built with KMS support. Maybe the build > > dependencies are too lax. > > > > He's using i386, that's what I uploaded. I see "Kernel modesetting: > yes" at the end of my build log, and I get KMS on my r300 machines. > Strange...
Hmm, the line (II) [KMS] drm report modesetting isn't supported. in the X log file indicates that drmCheckModesettingSupported() fails, i.e. can't find some files in /sys . Alexey, what does find /sys/bus/pci/devices/*/ -name \*controlD\* say for you? Note that the asterisk and slash at the end of the second term are critical, otherwise there will be no results. -- Earthling Michel Dänzer | http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1267976033.8327.3193.ca...@thor.local
