[gentoo-user] More splash problems

[gentoo-user] More splash problems

[Nagatoro]

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 /etc/splash/livecd-2005.1/800x600.cfg
No 8bpp verbose pic found...
Failed to get ...
---

But as you can see below i specify a 1280x1024 resolution in 16bpp 
mode (same result if I try 1024x768).

dmesg:
---
[2001] $ dmesg | grep fb
Kernel command line: root=/dev/hda2
video=vesafb-tng:ywrap,mtrr,1280x1024-16@60
splash=verbose,theme:livecd-2005.1 quiet CONSOLE=/dev/tty1 udev
CPU: After generic identify, caps: 3febfbff 00000000 00000000 00000000
00000000 00000000 00000000
CPU: After vendor identify, caps: 3febfbff 00000000 00000000 00000000
00000000 00000000 00000000
CPU: After all inits, caps: 3febfbff 00000000 00000000 00000080
00000000 00000000 00000000
vesafb: NVIDIA Corporation, NV34 Board - c116dnz , Chip Rev    (OEM:
NVIDIA)
vesafb: VBE version: 3.0
vesafb: protected mode interface info at c000:f090
vesafb: pmi: set display start = c00cf0c6, set palette = c00cf130
vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc
3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
vesafb: hardware supports DDC2 transfers
vesafb: monitor limits: vf = 76 Hz, hf = 81 kHz, clk = 140 MHz
vesafb: scrolling: redraw
fbsplash: console 0 using theme 'livecd-2005.1'
vesafb: framebuffer at 0xd0000000, mapped to 0xe8880000, using 937k,
total 131072k
fb0: VESA VGA frame buffer device
  [<c012fb07>] load_module+0xa15/0xb69
  [<c012fb07>] load_module+0xa15/0xb69
  [<c012fb07>] load_module+0xa15/0xb69
  [<c012fb07>] load_module+0xa15/0xb69
  [<c012fb07>] load_module+0xa15/0xb69
fbsplash: console 0 using theme 'livecd-2005.1'
fbsplash: console 1 using theme 'livecd-2005.1'
fbsplash: switched splash state to 'on' on console 1
---

Kernel config:
---
[2001] $ zcat /proc/config.gz | grep FB_
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SOFT_CURSOR=y
# CONFIG_FB_MACMODES is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
# CONFIG_FB_VESA_STD is not set
CONFIG_FB_VESA_TNG=y
CONFIG_FB_VESA_DEFAULT_MODE="1280x1024@60"
# CONFIG_FB_HGA is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_VIRTUAL is not set
CONFIG_FB_SPLASH=y
---

Does anyone have an idea as to what is wrong here? It used to work 
(some emerge -uDNav world 's ago...).

--
Naga
-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] More splash problems

[Michael Kintzios]

> -----Original Message-----
> From: Nagatoro [mailto:nagatoro@gmail.com] 
> 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 tried: 1280x1024-32@60, or 1280x1024-24@60 ?
-- 
Regards,
Mick

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Nagatoro]

Michael Kintzios wrote:
> 
> Have you tried: 1280x1024-32@60, or 1280x1024-24@60 ?

Same result I'm afraid :(

-- 
Naga
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Uwe Thiem]

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 config file /etc/splash/livecd-2005.1/800x600.cfg
> No 8bpp verbose pic found...
> Failed to get ...
> ---
>
> But as you can see below i specify a 1280x1024 resolution in 16bpp
> mode (same result if I try 1024x768).
>
> dmesg:
> ---
> [2001] $ dmesg | grep fb
> Kernel command line: root=/dev/hda2
> video=vesafb-tng:ywrap,mtrr,1280x1024-16@60
> splash=verbose,theme:livecd-2005.1 quiet CONSOLE=/dev/tty1 udev

Try "video=vesafb:..." instead of "vesafb-tng".

Uwe

-- 
95% of all programmers rate themselves among the top 5% of all software 
developers. - Linus Torvalds

http://www.uwix.iway.na (last updated: 20.06.2004)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Nagatoro]

Uwe Thiem wrote:
> 
> Try "video=vesafb:..." instead of "vesafb-tng".

Same thing...

-- 
Naga
-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] More splash problems

[Michael Kintzios]

> -----Original Message-----
> From: Nagatoro [mailto:nagatoro@gmail.com] 
> 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 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).
-- 
Regards,
Mick

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Nagatoro]

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 mailing list

