Bug 28233

Summary: splash_bmp broken in 4.3-STABLE
Product: Base System Reporter: glebius <glebius>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.3-STABLE   
Hardware: Any   
OS: Any   

Description glebius 2001-06-17 18:00:07 UTC
I have been using the following config since 4.0-RELEASE, and
it worked well:

Important lines in kernel config:
device          vga0    at isa?
options         VESA
pseudo-device   splash
device          agp

Lines in /boot/loader.conf:
splash_bmp_load="YES"
bitmap_load="YES"
bitmap_name="/boot/logow.bmp"
bitmap_type="splash_image_data"

After I CVSuped yesterday, and rebooted I have got this errors:

Preloaded elf kernel "kernel" at 0xc04e5000.
Preloaded elf module "splash_bmp.ko" at 0xc04e509c.
Preloaded splash_image_data "/boot/logow.bmp" at 0xc04e5140.
splash_bmp: No appropriate video mode found
module_register_init: MOD_LOAD (splash_bmp, c03c8798, 0) error 19
VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc0353482 (1000022)
VESA: NVidia

Fix: 

none
How-To-Repeat: 	try the same configuration
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2001-08-19 10:28:50 UTC
State Changed
From-To: open->analyzed

Problem is probably due to a stale module.
Comment 2 Kris Kennaway 2001-08-19 10:29:03 UTC
On Sun, Jun 17, 2001 at 08:54:42PM +0400, glebius@snark.rinet.ru wrote:

> After I CVSuped yesterday, and rebooted I have got this errors:
> 
> Preloaded elf kernel "kernel" at 0xc04e5000.
> Preloaded elf module "splash_bmp.ko" at 0xc04e509c.
> Preloaded splash_image_data "/boot/logow.bmp" at 0xc04e5140.
> splash_bmp: No appropriate video mode found
> module_register_init: MOD_LOAD (splash_bmp, c03c8798, 0) error 19
> VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc0353482 (1000022)
> VESA: NVidia
> 
> >How-To-Repeat:
> 	try the same configuration


This is almost certainly caused by an out of date module.  Does the
problem persist after you rebuild your kernel and modules completely?

Kris
Comment 3 Kris Kennaway freebsd_committer freebsd_triage 2001-08-20 07:39:22 UTC
State Changed
From-To: analyzed->closed

Submitter reports problem was caused by stale modules