On Wed, 4 Apr 2001, Boris Pisarcik wrote:
> I looked a bit at the source of sysrq handling. I've found there is
> rather big difference between sysrq+b and other killers handling.
> Sysrq+b is just called with pretty straitforward fashion - stops other
> processors on SMP and reboots directly (har
> It is a very good idea, and to implement quite easy. You just do have to
> diff between three types of video cards (MDA, MGA and HGC vs. CGA and AGA vs. EGA+).
> Then you do direct register writes. For the HGC I did it recently in a DOS proggy
> which switched from text to gfx and back. I had a
>You could even set sysvinit
> to run it when you press a certain key combo.
You mean inittab & kbrequest ? I didn't know about this. Must have a look
at some documentation, manpage didn't help me a lot.
Besides, you have very interesting name/domain, cheaf of bandits !!
Some stupid questions about videomem:
1) How do 2 or more X servers, or svgalibbed apps share the same physical video
memory ? Does it get saved to ram when switching between them ?
2) Does console switching (gfx or text) save and restore all registers of
videocard in kernel ? Or kernel only r
You write:
> Can you anyhow find something in your logs/console/serial console messages
> like 13.13.2000 kernel : Sysrq: Emergency Sync (this should be present - is
> written within keyboard handler, not after shedule) and what's next logs ?
> We could determine, if the bdflush thread got schedu
Unfortunately,
> the only one that responds is sysrq-b, which boots the box without
> syncing or unmounting the disks. Not only does that piss me off but it's
> led to some fs corruption as well (which pisses me off even more). sysrq-b
> is the *only* combination I can get working when this happ
> One more property, that i'd like to have should be request key to force
> the most basic text mode (say 80x25) on the console, when eg. X freezes
> and i kill its session, then last gfx mode resides on the screen and
> see no way to restore back the text mode - /usr/bin/reset or something
> ali
On Sat, 31 Mar 2001, Boris Pisarcik wrote:
> on say tty2. The processes get created pretty fast. After a short while
> I supposed a single solution to this to kill all session by alt+sysrq+k,
> but nothing happened. Under normal averagely loaded situation, this will
> imidiately kill all processes
> Thought, i really love all sysrq properties of linux, so i need less often
> to make hardware resets an then await and fear, what fsck will print.
101% ACK
> One more property, that i'd like to have should be request key to force the
> most basic text mode (say 80x25) on the console, when eg.
9 matches
Mail list logo
