Arch Linux

treysis

Member

Registered: 2009-05-10

Posts: 23

Fbsplash not working - initscripts-issue?

Hey guys,

lately i tried to get some more eye-candy by installing fbsplash from AUR.
I did everything the way it is explained in the wiki-article (at least i think i did).

what i didn't do (cause it wasn't mentioned), is to install/build a new/patched kernel. is this needed?

well, the problem i encounter is, that when i boot my machine, i get lot's of errors like "basename: command not found", which originate mostly from a script called splash-functions.sh or somehow. but: if i open a console windows and type in the command basename is found and working. thus, i expect that the problem might be the initscripts-package? but i installed it and also rebuild the initramdisk. it even lists fbsplash as a hook while rebuildung.

it would like to give you the complete output of error-messages, but i don't know where to find them? i searched the whole /var/log-directory, but even in the everything.log-logfile i couldn't find any of the messages. maybe something with syslog-ng is also wrong?

all the same, i try to give you some information which might be usefull for investigating my problem, so here they go:

/etc/rc.conf - DAEMONS

DAEMONS=(syslog-ng acpid portmap cpufreq fam hal network alsa netfs crond sensors networkmanager fbsplash gdm tor)

/etc/mkinitpcio.conf - HOOKS

HOOKS="base udev autodetect pata scsi sata fbsplash filesystems"

maybe to mention: i'm using an IDE-only system (older laptop when sata wasn't out yet, but i think the new ATA-driver has went into the SATA-tree or something like that...)

