On 25.03.2010 10:53, Julien Cristau wrote:
> On Thu, Mar 25, 2010 at 09:47:43 +0100, Michel Dänzer wrote:
>
>> The above means that the X driver is using UMS whereas KMS is enabled in
>> the kernel. This results in a conflict for hardware access and cannot
>> work properly.
>>
>> It's usually cau
On Thu, 2010-03-25 at 10:53 +0100, Julien Cristau wrote:
> On Thu, Mar 25, 2010 at 09:47:43 +0100, Michel Dänzer wrote:
>
> > The above means that the X driver is using UMS whereas KMS is enabled in
> > the kernel. This results in a conflict for hardware access and cannot
> > work properly.
> >
>
On Thu, Mar 25, 2010 at 11:21:45 +0100, Xavier Bestel wrote:
> On Thu, 2010-03-25 at 10:53 +0100, Julien Cristau wrote:
> > On Thu, Mar 25, 2010 at 09:47:43 +0100, Michel Dänzer wrote:
> >
> > > The above means that the X driver is using UMS whereas KMS is enabled in
> > > the kernel. This result
On Thu, Mar 25, 2010 at 09:47:43 +0100, Michel Dänzer wrote:
> The above means that the X driver is using UMS whereas KMS is enabled in
> the kernel. This results in a conflict for hardware access and cannot
> work properly.
>
> It's usually caused by the radeon kernel module being loaded too lat
On Don, 2010-03-25 at 03:15 +0100, Vedran Furač wrote:
> Source: xserver-xorg-video-ati
> Version: 1:6.12.192-2
>
> Current Operating System: Linux antares 2.6.32-4-amd64
> (II) [KMS] drm report modesetting isn't supported.
> (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version
>
Source: xserver-xorg-video-ati
Version: 1:6.12.192-2
Current Operating System: Linux antares 2.6.32-4-amd64
(II) [KMS] drm report modesetting isn't supported.
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version
mismatch.
[dri] This chipset requires a kernel module version of 1.17
6 matches
Mail list logo