Date: Sat, 15 Jul 2006 08:37:59 +1200 From: wolfie@xnet.co.nz To: freebsd-hackers@freebsd.org Subject: Genius slimstar pro keyboard Message-ID: <20060715083759.k6znpbil1wswcsc8@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) with =20 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 =20 the spades symbol, for example). If I hit d, it is the same as hitting =20 ctrl+d. It does output the same symbols for each key, so at least =20 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 =20 AT keyboard starts outputting the same characters as the USB keyboard. =20 I have also tried without the AT keyboard plugged in, there is no =20 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: =20 Inappropriate ioctl for device. When I try a kbdcontrol -k /dev/ukbd0 =20 I get the message: kbdcontrol: cannot open /dev/ukbd0: Device busy. =20 When I try to disconnect the USB keyboard from the kbmux, I get: =20 kbdcontrol: unable to obtain keyboard information: Inappropriate ioctl =20 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 =20 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 =20 relating file, ukbd.c or one of the 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?20060715083759.k6znpbil1wswcsc8>