public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Tigran Aivazian <tigran@veritas.com>
Cc: "Mohammad A. Haque" <mhaque@haque.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: how to capture long oops w/o having second machine
Date: Tue, 12 Dec 2000 16:28:36 MET-1	[thread overview]
Message-ID: <F7716111F69@vcnet.vc.cvut.cz> (raw)

On 12 Dec 00 at 13:31, Tigran Aivazian wrote:
> > > I'm gonna try to compile in a framebuffer and use a high resolution and
> > > see if that'll hold it all when I get back later today.
> > 
> > shift+pageup ?
> 
> the problem with Shift-PgUP is that all the framebuffer drivers I tried
> (matrox, ati, vesa) corrupt the screen when it is used. The only way to
> use Shift-PgUp reliably I have ever seen was on vgacon. These bugs seemed
> to be there for years so I didn't even bother reporting them - I just got
> used to the idea "using fb? forget the Shift-PgUP then".

Do not hit 'shift-pgup' while penguin logo is on the screen. Something
somewhere is wrong... (and never hit shift-pgdn; shift-pgup corrupts
screen while shift-pgdn corrupts kernel memory)

Or better, boot with 'video=scrollback:0' (*). I think that we should 
make this default for 2.4, as (except this problem) scrollback code is 
broken for multihead and fix is not trivial.
                                        Best regards,
                                                Petr Vandrovec
                                                vandrove@vc.cvut.cz

(*) With matrox in 8bpp you'll get almost always bigger and faster scrollback
with 'video=scrollback:0' than with default 'scrollback:32768' ...
                                                
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-12 16:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-12 16:28 Petr Vandrovec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-12 13:10 how to capture long oops w/o having second machine Mohammad A. Haque
2000-12-12 13:19 ` Xavier Bestel
2000-12-12 13:31   ` Tigran Aivazian
2000-12-12 13:32   ` Mohammad A. Haque
2000-12-12 14:34 ` Mohammad A. Haque
2000-12-12 16:38   ` Greg KH
2000-12-12 20:38     ` Mohammad A. Haque
2000-12-12 20:51       ` Miles Lane
2000-12-12 23:24         ` dean gaudet
2000-12-12 23:38           ` Mohammad A. Haque
2000-12-15 22:57     ` Pavel Machek
2000-12-12 17:13   ` Andreas Bombe
2000-12-12 21:58     ` Greg KH
2000-12-15 22:57       ` Pavel Machek
2000-12-12 15:31 ` Wakko Warner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F7716111F69@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhaque@haque.net \
    --cc=tigran@veritas.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox