Re: [XFree86] How to set up two monitors with ATI Mach64 Rage Pro AGP and S3 Trio64V2 (fwd)
On Wed, 28 Jul 2004, Asri Sulaiman wrote: Marc Aurele La France wrote: Your options, at this point, are to talk to Dell (dead end), give up on the onboard adapter in multihead, replace your motherboard, or get a system that's not so broken. Or, as I suggested above, atyfb _might_ come in handy for a change. I would like to try atyfb first. But please forgive my ignorance. What would be the best way to set it up? I found atyfb.o in /lib/modules/2.4.22-1.2115.nptl/kernel/drivers/video/aty modprobe atyfb seems ok at first, but system hang when I do init 3. Well, I did say atyfb _might_ work, not _would_ work. Put modprobe in rc.local, and it hang during boot. (Fortunately I found the install CD needed to do a rescue. A good side effect: it moved me to convert all my ext2 partition to ext3 so recovery would not be so long next time I hit reset) Adding Load atyfb in the XF86Config file, Section Module: it says module not found in XF86 log. Right. atyfb is a kernel module, not an XFree86 one. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] How to set up two monitors with ATI Mach64 Rage Pro AGP and S3 Trio64V2 (fwd)
Marc Aurele La France wrote: Your options, at this point, are to talk to Dell (dead end), give up on the onboard adapter in multihead, replace your motherboard, or get a system that's not so broken. Or, as I suggested above, atyfb _might_ come in handy for a change. Hi, I would like to try atyfb first. But please forgive my ignorance. What would be the best way to set it up? I found atyfb.o in /lib/modules/2.4.22-1.2115.nptl/kernel/drivers/video/aty modprobe atyfb seems ok at first, but system hang when I do init 3. Put modprobe in rc.local, and it hang during boot. (Fortunately I found the install CD needed to do a rescue. A good side effect: it moved me to convert all my ext2 partition to ext3 so recovery would not be so long next time I hit reset) Adding Load atyfb in the XF86Config file, Section Module: it says module not found in XF86 log. I am running the standard Fedora Core1: Kernel : 2.4.22-1.2115.npt1 XFree86: Version 4.3.0 Thank You for your reply -Asri Sulaiman ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] How to set up two monitors with ATI Mach64 Rage Pro AGP and S3 Trio64V2 (fwd)
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: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] How to set up two monitors with ATI Mach64 Rage Pro AGP and S3 Trio64V2 (fwd)
On Tue, 27 Jul 2004, Jay R. Ashworth wrote: On Tue, Jul 27, 2004 at 08:16:32AM -0600, Marc Aurele La France wrote: 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. Would it be practical to teach XFree to let the user lie to it, and pretend to be the BIOS? I know it would be another config file (or extension), but this seems a fairly common problem. Is the problem just that the BIOS won't tell X what it needs to know, or does it actively get in the way? Such things as video memory timing and the like are VERY adapter-specific, making it quite unrealistic for the driver to perform adapter initialisation. Thus the driver requires that the adapter be previously initialised or have a BIOS available. This is simply a consequence of ATI's adapter design and there's dick-all the driver can do about it. One could, I suppose, boot with the onboard adapter as primary, save its initialised BIOS somewhere, and have int10 use that copy in the multihead situation. But the code to do that (securely or not) just isn't there. Your options, at this point, are to talk to Dell (dead end), give up on the onboard adapter in multihead, replace your motherboard, or get a system that's not so broken. Or, as I suggested above, atyfb _might_ come in handy for a change. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 developer and VP. ATI driver and X server internals. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] How to set up two monitors with ATI Mach64 Rage Pro AGP and S3 Trio64V2 (fwd)
On Tue, Jul 27, 2004 at 02:56:21PM -0600, Marc Aurele La France wrote: On Tue, 27 Jul 2004, Jay R. Ashworth wrote: On Tue, Jul 27, 2004 at 08:16:32AM -0600, Marc Aurele La France wrote: 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. Would it be practical to teach XFree to let the user lie to it, and pretend to be the BIOS? I know it would be another config file (or extension), but this seems a fairly common problem. Is the problem just that the BIOS won't tell X what it needs to know, or does it actively get in the way? Such things as video memory timing and the like are VERY adapter-specific, making it quite unrealistic for the driver to perform adapter initialisation. Thus the driver requires that the adapter be previously initialised or have a BIOS available. This is simply a consequence of ATI's adapter design and there's dick-all the driver can do about it. Ok. I wasn't sure whether the problem was that the card was ready to go but the BIOS neglected to tell the server something that the user could, or if the problem was that that card was uninitialized. One could, I suppose, boot with the onboard adapter as primary, save its initialised BIOS somewhere, and have int10 use that copy in the multihead situation. But the code to do that (securely or not) just isn't there. Sure. Your options, at this point, are to talk to Dell (dead end), give up on the onboard adapter in multihead, replace your motherboard, or get a system that's not so broken. Or, as I suggested above, atyfb _might_ come in handy for a change. Someone else's options; I was just kibitzing. Some people actually *do* subscribe to this list. :-) Cheers, -- jra -- Jay R. Ashworth[EMAIL PROTECTED] Designer Baylink RFC 2100 Ashworth AssociatesThe Things I Think'87 e24 St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274 You know: I'm a fan of photosynthesis as much as the next guy, but if God merely wanted us to smell the flowers, he wouldn't have invented a 3GHz microprocessor and a 3D graphics board. -- Luke Girardi ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
