Hi
(wow, fast reply!)
On Tue, Apr 08, 2008 at 04:47:26AM +0200, Michael Schmitz wrote:
Well, even though I still read and answer mail from Duesseldorf I am
physically based in Auckland, NZ now. So 4 am is 2pm for me :-)
Package: powerpc-utils
Version: 1.1.3-22
Severity: normal
Recent kernels seemed to have changed the behaviour of the fn keys. I
recently upgraded from 2.6.4.19 to 2.6.4.24 and now the F-keys have
their hot key behaviour by default and the "normal" behaviour only if
fn is pressed, which is quite annoying. (I tried 2.6.22 from Lenny
which exhibited the same behaviour). I did not find a kernel option to
revert this but found fnkeys which should be able to change, but:
I haven't followed powerpc for a while but there should be other ways
aside from fnset to deal with this (perhaps via input devices?).
I am currently looking for any way to achive this, so if you have
pointers, I'll gladly take them (until 2.6.19 it worked fine, from
2.6.22 it no longer does, and I haven't found anything in the kernel
config yet).
I doubt it's in the config anywhere. I haven't followed the powerpc kernel
list in the past months so I might have missed some discussion there. CC
to BenH ...
twotofive:~# fnset -u
unknown PMU version 17
twotofive:~# fnset -v -d -u
writing 2 bytes: { 0x06 0xea }
read 2 bytes: { 0x00 0x11 }
unknown PMU version 17
What hardware is that on? Please send the output of /proc/cpuinfo.
It is a PowerBook G4.
processor : 0
cpu : 7447A, altivec supported
clock : 1666.666000MHz
revision : 0.5 (pvr 8003 0105)
bogomips : 33.15
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
Mine's a 5,5 and fnset works there ...
Please do also test fnset -f -v -d -u and report the output. If that still
fails to toggle the fn setting, I will need the section reporting the ADB
probe results from your dmesg output.
It does not understand -f (despite the help output):
twotofive:~# fnset -f -v -d -u
fnset: invalid option -- f
Uh - that's a bug for sure. Getopt option list not updated when adding the
force option, yikes.
(btw. how serious is this "damage hardware" thing? I'd rather have a
non-working Fn behaviour than a nice apple brick :-(( )
I doubt it is very serious. In your case, chances are it won't do a thing
anyway, see below.
I grabbed the lines before and after the adb output from dmesg:
console [netcon0] enabled
netconsole: network logging started
MacIO PCI driver attached to Intrepid chipset
input: Macintosh mouse button emulation as /class/input/input0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
adb: starting probe task...
adb: finished probe task...
PCI: Enabling device 0002:24:0d.0 (0000 -> 0002)
ide0: Found Apple UniNorth ATA-6 controller, bus ID 3, irq 39
Probing IDE interface ide0...
These new models still do have ADB keyboards, do they?
Well, how do I find out? (I think they do, yes, but so far I haven't
ever tried to understand/look for this).
If you had an ADB keyboard, it would have shown before. You'll probably
find a keyboard probe message in the USB or input device section instead.
Benh: Starting from what PMU version, did Apple switch to USB keyboards on
their powerbooks? Version 12 still had ADB keyboard, 17 does not - what
happened in between? And how to toggle the fn key status on USB keyboards?
Why does opening /dev/adb rw even succeed on a machine with no ADB devices
attached to the bus? Where could I check for the number of registered ADB
devices?
Cheers,
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