Re: [gentoo-user] More splash problems

[Holly Bostick]

Nagatoro schreef:
> 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 /etc/splash/livecd-2005.1/800x600.cfg
> No 8bpp verbose pic found...
> Failed to get ...
> ---
> 
Your problem seems to be the same one I had.
> 
> dmesg:
> ---

> CONFIG_FB_VESA_DEFAULT_MODE="1280x1024@60"

> 
> Does anyone have an idea as to what is wrong here? It used to work (some
> emerge -uDNav world 's ago...).

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

1280x1024-32@60

(or whatever your preferred resolution is, thereby specifying a bit
depth to the kernel config)

recompile the kernel, and try again, using the setting you want in
grub.conf, and it should work. At least, that's what fixed it for me.

This is not the way it's *supposed* to work-- the setting in the kernel
is supposed to be overridden by the setting in grub.conf. And for most
everybody, it seems to work that way. But in my experience, the setting
in grub.conf is ignored if the kernel config doesn't conform to it-- if
I haven't set a bit depth in the kernel, the kernel framebuffer settings
default to 8bpp, which the livecd theme does not support, causing the
livecd themes to fail (because the theme looks for 8bpp pix instead of
overriding the fallback to what I specified in grub.conf). Emergence
does support 8bpp, so that would work, but that's not what we're trying
to do.

It seems to be a bug, but if you could confirm that 'fixing' your kernel
setting fixes the problem for you, then that would help confirm that it
is a bug (as well as fixing your problem), although it seems to not
affect everyone for some reason (yet to be determined).

Holly


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Nagatoro]

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
> 1280x1024-32@60
> (or whatever your preferred resolution is, thereby specifying a bit
> depth to the kernel config)
> recompile the kernel, and try again, using the setting you want in
> grub.conf, and it should work. At least, that's what fixed it for me.

Sorry didn't work.
The 8bpp message did dissapear but the framebuffer still want's to 
read the config file for 800x600.

-- 
Naga
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Holly Bostick]

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
>> 1280x1024-32@60
>> (or whatever your preferred resolution is, thereby specifying a bit
>> depth to the kernel config)
>> recompile the kernel, and try again, using the setting you want in
>> grub.conf, and it should work. At least, that's what fixed it for me.
> 
> 
> Sorry didn't work.
> The 8bpp message did dissapear but the framebuffer still want's to read
> the config file for 800x600.
> 

Well, actually it did work-- it solved *half* the problem, which is an
improvement.

Now I'm wondering:

1) What command did you use to generate the splash initrd? Is it
compiled into the kernel, or do you use an initrd line in grub.conf? If
the latter, what does that line say?

2) Did you ever attempt to use 800x600? Maybe it's a cache issue, then.
 I didn't find out how to remove /lib/splash/cache from /etc/mtab (short
of manually deleting it, which I didn't want to do), but I did manage to
unmount it as root (umount cachedir), which (afaics) allowed it to be
regenerated when I rebooted. Maybe that would help.

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Matthias Krebs]

> 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 before, vesafb-tng is not a valid kernel
parameter, so everything after it is ignored.

HTH,

Matze

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Holly Bostick]

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 surprise, given that it was created by spock, a gentoo
developer), then it most certainly is a valid kernel parameter (and was
selected in the kernel config output that was posted in a previous message.

If the post you're referring to was Uwe's, I don't think he meant that
the parameter was invalid, but rather that rather than using vesafb-tng,
that the OP should try "regular" vesafb, which might work where
vesafb-tng wasn't working.

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
respect, Matthias is on to something: if the line wraps to another line
(with some kind of soft return), and is not really all on one line as it
is supposed to be, the second half of the kernel line (after the soft
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.

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Matthias Krebs]

On 8/23/05, Holly Bostick <motub@planet.nl> 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 which you get with the gentoo kernels,
> which is no surprise, given that it was created by spock, a gentoo
> developer), then it most certainly is a valid kernel parameter (and was
> selected in the kernel config output that was posted in a previous message.
> 
To quote the author of vesafb-tng: "The driver name used in the video=
kernel command line section is still vesafb, and not vesafb-tng. Thus,
video=vesafb-tng:1024x768-32@85 is invalid,
video=vesafb:1024x768-32@86 being the proper form"

See his website at http://dev.gentoo.org/~spock/projects/vesafb-tng/

Cheers,

Matze

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Holly Bostick]

