View previous topic :: View next topic |
Author |
Message |
jlmcp Tux's lil' helper
Joined: 27 Apr 2005 Posts: 134
|
Posted: Sat Apr 30, 2005 12:42 am Post subject: 2005.0 Boot up screen ... [solved] |
|
|
This is interesting:
http://www.gentoo.org/news/en/gwn/20050418-newsletter.xml#doc_chap5
I would be interested to know if anyone got this to work. I tried, and all I get is a blank screen with nothing on it.
Jake
Last edited by jlmcp on Mon May 02, 2005 8:00 am; edited 1 time in total |
|
Back to top |
|
|
/dev/random l33t
Joined: 26 Nov 2004 Posts: 704 Location: Austin, Texas, USA
|
Posted: Sat Apr 30, 2005 3:15 am Post subject: |
|
|
Works like a charm. Post your grub.conf and make sure framebuffer and framebuffer splash support are compiled into your kernel. |
|
Back to top |
|
|
jlmcp Tux's lil' helper
Joined: 27 Apr 2005 Posts: 134
|
Posted: Sat Apr 30, 2005 5:05 am Post subject: |
|
|
Thanks for the reply.
Here is what I did (grub.conf posted at the end):
- emerge splash-themes-livecd ... worked.
- mount /dev/hda1/boot ... worked.
- splash_geninitramfs -v -g /boot/splash-livecd-2005.0-1024x768 -r 1024x768 livecd-2005.0 ... worked.
- Used the kernel generator (make menuconfig) to enable te following:
---| Device Drivers --> Block devices --> RAM disk support --> Initial RAM disk (initrd) support
---| Graphics Support --> Support for frame buffer devices
---| Graphics Support --> VESA VGA graphics support --> VESA driver type (vesafb-tng) --> (1024x768@60) VESA default mode
** Note here: I have a ATI Redeon 7500 in my laptop, but I chose the VESA driver anyway. Any conflict there? Also, this is a dual boot box, and in Windows, the default mode is 1024x768 @ 60 hrz.**
- Added the following lines to my menu.lst:
---| kernel /boot/kernel-2.6.11-gentoor3 root=/dev/hda4 video=vesafb:1024x768-32@60 splash=silent,theme:livecd-2005.0 quiet CONSOLE=/dev/tty1
---| initrd /boot/splash-livecd-2005.0-1024x768
- cd /etc/splash ... worked.
- rm default ... worked.
- ln -s livecd-2005.0 default ... worked.
- rc-update add splash default ... worked.
Then, when I reboot, I get a blank screen with a cursor blinking in the bottom left corner, and eventually I get popped back out to the normal console screen.
Hints?
grub.conf here:
Quote: | #
# Last edited: 4/29/05
#
timeout 10
default 0
splashimage=(hd0,1)/grub/splash.xpm.gz
title=Gentoo Linux 2005.0 (Linux 2.6.11-r3)
root (hd0,1)
kernel /kernel-2.6.11-gentoo-r3 root=/dev/hda4 video=vesafb:1024x768-32@60 splash=silent,theme:livecd-2005.0 quiet CONSOLE=/dev/tty1
initrd /boot/splash-livecd-2005.0-1024x768
title=Windows XP Professional, SP1
rootnoverify (hd0,0)
makeactive
chainloader +1 |
|
|
Back to top |
|
|
jlmcp Tux's lil' helper
Joined: 27 Apr 2005 Posts: 134
|
Posted: Sat Apr 30, 2005 5:52 am Post subject: |
|
|
Quote: | ... make sure framebuffer and framebuffer splash support are compiled into your kernel. |
Reading this again, wasn't sure what you meant by "framebuffer" AND "framebuffer splash support". I didn't see another option for "framebuffer splash support" in menuconfig.
Anyway ... when you have time.
Jake |
|
Back to top |
|
|
xaos5 Apprentice
Joined: 19 Apr 2005 Posts: 255 Location: Michigan
|
Posted: Sat Apr 30, 2005 6:37 am Post subject: |
|
|
Quote: | I didn't see another option for "framebuffer splash support" in menuconfig. |
this probably means your kernel isn't patched with the bootsplash which I think splashutils should check for. If you enabled all the options right it should pop up near the bottom with all the frambuffer support crap.
I couldn't get this to work either, so I looked around and found some stuff. This is what I did:
Code: | # rm -v /usr/src/linux/usr/initramfs_data.cpio.gz
# splash_geninitramfs -v -g /usr/src/linux/usr/initramfs_data.cpio.gz -r 1024x768 livecd-2005.0
# cd /usr/src/linux
# touch usr/initramfs_data.cpio.gz
# make (recompile the kernel) |
then my grub.conf looks like this:
Code: | title Gentoo 2.6.11
root (hd0,0)
kernel /2.6.11-gentoo-r6 root=/dev/hda3 video=vesafb:1024x768-32@85 splash=silent,theme:livecd-2005.0 quiet
CONSOLE=/dev/ttyl |
edit: I took this all off this site http://gentoo-wiki.com/HOWTO_fbsplash |
|
Back to top |
|
|
jlmcp Tux's lil' helper
Joined: 27 Apr 2005 Posts: 134
|
Posted: Sat Apr 30, 2005 9:04 am Post subject: |
|
|
Sorry to be a pain in the a**, but when you say:
Quote: | If you enabled all the options right it should pop up near the bottom with all the frambuffer support crap. |
What menu are you referring to? I am assuming we are talking about menuconfig,
---|Device Drivers --> Graphics Support
I tried the recommended steps below in the first code block, but to no avail. ;-/ And I still don't see the "framebuffer splash support" option. I just attempted the following, which may be interesting:
Code: | # emerge -p bootsplash
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[blocks B ] media-gfx/splashutils (is blocking media-gfx/bootsplash-0.6.1-r7)
[ebuild N ] media-libs/lcms-1.13
[ebuild N ] media-gfx/bootsplash-0.6.1-r7 |
Maybe splashutils is not quite as smart as we thought.
?
Jake |
|
Back to top |
|
|
/dev/random l33t
Joined: 26 Nov 2004 Posts: 704 Location: Austin, Texas, USA
|
Posted: Sat Apr 30, 2005 1:16 pm Post subject: |
|
|
splashutils and bootsplash cannot coexist. splashutils is superior so emerge -C bootsplash should take care of that. As for your kernel options are you using gentoo-sources or vanilla-sources? If you're using vanilla-sources you have to get the patch for splashutils. At the very bottom of Device Driver ----> Graphics Support I have a support for framebuffer splash option with gentoo-sources-2.6.10-r7
Also, using the vesa(-tng) driver is a wise choice. I have an AMD64 and even in 32-bit Gentoo I've noticed that only the vesa driver (not vesa-tng) will work. |
|
Back to top |
|
|
xaos5 Apprentice
Joined: 19 Apr 2005 Posts: 255 Location: Michigan
|
Posted: Sat Apr 30, 2005 7:05 pm Post subject: |
|
|
/dev/random is right, you need the patch in the kernel and I think the genkernel already has it built into it. |
|
Back to top |
|
|
jlmcp Tux's lil' helper
Joined: 27 Apr 2005 Posts: 134
|
Posted: Sat Apr 30, 2005 10:19 pm Post subject: |
|
|
Alright, I feel like we are getting closer...
So, first to answer the Q's:
- Sources are Gentoo ... as far as I know. I did *not* use genkernel during my install, but all the src is Gentoo.
- Bootsplash: not curently installed (note the 'N' in the remarks from emerge in last post) so I think we are good there.
- Kernel is 2.6.11-r3.
- Vesa vs. -tng ... easy enough to change.
Ok, now for the tricky stuff...
When I look to the bottom of Device Drivers --> Graphics Support the only two options I see that look related to framebuffering are the following:
Code: |
< > Virtual Frame Buffer support (ONLY FOR TESTING!)
Console display driver support --> Framebuffer Console support |
Are either of those two what I am looking for? I was expecting to see something with the word "splash" in it based on our conversation. I guess I thought I had applied the patch for splashutils already, but maybe I am mistaken. Is there a way to check? Or can you point me to install instructions?
Thanks for that patience.
Jake |
|
Back to top |
|
|
jlmcp Tux's lil' helper
Joined: 27 Apr 2005 Posts: 134
|
Posted: Sun May 01, 2005 3:55 pm Post subject: |
|
|
Update...
Switcing from vesa-tng back to vesa didn't seem to make a big change. Hm. Probably missing the kernel patch.
Let me know if you think of something.
Jake |
|
Back to top |
|
|
alechiko Guru
Joined: 01 Feb 2004 Posts: 465 Location: Inside piano, do not disturb.
|
Posted: Sun May 01, 2005 7:32 pm Post subject: |
|
|
Ive followed the guide to the letter and when i boot up i get a black screen with a white bar flashing on the left side.
Fortunately because nothing else was affected i simply waited until the HDD had stopped spinning and assumed Gentoo had loaded, then logged in as root (even though i couldnt see what i was typing) and started GDM =)
Anyway, here I am now and here is my kernel config: http://homepage.ntlworld.com/l.levy1/links/config-2.6.11-gentoo-r6-fbsplash
and my Grub.conf: http://homepage.ntlworld.com/l.levy1/links/grub.conf
Anyone know whats going on? Im really eager to have this setup right =)
akiru _________________ None |
|
Back to top |
|
|
jlmcp Tux's lil' helper
Joined: 27 Apr 2005 Posts: 134
|
Posted: Mon May 02, 2005 1:04 am Post subject: |
|
|
akiru,
Ditto. Your experince mirrors mine. As best as I can tell, there are probably some steps we need to take that the author of the article in the Weekly Update took for granted.
Just trying to track down that mising link.
Jake |
|
Back to top |
|
|
jlmcp Tux's lil' helper
Joined: 27 Apr 2005 Posts: 134
|
Posted: Mon May 02, 2005 7:59 am Post subject: |
|
|
* SOLVED * SOLVED * SOLVED *
As suspected, there was a rather large assumption made by the author of the article in the Gentoo Weekly that the reader had already setup their system for bootspash/frame-buffer images and console themes. The lights went on when I stumbled across this bit-o-instruction when linked to the the Gentoo frambuffer splash Wiki at http://gentoo-wiki.com/HOWTO_fbsplash.
When properly configuring your kernel, follow these instructions (for users of menuconfig) instead:
Code: | Device Drivers > Graphics support:
[*] Support for frame buffer devices
<*> VESA VGA graphics support
VESA driver type (vesafb-tng) --->
Device Drivers > Graphics support > Console display driver support:
[*] Video mode selection support
<*> Framebuffer Console support
Device Drivers > Graphics support:
[*] Support for the framebuffer splash (NEW)
Device Drivers > Block devices:
<*> RAM disk support
(4096) Default RAM disk size (kbytes) (NEW)
[*] Initial RAM disk (initrd) support |
Note that it is only AFTER you enable the "Console Display Driver Support" that the option to enable "Support for the framebuffer splash (NEW)" will appear in the parent menu. :-/ After compiling the kernel, THEN emerge splashutils et al. and continue with the directions specified in the article.
Also, if you used menuconfig (manual kernel config) don't add the line specified in the article:
Add the following line to your kernel-config:
initrd /boot/splash-livecd-2005.0-1024x768
Grub will get confused.
Once I did this, all worked!
Jake |
|
Back to top |
|
|
alechiko Guru
Joined: 01 Feb 2004 Posts: 465 Location: Inside piano, do not disturb.
|
Posted: Mon May 02, 2005 10:53 am Post subject: |
|
|
jlmcp wrote: | * SOLVED * SOLVED * SOLVED *
As suspected, there was a rather large assumption made by the author of the article in the Gentoo Weekly that the reader had already setup their system for bootspash/frame-buffer images and console themes. The lights went on when I stumbled across this bit-o-instruction when linked to the the Gentoo frambuffer splash Wiki at http://gentoo-wiki.com/HOWTO_fbsplash.
When properly configuring your kernel, follow these instructions (for users of menuconfig) instead:
Code: | Device Drivers > Graphics support:
[*] Support for frame buffer devices
<*> VESA VGA graphics support
VESA driver type (vesafb-tng) --->
Device Drivers > Graphics support > Console display driver support:
[*] Video mode selection support
<*> Framebuffer Console support
Device Drivers > Graphics support:
[*] Support for the framebuffer splash (NEW)
Device Drivers > Block devices:
<*> RAM disk support
(4096) Default RAM disk size (kbytes) (NEW)
[*] Initial RAM disk (initrd) support |
Note that it is only AFTER you enable the "Console Display Driver Support" that the option to enable "Support for the framebuffer splash (NEW)" will appear in the parent menu. :-/ After compiling the kernel, THEN emerge splashutils et al. and continue with the directions specified in the article.
Also, if you used menuconfig (manual kernel config) don't add the line specified in the article:
Add the following line to your kernel-config:
initrd /boot/splash-livecd-2005.0-1024x768
Grub will get confused.
Once I did this, all worked!
Jake |
Did everything just like you said buddy.. unfortunately still no dice
I did find something interesting though. I also tried compiling my kernel again with rivafb as the driver instead of vesa-tng. Same options in grub etc.. It booted in high res, but wouldnt start the nvidia module or the eth0 module or the splash at the end.
I fiddled around a bit and managed to start the eth0 module and then manually ran /etc/init.d/splash start (which worked), but I cant seem to fix the nvidia problem. I guess that rivafb and nvidia-kernel are not compatible with eachother. This is a shame because except for the fact that eth0 didnt start automatically and the splash didnt splash (even though its in default runlevel) everything worked just fine.
Sigh.. the things I do for gentoo
akiru _________________ None |
|
Back to top |
|
|
atdsm Tux's lil' helper
Joined: 15 Jun 2003 Posts: 118 Location: Pennsylvania
|
Posted: Thu May 05, 2005 8:06 pm Post subject: |
|
|
akiru wrote: | I guess that rivafb and nvidia-kernel are not compatible with eachother. |
This is correct. If you are using nvidia's drivers then you should disable rivafb. I was trying to figure out the same thing... searching for nvidia and rivafb in the forums pulls up a lot about this, actually. Somewhere I saw the official message portage generates from someone who had emerged nvidia w/ rivafb enabled... but I can't find it now. _________________ There are 10 kinds of people: those who know binary and those who don't. |
|
Back to top |
|
|
|