Different Grub Resolution / Theme for Manjaro

Hi, guys!

Hope everyone is ok. Wondering if anyone can lend me a hand with something that is quite annoying for me. It’s not a real issue but kind of got me racking my brain trying to find a solution for this.

So I’m in a brand new and fresh Manjaro installation on my computer. Just got some hardware upgrade by changing CPU and motherboard, and took advantage of it and got myself a new NVMe storage disk as well (I was using a regular hard drive before that).

Got new pc built up, got system installed, rebooted and on startup I come across a ‘new’ grub screen which looks like from 1996 back when I was using bedroom-sized computers. I’ll leave a picture of what I’m seeing below:

It may not be noticeable from the picture, but the resolution on this grub screen is so big and so different from it was before I got my new Manjaro installation that got me thinking what I could do to get it back to what it was.

Here is an example of how it was looking like on my previous Manjaro installation (looked this picture up on internet):

Not only the appearance looks different, but the resolution above all things.

But this is ~not~ restricted to the appearance / aesthetic. It feels so unresponsive and I need to wait about 4-5 seconds before having the selection changed when pressing the arrow keys up or down to select another option, or when I press enter to get advanced options for Majaro, etc. In other words, it’s also slow and unresponsive, although functional with the right dose of human patience.

I tried looking in Manjaro official forum, as well on other sources in the internet, but haven’t found a solution for my case.


I have tried:

1. Downloading a new Manjaro grub theme

I noticed that the default theme on my system was “manjaro”, which is installed at: /usr/share/grub/themes/manjaro/

Looking for other related themes in pamac I found “manjaro-live” so did try it with: sudo pamac install grub-theme-live-manjaro

It got installed to: /usr/share/grub/themes/manjaro-live/

But the despite the different name, it contains the very same files with same settings as the other one, so didn’t seem to be of help. Either way, to apply the change I replaced the grub theme path on grub config file to: GRUB_THEME=“/usr/share/grub/themes/manjaro-live/theme.txt”.

Saved and applied with sudo update-grub and rebooted, no luck.

Somehow I don’t really think this is a matter of theme, but something else, so went a bit deeper.

2. Modifying GRUB_GFXMODE in grub config settings

Also tried modifying this parameter in the grub config settings.

