Subject: Re: -current panics
To: None <port-macppc@netbsd.org>
From: Valeriy E. Ushakov <uwe@ptc.spbu.ru>
List: port-macppc
Date: 04/24/2004 21:20:47
Krister Walfridsson <cato@df.lth.se> wrote:

>> (II) R128(0): initializing int10
>>
>> Fatal server error:
>> xf86MapVidMem: could not mmap screen [s=20000,a=a0000] (Invalid argument)
> 
> It looks like you get the error when r128_driver.c is initializing
> int10.
[...]

Note that X -configure will force the loading of int10 anyway, so
simply disabling the use of int10 in r128 driver is not generally
sufficient.



> So you might win by doing:
> 
> Index: r128_driver.c
> ===================================================================
> RCS file: /cvsroot/xsrc/xfree/xc/programs/Xserver/hw/xfree86/drivers/ati/r128_driver.c,v
> retrieving revision 1.1.1.7
> diff -u -r1.1.1.7 r128_driver.c
> --- r128_driver.c       5 Mar 2004 14:28:38 -0000       1.1.1.7
> +++ r128_driver.c       24 Apr 2004 19:40:35 -0000
> @@ -1695,7 +1695,7 @@
> static Bool R128PreInitInt10(ScrnInfoPtr pScrn, xf86Int10InfoPtr *ppInt10)
> {
>     R128InfoPtr   info = R128PTR(pScrn);
> -#if 1 && !defined(__alpha__)
> +#if !defined(__powerpc__) && !defined(__alpha__)
>     /* int10 is broken on some Alphas */
>     if (xf86LoadSubModule(pScrn, "int10")) {
>        xf86LoaderReqSymLists(int10Symbols, NULL);

Nope.  I tried that part of the XFree 4.2 patch and it then fails with
something else that tries to map 0xa0000.

[...]
(WW) R128(0): Cannot read colourmap from VGA.  Will restore with default

Fatal server error:
xf86MapVidMem: could not mmap screen [s=10000,a=a0000] (Invalid argument)


This is on my B&W G3.

SY, Uwe
-- 
uwe@ptc.spbu.ru                         |       Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/            |       Ist zu Grunde gehen