Boot splash is installed. but on reboot the grub menu is still text not graphical. what turns it on. In 8.2 pro it had a nice graphical around the menu. Can I use my own graphic? -- | \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
On Thursday 29 July 2004 06:52 pm, Carl William Spitzer IV wrote:
Boot splash is installed. but on reboot the grub menu is still text not graphical. what turns it on. In 8.2 pro it had a nice graphical around the menu.
Can I use my own graphic? --
| \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
Carl, If your install initially setup for 640x480, you won't have a graphical boot, it will always stay text. I had that happen on an older machine I setup a few months ago with weak builtin video. It displays nicely in KDE, but I never bothered to try to change the boot up. I once adjusted that on an install and forever got the question about what screen I wanted to use after that! So now, I just let it choose, don't bother it and set my final screens as I wish later. Don't know if that was your problem or not, just thought it might be of some interest, if it was. Lee -- --- KMail v1.6.2 --- SuSE Linux Pro v9.1 --- Registered Linux User #225206 I do everything my Rice Krispies tell me to do!
BandiPat a écrit :
On Thursday 29 July 2004 06:52 pm, Carl William Spitzer IV wrote:
Boot splash is installed. but on reboot the grub menu is still text not graphical. what turns it on. In 8.2 pro it had a nice graphical around the menu.
Can I use my own graphic? --
| \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
----------------
Carl,
If your install initially setup for 640x480, you won't have a graphical boot, it will always stay text. I had that happen on an older machine I setup a few months ago with weak builtin video. It displays nicely in KDE, but I never bothered to try to change the boot up. I once adjusted that on an install and forever got the question about what screen I wanted to use after that! So now, I just let it choose, don't bother it and set my final screens as I wish later.
Don't know if that was your problem or not, just thought it might be of some interest, if it was.
Lee
If you want bootsplash to work, add an entry vga=0x??? as grub parameter choose 0x??? according to the capabilities of your system, in order to know you can run : hwinfo --framebuffer then run : mkinitrd and the splash screen will be there at next boot. Michel.
On Fri, 2004-07-30 at 03:51, Catimimi wrote:
BandiPat a écrit :
On Thursday 29 July 2004 06:52 pm, Carl William Spitzer IV wrote:
Boot splash is installed. but on reboot the grub menu is still text not graphical. what turns it on. In 8.2 pro it had a nice graphical around the menu.
Can I use my own graphic? --
| \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
----------------
Carl,
If your install initially setup for 640x480, you won't have a graphical boot, it will always stay text. I had that happen on an older machine I setup a few months ago with weak builtin video. It displays nicely in KDE, but I never bothered to try to change the boot up. I once adjusted that on an install and forever got the question about what screen I wanted to use after that! So now, I just let it choose, don't bother it and set my final screens as I wish later.
Don't know if that was your problem or not, just thought it might be of some interest, if it was.
Lee
If you want bootsplash to work, add an entry vga=0x??? as grub parameter
choose 0x??? according to the capabilities of your system, in order to know you can run : hwinfo --framebuffer
then run : mkinitrd
and the splash screen will be there at next boot.
Michel.
According to hwinfo Mode 0x031a: 1280x1024 (+2560), 16 bits is what I am already using but its still a mode at boot. linux:/home/cwsiv # cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Sat Jun 12 14:54:27 2004 color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,9)/message ###Don't change this comment - YaST2 identifier: Original name: linux### title Linux kernel (hd0,9)/vmlinuz root=/dev/hda12 vga=0x31a splash=silent desktop resume=/dev/hda11 showopts initrd (hd0,9)/initrd <SNIP> What else have I left out or done wrong? -- | \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
On Saturday 31 July 2004 11:00 am, Carl William Spitzer IV wrote:
###Don't change this comment - YaST2 identifier: Original name: linux### title Linux kernel (hd0,9)/vmlinuz root=/dev/hda12 vga=0x31a splash=silent desktop resume=/dev/hda11 showopts initrd (hd0,9)/initrd <SNIP>
What else have I left out or done wrong?
I suspect there is something else causing the problem. My menu.lst is virtually identical to yours and the splash screen works normally on this machine while on a second with similar menu.lst the splash screen wont work. The only difference is the partition which holds the initrrd and root, etc. the one that works has hd0,1 while the other is hd0,4. Wish I knew what the problem is, too. RA
On Sat, 2004-07-31 at 20:18, Richard Atcheson wrote:
On Saturday 31 July 2004 11:00 am, Carl William Spitzer IV wrote:
###Don't change this comment - YaST2 identifier: Original name: linux### title Linux kernel (hd0,9)/vmlinuz root=/dev/hda12 vga=0x31a splash=silent desktop resume=/dev/hda11 showopts initrd (hd0,9)/initrd <SNIP>
What else have I left out or done wrong?
I suspect there is something else causing the problem. My menu.lst is virtually identical to yours and the splash screen works normally on this machine while on a second with similar menu.lst the splash screen wont work. The only difference is the partition which holds the initrrd and root, etc. the one that works has hd0,1 while the other is hd0,4.
Wish I knew what the problem is, too.
Now I see part of the problem the grub boot menu is separate from the boot splash which comes up later when your asked for detail boot information or the graphic. What I have been looking for is the graphical grub menu which existed in 8.2 but does not appear to exist in 9.1. How can I get the grub menu to be graphical. -- | \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
Carl William Spitzer IV a écrit :
On Sat, 2004-07-31 at 20:18, Richard Atcheson wrote:
On Saturday 31 July 2004 11:00 am, Carl William Spitzer IV wrote:
###Don't change this comment - YaST2 identifier: Original name: linux### title Linux kernel (hd0,9)/vmlinuz root=/dev/hda12 vga=0x31a splash=silent desktop resume=/dev/hda11 showopts initrd (hd0,9)/initrd <SNIP>
What else have I left out or done wrong?
I suspect there is something else causing the problem. My menu.lst is virtually identical to yours and the splash screen works normally on this machine while on a second with similar menu.lst the splash screen wont work. The only difference is the partition which holds the initrrd and root, etc. the one that works has hd0,1 while the other is hd0,4.
Wish I knew what the problem is, too.
Now I see part of the problem the grub boot menu is separate from the boot splash which comes up later when your asked for detail boot information or the graphic.
What I have been looking for is the graphical grub menu which existed in 8.2 but does not appear to exist in 9.1. How can I get the grub menu to be graphical.
Hi, I was away for a while but followed the discussion. I can tell you that bootsplash works with SuSE 9.1 and that the problem is on your side. You certainly have done something which broke the splash. Did you compile your kernel ? if so did you change the config options such as initrd bootsplash, framebuffer ...? If not and if you use the native SuSE kernel, it should work. In order to reply to an earlier post, I've to tell that I always use the vanilla kernel (2.6.8-rc2 at the present time) but that I patch it with tha bootsplash patch that I've to maintain up to date by myself. Did you upgrade from SuSe 8.2 or did you make a fresh install ? What is the type of your video card ? Michel.
On Monday 02 August 2004 11:55 am, Catimimi wrote:
Carl William Spitzer IV a écrit :
On Sat, 2004-07-31 at 20:18, Richard Atcheson wrote:
On Saturday 31 July 2004 11:00 am, Carl William Spitzer IV wrote:
You certainly have done something which broke the splash. On the machines that don't do splash I did a fresh install with plain old suse kernel all updated by Yast. Did you compile your kernel ? if so did you change the config options such as initrd bootsplash, framebuffer ...?
If not and if you use the native SuSE kernel, it should work. No changes made to any of the above. In order to reply to an earlier post, I've to tell that I always use the vanilla kernel (2.6.8-rc2 at the present time) but that I patch it with tha bootsplash patch that I've to maintain up to date by myself.
Did you upgrade from SuSe 8.2 or did you make a fresh install ?
What is the type of your video card ? Intel 855 Gm on a Dell 1150.
I have followed all the suggestions so far with no luck. If I go into Yast>System>Runlevel Editor and look at the splash entries, Splash Early and Splash Late are running. Splash is not running so I click start and I get the error message : /etc/init.d/splash start returned 5 (program is not installed). So I look at /etc/init.d/splash and it is identical to the machine that works. Then I look into /sbin and I find splash and splash.bin which are the same as the machine that works. I checked the splash rpms and they are installed. To be sure, I remove and reinstall them but problem remains the same. Just now I did a cat /proc/splash which returned no such file or directory. On the machine that works it returns Splash screen v3.1.6 . . .: on So my question now is how is the /proc/splash supposed to get the correct info? I wonder if the others with this problem have the same result with cat /proc/splash. Richard
i followed the directions in /boot/grub/menu.1st I changed the vga like to vga=0x317 I ran /sbin/mk_initrd the grub boot is still text based. What now does anyone have the graphical boot working in 9.1? Can I see your menu.1st ? CWSIV ________________________________________________________________ The best thing to hit the Internet in years - Juno SpeedBand! Surf the Web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!
i followed the directions in /boot/grub/menu.1st I changed the vga like to vga=0x317 I ran /sbin/mk_initrd
the grub boot is still text based.
What now does anyone have the graphical boot working in 9.1?
Can I see your menu.1st ?
CWSIV
To be honest, I'm a bit stumped by this - are you running the default kernel, and not a custom one with the framebuffer disabled? Heres my /boot/grub/menu.lst: # Modified by YaST2. Last modification on Sat Jul 24 16:58:45 2004 color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,2)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title Linux kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 idebus=100 vga=0x317 splash=verbose desktop resume=/dev/hda2 showopts initrd (hd0,2)/boot/initrd ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows XP root (hd0,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3 initrd (hd0,2)/boot/initrd ###Don't change this comment - YaST2 identifier: Original name: Memory Test### title Memory Test kernel (hd0,2)/boot/memtest.bin David
On Sun, 2004-08-01 at 04:57, David Robertson wrote:
i followed the directions in /boot/grub/menu.1st I changed the vga like to vga=0x317 I ran /sbin/mk_initrd
the grub boot is still text based.
What now does anyone have the graphical boot working in 9.1?
Can I see your menu.1st ?
CWSIV
To be honest, I'm a bit stumped by this - are you running the default kernel, and not a custom one with the framebuffer disabled?
Heres my /boot/grub/menu.lst:
# Modified by YaST2. Last modification on Sat Jul 24 16:58:45 2004
color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,2)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title Linux kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 idebus=100 vga=0x317 splash=verbose desktop resume=/dev/hda2 showopts initrd (hd0,2)/boot/initrd
###Don't change this comment - YaST2 identifier: Original name: windows### title Windows XP root (hd0,0) chainloader +1
###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3 initrd (hd0,2)/boot/initrd
###Don't change this comment - YaST2 identifier: Original name: Memory Test### title Memory Test kernel (hd0,2)/boot/memtest.bin
David
Standard kernal on both the PII and PIII. -- | \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
On Sun, 2004-08-01 at 04:57, David Robertson wrote:
i followed the directions in /boot/grub/menu.1st I changed the vga like to vga=0x317 I ran /sbin/mk_initrd
the grub boot is still text based.
What now does anyone have the graphical boot working in 9.1?
Can I see your menu.1st ?
CWSIV
To be honest, I'm a bit stumped by this - are you running the default kernel, and not a custom one with the framebuffer disabled?
Heres my /boot/grub/menu.lst:
# Modified by YaST2. Last modification on Sat Jul 24 16:58:45 2004
color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,2)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title Linux kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 idebus=100 vga=0x317 splash=verbose desktop resume=/dev/hda2 showopts initrd (hd0,2)/boot/initrd
###Don't change this comment - YaST2 identifier: Original name: windows### title Windows XP root (hd0,0) chainloader +1
###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3 initrd (hd0,2)/boot/initrd
###Don't change this comment - YaST2 identifier: Original name: Memory Test### title Memory Test kernel (hd0,2)/boot/memtest.bin
David
Standard kernal on both the PII and PIII. -- | \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
On Sat, 2004-07-31 at 18:22, Carl William Spitzer IV wrote:
i followed the directions in /boot/grub/menu.1st I changed the vga like to vga=0x317 I ran /sbin/mk_initrd
the grub boot is still text based.
What now does anyone have the graphical boot working in 9.1?
Can I see your menu.1st ?
CWSIV
# Modified by YaST2. Last modification on Sun Jun 27 02:42:32 2004 color white/blue black/light-gray default 0 gfxmenu (hd0,3)/boot/message timeout 8 ###Don't change this comment - YaST2 identifier: Original name: linux### title Linux kernel (hd0,3)/boot/vmlinuz root=/dev/hda4 vga=0x314 splash=silent desktop resume=/dev/hda3 showopts initrd (hd0,3)/boot/initrd ###Don't change this comment - YaST2 identifier: Original name: windows### title windows root (hd0,1) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title floppy root (fd0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe kernel (hd0,3)/boot/vmlinuz root=/dev/hda4 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3 initrd (hd0,3)/boot/initrd ###Don't change this comment - YaST2 identifier: Original name: memtest86### title Memory Test kernel (hd0,3)/boot/memtest.bin
Perhaps I misunderstand the settings. but it appears that the grub meny should be graphical. But its white on blue and text in appearence not as it was in 8.2. Perhaps this is a dropped feature but its more likely I dont know what I am doing. linux:/home/cwsiv # cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Sat Jun 12 14:54:27 2004 color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,9)/message ###Don't change this comment - YaST2 identifier: Original name: linux### title Linux kernel (hd0,9)/vmlinuz root=/dev/hda12 vga=0x31a splash=silent desktop resume=/dev/hda11 showopts initrd (hd0,9)/initrd ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows root (hd0,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy root (fd0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe kernel (hd0,9)/vmlinuz root=/dev/hda12 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3 initrd (hd0,9)/initrd ###Don't change this comment - YaST2 idlinux:/home/cwsiv # cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Sat Jun 12 14:54:27 2004 color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,9)/message ###Don't change this comment - YaST2 identifier: Original name: linux### title Linux kernel (hd0,9)/vmlinuz root=/dev/hda12 vga=0x31a splash=silent desktop resume=/dev/hda11 showopts initrd (hd0,9)/initrd ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows root (hd0,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy root (fd0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe kernel (hd0,9)/vmlinuz root=/dev/hda12 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3 initrd (hd0,9)/initrd ###Don't change this comment - YaST2 identifier: Original name: memtest86### title Memory Test kernel (hd0,9)/memtest.bin entifier: Original name: memtest86### title Memory Test kernel (hd0,9)/memtest.bin -- | \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
Darn it... I still forget to reply to list sometimes. Sorry for the personal reply Carl. On Thursday 29 July 2004 05:52 pm, Carl William Spitzer IV wrote:
Boot splash is installed. but on reboot the grub menu is still text not graphical. what turns it on. In 8.2 pro it had a nice graphical around the menu.
I don't know much about graphical booting but if I understand your question correctly, you are asking about a graphic at the grub menu stage, not during the boot process. If so, that is done with the grub entry gfxmenu. On my machine that is gfxmenu (hd0,6)/boot/message Just make sure it is pointing to a file that was built for this purpose.
Can I use my own graphic?
While man (as in man grub) is a good friend in trying to solve problems, info (as in info grub) sometimes helps more. From info grub: gfxmenu ------- - Command: gfxmenu file Use the graphical menu interface. The graphics data are taken from FILE and must be created using 'mkbootmsg' from the gfxboot package. While I haven't tried this, it looks like you can build your grub screen. Hope that helps Doug
I don't know much about graphical booting but if I understand your question correctly, you are asking about a graphic at the grub menu stage, not during the boot process.
If so, that is done with the grub entry gfxmenu. On my machine that is gfxmenu (hd0,6)/boot/message
Just make sure it is pointing to a file that was built for this purpose.
Well, that'll teach me to read the original post properly! I thought we were talking about the graphical boot - which to me is a bootsplash - rather than the menu graphic. Have I got the terminology wrong? Feel a bit silly now................... David
On Sunday 01 August 2004 10:10 am, David Robertson wrote:
I thought we were talking about the graphical boot - which to me is a bootsplash - rather than the menu graphic. Have I got the terminology wrong?
Actually, I don't know for sure. I don't care whether I have a graphical boot or not. My 9.0 had a graphical boot. If I was sitting at the console during boot, I usually hit <F2>(or whatever it was) so I could see the detail. I just like to see if there are any slow spots or errors I may have missed before. My 9.1 install doesn't have a graphical boot, which is fine. That said, I associate boot splash with the boot process, not with grub which is a boot loader. My confusion in this thread comes from the OP:
Boot splash is installed. but on reboot the grub menu is still text not graphical. what turns it on. In 8.2 pro it had a nice graphical around the menu.
The first line leads me to think 'boot process'... The following lines seem to indicate the boot loader screen. Since I was confused, I didn't respond right away. All the responses went toward the boot process and not the grub menu, and since they weren't doing what the OP wanted, I thought I would take a different track. I still don't know if it was the right track! Doug
On Sunday 01 August 2004 11:35 am, Doug B wrote:
Actually, I don't know for sure. I don't care whether I have a graphical boot or not. My 9.0 had a graphical boot. If I was sitting at the console during boot, I usually hit <F2>(or whatever it was) so I could see the detail. I just like to see if there are any slow spots or errors I may have missed before. My 9.1 install doesn't have a graphical boot, which is fine.
I too am amazed at how many people insist on having a graphical boot screen... What do these people do, boot 5 times a day? And sit there and marvel at the wunnerful graphics? Since linux hardly ever needs booting, seems like a rather strange desire. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 08/01/04 11:57 + +----------------------------------------------------------------------------+ "It has recently been discovered that research causes cancer in rats."
On Sunday 01 August 2004 11:35 am, Doug B wrote:
Actually, I don't know for sure. I don't care whether I have a graphical boot or not. My 9.0 had a graphical boot. If I was sitting at the console during boot, I usually hit <F2>(or whatever it was) so I could see the detail. I just like to see if there are any slow spots or errors I may have missed before. My 9.1 install doesn't have a graphical boot, which is fine.
I too am amazed at how many people insist on having a graphical boot screen...
What do these people do, boot 5 times a day? And sit there and marvel at the wunnerful graphics? Since linux hardly ever needs booting, seems like a rather strange desire. Bruce, I put together systems for people who could care less what happens during boot. Most of those people are windows users who really cant tell
On Sunday 01 August 2004 10:59 am, Bruce Marshall wrote: the difference between windows and linux except by what they see on the screen. Those same people, quite often, shutdown the computer when they have finished whatever it was they wanted to do. So Yes, they may reboot several times each day. They dont marvel at the graphics, they simply ignore it. Another reason I like to use the silent splashscreen feature for them is it results in less of my time trying to explain to them what all that boot stuff means. For myself, I find the boot sequence, as it scrolls across the screen, distracting. Usually I dont really need to watch all that. When I need to see what happens I can press F2. So I would really like to find out how to make the splashscreen work on those machines where it doesn't. Surely there is someone who knows how it really works and will tell us their secret. ra
On Sunday 01 August 2004 02:00 pm, Richard Atcheson wrote:
For myself, I find the boot sequence, as it scrolls across the screen, distracting. Usually I dont really need to watch all that. When I need to see what happens I can press F2. So I would really like to find out how to make the splashscreen work on those machines where it doesn't. Surely there is someone who knows how it really works and will tell us their secret.
I believe the true silent spashscreen involves a kernel mod done by SuSE. This is one thing I lose when I (always) switch to a vanilla kernel. But for me it is no loss. Should work for you unless the kernel mod has been lost somewhere... or the graphics specification to the kernel vga=xxxxxx is wrong. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 08/01/04 14:25 + +----------------------------------------------------------------------------+ "This cookie is void where prohibited, licensed, or taxed."
On Sunday 01 August 2004 20:00, Richard Atcheson wrote:
On Sunday 01 August 2004 10:59 am, Bruce Marshall wrote:
On Sunday 01 August 2004 11:35 am, Doug B wrote:
Actually, I don't know for sure. I don't care whether I have a graphical boot or not. My 9.0 had a graphical boot. If I was sitting at the console during boot, I usually hit <F2>(or whatever it was) so I could see the detail. I just like to see if there are any slow spots or errors I may have missed before. My 9.1 install doesn't have a graphical boot, which is fine.
I too am amazed at how many people insist on having a graphical boot screen...
What do these people do, boot 5 times a day? And sit there and marvel at the wunnerful graphics? Since linux hardly ever needs booting, seems like a rather strange desire.
Bruce, I put together systems for people who could care less what happens during boot. Most of those people are windows users who really cant tell the difference between windows and linux except by what they see on the screen. Those same people, quite often, shutdown the computer when they have finished whatever it was they wanted to do. So Yes, they may reboot several times each day. They dont marvel at the graphics, they simply ignore it. Another reason I like to use the silent splashscreen feature for them is it results in less of my time trying to explain to them what all that boot stuff means.
For myself, I find the boot sequence, as it scrolls across the screen, distracting. Usually I dont really need to watch all that. When I need to see what happens I can press F2. So I would really like to find out how to make the splashscreen work on those machines where it doesn't. Surely there is someone who knows how it really works and will tell us their secret.
ra
1) These packages are needed: bootsplash-theme-SuSE or bootsplash-theme-SuSE-Home bootsplash I think these are not part of the 'Default' install. 2) There must be a vga=<size> as a kernel argument, where <size> is e.g. 0x31A (see /usr/src/linux/Documentation/fb/vesafb.txt, second table) 3) The initrd must have the splash picture appended. mkinitrd takes care of that. To append more than one splash picture for several resolutions, use the -s option: mkinitrd -s '1280x1024 1400x1050 1600x1200' Mind the quotes and spaces. mkinitrd is also executed automatically after installing/upgrading the kernel. If you need more bootsplash pictures, then execute mkinitrd manually, specifying the desired resolutions. Hope this helps, Cheers, Leen
On Sun, 2004-08-01 at 11:46, Leendert Meyer wrote:
On Sunday 01 August 2004 20:00, Richard Atcheson wrote:
On Sunday 01 August 2004 10:59 am, Bruce Marshall wrote:
On Sunday 01 August 2004 11:35 am, Doug B wrote:
Actually, I don't know for sure. I don't care whether I have a graphical boot or not. My 9.0 had a graphical boot. If I was sitting at the console during boot, I usually hit <F2>(or whatever it was) so I could see the detail. I just like to see if there are any slow spots or errors I may have missed before. My 9.1 install doesn't have a graphical boot, which is fine.
I too am amazed at how many people insist on having a graphical boot screen...
What do these people do, boot 5 times a day? And sit there and marvel at the wunnerful graphics? Since linux hardly ever needs booting, seems like a rather strange desire.
Bruce, I put together systems for people who could care less what happens during boot. Most of those people are windows users who really cant tell the difference between windows and linux except by what they see on the screen. Those same people, quite often, shutdown the computer when they have finished whatever it was they wanted to do. So Yes, they may reboot several times each day. They dont marvel at the graphics, they simply ignore it. Another reason I like to use the silent splashscreen feature for them is it results in less of my time trying to explain to them what all that boot stuff means.
For myself, I find the boot sequence, as it scrolls across the screen, distracting. Usually I dont really need to watch all that. When I need to see what happens I can press F2. So I would really like to find out how to make the splashscreen work on those machines where it doesn't. Surely there is someone who knows how it really works and will tell us their secret.
ra
1) These packages are needed:
bootsplash-theme-SuSE or bootsplash-theme-SuSE-Home bootsplash
I think these are not part of the 'Default' install.
2) There must be a vga=<size> as a kernel argument, where <size> is e.g. 0x31A (see /usr/src/linux/Documentation/fb/vesafb.txt, second table)
3) The initrd must have the splash picture appended. mkinitrd takes care of that. To append more than one splash picture for several resolutions, use the -s option:
mkinitrd -s '1280x1024 1400x1050 1600x1200'
Mind the quotes and spaces.
mkinitrd is also executed automatically after installing/upgrading the kernel. If you need more bootsplash pictures, then execute mkinitrd manually, specifying the desired resolutions.
Well I seem to have splash installed cat /proc/splash Splash screen v3.1.6-2004/03/31 (0x07, 1280x1024): on cwsiv@linux:~> ls /etc/init.d/sp* -lh -rwxr-xr-x 1 root root 3.0K 2004-04-05 18:50 /etc/init.d/splash -rwxr-xr-x 1 root root 617 2004-04-05 18:50 /etc/init.d/splash_early -rwxr-xr-x 1 root root 707 2004-04-05 18:50 /etc/init.d/splash_late cwsiv@linux:~> cat /proc/splash Splash screen v3.1.6-2004/03/31 (0x07, 1280x1024): on cwsiv@linux:~> ls /sbin/sp* -lh -rwxr-xr-x 1 root root 3.4K 2004-04-05 18:50 /sbin/splash -rwxr-xr-x 1 root root 11K 2004-04-05 18:50 /sbin/splash.bin -rwxr-xr-x 1 root root 5.8K 2004-04-05 18:50 /sbin/splashpbm cwsiv@linux:~> I dont have the sources so no /usr/src/linux/documentation/... what I get is a blue screen with a text box in the middle and of course its too early in boot to capture screen and I dont have a digital camera. I remember 8.2 having a nice graphic etc so I dont know If I installed the wrong one. If there are third party sources for nicer screens or the ability to use my own graphic that would work for me. -- _______ _______ _______ __ / ____\ \ / / ____|_ _\ \ / / | | \ \ /\ / / (___ | | \ \ / / | | \ \/ \/ / \___ \ | | \ \/ / | |____ \ /\ / ____) |_| |_ \ / \_____| \/ \/ |_____/|_____| \/ | \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
On Monday 09 August 2004 06:55, Carl William Spitzer IV wrote:
On Sun, 2004-08-01 at 11:46, Leendert Meyer wrote:
1) These packages are needed:
bootsplash-theme-SuSE or bootsplash-theme-SuSE-Home bootsplash
To see if these packages are installed, do: rpm -qa|grep "^bootsplash"
I think these are not part of the 'Default' install.
2) There must be a vga=<size> as a kernel argument, where <size> is e.g. 0x31A (see /usr/src/linux/Documentation/fb/vesafb.txt, second table)
3) The initrd must have the splash picture appended. mkinitrd takes care of that. To append more than one splash picture for several resolutions, use the -s option:
mkinitrd -s '1280x1024 1400x1050 1600x1200'
Mind the quotes and spaces.
mkinitrd is also executed automatically after installing/upgrading the kernel. If you need more bootsplash pictures, then execute mkinitrd manually, specifying the desired resolutions.
I forgot: 4) A SuSE kernel is needed, or at least a bootsplash-enabled kernel (See http://www.bootsplash.org/ for patches).
Well I seem to have splash installed
rpm -qa|grep "^bootsplash"
cat /proc/splash ... I dont have the sources so no /usr/src/linux/documentation/...
So you refuse to RTFM. Fine. Please tell me when you have changed your mind and did RTFM. And please get rid of that *insane* sig!
On Sun, 2004-08-08 at 23:43, Leendert Meyer wrote:
On Monday 09 August 2004 06:55, Carl William Spitzer IV wrote:
On Sun, 2004-08-01 at 11:46, Leendert Meyer wrote:
1) These packages are needed:
bootsplash-theme-SuSE or bootsplash-theme-SuSE-Home bootsplash
To see if these packages are installed, do: rpm -qa|grep "^bootsplash"
rpm -qa|grep "^bootsplash" bootsplash-3.1-37 bootsplash-theme-SuSE-3.1-16 cwsiv@linux:~>
...
I dont have the sources so no /usr/src/linux/documentation/...
So you refuse to RTFM. Fine. Please tell me when you have changed your mind and did RTFM.
I got the bookless edition this time so no manual to read. first time in a while the books would help more than the list. _______ _______ _______ __ / ____\ \ / / ____|_ _\ \ / / | | \ \ /\ / / (___ | | \ \ / / | | \ \/ \/ / \___ \ | | \ \/ / | |____ \ /\ / ____) |_| |_ \ / \_____| \/ \/ |_____/|_____| \/
On Tuesday 10 August 2004 08:20, Carl William Spitzer IV wrote:
On Sun, 2004-08-08 at 23:43, Leendert Meyer wrote:
On Monday 09 August 2004 06:55, Carl William Spitzer IV wrote:
On Sun, 2004-08-01 at 11:46, Leendert Meyer wrote: I dont have the sources so no /usr/src/linux/documentation/...
So you refuse to RTFM. Fine. Please tell me when you have changed your mind and did RTFM.
I got the bookless edition this time so no manual to read. first time in a while the books would help more than the list.
They are on ftp.suse.com available. Cheers, Leen
Another user reported to me that the splash-silent has no affect on the
newer kernels. This is true for both 9.0 and 9.1. Since I always use
verbose, I didn't notice the change, but the user reports that the
problem appeared after an online update to the 2.4.21-238 kernel.
In my GRUB menu, I have splash=silent, but it still boots as verbose.
BTW: In looking at the kernel sources, the silent option is tested.
/usr/src/linux/drivers/video/fbcon-splash.c
int __init splash_init(char *options)
{
if(!strncmp("silent",options,6)) {
printk(KERN_INFO "bootsplash: silent mode.\n");
splash_usesilent = 1;
/* skip "silent," */
if (strlen(options)==6)
return 0;
options+=7;
}
if(!strncmp("verbose",options,7)) {
printk(KERN_INFO "bootsplash: verbose mode.\n");
splash_usesilent = 0;
return 0;
}
--
Jerry Feldman
On Sun, 2004-08-01 at 08:59, Bruce Marshall wrote:
On Sunday 01 August 2004 11:35 am, Doug B wrote:
Actually, I don't know for sure. I don't care whether I have a graphical boot or not. My 9.0 had a graphical boot. If I was sitting at the console during boot, I usually hit <F2>(or whatever it was) so I could see the detail. I just like to see if there are any slow spots or errors I may have missed before. My 9.1 install doesn't have a graphical boot, which is fine.
I too am amazed at how many people insist on having a graphical boot screen...
What do these people do, boot 5 times a day? And sit there and marvel at the wunnerful graphics? Since linux hardly ever needs booting, seems like a rather strange desire.
At least once as this is a multiboot system. Otherwise I agree with you about keeping it up. In any case this is just one more thing I needed to understand in the thousands that is Suse. Perhaps Ill get to Spam Assassin next -- | \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
On Sun, 2004-08-01 at 07:11, Doug B wrote:
Darn it... I still forget to reply to list sometimes. Sorry for the personal reply Carl. No Problem
On Thursday 29 July 2004 05:52 pm, Carl William Spitzer IV wrote:
Boot splash is installed. but on reboot the grub menu is still text not graphical. what turns it on. In 8.2 pro it had a nice graphical around the menu.
I don't know much about graphical booting but if I understand your question correctly, you are asking about a graphic at the grub menu stage, not during the boot process.
If so, that is done with the grub entry gfxmenu. On my machine that is gfxmenu (hd0,6)/boot/message
gfxmenu (hd0,9)/message Perhaps I need only hack to make mine reflect; yours. Looks like there is a file called message in /boot
Just make sure it is pointing to a file that was built for this purpose.
Can I use my own graphic?
While man (as in man grub) is a good friend in trying to solve problems, info (as in info grub) sometimes helps more. From info grub:
gfxmenu -------
- Command: gfxmenu file Use the graphical menu interface. The graphics data are taken from FILE and must be created using 'mkbootmsg' from the gfxboot package.
While I haven't tried this, it looks like you can build your grub screen.
Hope that helps Doug -- | \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/
On Monday 02 August 2004 06:23 pm, Carl William Spitzer IV wrote:
On Sun, 2004-08-01 at 07:11, Doug B wrote:
If so, that is done with the grub entry gfxmenu. On my machine that is gfxmenu (hd0,6)/boot/message
gfxmenu (hd0,9)/message
Perhaps I need only hack to make mine reflect; yours. Looks like there is a file called message in /boot
If there is a file in boot called message, that is good. Now you need to make sure grub can find it. On my machine, the /boot directory I want to use is on /dev/hda7. You need to know what device and partion your /boot directory is on. Remember that grub names the hard drives a little different. The first drive is 0 and the first partition is 0. On my machine I want /dev/hda7 (first drive, 7 th partition). In grub that would be (hd0,6). Doug
participants (12)
-
BandiPat -
Bruce Marshall -
Carl William Spitzer IV -
Carl William Spitzer IV -
Catimimi -
Catimimi
-
David Robertson -
Doug B -
Jerry Feldman -
Leendert Meyer -
Mike McMullin -
Richard Atcheson