Bug #170
closed
Feature #81: Improve CD boot and shutdown
Splashy does not start in initramfs
Description
Splashy should start during very early boot since the initramfs option was set. Uncompressing the initramfs file shows that all the required files to start splashy are in the RAM disk file. Using the pause feature of VirtualBox made it possible to shortly see the splashy boot screen during early boot. However it immediately disappeared and was later replaced by messages “Splashy ERROR: connection refused”.
Searching for this message lead to the following thread:
http://lists.alioth.debian.org/pipermail/splashy-users/2008-February/000347.html
It seems that splashy should start after udev to avoid this kind of error. In the initramfs file, both are started from the directory /scripts/init-bottom/ without dependency information, which means splashy should start first due to alphabetical order. So we propose 2 solutions:
- add a dependency using the variable
PREREQSof the splashy script - rename both scripts by adding numbering before the name
The first solution requires patching the package splashy only, as the second one needs a patch for udev too a priori.
Updated by Jean-Michel Philippe almost 13 years ago
- Due date set to 05/26/2011
- Category set to System
- Assignee set to Jean-Michel Philippe
- Target version set to 2011-05 (Gondwana)
- % Done changed from 0 to 20
- Estimated time set to 2:00 h
Updated by Jean-Michel Philippe almost 13 years ago
- % Done changed from 20 to 50
The first solution has be tested and did not solve the issue. It is not obvious that this issue could be solved quickly…
Updated by Jean-Michel Philippe almost 13 years ago
- Status changed from New to Won't fix
- % Done changed from 50 to 100
The second solution has been tested too and it is failing too :(. We have to close this ticket and hope the issue will be solved in Debian Squeeze.