I can confirm blacklisting usbhid worked for me. I simply made a
blacklist entry for usbhid and then in /etc/modules I loaded bcm5974 and
then usbhid.
That way usbhid still gets loaded, but after bcm5974
--
[Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
https://bugs.launc
here's the i386 kernel module also
** Attachment added: "hid.ko"
http://launchpadlibrarian.net/12839900/hid.ko
--
Slim USB Apple Keyboard not working correctly..
https://bugs.launchpad.net/bugs/201887
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
nd, the new patch, because launchpad is weird and only lets you
attach one file at a time
** Attachment added: "keyboard.patch"
http://launchpadlibrarian.net/12834430/keyboard.patch
--
Slim USB Apple Keyboard not working correctly..
https://bugs.launchpad.net/bugs/201887
You received this
As for the numlock problem, it's very obvious from viewing the code in
the drivers/hid/hid-input.c file what is going on. Basically, when you
hit the numlock key on an apple keyboard that has a real keypad, it
doesn't actually care that you have a real keypad and switches the
keyboard into powerbo
Ok, sounds good mario, I'll build the kernel module for easier testing.
However, I was thinking about it some more, and I don't think this is
even the right fix. The keypad number keys should just be on by
default, and the "clear" key should not be even interpreted as a
numlock, but an actual clea
oops, that first patch is backwards, use this instead
** Attachment added: "apple-keyboard-numlock.patch"
http://launchpadlibrarian.net/12736374/apple-keyboard-numlock.patch
--
Slim USB Apple Keyboard not working correctly..
https://bugs.launchpad.net/bugs/201887
You received this bug notific
Brad, I have the same keyboard too. Ok, here's what I saw going on while
I was monitoring the events that were being created when pressing
different keys. What's happening is, when numlock is pressed it's
basically getting stuck in an infinite loop.
I created a kernel patch file that worked for m
Mario,
Thank you! numlockx was my problem. I forgot that I had installed it
months ago. Found this forum post showing how to change the default F
key behavior http://ubuntuforums.org/showpost.php?p=3518372&postcount=5
However, pressing the numlock key, or on this keyboard it's labeled
"clear",
I now think this is most likely a kernel bug. I booted up into rescue
mode and the keyboard displayed the same behavior where pressing keys on
the numpad disabled the letters. Could this be due to recent apple
keyboard patches in the kernel?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/16
I'm having this problem too. Except that today I can't get it to return
to normal even by unplugging/rebooting. I'm still looking for why.
Hopefully we can get this fixed
--
Slim USB Apple Keyboard not working correctly..
https://bugs.launchpad.net/bugs/201887
You received this bug notification
10 matches
Mail list logo
