[Cooker] fix proposal: XFree86
This updated package will fix XFree86 running on the alpha (perhaps also other non-ix86 platforms -- just change the "%ifarch alpha" into "%ifnarch %ix86") with MGA hardware. Take a look at this e-mail from Jay Estabrook below. http://d10179.dtk.chello.nl/build/fixes/cooker/XFree86-4.0.2-2mdk.src.rpm http://d10179.dtk.chello.nl/build/fixes/cooker/XFree86-4.spec http://d10179.dtk.chello.nl/build/fixes/cooker/XFree86-4.spec.diff http://d10179.dtk.chello.nl/build/fixes/cooker/XFree86-4.spec.orig Can this fix please be included in the next release (the only thing touched was the .spec file)? Stefan === Subject:Re: XFree-4.0.2 mga alpha Date: Wed, 27 Dec 2000 10:22:46 -0500 From: Jay Estabrook [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] References: 1 , 2 On Mon, Dec 25, 2000 at 10:49:41PM -0500, Christopher C. Chimelis wrote: On Sun, 24 Dec 2000, Stefan van der Eijk wrote: The alpha (miata) has a 4Mb Matrox Millienium II card in it... The problem probably lies in the mga_drv.o module (see the error messages below): Any idea's? Check to see if the modules are stripped. For some reason, I have had nothing but problems when trying to use modules that are stripped on Alpha. I haven't yet had time to see why this happens, but the "unresolved symbol" problems go away if the modules are unstripped (at least for the two cards that I've tried...s3virge and tdfx). Been there, done that... ;-} The problem is that the Matrox HAL was enabled by default at a very late date, and not tested on Alpha, if that's even possible. The HAL is, IIRC, a low-level library between the server and the card that Matrox wants to supply, and it may be in binary only at the moment, source later. So, IIRC, the patch for the build was to put: #define UseMatroxHalNO in the host.def file before starting the build. The only thing affected, again AFAIK, would be the mga_drv.o. Good luck. --Jay++ - Jay A EstabrookAlpha Engineering - LINUX Project Compaq Computer Corp. - MRO1-2/K20 (508) 467-2080 200 Forest Street, Marlboro MA 01752 [EMAIL PROTECTED] - ___ Axp-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/axp-list
Re: [Cooker] fix proposal: XFree86
Stefan van der Eijk wrote: This updated package will fix XFree86 running on the alpha (perhaps also other non-ix86 platforms -- just change the "%ifarch alpha" into "%ifnarch %ix86") with MGA hardware. Take a look at this e-mail from Jay Estabrook below. http://d10179.dtk.chello.nl/build/fixes/cooker/XFree86-4.0.2-2mdk.src.rpm http://d10179.dtk.chello.nl/build/fixes/cooker/XFree86-4.spec http://d10179.dtk.chello.nl/build/fixes/cooker/XFree86-4.spec.diff http://d10179.dtk.chello.nl/build/fixes/cooker/XFree86-4.spec.orig Can this fix please be included in the next release (the only thing touched was the .spec file)? Stefan === Subject:Re: XFree-4.0.2 mga alpha Date: Wed, 27 Dec 2000 10:22:46 -0500 From: Jay Estabrook [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] References: 1 , 2 On Mon, Dec 25, 2000 at 10:49:41PM -0500, Christopher C. Chimelis wrote: On Sun, 24 Dec 2000, Stefan van der Eijk wrote: The alpha (miata) has a 4Mb Matrox Millienium II card in it... The problem probably lies in the mga_drv.o module (see the error messages below): Any idea's? Check to see if the modules are stripped. For some reason, I have had nothing but problems when trying to use modules that are stripped on Alpha. I haven't yet had time to see why this happens, but the "unresolved symbol" problems go away if the modules are unstripped (at least for the two cards that I've tried...s3virge and tdfx). Been there, done that... ;-} The problem is that the Matrox HAL was enabled by default at a very late date, and not tested on Alpha, if that's even possible. The HAL is, IIRC, a low-level library between the server and the card that Matrox wants to supply, and it may be in binary only at the moment, source later. So, IIRC, the patch for the build was to put: #define UseMatroxHalNO in the host.def file before starting the build. The only thing affected, again AFAIK, would be the mga_drv.o. AFAIK, unless you are including the mgaHALlib for x86 builds, you need to do this as well. I haven't tried that yet, but I've been unable to get any available X 4.0.2 binaries to run on my dual P3 system. John
