[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Alt+Cont+F(1,2,...) not responding



On Wed, Feb 25, 2004 at 03:09:01PM -0500, Antonio Rodriguez wrote:
> On Wed, Feb 25, 2004 at 09:53:34PM +1100, Tim Connors wrote:
> > Antonio Rodriguez <arodriguez31@cfl.rr.com> said on Wed, 25 Feb 2004 04:58:05 -0500:
> 
> > 
> > !seems X4.3 broke Xemacs. Try removing these again later
> > keycode  67 = F1
> > keycode  68 = F2
> > keycode  69 = F3
> > keycode  70 = F4
> > keycode  71 = F5
> > keycode  72 = F6
> > keycode  73 = F7
> > keycode  74 = F8
> > keycode  75 = F9
> > keycode  76 = F10
> > keycode  95 = F11
> > keycode  96 = F12
> > 
> > or something similar. Except now, you have shifted function keys in
> > xemacs, but can't switch consoles.
> > 
> > Fsck, and I hate 4.3 for other reasons too. And it looks like we can't
> > use 4.4 now, because of the license change.
> > 
> 
> We will see what happens. Here goes another one: I have noticed that
> if I have enabled in my locale iso-8859-15 (usually I pick it for
> English and Spanish), then afterstep, fvwm2 (and may be others) can't
> work. So I have to revert every time that I want to use these
> window managers to only 8859-1.
> Stinks, but I haven't figured out why.
> 

In case someone has the same problem, for the record:
Seemingly, there is some issue with the ati driver provided by ati.com
and X 4.3. My best solution was to revert to X 4.2, and to get rid of
the ati binary driver. I am working with vesa, the only driver that
works with my video card (from the GPL ones). Flickering and not as
good as the one from ati for 4.2, but at least doesn't get in the way
in all upgrades and so forth. I was already getting tired of handling
and fixing by hand the mesa.libs and related crap because of the ati
driver.
ICTHSOE



Reply to: