public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Fish <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] fbsplash problems
Date: Fri, 22 Jul 2005 17:00:07 +0200	[thread overview]
Message-ID: <42E109F7.9080601@asmallpond.org> (raw)
In-Reply-To: <200507220926.07614.samael@ugcc.org.ua>

Vitaly Kovalyshyn aka samael wrote:

>Hello!
>
>I've problems with fbsplash 2!
>
>in grub.conf:
>title  Gentoo Linux
>root (hd0,0)
>kernel /kernel-2.6.11-gentoo-r11 root=/dev/hda3 video=vesafb:1024x768-16@85 
>plash=silent,theme:livecd-2005.0
>initrd /fbsplash-livecd-2005.0-1024x768
>
>in dmesg:
># dmesg | grep vesafb
>Kernel command line: ro root=/dev/hda3 video=vesafb:ywrap,mtrr,1024x768-16@85 
>splash=silent
>vesafb: ATI Technologies Inc., V280, 01.00 (OEM: ATI RADEON 9200)
>vesafb: VBE version: 2.0
>vesafb: protected mode interface info at c000:5767
>vesafb: pmi: set display start = c00c57fb, set palette = c00c5847
>vesafb: pmi: ports = a010 a016 a054 a038 a03c a05c a000 a004 a0b0 a0b2 a0b4
>vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
>vesafb: scrolling: ywrap using protected mode interface, yres_virtual=1536
>vesafb: framebuffer at 0xe0000000, mapped to 0xe0880000, using 3072k, total 
>16384k
>
>  
>

Do you also get a message about "checking if initrd is initramfs..." in 
dmesg?  If not, then you probably don't have ram disk or initrd support 
in your kernel configuration.  If so, then everything looks right, and 
maybe you can try a couple of different resolutions, and particularly, 
bit depths.  1024x768-24 or 1024x768-32 might work better.

-Richard

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-22 15:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 14:51 [gentoo-user] fbsplash problems LostSon
2005-07-19 15:49 ` Ramón Gutiérrez
2005-07-19 18:49   ` Richard Fish
2005-07-19 15:50 ` Holly Bostick
2005-07-19 16:00   ` LostSon
2005-07-19 17:07     ` cafairle
2005-07-19 17:31       ` Christoph Eckert
2005-07-19 18:44 ` Richard Fish
2005-07-19 20:00   ` LostSon
2005-07-19 20:12     ` Richard Fish
2005-07-19 20:27       ` charly ghislain
2005-07-19 20:45         ` Tony Davison
2005-07-19 20:51           ` LostSon
2005-07-19 21:10             ` Christoph Eckert
2005-07-19 21:10               ` LostSon
2005-07-19 21:30                 ` Christoph Eckert
2005-07-19 21:31               ` Holly Bostick
2005-07-19 22:03                 ` LostSon
2005-07-19 22:38                   ` Holly Bostick
2005-07-20  5:11                   ` Richard Fish
2005-07-21 16:14                     ` LostSon
2005-07-21 16:23                       ` LostSon
2005-07-21 21:36                       ` Richard Fish
2005-07-21 16:57                         ` LostSon
2005-07-22  6:26                         ` Vitaly Kovalyshyn aka samael
2005-07-22 15:00                           ` Richard Fish [this message]
2005-07-25  6:48                             ` Vitaly Kovalyshyn aka samael
2005-07-19 22:00               ` Richard Fish
2005-07-19 22:54                 ` Christoph Eckert
2005-07-20  7:33           ` charly ghislain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42E109F7.9080601@asmallpond.org \
    --to=bigfish@asmallpond.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox