- This topic has 10 replies, 5 voices, and was last updated Oct 20-9:22 pm by Brian Masinick.
-
Posts
-
AA BB
Prior to my AntiX 19.2 to 19.3 update, I was able to dual boot antiX and MX 19 from the boot menu.
After the update, the new AntiX GRUB menu now only shows AntiX.
My MX boot, swap and root partitions are still intact, but the new boot menu wont allow access the MX boot partition.Is there any way to change the current AntiX GRUB loader so that I can again boot both AntiX and MX ?
PS This is an older 386 Intel box ..No UEFI, only BIOS
- This topic was modified 2 years, 6 months ago by AA BB.
caprea
my AntiX 19.2 to 19.3 update
Can you please explain more clearly how you performed that ?
Normaly a
sudo update-grub
could helpex_Koo
I was wondering the same thing updated how.
” Can you please explain more clearly how you performed that ”
I did sudo apt update …followed by sudo apt upgrade
At the end of the upgrade, I got a severe warning screen after selecting “do not install grub”
The upgrade never asked “Do you want to boot AntiX only OR AntiX plus other OS in your current GRUB ?
“sudo update-grub” will only work if it searches for other boot partitions on the current drive and updates the GRUB menu.
Does it do that ??- This reply was modified 2 years, 6 months ago by AA BB.
- This reply was modified 2 years, 6 months ago by AA BB.
Xecure
After the update, the new AntiX GRUB menu now only shows AntiX.
I did sudo apt update …followed by sudo apt upgrade
Didn’t you see the same pop up in your MX linux installation? This is related to a “security bug fix” on grub a month or two ago (nothing to do with antiX or MX, it hit all linux distros at about the same time). I reported that the stupid grub installer is stupid, but most people didn’t experience any problem, so the stupid must be me.
First, which distro was managing your grub (antiX or MX)? Launch that distro and do
sudo update-grub
to update the grub list and let it find and add all available grub entries, including MX and antiX.If that doesn’t work, in antiX (or MX linux, if that was the distro that controlled grub) go to Control centre > Maintenance > Boot Repait. I would reinstall grub and then Repair grub. that should fix your problem.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure
“sudo update-grub” will only work if it searches for other boot partitions on the current drive and updates the GRUB menu.
Does it do that ??Yes. See if that fixes it. That is what it is suposed to do.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.” First, which distro was managing your grub (antiX or MX)? Launch that distro and do
sudo update-grub…to update the grub list and let it find and add all available grub entries, including MX and antiX.
”
AintX is the mangler..and after doing the above, on re-boot only AntiX shows on the GRUB menu ..no MX” If that doesn’t work, in antiX (or MX linux, if that was the distro that controlled grub) go to Control centre > Maintenance > Boot Repait. I would reinstall grub and then Repair grub.
”
Done.. but again, on re-boot only AntiX shows on the GRUB menu ..no MXWhen GParted is run under AntiX, it shows my three MX partitions: ( MX Boot, MX root and MX swap).
” I reported that the stupid grub installer is stupid”… I would strongly agree the warning screen wording should be changed
- This reply was modified 2 years, 6 months ago by AA BB.
- This reply was modified 2 years, 6 months ago by AA BB.
- This reply was modified 2 years, 6 months ago by AA BB.
Xecure
When GParted is run under AntiX, it shows my three MX partitions: ( MX Boot, MX root and MX swap).
I suspect that it was MX that managed the boot, as it is the one that has a boot partition.
I would use a live USb with antiX or MX, use the grub menu to serach for grub entries, and boot into MX. Once inside your MX Linux partition, use Boot Repair from the MX Tools to repair (maybe even reinstall grub) to the boot partition. Wasn’t that the reason you creted an MX boot partition, so that it would manage booting? Maybe it has another purpose.At least this way you should be able to boot into you MX system and have it as the main boot manager.
If this is not the purpose, then we need to figure out how to get antiX grub to detect the other grub entries.
Does anyone have a good idea?
antiX Live system enthusiast.
General Live Boot Parameters for antiX.caprea
If the above does not help one more possibility to try is,
you boot into your antiX and run from the terminalsudo grub-install /dev/sdawhere sda depends on the name of your hard disk where antiX is installed, not the partition-name (eg. sda1,sda2),just the harddisk-name.
antiX will from then on manage the boot. Might followed by sudo update-grub.
Success !…For the record, here’s what I did…
Using my Live MX USB
I was able to get to the “Boot rescue menu”
From there, I selected “Find Grub Bootloaders” which produced the following list of items:
* live USB
* Antix 19.3
* item3 (with a vague description)Next, I selected item 3, which successfully booted into my MX partition
Once inside MX, I used MX tools > Boot repair to reinstall GRUBEvery thing now works.. I can now dual boot to Antix 19.3 or MX
Many thank to all who helped me resolved this
Brian Masinick
Success !…For the record, here’s what I did…
Using my Live MX USB
I was able to get to the “Boot rescue menu”
From there, I selected “Find Grub Bootloaders” which produced the following list of items:
* live USB
* Antix 19.3
* item3 (with a vague description)Next, I selected item 3, which successfully booted into my MX partition
Once inside MX, I used MX tools > Boot repair to reinstall GRUBEvery thing now works.. I can now dual boot to Antix 19.3 or MX
Many thank to all who helped me resolved this
Congratulations, great job!
--
Brian Masinick
- You must be logged in to reply to this topic.
