Hello Michael, (wow, fast reply!) On Tue, Apr 08, 2008 at 04:47:26AM +0200, Michael Schmitz wrote: > >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).
> >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
> 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
Usage: fnset [-hdfusb] [0|1]
-h Help, this message.
-d Turn debugging on.
-f Force search and setting of bits for an unknown PMU.
WARNING: may damage hardware.
-s Set, function keys require <fn> modifier.
Same as checking the box in MacOS.
-u Unset, hot keys require <fn> modifier.
Same as unchecking the box in MacOS.
-v Verbose output.
-b Brief, output adb register bit value only.
0 Set adb register bit to 0.
May not be the same as the -u option.
1 Set adb register bit to 1.
May not be the same as the -s option.
No arguments displays the <fn> mode as if -v was used.
(btw. how serious is this "damage hardware" thing? I'd rather have a
non-working Fn behaviour than a nice apple brick :-(( )
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).
Greetings
Helge
--
Dr. Helge Kreutzmann [EMAIL PROTECTED]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
