Date: Fri, 10 May 2002 01:34:20 -0400 From: Scott <scottro@nyc.rr.com> To: "Greg 'groggy' Lehey" <grog@FreeBSD.ORG>, Tuslers PC Repair <Tuslerspcrepair@cox.net> Cc: questions@FreeBSD.ORG Subject: Re: X386 stuff Message-ID: <5.1.0.14.0.20020510012633.00bd9c78@pop-server.nyc.rr.com> In-Reply-To: <20020510144752.B413@wantadilla.lemis.com> References: <002d01c1f7e1$e9b5e9c0$6501a8c0@cox.net> <002d01c1f7e1$e9b5e9c0$6501a8c0@cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 14:47 2002/05/10 +0930, Greg 'groggy' Lehey wrote: >[Format recovered--see http://www.lemis.com/email/email-format.html] > >Overlong lines, presumably representing paragraphs. > >On Thursday, 9 May 2002 at 22:16:56 -0700, Tuslers PC Repair wrote: > > > > > > I am using a Voodoo 5 5500 card with a standard Super VGA monitor > > 1024x768. The best I can get is showing Half the screen, its like the > > screen would need 4 17" monitors to see the whole thing. I figure > > this is probably 640x480 mode. When I go back in and set it to > > 1024x768 it will not even start. How do I configure this. Linux and > > windows runs great on this computer, > >Then so does FreeBSD. You're not complaining about FreeBSD, you're >complaining about XFree86. That's what you (presumably) used with >Linux, you've obviously just misconfigured it. Since you haven't >given any details of what you've done and what happened, the best I >can recommend is to take the XF86Config file from your Linux >configuration. Unless you have an ASUS Motherboard with Duron or Athlon processor. This sounds like the sort of thing that sometimes happens with it. It's fixed in current stable (I suppose that's an oxymoron---I mean that if you cvsup the present version of stable the problem is fixed.) If it is an ASUS MB and you're not yet familiar with cvsup and doing a buildworld, then (Sorry about bad formatting here---all night I've been using mutt but saw this message when I went back into Windows, and am using Eudora, as well as cutting and pasting from an html doc. that I made for myself.....) ....Now I began to suspect the motherboard, an ASUS A7A266. A bit more research showed that this had been noted as a problem since 4.3 RELEASE. It is listed as PR 28418 and can be viewed at http://www.freebsd.org/cgi/query-pr.cgi?pr=28418 Mr. Malone has made a patch--however, I did something wrong and it didn't apply properly. However, here's the trick, given me by Bill Triplett. Just open up /usr/src/sys/i386/i368/i686_mem.c with your favorite text editor. Around line 269 (in vi, it's easy to find--just do :269 while in command mode), you'll see u_int cr4save; mrd = sc->mr_desc; Between those two lines, insert a line return; That's it. Putting in the word return, followed by a semi colon will keep X from doing whatever it's doing with the MTRR, which is what is causing the ASUS boards to lock up when XFree 4.x is started. Then of course, you have to recompile your kernel. So, say your kernel is called MYKERN (Sorry for the lack of originality, but I'm sleepy) cd /usr/src/sys/i386/conf config MYKERN You will then see the thing something like source is ../../compile/MYKERN Don't forget to do make depend So cd ../../compile/MYKERN make depend; make; make install Reboot and you should be good to go. If you aren't using an ASUS MB, then all this is irrelevant. Scott Robbins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.0.20020510012633.00bd9c78>