Support for MX and antiX Linux distros
https://www.forum.mxlinux.org/
Unfortunately, there is no Linux installed on one of the partitions on the hard driveCharlie Brown wrote: Mon Jan 22, 2024 9:52 am If you have any other Linux installed, you can create a custom entry for Grub, then start MX "fromiso" .
Laptop, not server, etc
And does the laptop also have an Operating System? And does it boot?
This option is excluded because the virtual machine depends on the resources of the physical machine, which has poor performanceCharlie Brown wrote: Mon Jan 22, 2024 11:19 am Though this is not what you asked, you can install and use it on VirtualBox on Windows.
Yes, it contains a Windows 10 Pro operating system with a 32-bit architecture. The boot is fine and is currently booting from it. The target device contains hardware and physical components from external media ports. It is also compatible with the requirements of the target operating system.fehlix wrote: Mon Jan 22, 2024 11:36 amAnd does the laptop also have an Operating System? And does it boot?
Please don't answer with just yes or no, rather give a bit more information
about the laptop which does "not have a flash drive or any external media."
OK, based on given information here a general way toTarq wrote: Mon Jan 22, 2024 11:55 amYes, it contains a Windows 10 Pro operating system with a 32-bit architecture. The boot is fine and is currently booting from it. The target device contains hardware and physical components from external media ports. It is also compatible with the requirements of the target operating system.fehlix wrote: Mon Jan 22, 2024 11:36 amAnd does the laptop also have an Operating System? And does it boot?
Please don't answer with just yes or no, rather give a bit more information
about the laptop which does "not have a flash drive or any external media."
I did not mention the model of the device and its features because I made sure it was compatible with the system
This option is not availableCharlie Brown wrote: Mon Jan 22, 2024 12:27 pm You can just request a friend or relative to borrow their usb stick for a short time (it can be even an old one, 4GB or so) , of course when there's nothing important in it (as it will be reformatted).. Then use Rufus on Windows to write the MX iso, then boot with (after entering Bios settings and setting the Boot Sequence according to that, usb option before/above the hdd etc.. )
Bad news. I will try to install directly via the hard disk, as one of the members here said. I know that it is complicated, as is the case when installing over the network, but I think it may be less complicated. I will see what I can do.
The rules of this forum (you have read the rules, right?) require that all help requests be accompanied by a Quick System Info (QSI) report. Since you are not in a position to provide a QSI yet, the very least you can do to comply is to give use the make and model of the target laptop.I did not mention the model of the device and its features because I made sure it was compatible with the system
Ok, in case you manage to get GRUB2WIN installed.Tarq wrote: Mon Jan 22, 2024 6:58 pm ...I will try to install directly via the hard disk, as one of the members here said. I know that it is complicated, as is the case when installing over the network, but I think it may be less complicated. I will see what I can do.
Code: Select all
menuentry "MX 23.2 Libretto manual Frugal Install" {
insmod part_msdos
insmod fat
search --no-floppy --set=root --label MX-linux
linux /antiX/vmlinuz bdir=antiX blab=MX-Linux quiet splasht nosplash
initrd /antiX/initrd.gz
}
Hi there,Tarq wrote: Mon Jan 22, 2024 6:50 pm I did not mention the model of the device and its features because I made sure it was compatible with the system
I trust members of the Linux community, but you ask about the make and model of the device and do not ask about the device specifications, and I reserve that until security measures are takenj2mcgreg wrote: Mon Jan 22, 2024 7:04 pm @Tarq
Until you tell us the make and model of your laptop, there's very little if anything we can help you with.
Are Linux MX forum rules ignoring cybersecurity?j2mcgreg wrote: Mon Jan 22, 2024 7:28 pm @Tarq wrote:The rules of this forum (you have read the rules, right?) require that all help requests be accompanied by a Quick System Info (QSI) report. Since you are not in a position to provide a QSI yet, the very least you can do to comply is to give use the make and model of the target laptop.I did not mention the model of the device and its features because I made sure it was compatible with the system
Tarq wrote: Mon Jan 22, 2024 9:49 am good greeting
I do not have a flash drive or any external media. What are my options for installation?
The QSI report is automatically scrubbed of all personal information.Tarq wrote: Wed Jan 24, 2024 11:44 amAre Linux MX forum rules ignoring cybersecurity?j2mcgreg wrote: Mon Jan 22, 2024 7:28 pm @Tarq wrote:The rules of this forum (you have read the rules, right?) require that all help requests be accompanied by a Quick System Info (QSI) report. Since you are not in a position to provide a QSI yet, the very least you can do to comply is to give use the make and model of the target laptop.I did not mention the model of the device and its features because I made sure it was compatible with the system
We can get the device specifications from the manufacturers' websites.Tarq wrote: Wed Jan 24, 2024 11:41 amI trust members of the Linux community, but you ask about the make and model of the device and do not ask about the device specifications, and I reserve that until security measures are takenj2mcgreg wrote: Mon Jan 22, 2024 7:04 pm @Tarq
Until you tell us the make and model of your laptop, there's very little if anything we can help you with.
Yes, dear, but I am currently checking for device and software updates, etc., so I will provide you with the device specifications until I finish, do not worry.j2mcgreg wrote: Wed Jan 24, 2024 12:07 pmWe can get the device specifications from the manufacturers' websites.Tarq wrote: Wed Jan 24, 2024 11:41 amI trust members of the Linux community, but you ask about the make and model of the device and do not ask about the device specifications, and I reserve that until security measures are takenj2mcgreg wrote: Mon Jan 22, 2024 7:04 pm @Tarq
Until you tell us the make and model of your laptop, there's very little if anything we can help you with.
Why did you ask for three partitions, because I think the need for two partitions makes sense? A partition containing ISO files after burning and extraction, and a partition for the purpose of exchanging the hard disk with random memory during intense activity, as the raw ISO file is now located in a random partition. Why should I dedicate a section to it?1st step:
OK, based on given information here a general way to
Install and Boot MX Linux from a 32bit based laptop with Windows Operating system
with legacy BIOS/MBR bootloader without any external boot media:
1st step:
* Prepare the target laptop: by creating at minimum 2 partitions:
a FAT-32 about 2-3-GB to hold the MX Linux ISO
and a
2nd one to be used for root-partition, choose simply FAT32 with windows,
the partition will be reformatted anyway during installation.
You can create more partitions if needed for extra /home and swap.
In post #1, you asked for "installation".Tarq wrote: Sat Jan 27, 2024 6:50 amWhy did you ask for three partitions, because I think the need for two partitions makes sense? A partition containing ISO files after burning and extraction, and a partition for the purpose of exchanging the hard disk with random memory during intense activity, as the raw ISO file is now located in a random partition. Why should I dedicate a section to it?1st step:
OK, based on given information here a general way to
Install and Boot MX Linux from a 32bit based laptop with Windows Operating system
with legacy BIOS/MBR bootloader without any external boot media:
1st step:
* Prepare the target laptop: by creating at minimum 2 partitions:
a FAT-32 about 2-3-GB to hold the MX Linux ISO
and a
2nd one to be used for root-partition, choose simply FAT32 with windows,
the partition will be reformatted anyway during installation.
You can create more partitions if needed for extra /home and swap.
Curious about this, I gave it a shot with a VM. Nothing fancy, Just:fehlix wrote: Mon Jan 22, 2024 1:01 pm OK, based on given information here a general way to
Install and Boot MX Linux from a 32bit based laptop with Windows Operating system
with legacy BIOS/MBR bootloader without any external boot media:
1st step:
* Prepare the target laptop: by creating at minimum 2 partitions:
a FAT-32 about 2-3-GB to hold the MX Linux ISO
and a
2nd one to be used for root-partition, choose simply FAT32 with windows,
the partition will be reformatted anyway during installation.
Yes, when booting from iso you need to pass a fromiso if booting from iso,DukeComposed wrote: Sat Jan 27, 2024 9:09 amCurious about this, I gave it a shot with a VM. Nothing fancy, Just:fehlix wrote: Mon Jan 22, 2024 1:01 pm OK, based on given information here a general way to
Install and Boot MX Linux from a 32bit based laptop with Windows Operating system
with legacy BIOS/MBR bootloader without any external boot media:
1st step:
* Prepare the target laptop: by creating at minimum 2 partitions:
a FAT-32 about 2-3-GB to hold the MX Linux ISO
and a
2nd one to be used for root-partition, choose simply FAT32 with windows,
the partition will be reformatted anyway during installation.
The ISO uncompresses and boots, but quickly fails during startup with the error:
- Installed Win10 through installation wizard
- Shrunk the NTFS partition by as much as suggested in diskmgmt.msc and created new simple volume
- Copied an MX-23 ISO and "EasyBCD 2.4.exe" to the new E:\ drive (Version 2.4 is just what I had laying around.)
- Installed EasyBCD, added new NeoSmart ISO entry
- Rebooted and chose the NeoSmart entry
Fatal Error
Could not find file antiX/linuxfs
Searched devices: /dev/sr0
Searched types: usb,cd
All block devices: /dev/sr0 /dev/sda3 /dev/sda2 /dev/sda1 /dev/sda
It then suggests I contact BitJam and gives me two options: p = power off or r = reboot.
I've tried this with both the "Load from memory" and "Read from disk" options in EasyBCD, so this technique may not be as straightforward as originally hoped. Then again, this is just one data point. It may function differently on a real machine and not a VM with 8GB of RAM.
The "MX Installer" creates the root partition, e.g on a ext4 filesystem,Tarq wrote: Sat Jan 27, 2024 4:57 pm Why should the ISO file be in its basic format on one of the partitions, then the program is burned in one of the partitions, then the kernel is in one of the partitions? What I know is that I need to run a partition that includes only the root
Enriching information, but the answer did not match the question, perhaps a misunderstanding on my part. In any case, I cannot focus and engage in a discussion at the moment. I do not think this section is appropriate for asking cognitive and conceptual questions. It is a problem solving section, so when I finish the tasks that need to be done and get rid of the stress, I free up and put a topic in the appropriate section.Not sure, whether I answered you question and this was what you asked / wanted to know.
If you need guidance for this see MX Linux User Manual section 2.2, Creating bootable medium. On Windows, it is recommended to use either balena Etcher or Rufus to write the MX Linux ISO to your USB drive. Etcher is the hands-down go-to choice for PC novices.Tarq wrote: Sun Jan 28, 2024 11:18 pm Can you provide me with a program or tool to burn the operating system image with 32 and 64 bit Windows?
Maybe this helps to get it done without an external boot medium:Tarq wrote: Sun Jan 28, 2024 11:18 pm Can you provide me with a program or tool to burn the operating system image with 32 and 64 bit Windows?
Code: Select all
sudo minstall --braveYes, I have the problem now in a physical environmentThe ISO uncompresses and boots, but quickly fails during startup with the error:
Fatal Error
Could not find file antiX/linuxfs
Searched devices: /dev/sr0
Searched types: usb,cd
All block devices: /dev/sr0 /dev/sda3 /dev/sda2 /dev/sda1 /dev/sda
It then suggests I contact BitJam and gives me two options: p = power off or r = reboot.
OK, maybe give some more details.Tarq wrote: Tue Jan 30, 2024 9:13 amYes, I have the problem now in a physical environmentThe ISO uncompresses and boots, but quickly fails during startup with the error:
Fatal Error
Could not find file antiX/linuxfs
Searched devices: /dev/sr0
Searched types: usb,cd
All block devices: /dev/sr0 /dev/sda3 /dev/sda2 /dev/sda1 /dev/sda
It then suggests I contact BitJam and gives me two options: p = power off or r = reboot.
Boot from ISODo you boot from the ISO or did you extracted the ISO? What method was used to get booted?
I've tried booting through a WinPE window but it doesn't show the required files other than this directive https://www.youtube.com/watch?v=HoMejK_yjLMDo you boot from the ISO or did you extracted the ISO? What method was used to get booted?
OK, so you managed to boot the ISO at least to the LiveBoot system on the ISO, but next boot step failed.Tarq wrote: Tue Jan 30, 2024 6:49 pmBoot from ISODo you boot from the ISO or did you extracted the ISO? What method was used to get booted?
EasyBCDWhat method was used to get to this stage. EasyBCD, GRUB2WIN or something else?
Where is the live boot menu located? Do you mean on the boot manager screen? How do I add the path? Do you mean through the direct boot command line screen or through one of the graphical interface options in the easy bcd program? Be precise in describing everything because sometimes I have no idea about a certain component.Do you get Live-Boot menu? If yes, add this two boot parameter:
fromiso="path-to-the-iso"
and
blab="Label-of-the-file-system"
Correction of information with reservation:Tarq wrote: Wed Jan 31, 2024 11:05 pm Let's summarize what happened theoretically and not practically:
An exact distribution image was added via the ISO window in the easybcd program in order for the program to add the entry for booting the system directly from the hard disk into the boot list. This succeeded. After that, an attempt was made to boot via live boot mode, which is the default mode from developers in most Linux systems and not the normal boot, the live system responsible for running live boot mode was unable to find the ISO file. The easybcd program was supposed to only show the entry of the boot option in the boot menu, since the success of this task was considered impressive and good progress for the program. It should have played the role of boot loader on behalf of grub, but it did not do so. It should have provided the live system with information about where to find the ISO, since that is the function of the boot loader, and this did not happen. This may be due to a glitch, error, or settings adjustment.
Code: Select all
BOOTLOADERS:
lilo ----------- legacy bootloader good for smaller disks
grub ----------- boots most operating systems
systemd-boot---- systemd bootloader
rEFIt (redEFIt)-- open source bootloader for UEFI
syslinux ---------includes isolinux and PXElinux and boots most systems, especially usbsTesting this out on a VM, the blab argument didn't work for me. It may have been because the label of the partition was "NEW VOLUME". Using blab="NEW VOLUME" didn't work, so I ended up booting the ISO normally just to run blkid and get the UUID of the partition. After shrinking the NTFS partition of the VM, creating a new FAT32 partition from the unused space, and I renamed the MX-23 ISO to "MX.iso" for brevity. After configuring the EasyBCD boot menu to load the ISO with the "Run from disk" option, I added "fromiso=MX.iso buuid=C608-DE1A" to the boot arguments and that allowed the ISO to finally start.fehlix wrote: Wed Jan 31, 2024 4:26 am Do you get Live-Boot menu? If yes, add this two boot parameter:
fromiso="path-to-the-iso"
and
blab="Label-of-the-file-system"
Followup: In Windows, run System Information, select Components > Storage > Drives. The UUID string needed for the buuid argument will match the partition's "Volume Serial Number", but without any hyphens.DukeComposed wrote: Thu Feb 01, 2024 12:55 am The concern I have about this approach is how to get the UUID of the partition while still running Windows.
Good, you have confirmed that it works.DukeComposed wrote: Thu Feb 01, 2024 12:55 amTesting this out on a VM, the blab argument didn't work for me. It may have been because the label of the partition was "NEW VOLUME". Using blab="NEW VOLUME" didn't work, so I ended up booting the ISO normally just to run blkid and get the UUID of the partition. After shrinking the NTFS partition of the VM, creating a new FAT32 partition from the unused space, and I renamed the MX-23 ISO to "MX.iso" for brevity. After configuring the EasyBCD boot menu to load the ISO with the "Run from disk" option, I added "fromiso=MX.iso buuid=C608-DE1A" to the boot arguments and that allowed the ISO to finally start.fehlix wrote: Wed Jan 31, 2024 4:26 am Do you get Live-Boot menu? If yes, add this two boot parameter:
fromiso="path-to-the-iso"
and
blab="Label-of-the-file-system"
The concern I have about this approach is how to get the UUID of the partition while still running Windows.
In case the boot method used by EasyBCD won't show you the LiveBoot menu, you may need to find the place within EasyBCD to add those boot parameter. Maybe @DukeComposed can give some hints.Tarq wrote: Wed Jan 31, 2024 10:30 pmWhere is the live boot menu located? Do you mean on the boot manager screen? How do I add the path? Do you mean through the direct boot command line screen or through one of the graphical interface options in the easy bcd program? Be precise in describing everything because sometimes I have no idea about a certain component.Do you get Live-Boot menu? If yes, add this two boot parameter:
fromiso="path-to-the-iso"
and
blab="Label-of-the-file-system"
I was curious to know if this method would work without having to shrink the C: partition and create a new one. So I moved the iso to C:\MX.iso and replaced the EasyBCD boot menu entry to use it. I also ended up having to give C: a volume label in Explorer. I chose "X" because it's short.fehlix wrote: Thu Feb 01, 2024 5:06 am Good, you have confirmed that it works.
Don't use spaces in the file system label. Just re-label using Windows file manager.
Code: Select all
quiet splasht nosplashCode: Select all
quiet splasht nosplash fromiso=MX.iso blab="X"Thanks, for the details. Yes, and note, when using full path remember to use forward slash likeDukeComposed wrote: Thu Feb 01, 2024 6:01 amI was curious to know if this method would work without having to shrink the C: partition and create a new one. So I moved the iso to C:\MX.iso and replaced the EasyBCD boot menu entry to use it. I also ended up having to give C: a volume label in Explorer. I chose "X" because it's short.fehlix wrote: Thu Feb 01, 2024 5:06 am Good, you have confirmed that it works.
Don't use spaces in the file system label. Just re-label using Windows file manager.
I then changed the normal boot arguments from
toCode: Select all
quiet splasht nosplash
It loaded the MX live session as expected. So installing MX from the ISO doesn't require a FAT32 partition. It can also work from a regular old NTFS-formatted C: drive if you have permissions to (1) write the ISO to C:\, though I'm sure storing the ISO elsewhere is possible, (2) install and run EasyBCD to edit the bootloader, and (3) set a simple volume label on that C: drive.Code: Select all
quiet splasht nosplash fromiso=MX.iso blab="X"
Code: Select all
fromiso=/iso/MX.iso
Both "fromiso=MX.iso" and "fromiso=/MX.iso" work when MX.iso is in C:\. I imagine "fromiso=/Users/username/Downloads/MX-whatever.iso" is just as viable a path, but it's longer to type and, let's be honest here, you need Administrator permissions to disable SecureBoot and replace the bootloader with EasyBCD, so it doesn't really matter if you're saving the ISO to a non-privileged path.fehlix wrote: Thu Feb 01, 2024 6:05 am Thanks, for the details. Yes, and note, when using full path remember to use forward slash likeCode: Select all
fromiso=/iso/MX.iso
OK, here is the trick: When having the ISO on the same drive/disk (like C:\ on the first disk)DukeComposed wrote: Thu Feb 01, 2024 6:26 am I haven't actually installed MX this way, but I can at least get to the MX live session. I have to presume that the installer can still unsquash the linuxfs file to a newly-repartitioned drive even though the ISO itself ceases to exist on disk as soon as the new partition table gets created. It would be tragic to have done all this work solving this silly problem and get stuck needing the ISO to finish installing the image that exists on the ISO.
Code: Select all
sudo minstall --brave
Tarq wrote: Wed Jan 31, 2024 10:30 pmWhere is the live boot menu located? Do you mean on the boot manager screen? How do I add the path? Do you mean through the direct boot command line screen or through one of the graphical interface options in the easy bcd program?Do you get Live-Boot menu? If yes, add this two boot parameter:
fromiso="path-to-the-iso"
and
blab="Label-of-the-file-system"
Be precise in describing everything because sometimes I have no idea about a certain component.
OK, here's the first way I've found to replace Windows on a machine with MX Linux without using external media.fehlix wrote: Thu Feb 01, 2024 7:11 am In the case of same disk for boot-disk and installation target disk,
do start the installer from terminal command line like thisAnd may be important for legacy BIOS-boot (= none UEFI boot) do first not install GRUB to MBR of the WIndows Boot Disk whre C:\ is located but select PBR (Partition Boot Record) of the "/"-root partition. B/c in case of any error and grub boot loader on MBR would fail to boot, you would also not be able to boot into Windows and also into the ISO anymore using EasyBCD.Code: Select all
sudo minstall --brave
So, after installing GRUB to PBR, use EasyBCD again and create Windows Boot Menu entry for booting from the root "Partition".
You can later use MX Boot Repair to install GRUB onto MBR, but better do first backup the Windows MBR,which can be done also with MX Boot Repair.
Code: Select all
TARGET=/media/demo/rootMX23
for i in /dev /dev/pts /proc /sys
do
test -d ${TARGET}$i || mkdir -p ${TARGET}$i
mount --bind $i ${TARGET}$i
done
Thanks, for trying this out.DukeComposed wrote: Fri Feb 02, 2024 7:33 am OK, here's the first way I've found to replace Windows on a machine with MX Linux without using external media.
That would also have been useful. This experiment was only performed on a VM with 8GB of RAM, so it may have been possible to attempt this method, though I recall setting the "Load into memory" option in EasyBCD, so there's no knowing exactly how much RAM was left after invoking the live session. Optimizations like this are certainly possible and may be necessary if anyone is unfortunate enough to need them.fehlix wrote: Fri Feb 02, 2024 8:18 amThanks, for trying this out.DukeComposed wrote: Fri Feb 02, 2024 7:33 am OK, here's the first way I've found to replace Windows on a machine with MX Linux without using external media.
Note in case enough RAM like 3-4GB++ is available, one can use the "toram" bootparameter,
How do I display the boot loader command line?At the GRUB boot menu, add the arguments "fromiso=MX.iso blab=X". Hit Enter.
Add the live grub menu menu: You'll find a line explaining how to open the grub menu editor: Now add the desired boot parameter at the end of the line starting with "linux..."Tarq wrote: Sun Feb 11, 2024 9:24 pmHow do I display the boot loader command line?At the GRUB boot menu, add the arguments "fromiso=MX.iso blab=X". Hit Enter.
I had a confusion, as I think I am dealing so far with two components: the name of the partition on the hard disk and the name of the system image file. What do you mean in the third configuration, 'File System Name', where I know the designation of the file system type?Don't use spaces in the file system label. Just re-label using Windows file manager.
Maybe post the question with more context, b/c that's a long thread already and you missed quoting properly with reference to the post.Tarq wrote: Mon Feb 12, 2024 8:28 amI had a confusion, as I think I am dealing so far with two components: the name of the partition on the hard disk and the name of the system image file. What do you mean in the third configuration, 'File System Name', where I know the designation of the file system type?Don't use spaces in the file system label. Just re-label using Windows file manager.
PS: Don't send me PM to answer questions. Please post here, doesn't matter if you feel it's a silly question or not.fehlix wrote: Mon Feb 12, 2024 9:18 amMaybe post the question with more context, b/c that's a long thread already and you missed quoting properly with reference to the post.Tarq wrote: Mon Feb 12, 2024 8:28 amI had a confusion, as I think I am dealing so far with two components: the name of the partition on the hard disk and the name of the system image file. What do you mean in the third configuration, 'File System Name', where I know the designation of the file system type?Don't use spaces in the file system label. Just re-label using Windows file manager.
Esp. post:
lsblk -f
and the file path (path including file name of the iso-file, and on what partition is the iso-file saved on.
The simplest would be this:Tarq wrote: Wed Feb 21, 2024 11:44 am Can you help me on how to access GRUB settings through the Grub2win program?
Until we provide you with what you want, look at the attachment. It contains commands, but I am thinking why I have to direct the program to all the important files to start booting and operating, and what is the point then of attaching an ISO file to the program, if that is the case? I think I am stuck on a screen stating that the grub2win program is unable to see the file. The image of the initial system, not access to the kernel, etc. I am trying to understand what is happening theoretically so that it will be easier for me in practicefehlix wrote: Wed Feb 21, 2024 1:49 pmThe simplest would be this:Tarq wrote: Wed Feb 21, 2024 11:44 am Can you help me on how to access GRUB settings through the Grub2win program?
* Locate the grub.cfg file (which is a text file), and post the content of the file.
the directory might be something like c:\grub (or similar) where you look for the file.
* Next, post the file name of the MX linux iso file
and the full path where the iso-file is located.
With this information provided we may be able to proceed.
Good, they do provide a generic way to boot from the iso.Tarq wrote: Wed Feb 21, 2024 3:37 pm --grubwork--cfg.txtUntil we provide you with what you want, look at the attachment. It contains commands, but I am thinking why I have to direct the program to all the important files to start booting and operating, and what is the point then of attaching an ISO file to the program, if that is the case? I think I am stuck on a screen stating that the grub2win program is unable to see the file. The image of the initial system, not access to the kernel, etc. I am trying to understand what is happening theoretically so that it will be easier for me in practicefehlix wrote: Wed Feb 21, 2024 1:49 pmThe simplest would be this:Tarq wrote: Wed Feb 21, 2024 11:44 am Can you help me on how to access GRUB settings through the Grub2win program?
* Locate the grub.cfg file (which is a text file), and post the content of the file.
the directory might be something like c:\grub (or similar) where you look for the file.
* Next, post the file name of the MX linux iso file
and the full path where the iso-file is located.
With this information provided we may be able to proceed.
Note: I am working on setting up two devices simultaneously, one of them via easybcd and grub2win, due to the inability to open the program interface, and I preferred that.
linuxmint-21.3-xfce-64bitfehlix wrote: Wed Feb 21, 2024 1:49 pmThe simplest would be this:Tarq wrote: Wed Feb 21, 2024 11:44 am Can you help me on how to access GRUB settings through the Grub2win program?
* Locate the grub.cfg file (which is a text file), and post the content of the file.
the directory might be something like c:\grub (or similar) where you look for the file.
* Next, post the file name of the MX linux iso file
and the full path where the iso-file is located.
With this information provided we may be able to proceed.
Tarq wrote: Wed Feb 21, 2024 4:36 pmNote: The necessity of adjusting distances, etc., has not been ignored. It is just a theoretical understanding before applicationfehlix wrote: Wed Feb 21, 2024 1:49 pmThe simplest would be this:Tarq wrote: Wed Feb 21, 2024 11:44 am Can you help me on how to access GRUB settings through the Grub2win program?
* Locate the grub.cfg file (which is a text file), and post the content of the file.
the directory might be something like c:\grub (or similar) where you look for the file.
* Next, post the file name of the MX linux iso file
and the full path where the iso-file is located.
With this information provided we may be able to proceed.
So you seem to try to boot somehow linux-mint.Tarq wrote: Wed Feb 21, 2024 4:36 pmlinuxmint-21.3-xfce-64bitfehlix wrote: Wed Feb 21, 2024 1:49 pmThe simplest would be this:Tarq wrote: Wed Feb 21, 2024 11:44 am Can you help me on how to access GRUB settings through the Grub2win program?
* Locate the grub.cfg file (which is a text file), and post the content of the file.
the directory might be something like c:\grub (or similar) where you look for the file.
* Next, post the file name of the MX linux iso file
and the full path where the iso-file is located.
With this information provided we may be able to proceed.
D:\
D:\boot\grub
Storage unit serial number FE3EEDEA
You have what you want, but Felix, I added the ISO file in a field where everything is supposed to be automatic, not manualfehlix wrote: Wed Feb 21, 2024 5:15 pmSo you seem to try to boot somehow linux-mint.Tarq wrote: Wed Feb 21, 2024 4:36 pmlinuxmint-21.3-xfce-64bitfehlix wrote: Wed Feb 21, 2024 1:49 pm
The simplest would be this:
* Locate the grub.cfg file (which is a text file), and post the content of the file.
the directory might be something like c:\grub (or similar) where you look for the file.
* Next, post the file name of the MX linux iso file
and the full path where the iso-file is located.
With this information provided we may be able to proceed.
D:\
D:\boot\grub
Storage unit serial number FE3EEDEA
And the grub.cfg you probably got from extracted linux-mint ISO.
It looks like you extracted the ISO at drive D:
Maybe it can be made that it work, but at least quite a bit is missing, b/c you haven't told grub2win what partition the iso is on.
And not sure they do support to boot from an extracted iso.
Suggest to try MX-Linux iso to boot which can be booted either from iso
and also from extracted iso.
Note: the file name of an iso normally also has an extension like .iso
and serial number FE3EEDEA may or not provide the UUID.
You may consider to give more details, otherwise I'm afraid, we can give only generic comments.
I don't have currently grub2win installed, so you might get some support for GRUB2WIN on their support forum.Tarq wrote: Wed Feb 21, 2024 5:28 pmYou have what you want, but Felix, I added the ISO file in a field where everything is supposed to be automatic, not manualfehlix wrote: Wed Feb 21, 2024 5:15 pmSo you seem to try to boot somehow linux-mint.Tarq wrote: Wed Feb 21, 2024 4:36 pm
linuxmint-21.3-xfce-64bit
D:\
D:\boot\grub
Storage unit serial number FE3EEDEA
And the grub.cfg you probably got from extracted linux-mint ISO.
It looks like you extracted the ISO at drive D:
Maybe it can be made that it work, but at least quite a bit is missing, b/c you haven't told grub2win what partition the iso is on.
And not sure they do support to boot from an extracted iso.
Suggest to try MX-Linux iso to boot which can be booted either from iso
and also from extracted iso.
Note: the file name of an iso normally also has an extension like .iso
and serial number FE3EEDEA may or not provide the UUID.
You may consider to give more details, otherwise I'm afraid, we can give only generic comments.
Code: Select all
menuentry "ISO-Boot MX-Linux.iso" {
iso_path=/iso/MX-snapshot.iso
export iso_path
# change below if desired
# bootoptions="kbd=de kbvar=nodeadkeys kbopt=caps:none lang=de tz=Europe/Amsterdam"
insmod part_gpt
insmod part_msdos
insmod ext2
insmod exfat
insmod ntfs
insmod probe
insmod loopback
# use this to search for the full iso_path
search --no-floppy --file --set=root $iso_path
probe -u $root --set=buuid
loopback loop $iso_path
linux (loop)/antiX/vmlinuz buuid=${buuid} fromiso=${iso_path} quiet splasht nosplash ${bootoptions}
initrd (loop)/antiX/initrd.gz
}
Code: Select all
demo@mx1:~
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
demo@mx1:~
$ uname -a
Linux mx1 6.1.0-17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux
Code: Select all
demo@mx1:~
$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /live/linux
sda
├─sda1 ntfs النظام 20
├─sda2 ntfs Windows 10
├─sda3
├─sda4 xfs rootMX23
├─sda5 ntfs Files Photos and More
│ └─ventoy 0 100% /live/boot-dev
├─sda6 ntfs Windows 10
└─sda7 ntfs Files Photos and More
sdb
├─sdb1 vfat FAT32 VENTOY
└─sdb2 vfat FAT16 VTOYEFI
sr0The explanation is in the link attached to this postBuck Fankers wrote: Thu Mar 14, 2024 11:43 am Nice, congratulation!
You could now post your steps for anyone else, that may want at some point do the same.