Hi,
Pene Chamuscado del Caballo a écrit:
Yes, this means that DRI and DRM are not being initialized. I had the
same problem, but I can't remember the exact steps I took to resolve
it. I beleive you need to load the module 'agpgart' if it is not
already built into the kernel, and then load your agp
>
> That's strange, most of the lines about dri and drm are OK (begin with
> "(II)"). But there is only one failure in XFree86.1.log :
>
> (==) R128(0): Write-combining range (0xe400,0x100)
> (II) R128(0): [drm] drmSetBusid failed (6, PCI:1:0:0)
>
> (EE) R128(0): [dri] DRIScreenInit fail
Hi,
First, here is the result of glxinfo with the libGL debug flag :
bash-2.05a$ export LIBGL_DEBUG=1
bash-2.05a$ glxinfo
name of display: :0.0
libGL error: drmMap of sarea failed
display: :0 screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx ext
On Sat, 04 Sep 2004 the mental interface of
Nicos Gollan told:
> On Sat, 04 Sep 2004 16:14:29 +0200
> Prakash Countcham <[EMAIL PROTECTED]> wrote:
>
> > When I launch an application which use libGL (openoffice, glGo, licq,
> > glxinfo, etc.) I have the following error message (even if the
> > ap
On Sat, 04 Sep 2004 16:14:29 +0200
Prakash Countcham <[EMAIL PROTECTED]> wrote:
> When I launch an application which use libGL (openoffice, glGo, licq,
> glxinfo, etc.) I have the following error message (even if the
> application works) :
>
> libGL error: drmMap of sarea failed
That sounds lik
On Wed, Nov 05, 2003 at 01:00:58PM +, Richard Kimber wrote:
>
> Some apps give an error when started saying:
>
> libGL error: failed to open DRM: Operation not permitted
> libGL error: reverting to (slow) indirect rendering
>
> XFree86.0.log says:-
> MGA(0): Direct rendering enabled
>
> Is
6 matches
Mail list logo
