From owner-freebsd-current Tue Feb 24 02:10:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10143 for freebsd-current-outgoing; Tue, 24 Feb 1998 02:10:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10114 for ; Tue, 24 Feb 1998 02:10:49 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id LAA24300; Tue, 24 Feb 1998 11:13:16 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 24 Feb 1998 11:13:16 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Kazutaka YOKOTA cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed addition to panic() behaviour In-Reply-To: <199802241011.TAA12153@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Feb 1998, Kazutaka YOKOTA wrote: > >> > Many people (including me) suffered from panic while their console was in > >> > graphic mode (e.g. X Window). I don't know if this would be proper place > >> > to do this, but in case of panic (where everything is lost anyway) just > >> > add there the code to forcefully reset the video card to set it in > >> > known (and useful) mode... > >> > >> See the numerous "DDX in the kernel" discussions in the -current list > >> archives to see why "just add there the code to forcefully reset the > >> video card" requires knowing how the video card got in the mode it's > >> in, and specific knowledge of the card (hint: write-only hardware > >> registers not shadoewed in RAM). > > > >But I also vaguely recall something like dump of VGA registers > >when booted with -v, so they are stored somewhere, right? > > The video BIOS ROM contains the table of STANDARD register values only. > We cannot know which additional registers should be set to what value. Ok. Call me stubborn, but why can't we just write the STANDARD register values corresponding to the initial state of the card, and if the screen is still garbled, well - at least we tried... But, my point is (or maybe I'm still wrong), that *most of the time* this will restore the card to some usable state... Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message