Bug#455872: [Splashy-devel] Bug#455872: splashy: Fails to initialize, messes up loading other modules
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 0018 rip 2611de7774c7 rsp 7fffce751248 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]
Processed: Re: Bug#455872: splashy: Fails to initialize, messes up loading other modules
Processing commands for [EMAIL PROTECTED]: clone 455872 -1 Bug#455872: splashy: Fails to initialize, messes up loading other modules Bug 455872 cloned as bug 459447. submitter -1 Luca Capello [EMAIL PROTECTED] Bug#459447: splashy: Fails to initialize, messes up loading other modules Changed Bug submitter from Georg Wittenburg [EMAIL PROTECTED] to Luca Capello [EMAIL PROTECTED]. (By the way, that Bug is currently marked as done.) retitle -1 should start after udev Bug#459447: splashy: Fails to initialize, messes up loading other modules Changed Bug title to `should start after udev' from `splashy: Fails to initialize, messes up loading other modules'. (By the way, that Bug is currently marked as done.) found -1 0.3.7-1 Bug#459447: should start after udev Bug marked as found in version 0.3.7-1. severity -1 important Bug#459447: should start after udev Severity set to `important' from `critical' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#455872: splashy: Fails to initialize, messes up loading other modules
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 0018 rip 2611de7774c7 rsp 7fffce751248 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 Thx, bye, Gismo / Luca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Dec 20, 2007 2:45 AM, Georg Wittenburg [EMAIL PROTECTED] wrote: Hi, with regard to the screen corruption I mentioned in my previous, have a look at the attached screenshot. Regards, Georg Yeah I've seen that myself. And in fact, the directfb devels know about this [1]. I'm trying to address that problem for 0.3.9. 0.3.8 is out and it should fix most of the current bugs. Sit tight as we are now in holiday mode and everybody is away from their keyboards ;-) Notes: 1. http://mail.directfb.org/pipermail/directfb-dev/2007-December/003775.html -- )(- 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) --
Bug#455872: splashy: Fails to initialize, messes up loading other modules
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for the delay, I forgot to subscribe the bug...
This looks like udev is not starting properly. Can you move
/usr/share/initramfs-tools/scripts/init-top/splashy to
/usr/share/initramfs-tools/scripts/init-bottom/z_splashy
udev is still screwed up. (Moreover, update-initramfs is going crazy,
with a lot of errors about dpkg wrong options and building initrd for
non-installed kernels! I can't understand...).
Also, I have attached 2 scripts to this email. /etc/lsb-base-logging.sh and
/etc/console-tools/config.d/splashy. Please use this scripts to replace the
ones that you have. These come straight from our Git repository (See more
here http://splashy.alioth.debian.org/wiki/developers).
GDM starts now, but Splashy crashes ('killed by '). Further tests
needed.
If you have libdirectfb-0.9.25-x installed, can you please remove it?
It seems that even though Splashy links against libdirectfb-1.0.x (from
Sid), the binary tries to access the older version of the lib causing the -3
errors.
Removing libdirectfb-0.9.25-x and leaving libdirectfb-1.0.x only splash
screen appears, but with the black blocks reported by Georg Wittenburg.
Anyway screen glitches during fade-in fade-out and.
I removed splashy packages, for now, I will retry later, restarting from
scratch... Holidays are for me too!
Happy new year!
- --
Alessio Gaeta
http://meden.uni.cc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHansdirbk3DO+UZ0RAiyIAKCz/quESoiJSceccwi8c56pGWiGqgCfZNr8
vCMpGwL1mA2CAkQ6L1lwgL8=
=sOd2
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Tuesday 18 December 2007 16:31:09 Luis Mondesi wrote: If you have libdirectfb-0.9.25-x installed, can you please remove it? It seems that even though Splashy links against libdirectfb-1.0.x (from Sid), the binary tries to access the older version of the lib causing the -3 errors. Please report back ASAP as we are getting ready to do a bug fix release. Removing libdirectfb-0.9.25 definately helped. Splashy now generally works, although not perfectly: 1) After about 5% progress while booting, the boot process stalls (with Splashy visible) until F2 is pressed, at which point booting continues (Splashy still being displayed). 2) After logging into X, there are some small black spots near the top of the screen. This is X.org 1:7.3+8 with NVidia drivers 100.14.19-1 compiled from source. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ signature.asc Description: This is a digitally signed message part.
Bug#455872: splashy: Fails to initialize, messes up loading other modules
If you have libdirectfb-0.9.25-x installed, can you please remove it? It seems that even though Splashy links against libdirectfb-1.0.x (from Sid), the binary tries to access the older version of the lib causing the -3 errors. Please report back ASAP as we are getting ready to do a bug fix release.
Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Dec 15, 2007 12:05 PM, Alessio Gaeta [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I can confirm this bug, it happens on my machine too. The problem shows itself only when the parameter splashy is passed to the kernel. If I remove it, the system boots normally, but for the bug #455685 (Splashy makes GDM initscript fail. Symptoms are the same: splashy fails to start with error code - -3 from splashy_start_splashy(), no sound, no usbhid, no networking... Hotplugging doesn't work at all, modules aren't automatically loaded and modprobe rules aren't satisfied (i.e. I have a rule to load usbnet whith cdc_subset, but when I plug my Linux Ipaq in the cradle the module cdc_subset isn't loaded; if I probe the module manually the module usbnet isn't automatically loaded. I noted that when starting without the parameter splashy i can see the log line Waiting for /dev to be fully populated...done. but with splashy activated that line doesn't appear. So I guess it is a udev (odd-)interaction problem (or maybe a more complicated splashy/udev/initramfs-tool, seen problems of update-initramfs with udev...). Moreover, it happens that if I reboot and temporary delete the initrd line from GRUB (my kernel can boot without initrd, but I need it for uswsuspend), boot fails because /dev is completely screwed up. Hello, Sorry for taking so long to reply (holidays are almost here!) Can you do a test for me? As root, run the following on your system: mv /usr/share/initramfs-tools/scripts/init-top/splashy /usr/share/initramfs-tools/scripts/init-bottom/z_splashy update-initramfs -u make sure that you put back splash vga=791 to your kernel boot parameters. Note that it's not splashy but splash. Also, I have attached 2 scripts to this email. /etc/lsb-base-logging.sh and /etc/console-tools/config.d/splashy. Please use this scripts to replace the ones that you have. These come straight from our Git repository (See more here http://splashy.alioth.debian.org/wiki/developers). Please report back your experience. If this is too much for you to do, then you can hold on for the next Splashy revision (which should come out pretty quickly). Regards, -- )(- 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) -- console-tools_config.d_splashy Description: Binary data etc_lsb-base-logging.sh Description: Bourne shell script
Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Dec 12, 2007 3:13 AM, Georg Wittenburg [EMAIL PROTECTED] wrote: Package: splashy Version: 0.3.7-1 Severity: critical Justification: breaks the whole system Hi! 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 haven't seen any suspicios messages in dmesg or syslog that would point to what exactly the problem is, but I could provide the output if necessary. As a workaround I removed splash from the kernel command line and the system works fine. Regards, Georg This looks like udev is not starting properly. 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. We will do a minor (bug fix) release shortly. If you can send us the result of this test it will be greatly appreciated. Regards, -- )(- 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) --
Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Tuesday 18 December 2007 04:47:11 Luis Mondesi wrote: On Dec 12, 2007 3:13 AM, Georg Wittenburg [EMAIL PROTECTED] wrote: Package: splashy Version: 0.3.7-1 Severity: critical Justification: breaks the whole system Hi! 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 haven't seen any suspicios messages in dmesg or syslog that would point to what exactly the problem is, but I could provide the output if necessary. As a workaround I removed splash from the kernel command line and the system works fine. Regards, Georg This looks like udev is not starting properly. 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. We will do a minor (bug fix) release shortly. If you can send us the result of this test it will be greatly appreciated. Regards, Unfortunately, even with the new initrd, the problem remains unchanged. In fact, on shutdown splashy segfaults (I assume it did that, too, prior to the changes). If the problem had to do with hardware initialization, I find it strange that splashy should crash when the system is going down. The exact message (as captured with `splashy test`) is segfault at 000c eip b7efb27d esp bfcab720 error 4 Two more bits of information: On boot, just before I get error code -3 from splashy_start_splashy(), it complains that it can't open /dev/fb0. Further, NetworkManager also gives me errors on shutdown, if splashy is enabled. It's quite a bit of text and I'm unsure how to capture that. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ signature.asc Description: This is a digitally signed message part.
Bug#455872: splashy: Fails to initialize, messes up loading other modules
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I can confirm this bug, it happens on my machine too. The problem shows itself only when the parameter splashy is passed to the kernel. If I remove it, the system boots normally, but for the bug #455685 (Splashy makes GDM initscript fail. Symptoms are the same: splashy fails to start with error code - -3 from splashy_start_splashy(), no sound, no usbhid, no networking... Hotplugging doesn't work at all, modules aren't automatically loaded and modprobe rules aren't satisfied (i.e. I have a rule to load usbnet whith cdc_subset, but when I plug my Linux Ipaq in the cradle the module cdc_subset isn't loaded; if I probe the module manually the module usbnet isn't automatically loaded. I noted that when starting without the parameter splashy i can see the log line Waiting for /dev to be fully populated...done. but with splashy activated that line doesn't appear. So I guess it is a udev (odd-)interaction problem (or maybe a more complicated splashy/udev/initramfs-tool, seen problems of update-initramfs with udev...). Moreover, it happens that if I reboot and temporary delete the initrd line from GRUB (my kernel can boot without initrd, but I need it for uswsuspend), boot fails because /dev is completely screwed up. Regards - -- Alessio Gaeta meden.uni.cc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHZAlairbk3DO+UZ0RAg2GAKCeUmCGeaeZxI2gZepiV9K/FFIS5QCg7IkQ VFb7U1jfvFuzDId9S0Tp+fo= =3uO9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#455872: splashy: Fails to initialize, messes up loading other modules
Package: splashy Version: 0.3.7-1 Severity: critical Justification: breaks the whole system Hi! 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 haven't seen any suspicios messages in dmesg or syslog that would point to what exactly the problem is, but I could provide the output if necessary. As a workaround I removed splash from the kernel command line and the system works fine. Regards, Georg -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages splashy depends on: ii initramfs-tools 0.90atools for generating an initramfs ii libc6 2.7-3GNU C Library: Shared libraries ii libdirectfb-1.0-0 1.0.1-5 direct frame buffer graphics - sha ii libgcc1 1:4.2.2-4GCC support library ii libglib2.0-02.14.3-1 The GLib library of C routines ii libmagic1 4.21-3 File type determination library us ii libsplashy1 0.3.7-1 Library to draw splash screen on b ii lsb-base3.1-24 Linux Standard Base 3.1 init scrip ii zlib1g 1:1.2.3.3.dfsg-6 compression library - runtime splashy recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
