On 30 August 2005 16:31, bshlists wrote:
On August 30, 2005 10:51 am, Holly Bostick wrote:
Afaik, it's not a change to a config file, it's a change in the way you
generate the initramfs.
If you compile it into the kernel (instructions on the Wiki; see How-to
fbsplash), it will start up
On August 31, 2005 04:02 am, Uwe Thiem wrote:
On 30 August 2005 16:31, bshlists wrote:
On August 30, 2005 10:51 am, Holly Bostick wrote:
Afaik, it's not a change to a config file, it's a change in the way you
generate the initramfs.
If you compile it into the kernel (instructions on
On August 23, 2005 04:25 am, Nagatoro wrote:
Hi,
I've got another interesting problem with the splash. It seems like
no matter what I specify the computer always wants to use a 800x600
resolution.
At startup I get this (not word for word since showconsole won't play
nicely):
Using
bshlists schreef:
Using all the suggestions on this thread I was able to get gensplash up and
running. I however have one small problem the bootsplash come up some 1/3
the way through the bootup process. Now I remember seeing somewhere a change
to a config file which would change when
On August 30, 2005 10:51 am, Holly Bostick wrote:
bshlists schreef:
Using all the suggestions on this thread I was able to get gensplash up
and running. I however have one small problem the bootsplash come up
some 1/3 the way through the bootup process. Now I remember seeing
somewhere
bshlists schreef:
On August 30, 2005 10:51 am, Holly Bostick wrote:
bshlists schreef:
Using all the suggestions on this thread I was able to get gensplash up
and running. I however have one small problem the bootsplash come up
some 1/3 the way through the bootup process. Now I remember
On Tuesday 30 August 2005 15:51, Holly Bostick wrote:
bshlists schreef:
Using all the suggestions on this thread I was able to get
gensplash up and running. I however have one small problem the
bootsplash come up some 1/3 the way through the bootup process.
Now I remember seeing
On 23 August 2005 20:14, Holly Bostick wrote:
Matthias Krebs schreef:
And as
someone else mentioned before, vesafb-tng is not a valid kernel
parameter, so everything after it is ignored.
In what world is this? If you're using vesafb-tng (added to the kernel
options by the fbsplash patch
On 23 August 2005 20:14, Holly Bostick wrote:
Sorry, forgot this in my other posting.
Oh, and btw, Nagatoro... it's silly, but just open up your grub.conf
with nano and make sure that some word-wrap somewhere didn't mess up
your kernel line. That happened to me a couple of times, and in that
Hi,
I've got another interesting problem with the splash. It seems like
no matter what I specify the computer always wants to use a 800x600
resolution.
At startup I get this (not word for word since showconsole won't play
nicely):
---
can't open config file
-Original Message-
From: Nagatoro [mailto:[EMAIL PROTECTED]
Sent: 23 August 2005 09:26
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] More splash problems
But as you can see below i specify a 1280x1024 resolution in 16bpp
mode (same result if I try 1024x768).
Have you
Michael Kintzios wrote:
Have you tried: [EMAIL PROTECTED], or [EMAIL PROTECTED] ?
Same result I'm afraid :(
--
Naga
--
gentoo-user@gentoo.org mailing list
On 23 August 2005 09:25, Nagatoro wrote:
Hi,
I've got another interesting problem with the splash. It seems like
no matter what I specify the computer always wants to use a 800x600
resolution.
At startup I get this (not word for word since showconsole won't play
nicely):
---
can't open
Uwe Thiem wrote:
Try video=vesafb:... instead of vesafb-tng.
Same thing...
--
Naga
--
gentoo-user@gentoo.org mailing list
-Original Message-
From: Nagatoro [mailto:[EMAIL PROTECTED]
Sent: 23 August 2005 13:23
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] More splash problems
Uwe Thiem wrote:
Try video=vesafb:... instead of vesafb-tng.
Same thing...
Did you re-emerge your
Holly Bostick wrote:
Yes... you see your kernel config for the default mode? It does not
specify a bit depth. Neither did mine. Change the setting in the kernel to
[EMAIL PROTECTED]
(or whatever your preferred resolution is, thereby specifying a bit
depth to the kernel config)
recompile the
Michael Kintzios wrote:
Did you re-emerge your splashutils and rerun genitramfs with /boot
mounted? Also, did you check the resolution for your vesa-tng entry in
the kernel menuconfig? (see Holly's previous post on this topic).
Yes, unfortunaly no change.
--
Naga
--
gentoo-user@gentoo.org
Nagatoro schreef:
Holly Bostick wrote:
Yes... you see your kernel config for the default mode? It does not
specify a bit depth. Neither did mine. Change the setting in the
kernel to
[EMAIL PROTECTED]
(or whatever your preferred resolution is, thereby specifying a bit
depth to the kernel
Matthias Krebs schreef:
And as
someone else mentioned before, vesafb-tng is not a valid kernel
parameter, so everything after it is ignored.
In what world is this? If you're using vesafb-tng (added to the kernel
options by the fbsplash patch which you get with the gentoo kernels,
which is no
Sorry didn't work.
The 8bpp message did dissapear but the framebuffer still want's to
read the config file for 800x600.
--
Naga
Maybe you want to use a mode your graphic board doesn't support. Do a
cat /proc/fb0/modes to get the modes your board supports. And as
someone else mentioned
Matthias Krebs wrote:
Maybe you want to use a mode your graphic board doesn't support. Do a
cat /proc/fb0/modes to get the modes your board supports. And as
Well that's where it get weird! cat /proc/fb0/modes report that
800x600 *is* the highest resolution I can have but I've had 1280x1024
On 8/23/05, Holly Bostick [EMAIL PROTECTED] wrote:
Matthias Krebs schreef:
And as
someone else mentioned before, vesafb-tng is not a valid kernel
parameter, so everything after it is ignored.
In what world is this? If you're using vesafb-tng (added to the kernel
options by the fbsplash
Matthias Krebs schreef:
On 8/23/05, Holly Bostick [EMAIL PROTECTED] wrote:
Matthias Krebs schreef:
And as
someone else mentioned before, vesafb-tng is not a valid kernel
parameter, so everything after it is ignored.
In what world is this? If you're using vesafb-tng (added to the kernel
Holly Bostick wrote:
wrap) will be ignored. So opening up the file with nano and going to the
beginning of any apparently wrapped line and hitting Backspace to pull
it all together is not a bad idea.
Nope al in one line.
On side note I found some fourum posting claming that agppart and
24 matches
Mail list logo
