Linux Easy Access Keyboard

On Wed, 15 Dec 2004 13:34:43 -0500, Sheldon Bernard Lee Wen
<sheldon.leewen@...> wrote:
>  Hello,
>  
>  I know there are some people out there that have keyboards with keys that
> do not work unless a setkeycode command is run to bind that scancode to a
> keycode. In the lineakd cvs package there is now a utils/ directory with the
> evtest program in it. I need people to checkout that package from the CVS
> and compile the evtest program (you'll have to do make -f Makefile.dist;
> ./configure first, then go into the utils directory and just type make.)
>  
>  Please report to me if those keys work w/o the setkeycodes command being
> run for those keys. 
>  

How do I set the commands with this new feature, do you have some
documentation about it?
I have an Acer Aspire 1406LC Notebook and currently use lineak + the
omnibook driver (omke.sourceforge.net) with following configuration:

----------On systemstartup:
ebegin "Setting extra keycodes "
        setkeycodes \
                e071 220 \
                e073 221 \
                \
                e06e 222 \
                e064 223 \
                e017 224 \
                \
                e018 225 \
                e016 226 \
                \
                e059 227 \
                e078 228 \
                \
                e006 229 \
                e013 230 \
                e034 231
        #e018 94 
        #brightness release: e059 96
        #sometimes: e078 97
eend $?
-----------------end

I did not yet request these for inclusion as the values above and here
are chosen randomly by me, I just took, what worked.
------------/etc/lineak/lineakkbd.conf:
[aceraspire]
 brandname = "ACER"
 modelname = "AS3000 (User Defined)"
        [KEYS]
                Internet        = 196
                Launch          = 197

                Mute|Unmute     = 160
                FNF1            = 148
                FNF2            = 202
                Sleep           = 101
                Hibernate       = 212

                Wifi            = 237
                #FNRelease      = 215

                MP3             = 217
                CD              = 216
                Play|Pause      = 162
                Stop            = 164
                Next            = 153
                Previous        = 144
                MediaOff        = 218
        [END KEYS]
[END aceraspire]
-----------------end



----------------------/etc/lineak/lineakd.conf:
Internet        = "sudo -u stefan env DISPLAY=':0.0'
XAUTHORITY='/home/stefan/.Xauthority' /usr/bin/firefox http://www.heise.de"
Launch          = "sudo -u stefan env DISPLAY=':0.0'
XAUTHORITY='/home/stefan/.Xauthority' /usr/bin/gmplayer
http://64.236.34.67:80/stream/1006 -cache 256"

Mute|Unmute     = "/home/stefan/mute"
FNF1            = ""
FNF2            = "/sbin/halt"
Sleep           = "/usr/sbin/hibernate -F/etc/hibernate/sleep.conf"
Hibernate       = "/usr/sbin/hibernate -F/etc/hibernate/hibernate.conf"

Wifi            = ""
#FNRelease      = ""

MP3             = ""
CD              = ""
Play|Pause      = ""
Stop            = ""
Next            = ""
Previous        = ""
MediaOff        = ""
-----------------end


Kind regards
Stefan Schweizer

On Wed, 15 Dec 2004 14:40:22 -0500, Sheldon Bernard Lee Wen
<sheldon.leewen@...> wrote:
>  cat /proc/bus/input/devices
>  Find the one for your keyboard and note the event number, eg.
>  
>  I: Bus=0003 Vendor=045e Product=001d Version=0111
>  N: Name="Microsoft Natural Keyboard Pro"
>  P: Phys=usb-0000:00:1f.2-2.1/input1
>  H: Handlers=kbd event1
>  B: EV=10000b
>  B: KEY=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
> ffffffff ffff0000 38000 39fa d843d7a9 9e0000 0 0 1
>  B: ABS=1 0
>  
>  notice the line Handlers=kbd event1
>  
>  so then you  can run evtest as:
>  evtest /dev/input/event1

I can use 2 drivers for my laptops hotkeys: acerhk and omnibook.
With omnibook I have no change on cat /proc/bus/input/devices
With acerhk I see the following appended:

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name=""
P: Phys=
H: Handlers=kbd 
B: EV=3 
B: KEY=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff 


With both I dont see a /dev/input/eve* device.
Do you have any idea on what to try next?

Kind regards
Stefan Schweizer

