![]() Therefore, I guess, the problem lies with something that changed installing some software and which impedes the b43 to be found by netctl at boot, which in turn prevents nectl to work and thus the delay error message. Note that once I log in after the 1:30 seconds usual delay (and of course wifi-menu does not connect at boot) I can connect loading the b43 module manually with modprobe and then running wifi-menu. Then I got it again, so I tried to remove and reinstall nectl of the b43-firmware-classic module but the error persisted. I checked the various solution posted in different places and got rid of the error message once. Moreover, from Windows 11 installation media filesystem I'm able to trigger cdboot.efi (prompts to press any key, quits after that's done) and cdboot_noprompt.I have installed two identical Archlinux 32 in two partitions of the same laptop Compaq C500, and got in both the identical issue.Īfter installing the system and using netctl and wifi-menu to successfully connect several times automatically at boot, all of a sudden I got the error message at boot. efi files that seem to work using regular F10 and selection. "Nothing" -> EFI shell goes to newline and nothing happens, seems to correlate with "flash" behaviour I tried chrooting into the linux drive and all the files are still there. I reinstalled grub, It's only detecting my Windows 10 Drive, not my Arch drive. The files exists, the directories listed by pkg-config contain those headers, yet gcc, cc and clang cant find them. efi files I get either:Ĭommand Error Status: Unsupported # probably files that aren't really compatible with UEFI, e.g. This has happened before when reinstalling windows or updating my bios. gcc pkg-config -cflags gtk4 main.c pkg-config -libs gtk4 returns gtk/gtk.h: No such file or directory. Configure Clover to recognise Linux partitions. Also UUID doesn't seem to match anything. Enter the BIOS/UEFI settings and use trial and error to determine which of the boot options is Clover (the option may not have a helpful name) Inside Clover, you won't see any Linux partitions, so boot into MacOS to fix that. UPDATE2: I can see "Windows Boot Manager" entry in efibootmgr but not in UEFI boot menu. Is it possible it's some bug in UEFI that doesn't work with Windows? It's able to boot on NUC using purely UEFI mode (systemd-boot as a bootloader). ![]() UPDATE: Swapped yet another drive, SATA SSD, this time with Arch Linux installed. I'm unhappy to report that my FAT32-formatted, Windows 11-host MS tool created Windows 11 bootable USB stick (not using Rufus or any other shenanigans) is still "flashing" after getting selected.Ĭan boot in legacy mode but like I said, not really my goal. flashing) unless Arch USB is used, then I get Image Authorization Fail (again, expected). Check that Windows 10 dual-booting works in UEFI mode - grub can chainload. Just for clarity - no Secure Boot enabled on NUC either, not that it matters that much.īehaviour with it is still the same (i.e. 1 Your Windows install is UEFI, so cannot be booted from a BIOS grub install. Let me know if you need any more details about it vs the other USBs/OS.Īside from the existing SSD I was able to confirm other SSD and USBs boot on other UEFI boards (intel-based: Z97 and AMD-based: X570, both ASRock if that matters). I think it might have been dd'd from the img/iso years ago. Now, for some reason it does boot to Arch Linux archiso just fine using UEFI on generic USB 2.0 thumb-drive. ![]() "New" SSD from another PC with working OS: Samsung 970 EVO (M.2 NVMe) with UEFI-enabled Windows 11 (boots in two different PCs). ![]() Didn't experiment more at this stage, goal is UEFI (not Legacy).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |