Date: Fri, 24 Apr 1998 13:24:50 -0700 From: Bill Trost <trost@cloud.rain.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: mobile@FreeBSD.ORG Subject: Re: GENERIC 800x600 support in XF86_VGA16 now in -current Message-ID: <1611.893449490@cloud.rain.com> In-Reply-To: Your message of Thu, 12 Feb 1998 23:08:30 %2B0100. <6977.887321310@critter.freebsd.dk> References: <6977.887321310@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp writes:
Add support for VESA mode 0x102 (800x600x4) in syscons. You
can activate this using option "-b" to the boot blocks. It is
smartest to compile a font into your kernel (See LINT), but not
mandatory, but apart from the cursor you will see nothing on the
screen until you load a font.
I have been using this code for a week or two now, and am *very* happy
to be able to use the whole screen under X (even if Navigator looks
terrible in 4-bit color). However, I am getting that the impression
that this feature is walking on top of the file system (or vice versa).
Ever since I installed the new boot code, I have been having to run fsck
by hand on the root partition every other reboot (or so). It only seems
to happen when I use -b, and creating boot.config and/or boot.help seems
to have reduced the problem (or at least obscured it).
Any ideas? I do not think this can simply be the result of switching
to -current, as I was playing around at least some with that before
installing the new boot blocks. And, like I said, it seems to only
occur when I use -b.
Oh...and is there any way I can avoid having to type -b all the time?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1611.893449490>