MX Linux Forum

Oops!

The sudo dpkg-reconfigure grub-pc followed by update-grub trick didn't work. But the chmod -x trick (followed by update-grub) did work.

Thanks!

It works! Mostly. One issue I have is how do I reset the MX grub boot menu to NOT show what it picked up when using OS prober. In other words, only show MX boot choices. Merely setting /etc/default/grub to have GRUB_DISABLE_OS_PROBER=true and doing an update-grub didn't change the menu back. I even ...

I'm reading the rEFInd doc, which is very extensive. I think I understand what it does now, and how to configure things. It seems like rEFInd installs itself as an boot manager, which becomes known to your machine's hardware (non-volatile RAM based) BIOS/EFI system. You can go into your machine's ...

rEFInd is totally compatible with MX. Does rEFInd show multiple ways of booting each OS install, such as MX's usual two kernels X sysVinit/systemD? Does it remember a default or last option? Do MX Boot Options and MX Boot Repair know about rEFInd, and if so, how do they interact? Would it help if I ...

Would something like rEFInd work in my case?:

It sounds like it does the necessary scanning at boot time. And rEFInd exists in the Debian repo. Would it be compatible with MX?

grub menus are not built at boot time. it either happens when update-grub is issued manually, or when triggered by a kernel install. even when our installer installs grub, it issues and "update-grub" to update the menu. I could have sworn that I've seen the grub menu pick up OSs that are on ...

I guess the question is really about what the OS Probe in Grub does, and when it does it. It has to be doing something at boot time in order to discover new OS installs that were not there on previous boots. But it seems to retain its knowledge of past discoveries to the point of limiting the ...

I would have issued "sudo /sbin/reboot" or "sudo /sbin/halt" from a new tty instead. What if your keyboard was unresponsive when the system froze? Use the magic SysReq REISUB (to reboot) or REISUO (to shutdown) key sequence, which will often work even when the system is otherwise unresponsive to ...

I have a dual boot setup with MX 23.5 AHS and Debian Testing, with the boot menu setup by MX. This is working almost perfectly, except: When a new kernel is installed in Debian Testing, I have to boot MX and use the MX Boot Options tool to get the boot menu to see that new kernel. Is there a way to ...