Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!news.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!news.uoregon.edu!cs.uoregon.edu!sgiblab!uhog.mit.edu!news.intercon.com!panix!not-for-mail From: tls@panix.com (Thor Lancelot Simon) Newsgroups: comp.os.386bsd.questions Subject: Strange XFree86 problem -- blank white screen? Date: 14 Jan 1994 15:55:59 -0500 Organization: PANIX Public Access Internet and Unix, NYC Lines: 45 Message-ID: <2h70sv$hps@panix.com> NNTP-Posting-Host: panix.com I just installed plain, out-of-the-box NetBSD 0.9 on a Gateway 2000 4DX2-66V (a 486/66DX2 VESA box, in plainspeak) at work. Everything went fine 'till I tried to get XFree86 2.0 running, at which point I was stumped. Ferinstance, X -probeonly gives what seem to be the correct clocks for the Gateway "Rocket" 90C33 card the first, and only the first, time it's run after a reboot. Subsequent executions yield incorrect and clearly bogus values, all within 1 or 2 of 28. Oh well -- that's ignoreable, the card appears to have a 65.3M clock, so I'm using that with a "1024x768" line that's as follows: "1024x768" 65 1024 1064 1272 1304 768 768 789 789 Which works with my Sony 1304 -- sort of! (see below) though it seems to need some slight work around the upper edge. The clocks for my card I'm using are: Clocks 25.40 28.32 65.30 36.30 0.00 28.30 0.00 0.00 0.00 *The problem*: Using these values, the X server starts, and the screen initially flips to a pattern of vertical black-and-white stripes. In fact, if invoked simply as "X", it stays that way. But as soon as any X application is invoked, it changes to all white, and stays like that; subsequent applications cause small flickers as they're invoked, but the screen stays all white and won't change. Eventually I always have to give up and kill the server. Same thing happens with an "800x600" mode of: "800x600" 36 800 824 896 1024 600 601 603 625 Killing the server with a SIGHUP causes a flick to white,and then back to the stripes. (If no application is trying to use it.) Killing the server with SIGINT results in the previous text mode not being reset properly -- some odd mode with the text very wide and partially off the edge of the screen results. Has anyone seen anything like this before? What's the cause?! -- Thor Lancelot Simon tls@panix.COM But as he knew no bad language, he had called him all the names of common objects that he could think of, and had screamed: "You lamp! You towel! You plate!" and so on. --Sigmund Freud