On Wednesday 15 December 2004 22:23, Stefan Schweizer wrote:
> On Wed, 15 Dec 2004 14:40:22 -0500, Sheldon Bernard Lee Wen
> <sheldon.leewen@...> wrote:
> >  cat /proc/bus/input/devices
> >  Find the one for your keyboard and note the event number, eg.
> >  
> >  I: Bus=0003 Vendor=045e Product=001d Version=0111
> >  N: Name="Microsoft Natural Keyboard Pro"
> >  P: Phys=usb-0000:00:1f.2-2.1/input1
> >  H: Handlers=kbd event1
> >  B: EV=10000b
> >  B: KEY=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
> > ffffffff ffff0000 38000 39fa d843d7a9 9e0000 0 0 1
> >  B: ABS=1 0
> >  
> >  notice the line Handlers=kbd event1
> >  
> >  so then you  can run evtest as:
> >  evtest /dev/input/event1
> 
> I can use 2 drivers for my laptops hotkeys: acerhk and omnibook.
> With omnibook I have no change on cat /proc/bus/input/devices
> With acerhk I see the following appended:
> 
> I: Bus=0000 Vendor=0000 Product=0000 Version=0000
> N: Name=""
> P: Phys=
> H: Handlers=kbd 
> B: EV=3 
> B: KEY=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff 
> 
> 
> With both I dont see a /dev/input/eve* device.
> Do you have any idea on what to try next?
oops! I forgot notify!

modprobe evdev
is neccessary command to turn on input event interface.
This interface does not exist in the 2.2 and below 
linux kernel serie

Aivils

On Thu, 16 Dec 2004 10:26:57 +0200, Aivils <aivils@...> wrote:
> On Wednesday 15 December 2004 22:23, Stefan Schweizer wrote:
> > On Wed, 15 Dec 2004 14:40:22 -0500, Sheldon Bernard Lee Wen
> > <sheldon.leewen@...> wrote:
> > >  cat /proc/bus/input/devices
> > >  Find the one for your keyboard and note the event number, eg.
> > >
> > >  I: Bus=0003 Vendor=045e Product=001d Version=0111
> > >  N: Name="Microsoft Natural Keyboard Pro"
> > >  P: Phys=usb-0000:00:1f.2-2.1/input1
> > >  H: Handlers=kbd event1
> > >  B: EV=10000b
> > >  B: KEY=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
> > > ffffffff ffff0000 38000 39fa d843d7a9 9e0000 0 0 1
> > >  B: ABS=1 0
> > >
> > >  notice the line Handlers=kbd event1
> > >
> > >  so then you  can run evtest as:
> > >  evtest /dev/input/event1
> 
> modprobe evdev

for acerhk I get event3 for omnibook I have no additional event interface.

on evtest /dev/input/event3 it prints all different keycodes and then:

[...all events...]
    Event code 255 (?)
Testing ... (interrupt to exit)

nothing more then, any ideas?

Stefan

On Thu, 16 Dec 2004 07:24:23 -0500, Sheldon Bernard Lee Wen
<sheldon.leewen@...> wrote:
>  So do you mean that if you press those keys while running evtest nothing
> happens?

exactly that happens.
>  I have noticed this on another keyboard I tested as well, I'd run evtest
> and nothing would happen when I pressed the media keys,
>  only when I pressed the normal keyboard keys.
>  
>  So much for that.... I was hoping for something that would work for all or
> most keyboards w/o requiring X.
> 

I think the 2 drivers I can use are basically broken, and this is
after all a driver issue.
Maybe I will have some other drivers in the future, but for now the
event interface is maybe not in the drivers ..

Stefan

On Thursday 16 December 2004 14:24, Sheldon Bernard Lee Wen wrote:
> So do you mean that if you press those keys while running evtest nothing
> happens?
> I have noticed this on another keyboard I tested as well, I'd run evtest
> and nothing would happen when I pressed the media keys,
> only when I pressed the normal keyboard keys.
> 
> So much for that.... I was hoping for something that would work for all
> or most keyboards w/o requiring X.

Some keyboards, mostly USB , have two event interfaces 1st an 2nd
1st for normal keys
2nd for mutimedia keys
Of course
cat /proc/bus/input/devices
must show it all. That keyboard actualy register two USB devices.
My 3 USB keyboards all register two USB interfaces.

Aivils

