From owner-freebsd-mobile Fri Apr 24 13:26:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22394 for freebsd-mobile-outgoing; Fri, 24 Apr 1998 13:26:16 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA22387 for ; Fri, 24 Apr 1998 13:26:13 -0700 (PDT) (envelope-from trost@cloud.rain.com) Received: (qmail 1549 invoked by uid 4); 24 Apr 1998 20:25:39 -0000 Received: (qmail 1614 invoked from network); 24 Apr 1998 20:24:51 -0000 Received: from localhost.cloud.rain.com (127.0.0.1) by localhost.cloud.rain.com with SMTP; 24 Apr 1998 20:24:51 -0000 To: Poul-Henning Kamp cc: mobile@FreeBSD.ORG Subject: Re: GENERIC 800x600 support in XF86_VGA16 now in -current References: <6977.887321310@critter.freebsd.dk> In-reply-to: Your message of Thu, 12 Feb 1998 23:08:30 +0100. <6977.887321310@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1610.893449490.1@cloud.rain.com> Date: Fri, 24 Apr 1998 13:24:50 -0700 Message-ID: <1611.893449490@cloud.rain.com> From: Bill Trost Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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