linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: XF4, SysRq, VT, mouse buttons, Keymaps and all that
Date: Thu, 19 Apr 2001 15:36:07 +0100	[thread overview]
Message-ID: <20010419143631.8A7F72EFC2@apollo.valhalla.net> (raw)


Hi Franz,

copied to the list - since I think I've resolved the issues now ;-)

Franz wrote:
>I wrote:
>> I've figured out the mouse key emulation, and VT switches (by using Option
>> XkbDisable) - but I can't figure out where SysRq has ended up... and anyway
>> the idea was to see if there's a way of dealing with it so that Laptops can
>> use it too...
>
> Well, just try to setup your configuration files correctly. See the excerpt
> from my XF86Config-4 below. VT switches happen with alt(option)-ctrl-Fx if
> configured correctly.

OK.  What's happened is that the VT combination has shifted from
<CMD>-<CNTL>-Fx to <ALT>-<CNTL>-Fx ... all OK now.  (the config was correct)

[...]

>> For use of >4.0.99.x should I have CONFIG_ADB_KEYCODE disabled?
>
> For maximum compatibility options to be active you need:
>
> CONFIG_INPUT_ADBHID=y
> CONFIG_MAC_ADBKEYCODES=y
> CONFIG_MAC_EMUMOUSEBTN=y

This is what I've had (or the equivalent) since the input layer back-port to
2.2.x...

and Option "XkbModel" "macintosh"

> This will give you all the /proc entries.

yep. it does.

>> the SysRq needs to be quite low-level to be a fairly guaranteed way of
>> doing 'emergency' syncs and so on ... I'm assuming it's done individually
>> for each of the possible hid input sources.
>
> But is it enabled at all? Check /proc/sys/kernel/sysrq.

OK.  It isn't by default (which was catching me out)

Shouldn't it be enabled by default if the kernel is built CONFIG_SYSRQ?

Additionally, like VT-switching, the modifier key appears to have changed to
<ALT> from <CMD>...

SysRq doesn't appear to have _exactly_ the same behaviour as before (but
this may be a consequence of the change of Xserver - no longer using
fbdevhw).

The SysRq messages no longer break through onto the screen (I did get them
on VT-1 at one point - but couldn't reproduce it).

- and once you've got into SysRq mode it appears to be 'sticky' - i.e.
commands accepted with a single keypress until you do SysRq again.  Hmmm.
It might have been like that before - and I never noticed - because I always
did three-key-presses.

----

The issue of a "GoodWay" (tm) to support Laptops with SysRq remains - I'd
like to be able to use it on my Lombard...

====

So, now the correct place to make changes to get the right symbols out for
~/` ±/§ and so on is in  /usr/X11R6/..../xkb/symbols/gb - I assume.

====

I guess that I must have missed a place to look for the changes that
occurred to the modifier keys etc.... perhaps Kaoru should add this
information to his ftp directory.  If people who monitor the -dev list don't
know, what chance have Users got ;-?

====

anyway, thanks for the help - I'm now the proud owner of a nicely
accelerated, non-flickering, ati mach64 XF4 installation.... *and* know
which keys to press ;-))

next time I have some time - I'll do the Lombard & the 9600 (imstt could be
amusing)...

BTW: It runs MoL (almost fine) too.

ciao,
Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-04-19 14:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19 14:36 Iain Sandoe [this message]
2001-04-19 19:32 ` XF4, SysRq, VT, mouse buttons, Keymaps and all that Martin Costabel
2001-04-20 10:12   ` Franz Sirl
2001-04-21 22:45     ` Martin Costabel
2001-04-21 22:59       ` Michel Dänzer
  -- strict thread matches above, loose matches on Subject: below --
2001-04-18 13:16 Iain Sandoe
2001-04-18 13:23 ` Tony Mantler
2001-04-18 15:18 ` Michel Dänzer
2001-04-18 12:44 Iain Sandoe
2001-04-18 13:06 ` Tony Mantler
2001-04-18 13:39 ` Gabriel Paubert
2001-04-18 14:54   ` Franz Sirl
2001-04-18 16:10     ` Gabriel Paubert
2001-04-18 12:03 Iain Sandoe
2001-04-18 12:13 ` Michel Dänzer
2001-04-18 12:24 ` Tony Mantler
2001-04-18  9:03 Iain Sandoe
2001-04-18 11:40 ` Martin Costabel
2001-04-18  0:28 Iain Sandoe
2001-04-18  3:40 ` Tony Mantler
2001-04-18  4:04 ` Steven Hanley
2001-04-18  0:06 Iain Sandoe
2001-04-18  0:08 ` Michel Dänzer
2001-04-17 21:14 Iain Sandoe
2001-04-17 22:15 ` Michel Dänzer
2001-04-17 22:49 ` Martin Costabel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010419143631.8A7F72EFC2@apollo.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).