> On Thu, 2004-12-16 at 12:15 +0100, Stefan Schweizer wrote:
> 
> > On Thu, 16 Dec 2004 10:26:57 +0200, Aivils <aivils@...> wrote:
> > > On Wednesday 15 December 2004 22:23, Stefan Schweizer wrote:
> > > > On Wed, 15 Dec 2004 14:40:22 -0500, Sheldon Bernard Lee Wen
> > > > <sheldon.leewen@...> wrote:
> > > > >  cat /proc/bus/input/devices
> > > > >  Find the one for your keyboard and note the event number, eg.
> > > > >
> > > > >  I: Bus=0003 Vendor=045e Product=001d Version=0111
> > > > >  N: Name="Microsoft Natural Keyboard Pro"
> > > > >  P: Phys=usb-0000:00:1f.2-2.1/input1
> > > > >  H: Handlers=kbd event1
> > > > >  B: EV=10000b
> > > > >  B: KEY=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
> > > > > ffffffff ffff0000 38000 39fa d843d7a9 9e0000 0 0 1
> > > > >  B: ABS=1 0
> > > > >
> > > > >  notice the line Handlers=kbd event1
> > > > >
> > > > >  so then you  can run evtest as:
> > > > >  evtest /dev/input/event1
> > > 
> > > modprobe evdev
> > 
> > for acerhk I get event3 for omnibook I have no additional event interface.
> > 
> > on evtest /dev/input/event3 it prints all different keycodes and then:
> > 
> > [...all events...]
> >     Event code 255 (?)
> > Testing ... (interrupt to exit)
> > 
> > nothing more then, any ideas?
> > 
> > Stefan
> > 
> > 
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now. 
> > http://productguide.itmanagersjournal.com/
> > _______________________________________________
> > LinEAK-devel mailing list
> > LinEAK-devel@...
> > https://lists.sourceforge.net/lists/listinfo/lineak-devel
> 
> Sheldon Lee-Wen
> 
> Systems Analyst and Architect
> Ottawa Data Center, Unix Services
> CGI Information Systems and Management
> Phone: 613-740-5900 ext 5363
> Fax: 613-749-2201
> Email: sheldon.leewen@...
> 
> 
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sheldon Bernard Lee Wen escribi=C3=B3:

| I know there are some people out there that have keyboards with keys
| that do not work unless a setkeycode command is run to bind that
| scancode to a keycode. In the lineakd cvs package there is now a utils/=

| directory with the evtest program in it. I need people to checkout that=

| package from the CVS and compile the evtest program (you'll have to do
| make -f Makefile.dist; ./configure first, then go into the utils
| directory and just type make.)

Is this trying to solve the problem I have with the Logitech Cordless
Desktop Precision Y-RH35?
Some keys (messenger, webcam, volume up and all function keys)
doesn"t work -no reaction, even in xev:

valinor kernel: atkbd.c: Unknown key pressed (translated set 2, code
0x91 on isa0060/serio0).
valinor kernel: atkbd.c: Use "setkeycodes e011 <keycode>" to make it know=
n.

"evtest" didn't do nothing, none of the unknown keys were seen by xev or
lineak.
I added "setkeycodes e043 189" for every key in boot.local in order to
use multimedia keys. SuSE 9.1 x86
- --
Oscar Curero - Linux user: 306877
- --    GPG keyID: 0xE0EA0B24    --


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBwauH9rf3ZuDqCyQRAuggAKCl98GWKf4f03NMBCP0rpdagnZ4xgCgzUgo
hGIh70a0OID1zIWWWC+C/00=3D
=3Dzr/Y
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sheldon Bernard Lee Wen escribi=C3=B3:
|
|>Is this trying to solve the problem I have with the Logitech Cordless
|>Desktop Precision Y-RH35?
|>Some keys (messenger, webcam, volume up and all function keys)
|>doesn"t work -no reaction, even in xev:
|>
| We are trying to find a more reliable way to do handling of media keys.=

|
|>
|>valinor kernel: atkbd.c: Unknown key pressed (translated set 2, code
|>0x91 on isa0060/serio0).
|>valinor kernel: atkbd.c: Use "setkeycodes e011 <keycode>" to make it
known.
|>
| You are using a keyboard in PS/2 mode or USB?
PS/2 (with a USB->PS/2 adapter).

|>"evtest" didn't do nothing, none of the unknown keys were seen by xev o=
r
|>lineak.
|>I added "setkeycodes e043 189" for every key in boot.local in order to
|>use multimedia keys. SuSE 9.1 x86
|>
| once you added the setkeycodes command did evtest or xev show anything
| for those keys?

Yes, both. Play/pause (F7):

evtest:

Event: time 1103219526.996893, -------------- Config Sync ------------
Event: time 1103220251.305942, type 1 (Key), code 187 (International7),
value 1
Event: time 1103220251.305946, -------------- Config Sync ------------
Event: time 1103220251.403022, type 1 (Key), code 187 (International7),
value 0
Event: time 1103220251.403027, -------------- Config Sync ------------

Xev:

FocusOut event, serial 31, synthetic NO, window 0x4400001,
~    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 31, synthetic NO, window 0x4400001,
~    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 31, synthetic NO, window 0x0,
~    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0=

~           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0=

- --
Oscar Curero - Linux user: 306877
- --    GPG keyID: 0xE0EA0B24    --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD4DBQFBwc+H9rf3ZuDqCyQRAkw2AJ9kEMN5AMsJqeZRsKrIkw47r1Vg7gCYvC12
tgDDBlMVG3Pwrl/5899/xw=3D=3D
=3D/dJp
-----END PGP SIGNATURE-----