Default value was: GRUB_GFXMODE=auto
According to this Change GRUB Resolution Scaling, I would be able to “set to any resolution that appears in grub > videoinfo (enter grub, press c to enter command line and issue command videoinfo”. However, when I tried checking videoinfo on grub, I got no available resolutions as output for the command, so I think this didn’t work for me.

Please see below a picture of my output (pardon for the low-quality picture):

Yet, I was still hopeful of getting a positive outcome, so I tried the impossible, crossed my fingers and edited the value in the grub config file and went along.
Current value: GRUB_GFXMODE=1920x1080
sudo update-grub, rebooted, although it didn’t work. :melting_face:

So I had this error (or lack of information) from “videoinfo” as a starting point for a new deep dive in Google.
Pages like Grub videoinfo doesn’t show all resolutions seemed helpful but this guy was at least having some output for videoinfo, whereas How to safely change grub2 screen resolution? was too old, yet addressing the issue with the same solution.

3. Despair led me to generative AI consultation - the oracle
I tried asking ChatGPT for possible solutions and even followed suggested steps, but nothing was of help.

Does anyone have any idea what could I do to sort this out?
Grub file settings

# GRUB boot loader configuration

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=UUID=aba3e479-1eb3-46ec-94a8-acea5508f633 udev.log_priority=3"
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'menu' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=hidden

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y

# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false

# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true

mhwd command output

> 0000:03:00.0 (0300:1002:7340) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI

Additional information:

  • When updating grub I see an warning message which seems to accuse the difficulty on acknowledging my new NVMe disk:
    ~  sudo update-grub                                                                                                                               ✔ 
[sudo] password for marcos: 
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro-live/theme.txt
Found linux image: /boot/vmlinuz-6.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-6.10-x86_64.img
Found initrd fallback image: /boot/initramfs-6.10-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
  • But I’m not sure that this would be a problem once, as reported in this thread (long thread warning) Unknown device type nvme0n1 (two ssd) this could be a known issue – reported by user “Chomsky” in Sep 2020.

  • The theme files I see in my theme folders (for example: /usr/share/grub/themes/manjaro-live/) seem to correlate the picture I see on my current grub menu, but in a total different scale, which leads me to think it’s a matter of resolution rather than anything else. For example, see below a capture of file “background.png” found in the folder and a capture from my grub selection:


They do seem to have the same pattern, although what I see in my monitor is a amplified and visually destroyed version of the same.
Also the manjaro logo seems to match the current grub version:

Is there anything I can do to get my grub resolution corrected? Is this a theme-related issue? What can I do to get “videoinfo” grub command to work, to show me available resolutions so that I can use one of them in the grub config file and get it to work?

Thank you in advance for your help.
My apologies if this topic is duplicated/miscategorized. I tried looking in the whole forum before posting.

Thanks and cheers.

You should find this helpful:

taken from the Arch Wiki.

Keep in mind that any resolution you set must be supported by your video card.

1 Like

It’s not the theme, it’s not the nvme warning which is pretty much standart these days, and mhwd is not active at the time.

I’m not an expert in this situation, but since you already tried changing resolution manuall, the only thing that leaves is the video drive. Grub just does not recognize your new video. You most probably have to preload some module in the grub config. Or even at the first stage as a parameter while installing on the efi partition. But i cannot help more, no idea how to find the module you need, if it at all exists.

P.s. another idea might be to disable the framebuffer, as per another section of the link above. If that makes it ugly but responsive it might be more acceptable.

1 Like

Thanks @soundofthunder. I`ll check it out to the detail. I just wonder why this is happening on a new installation once I-m using the same video card as before… strange, but that’s what I got for now.

Thanks @Teo. Then I’ll see if I can spend more time checking on my video drives. I’m using a AMD Radeon Sapphire 5500 XT, same video card from my previous installation… never got a problem before but I understand this is no guarantee that it would this time. Will keep my research and try to find and answer.

Probably not the same GRUB version installed, that can be the difference. If you never reinstall GRUB manually, it will not update by itself. The package installed in Manjaro will, but not the one “installed” as your bootloader.

I did notice another thread where the OP mentioned removing a recent Plymouth version, and after a subsequent reboot, their resolution had (magically) returned to its previous state.

Now, it might just have been coincidence. It’s possible other things they tried before rebooting had actually fixed the issue, but maybe it’s worth trying.

Plymouth is the boot screen (the three dots that you see during boot); a quick forum search will show it can often contribute to boot related issues.

It’s not a simple uninstall procedure; there are several other tasks that must be undertaken to ensure Plymouth is removed properly.

This may or may not solve your issue.

However, if you do decide to remove Plymouth, please see the following tutorial for guidance:

I hope this helps.

Cheers.

Hey guys, quick update on this subject.

SHORT VERSION
– >ISSUE IS SOLVED

What did I do? Reinstalled Manjaro.
What did I do different on this new brand new installation?
Installed Manjaro UEFI instead of BIOS!


LONG VERSION

I was still doing some research

Well, I can’t even recall all the pages I have visited which helped me to find the solution, but it all started by running the command “sudo hwinfo --framebuffer”, from which I was supposed to get the available resolutions detected by my computer. Well, I was getting nothing there.

Then, I finally came across this page from Stack Exchange: GRUB not showing support for all possible video modes. This drew my attention:

Light at the end of the tunnel :bulb:
So two things drew my attention here:

  1. Why was user harrymc asking which computer model install (BIOS or UEFI) the other guy was using? Why is this important in this case?
  2. Jibun no Kage replied saying his computer is BIOS basedand this felt important as so was mine!


Double checking that my case was the same as that guy

As I recently went through the Manjaron installation, I remember specifically the time when I was asked by Calamares intallation agent to create at least a 8 Mb BIOS partition for “bios-grub”, boot or something alike (can’t remember exactly what it was).

I was almost sure that my Manjaro installation was BIOS based, but wanted to double check anyways. Found this: Check if you are using UEFI or BIOS on Linux
.

Well, EFI folder was not there, I was definitely on BIOS.



Reinstalling the system

Recent Manjaro installation, having these issues, no files on system… what am I afraid of? So I decided to start over and re-install Manjaro on my computer.

This time, I ensured it would be installed with UEFI system. This older thread in our forum fitted like a glove:

When setting up my new installation parameters, I followed exactly the same steps described in the second link:

Manjaro installation

Now that you have partition sizes defined let start and the numbers are MB which is the unit Calamares makes use of

  1. Reboot your computer to the live USB media.
  2. Launch the graphical installer - it is named Calamares.
  3. Follow the guide until you reach the Disk selection/preparation
  4. Select Manual partitioningNext.
  5. Select the correct disk selected - should be easy to see.
  6. EFI PARTITION
    :warning: Skip if using BIOS/MBR
    Select the unpartitioned space → Create
    a. Size → input 512
    b. Filesystem → select FAT32
    c. Mountpoint → select /boot/efi
    d. Flags → check bootOK
  7. SWAP PARTITION
    Select the unpartitioned space → Create
    a. Size → input 2048
    b. Filesystem → select linuxswapOK
  8. ROOT PARTITION
    Select the unpartitioned space → Create
    a. Size → input 20480 (min. recommended size)
    b. Filesystem → select ext4
    c. Mountpoint → select / (root) → OK
  9. HOME PARTITION
    Select the unpartitioned space → Create
    a. Size → Use remaining
    b. Filesystem → select ext4
    c. Mountpoint → select /homeOK

:warning: Skip if using BIOS/MBR

  • Continue with the guide and when finished do not reboot.
  • Open a terminal
  • Input efibootmgrEnter
  • Verify the BootOrder - you should have a manjaro entry and the >corresponding number should be first in the BootOrder

Upon reboot, it was working working again as expected!

Manjaro grub (this one is not from the internet, but from my computer):

Grub “videoinfo” command:



So reinstalling Manjaro with UEFI booting partition has solved this problem for me. I continue not fully understand the reason behind it, but I’ll leave it here. If anyone comes to know the reason, I think it would be great to enrich this thread with a possible root cause and explanation, otherwise let’s just leave this here.

I decided to document this as good as I can hoping this might be useful for someone down the road.

Thank @soundofthunder , @Teo and @omano for your engagement and support.

Cheers!

It is good that you found a solution (sort of) by reinstalling. I am just wondering if you could have also gone down the path of switching from BIOS to UEFI without reinstalling by following the instructions on Manjaro’s wiki: 4 Switching from BIOS to UEFI

I followed those same instructions earlier this year and encountered zero issues changing to UEFI boot (although I only have Manjaro installed, so I can’t advise on multi-booting with Windows or other Linux distros).

2 Likes

Well, that’s probably how you should have installed Manjaro to begin with. A lower resolution might typically be expected with an MBR installation.

I seem to recall a decade (or more) ago trying to increase console resolution on some old system, without much success. Usually, I simply ignore it.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.