Here I found something that sounds interesting:
http://ubuntuforums.org/archive/index.php/t-75132.html
It seems that the timeout can be changed in
/usr/share/initramfs-tools/scripts/init-top/usplash by adding
/sbin/usplash_write TIMEOUT 60 at the end of the file.
What do you think?
Florian
--
Florian, if you do: grep 'TIMEOUT' /etc/init.d/* you'll see that several
start-up scripts change the timeout. You can try modifying checkfs.sh if you
like.
See bug #22658 for more on this.
--
[PATCH] two simple errors in /etc/init.d/mountall.sh
https://launchpad.net/bugs/28447
--
ubuntu-bugs
Thanks Tormod, that worked for me!
Florian
--
[PATCH] two simple errors in /etc/init.d/mountall.sh
https://launchpad.net/bugs/28447
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sounds interesting because my bootprocess gets interrupted by verbose
mount output too. But how to apply this patch?
--
[PATCH] two simple errors in /etc/init.d/mountall.sh
https://launchpad.net/bugs/28447
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
dorpm, the patch is not valid any longer. The scripts were later
changed, and now look different in both 6.06 final and in edgy.
Can you please attach your /dev/.initramfs/usplash_log ?
--
[PATCH] two simple errors in /etc/init.d/mountall.sh
https://launchpad.net/bugs/28447
--
ubuntu-bugs
Here you are:
TEXT Loading essential drivers...
SUCCESS ok
PROGRESS 1
TIMEOUT 180
TIMEOUT 15
TEXT Mounting root file system...
TIMEOUT 540
TIMEOUT 15
SUCCESS ok
PROGRESS 2
PROGRESS 4
TEXT Reading files needed to boot...
SUCCESS ok
PROGRESS 6
TEXT Setting hostname 'mm-home'...
SUCCESS ok
PROGRESS
Florian, since your usplash_log stops at Checking root file system, I
think it is the checking of the root fs that takes so much time that
usplash quits, and you get all these messages afterwards.
--
[PATCH] two simple errors in /etc/init.d/mountall.sh
https://launchpad.net/bugs/28447
--
Is there a time-dependency?
Unfortunately the log was from a boot process where the root fs was
completely checked. But normally there is not much more in the log:
TEXT Checking root file system...
SUCCESS ok
PROGRESS 27
PROGRESS 29
PROGRESS 31
TEXT Checking all filesystems...
At the latest
usplash has a timeout, so that if something takes longer than normally
expected, the splash screen goes away so that the user can read the
messages and see what is going on. Probably you have some filesystems
that are slow to check.
I experienced this myself when I had two vfat filesystems in
