You are not logged in.
Yes, grub-cpu is 'i386'
So what can I do ?
Just wait for a new relese ?
Offline
It's unlikely that waiting will solve it.
Report a bug against the grub package detailing that the i386-efi target doesn't boot Arch's kernels.
Offline
Thanks, I see that the bug has already been reported and assigned to a developer. So I can just wait...
Offline
Oh, I missed that there's one already. FS#79098, for reference.
For now, those with IA32 UEFI can vote on the issue.
Offline
I don't understand how I can vote...
Offline
Ok, found (I had to login) and voted.
Offline
My grub_cpu is x86_64, so it's something other.
Offline
Before you're somehow kicked back to grub, maybe after a second or so.
But w/ rootwait, you'd ideally not be returned to grub at all, but the kernel waits forever for the root device to appear.
With or without rootwait, I got the same errors when unplug the usb stick. Errors about broken sectors, "unable to load" and so on.
Offline
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
But "broken sectors" very much sounds like actual IO errors and either the usb key is physically damaged or loosely seated or something like that.
Online
I had the same issue. It started working when I disabled Secure Boot in the bios.
Offline
I had the same issue. It started working when I disabled Secure Boot in the bios.
Let me embrace you!
I thought SecureBoot was turned off on my PC, but it was not. And since I never used it anyway, I turned it off and immediately checked ArchISO 2023.09.01. And it boots!
Offline
If Secure Boot was enabled how did you even see that error from GRUB? The act of launching unsigned GRUB is an security violation.
Offline
If Secure Boot was enabled how did you even see that error from GRUB? The act of launching unsigned GRUB is an security violation.
I have almost zero knowledge about Secure Boot, but versions prior to 2023.06.01 are loaded with absolutely the same PC configurations. Don't know how an why.
Offline
Searching on the web I've found the following module:
https://github.com/jfwells/linux-asus-t … otia32.efi
In effect using such module the boot starts, but it stops after a while with the following error :
...
running hook [archiso_pxe_http]
running hook [archiso_pxe_nfs]
mounting 'UUID=' to '/run/archiso/bootmnt'
blkid -t needs NAME=value pair
Try 'Blkid --help' for more information
Waiting 30 seconds for device /dev/disk/by-uuid/ ...
Error 'UUID=' device did not show up after 30 seconds...
Falling back to interactive prompt
This is what I did:
Used wipefs -a of a pendrive.
Created on it a dos partition table and a primary partition of type 0c (windows fat32 lba).
Formatted the partition as fat32.
Set the partition label with:
fatlabel /dev/sdc1 ARCH_202309.
Mounted the pen drive on /mnt.
Mounted the Arch iso on a loop device.
Copied all the contents of the device on the pen,
Copied the mentioned module on /mnt/EFI/boot, replacing the preexistent module, then sync.
Unmounted the pen.
Transferred it to the device and booted.
Any suggestion ?
Offline
Found ! I detected the UUID of the pendrive (ls /dev/disk/by-uuid)
and then I inserted it in the install script, just before the linux command:
set ARCHISO_UUID=XXXX-XXXX
linux ...
Now I'm installing ...
Offline
You could use the BOOTIA32.EFI binary from the 2023.06.01 iso.
Offline
Thanks, given that the last Grub distribuition has problems,
I have downloaded and compiled Grub myself (it's not difficult)
and i've added some comments about the process on the bug tracking site.
Offline
Someone really should bisect the issue and report it upstream. IA32 UEFI can be tested in a VM, so it's not that hard.
Offline
By the way, I had the same problem today 18 October 2023 and I just had to disable Windows secure boot from my bios settings.
Github Account: github.com/babaliaris Arch General Guidelines
Favourite Distro: archlinux.org Arch Wiki
Offline
The ISO does not support Secure Boot. This is documented in https://wiki.archlinux.org/title/Instal … nvironment and https://wiki.archlinux.org/title/Unifie … ion_medium. Nothing regarding this has changed in years.
Last edited by nl6720 (2023-10-18 11:30:42)
Offline