Date: Mon, 6 Oct 1997 22:07:12 +0200 (MEST) From: Søren Schmidt <sos@sos.freebsd.dk> To: gurney_j@resnet.uoregon.edu Cc: tlambert@primenet.com, regnauld@deepo.prosa.dk, freebsd-current@FreeBSD.ORG Subject: Re: current on notebook (as of Oct 3) Message-ID: <199710062007.WAA25876@sos.freebsd.dk> In-Reply-To: <19971006125237.17144@hydrogen.nike.efn.org> from John-Mark Gurney at "Oct 6, 97 12:52:37 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
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.
> you just go and try to look at the code.. and I doubt that you will
> get much father... ttyl.
Well, I just did :)
Sorry, but I just tried to point you in the right direction, without the
need to pull out linenumbers etc etc...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
Even more code to hack -- will it ever end
..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710062007.WAA25876>