Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!newsroom.utas.edu.au!munnari.OZ.AU!uunet!in2.uu.net!news-feed.iguide.com!imci2!news.internetMCI.com!newsfeed.internetmci.com!news.dacom.co.kr!usenet.seri.re.kr!news.kreonet.re.kr!overload.lbl.gov!gracie.lbl.gov!jin From: jin@gracie.lbl.gov (Jin Guojun[ITG]) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Mach64 Xserver problem. Date: 16 Feb 1996 18:45:32 GMT Organization: Lawrence Berkeley Laboratory Lines: 27 Message-ID: <4g2jcc$2bq@overload.lbl.gov> References: <MAGNER.96Feb12110112@hstud1.cs.uit.no> <4fs5mp$hcg@uriah.heep.sax.de> <4g1fma$f33@prometheus.algonet.se> NNTP-Posting-Host: gracie.lbl.gov In article <4g1fma$f33@prometheus.algonet.se>, Peter Landgren <Peter@lwab.se> wrote: >j@uriah.heep.sax.de (J Wunsch) wrote: > >>magner@hstud1.cs.uit.no (Magne Rasmussen) writes: >>> I have an ATI Mach64 Xpression PCI w/2Mb DRAM. When I try to run the >>> Mach64 XServer on a FreeBSD 2.1.0R system, strange things happen: > >>I'm not aware about Mach's terminology, but some of the newer Mach64's >>require a newer Xserver (still beta though) than XFree86 3.1.2. > >>They also require a fix (or hack) to prevent the kernel from stomping >>over register 0x2e8 during sio probing. > >So, please tell me, were do I find this fix? I believe that you need to disable sio3 and higher. Just leave sio[0-1] confiured. You can do it with boot -c or rebuild the kernel. Good luck, -- /-------------- Jin Guojun ------------ v ---- Internet: g_jin@lbl.gov ----\ | Imaging & Distributed Computing | Usenet: ucbvax!g_jin@lbl.gov | | Lawrence Berkeley Laboratory | Bitnet: -- | | 50B-2239, Berkeley, CA 94720 - jin%george.lbl.gov@Csa3.LBL.Gov |