I have a Logitech Cordless Internet Pro kb+mouse. Everything works fine
with appropriate drivers ukbd and ums, but there is no reaction on
multimedia keys on keyboard. In xev I don't see any reaction. As far as
I understand the problem is in ukbd driver (keyboards with ps/2 and
atkbd works fine with mmedia keys) Is there any plan to add support of
multimedia keys to ukbd driver? I try to do it myself, but my knowledge
isn't enough to do this. How to add translation of USB HID codes from
page OC ( page 07 is already translated) ???
In Linux there is no problem with usb keyboard and multimedia keys, but
I don't like Linux.. I like FreeBSD :o)
How-To-Repeat: Try to get any response in xev on multimedia keys on usb keyboard
this bug still applies to the latest -CURRENT:
FreeBSD zardoz.localnet 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Tue Sep 4
23:37:45 CEST 2007 firstname.lastname@example.org:/usr/obj/usr/src/sys/ZARDOZ
ukbd0: <vendor 0x046a product 0x0023, class 0/0, rev 2.00/0.32, addr 2>
nothing new here, it does not work with 7.0-PRERELEASE:
| ukbd0: <vendor 0x046a product 0x0023, class 0/0, rev 2.00/0.27,
| addr 3> on uhub0
Any hints or solutions?
Thanks in advance.
Also F13-F19 on new Apple USB keyboards recognize no scancode.
% sysctl dev.ukbd
dev.ukbd.0.%desc: Apple, Inc Apple Keyboard, class 0/0, rev 2.00/0.69,
dev.ukbd.0.%location: port=1 interface=0
dev.ukbd.0.%pnpinfo: vendor=0x05ac product=0x0221 devclass=0x00
devsubclass=0x00 release=0x0069 sernum="" intclass=0x03 intsubclass=0x01
OTOH I've seen in CVS that /src/sys/dev/usb/ukbd.c was deleted in HEAD,
as 8.0 will contain the new USB stack, so the patch better be done to
the new file ;-)
'There is no reason anyone would want a computer in their home.' (Ken Olson, founder of DEC, 1977)
Do you know if this keyboard now works as expected with the new USB stack
in FreeBSD 8.0? Or if it was ever fixed in 7.x? Thanks!
bug still applies to FreeBSD 8.0-RELEASE-p2 with Logitech Internet 350
# sysctl dev.ukbd
dev.ukbd.0.%desc: LITEON Technology USB Multimedia Keyboard, class 0/0,
rev 1.10/1.01, addr 2
dev.ukbd.0.%location: port=2 interface=0
dev.ukbd.0.%pnpinfo: vendor=0x046d product=0xc313 devclass=0x00
devsubclass=0x00 sernum="" release=0x0101 intclass=0x03 intsubclass=0x01
no reactions from multimedia keys in xev
If you still have the opportunity could you do the following as root:
# figure out the USB bus the device is attached to and the ugen device
# in use using:
dmesg | grep usbus
# then start dumping USB transfers for this device:
usbdump -v -i usbusX -f Y
# where Y is the number after ugenY (I think).
This should produce tcpdump like output of the USB transfers. Now
press the keys that are dead and see whether that produces additional
My uname is... well, not nick, in any case ...
I'm not the PR opener, but just in case this is for the Apple keyboard:
% uname -a
FreeBSD lapo.andxor.it 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 #0: Tue Jun
12 00:39:29 UTC 2012
% dmesg|fgrep ukbd0:
ukbd0: <Apple, Inc Apple Keyboard, class 0/0, rev 2.00/0.69, addr 3> on
% sudo usbdump -v -i usbus4 -s 0
frame READ 8 bytes
0000 00 00 68 00 00 00 00 00
frame READ 8 bytes
0000 00 00 6E 00 00 00 00 00
...and it seems that the third byte (68..6E) is incrementing in F13-F19.
OTOH the "eject" key (between F12 and F13) and the "fn" key don't seem
to produce any traffic at all.
(I can provide dumps)
Lapo Luchini - http://lapo.it/
âWe can factor the number 15 with quantum computers. We can also factor
the number 15 with a dog trained to bark three times.â (Robert Harley,
You could also try to use
About that last one: You might want to check whether that one isn't running and grabbing events before they reach xev.
Last but not least: It might be that the multimedia keys are only available in a different config than the default one.
sudo usbconfig -d ugenX.Y dump_all_config_desc
where ugenX.Y is the keyboard device's ugen sibling. If that shows multiple configurations you might want to try other configurations on the device using
sudo usbconfig -d ugenX.Y set_config <cfg index>
sudo usbconfig -d ugenX.Y set_alt <alt_index>
If this does apply you might want to make this a permanent change by adding a devd script in /etc/devd/ to set the config when the device is attached. I can provide you with details if you need help there.
I've got some ideas on how to resolve these two issues:
- more keys available on the console from USB keyboards
- full support for USB keys in X11
The solution to using USB multimedia keyboards in X, and having keys appear in xev is to use uhidd mentioned on
It can attach to the Consumer USB interface on the keyboard next to ukbd providing only support for those keys (*).
An alternative is to use usbhidaction(1), which will use the uhid driver.
(*) The problem with reattachment mentioned when using uhidd has been resolved in june of 2012 in FBSD8 and up.
Note: FBSD7 having the old USB stack won't be considered here.
For bugs that match the following
- Status Is In progress
- Untouched since 2018-01-01.
- Affects Base System OR Documentation
Reset to open status.
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.