You are not logged in.
I've checked it earlier - when I restart splash script, it changes the font to the proper one (i.e. it works properly).
Offline
nice one - great when people are ahead of you! so the problem lies in whether it is running correctly then, i always thought that script was crap! i'll look into it!
Offline
I'd love to see this nicely put into a repo, kernel n all. tbh i never used PKGBUILDS and dun have the time to go figure out how it all works.
Offline
First, putting custom kernels in repos defeats the point so that will never happen (at least from me) - there are plenty of guidelines on the wiki and forum for compiling custom kernels.
Second, all th eother stuff is already in my repo - chop away
Offline
Just want to ask, how early does fsplash start?
Does it start the moment you choose Linux from the bootloader?
Bootsplash starts late and it doesn't really differ alot if you already have to watch the scrolling text during kernel decompression.
Offline
Nah, it starts during the kernel decompression. It scrolls a bit of genuine white text. But I guess it's inevitable, it comes from the nature of initrd or framebuffer or whatever, I don't remember correctly, but I've read about it somewhere.
Offline
what lucke said is correct but i'd like to add that if you use fbvesa rather than fb-tng it does start earlier - i can't see the benefits of fb-tng myself!
Offline
added links to screenshots in the main post of the thread - so updates coming soon based on suggestions by z4ziggy - apparently they make it faster (8 secs?) - but i'm not sure if that is possible as it means my system might start in a negative time with hotplug! i'll do some testing 1st
Offline
nice screenshots and they actually made me go through all this *g*
so just to make sure I got it right.
* make kernel with fb support [compiling right now]
* pacman -S gensplashutils [out of your repo]
* "Create the initramfs image for your prefered theme"
* edit grub/lilo [whichever]
that correct? I am trying to figure out what the worst case scenario could be in case I screw up
this should work with my patched grub [patched it for grubsplash], should it?
ps. the title of this thread really sucks. ultima gensplash just doesn't describe really what's going on imho :twisted:
ArchLinux (x86_64) w/ kdemod
Offline
sorry i'll change the title!
um - yup, you have it about covered, i have the patched grub thing too and it works fine. nothing bad can happen really. you might screw up your grub config but then you'll keep a safe boot option in there won't you? and the fb stuff isn't going to do much at all to your kernel so it's all pretty bullet proof.
this thread has been better summarized in the wiki and i am open to suggestions and help!
i'll have an updated gensplash utils in a day or so and new initscripts so keep em peeled
Offline
hi dibblethewrecker,
thx for changing the title, I think it's better now
I think for the most part I used the wiki entry [i dunno why but your gensplash entry seems to look particularly ugly in our wiki typ, all grey and grey]
I think what I don't like is that the difference between the silent splash and the normal splash way isn't as clear as I'd like.
Like I don't care really about silent splash and since initscripts would have to be patched for it I am quite glad b/c it's one less thing to patch ( patching system things always seems a bit scary to me )
You need the splashutils userspace utilites to make fbsplash work properly. There are several utilites in the package but we are mainly interested in splash_helper, splash_geninitramfs, bootsplash2fbsplash, and splash_util. Splashutils needs to link to your patched kernel source if you build it yourself.
The first utility contains the code to make the splash screen work. The second utility generates a RAM disk image containg splash_helper and the graphics we choose. The third is a utility to convert older bootsplash themes into the new fbsplash format. The last utility allows us to control the silent mode progress bar from the init scripts.
How about you put it in less text but more like this
You need the splashutils userspace utilites to make fbsplash work properly. There are several utilites in the package but we are mainly interested in splash_helper, splash_geninitramfs, bootsplash2fbsplash, and splash_util. Splashutils needs to link to your patched kernel source if you build it yourself.
About the most important tools:
* splash_helper = actual code to make the splash screen work
* splash_geninitramfs = generates a RAM disk image containg splash_helper and the graphics we choose
* bootsplash2fbsplash = convert older bootsplash themes into the new fbsplash format
* splash_util = allows us to control the silent mode progress bar from the init scripts
what do you think?
update:
well kernel, runs, gensplashutils are there. fbsplash is in /boot.. however nothing comes up when I boot.
I added "splash" to the daemons array in rc.conf.
anything else that I forgot??
sidenote:
this kernel option
Support for the framebuffer splash (FB_SPLASH) = Y
I couldn't find it in my kernel config I guess it was important.. I am using the ck6 patch, guess the whole splash part isn't in there. Could that be? Would explain why it's not working..
update 1:
well well well.. the 2.6.10-nitro4 is compiling right now. the missing framebuffer splash option was in there so hopefully with that it works
may I say how nice and easy your packagebuild is with kernel and patches ? I love it
ArchLinux (x86_64) w/ kdemod
Offline
well, the nitro4 kernel is running.. however I have no gensplash *g*
god I feel stupid, can it be that hard??
mith@middleearth|[~]:~ > uname -r
2.6.10-nitro4-arch
I do have the proper options enabled I do believe
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_FB=y
CONFIG_FB_VESA=y
CONFIG_FB_VESA_STD=y
CONFIG_FB_SPLASH=y
# CONFIG_LOGO is not set
gensplashutils 0.9-5 are installed.
The actual image for the theme is there too and I do believe that menu.lst is setup correctly
-rw-r--r-- 1 root root 525258 2005-02-25 19:07 /boot/fbsplash-ArchMetal-1024x768
title Arch -nitro4
root (hd1,0)
kernel /boot/vmlinuz2610-nitro4-arch root=/dev/discs/disc1/part1 video=vesafb:ywrap,mtrr,1024x768-32@70 splash=verbose,theme:ArchMetal
initrd /boot/fbsplash-ArchMetal-1024x768
I guess I'll give up for now.. :evil:
ArchLinux (x86_64) w/ kdemod
Offline
ok - re: the wiki - change it however you think is best - it is a nightmare to keep up to date - i would appreciate the help! Your proposed changes look good.
second...try, instead of the video= line, just try vga=791 (i think - all the options are in the /etc/splash/lilo.sample file) - you only need the video line if you use fbvesa-tng
I need to update the bootloader section too - it is the same as the original and it is far too wordy!
P.S. AFAIK -ck doesn't contain the fbsplash patches
Offline
there is now updated gensplashutils and initscripts pkgs on my server.
I have cleaned up the rc.d/splash script - it's now called gensplash - so you will need to alter you rc.conf.
The script should now not produce any errors about being run on the wrong terminal - it still starts unreliably tho! I am working on that.
i also added some changes to initscripts that z4ziggy suggested. He suggested they would make verbose startup faster but i have noticed no big difference - they seem like good changes any way so thanks z4ziggy!
Offline
hooray *g*
Finally it's working!! I updated to your new package and also changed that vga line in my menu.lst. It clearly states to do so in your wiki page but I just didn't see it. . .
anyway, I updated your wiki with your latest PKGBUILD and changed the layout of the info about the tools used.
However I do get error messages while starting. Line 29 and line 35 of whatever gensplash file..
Unfortunately I have no clue if and where those startup messages are logged, otherwise I'd paste the error messages in here
update:
hey dibble,
I hope you don't mind but I messed around with your wiki entry. I replaced all the PKGBUILDs with links to your server. I believe that should be enough, who really cares about every single line can just look it up there.
Also I kicked out that warning for the bootloader.. people messing with gensplash should know what they're doing. It's still pretty foolproof though . I wish our wiki would support some color, things could be so cool and much easier to understand / highlight.. oh well.. guess it's not gonna happen for a while
ArchLinux (x86_64) w/ kdemod
Offline
no worries, mith, go for it!
the gensplash script has become a royal pain in the butt for me - it has never worked properly and i don't think i really have what it takes to fix it. I have a reworked version now which i'll upload soon. But as i have said many times before i have no inet connection so i can't do it easily
If you want to duplicate the error you could always try restarting the daemon /etc/rc.d/gensplash restart - if there are errors in teh script that should show them up
Offline
dibble: could you link me to the gentoo initscripts? i want to have a look at them and fiddle with them myelf. thanks
Offline
gentoo invokes these mechanisms through an entirely different system, using static devices and a script that can be run much sooner (or so i understand it)
I developed the current initscripts patches based entirely on brice's old bootsplash patch, which, no offense to him, was fairly simplistic but did the job. I don't actually know what some of the bash commands do to be honest!
The gensplash script discussed above is directly ported from the splash-init script that gentoo uses to start the vc backgrounds.
http://dev.gentoo.org/~spock/projects/g … .4.tar.bz2
I think this is the scripts that gentoo uses - i have looked through them but in isolation from the rest of the gentoo stuff they don't mean much to me.
I apologise for sounding defensive about this but i worked my arse off to do this with virtually no help aside from great testers, despite repeated requests and when someone shows up and says "i want to have a look at them and fiddle with them myelf", which doesn't seem like a very friendly offer to help but rather to do it their way - i feel justified in feeling so.
Although, in the long run it might actually be good
and, iphitus, seeing as i had to search the web for them for weeks you could have too
Offline
hey dibble,
cheer up
anyway,
I have no clue about all this kernel / initram / etc. crap so I can't really help you much there.. The whole gensplash bash file doesn't seem to help that much either, I mean I can read and try to understand it, possibly fill in the functions from /etc/functions but still I don't think I could help you out making the whole thing work better for arch
( though I'd sure like to.. )
ArchLinux (x86_64) w/ kdemod
Offline
yeah - i'm not bitter, just depressed!
Offline
Hey great job... Now theres just one small bug i get.... Some gettheme command doesnt exist and something else... Running in verbose mod if ya need to know. Also how do you make the verbose splash on each virtual console?
Offline
To get splashes on every virtual console, just run /etc/rc.d/gensplash (or add it to rc.conf).
ps. Just for reminder: this font bug still persists, dibble :-)
Offline
I am running /etc/rc.d/gensplash...
Offline
hey guys,
I got a question for ya.. I thought about and started writing a little bash script that kinda could add the necessary entries to menu.lst
Do you think that would be a good thing to have or not? I am just asking to save myself time and thoughts about the whole thing.. also it could maybe work as a theme switcher, you know like give a list of avaiable themes and then based on a selection edit menu.lst or at least print out the proper new lines or I-don-t-know-what-else
I thought it could try to auto-detect what fb driver is in the kernel and if fbsplash at all is avaiable and according to that just give out the necessary lines for menu.lst
what do you think?
ArchLinux (x86_64) w/ kdemod
Offline
Mith - worth a try - even if it is just to exercise the mind - grep kconfig for the fb type for starters
I have to apologise for dropping the ball a bit - in my last pkg gensplash was screwed up and i haven't actually updated the genplash-files pkg on the server at all - so if you built you own gensplashutils pkg you really need to build a new one!
There is now a new gensplashutils pkg up - hopefully the gensplash script you should be better - could you all give that one a test - specially the font prob!
Offline