Skip to contentSkip to conversation

missing sysrq

DISCUSSION Dieter Nützel 4 participants 4 messages Jun 1, 2001 – Jun 9, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 7 lines
Quoted 5 lines · D. Stimits
Quoted 1 line · Bernd Eckenfels
Quoted 1 line · In article <[email protected]> you wrote:

However, if I go to /proc/sys/kernel/sysrq does not exist.

Quoted 8 lines
Quoted 2 lines

It is a compile time option, so the person who compiled your kernel left it out.

I compiled it, and the sysrq is definitely in the config. No doubt at all. I also use make mrproper and config again before dep and actual compile. Maybe it is just a quirk/oddball.

D. Stimits, [email protected]

Have you tried "echo 1 > /proc/sys/kernel/sysrq"?
You need both, compiled in and activation.

Regards,
Dieter

Signature · 5 lines
Dieter Nützel
Graduate Student, Computer Science

email: [email protected]
@home: [email protected]
#1 lore raw
Quoted 6 lines · Dieter Nützel
Quoted 6 lines
Quoted 5 lines
Quoted 1 line · In article <[email protected]> you wrote:

However, if I go to /proc/sys/kernel/sysrq does not exist.

It is a compile time option, so the person who compiled your kernel left it out.

Quoted 8 lines
Quoted 5 lines

I compiled it, and the sysrq is definitely in the config. No doubt at all. I also use make mrproper and config again before dep and actual compile. Maybe it is just a quirk/oddball.

D. Stimits, [email protected]

Have you tried "echo 1 > /proc/sys/kernel/sysrq"?
You need both, compiled in and activation.

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.
----------------------------------------------------------------------

#2 lore raw
Quoted 9 lines · Mike A. Harris
Quoted 6 lines · Dieter Nützel
Quoted 6 lines
Quoted 5 lines
Quoted 1 line · In article <[email protected]> you wrote:

However, if I go to /proc/sys/kernel/sysrq does not exist.

It is a compile time option, so the person who compiled your kernel left it out.

Quoted 8 lines
Quoted 8 lines
Quoted 5 lines

I compiled it, and the sysrq is definitely in the config. No doubt at all. I also use make mrproper and config again before dep and actual compile. Maybe it is just a quirk/oddball.

D. Stimits, [email protected]

Have you tried "echo 1 > /proc/sys/kernel/sysrq"?
You need both, compiled in and activation.

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, [email protected]

Quoted 34 lines

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.
----------------------------------------------------------------------

#3 lore raw
In reply to Mike A. Harris

BTW, you ONLY need to echo 1 > /proc../sysrq if you use a distribution that puts a 0 there on init.

By default the kernel initializes with '1'.

David

Quoted 9 lines
Quoted 9 lines
Quoted 6 lines

I compiled it, and the sysrq is definitely in the config. No doubt at all. I also use make mrproper and config again before dep and actual compile. Maybe it is just a quirk/oddball.

D. Stimits, [email protected]

Have you tried "echo 1 > /proc/sys/kernel/sysrq"?
You need both, compiled in and activation.