[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde
Subject:    Re: [kde] due to compositing,
From:       Bill Wells <hammer29 () sbcglobal ! net>
Date:       2009-08-17 22:24:37
Message-ID: 200908171524.37200.hammer29 () sbcglobal ! net
[Download RAW message or body]

On Monday 17 August 2009 11:35:28 am Anne Wilson wrote:
> On Monday 17 August 2009 19:26:47 Nikos Chantziaras wrote:
> > >>> So how do you use that, if, as you say, the keyboard doesn't respond?
> > >>
> > >> SysRq is hardwired into the kernel.  If the kernel didn't panic, SysRq
> > >> still works even if X stopped processing keyboard events.  And from
> > >> the sound of it, the kernel did not panic in this case since the mouse
> > >> still moves, so the kernel must be running.
> > >
> > > Interesting, because (some months back) I have been in the same
> > > situation and tried the SysRq 'magic keys', just in case, but without
> > > success.
> >
> > It must be enabled in the kernel configuration.  If the file
> > "/proc/sysrq-trigger" doesn't exist, you don't have it enabled.
>
> In that case I don't have it, and, presumably didn't have it in the distro
> I was using at that time.  How common is it for this to be enabled?
>
It is here in Slackware 12.2 32 bit.
> Anne


Bill
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
[prev in list] [next in list] [prev in thread] [next in thread]