Changing from XFCE 64bit to Fluxbox 64bit  [Solved]

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
pete67
Posts: 146
Joined: Sun Apr 17, 2022 8:26 am

Re: Changing from XFCE 64bit to Fluxbox 64bit  [Solved]

#11 Post by pete67 »

@Charlie Brown, well MX-23.1 is installed and I could restore my programs as before, but Grub doesn't recognize my Win11 and so I cannot but it but this is another theme and I will now search the forum for a solution.

Thanks until here. You helped me very well.

Charlie Brown

Re: Changing from XFCE 64bit to Fluxbox 64bit

#12 Post by Charlie Brown »

Glad to hear it's ok now.

The reason for that Windows issue is (in general), i.e. Windows was installed when it was set to Uefi and later you install any Linux when it's Legacy .. (or the vice versa) .. etc..

In the worst case we can create a custom entry.

Still nothing to lose to manually:

Code: Select all

sudo update-grub

User avatar
pete67
Posts: 146
Joined: Sun Apr 17, 2022 8:26 am

Re: Changing from XFCE 64bit to Fluxbox 64bit

#13 Post by pete67 »

Code: Select all

sudo update grub
brings

Code: Select all

$ sudo update-grub
[sudo] Passwort für tuxpete:    
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-6.6.7-1-liquorix-amd64
Found initrd image: /boot/initrd.img-6.6.7-1-liquorix-amd64
Found linux image: /boot/vmlinuz-6.5.0-1mx-ahs-amd64
Found initrd image: /boot/initrd.img-6.5.0-1mx-ahs-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Adding boot menu entry for EFI firmware configuration
done
So I think we must try the 40_custom version

As I wrote to fehlix in this new thread viewtopic.php?t=78641

there I wrote:
To edit

/etc/grub.d/40_custom

and insert under the

exec tail -n +3 $0

the following:

Code: Select all

menuentry 'Windows 11 Pro' {
search --fs-uuid --set=root $uuid
chainloader /EFI/Microsoft/Boot/bootmgfw.efi


Additionally I've looked up the UUIDs on my system with "blkid"

Code: Select all

$ blkid
/dev/nvme0n1p2: LABEL="NVMe-SSD_980_Games" BLOCK_SIZE="512" UUID="3860FBFB60FBBE26" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="94094084-1aa0-47a4-a911-a3b485a99a5f"
/dev/sdd1: LABEL="Samsung_860_EVO_SATA-SSD" BLOCK_SIZE="512" UUID="7C50627A50623B52" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="17c6efda-f458-4a4b-8aaf-bd5159d5dbbe"
/dev/sdb1: LABEL_FATBOOT="Austausch" LABEL="Austausch" UUID="CB1B-933E" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="da5b4055-78d9-11ed-91fc-1831bf25e70a"
/dev/sdc2: LABEL="Samsung_870_QVO_SATA-SSD" BLOCK_SIZE="512" UUID="1C4C54294C53FFC6" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="e0c1e71a-bc60-4e17-874b-41e3820eb3e6"
/dev/nvme1n1p2: LABEL="NVMe_SSD_Windows" BLOCK_SIZE="512" UUID="068CFCA08CFC8C05" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="33ac05b4-5a9a-4029-9dd4-f5446e42fea5"
/dev/nvme1n1p3: BLOCK_SIZE="512" UUID="CC08738808736FF6" TYPE="ntfs" PARTUUID="1f5388da-d72d-427c-91b1-25bc86c114be"
/dev/sda2: LABEL="rootMX23" UUID="4e77752f-8b89-414c-be14-fa342c0915bf" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="ef2f731e-22d6-49d8-a106-ff24d2947a3e"
/dev/sda1: LABEL_FATBOOT="EFI-SYSTEM" LABEL="EFI-SYSTEM" UUID="32DC-956D" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="c5071425-43ab-48c7-bc57-4b64f5ce1320"

So I assume I could try it with the UUID "068CFCA08CFC8C05" but I'm unsure how to name the chainloader command due to the target "under Program Files (x86)/AOMEI/bootmgfw.efi"

But if that is not possible to take for the chainloader command I assume to take the standard under

Code: Select all

chainloader /EFI/Microsoft/Boot/bootmgfw.efi

so that I can boot Win11 again and than I can restore that part of AOMEI Backupper again under Windows what will not harm MX Grub.

Post Reply

Return to “MX Help”