Re: splash_bmp_load problems.

richard childers / kg6hac <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile,gmane.os.freebsd.questions
Message-ID <[email protected]>
"bitmap_load="NO"
bitmap_name="/boot/splash.pcx"
splash_pcx_load="NO"

I was looking at the splash(4) stuff myself last week, and I seemed to
recall it expected a '.bmp' file, by default. I note this is described (see
above) as a type '.pcx' file, and further, that you seem to have
'splash_pcx_load' set to 'NO'.

Could this inconsistency be the cause of problems?


-- richard


lewiz wrote:

> Hi,
>
>   This might seem a bit of a silly question to be asking.  It's a bit
> pointless really but I can't figure out why it shouldn't work.
>
>   I tried setting a 800x600 256 color bitmap as my splash bmp.  The same
> bitmap works just fine on another machine (that isn't a laptop).
> Basically, while the modules are all loaded nicely I get a squashed and
> repeated image in the upper section of the screen.  It's no more than
> 1/5th of the screen's height and it's repeated horizontally about four
> or five times.  Any idea what might cause this?
>
>   My /boot/loader.conf reads:
>
> bitmap_load="NO"
> bitmap_name="/boot/splash.pcx"
> splash_pcx_load="NO"
>
>   I have the VESA compiled into my kernel for the 800x600 mode (I also
> had the same problem with a smaller bitmap.  PCX files result in the
> same problem also).
>
>   Many thanks,
>
> -lewiz.
>
> --
> However, never daunted, I will cope with adversity in my traditional
> manner ... sulking and nausea.
>                 -- Tom K. Ryan
> ------------------------------------------------------------------------
> --|| url: http://lewiz.info/ | http://www.westwood.karoo.net/pgpkey ||--
>
>   -----------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature


To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-mobile" in the body of the message
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.