Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
why did you bother patching bootsplash into the kernel if you are just going to set splash=verbose?
splash=silent is the option you want if you want it to show a bootsplash screen.
so infact it would seem that you don't want the bootsplash showing. you want to watch the boot process, don't you?
In this case, why did you patch the kernel with bootsplash? the idea would have been to remove bootsplash from the kernel.
Sorry, but verbose has a bootsplash image on which the boot-messages are displayed. Yes, I would like to have this (not just a black screen, which would be splash=0). I know that there are more important things in life and linux, but I simply would like to understand this behaviour.
that isn't what i meant.
why did you install the bootsplash stuff.
no bootsplash is when you watch the messages.
removing the splash=something line might solve this problem.
recompiling the kernel without bootsplash support would almost definitly do it.
1. no splash, a simple text console is shown.
This does not require the bootsplash-patch, right!
2. splash= silent
Instead of showing messages, a more or less nice graphical picture is shown. Sometimes with a progress-bar. I don't want this, but there is a 3rd alternative:
In this variant, the boot messages are shown just like in #1, but with an underlying picture. In my case this is a cute tux that I downloaded from www.bootsplash.org
Have a look on that site and you'll see what I mean. This is what I want and it is called 'verbose'. And it requires the patch.
To rephrase my question (makes it more general):
Why does the kernel receive a command-line that I did not sent to it? Where did it come from and what happend to my parameters?
this is going to sound like a dumb question, but which bootloader are you using? you did edit the right config file and install the right bootloader, didn't you?
i made that mistake a while ago.
if that was all done right, try installing this: http://kat.sourceforge.net/
it lets you search through text files, and you can run a search for the string "splash=silent" to find and change the offending file.
- The patch was applied without any errors, still it could be something wrong with it...
- When I exit the graphical grub menu (SUSE uses a file called gfxmenu to display a graphical screen) and use the 'dos-style' menu-mode to boot instead, the behaviour is correct (the verbose splash is loaded). If I use the graphical menu however, the wrong kernel command line is submitted. Strange!
I think SUSE demands that you use splash=silent. Its probably hidden in a random config file, maybe event in initrd or vmlinuz. I would try installing kat and searching for it, or even recompiling the kernel and checking that the correct toggles were chosen.
what does the top section of your menu.lst file say, the bit above each OS section.
i just looked in /boot/message (used command 'cpio -i </boot/message' to extract it) and didn't find anything useful.
just some config files and a help file (which only repeated what we have already tried).
you might want to look inside yours to determine if there is anything relevent.
I'm running SUSE 9.2 (without any major modifications), and decided to try setting splash=verbose to determine whether I have the same problem.
The steps I took were:
1. Open /boot/grub/menu.lst
2. Change splash=silent to splash=verbose in the SUSE section.
3. Save menu.lst
4. Re-install grub (command: grub-install /dev/hda)
When it rebooted, it showed the verbose screen. The fact that you installed the bootsplash patch might be working against you here. Try re-installing the vanilla kernel (the one that came with suse), or even try this one (its the one i use) kernel-default and the non-gpl bit (both should be installed) kernel-default-nongpl
by the way, im using apt-for-suse to keep stuff up to date.
For some strange reason, I have used a tab instead of a space between the vga and the splash parameters. This seemed to cause grub to ignore all following parameters and to use a default, which seemed to be splash=silent. I did not see this in my favourite editor pico, only when I used kwrite.
Thanks again for the help and sorry for the inconvenience!