Re: XFree86 4.1.0: Cannot read V_BIOS (5)
On 14/06/01 12:13, "Michel Dänzer" <michdaen@iiic.ethz.ch> wrote:
>
> [ trimmed Branden and XFree86@XFree86.Org, this is none of their business. ]
>
> Lars Brinkhoff wrote:
>
>> After upgrading to XFree86 4.1.0-0pre1v1.1 on my PowerMac G4 running
>> Debian GNU/Linux, X doesn't work any more.
>>
>> Seemingly relevant lines from /var/log/XFree86.0.log: (full output below)
>>
>> XFree86 Version 4.1.0 / X Window System
>> (--) PCI: (1.21.0) ATI Rage 128 RE rev 0, Mem @ 0x84000000/26, 0x80088000/14,
>> I/O @ 0x1000/8, BIOS @ 0x800a0000/17
>> (II) Module r128: vendor="The XFree86 Project"
>> compiled for 4.1.0, module version = 4.0.1
>> (II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 RE (PCI),
>> (--) Chipset ATI Rage 128 RE (PCI) found
>> (II) R128(0): PCI bus 1 card 21 func 0
>> (II) R128(0): initializing int10
>> (EE) R128(0): Cannot read V_BIOS (5)
>
> This error has never been fatal. If it were, the server would exit without
> crashing.
>
>> (--) Chipset: "ATI Rage 128 RE (PCI)" (ChipID = 0x5245)
>> Fatal server error:
>> Caught signal 11. Server aborting
>
> The problem is that the vgaHW layer now tries to do ISA I/O using a new
> syscall to get the iobase. Unfortunately, it doesn't seem to work on UniNorth
> machines. For now you'll have to either use Option "UseFBDev" or hack the
> syscall (something with sysconfig_iobase) out of your kernel or X server.
>
>
I have the exact same problem with XFree 4.03 from the new Mandrake 8 PPC,
and i've found nothing better to do than use the fb driver and disable the
r128.
Does anyone have an idea on how we could make this R128 driver work ?
Cheers,
Pejvan
Reply to: