| 1 |
On Tue, 2003-03-18 at 06:11, Alex wrote: |
| 2 |
> I saw the posting for X and dri over the weekend - I have a clamshell iBook |
| 3 |
> Firewire (366mhz with 320 MB) lspci states |
| 4 |
> |
| 5 |
> 00:10.0 VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP |
| 6 |
> 2x (rev 02) - vidoe device running an upto date Gentoo |
| 7 |
> |
| 8 |
> Recived that following error on starting X. Can anyone tell me what V_BIOS |
| 9 |
> is and how i can enable it to be read? |
| 10 |
> |
| 11 |
> thanks - any help would be apprciated |
| 12 |
> __________________________________________________________________________- |
| 13 |
> XFree86 Version 4.3.0 |
| 14 |
> Release Date: 27 February 2003 |
| 15 |
> X Protocol Version 11, Revision 0, Release 6.6 |
| 16 |
> Build Operating System: Linux 2.4.20-ppc-r2 ppc [ELF] |
| 17 |
> Build Date: 16 March 2003 |
| 18 |
> Before reporting problems, check http://www.XFree86.Org/ |
| 19 |
> to make sure that you have the latest version. |
| 20 |
> Module Loader present |
| 21 |
> Markers: (--) probed, (**) from config file, (==) default setting, |
| 22 |
> (++) from command line, (!!) notice, (II) informational, |
| 23 |
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown. |
| 24 |
> (==) Log file: "/var/log/XFree86.0.log", Time: Tue Mar 18 08:18:35 2003 |
| 25 |
> (==) Using config file: "/etc/X11/XF86Config-4" |
| 26 |
> (EE) R128(0): Cannot read V_BIOS (5) |
| 27 |
> Symbol DRIGetDeviceInfo from module |
| 28 |
> /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved |
| 29 |
> Symbol drmGetInterruptFromBusID from module |
| 30 |
> /usr/X11R6/lib/modules/drivers/r128_drv.o is un |
| 31 |
> Symbol drmCtlInstHandler from module |
| 32 |
> /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolve |
| 33 |
> Symbol drmCtlUninstHandler from module |
| 34 |
> /usr/X11R6/lib/modules/drivers/r128_drv.o is unresol |
| 35 |
> Symbol drmAgpBase from module /usr/X11R6/lib/modules/drivers/r128_drv.o is |
| 36 |
> unresolved! |
| 37 |
> |
| 38 |
> *** If unresolved symbols were reported above, they might not |
| 39 |
> *** be the reason for the server aborting. |
| 40 |
> |
| 41 |
> Fatal server error: |
| 42 |
> Caught signal 11. Server aborting |
| 43 |
> ___________________________________________________________________________ |
| 44 |
|
| 45 |
Do you have '/dev/agpgart' and DRI built into your kernel (or as a |
| 46 |
module)? |
| 47 |
|
| 48 |
r. |
| 49 |
|
| 50 |
-- |
| 51 |
gentoo-ppc-user@g.o mailing list |
Archives