You are not logged in.
works like a charm here
Thank you!
Offline
Is it possible to have a fancy progressbar like Ubuntu's? I know you can with fbsplash.
There should be such thing in splashy 0.4.
I thought that they don't want initscripts patched. They want you to override functions and put them in functions.d.
That's the only patch needed until we find out a workaround for killall5
I'm using GDM in the daemons array.
Also, I'm having issues with themes. It falls back to default. It might show archlinux-simplyblack at shutdown for the first time when you enable it, but that's it. It falls back to default. It can also drop you in tty1 instead of tty7.
I already fixed gdm/kdm/xdm/slim as daemon (in the DAEMON array in rc.conf)
I will look in the console behavior because splashy is acting weird (i think it's time to backport important fix from git).
I'm having one small problem. The scripts don't seem to support the inittab method of launching a display manager. It works fine if I add GDM to my daemons array, but if I try to do this method (run level 5) Splashy just hangs on the last daemon launched and I have to ctrl+alt+del to restart.
Confirmed, the script doesn't work when you set initlevel 5 in /etc/inittab. I will look for a fix.
Thank you everybody for testing my work!
Offline
luciferin wrote:I'm having one small problem. The scripts don't seem to support the inittab method of launching a display manager. It works fine if I add GDM to my daemons array, but if I try to do this method (run level 5) Splashy just hangs on the last daemon launched and I have to ctrl+alt+del to restart.
Confirmed, the script doesn't work when you set initlevel 5 in /etc/inittab. I will look for a fix.
i dont have that behaviour when using inittab 5 although im using kdm so the issue might only relate to gdm
dovie andi se tovya sagain
Offline
lexiw wrote:luciferin wrote:I'm having one small problem. The scripts don't seem to support the inittab method of launching a display manager. It works fine if I add GDM to my daemons array, but if I try to do this method (run level 5) Splashy just hangs on the last daemon launched and I have to ctrl+alt+del to restart.
Confirmed, the script doesn't work when you set initlevel 5 in /etc/inittab. I will look for a fix.
i dont have that behaviour when using inittab 5 although im using kdm so the issue might only relate to gdm
I'm using gdm in inittab and runlevel 5 and don't have that problem. But i do have the black blinking squares at the top of the screen, but it doesn't annoy me.
Great work btw
Offline
I have problem with splashy. Splash screen is shown for a while and it suddenly disappears (I suppose it happens when the progress bar is to be shown). I fails with:
Couldn't splashy_start_splashy(). Error -10
This message is shown because the function init_font() fails, but I have no idea how to investigate it further.
To make matters worse - it used to work, but I can't reproduce it. I rebooted few times, reinstalled, reran mkinitcpio, rebooted few times again and sometimes it was ok, but I can't tell why.
I have Compaq Evo n800w laptop with ATI Radeon 9000 onboard. I tried release 4, 5 and now 6 of your splashy package and it's the same. I tried it with radeonfb and first time it was fine, but I decided to change, because of low colour depth. Now i use v86d, but still it feels the error is quite random regardless of framebuffer choice.
Here are my configs
/boot/grub/menu.lst
kernel /vmlinuz26 root=/dev/sda7 ro loglevel=0 splash
/etc/rc.conf
SPLASH="splashy"
/etc/mkinitcpio.conf
HOOKS="base v86d keymap autodetect udev pata splashy"
Offline
j.roszk, are you running from the testing repo? I had some issues until I enabled that (ran -Syu, then reinstalled the splashy packages)
Try changing your hooks to this:
HOOKS="base v86d splashy keymap autodetect udev pata"
Then reinstall your kernel.
Last edited by luciferin (2008-05-24 16:39:25)
Offline
I can't get v86d to work? Does it work on ATI?
Offline
I'm trying to get splashy working, and by so far, it works with arch-black-splashy theme, which comes within the AUR-package. But when changing the theme to anything (even default) it isn't working. I'm seeing "Loading initramfs" text and after that, when splashy is supposed to pop up, i only get blinking cursor for a second, and then normal verbose text boot, without any pictures.
Running splashy test as root works charmly, running it as an user it gives me "Framebuffer is not configured properly" but that's expected, right?
I have SPLASH="splashy" in my rc.conf and splashy in hook-section of mkinitcpio.conf and quiet vga=791 splash in menu.lst
What's wrong? Any ideas highly appreciated, thanks
Last edited by Detegr (2008-05-24 19:26:55)
Offline
I'm trying to get splashy working, and by so far, it works with arch-black-splashy theme, which comes within the AUR-package. But when changing the theme to anything (even default) it isn't working. I'm seeing "Starting initramfs" text and after that, when splashy is supposed to pop up, i only get blinking cursor for a second, and then normal verbose text boot, without any pictures.
Running splashy test as root works charmly, running it as an user it gives me "Framebuffer is not configured properly" but that's expected, right?I have SPLASH="splashy" in my rc.conf and splashy in hook-section of mkinitcpio.conf and quiet vga=791 splash in menu.lst
What's wrong? Any ideas highly appreciated, thanks
When you use another theme you have to mkinitcpio -g /boot/kernel26.img (as root) again. Does it give you any errors when you do that?
Madly in love with Arch64, Openbox, DotA, and of course... penguins!
Happy to help if you're not a Help Vampire. Use your wonderful resources like ArchWiki, Google, and our wonderful search page.
Offline
Yeah, i have done that but with no luck. I Forgot to mention that, sorry.
Offline
Yeah, i have done that but with no luck. I Forgot to mention that, sorry.
I've never tested any splashy theme not included in the splashy-themes package. Remember that the old splashy package (the one in aur) works a lot different from my version. The same is for initscripts-splash.
Here's a new version: http://slexiw.netsons.org/files/splashy-stuff3.tar.gz
-Fixed gdm/xdm/kdm/slim as daemons
-Fixed initlevel 5
-(should be) Fixed the console switching (but i'm probably wrong)
Edit:
A little note: after you upgrade splashy or change the theme, remember to rebuild your initramfs.
Last edited by lexiw (2008-05-24 19:44:13)
Offline
Yeah, got it working. I needed to edit theme.xml image files for just "boot.png" etc. instead of "/usr/share/splashy/themes/<theme>/boot.png"
Thanks for the help anyway!
Just one thing, how can i run the initrc script for shutdown image when shutting my system down? It seems that splashy isn't running when shutting down...
Last edited by Detegr (2008-05-24 19:50:53)
Offline
Offline
After the last update, it doesn't show up on boot any more.
Offline
After the last update, it doesn't show up on boot any more.
Do you get the usual messages and the system boots normally?
Offline
Great work! Will it work without the testing-repo? I'd really like to try it out but I dont have the time to fix anything that activating testing could break.
Offline
SpookyET wrote:After the last update, it doesn't show up on boot any more.
Do you get the usual messages and the system boots normally?
Yeah. I got quiet boot though. I should not see them.
Offline
lexiw wrote:SpookyET wrote:After the last update, it doesn't show up on boot any more.
Do you get the usual messages and the system boots normally?
Yeah. I got quiet boot though. I should not see them.
Quiet boot only hides the kernel messages. You'll still have the regular boot process thrown up on your screen (the list of everything that's being started).
New packages fixed all my problems on boot. Everything is working perfectly here now.
Last edited by luciferin (2008-05-25 04:16:22)
Offline
SpookyET wrote:lexiw wrote:Do you get the usual messages and the system boots normally?
Yeah. I got quiet boot though. I should not see them.
Quiet boot only hides the kernel messages. You'll still have the regular boot process thrown up on your screen (the list of everything that's being started).
New packages fixed all my problems on boot. Everything is working perfectly here now.
That's the thing. It worked with the older packages. It doesn't now.
Offline
luciferin wrote:SpookyET wrote:Yeah. I got quiet boot though. I should not see them.
Quiet boot only hides the kernel messages. You'll still have the regular boot process thrown up on your screen (the list of everything that's being started).
New packages fixed all my problems on boot. Everything is working perfectly here now.
That's the thing. It worked with the older packages. It doesn't now.
I've been playing around with theme selection and I think I've got this a little figured out. My "/etc/splashy/config.xml" has to look just like this to get it to show up on boot. My "current_theme" selection shows up on shutdown no matter what, but whatever I have selected for the "default_theme" shows up on boot, or splashy fails to launch on certain initramfs. That's as much as I've been able to figure out.
<?xml version="1.0" encoding="UTF-8"?>
<!-- Automatically generated by splashy_config. Do not edit -->
<splashy>
<!-- themes directory: conventional path /etc/splashy/themes -->
<themes>/usr/share/splashy/themes</themes>
<!-- current theme could be relative the themes defined above or full path $
<current_theme>archlinux-simplyblack</current_theme>
<!-- full path to theme to fall back in case of problems. DO NOT CHANGE -->
<default_theme>/etc/splashy/themes/archlinux-simplyblack</default_theme>
<pid>/etc/splashy/splashy.pid</pid>
</splashy>
Offline
Not good:
[root@LTS-Arch ~]# tupac -S splashy-themes
resolving dependencies...
looking for inter-conflicts...Targets: archlinux-wallpaper-1.2-1 splashy-themes-0.3-1
Total Download Size: 0.00 MB
Total Installed Size: 11.60 MBProceed with installation? [Y/n] y
:: Retrieving packages from archlinuxve...
splashy-themes-0.3-... 2.2K 203.9K/s 00:00:00 [#####################] 100%
checking package integrity...
:: File splashy-themes-0.3-1-i686.pkg.tar.gz is corrupted. Do you want to delete it? [Y/n] n
error: failed to commit transaction (corrupted package)
file splashy-themes-0.3-1-i686.pkg.tar.gz was corrupted (bad MD5 checksum)
Errors occurred, no packages were upgraded.
:S
I tried to download it again, but still no luck...
Proud Ex-Arch user.
Still an ArchLinux lover though.
Currently on Kubuntu 9.10
Offline
Seems the repository is down, at least for me.
Cerebral: "Welcome to the distro. You'll never leave. Mwahaha"
Offline
@luciferin: To me it seems that changing the theme first affects the shutdown screen and only effects the boot screen when creating a new initial ramdisk.
So, after chosing a theme and modifying the splashy-config, run "mkinitcpio -g /boot/kernel26.img" , that should make splashy use the "new" theme that you chose.
Offline