<br><br><div class="gmail_quote">On Nov 20, 2007 10:23 AM, Johannes Wagner <<a href="mailto:dongiovanni@archlinux.de">dongiovanni@archlinux.de</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>first of all thanks for the help with the shared libraries. If splashy is used on boot, there is a small black square on the top left corner. Others report small black lines on the top. I get these if I use vga=792. If I use vga=795 I get the square. This happens not only on Archlinux, where I wrote the scripts myself, but also on Ubuntu. I read about this also on the bug tracker, but that doesn't solve this issue for me. Splashy is definitely killed bevor X is started. Another thing is, that if I use plain text consoles, I have to push any key to see somthing on the screen after splashy exits... Any ideas?
<br></blockquote></div><br>If you don't start Splashy during boot, do you still get those artifacts? (especially if you don't change anything else)<br><br>Are you running Splashy from initramfs? This might have something to do with you having to press ENTER for getty to start your text console. Try setting /etc/default/splashy to change to a tty that is not used (after boot), like 8 or 9.
<br><br>I changed the default for this on our Git repo so that Splashy stays in the same console that it was started from (tty2 typically, if running from initramfs).<br><br>These might be problems with directfb (in fact, they are), since Splashy itself does not talk to the framebuffer. There might be a tweak that one can do on /etc/directfbrc to fix these artifacts... (a good thing to ask in directfb-users).
<br><br>Regards,<br>-- <br>----)(----- <br>Luis Mondesi<br>Maestro Debiano<br><br>----- START ENCRYPTED BLOCK (Triple-ROT13) ------<br>Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq.<br>
----- END ENCRYPTED BLOCK (Triple-ROT13) ------