| 1 |
On Tuesday, April 07, 2015 9:21:38 PM lee wrote: |
| 2 |
> Fernando Rodriguez <frodriguez.developer@×××××××.com> writes: |
| 3 |
> |
| 4 |
> > On Saturday, April 04, 2015 2:41:12 PM lee wrote: |
| 5 |
> >> I always can't remember which keys to press with that, so I have it |
| 6 |
> >> disabled. |
| 7 |
> >> |
| 8 |
> >> And when the keyboard is unresponsive, it won't work. |
| 9 |
> > |
| 10 |
> > It will in many cases (probably most). Usually it's xorg that "freezes" |
| 11 |
the |
| 12 |
> > keyboard, in those cases ctrl-alt-sysrq-r followed by ctrl-alt-f1 should |
| 13 |
get |
| 14 |
> > you to the VT where you can restart xorg. I think the kernel needs to be |
| 15 |
> > completely locked with interrupts disabled or locked in a higher priority |
| 16 |
> > interrupt (unlikely) for it not to work or the USB stack totally broken. I |
| 17 |
can |
| 18 |
> > see some of the commands failing or even completely locking the kernel if |
| 19 |
> > something's really messed up. |
| 20 |
> |
| 21 |
> How do you remember these keys? A long time ago, I even printed a list, |
| 22 |
> and of course, it got lost before I ever came close to needing it. |
| 23 |
> Paper is just too volatile. |
| 24 |
|
| 25 |
Like I said: "Reboot Even If System Utterly Broken" I don't have a way to |
| 26 |
remember the specific keys other than knowing what the shutdown sequence is. |
| 27 |
|
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Fernando Rodriguez |
Archives