Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:14369 comp.os.386bsd.questions:15213 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!bloom-beacon.mit.edu!news.kei.com!eff!cs.umd.edu!info.usuhs.mil!info.usuhs.mil!not-for-mail From: dobson@info.usuhs.mil (Michael Dobson) Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.questions Subject: Re: Patched XF86_S3 binary for FreeBSD 2.0R? Date: 13 Dec 1994 10:07:19 -0500 Organization: Uniformed Services University of the Health Sciences Lines: 32 Message-ID: <3ckdb7$7n5@info.usuhs.mil> References: <3c7joa$i3k@info.usuhs.mil> <D0J26G.667@ucc.su.OZ.AU> NNTP-Posting-Host: info.usuhs.mil In article <D0J26G.667@ucc.su.OZ.AU>, David Dawes <dawes@physics.su.oz.au> wrote: [ I was asking about a patched S3 server for FreeBSD 2.0-RELEASE] >Which patch are you referring to? The 3.1 S3 server binary for 2.0-RELEASE >is at PL3. I not really sure. Someone a week or so ago described a problem using the 3.1 S3 server on their IBM PS/Value Point that matched the problem I have. They mentioned that the patches to the S3 server fixed it but I don't believe they mentioned a patchlevel. Unfortunately the article has expired here. >If by some chance the ramdac probing is causing a problem on your system, >try adding the following line to the Device section of your XF86Config: > >Ramdac "att20c490" That didn't help any, it still locks up completely immediately after probing when it's setting the initial mode. Running with -probeonly works fine and properly identifies the chip, ramdac, dot clocks, ram size, etc. Another poster suggested using -nonlinear but that also gave the same result. Guess I'm stuck with the VGA16 server for now :-( Mike -- LCDR M. Dobson | NetNews Admin info.usuhs.mil Experimental Hematology Dept | dobson@info.usuhs.mil Armed Forces Radiobiology | Research Institute | I don't have enough rank to speak for DoD