Matthias Krebs schreef:
> On 8/23/05, Holly Bostick <motub@planet.nl> 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 which you get with the gentoo kernels,
>>which is no surprise, given that it was created by spock, a gentoo
>>developer), then it most certainly is a valid kernel parameter (and was
>>selected in the kernel config output that was posted in a previous message.
>>
> 
> To quote the author of vesafb-tng: "The driver name used in the video=
> kernel command line section is still vesafb, and not vesafb-tng. Thus,
> video=vesafb-tng:1024x768-32@85 is invalid,
> video=vesafb:1024x768-32@86 being the proper form"
> 
> See his website at http://dev.gentoo.org/~spock/projects/vesafb-tng/
> 

Well, thanks for the heads-up; that seems to be a change from the
previous behaviour (and also means that the wiki entry needs updating;
the Handbook seems to have been updated).

I'll change my grub.conf. But it's good to know that the previous
behaviour still works (so it's more like deprecated rather than obsolete).

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Nagatoro]

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 
nvidia doesn't play together so I'm recompiling (again...). Hope it 
works this time.
-- 
Naga

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Uwe Thiem]

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 which you get with the gentoo kernels,
> which is no surprise, given that it was created by spock, a gentoo
> developer), then it most certainly is a valid kernel parameter (and was
> selected in the kernel config output that was posted in a previous message.
>
> If the post you're referring to was Uwe's, I don't think he meant that
> the parameter was invalid, but rather that rather than using vesafb-tng,
> that the OP should try "regular" vesafb, which might work where
> vesafb-tng wasn't working.

Nope, that was not what I meant. I meant: If you select vesafb-tng during 
kernel configuration, "vesafb" on the kernel command line refers to 
vesafb-tng. That's how it works here without *any* problem.

Uwe

-- 
95% of all programmers rate themselves among the top 5% of all software 
developers. - Linus Torvalds

http://www.uwix.iway.na (last updated: 20.06.2004)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Uwe Thiem]

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
> respect, Matthias is on to something: if the line wraps to another line
> (with some kind of soft return), and is not really all on one line as it
> is supposed to be, the second half of the kernel line (after the soft
> 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.

This can be easily proved. Do "cat /proc/cmdline" and check whether the output 
matches the line in grub.conf.

Uwe

-- 
95% of all programmers rate themselves among the top 5% of all software 
developers. - Linus Torvalds

http://www.uwix.iway.na (last updated: 20.06.2004)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Nagatoro]

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 
before and altho not the same driver but the same card X is at 1280x1024.

This needs some probing...

> someone else mentioned before, vesafb-tng is not a valid kernel
> parameter, so everything after it is ignored.

Since I get exactly the same result with vesafb as whit vesafb-tng I 
don't think this is the problem.

-- 
Naga
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[bshlists]

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 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 the bootsplash started.  

I'd appreciate it if someone would remind me how to do this.

--
DWW
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Holly Bostick]

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 the bootsplash started.  
> 
> I'd appreciate it if someone would remind me how to do this.

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 at the very start.

If you load it as a separate initrd, you have to wait for the
framebuffer to initialize before the splash can start (which takes a
short while).

Naturally, if you change from loading an initrd to compiling the initrd
into the kernel, you do have to change a config file (grub.conf, to
remove the initrd= line, since you no longer have one), but changing the
file alone won't make any difference if you haven't changed the way you
create the initrd in the first place.


HTH,
Holly

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[bshlists]

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 a change to a config file which would change when the
> > bootsplash started.
> >
> > I'd appreciate it if someone would remind me how to do this.
>
> 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 at the very start.
>
> If you load it as a separate initrd, you have to wait for the
> framebuffer to initialize before the splash can start (which takes a
> short while).
>
> Naturally, if you change from loading an initrd to compiling the initrd
> into the kernel, you do have to change a config file (grub.conf, to
> remove the initrd= line, since you no longer have one), but changing the
> file alone won't make any difference if you haven't changed the way you
> create the initrd in the first place.
>
>
> HTH,

Holly

Okay.  The method I used was by genkernel and the initramfs I'm using was to 
get the autodetection feature.  If I change this don't lose that ability or 
does it matter?
 
--
DWW
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Holly Bostick]

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 seeing
>>>somewhere a change to a config file which would change when the
>>>bootsplash started.
>>>
>>>I'd appreciate it if someone would remind me how to do this.
>>
>>Afaik, it's not a change to a config file, it's a change in the way you
>>generate the initramfs.
>>
>
> 
> Okay.  The method I used was by genkernel and the initramfs I'm using was to 
> get the autodetection feature.  If I change this don't lose that ability or 
> does it matter?

