Maverick is buggy, you say? It works fine on my Eee 1015PED...I'm typing to you on it now. I donno.
Anyway, let's try to see if it detects the numlock press on the low-level end, and if it's a higher-level GUI-related thing.
Get a terminal and run "xev". This will detect all input that you put in, provided the "Event Tester" window is in focus. So do just that, and hit the combination for numlock, Fn-Insert I'm guessing.
If it finds the keypress, the terminal should output something like this as it detects it being pressed and released:
Code:
KeyPress event, serial 36, synthetic NO, window 0x7400001,
root 0xaa, subw 0x0, time 15976832, (84,-7), root:(134,291),
state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
PropertyNotify event, serial 36, synthetic NO, window 0x7400001,
atom 0x19a (XKLAVIER_STATE), time 15976847, state PropertyNewValue
KeyRelease event, serial 36, synthetic NO, window 0x7400001,
root 0xaa, subw 0x0, time 15977081, (84,-7), root:(134,291),
state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
Does it?
If it doesn't, you might want to see if it still works with the old kernel, which I assume you still have. Shutdown the computer, and hold Shift while it's starting. This will show you GRUB's menu and your installed kernels. The one that says "2.6.35-xx" is the one that was installed to get acceleration support. Run any other previous version and try it. If it works with the older kernel, you may have to stay with that one if you want your numlock to work, but you won't have acceleration. Or you can try Maverick again.
If it does, then I don't really know what to do next, as UI monkeying isn't really my forte. Maybe someone else can pick up on it.
Bookmarks