- This topic has 12 replies, 3 voices, and was last updated Jul 22-5:26 pm by stevesr0.
-
Posts
-
stevesr0
I just installed antiX19 to its own ssd as a dual boot with Windows 10. Grub2 is installed to the ESP partition on the antiX19 drive and the windows bootmanager is on the drive with the windows OS.
It works, except the presence of two selections that launch antiX. in /etc/fstab, they appear to be the same os BUT have different boot files (one is grub and the other is boot).
The boot file (associated with a label of UEFI OS) seems to be the name of the “fallback” file, but it boots to antiX. The other (with a label of AntiX19) gets stops after displaying some ACPI errors.
But the UEFI OS choice displays the same errors and then continues to boot to a normal functioning desktop.
Not sure how to analyze further.
Appreciate suggestions.
stevesr0
- This topic was modified 2 years, 11 months ago by stevesr0.
Xecure
I am no expert on EFI stuff. Mount the EFI partition in antiX and have a look at the folders there. There should only be one antiX19 (or antiX19.2) folder there, with the corresponding EFI information.
Could your system have both UEFI and Legacy boot options enabled (some computers have both set at the same time) and that is why both options appear in the BIOS?
In the worst case, you could reinstall GRUB, but leave that for last, until someone with more knowledge can come up with a better idea.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Thanks Xecure,
I didn’t think to do that.
Only one is named antix19; the other has a generic sounding name UEFI OS, which I think is linked to the (built in?) fallback boot.efi file. It is peculiar that the fallback launches Antix19 rather than Win10, but that might be because the Win10 is set lower in the HD priority list than the UEFI OS choice.
What is also puzzling is that the Antix19 choice when specified manually stops with errors, although the same errors DON’T stop the UEFI OS boot.
I will check those directories and follow up.
stevesr0
Hi Xecure,
On the ssd that has antix installed, there is an ESP partition mounted at /boot/efi. Within this is a single subdirectory /EFI.
Within the /EFI subdirectory, there are two (sub)subdirectories. One is named antiX19 and the other is named BOOT.Within the antiX19 subdirectory is a subdirectory named GRUBX64.EFI. Within, the BOOT subdirectory is a subdirectory named BOOTX64.EFI.
The 4 files within these two subdirectories have identical names, date and time modified (1969) and sizes.
The names are /data, .reloc, .text and mods. Each file is only a small number of kilobytes.
On the other ssd, there is an ESP partition with Boot, EFI and System Volume information directories and two files (bootmgr and BOOTNXT).
Within the EFI directory are two directories (Boot and Microsoft). The /Boot directory is identical to the /EFI/Microsoft/Boot directory, while the /EFI/Boot directory houses (only) a bootx64.efi folder of 1.5 Megabytes. Within this folder are 7 files and one directory.Thus the two efi folders on the linux installation are small and identical, while the efi folder for windows which was already installed when I purchased the computer is different and much larger.
If the two apparently identical efi subfolders on the linux drive are identical, I am puzzled why one boots fine and the other stops early in the boot.
But, except for a cursor which jumps around, I am happy that the install seems to work.
stevesr0
- This reply was modified 2 years, 11 months ago by stevesr0.
Xecure
Very strange. I also have a BOOT option in my UEFI system, but it takes me to a EFI shell. antiX19 entry takes me to antiX without a problem. My only guess is that somehow the partition name changed after installing grub to ESP and makes it impossible to launch antiX with the correct entry.
If you are happy how everything is working launching from BOOT/UEFI BIOS, the leave it as is.
If you would like to try to fix the antiX entry, you could do so from your installed antiX system. In Control Centre, go to Maintenance tab and launch Boot Repair. You could try Fixing Grub first, or reinstalling to ESP.
This ESP reinstallation should only affect the antiX19 option in your EFI partition, so no risk should come to your working BOOT option.Good thing that everything is working with the BOOT option, otherwise you would have to try fixing grub from a live system.
Best Regards.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure
But, except for a cursor which jumps around, I am happy that the install seems to work.
If you cannot solve that by changing Control Centre > Hardware > Mouse COnfiguration options, you could open a new thread and we could try to take a look at that.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.I have some questions about the GRUB install performed by AntiX. I understand that a grubx64.efi file is produced and wonder what other files are normally present in the /boot/efi/EFI/Antix subdirectory? My subdirectory has only the grubx64.efi file and is 128 kB. In the file manager, when I click on the file, a window opens with 4 “files” displayed (.text, mods, .reloc and .data. The grub.cfg file is located in /boot/grub/.
Wondering if this suggests why I can’t successfully boot from the Antix19 menu choice.
Thanks for comments and references.
stevesr0
- This reply was modified 2 years, 11 months ago by stevesr0.
dolphin_oracle
not seeing the errors its hard to diagnose, but do you have secure boot disabled?
Hi dolphin_oracle,
Yes, secure boot is disabled.
AntiX boots fine – but only when I select UEFI OS to boot from rather than AntiX19. As I mentioned in a previous post in this thread, the two subdirectories /boot/efi/EFI/antiX19/grubx64.efi and /boot/efi/EFI/BOOT/BOOTX64.efi seem to be identical, yet the antix19 stops after displaying the errors (see photo below), while BOOT goes on to boot normally.
(I assume that UEFI OS is the “fallback” choice and is linked to the /boot/efi/EFI/BOOT directory.)
Both files are 128 kB in size and contain four “files” as displayed by file manager (although) neither is characterized as directories according to their attributes.
The four “files” are titled .reloc, .text. mods and .data.
I checked my other dual booting computer – running Antix17 and Windows 10, and the grub entry is the same, with one exception. In the new computer, the entry for grubx64.efi is in LOWER case, but in efibootmgr -v, it is displayed in UPPER case. In the older system, both entries are lower case.
(I was told that FAT will ignore differences in case, so just changing the name of the file to UPPER case wouldn’t make the AntiX19 entry boot.Also, there is no boot item in efibootmgr, although there is a bootx64.efi file in /boot/efi/EFI/BOOT/.
Obviously, I don’t understand the workings of grub install to make sense of this <g>.
I would love to know what antiX uses to install grub, as that would give me something specific to study further.
Appreciate any thoughts, comments, suggestions or references.
stevesr0
Attachments:
Xecure
Even if they are the same size, the contents are clearly different, as one works and the other doesn’t. If you can fix/reinstall grub to ESP, maybe this would solve it.
The ACPI Errors you posted seem to be related to the kernel having trouble communicating with a device. I tried searching for the error and it could be related to a driver issue (some post say it is touchpad, others power management). Maybe a newer kernel may solve this, but I will let someone with more experience answer this.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.? Solved.
I remembered that I had to add a special term to control video in the install (nomodeset i915.modeset=1) to get it to work, and I had glimpsed that in the Grub menu at one point. So, it occurred to me that I might have entered it when booting from the UEFI OS choice, but not when booting from the antiX19 choice.
So, this morning, I moved the antiX19 to the #1 boot choice in the “BIOS” and then used the editing function in the GRUB menu to see if the nomodeset variable was set.
The top choice (AntiX19) was blank, so I checked the next choice (“Advanced options for AntiX19”) and that one had a bunch of items – including nomodeset i915.modeset=1. So, I hit Control+X from that screen to boot and the computer actually booted normally.
If it boots consistently in the future, I will blame the problem on my failure to add the nomodeset line to grub for antiX19.
(I believe the reason I needed that was I have two GPUs on this “gaming” laptop, so I had to tell the boot which to use.)
I will probably try newer kernels also, just because…<g>.
Thanks for your comments.
Steve Rinsler
Not solved. Sometimes, it requires four or five reboots to get the system to get past the error messages.
I will try updating the kernel and report back.
stevesr0
With a 5.6.0.0 kernel, the system boots (so far). There are some additional error messages and a very brief delay after the ACPI errors, but it then moves forward.
If it boots consistently, I will marked this as solved.
stevesr0
- You must be logged in to reply to this topic.