Well, insofar as I've never used genkernel a day in my life, I don't
know for certain. But if you went to all the trouble of using genkernel
to get autodetection, then clearly autodetection 'matters' and should be
preserved.

I seem to recall Uwe posting in one of the several threads on this
subject a command line to get genkernel to include the splash data (as
well as whatever its already set to generate).

That information might be on the Wiki as well.

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Uwe Thiem]

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 at the very start.
> >
> > If you load it as a separate initrd, you have to wait for the
> > framebuffer to initialize before the splash can start (which takes a
> > short while).
> >
> > Naturally, if you change from loading an initrd to compiling the initrd
> > into the kernel, you do have to change a config file (grub.conf, to
> > remove the initrd= line, since you no longer have one), but changing the
> > file alone won't make any difference if you haven't changed the way you
> > create the initrd in the first place.
> >
> >
> > HTH,
>
> Holly
>
> Okay.  The method I used was by genkernel and the initramfs I'm using was
> to get the autodetection feature.  If I change this don't lose that ability
> or does it matter?

"genkernel --menuconfig --gensplash=yourtheme --gensplash-res=1024x768 all" or 
whatever resolution you want. You can use the initramfs as usual.

Uwe

-- 
95% of all programmers rate themselves among the top 5% of all software 
developers. - Linus Torvalds

http://www.uwix.iway.na (last updated: 20.06.2004)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[bshlists]

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 the Wiki; see How-to
> > > fbsplash), it will start up at the very start.
> > >
> > > If you load it as a separate initrd, you have to wait for the
> > > framebuffer to initialize before the splash can start (which takes a
> > > short while).
> > >
> > > Naturally, if you change from loading an initrd to compiling the initrd
> > > into the kernel, you do have to change a config file (grub.conf, to
> > > remove the initrd= line, since you no longer have one), but changing
> > > the file alone won't make any difference if you haven't changed the way
> > > you create the initrd in the first place.
> > >
> > >
> > > HTH,
> >
> > Holly
> >
> > Okay.  The method I used was by genkernel and the initramfs I'm using was
> > to get the autodetection feature.  If I change this don't lose that
> > ability or does it matter?
>
> "genkernel --menuconfig --gensplash=yourtheme --gensplash-res=1024x768 all"
> or whatever resolution you want. You can use the initramfs as usual.
>
> Uwe
>

Thanks for the suggestion.  After reading Holly's suggestion I did more 
reading and found what you just posted.  What seemed to mess my attempts up 
was that I had to delete the old initramfs before running the above command 
or I would just get the same results.  

Once that was sorted you everything was good. :-)

--
DWW
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] More splash problems

[Tony Davison]

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 somewhere a change to a config file which
> > would change when the bootsplash started.
> >
> > I'd appreciate it if someone would remind me how to do this.
>
> 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 at the very start.
>
> If you load it as a separate initrd, you have to wait for the
> framebuffer to initialize before the splash can start (which takes a
> short while).
>
> Naturally, if you change from loading an initrd to compiling the
> initrd into the kernel, you do have to change a config file
> (grub.conf, to remove the initrd= line, since you no longer have
> one), but changing the file alone won't make any difference if you
> haven't changed the way you create the initrd in the first place.
>
I have two 2.6.12-r9 kernels ATM one which has framebuffer splash on all 
ttys and the other which only has boot splash.
The bootsplash one starts after the udev message and the other one 
starts after the initial uncompressing kernel message (which IIRC is 
when the framebuffer starts, for sure its when the console changes to 
1024x768 on this box)
As far as I know the .config files were the same apart from the fbsplash 
support.
(can't check now as I've been kernel compiling to test some new scsi 
hardware:-( and forgot to save the old .config )
If this is not very clear, both kernels have framebuffers, one has 
bootsplash, and the other has bootsplash and pretty pictures on tty1-6. 
the initrd is the same in both cases, not in the kernel.
Wonderful are the ways of splash.
Tony Davison
tony.davison2@ntlworld.com
-- 
gentoo-user@gentoo.org mailing list