Date: Mon, 16 Jul 2007 03:06:47 +0200 From: Nikola Lecic <nlecic@EUnet.yu> To: Michael Gass <mgass@unix.csbsju.edu> Cc: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>, freebsd-questions@freebsd.org Subject: Re: Garbled text in xterm Message-ID: <200707160106.l6G16grP029895@smtpclu-3.eunet.yu> In-Reply-To: <20070716001503.GA17213@unix.csbsju.edu> References: <20070716001503.GA17213@unix.csbsju.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 15 Jul 2007 19:15:03 -0500 Michael Gass <mgass@unix.csbsju.edu> wrote: > Lowell Gilbert wrote: >=20 > > Hmm. I've never heard of any symptoms quite like this. > > A few stabs in the dark: > > What happened if you used no xorg.conf at all? Did you get the same > > xterm problem? >=20 > > Do you have a locale set? >=20 > Thanks for the response. > 1. If I try to running with no xorg.conf, it just hangs. I think the > equipment is too old for the defaults. > 2. My locale is set to "C" > 3. If I set the DefaultDepth to 1 in Screen, then it works - but of > course there is no color. If I set the DefaultDepth to either 4 or 8, > then I get the garbled text again. I do not think it is the keyboard, > as the garbled text happens right at the prompt, and when I do type, > it garbles, but the correct thing happens. For instance, if I type > "xterm" then the charactors are messed up, but an xterm comes up > (again with garbled text). > 4. I tried having X construct a configure file for me (Xorg > -configure), but same problem. Hello Michael, What happens if you add Option "XaaNoScanlineImageWriteRect" "true" Option "XaaNoScanlineCPUToScreenColorExpandFill" "true" to the Screen section (try Device too)? Try also: Option "Accel" "false" Nikola Le=C4=8Di=C4=87
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707160106.l6G16grP029895>