antiX / MX LinuxThis forum is for the discussion of antiX and MX Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As so often in the past, your comments are of no help whatsoever. I've been looking Online for hours and can't find anything which would resolve the excessive grub entries. Really, I wish you would just stay away from my posts. Every time that you comment, it's without any useful information whatsoever. Someone who responds with comments designed to pad their stats. Ridiculous. Do you really believe that I don't know how to use the internet or how to look for solutions there? Going to a forum is always my *LAST* stop, only after I couldn't find the correct solution on my own.
@hazel @captain_sensible
My apologies, but I have seen this the above users comments literally hundreds of times on this forum already, where instead of help there's nothing but a blank or criticism. It's ridiculous, as if there's nothing better to do than to leave useless remarks (see my signature too).
Anyway, I'm afraid that I'll have to give up on this for now. As I've already explained previously, I can't find the older installed kernels within Synaptic, MX Packager Manager Stable, or MX Package Manager Debian Backports. So if I can't find something, then obviously I can't delete it either.
As far as grub is concerned, I found grub, grub config, and grub backup files in no less than 4 different locations. Altogether within their folders/sub-folders probably a dozen of them. But I can't find a single file that would account for the eight kernel entries that I'm seeing upon startup. I'll be checking out the dedoimedo link sometime in the next few days.
Last but not least, I also installed/re-installed everything grub and grub-customizer related. Nothing that I tried made any difference. Grub customizer displays the correct grub menu as it should appear during startup, but for some reason that's not what I get on the screen. No matter what I try with the grub-customizer as a last resort, even though changes take place without errors as they're applied, those same changes do not remain present when the machine is started up again.
On a positive note ... no matter what I edited, re-installed, or -reconfigured, the system didn't get borked. At least that's something.
This user has completely lost it IMO.
S/he is doing this every time! It's like s/he's really intent on derailing his/her own threads.
To clarify, both comments criticised here are relevant to OP's problem and not "useless" or "of no help whatsoever".
Also, consider this:
Quote:
Originally Posted by LinWinux
Well, the grub configuration seems to have changed a lot during the past 5+ years ...
Utilizing MX Linux which has been updated & upgraded multiple times now, I can no longer figure out precisely where I can go in order to remove obsolete entries. There seem to be several locations with grub related files. Currently I have 8 entries for the previous 4 kernels. I would like to simply remove the oldest two entries, since it annoys me to have the startup screen cluttered with things that I don't want to see.
5 years ago , GRUB was already at version 2. No doubt some things have changed, but the configuration process is the same.
I find it strange that after "decades of Linux experience" this user has not grasped s few essesntials of grub configuration, and, worse, is not able to read a few man pages.
I happen to know exactly how to "solve" it but I'm not going to tell them, because it wouldn't cater to all of OP's desires and consequently I would just get abuse for it.
Based on what I've read from captain-sensible's provided link, I'm beginning to think that perhaps the menu.lst is still being recognized from some old remnant somewhere? It's the only thing that makes any sense to me, since on one hand grub-customizer has absolutely no effect on the startup of grub ... yet not a single grub related file that I could find on the system shows anything even remotely close to what I see on the screen during startup.
An old menu.lst file on the other hand, would look exactly like the content that I'm seeing on the screen.
I'll be investigating the menu.lst angle today, to see what I can find.
@ondoho
I don't have a lot of threads here, but if you look at them you'll find that with but 3 exceptions ... two of which didn't really require a solution ... all of them have been solved, and most have those have been solved and marked as such by myself. See my threads here: https://www.linuxquestions.org/quest...rchid=11300115
You're just here to waste space, waste time, and pad your stats as you've already done twice or thrice in this thread as well.
@hazel
No, I think you misunderstood what I wrote. To see which kernels were available and/or installed, I went to the MX Package Manager / Stable Repository (or perhaps it was just the default popular packages). One of the options there was ... Kernels. When I clicked on that, only 5 Kernel related apps showed up and one of those was the Liceurix Kernel. I've never installed it, I just went there to look for more clues about installing/removing various Kernels.
Last edited by LinWinux; 11-15-2020 at 02:53 AM.
Reason: Error
5 years ago , GRUB was already at version 2. No doubt some things have changed, but the configuration process is the same.
I find it strange that after "decades of Linux experience" this user has not grasped s few essesntials of grub configuration, and, worse, is not able to read a few man pages.
Would you be so kind and show me where you come up with this nonsense? At no point in my life have I *EVER* claimed to have decades of Linux experience. I have 31 years of computer experience which obviously does not translate into Linux experience. Read my signature, and stop wasting everyone's time with your utterly useless remarks.
Are you sure that MX is controlling grub? Are you dual booting another linux?
No, it's not a dual boot system. Strictly Linux on a 120 GB SSD. This was a snapshot which was originally created with MX Linux on another machine about 1 year ago. The other machine was strictly Linux too, updated and also upgraded (sudo apt-get dist-upgrade) for apx. 12 months before the snapshot was created. Both machines same model, Dell E6500. No dual-boot on that one either.
And no, due to my experience with Grub-Customizer and reading about the menu.lst file, I'm not at all certain about what's controlling Grub.
It's obviously not "a real problem" since everything works, but it would be nice to figure this out.
OP has been doing the same dance on the MXLinux forums, and are not an active user there anymore.
Whether they've been banned or requested account closing I do not know, I guess the result is the same.
You are complaining a lot. I do respect your feelings and understand your frustrations.
But if you realy want to get help I' suggest you start from scratch and perhaps go to
Guide on How to ask for Help(...)
and show us the exact steps, commands and error-logs etc. You need to stay focused otherwise you would waste (at least my) time.
If you now don't like the MX approach to systemd, don't like the Forum, don't like the hardware recognition, and don't like...I can't even remember what else now...oh yes, that we don't cater to the unfortunate masses as you would like, then it sounds like you should consider moving on.
LinWinux won't get an answer like this here on LQ.
Are we a catch basin for those who fell through trolling other, more specialised forums? I hope not.
Quote:
Originally Posted by LinWinux
You're just here to waste space, waste time, and pad your stats as you've already done twice or thrice in this thread as well.
That was my first post to this thread.
I am way beyond the stage of wanting to pad my stats, sorry.
And I won't shut up, because I think it's you who's wasting our time and ultimately causing trouble, not me.
Thanks, but that was another problem where the system wouldn't boot up with grub. The only way that I was able to resolve that problem, was by running boot repair on that setup.
Technically I could do that here as well, but then I would lose my nice MX boot screen since boot repair overlays its own image or color once it's finished. I have no idea how I would then get my old MX boot background back again. I'll try that as a last resort and then use grub-customizer to see if it will let me add a background image. I'm really surprised that it's so difficult to find those obsolete entries, in order to remove them.
Have a nice remaining Sunday. I'm done for today (almost evening here).
Well, I ended up having to resort to Grub-Repair again. At least that got rid of any unwanted entries.
I would really like to have my old MX Linux (Lightdm?) screen back, during startup of the machine.
Does anyone know whre to find the grub-repair location which contains the background? I'm not sure if that's just a color or if that's a single color background image, but I really don't care for that blue background. Tried using grub customizer but that didn't work. Actually, nothing that's selected with grub-customizer works, so I assume that that still looks for the older grub which used the menu.lst file. Every change made in grub-customizer remains as made, you can save, adjust, etc. But a reboot just keeps everything the same as before.
Distribution: antiX using herbstluftwm, fluxbox, IceWM and jwm.
Posts: 631
Rep:
menu.lst = grub legacy ie grub 1 before grub2. There is no file called menu.lst on a standard Debian/MX Linux install since grub2 uses grub.cfg.
How did it get onto your box?
I have absolutely no idea. The only thing that I've been working with were MX snapshots which were started a couple of years ago. After 4 - 6 months I'd update & upgrade followed by creating new snapshot to be used. This was repeated apx. 3 times during two years.
Well, I ended up having to resort to Grub-Repair again. At least that got rid of any unwanted entries.
I would really like to have my old MX Linux (Lightdm?) screen back, during startup of the machine.
Does anyone know whre to find the grub-repair location which contains the background? I'm not sure if that's just a color or if that's a single color background image, but I really don't care for that blue background. Tried using grub customizer but that didn't work. Actually, nothing that's selected with grub-customizer works, so I assume that that still looks for the older grub which used the menu.lst file. Every change made in grub-customizer remains as made, you can save, adjust, etc. But a reboot just keeps everything the same as before.
OP's refusal to read grub documentation is amazing.
It's really not hard to change the background.
Grouping things into submenus is also possible, less visual clutter.
Is this supposed to be some sort of protest? Like: "GRUB2 is too complex, I refuse to acknowledge how it works and use it as intended, instead I will keep on hacking around the problem until GRUB2 developers hear me! There!"
I also wonder about OP's refusal to address the issue of the multitude of old kernels they seem to be dragging along.
I addressed the inability to find the installed kernels in order to be able to remove them on the first page already. I'm not a terminal guru, so terminal commands are only possible for me when someone lets me know what I should be typing into the terminal window. If I look at all of the grub related files that I can find, without finding one which would allow me to edit the unwanted kernel references out of it, then what else can I do.
I can't find the installed kernels with the package manager, and I can't find the obsolete kernel lines within the grub files.
Perhaps I've missed some files, but I wouldn't know.
That's why I'm on a forum, looking for help and for answers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
