From owner-freebsd-current Mon Oct 6 12:44:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA22728 for current-outgoing; Mon, 6 Oct 1997 12:44:22 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA22717 for ; Mon, 6 Oct 1997 12:44:19 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id MAA19733; Mon, 6 Oct 1997 12:43:45 -0700 (MST) From: Terry Lambert Message-Id: <199710061943.MAA19733@usr04.primenet.com> Subject: Re: current on notebook (as of Oct 3) To: sos@sos.freebsd.dk (Søren Schmidt) Date: Mon, 6 Oct 1997 19:43:44 +0000 (GMT) Cc: gurney_j@resnet.uoregon.edu, regnauld@deepo.prosa.dk, freebsd-current@FreeBSD.ORG In-Reply-To: <199710061834.UAA00372@sos.freebsd.dk> from "Søren Schmidt" at Oct 6, 97 08:34:32 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > The only reason I can think of is that the check_modetable_for_sanity > > > function, somehow is discarding the modetable in the video BIOS, why > > > I cant tell offhand, but with a verbose boot the table is dumped so > > > it should be possible to inspect and compare with what the check > > > function wants... > > > > well.. I posted the -v boot from the kernel.. do you need it again?? > > ERhm, not really, I pointed you at where to look :) I think he meant to say "it should be possible for *you* to inspect" ... 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.