Fbsplash doen't work!

root_tux_linux · 2007-05-31 12:06:58

Fbsplash works fine on my GENTOO but not on Arch

1. i installed the kernel26viper kernel.
2. Readed this howto <http://wiki.archlinux.org/index.php/Gensplash http://wiki.archlinux.org/index.php/Gensplash>
3. /etc/mkinitcipo.conf, /etc/conf.d/gensplash, /boot/grub/menu.lst edited
4. splash_geninitramfs -v -g /boot/arch-glass -r 1280x1024 arch-glass
5. My Configs

With initrd /boot/arch-glass in menu.lst i see the silent splash and i have a kernelpanic
With initrd /boot/kernel26viper.img i see nothing from fbsplash but arch works

Can anyone help me?

HOOKS="base udev autodetect ide fbsplash sata keymap filesystems"
FBTHEMES="arch-glass"
FBRES="1280x1024"

[root@Arch ~]# ls /etc/splash/
arch-glass  darch  grub.sample  lilo.sample  luxisri.ttf
[root@Arch ~]#

[root@Arch ~]# ls /etc/splash/arch-glass/
1280x1024.cfg  INSTALL  Vera.ttf  images
[root@Arch ~]#

# (0) Arch Linux
title  Arch Linux Viper
root   (hd0,3)
kernel (hd0,3)/boot/vmlinuz26viper root=/dev/hda4 ro panic=10  video=vesafb:mtrr:3,ywrap,1280x1024-32@60 console=tty1  splash=silent,theme:arch-glass
initrd (hd0,3)/boot/kernel26.img
#initrd /boot/arch-glass

[root@Arch ~]# splash_geninitramfs -v -g /boot/arch-glass  -r 1280x1024 arch-glass
o Creating directory structure..
o Copying /sbin/splash_helper..
o Copying themes..
  - arch-glass
o Creating initramfs image..
[root@Arch ~]#

[root@Arch ~]# mkinitcpio -p kernel26viper
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.21-VIPER -c /etc/mkinitcpio.conf -g /boot/kernel26viper.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [ide]
:: Parsing hook [fbsplash]
       Adding arch-glass fbsplash Theme...
:: Parsing hook [sata]
:: Parsing hook [keymap]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26viper.img'...SUCCESS
==> SUCCESS

Last edited by root_tux_linux (2007-05-31 12:08:47)

klixon · 2007-05-31 12:42:54

root_tux_linux wrote:

initrd (hd0,3)/boot/kernel26.img

Considering the output of mkinitcpio i think this should be

initrd /boot/kernel26viper.img

(in /boot/grub/menu.lst)

dtw · 2007-05-31 12:45:01

OK, re-read the documents, check you configs and try again with the darch theme. Also try with a lower resolution.

Also, does Viper use the the tng framebuffer or vesa because you have used the tng settings.

The wiki IS out of date though, and I will update that ASAP.

dtw · 2007-05-31 12:46:45

klixon wrote:

root_tux_linux wrote:
initrd (hd0,3)/boot/kernel26.img
Considering the output of mkinitcpio i think this should be
initrd /boot/kernel26viper.img
(in /boot/grub/menu.lst)

Yeah, that looks like a good bet to me!

root_tux_linux · 2007-05-31 13:46:58

dtw wrote:

klixon wrote:
root_tux_linux wrote:
initrd (hd0,3)/boot/kernel26.img
Considering the output of mkinitcpio i think this should be
initrd /boot/kernel26viper.img
(in /boot/grub/menu.lst)
Yeah, that looks like a good bet to me!

DONT WORK!!!

dtw · 2007-05-31 13:54:00

root_tux_linux wrote:

dtw wrote:
klixon wrote:
Considering the output of mkinitcpio i think this should be
initrd /boot/kernel26viper.img
(in /boot/grub/menu.lst)
Yeah, that looks like a good bet to me!
DONT WORK!!!

In 99% of cases it's a config mistake. As I said: try the default theme at a lower resolution.

root_tux_linux · 2007-05-31 14:21:27

Silent works but verbose doen't works

I press f2 and i see no backgroundpic

dtw · 2007-05-31 14:46:12

Hmmm - that's odd. Silent should work if your kernel is not patched....but verbose will not, so maybe your kernel patch is dodgy? Or maybe still a config error ;-)

root_tux_linux · 2007-05-31 14:56:08

dtw wrote:

Hmmm - that's odd. Silent should work if your kernel is not patched....but verbose will not, so maybe your kernel patch is dodgy? Or maybe still a config error ;-)

Thats gay

which kernel you use?

dtw · 2007-05-31 15:01:10

And old -beyond one...at least for testing gensplash. I use the stock kernel normally.

Flying Saxman · 2007-05-31 19:20:33

root_tux_linux wrote:

