With regard to the "fn" key problem I would think the following line should be changed to a default value of 2 (if Mario is right)
+++ b/drivers/hid/hid-input.c
+static int hid_apple_fnmode = 1;
With regard to the swapped "½" and "<" key it is seemingly done by purpose by this, since my keyboard is an ISO keyboard:
+++ b/drivers/hid/hid-input.c
+static struct hidinput_key_translation apple_iso_keyboard[] = {
{ KEY_GRAVE, KEY_102ND },
{ KEY_102ND, KEY_GRAVE },
I don't know the reason for this, but it is wrong for my keyboard with danish layout. Does anyone know why this is done?
With regard to the Num-lock problem as far is I can see it is due to laptop and non-laptop keyboards treated equal. Erics patch above should address this.
I am no kernel hacker but would love to try to tinker with the code. Could anyone give me a pointer to how to compile a module as Eric has done above?
Also shouldn't this bug be set to affect "linux (Ubuntu)"?
After some digging around i think i finally found the commit where the issue is introduced: kernel. ubuntu. com/git? p=ubuntu/ ubuntu- hardy.git; a=commitdiff; h=efb3031b446d4 41dca5b10619503 ac0bba7f9748
http://
With regard to the "fn" key problem I would think the following line should be changed to a default value of 2 (if Mario is right) hid/hid- input.c
+++ b/drivers/
+static int hid_apple_fnmode = 1;
With regard to the swapped "½" and "<" key it is seemingly done by purpose by this, since my keyboard is an ISO keyboard: hid/hid- input.c key_translation apple_iso_ keyboard[ ] = {
+++ b/drivers/
+static struct hidinput_
{ KEY_GRAVE, KEY_102ND },
{ KEY_102ND, KEY_GRAVE },
I don't know the reason for this, but it is wrong for my keyboard with danish layout. Does anyone know why this is done?
With regard to the Num-lock problem as far is I can see it is due to laptop and non-laptop keyboards treated equal. Erics patch above should address this.
I am no kernel hacker but would love to try to tinker with the code. Could anyone give me a pointer to how to compile a module as Eric has done above?
Also shouldn't this bug be set to affect "linux (Ubuntu)"?