MX Linux Forum

DBeckett wrote: 
I prefer GRUB_SAVEDEFAULT="true". While my daily driver is at the top of the list, I may be playing with another distro. After major changes, like a kernel upgrade for instance, I like to reboot just to be sure everything's okay. I can walk away while it's rebooting and return to find it where I left it.

Yeah, as always different users tend to have different preferences. When we establish default preferences during development, we attempt to select reasonable values for the average user.

It is curious. Possibly something else broke it.

I installed antiX-16a1 and set it to MBR,
later changed back to MX-15 via Boot Repair.

Presently at boot, grub only shows 1 boot line: MX-15
Strange. :)

Richard wrote:It is curious. Possibly something else broke it.

I installed antiX-16a1 and set it to MBR,
later changed back to MX-15 via Boot Repair.

Presently at boot, grub only shows 1 boot line: MX-15
Strange. :)

I have also noticed this happen, but unfortunately didn't look into it further at the time because I was wiping that distro and expanding my home partition to fill the space. I'll have to play around with it abit more this weekend.

I added back another boot line for another kernel of MX-15 which shows and boots
but update-grub doesn't pick up the WIN partition nor the antiX partition. Curious.

I'll leave it alone for a while to see if someone has an idea.
Well, a little while. Changed grub as follows:
# GRUB_DEFAULT="saved"
GRUB_DEFAULT="MX GNU/Linux, with Linux 4.1-7.dmz.1-686-pae (sda2)"
. . .
GRUB_SAVEDEFAULT="false"
# GRUB_SAVEDEFAULT="true"

then # update-grub to see what happens?

NOTE: Same result; update-grub doesn't pick up the other installed partitions.

@v3g4n

I have also noticed this happen, but unfortunately didn't look into it further at the time...

I too have experienced similar type confusion in the past that seemed to derive from over-zealous use of grub-customizer, but I was not sure just what configuration caused it and so, finally, reinstalled.