Since then I've completely removed that kernel source and kernel, only
the config file remains (and it had it activated if the config followed
it). All kernels before worked, and those since then also work, so I
know it isn't the keyboard. I also always run make mrproper and config
it again between compiles (I keep a list of config history), so I don't
know what was wrong, but replacing the kernel fixed it, and is no longer
an issue. I will, however, keep the showkey suggestion handy in case it
ever does it again.
D. Stimits, stimits@idcomm.com
>
> If you *know* it is compiled into your kernel, and you *know* it
> is enabled via the above, and it still does not work, do the
> following:
>
> Run:
>
> showkey -s
>
> Then press LALT quickly followed by SYSRQ, and keep holding both
> down, and you should see:
>
> 0x38
> 0x54
>
> You might see a bunch of extra 0x38's which is ok.
>
> If however when you press ALT-SYSRQ you see:
>
> 0x38 0x54 0xd4
>
> and are still holding both keys down, then your keyboard is
> broken and incompatible with the kernel SYSRQ feature.
>
> A proper keyboard will only show "0x38 0x54". I have written a
> patch for SYSRQ to allow it to be used with broken keyboards that
> send the make+break code for the SYSRQ sequence simultaneously.
>
> If you need it, let me know and I'll send it to you.
>
> ----------------------------------------------------------------------
> Mike A. Harris - Linux advocate - Open Source advocate
> Opinions and viewpoints expressed are solely my own.
> ----------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/