I’m hoping someone can assist me with a problem I’m having since upgrading from 12.2 to 12.3 (64-bit). Everything went well with the upgrade with the exception of the GUI for GRUB2 and the Plymouth boot screen. Instead of the nice GUI I get an error that says: Error: Invalid filter value Press Any Key to Continue. I then get passed to a text mode GRUB2 menu that appears to be in 640x480 resolution. The system boots fine after that.
The system has a vfat /boot, Ext4 /boot/efi and the / and /home partitions are in an LVM vg. All of the documentation I’ve found for reinstalling grub2 doesn’t work and I’m assuming it might have something to do with EFI?
Grub2 works fine with GPT disks and in efi mode. From what you describe I suggest you stop using a separate /boot and put it in an EXT4 root / partition and stop messing around with configurations that are not created by the default installer. While having a separate /boot does work, you have too many things going on and how does this help having a separate /boot now? I find that it was necessity for lvm set up, but not for grub2 and faster system boot if set up with ext2, but not faster for EXT4. And in any event, veering from the norm is just likely to create a problem, as you have discovered. As efi and GPT become more common, it may do better in the future perhaps.
Well I hope you feel better getting that off of your chest. I didn’t ask for a lecture, I asked for help. Telling me that I should have done this and should have done that doesn’t help me with the problem at hand. If you know so **** much offer some help, otherwise keep your lectures to yourself.
So my suggestion is to place /boot back into the root / partition and reinstall Grub 2 that way. I am sorry if it sounded like a lecture, though I did not throw in any bad words. The installer is more likely to select a setup that will work without /boot being on a different partition and just today I have run into others having problems trying to create a separate /boot partition though one was due to too small a partition. It has been a long day and many problems to try and fix. If you can over look the lecture, do consider not using a separate /boot partition and no matter what else happens, I do wish you luck with your openSUSE installation.
press the Gecko symbol and select (assuming grub2 is being used) :-
-yast
–Boot Loader (under System)
—Boot Loader Options
----Vga Mode – select Unspecified
-----Use graphical console – select
------Console resolution – set to Autodetect by grub2
-------Console theme leave blank or delete any entry
On 2013-04-14 03:16, jwomack wrote:
> Well I hope you feel better getting that off of your chest. I didn’t
> ask for a lecture, I asked for help. Telling me that I should have done
> this and should have done that doesn’t help me with the problem at hand.
> If you know so **** much offer some help, otherwise keep your lectures
> to yourself.
>
> No help and no thanks
That will not attract others to help you much.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
I had a reply ready to post, and changed my mind after reading that.
I’m guessing this is a UEFI system, though you did not quite say.
Is “/boot” the EFI partition? (It should not be).
It’s hard to guess what to do, without knowing what you did wrong. You have not given much information about what you did wrong, and you seem unwilling to discuss it.
This message means grub2 could not decode PNG image. It looks like your theme is corrupted. Default theme is in grub2-branding-openSUSE package so you may try to remove it, cleanup /boot/grub2/themes (to make sure nothing it left) and reinstall above package.