I had started a thread in the german forum concerning problems with grub: When I try to stat Manjaro, I get “memory tester”. In the “extended” entry I find about 10 or 12 “memory tester” entries and the last entry “manjaro”, which indeed starts the sytem. There seem to be some answers, but I can’t access the forum anymore, instead get
“Forbidden
You don’t have permission to access this resource.Server unable to read htaccess file, denying access to be safe
when I try to login. I can’t even use the Page where I am logged in!
So I ask here, even if my english is not so good:
Is there a hidden? place, where grub can store entries where Grub-customizer can’t find them? Maybe efi-nvram or so? How can I kill this and return to ordinary grub?
here my /etc/default/grub:
# GRUB boot loader configuration
GRUB_DEFAULT="saved"
GRUB_TIMEOUT="5"
GRUB_DISTRIBUTOR="EndeavourOS"
GRUB_CMDLINE_LINUX_DEFAULT="nowatchdog nvme_load=YES nvidia_drm.modeset=1 loglevel=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 'hidden' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE="menu"
# 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-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
GRUB_BACKGROUND="/usr/share/endeavouros/splash.png"
GRUB_THEME="/path/to/gfxtheme"
# 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="false"
# Probing for other operating systems is disabled for security reasons. Read
# documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this
# functionality install os-prober and uncomment to detect and include other
# operating systems.
#GRUB_DISABLE_OS_PROBER="false"
GRUB_EARLY_INITRD_LINUX_STOCK=''
That is not an official forum. Can’t acces is too right now (from O2 mobile net). Maybe the server is down (i have set 403 when i updated the machine when i had a forum).
P.s. do NOT use grub customizer! It breaks things.
If you need further help with this, open a new topic.
This forum here has got a german section - as well as many other languages, although there might not be as many responses as in the english section because not as many people here spear/read/write the german language.
is, as far as I know, not associated with this forum here - which is the “official” forum for anything Manjaro.
It seems to be offline - perhaps permanently.
Perhaps search here for hints and instructions on how to remove the package “grub-customizer”
and then restore the “normal” grub configuration.
It (grub customizer) is known to create problems such as yours.
From this, it seems you don’t even run Manjaro, but EOS instead - which is nearly the same as Arch.
Posting this request on their forums would be more appropriate.
But your inxi output says “Manjaro” …
Installing grub-customizer is still not a good idea, be it on Manjaro or Arch/EOS.
grub-customizer is a package from AUR
You should remove it and restore the “normal” grub configuration.
It is a Very Bad™ idea, actually. It completely ruins Manjaro’s customized grub configuration. That’s why we removed grub-customizer from the repository a number of years ago already.
@bssmusic, remove grub-customizer, clean out your /etc/grub.d, and reinstall grub from the official Manjaro repositories.
Good resource right there… and obviously another reason to completely avoid reading anything in reddit as more than a joke (for every sane nay-sayer, there’s another dozen who come up saying ‘works great for me, never had an issue…’).
the amazon cloud services are disturbed at the moment. it’s a huge impact and affects a lot of services direct and indirect. possible a reason why the server is not avaiable.
Yes - clear instructions.
One good thing about the package is that they apparently have backed up all the original configurations
and put a file with instructions on how to restore them:
And here is how to remove it:
If you do already use grub-customizer and want to remove it follow this from /etc/grub.d/backup/RESTORE_INSTRUCTIONS to revert changes it has done to your system:
That’s perhaps because I have more than one system on my workstation:
-Manjaro with 6.12.48-1 (my production system)
-UbuntuStudio ( for music)
-EOS
-windoze11 (for DXO, Photoshop, Lightroom)
-Manjaro unstable (playground)
I have such setups for more than 10 years (since SuSE) and never had problems before UEFI came on the scene…
And that is the reason why I asked for the hidden place where the completely wrong grub config could be stored - I could not find it neither in /etc/grub nore in /etc/default/grub and suspect - as I mentioned before - it hides in the UEFI-BIOS.
A more manageable solution to multi-booting with several Linux flavours in the mix, is to use the refind boot manager as your initial boot loader, which in turn will effectively chainload every UEFI boot loader GRUB in your system, including that of Windows or BSD.
This allows one to leave each GRUB untouched and managed by it’s respective OS – this means less maintenance (no juggling settings just to enable a successful boot) – plus, the added convenience of being able to bypass any installed GRUB and boot the respective kernel stub directly.
“A more manageable solution to multi-booting with several Linux flavours in the mix, is to use the refind boot manager as your initial boot loader, which in turn will effectively chainload every UEFI boot loader GRUB in your system, including that of Windows or BSD.
This allows one to leave each GRUB untouched and managed by it’s respective OS – this means less maintenance (no juggling settings just to enable a successful boot) – plus, the added convenience of being able to bypass any installed GRUB and boot the respective kernel stub directly.”
Ah, that seems to be a reasonable solution, but
where do I find it - edit : OK, Rod Smith
first install the “refind boot manager” and then grub, or reverse?
how to get rid of the sense- and useless configuration I have on my startscreen
Well with default settings, they will write the boot files and efi variable with the same name, so yeah, this is to be expected.
When you restore grub, do not forget to name one of them something different than manjaro.
This and many more pains can be saved using refind in such complex multiboot scenarios.
Thanks for asking. I mention refind briefly toward the end of a multi-boot tutorial I authored;
refind is available from the official Manjaro repositories, and installation can be as simple as:
1. Install the refind package so that it’s available to your system: sudo pacman -S refind
2. Use refind’s own internal command to install it: refind-install
The default install location is $ESP/EFI/refind.
3. Reboot and immediately boot to BIOS to ensure that refind is first in boot order – this typically happens automatically, but it’s better to check.
Preferred:
Ideally, each GRUB would already allow booting to each OS (so that refind will find and detect them)
Install and update refind only from Manjaro; ensuring that it installs to Manjaro’s $ESP for consistent management.
Workaround for your current state:
Boot a Manjaro Installer USB and enter a chroot environment - install refind from there. This may not be ideal, as GRUB still won’t be working, but you can still bypass GRUB and boot to Manjaro via the kernel stub, from refind.
From that point, you can fix GRUB at your leisure.
There should be two Manjaro icons (possibly only one if GRUB isn’t working) when you reach the refind menu. Beneath the icon(s) will be an indication of which is which.
Configuration is in a single file within the $ESP/EFI/refind directory - it’s well documented - and shouldn’t take you long to configure it to your preference; though it already installs with what I like to call “sane defaults”; most only play with the theming.
As they are separate entities, the important factor is to make sure refind is first to boot.
The “memtest” entries, I’ll leave for others to address. Regarding how the GRUB menu displays; that can be configured in /etc/default/grub.
The memtests are probably ignorable. You have several linuxes, and each has 1 or 2 copies of it. So if all are detected, here are your 6 entries.
There were 2 methods to attack this: the duplication inside 1 os was solved uninstalling some package, and then there was some config to disable the detection from other oses. Maybe some sub setting in os prober. I have forgotten already, at the end i didn’t bother solving it (i have 1 manjaro so i had it 2 times).
After refind is working as expected, os-prober can probably be disabled completely, as there would be no more need to boot other boot loaders from GRUB – those extraneous entries should no longer be an issue.