Silent works but verbose doen't works
I press f2 and i see no backgroundpic

Same here with same kernel. Additionally the splash-screen appears very late, not before UDEV Uevents are ready. With my beyond-kernel it appeared almost immediatly after grub.
My menu.lst looks like this:

# (8) Arch Linux Viper
title  Arch Linux Viper
root (hd0,0)
kernel (hd0,0)/vmlinuz26viper root=/dev/sda6 resume2=swap:/dev/sda5 video=vesafb:mtrr:ywrap,1024x768-16@60 splash=silent,theme:darch console=tty1 quiet
initrd (hd0,0)/kernel26viper.img
savedefault

# (9) Arch Linux Viper Fallback
title  Arch Linux Viper Fallback
root (hd0,0)
kernel (hd0,0)/vmlinuz26viper root=/dev/sda6 ro
initrd (hd0,0)/kernel26viper-fallback.img
savedefault

Edit: The settings in my menu.lst for the viper-kernel are the same as for the beyond-kernel, so I think it's a problem of the viper-kernel or the viper-kernel needs to be configured another way.

Last edited by Flying Saxman (2007-05-31 19:28:17)

klixon · 2007-05-31 22:49:52

I think i recall having read that viper-kernel uses vesafb-tng by default (might check .config to be sure...). Maybe beyond uses the "normal" vesa framebuffer code and that would explain the delay?
also, you may have changed the order of the hooks in mkinitcpio.conf after building the beyond initramfs....

Flying Saxman · 2007-06-01 13:52:27

klixon wrote:

I think i recall having read that viper-kernel uses vesafb-tng by default (might check .config to be sure...). Maybe beyond uses the "normal" vesa framebuffer code and that would explain the delay?

