On Fri, 23 Jul 2004, A.Sulaiman wrote:
> I have spent over a week trying various XF86Config options,
> and have exhaustively searched the net to no avail.
> I look forward to any help on this problem.
> My system is a PIII-500 Dell Optiplex GX1 originally with just an
> on board ATI Mach64 ("ATI|3D Rage Pro AGP 1X/2X, 8MB" ) and runs
> a standard FedoraCore1 (fresh installation). Everything generally
> worked well (with lots of memory, fast disk, fvwm window manager,
> firefox and of course linux, the PIII is still as quick as the
> rest of them, even with scores of active windows).
> Due to an office move, I recently have to give up my 19" trinitron
> display on 1600x1200 to a 17" LCD which is limited to 1280x1024.
> A second LCD was available, so I added an old 2MB S3 Trio64V PCI
> card to attach it to. It immediately become the primary monitor.
> Dell BIOS have no option to switch the default monitor selection.
> This is a real bummer, as I cannot get the other LCD monitor
> attached to the ATI Mach64 to work, I am now restricted to
> just 1024x768 with the S3 Trio.
> There don't seem to be any problem with the h/w BIOS boot and linux
> initialisations in recognizing the two display cards.
> The snag seems to occur during XFree86 initialisation - the dreaded
> "(EE)" message.
> Note: I have attached both my XFree86.0.log XF86Config files in
> it's entirety.
> Here are some extracts from /var/log/XFree86.0.log:
> (**) ATI(1): Chipset: "mach64".
> (**) ATI(1): Depth 16, (--) framebuffer bpp 16
> (II) Loading sub module "int10"
> (II) LoadModule: "int10"
> (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
> (EE) ATI(1): Cannot read V_BIOS
> (WW) ATI(1): Unable to initialise int10 interface.
> (EE) ATI(1): Adapter has not been initialised.
> (II) UnloadModule: "ati"
> (II) UnloadModule: "int10"
> (II) UnloadModule: "atimisc"
> (II) Unloading /usr/X11R6/lib/modules/drivers/atimisc_drv.o
This is a system BIOS issue, a problem particularly common with Dell's
lobotomised BIOSes. And there's very little the driver can do about it.
Depending on your kernel, you _might_ be able to get past this point by
configuring it to use atyfb to drive the Rage Pro.
Marc.
+----------------------------------+-----------------------------------+
| Marc Aurele La France | work: 1-780-492-9310 |
| Computing and Network Services | fax: 1-780-492-1729 |
| 352 General Services Building | email: tsi@xxxxxxxxxxx |
| University of Alberta +-----------------------------------+
| Edmonton, Alberta | |
| T6G 2H1 | Standard disclaimers apply |
| CANADA | |
+----------------------------------+-----------------------------------+
XFree86 developer and VP. ATI driver and X server internals.
_______________________________________________
XFree86 mailing list
XFree86@xxxxxxxxxxx
http://XFree86.Org/mailman/listinfo/xfree86
