From owner-freebsd-hardware@FreeBSD.ORG Sat Jul 15 05:45:42 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D31016A4DE for ; Sat, 15 Jul 2006 05:45:42 +0000 (UTC) (envelope-from wolfie@xnet.co.nz) Received: from oberon.wxnz.net (oberon.wxnz.net [58.28.6.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9276043D46 for ; Sat, 15 Jul 2006 05:45:41 +0000 (GMT) (envelope-from wolfie@xnet.co.nz) Received: from xnet.co.nz (callisto.wxnz.net [58.28.6.10]) by oberon.wxnz.net (Postfix) with ESMTP id 20E562B9A02 for ; Sat, 15 Jul 2006 17:45:40 +1200 (NZST) Received: from ip-58-28-128-125.ubs-dsl.xnet.co.nz (ip-58-28-128-125.ubs-dsl.xnet.co.nz [58.28.128.125]) by webmail.xnet.co.nz (Horde MIME library) with HTTP; Sat, 15 Jul 2006 17:45:40 +1200 Message-ID: <20060715174540.z7kacu059c0oocgw@webmail.xnet.co.nz> Date: Sat, 15 Jul 2006 17:45:40 +1200 From: wolfie@xnet.co.nz To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.1) Subject: Genius slimstar pro keyboard X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 05:45:42 -0000 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: port 0x60,0x64 irq 1 on acpi0 atkbd0: 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.