that's the command i used to rebuild the initrd:
[...#] mkinitcpio -p kernel26

and that's a part of /var/log/syslog.log:

Jul 17 21:48:21 leiferiksson syslog-ng[4517]: Termination requested via signal, terminating;
Jul 17 21:48:21 leiferiksson syslog-ng[4517]: syslog-ng shutting down; version='3.0.3'
Jul 17 21:55:00 leiferiksson syslog-ng[4519]: syslog-ng starting up; version='3.0.3'
Jul 17 21:58:51 leiferiksson syslog-ng[4519]: Termination requested via signal, terminating;
Jul 17 21:58:51 leiferiksson syslog-ng[4519]: syslog-ng shutting down; version='3.0.3'
Jul 17 22:00:22 leiferiksson syslog-ng[4520]: syslog-ng starting up; version='3.0.3'
Jul 17 22:15:46 leiferiksson syslog-ng[4520]: Termination requested via signal, terminating;
Jul 17 22:15:46 leiferiksson syslog-ng[4520]: syslog-ng shutting down; version='3.0.3'
Jul 17 22:17:20 leiferiksson syslog-ng[4521]: syslog-ng starting up; version='3.0.3'
Jul 17 22:46:23 leiferiksson syslog-ng[4521]: Termination requested via signal, terminating;
Jul 17 22:46:23 leiferiksson syslog-ng[4521]: syslog-ng shutting down; version='3.0.3'
Jul 17 22:48:11 leiferiksson syslog-ng[4520]: syslog-ng starting up; version='3.0.3'
Jul 17 23:03:41 leiferiksson syslog-ng[4520]: Termination requested via signal, terminating;
Jul 17 23:03:41 leiferiksson syslog-ng[4520]: syslog-ng shutting down; version='3.0.3'
Jul 17 23:05:14 leiferiksson syslog-ng[4479]: syslog-ng starting up; version='3.0.3'
Jul 17 23:36:49 leiferiksson syslog-ng[4479]: Termination requested via signal, terminating;
Jul 17 23:36:49 leiferiksson syslog-ng[4479]: syslog-ng shutting down; version='3.0.3'
Jul 18 14:07:41 leiferiksson syslog-ng[4338]: syslog-ng starting up; version='3.0.3'
Jul 18 14:10:24 leiferiksson syslog-ng[4338]: Termination requested via signal, terminating;
Jul 18 14:10:24 leiferiksson syslog-ng[4338]: syslog-ng shutting down; version='3.0.3'
Jul 18 14:12:48 leiferiksson syslog-ng[4306]: syslog-ng starting up; version='3.0.3'
Jul 18 14:46:18 leiferiksson syslog-ng[4306]: Termination requested via signal, terminating;
Jul 18 14:46:18 leiferiksson syslog-ng[4306]: syslog-ng shutting down; version='3.0.3'
Jul 18 14:47:05 leiferiksson syslog-ng[4481]: syslog-ng starting up; version='3.0.3'
Jul 18 14:53:55 leiferiksson syslog-ng[4481]: Termination requested via signal, terminating;
Jul 18 14:53:55 leiferiksson syslog-ng[4481]: syslog-ng shutting down; version='3.0.3'
Jul 18 15:17:40 leiferiksson syslog-ng[4480]: syslog-ng starting up; version='3.0.3'
Jul 18 15:32:17 leiferiksson syslog-ng[4480]: Termination requested via signal, terminating;
Jul 18 15:32:17 leiferiksson syslog-ng[4480]: syslog-ng shutting down; version='3.0.3'
Jul 18 15:32:19 leiferiksson syslog-ng[5701]: syslog-ng starting up; version='3.0.3'

i don't really know why it's always starting and shutting down...at least it always seems to be running in the end.

Last edited by treysis (2009-07-18 14:07:59)

djszapi

Member

From: Cambridge, United Kingdom

Registered: 2009-06-14

Posts: 1,439

Website

Re: Fbsplash not working - initscripts-issue?

maybe output of /var/log/messages ?

---

http://lpapp.blogspot.com

treysis

Member

Registered: 2009-05-10

Posts: 23

Re: Fbsplash not working - initscripts-issue?

i only have /var/log/messages.log and there's nothing in there (well, there is of course something but no error-messages).

i think i'll have to fix the syslog-ng problem first? any idea how? i don't even know what to search for...

here's my /etc/syslog-ng.conf

@version: 3.0
#
# /etc/syslog-ng.conf
#

options {
  stats_freq (0);
  flush_lines (0);
  time_reopen (10);
  log_fifo_size (1000);
  long_hostnames(off); 
  use_dns (no);
  use_fqdn (no);
  create_dirs (no);
  keep_hostname (yes);
  perm(0640);
  group("log");
};

source src {
  unix-stream("/dev/log");
  internal();
  file("/proc/kmsg");
};

destination d_authlog { file("/var/log/auth.log"); };
destination d_syslog { file("/var/log/syslog.log"); };
destination d_cron { file("/var/log/crond.log"); };
destination d_daemon { file("/var/log/daemon.log"); };
destination d_kernel { file("/var/log/kernel.log"); };
destination d_lpr { file("/var/log/lpr.log"); };
destination d_user { file("/var/log/user.log"); };
destination d_uucp { file("/var/log/uucp.log"); };
destination d_mail { file("/var/log/mail.log"); };
destination d_news { file("/var/log/news.log"); };
destination d_ppp { file("/var/log/ppp.log"); };
destination d_debug { file("/var/log/debug.log"); };
destination d_messages { file("/var/log/messages.log"); };
destination d_errors { file("/var/log/errors.log"); };
destination d_everything { file("/var/log/everything.log"); };
destination d_iptables { file("/var/log/iptables.log"); };
destination d_acpid { file("/var/log/acpid.log"); };
destination d_console { usertty("root"); };

# Log everything to vc12
destination console_all { file("/dev/vc/12"); };

filter f_auth { facility(auth); };
filter f_authpriv { facility(auth, authpriv); };
filter f_syslog { program(syslog-ng); };
filter f_cron { facility(cron); };
filter f_daemon { facility(daemon); };
filter f_kernel { facility(kern) and not filter(f_iptables); };
filter f_lpr { facility(lpr); };
filter f_mail { facility(mail); };
filter f_news { facility(news); };
filter f_user { facility(user); };
filter f_uucp { facility(cron); };
filter f_news { facility(news); };
filter f_ppp { facility(local2); };
filter f_debug { not facility(auth, authpriv, news, mail); };
filter f_messages { level(info..warn) and not facility(auth, authpriv, mail, news, cron) and not program(syslog-ng) and not filter(f_iptables); };
filter f_everything { level(debug..emerg) and not facility(auth, authpriv); };
filter f_emergency { level(emerg); };
filter f_info { level(info); };
filter f_notice { level(notice); };
filter f_warn { level(warn); };
filter f_crit { level(crit); };
filter f_err { level(err); };
filter f_iptables { match("IN=" value("MESSAGE")) and match("OUT=" value("MESSAGE")); };
filter f_acpid { program("acpid"); };

log { source(src); filter(f_acpid); destination(d_acpid); };
log { source(src); filter(f_authpriv); destination(d_authlog); };
log { source(src); filter(f_syslog); destination(d_syslog); };
log { source(src); filter(f_cron); destination(d_cron); };
log { source(src); filter(f_daemon); destination(d_daemon); };
log { source(src); filter(f_kernel); destination(d_kernel); };
log { source(src); filter(f_lpr); destination(d_lpr); };
log { source(src); filter(f_mail); destination(d_mail); };
log { source(src); filter(f_news); destination(d_news); };
log { source(src); filter(f_ppp); destination(d_ppp); };
log { source(src); filter(f_user); destination(d_user); };
log { source(src); filter(f_uucp); destination(d_uucp); };
#log { source(src); filter(f_debug); destination(d_debug); };
log { source(src); filter(f_messages); destination(d_messages); };
log { source(src); filter(f_err); destination(d_errors); };
log { source(src); filter(f_emergency); destination(d_console); };
log { source(src); filter(f_everything); destination(d_everything); };
log { source(src); filter(f_iptables); destination(d_iptables); };

# Log everything to vc12
#log { source(src); destination(console_all); };

Last edited by treysis (2009-07-18 21:50:19)

treysis

Member

Registered: 2009-05-10

Posts: 23

Re: Fbsplash not working - initscripts-issue?

i now made a screenshot of a part of the bootup-process:

Last edited by treysis (2009-07-18 23:11:11)

treysis

Member

Registered: 2009-05-10

Posts: 23

Re: Fbsplash not working - initscripts-issue?

any ideas? maybe at least on the syslog-ng issue, so this way i could investigate on my own!!!

cyberpatrol

Member

From: Germany

Registered: 2006-11-22

Posts: 68

Re: Fbsplash not working - initscripts-issue?

Principally all you need to do to get fbsplash running is to follow the fbsplash wiki article.
Fbsplash and particularly the scripts specific for Arch Linux are working, but still in heavy development. So it can be, that the wiki is also not that clear.

1.
If you want to have a verbose splash (background image) on the text console, then you need to install kernel26-fbcondecor from AUR, which is kernel26 from core with the additional fbcondecor patch, or another kernel with the fbcondecor patch.

If you don't want to have a background image on the text console, then you can use every kernel you like.

2.
Install fbsplash from AUR. This installs the fbsplash daemon.

3.
Install initscripts-extras-fbsplash from AUR. This installs the necessary initscripts. They are seperated from fbsplash, because they are updated more often than fbsplash. So it's not necessary to always compile the daemon, when the scripts are changed.

4.
Install at least one fbsplash theme. You can find some in AUR. Just search AUR for fbsplash. The packages fbsplash and initscripts-extras-fbsplash don't contain a default theme anymore to be more flexible.

5.
Edit /etc/conf.d/fbsplash to your needs. Especially add the name of at least one fbsplash theme you want to use.

6.
Add fbsplash to /etc/mkinitcpio.conf directly after udev:
HOOKS="base udev fbsplash ..."

7.
Add fbsplash at the end of the DAEMONS array in /etc/rc.conf, but before the graphical login manager, if you're using the daemon method to autostart X at boot time:
DAEMONS=(... fbsplash)
or
DAEMONS=(... fbsplash gdm)

8.
Add these kernel parameters and this initrd to /boot/grub/menu.lst:
kernel     vmlinuz26-fbcondecor ... vga=<number of the vga mode> splash=silent,theme:<name of the fbsplash theme> quiet console=tty1
initrd     kernel26-fbcondecor.img

Replace vmlinuz26-fbcondecor and kernel26-fbcondecor by the names of the kernel and the initial ram disk you are using.

9.
Run this command for every kernel you have installed:
mkinitcpio -p kernel26-fbcondecor

Replace kernel26-fbcondecor by the name of the kernel package you are using.

10.
Reboot your PC.

If the package initscripts-extras-fbsplash is updated, check if there's a new version of /etc/conf.d/fbsplash. If it's changed, it's saved as /etc/conf.d/fbsplash.pacnew.

Everytime, when one of the above packages is updated, you need to run step 9.

Maybe we (kujub and me) will merge the packages fbsplash, initscripts-extras-fbsplash and a default theme to one single package one day, when we think the fbsplash related packages for Arch Linux are ready.

Feel free to contact kujub or me via the AUR comments for the corresponding package, if you need further help or find a bug.