I've (mostly) switched to using a Logitech k400r wireless keyboard for most of the time with the linux box that feeds AV to our TV, etc. However it doesn't have a key which is labelled as the sysreq. And when I tried the 'print screen' key to see if that could be used for this purpose it didn't work.
So, anyone know which key on this model of keyboard will deliver the
sysreq? Or how I can check to find out?
I tried a websearch but couldn't find any specific answer to this.
I've (mostly) switched to using a Logitech k400r wireless keyboard for
most of the time with the linux box that feeds AV to our TV, etc.
However it doesn't have a key which is labelled as the sysreq. And when
I tried the 'print screen' key to see if that could be used for this
purpose it didn't work.
So, anyone know which key on this model of keyboard will deliver the
sysreq? Or how I can check to find out?
I tried a websearch but couldn't find any specific answer to this.
This is all a bit esoteric of course and perhaps will set you towards
the wrong path. A more productive approach may be the following : on the Linux box in question what application is responsible for reading
sysreq (when it exists) and do the operation you want to achieve ? The documentation of that application may provide a clue.
I've (mostly) switched to using a Logitech k400r wireless keyboard for
most of the time with the linux box that feeds AV to our TV, etc.
However it doesn't have a key which is labelled as the sysreq. And when
I tried the 'print screen' key to see if that could be used for this
purpose it didn't work.
So, anyone know which key on this model of keyboard will deliver the
sysreq? Or how I can check to find out?
I tried a websearch but couldn't find any specific answer to this.
In article <VkuwifgCL6SOnqv9H@bongo-ra.co>, Spiros Bousbouras <spibou@gmail.com> wrote:
This is all a bit esoteric of course and perhaps will set you towards
the wrong path. A more productive approach may be the following : on the Linux box in question what application is responsible for reading
sysreq (when it exists) and do the operation you want to achieve ? The documentation of that application may provide a clue.
AIUI the purpose of SysKey is that the 'OS' picks this up as a trigger that what follows is to deal with something like a 'kernel panic'. i.e. it bypasses (or should) the GUI and apps.
In article <VkuwifgCL6SOnqv9H@bongo-ra.co>, Spiros Bousbouras <spibou@gmail.com> wrote:
This is all a bit esoteric of course and perhaps will set you towards
the wrong path. A more productive approach may be the following : on the Linux box in question what application is responsible for reading
sysreq (when it exists) and do the operation you want to achieve ? The documentation of that application may provide a clue.
AIUI the purpose of SysKey is that the 'OS' picks this up as a trigger that what follows is to deal with something like a 'kernel panic'. i.e. it bypasses (or should) the GUI and apps.
Is the information at https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html of any
use ?
It might also help if you explain what operation you want to achieve
with sysreq .
In article <1825036279@f1.n221.z2.fidonet.fi>, Spiros Bousbouras <Spiros.Bousbouras@f1.n221.z2.fidonet.fi> wrote:
Is the information at https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html of any
use ?
It is certainly useful as a handy guide, yes. :-)
It might also help if you explain what operation you want to achieve
with sysreq .
The machine in question sometimes seems to 'stiff' its GUI, etc following a mouseclick. Most often this is when a click on a ROX-Filer 'app' icon calls starting up VLC to play a file.
I *think* what happens is due to using a wireless mouse/keyboard where the control isn't 100% reliable. It *may* be due to more than one command being sent causing something like multiple instances of VLC to be started as they both try to get going. But this is a guess on my part.
The result is partly displayed VLC windows and a totally unresponsive (usually) system. i.e. the mouse and normal uses of the keyboard cease to have any visible effect.
An old wireless keyboard however then will let me run though the standard REISUB sequence to shot down and start up again.
I got the k400r as an alternative and it is, indeed, much more reliable in communicating with the machine. So the problem happens much less often. But when it did (for the first time) I found that the keyboard lacked a SysRq
key label, and 'print screen' seemed not to work for a REISUB sequence. Had to get the 'old' keyboard and that did the trick.
So I can keep the old keyboard handy for when needed. But it would be
better if I can suss how to get the new one to let me send the REISUB.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 81:55:58 |
Calls: | 6,658 |
Calls today: | 4 |
Files: | 12,203 |
Messages: | 5,333,417 |
Posted today: | 1 |