From owner-freebsd-current Fri May 28 9:26:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 4852E15434 for ; Fri, 28 May 1999 09:26:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA00805; Fri, 28 May 1999 09:23:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905281623.JAA00805@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kenneth Wayne Culver Cc: Mike Smith , freebsd-current@freebsd.org Subject: Re: splash screen broken?? In-reply-to: Your message of "Thu, 27 May 1999 23:05:00 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 May 1999 09:23:27 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Whenever I try to load the splash screen (300x200 256 colors) the modules > > > seem to load right, however, when the kernel boots, it gives me an error > > > about mod_register_init or something of that nature, I was just testing > > > the config... I tried these commands at the boot loader. > > > Here it is... I typed the exact same lines into the bootloader that I > showed you in my last mail, and here is my dmesg output... I also have the > line > > pseudo-device splash > > in my kernel so I know that's not the problem. ... > module_register_init: MOD_LOAD (splash_bmp, c028162c, 0) error 19 That's what we needed to see. Error 19 is ENODEV; this means you either don't have VESA support compiled in, haven't loaded the VESA module, or your VESA BIOS doesn't support a mode that allows a 300x200x8 image to be displayed. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message