SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My first post here.. I've been using this forum quite some time now, and it solved a lot of my problems/worries..
But it didn't solved my problem with bootsplash (not even after a long long long night of googling on this).
I've installed the patch into my kernel sources (2.6.18), config-ed the kernel, build the damn thing, installed the modules, etc, etc, etc.. Been doing this quite some time now, and i don't think i've missed a thing.
After that i'm getting stuck. The kernel has been build the right way, added an entry in lilo.conf, used lilo to save it, reboot, and the kernel is working.
After that i'm trying to generate a bootsplash. Using the bootsplash util "splash" with some nice downloaded bootsplashes seems to generate a initrd.gz in my /boot directory.
In the howto/website of bootsplash.org it says that i need to add this one to my lilo.conf..(and saved) which i did..
After a reboot my screen gets blank.. and it looks like it's hanging.
After some research i've found an error about gzip magic numbers. Looks like a corrupt gz file to me..
I've tried a lot of thing to get it to work.. nothing, nada, niets, noppes.
Also.. if i add a vga= options to my lilo.conf (i.e. vga=799 which is supported with my video card (radeon 9550) and monitor (intergraph 21")) it says that it's not a correct input option...
anyone has a idea?
I'm at work now.. so i can't post my lilo.conf (perhaps tonight)
Indeed, without you showing any of your configuration files, no idea at all.
I hope you ran "lilo" again after adding the initrd line to /etc/lilo.conf ?
i've ran /sbin/lilo with this one.. just a blank (black) screen.
The vga=0x0330 isn't good IMO, caus everywhere i look it says it has to be something like 799 (in my case 24 bit, 1600x1200)
in my first post i said initrd.gz.. that one is renamed to the above, everything seems to work without the initrd, no errors what so ever..
but with the initrd on (no # in front) it's going blank
Nope.. I've tried 791 to 799. Even tried it with 0x in front of it.. but lilo says it's not a number. I've also tried the 0x033E like numbers, but also nothing there.
I've compiled my kernel with the setting 1600x1200-16@60 for the vesafb (in this case with de fbsplash instead of bootsplash), also nothing.
ok.. a small update in my quest to get it to work...
my lilo.conf contains a vga=795 option, which is supported by my video card (ati radeon 9550) and monitor (intergraph 21sd95).
as soon as i start to boot up a message appears : switch to color mode framebuffer 80x30, which is absolutely not what i had given up in lilo.
Ok.. that one worked (stupid stupid stupid.. caus i knew that one)
right now it's booting into 1280x1024, which is acceptable..
but no bootsplash...
when i look in DMESG i see "fbsplash: console 0 using theme 'default'"
which is not my theme...
Hi Kremers78,
This might help for finding the right vga modes for your framebufferdev: http://www.mplayerhq.hu/vesautils/
from the vesautils compile and run the vbetest tool.
That will list some modes, now for the kernel vga= parameter, add 512, to the number in the []'s in front of your resolution of choice.
I made my 1280x800 laptop screen (behind a Intel945GM) work on native res. from boot
In 16 bit depth my mode calculated was 865, remember, this number is specifically for my setup, everybody should run the vbetest tool for themselves to find out the right vgamodes.
After i done that, i started playing with bootsplash, up till now i have the same problem with the initrd missing 'magic'. Seems to be a 2.6.18.x bug. When i boot into vga=791 (not intelfb but vesafb) and i load the initrd my screen gets blacked out. When i dont load the initrd it just boots in 1024x768, so that works.
I hope i saved some ppl a lot of time figuring out their vga modes wih this. If anybody found out a way to get a working bootsplash initrd under 2.6.18.x (solving the 'magic' problem), let us know.
GrtZ, DD.
Hi Kremers78,
This might help for finding the right vga modes for your framebufferdev: http://www.mplayerhq.hu/vesautils/
from the vesautils compile and run the vbetest tool.
That will list some modes, now for the kernel vga= parameter, add 512, to the number in the []'s in front of your resolution of choice.
I made my 1280x800 laptop screen (behind a Intel945GM) work on native res. from boot
In 16 bit depth my mode calculated was 865, remember, this number is specifically for my setup, everybody should run the vbetest tool for themselves to find out the right vgamodes.
After i done that, i started playing with bootsplash, up till now i have the same problem with the initrd missing 'magic'. Seems to be a 2.6.18.x bug. When i boot into vga=791 (not intelfb but vesafb) and i load the initrd my screen gets blacked out. When i dont load the initrd it just boots in 1024x768, so that works.
I hope i saved some ppl a lot of time figuring out their vga modes wih this. If anybody found out a way to get a working bootsplash initrd under 2.6.18.x (solving the 'magic' problem), let us know.
GrtZ, DD.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.