On Jan 6, 2008 11:10 AM, Luca Capello <[EMAIL PROTECTED]> wrote: > clone 455872 -1 > submitter -1 Luca Capello <[EMAIL PROTECTED]> > retitle -1 should start after udev > found -1 0.3.7-1 > severity -1 important > thanks > > Hello! > > IMHO this bug was a mix of two: the one related to the libdirectfb > version and the other one related to udev. While the first one is > closed, the second one remains, thus the cloning (-1). > > BTW, I cc:ed all the people involved in the bug, but setting myself as > the new submitter. > > On Tue, 18 Dec 2007 04:47:11 +0100, Luis Mondesi wrote: > > On Dec 12, 2007 3:13 AM, Georg Wittenburg <[EMAIL PROTECTED]> wrote: > >> After upgrading to splashy 0.3.7, splashy fails to start with error code > >> -3 from splashy_start_splashy(). > >> > >> What is worse, several unrelated other modules fail to load afterwards, > >> e.g. all sound drivers (snd_*) and the WLAN driver iwl4965. This > >> effectively breaks sound and networking on my system. > > I can reproduce it (but with error code -2) booting with just "splash" > (so no fb) on my sid-amd64. Various unrelated modules are messed up, > e.g. X cannot start because /dev/agpgart doesn't exist (and manually > loading the intel-agp module doesn't change anything). > > > This looks like udev is not starting properly. > > Indeed udev has some problems with splashy, here the output I recorded > on my MiniDV: > ===== > Starting the hotplug event dispatcher: udevdSplashy ERROR: Connection refused > Splashy ERROR: Coudln't splashy_start_splashy(). Error -2 > > splashy[1588]: segfault at 0000000000000018 rip 00002611de7774c7 rsp > 00007fffce751248 error 4 > ===== > > > Can you move /usr/share/initramfs-tools/scripts/init-top/splashy to > > /usr/share/initramfs-tools/scripts/init-bottom/z_splashy > > > > and redo your initrd? > > > > update-initramfs -u > > > > That should allow udev to start first and it should fix your problem. > > This works only when splashy is inside the initramfs. For the other > case, you need to move the splashy rc script after udev, something like > > $ mv /etc/rcS.d/03splashy /etc/rcS.d/z_splashy > > This fixes the problem and splashy nicely starts :-D
I'm guessing then that Splashy should always be used from initramfs or after udev when not from initramfs? Perhaps there is another way of doing this. Is there something we can do to work with udev? I know I did a test that splashy was started after udev in initramfs and that just didn't work as expected. I dunno outside of initramfs. -- ----)(----- Luis Mondesi Maestro Debiano ----- START ENCRYPTED BLOCK (Triple-ROT13) ------ Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. ----- END ENCRYPTED BLOCK (Triple-ROT13) ------ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