afair iphitus also used vesafb-tng for his last beyond-update. And I also used the menu.lst-configuration from beyond for my viper-configuration. If they would use different framebuffers, only one kernel would load with this configuration (that's what I think).

klixon wrote:

also, you may have changed the order of the hooks in mkinitcpio.conf after building the beyond initramfs....

Is also the same as before. Did no change in there since I configured my system for gensplash with the beyond-kernel.

mitsoko · 2007-06-01 14:06:43

in earlier version beyond used the normal vesafb . i can't remembr why it changed to -tng, (search the forums) ... the -viper also uses -tng by default, check the wiki it on Gensplash, it shows you where in the kernel config the setting needs to be changed .. if you are one like me who are unable to use -tng, then yu need to remember to change the fb when you recompile your kernel-viper, for me that's the only issue, once it's changed everything works perfectly again.

aRcHaTe · 2007-06-01 15:43:25

any one knows to splash it allways on verbose mode?

pkraw · 2007-06-01 20:25:10

Same problem here. I've used fbsplash with beyond for some time, so I suppose not to have any configuration errors. It really seems like there is something wrong with patch used in -viper, because silent mode (which is purely userspace solution) works well.

Nothing in logs, nothing in dmesg. I also checked mkinitcpio output file (zcat kernel26viper.img | cpio --list) - everything needed by verbose fbsplash seems to be there. Running gensplash daemon also produces no information (and no console background, of course).

dtw, I understand you have no problems with latest gensplashutils and -beyond kernel? If so, it has to be some -viper error.

Flying Saxman · 2007-06-02 08:21:06

sickhate wrote:

any one knows to splash it allways on verbose mode?

# (8) Arch Linux Viper
title  Arch Linux Viper
root (hd0,0)
kernel (hd0,0)/vmlinuz26viper root=/dev/sda6 resume2=swap:/dev/sda5 video=vesafb:mtrr:ywrap,1024x768-16@60 splash=verbose,theme:darch console=tty1 quiet
initrd (hd0,0)/kernel26viper.img
savedefault

You simply got to change the partition-names according to your partition. If you don't use suspend2, you can leave the "resume2=swap:/dev/sdx" out.
BUT: Currently not even the verbose-mode works with the viper-kernel!

Last edited by Flying Saxman (2007-06-02 08:21:36)

pkraw · 2007-06-02 10:16:06

Flying Saxman wrote:

BUT: Currently not even the verbose-mode works with the viper-kernel!

In fact, verbose mode has much more restrictive requirements than silent mode. The former requires kernel patching (thus there is probably something wrong with fbsplash patch in -viper), whilst the latter needs gensplashutils + initscripts-gensplash tandem only. Silent works fine for me, although there is, of course, no splash until initial ramdisk finishes its work and initscripts take control over system booting.

dtw · 2007-06-02 11:15:25

Am just building a kernel with the broken out fbsplash kernel from genpatches so we'll see how that works out.

Doesn't look like it works

Last edited by dtw (2007-06-02 11:48:56)

Flying Saxman · 2007-06-02 14:24:30

pkraw wrote:

In fact, verbose mode has much more restrictive requirements than silent mode.

Thanks for that info, thought it was just the other way round, because you get the verbose-mode easier with the beyond-patchset than the silent-mode (at least, if you use the wiki-howto).

Silent works fine for me, although there is, of course, no splash until initial ramdisk finishes its work and initscripts take control over system booting.

Take a look what happens, if you press [F2]. Do you have a backgound-picture (of course without starting the fbsplash-daemon through rc.conf ) or not? If not, you got the same problem as me.

pkraw · 2007-06-02 16:04:28

Pressing [F2] switches you to verbose mode - and this one doesn't work, as we've already noticed - also for me. So I guess we do are in the same situation .

Is there any way to debug the problem? I can find no useful messages to deal with it.

Flying Saxman · 2007-06-02 16:09:55

pkraw wrote:

Pressing [F2] switches you to verbose mode - and this one doesn't work, as we've already noticed - also for me. So I guess we do are in the same situation .

oh, right... I forgot... sorry master, me is young padawan. Young padawan still got to learn a lot! ^^

mehldutt · 2007-06-03 10:15:13

Same problem here. I've used fbsplash with beyond for some time, so I suppose not to have any configuration errors. It really seems like there is something wrong with patch used in -viper, because silent mode (which is purely userspace solution) works well.
Nothing in logs, nothing in dmesg. I also checked mkinitcpio output file (zcat kernel26viper.img | cpio --list) - everything needed by verbose fbsplash seems to be there. Running gensplash daemon also produces no information (and no console background, of course).
dtw, I understand you have no problems with latest gensplashutils and -beyond kernel? If so, it has to be some -viper error.

I'm having the same problem as "root_tux_linux".
At first it didn't work with the viper-kernel, but did with beyond. However, after one of those recent updates I'm having the exact same problem with the beyond-kernel after trying to change the splash image.
Therefore I don't think think that this problem is related to the viper-kernel.

Gary

Last edited by mehldutt (2007-06-03 10:29:33)

Flying Saxman · 2007-06-03 11:03:34

mehldutt wrote:

I'm having the exact same problem with the beyond-kernel after trying to change the splash image.
Therefore I don't think think that this problem is related to the viper-kernel.

Can't confirm that.

I tried something: My system is up to date, did mkinicpio -g kernel26viper and mkinitcpio -g kernel26beyond. Beyond: still no problems; Viper: still the same problem. So I don't think, that it is a problem caused by the updates, probably an update went wrong at your computer. I still think, this problem is viper-related, because beyond still works after pacman -Syu and mkinitcpio -g kernel26beyond.

Last edited by Flying Saxman (2007-06-03 11:04:00)

pkraw · 2007-06-03 11:50:38

The problem doesn't seem to be only viper-related, as dtw proved fbsplash patch (taken from the newest genpatches) not to work with -beyond too.

Arch Linux

#1 2007-05-31 12:06:58

Fbsplash doen't work!

#2 2007-05-31 12:42:54

Re: Fbsplash doen't work!

#3 2007-05-31 12:45:01

Re: Fbsplash doen't work!

#4 2007-05-31 12:46:45

Re: Fbsplash doen't work!

#5 2007-05-31 13:46:58

Re: Fbsplash doen't work!

#6 2007-05-31 13:54:00

Re: Fbsplash doen't work!

#7 2007-05-31 14:21:27

Re: Fbsplash doen't work!

#8 2007-05-31 14:46:12

Re: Fbsplash doen't work!

#9 2007-05-31 14:56:08

Re: Fbsplash doen't work!

#10 2007-05-31 15:01:10

Re: Fbsplash doen't work!

#11 2007-05-31 19:20:33

Re: Fbsplash doen't work!

#12 2007-05-31 22:49:52

Re: Fbsplash doen't work!

#13 2007-06-01 13:52:27

Re: Fbsplash doen't work!

#14 2007-06-01 14:06:43

Re: Fbsplash doen't work!

#15 2007-06-01 15:43:25

Re: Fbsplash doen't work!

#16 2007-06-01 20:25:10

Re: Fbsplash doen't work!

#17 2007-06-02 08:21:06

Re: Fbsplash doen't work!

#18 2007-06-02 10:16:06

Re: Fbsplash doen't work!

#19 2007-06-02 11:15:25

Re: Fbsplash doen't work!

#20 2007-06-02 14:24:30

Re: Fbsplash doen't work!

#21 2007-06-02 16:04:28

Re: Fbsplash doen't work!

#22 2007-06-02 16:09:55

Re: Fbsplash doen't work!

#23 2007-06-03 10:15:13

Re: Fbsplash doen't work!

#24 2007-06-03 11:03:34

Re: Fbsplash doen't work!

#25 2007-06-03 11:50:38

Re: Fbsplash doen't work!

Board footer