AluBook 5.6: sysctrl mouse button emulation broken with recent git kernel?
... or what did I miss ? .. :)
Hi All
$ cat /proc/cpuinfo
processor : 0
cpu : 7447A, altivec supported
clock : 833.333000MHz
revision : 0.5 (pvr 8003 0105)
bogomips : 16.57
timebase : 8320000
platform : PowerMac
machine : PowerBook5,8
motherboard : PowerBook5,8 MacRISC3 Power Macintosh
detected as : 287 (PowerBook G4 15")
pmac flags : 00000019
L2 cache : 512K unified
pmac-generation : NewWorld
excerpt from "sysctl -A"
dev.mac_hid.mouse_button3_keycode = 126
dev.mac_hid.mouse_button2_keycode = 100
dev.mac_hid.mouse_button_emulation = 1
Yet pressing <FN>-<LEFT_ALT> or <FN>-<MULTIKEY> (multikey is the
"Apple" key here) doesn't result in either a 2nd or 3rd mouse key,
neither on console or X on the alubook. The same works like a charm on
an old tibook IV, with the same codes showing up on both machines with
'showkey -s' resp. 'showkey -k'
("showkey -m" does not result in anything here when tapping the
<LEFT_ALT> or <MULTIKEY>, neither on the alubook nor on the ti-IV, so
I could only compare these cryptic (tho' identical) codes from the
output resulting from the showkey options mentioned above)
Values for the alubook:
$ uname -a
Linux debby1-6 2.6.17-rc3-g5528e568-dirty #1 Sun May 7 23:51:15 CEST
2006 ppc GNU/Linux
$ cat /proc/version
Linux version 2.6.17-rc3-g5528e568-dirty (root@debby1-6) (gcc version
4.1.1 20060428 (prerelease) (Debian 4.1.0-2)) #1 Sun May 7 23:51:15
CEST 2006
$ zgrep MAC_EMUMOUSEBTN /proc/config.gz
CONFIG_MAC_EMUMOUSEBTN=y
The titanium is run by an old, self-rolled 2.6.14.1 ...
Also the 'sysctl -A' output (please see above) regarding the mouse
stuff is identical on both machines ...
Especially the 3rd button is badly missing on the alubook: I use it
dozens of times daily, with the keyboard emu on the ti-IV ...
Thanks in anticipation
Best Regards
Wolfgang
--
Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer
Key ID: E3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on
Reply to: