Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!metro!news From: dawes@physics.su.OZ.AU (David Dawes) Subject: Re: XFree86 gives me a blank screen ! [SOLVED] Message-ID: <1992Oct6.071310.6234@ucc.su.OZ.AU> Keywords: X Xfree86 install Sender: news@ucc.su.OZ.AU Nntp-Posting-Host: physics.su.oz.au Organization: School of Physics, University of Sydney, Australia References: <BvEp22.24@news.cso.uiuc.edu> <BvnJMB.K5z@news.cso.uiuc.edu> <1992Oct5.163504.26932@fcom.cc.utah.edu> Date: Tue, 6 Oct 1992 07:13:10 GMT Lines: 50 In article <1992Oct5.163504.26932@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes: >In article <BvnJMB.K5z@news.cso.uiuc.edu> venkat@uxh.cso.uiuc.edu (Venkat) writes: >> I ran xdm and upon checking the xdm-errors file saw error messages >> of the out-of-memory type. Apparently I had not bothered to check >> that the resolutions that I was setting in the Xconfig file would >> fit in the available memory ! >> >> NOTE: Of the different resolutions that I had entered in the Xconfig >> file, only *one* required more memory than that availlable and yet >> *none* of the resolutions would work - would it be possible [in the >> next version, maybe] that XFree86 display atleast the possible >> resolutions rather than come crashing down for one teeny weeny fault > >The reasoning behind this is obviously that the memory for the highest >possible resoloution must be allocated, since dynamicly changing the >resoloution via keyboard command is allowed. To do otherwise could easily >case a crash as a result of your using the ctl-alt-ketpad-plus/minus. At startup, the server sets the (virtual) display size large enough to accomodate all modes specified in the Modes line of the Xconfig file. It then checks if there is enough video memory to support that size. To do it any other way would be too messy, and the consequences of errors in the Xconfig file could be even more confusing than at present. The Xconfig file must be customised for the card you are using. Both the modes and virtual size specified must be consistent with the hardware. BTW, you don't need to use xdm to find the messages printed by the server. Just start the server with: X >& x.out and the messages will be written to x.out. >This could probably be alleviate by "disabling" broken resoloutions -- >but this tends to get ugly fast. > > Terry Lambert > terry@icarus.weber.edu > terry_lambert@novell.com >--- >Any opinions in this posting are my own and not those of my present >or previous employers. David -- ------------------------------------------------------------------------------ David Dawes (dawes@physics.su.oz.au) DoD#210 | Phone: +61 2 692 2639 School of Physics, University of Sydney, Australia | Fax: +61 2 660 2903 ------------------------------------------------------------------------------