Michel Dänzer wrote:
> So the X server is 32 bit? If so, there's probably indeed some kind of
> 32/64 bit breakage somewhere, though unlikely related to the warnings in
> the bug report you referenced. It looks like although the X driver
> thinks setting the new memory map parameter succeeded, the
Julien Cristau wrote:
> On Wed, Jun 6, 2007 at 20:32:30 +0200, Brice Goglin wrote:
>
>> Jason Cormie wrote:
>>> [drm:radeon_do_init_cp] *ERROR* Cannot initialise DRM on this card
>>> This card requires a new X.org DDX for 3D
>>>
>> I don't thi
Brice Goglin wrote:
> Jason Cormie wrote:
>> Package: libdrm2
>> Version: 2.3.0-4
>> Followup-For: Bug #324560
>>
>>
>> Could this be the reason that with an amd64 kernel I get this:
>>
>> [drm:radeon_do_init_cp] *ERROR* Cannot initialise DRM on
Package: libdrm2
Version: 2.3.0-4
Followup-For: Bug #324560
Could this be the reason that with an amd64 kernel I get this:
[drm:radeon_do_init_cp] *ERROR* Cannot initialise DRM on this card
This card requires a new X.org DDX for 3D
Whilst it works OK with a 686 kernel?
-- System Information
It seems this problem comes from the utmp record in sessreg.c not being
initialised.
Their is a patch for it below
https://bugs.freedesktop.org/show_bug.cgi?id=1627
the patch uses bzero which is deprecated instead of memset, so maybe it
should be
memset(&u, 0, sizeof(u));
--
Jason Co
5 matches
Mail list logo
