[Ann.: Could you try to make the lines wrap at a suitable place ? TNX.]

> I tested my USB keyboard by smacking keys on it, while nothing happened. 

AFAIK this is correct behaviour, as the USB keyboard isn't considered to be
a primary input device and thus ignored by the Linux console, which is a 
design flaw IMHO, but I won't complain any more about the broken design of
the Linux console subsystem.

> Then i typed "cat /dev/Input0", and smacked some more keys....  strange
> strings scrolled past my screen showing that the kernel side works.

Yes. That sounds good.

> Then i downloaded the ggi 7/28/00 snaphot, and compiled libggi.  when i 
> typed ./configure it said "checking if we should build linux-evdev inputlib
> ... no".  That obviously wasn't good, so i looked in ./configure and found
> ... some possible options.  i tried "./configure --enable-linux-evdev" and
> ... "./configure--enable-linux_evdev".  neither made any differnce.

Hmm - CVS isn't responsive right now. I'd have to upgrade to have a look.
Usually these should force it.

> I noticed in config.h that it said i do not have a linux/input.h header 
> file.  so i looked and /usr/include/linux/input.h didn't exist, since my 
> glibc6 was compiled with a 2.2 kernel.  

That's a bit strange. On my system, /usr/include/linux already _is_
symlinked to /usr/src/linux/include/linux ... And I don't think I did this
by hand ...

> i tried linking /usr/include/linux to /usr/src/kernel-headers-2.4.0-test4, 
> and that didn't seem to help...  don't know why.

Did you remove config.cache ?

> at this time i tried setting export GII_INPUT=/dev/Input0, and running 
> mhub.  mhub complained that it couldn't load linux-evdev.so.

Yeah, as it wasn't compiled.

> anyway, eventually i just decided to cd to the linux-evdev directory, 
> and typed "make; make install", which successfully made the target 
> and installed it in /usr/local/...

In that case configure was at fault. If it wasn't the "stale config.cache"
problem, we should investigate.

> I tried running mhub and while it no longer complined about finding 
> linux-evdev.so, i couldn't figure out what mhub was supposed to do, 
> so it wasn't a good test of the keybaord ;)

Mhub is a mouse-translator.

> Then i ran monitest, and it totally ignores the evdev device, 
> and uses the main keyboard.   What am i doing wrong?

You did set GGI_INPUT - did you ? 

The usual syntax is "GGI_INPUT=target:options" btw.

Also always mind the difference between GGI and GII.

> (after getting this all written, i just realized a question..... 
> does monitest use GII?  if not, what programs do?)

All LibGGI programs implicitly use LibGII, unless you do really weird
contortions to avoid it. However they use their own way of detecting the
right inputs to use for a given display type, so they also have their own
override variables.

> (by the way, my old [EMAIL PROTECTED] account has been revoked....  
>  wonder why? ;)

Umm - I have no idea ... I thought hotmail was part of M$, which should
really like that address (they say, they appreciate customer feedback).

CU, ANdy

-- 
= Andreas Beck                    |  Email :  <[EMAIL PROTECTED]> =

Reply via email to