Well, in my last post I was asking about editing manjaro’s grub in a more friendly way, but I got your idea. Thanks again and happy New Year!
@groosha, just be aware that this package is not up-to-date with regard to security mitigations.
1 Like
Yes, it’s true.
I’m wondering what’s the best option right now for those who want to customize their grub or don’t want to use Manjaro’s grub.
I used grub-customizer because the entries were duplicated countless times and the theme was messed up every single time I updated grub.
It’s not
grub-customizer doesn’t just work with grub-vanilla, but it did with grub.
It doesn’t feel right that what I found to fix grub, (because that’s the only motive I had to use grub-cutomizer) it’s just not possible anymore. I find myself having to learn yet another way to fix my grub just because grub-customizer it’s making problems for other people.
What the hell, I know when I mess up with this things something can go wrong, and that’s why we have timeshift, you don’t have to block me out of it.
And I like what comes with grub, I don’t want start from scratch, just an easy way to fix my entries, and that’s all I did with grub-customizer, but now I can’t, and I’m stuck with an endless grub with duplicated entries and a messed up theme, or forced to learn what breaks grub at a lower level (which I think it’s more dangerous than what could grub-customizer do anyway) and start from vanilla or fix my already broken grub.
I don’t understand why would you take responsibility of my grub. If I want to use grub-customizer with grub and not grub-vanilla I should be able to do it, and if I break it I fix it.
I also don’t quite get this…
Yeah sure, if you don’t support grub-customizer, don’t give support for it, but if someone needs help with it and someone can give it, are you gonna block it?
5 Likes
Can you provide evidence for that or is it just your humble opinion?
Yes, this is most likely the best approach if you want to continue to use Manjaro.
Don’t forget you are using a free-of-charge distro and you are still free to do with your grub what you want, but you cannot expect that your personnel needs rule how a distro is maintained. It has be clearly explained why the use of GC poses issues for the majority of users. Take this as a chance to learn an alternative approach and you are welcome to tell your solution the community.
1 Like
The duplication of entries is actually caused by GC itself, if you use it regularly, and possibly from different instances of GC installed in different distros.
It adds more and more os_prober entries in the grub that GC uses, so your update grub command repeats itself and generates duplicate entries.
This has been the case for a long time as far as I can recall. I was using GC around 2013 but after I understood the problems and that I was using GC to remove duplicates it itself was making, I stopped using GC around 2016.
5 Likes
Oh, if that’s true that means I’ve been doing stupid things for months.
I do have multiple OSs but only one has GC. I’m going to reinstall that particular OS because of multiple problems, and as I can’t, I also won’t install GC. If the entry duplication still persists I’ll update.
Yes, I understand that, but I’m not the only one having the entry duplication issue. If it’s GC’s fault I’ll dump it, since is the only reason I keep it. But if it’s not GC’s fault, GC it’s a way the problem could be fixed, so if the problem still exists in grub (which i doubt right now) it wouldn’t make sense to put GC as incompatible unless the issue is fixed, that’s the point I intended to make.
If you install grub-vanilla and grub-customizer, launching GC says you have to configure I-don't-know-right-now-what-variables, while launching GC with grub it used to just launch and be ready.
It’s about $DEITY-damn time.
yes.
Sorry to cut to the quick on this…
But it doesnt matter how much you stamp your feet about wishing grub-customizer didnt conflict with grub.
The fact is it does … it always has, at least in the sense of whether its compatible or dependable … it just wasnt literally listed as a conflicting package until sometime recently.
If you were to look around at old blog posts or the previous forum you will find all the data you need.
grub-cusomizer is crap software. dont use it. it doesnt work well. it breaks things.
if you must use it … then use it with some other grub … however you do it … you are on your own.
(PS - not seen a duplicate grub entry from manjaro in all the years I have used it…)
1 Like
@cscs This is what I got today after running regular update via Octopi (for some reason, Pamac didn’t show any updates, but that’s another problem):
Previously I had to use grub-customizer to fix this. I guess I’ll have to learn how to deal with grub.cfg (and lots of other files like 10-linux, 20-os_prober etc.) manually now.
1 Like
Did we not already establish this is a symptom of grub-customizer ?
To be fair I dont know for sure … but from my view the correlation seems strong …
(and yes … now that you have used it … your grub is basically ‘broken’ and you have to ‘undo’ GC)
3 Likes
This - and to learn why these double entries could occur. 
1 Like
Yeah, I’ve used grub-customiser before, but after today update I’ve got a lot of new useless boot options.
Grub-customiser was auto deleted, and now I can’t change boot initrd to add patch to repair broken suspend mode on by Ryzen 4500, niceeee.
did you read anything else here?
or are you just throwing in your hat to be counted
“me too! I also messed up my grub and made duplicate entries by using grub-customizer!” ?
niceeee.
are you sure?
grub-customizer lets you add ‘patches’? in what way?
how ? why ?
by ‘patch’ are you referring to a boot flag or something ?
1 Like
yeah I did
I’ve got that “it was my fault to use gui to make it easier” )
yeah, patching ACPI tablie (nns.ee/blog/2020/10/18/acpi-patching.html)
Do I understand correctly that now I need to edit /boot/grub/grub.cfg manually?
Many users in old forum reported having duplicate entries in GRUB, which AFAIK always related to use of grub-customizer
These comments are from 2016:
Grub-customizer - possible caveats
Grub customizer can cause a lot of issues because it’s editing the /boot/grub/grub.cfg directly, which is not recommended. Just edit /etc/default/grub and do sudo update-grub
Grub-customizer has a lot of quirks. It is probably less bother to just learn how to edit the grub default files than it is to learn what not to do in grub-customizer`
1 Like
That link is decently advanced … but everything in there is by hand … they dont mention grub-customizer.
Yes… but its already walked through in that tutorial.
You add initrd /dsdt_patch before any of the *initramfs*.img
(or more specifically probably something more like just /boot/dsdt_patch on the same line but right before /boot/amd-ucode.img)
The mem_sleep_default=deep part goes in the normal CMDLINE options in /etc/default/grub
And of course you need to regenerate things using sudo update-grub.
(this can also be automated using scripting and such … see GRUB - ArchWiki)
PS.
This has nothing to do with GUI or anything like that.
Its simple - grub-customizer sucks. it should be considered broken and dangerous.
5 Likes
Ok, thanks, going to read archwiki to factory reset grub)
For some dummy like me, how I recovered grub after grub-customizer:
- remove all files from /etc/grub.d (backup them before)
- grub-mkconfig -o /boot/grub/grub.cfg
- to change (if you need that) initrd string in grub use GRUB_EARLY_INITRD_LINUX_STOCK (better GRUB_EARLY_INITRD_LINUX_CUSTOM) variable in /etc/default/grub and update-grub after changes
3 Likes
Why don’t you use
GRUB_EARLY_INITRD_LINUX_CUSTOM
Reference:
GNU GRUB Manual 2.04: Simple configuration
3 Likes