Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Oct 1997 13:23:45 -0700
From:      John-Mark Gurney <gurney_j@efn.org>
To:        =?iso-8859-1?Q?S=F8ren_Schmidt?= <sos@sos.freebsd.dk>
Cc:        tlambert@primenet.com, regnauld@deepo.prosa.dk, freebsd-current@FreeBSD.ORG
Subject:   Re: current on notebook (as of Oct 3)
Message-ID:  <19971006132345.63142@hydrogen.nike.efn.org>
In-Reply-To: =?iso-8859-1?Q?=3C199710062007=2EWAA25876=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Mon=2C_Oct_06=2C_1997_at_10=3A07=3A1?= =?iso-8859-1?Q?2PM_%2B0200?=
References:  <19971006125237.17144@hydrogen.nike.efn.org> <199710062007.WAA25876@sos.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
Søren Schmidt scribbled this message on Oct 6:
> In reply to John-Mark Gurney who wrote:
> > > > > 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" ...
> 
> That was exactly what I meant :)
> 
> > well..  the -v from the kernel says nothing about if the mode table
> > is dumped (any body object to me adding this under the bootverbose
> > flag?) and that the actual mode table as far as I can tell is compared
> > to what the vga is currently set to...
> 
> It dumps an array of hex mumbers, which is the mode table
> from your own posting:
> sc0: VGA registers upon power-up
> 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 
> bf 1f 00 4f 0d 0e 00 00 05 00 9c 8e 8f 28 1f 96 
> b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
> 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
> 
> Now uses this together with the function that checks for a sane modetable:
> comp_vgaregs(u_char *buf1, u_char *buf2) 
> located in syscons.c, and you can see what it is that upsets syscons.

ok.. this is the problem.... I don't see any sane modetable in syscons.c
and this is what I said in a response to you...  so, do you object to the
warning about the modetable from the bios not being used?  how about also
printing the modetable that it was comparing against...

> > you just go and try to look at the code..  and I doubt that you will
> > get much father...  ttyl.
> 
> Well, I just did :)

I would hope so, most of it's your code.. :)

> Sorry, but I just tried to point you in the right direction, without the
> need to pull out linenumbers etc etc...

well.. I assumed that the -v would print out warnings or message that
would tell what was happening...   now can you just point me to the
sane table??

-- 
  John-Mark Gurney                          Modem/FAX: +1 541 683 6954
  Cu Networking

  Live in Peace, destroy Micro$oft, support free software, run FreeBSD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971006132345.63142>