OK - thanks so far, this is what I found:
Using the r128 from 2.4.23-pre5-ben0 (I now disabled the Xfree 4.0.x
support) and 24/32 bpp I do not have enough memory, but the worse point
is, if I switch to 16bpp there is enough memory but the maschine
instantly crashes while staring up X in 16bpp mode
On Sun, 2003-11-09 at 09:43, Percy Zahl wrote:
>
> (WW) R128(0): Static buffer allocation failed -- need at least 10368 kB
> video memory
[...]
> May be it did not works because I've only 8MB Videoram? There is a
> warning "need at least 10368 kB".
Indeed, you need to run at a lower virtual res
On Sun, 2003-11-09 at 00:24, Michel Dänzer wrote:
> On Sat, 2003-11-08 at 22:50, Percy Zahl wrote:
> >
> > (II) R128(0): Direct rendering disabled
>
> The server log should say why further up.
This is the section above:
(**) R128(0): Using AGP 2x mode
(!!) R128(0): For information on using the
On Sat, 2003-11-08 at 22:50, Percy Zahl wrote:
>
> (II) R128(0): Direct rendering disabled
The server log should say why further up.
> Symbol xf86int10Addr from module
> /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved!
[...]
As Derrik said, these are just cosmetic side effects of the i
Percy Zahl wrote:
I'm experiencing for a while the following problem with the
xserver-xfree86 4.2.1-13 (Debian:unstable)
package (DRI module) using the ATI/r128 drivers on my old PowerBook
G4/400:
Actually those messages you cited have _nothing_ to do with DRI. That's
int10 stuff, which is use
I'm experiencing for a while the following problem with the
xserver-xfree86 4.2.1-13 (Debian:unstable)
package (DRI module) using the ATI/r128 drivers on my old PowerBook
G4/400:
/var/log/XFree86.0.log:
(II) R128(0): Direct rendering disabled
Symbol xf86int10Addr from module
/usr/X11R6/lib/module
6 matches
Mail list logo
