Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Jul 2006 17:45:40 +1200
From:      wolfie@xnet.co.nz
To:        freebsd-hardware@freebsd.org
Subject:   Genius slimstar pro keyboard
Message-ID:  <20060715174540.z7kacu059c0oocgw@webmail.xnet.co.nz>

next in thread | raw e-mail | index | archive | help
Hey all,

I have a Genius slimstar pro USB keyboard. I am having the same =20
problems as other people
are having =20
(http://www.google.com/bsd?hl=3Den&lr=3D&q=3Dgenius+slimstar+pro&btnG=3DSear=
ch) =20
with
this keyboard. There seems to be no resolution to this problem short =20
of buying a new
keyboard.

The problem I'm having is when you hit any key, other than enter, on =20
the USB keyboard, it
outputs garbage (extended ASCII characters like the spades symbol, for =20
example). If I hit
d, it is the same as hitting ctrl+d. It does output the same symbols =20
for each key, so at
least there is some consistency :)

I also have a AT keyboard plugged in which works as it should until I =20
hit a key on the
USB keyboard. If I hit a key on the USB keyboard, the AT keyboard =20
starts outputting the
same characters as the USB keyboard. I have also tried without the AT =20
keyboard plugged
in, there is no change.

I read in another post that disabling all legacy AT support in the =20
kernel could fix this.
I tried this to no avail.

When I use kbdcontrol -i for any keyboard, I get the following =20
message: kbdcontrol:
unable to obtain keyboard information: Inappropriate ioctl for device. =20
When I try a
kbdcontrol -k /dev/ukbd0 I get the message: kbdcontrol: cannot open =20
/dev/ukbd0: Device
busy. When I try to disconnect the USB keyboard from the kbmux, I get: =20
kbdcontrol: unable
to obtain keyboard information: Inappropriate ioctl for device.

The important lines at boot up, in order of appearance, are:
kbd1 at kbdmux0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <aT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
ukbd0: vendor 0x0458 ABBHOME, rev 1.10/1.01, addr 3, iclass 3/1
kbd2 at ukbd0

What I would find really helpful from you people is any idea's about =20
how to move forward
with/resolve this problem. I am happy to trawl through and modify any code.

One idea I have, and correct me if I'm wrong, is to get each =20
individual keyscan code from
the keyboard and map this into the relating file, ukbd.c or one of the =20
related header
files?

If anyone is needing any additional info on this one, just yell out =20
and I will get this
to you.

Thanks in advanced,

Sam.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060715174540.z7kacu059c0oocgw>