Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!menudo.uh.edu!sugar!karl From: karl@NeoSoft.com (Karl Lehenbauer) Subject: Re: [XFree86] Help needed badly Organization: NeoSoft Communications Services -- (713) 684-5900 Date: Mon, 23 Nov 1992 04:45:32 GMT Message-ID: <By5Jvx.8tI@NeoSoft.com> References: <1992Nov22.203129.17299@ultb.isc.rit.edu> Lines: 21 In article <1992Nov22.203129.17299@ultb.isc.rit.edu> sxx4519@ultb.isc.rit.edu (S.X. Xue) writes: >A suggestion I >would give here is to redirect the errors to a file by > xinit >& err;sync >then you will you some error messages that you don't see on the screen by >catting the file "err." In my case, I found out the permission of my mouse >port (com1) and the font path were not set properly. Yes, redirecting xinit is essential to figuring out problems. I'd like to point out, too, that even if you're not getting your card switched into graphics code, you won't see xinit's error output unless you save it off. In my case it couldn't find the entry in the modem DB. Now we're up with a Farenheit 1280! -- -- Email info@NeoSoft.com for info on getting interactive Internet access. "Turn on your hot tub by email now. Ask me how."