View previous topic :: View next topic |
Author |
Message |
Martux Veteran
Joined: 04 Feb 2005 Posts: 1917
|
Posted: Mon Oct 22, 2012 4:11 pm Post subject: Grub2 and Framebuffer Decorations |
|
|
Hi all!
I just switched from grub-legacy to grub2.
So far everything went well, except one thing:
In grub the first thing after pressing return was that the framebuffer wallpaper was loaded and displayed throughout the whole booting process until the dm took over. Very good.
With grub2, the wallpaper loads pretty late during the boot process. A bit earlier when I change the runlevel of fbcondecor from "default" to "boot", but still too late and not like grub-legacy.
Anyone has an idea how to fix this? _________________ "Coincidence is God's way of remaining anonymous."
Albert Einstein
"The road to success is always under construction" |
|
Back to top |
|
|
Fitzcarraldo Advocate
Joined: 30 Aug 2008 Posts: 2034 Location: United Kingdom
|
Posted: Tue Oct 23, 2012 3:10 pm Post subject: |
|
|
I could be wide of the mark here, but do you use initramfs? I have to rebuild that separately to get back the console decoration sometimes:
Code: | genkernel --splash=Emergance --splash-res=1024x768 --no-clean --disklabel initramfs |
(Obviously replace "Energance" with the splash theme of your choice in /etc/splash/) _________________ Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC udev elogind & KDE on both.
Fitzcarraldo's blog |
|
Back to top |
|
|
Martux Veteran
Joined: 04 Feb 2005 Posts: 1917
|
Posted: Tue Oct 23, 2012 6:36 pm Post subject: |
|
|
Hi!
No, I am only using the initramfs-bootsplash, following in detail
http://en.gentoo-wiki.com/wiki/Fbsplash#The_manual_way
This is my kernel line in /boot/grub2/grub.cfg:
Code: |
linux /boot/vmlinuz root=/dev/sda6 quiet video=1280x800 splash=verbose,theme:sabayon console=tty1 init=/boot/initramfs-bootsplash
|
I also did a rebuild of this initramfs, same results... _________________ "Coincidence is God's way of remaining anonymous."
Albert Einstein
"The road to success is always under construction" |
|
Back to top |
|
|
BitJam Advocate
Joined: 12 Aug 2003 Posts: 2508 Location: Silver City, NM
|
Posted: Tue Oct 23, 2012 8:32 pm Post subject: |
|
|
Martux wrote: | Code: | init=/boot/initramfs-bootsplash |
|
I don't know the syntax/commands for Grub-2 but clearly this is wrong. This boot parameter is telling the kernel to run /boot/initramfs-bootsplash as a program instead of the init program. For example try saying init=/bin/bash instead.
There must be some other way to tell Grub-2 where the initramfs file is. This migration guide might help. For one thing, it says Grub-2 has a strict naming policy for initramfs files. |
|
Back to top |
|
|
Martux Veteran
Joined: 04 Feb 2005 Posts: 1917
|
Posted: Wed Oct 24, 2012 3:56 am Post subject: |
|
|
@BitJam: Thanks for the input, but at that point our migration guide is wrong.
That is actually the reason why I gave grub2 another shot (because of the nice wallpaper feature it provides, compared to grub-legacy).
I found hints that grub2 is perfectly capable to behave exactly like grub-legacy, thus is capable to handle a maintenance-free setup.
Read: it can be told to always boot from a kernel named /boot/vmlinuz instead of /boot/vmlinuz-{version}. This is necessary to deal with kernel-updates made by "make install".
Initial hint found here: https://forums.gentoo.org/viewtopic-t-932262-highlight-grub2.html
Please see the post from nlsa8z6zoz7lyih3ap in the last third of the thread.
After further investigation, I stumbled upon this very enlightening article:
https://help.ubuntu.com/community/Grub2/CustomMenus#Maintenance-Free_Menuentries
I followed that guide pretty much step by step, ignoring the obvious errors of course.
Currently, my boot-entry looks like this:
Code: |
linux /boot/vmlinuz root=/dev/sda6 quiet video=1280x800 splash=verbose,theme:sabayon vt_handoff initrd /boot/initrd.img
|
Guess what? It still does NOT work as intended. The vt_handoff parameter seems irrelevant, no change if I change it
More interestingly the initrd entry gets ignored completely.
I have the exact same behaviour, even if I comment that initrd line with a #.
Also I have tried to "play by the book" and temporarily changed /boot/vmlinuz to /boot/vmlinuz-3.6.2-gentoo and /boot/initrd.img to /boot/initrd-3.6.2-gentoo.img. Of course both were present in /boot/.
Nothing changes: The framebuffer decoration only gets displayed after init started fbcondecor.
So far I only know that I totally agree to this other topic: grub2 IS a major pita. Still I would like to do the migration now once and for all and hope you guys can further help me out. _________________ "Coincidence is God's way of remaining anonymous."
Albert Einstein
"The road to success is always under construction" |
|
Back to top |
|
|
BitJam Advocate
Joined: 12 Aug 2003 Posts: 2508 Location: Silver City, NM
|
Posted: Wed Oct 24, 2012 5:54 am Post subject: |
|
|
Martux wrote: | So far I only know that I totally agree to this other topic: grub2 IS a major pita. | I completely agree with you here. Sorry I was not more help.
Quote: | That is actually the reason why I gave grub2 another shot (because of the nice wallpaper feature it provides, ... | I use a modified version of legacy grub that supports splash images. The difference is entirely in the files in /boot/grub. I keep a backup copy of them in case they get overwritten when I do an emerge world. Send me a PM if you want me to email you a tarball containing the modified grub files.
I use a grub splash image and an initramfs splash image and a different image on every vconsole. I also have a different background image on every desktop in my window manager. If you switch to mdev instead of udev then you avoid that annoying flicker when udev starts up.
BTW: I think you need an equal sign between "initrd" and then name of the initrd file. Linux says: Code: | 51 Boot command-line options
52 -------------------------
53
54 initrd adds the following new options:
55
56 initrd=<path> (e.g. LOADLIN)
57
58 Loads the specified file as the initial RAM disk. When using LILO, you
59 have to specify the RAM disk image file in /etc/lilo.conf, using the
60 INITRD configuration variable. |
In my experience, boot parameters for the kernel that take a value are always of the form "name=value". |
|
Back to top |
|
|
Martux Veteran
Joined: 04 Feb 2005 Posts: 1917
|
Posted: Wed Oct 24, 2012 2:39 pm Post subject: |
|
|
@BitJam:
Unfortunately even the = sign does not make a difference. I have no idea anymore, will PM you and give that modified grub-legacy a shot. Thanks! _________________ "Coincidence is God's way of remaining anonymous."
Albert Einstein
"The road to success is always under construction" |
|
Back to top |
|
|
Fitzcarraldo Advocate
Joined: 30 Aug 2008 Posts: 2034 Location: United Kingdom
|
Posted: Thu Oct 25, 2012 12:06 am Post subject: |
|
|
In case it is of any help, here's the kernel boot line from /boot/grub2/grub.cfg on my main laptop:
Code: | linux /kernel-genkernel-x86_64-3.6.1-gentoo ro BOOT_IMAGE=/kernel-genkernel-x86_64-3.6.1-gentoo root=/dev/ram0 ramdisk=8192 real_root=/dev/sda6 init=/linuxrc splash=silent,theme:Emergance console=tty1 quiet resume=swap:/dev/sda5 real_resume=/dev/sda5 intel_iommu=off |
_________________ Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC udev elogind & KDE on both.
Fitzcarraldo's blog |
|
Back to top |
|
|
Martux Veteran
Joined: 04 Feb 2005 Posts: 1917
|
Posted: Thu Oct 25, 2012 1:54 pm Post subject: |
|
|
I tried it now with several combinations: init, initrd, initrd=... No luck at all.
Only the framebuffer decorations get loaded at some point.
Well, I don't care anymore. After all we are talking about something I get to see maybe once a day for 3 seconds
Thanks to all who participated! _________________ "Coincidence is God's way of remaining anonymous."
Albert Einstein
"The road to success is always under construction" |
|
Back to top |
|
|
|