| 1 |
On August 30, 2005 10:51 am, Holly Bostick wrote: |
| 2 |
> bshlists schreef: |
| 3 |
> > Using all the suggestions on this thread I was able to get gensplash up |
| 4 |
> > and running. I however have one small problem the bootsplash come up |
| 5 |
> > some 1/3 the way through the bootup process. Now I remember seeing |
| 6 |
> > somewhere a change to a config file which would change when the |
| 7 |
> > bootsplash started. |
| 8 |
> > |
| 9 |
> > I'd appreciate it if someone would remind me how to do this. |
| 10 |
> |
| 11 |
> Afaik, it's not a change to a config file, it's a change in the way you |
| 12 |
> generate the initramfs. |
| 13 |
> |
| 14 |
> If you compile it into the kernel (instructions on the Wiki; see How-to |
| 15 |
> fbsplash), it will start up at the very start. |
| 16 |
> |
| 17 |
> If you load it as a separate initrd, you have to wait for the |
| 18 |
> framebuffer to initialize before the splash can start (which takes a |
| 19 |
> short while). |
| 20 |
> |
| 21 |
> Naturally, if you change from loading an initrd to compiling the initrd |
| 22 |
> into the kernel, you do have to change a config file (grub.conf, to |
| 23 |
> remove the initrd= line, since you no longer have one), but changing the |
| 24 |
> file alone won't make any difference if you haven't changed the way you |
| 25 |
> create the initrd in the first place. |
| 26 |
> |
| 27 |
> |
| 28 |
> HTH, |
| 29 |
|
| 30 |
Holly |
| 31 |
|
| 32 |
Okay. The method I used was by genkernel and the initramfs I'm using was to |
| 33 |
get the autodetection feature. If I change this don't lose that ability or |
| 34 |
does it matter? |
| 35 |
|
| 36 |
-- |
| 37 |
DWW |
| 38 |
-- |
| 39 |
gentoo-user@g.o mailing list |
Archives