Hi,

> ok, i have found that the combination of removing config.cache, linking 
> /usr/include/linux, and --enable-linux-evdev gets it to say "yes".  
> compilation & installation now works just peachy.  thanks.

O.K. - correct.

> > You did set GGI_INPUT - did you ? 
> 
> yep, i'm using 
> 
> export GII_INPUT=linux-evdev:/dev/input/event0
> export GGI_DISPLAY=fbdev:/dev/fb1

Read carefully: 
> > You did set GGI_INPUT - did you ?

You did set GII_INPUT, but that is ignored in G _G_ I applications, as those
never open a GII input with argument NULL, but rather open the additional
inputs from GGI_INPUT themselves and join them. So try:

export GGI_INPUT=linux-evdev:/dev/input/event0
export GGI_DISPLAY=fbdev:/dev/fb1

> unfortunately, after building it through proper means, monitest, and xggi, 
> still fail to access the new keyboard.  they access the old 
> "console keyboard" though, so i can still quit the applications.

Yeah. Expected behavior, see above. In case you want to do true multihead,
you can give the -noinput option to the fbdev target to disable main 
keyboard, once you have the secondary keyboard running.

Oh - and "inputdump" from libggi/programs/utils should help you diagnosing
input related problems.

> other notes:  i've also tried /dev/input/event1 (a usb mouse), and it ends 
> up grabbing the /dev/mouse mouse, even though i've given it no command 
> line to use it.  This is kinda concerning.

The standard mouse and keyboard are autodetermined according to the used
target (fbdev in your case) and thus opened. However you can explicitly 
override the mouse settings in $prefix/etc/ggi/input/linux-mouse (with 
prefix usually being /usr/local - you will know, if you set it differently).

The -noinput will also help, if you want to suppress that "smart" behaviour.

> be careful when testing USB devices with GGI_INPUT.  It can uncover a kernel 
> bug in the 2.4.0-test series USB code that kills the scheduler.  My machine 
> has been rebooted many times these last two weeks :)

Ouch. Not even Magic SysRq helps a bit in that case probably ...

CU, Andy

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

Reply via email to