[SOLVED]Arch boot entry not showing up

Omarz2012 · 2024-11-03 14:46:11

i have a dualboot system between windwos and arch on an acer nitro 5 and i recently got a kingston 1TB NV2 SSD and tried installing arch on that. but when i tried acessing my newly installed system. it didn't show up in the f12 boot options menu. i dont really know how to fix this cause there is no related settings in my bios.(i also have another problem with grub not detecting windows even with os-prober due to them being on sperate SSDs(yes, windows and my new arch installation are installed with GPT))

Last edited by Omarz2012 (2024-11-05 20:00:45)

V1del · 2024-11-03 18:04:14

Acers tend to have a weird UEFI. if you're sure you ran the proper grub-install command but it still not showing up, go into your UEFI, enable secureboot, reboot, go back into your UEFI, mark the grubx64.efi file on your ESP as "trusted", reboot, go back into the UEFI and disable secureboot. You should now have an entry for GRUB.

As for the Windows detection issue, make sure that the Windows ESP is mounted "somewhere" (doesn't matter where, but don't mask the ESP for your Arch install) and recheck, os-prober should find it.

If neither of these help, post details of your setup, e.g. mount all the partitions like you think they are correct and post your

lsblk -f
mount
efibootmgr -uv
cat /boot/grub/grub.cfg

https://wiki.archlinux.org/title/List_o … n_services

Omarz2012 · 2024-11-03 18:36:09

doesn't grub not play nicely with secure boot? And also where is the grubx64.efi file located in my boot partition also here is a diagram if my original post's wording gave a seizure Diagram

Last edited by Omarz2012 (2024-11-03 20:04:55)

Omarz2012 · 2024-11-03 19:52:36

do i post my newly installed arch which i can't access as i said before, or my already existing one

V1del wrote:

Acers tend to have a weird UEFI. if you're sure you ran the proper grub-install command but it still not showing up, go into your UEFI, enable secureboot, reboot, go back into your UEFI, mark the grubx64.efi file on your ESP as "trusted", reboot, go back into the UEFI and disable secureboot. You should now have an entry for GRUB.
As for the Windows detection issue, make sure that the Windows ESP is mounted "somewhere" (doesn't matter where, but don't mask the ESP for your Arch install) and recheck, os-prober should find it.
If neither of these help, post details of your setup, e.g. mount all the partitions like you think they are correct and post your
lsblk -f
mount
efibootmgr -uv
cat /boot/grub/grub.cfg
https://wiki.archlinux.org/title/List_o … n_services

V1del · 2024-11-03 20:43:39

You can configure it to not have an issue, but the idea is to enable GRUB as trusted and then disable secure boot again, you need to enable secure boot to get the option of adding UEFI entries, add the entry, disabling secure boot afterwards will not clear the boot entry.

But if you already have a working installation, then posting these outputs (from the perspective of the new disk, chrooted in from a live system if need be) will be quite relevant.

Omarz2012 · 2024-11-03 22:24:51

according to efibootmgr, these are my entries(yes was a boot entry that i somehow created a few years ago(idk how) which does nothing)

BootOrder: 0002,0001,2001,0004,2002,2003
Boot0000* USB HDD: USB FLASH DRIVE      UsbWwid(1005,b113,0,07BC178048556C7)/HD(1,GPT,146e8c41-8750-4b47-8461-c04223ebc6bb,0x800,0xeeb7b8)䍒
      dp: 03 10 2a 00 00 00 05 10 13 b1 30 00 37 00 42 00 43 00 31 00 37 00 38 00 30 00 34 00 38 00 35 00 35 00 36 00 43 00 37 00 43 00 / 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 b8 b7 ee 00 00 00 00 00 41 8c 6e 14 50 87 47 4b 84 61 c0 42 23 eb c6 bb 02 02 / 7f ff 04 00
    data: 52 43
Boot0001* Windows Boot Manager  HD(1,GPT,37bdae12-b360-481e-a1ee-13a86b6ca3a3,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi䥗䑎坏S
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 12 ae bd 37 60 b3 1e 48 a1 ee 13 a8 6b 6c a3 a3 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 47 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0002* HDD0: 50026B7684DB0CC8-KINGSTON OM8PDP3512B-AA1       PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/NVMe(0x1,00-26-B7-68-4D-B0-CC-85)/HD(5,GPT,5836fe81-638d-4139-a4d3-ff2733864d81,0x27efe000,0x200000)䍒
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 01 / 01 01 06 00 00 00 / 03 17 10 00 01 00 00 00 00 26 b7 68 4d b0 cc 85 / 04 01 2a 00 05 00 00 00 00 e0 ef 27 00 00 00 00 00 00 20 00 00 00 00 00 81 fe 36 58 8d 63 39 41 a4 d3 ff 27 33 86 4d 81 02 02 / 7f ff 04 00
    data: 52 43
Boot0003* arch  HD(2,GPT,3cca1fe7-bb07-44ee-889c-c7737d14fe41,0x8000,0x200000)/\EFI\arch\grubx64.efi
      dp: 04 01 2a 00 02 00 00 00 00 80 00 00 00 00 00 00 00 00 20 00 00 00 00 00 e7 1f ca 3c 07 bb ee 44 88 9c c7 73 7d 14 fe 41 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 61 00 72 00 63 00 68 00 5c 00 67 00 72 00 75 00 62 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0004* yes   PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/NVMe(0x1,00-26-B7-68-4D-B0-CC-85)/HD(1,GPT,37bdae12-b360-481e-a1ee-13a86b6ca3a3,0x800,0x32000)/\EFI\HackBGRT\bootmgfw-original.efiぁ‱급
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 01 / 01 01 06 00 00 00 / 03 17 10 00 01 00 00 00 00 26 b7 68 4d b0 cc 85 / 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 12 ae bd 37 60 b3 1e 48 a1 ee 13 a8 6b 6c a3 a3 02 02 / 04 04 4c 00 5c 00 45 00 46 00 49 00 5c 00 48 00 61 00 63 00 6b 00 42 00 47 00 52 00 54 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2d 00 6f 00 72 00 69 00 67 00 69 00 6e 00 61 00 6c 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 41 30 31 20 09 ae
Boot2001* EFI USB Device        䍒
      dp: 7f ff 04 00
    data: 52 43
Boot2002* EFI DVD/CDROM 䍒
      dp: 7f ff 04 00
    data: 52 43
Boot2003* EFI Network   䍒
      dp: 7f ff 04 00
    data: 52 43

as you can see, the arch entry does not appear in the boot entry making the f12 boot menu look like this, and when I try to edit the boot menu with efibootmgr, it just resets once I reboot

Last edited by Omarz2012 (2024-11-04 22:11:33)

Omarz2012 · 2024-11-03 22:41:14

*how do I delete this post

Last edited by Omarz2012 (2024-11-04 18:18:31)

Omarz2012 · 2024-11-03 22:56:25

*deleted

Last edited by Omarz2012 (2024-11-04 18:21:46)

Omarz2012 · 2024-11-03 22:59:49

*deleted

Last edited by Omarz2012 (2024-11-04 18:22:51)

Omarz2012 · 2024-11-03 23:26:13

*deleted

Last edited by Omarz2012 (2024-11-04 18:23:21)

ewaller · 2024-11-04 01:30:30

Omarz2012,
Two things, please. When posting large images, do not insert them in line using img tags, rather provide them as url tags.
Second, to not make serial posts. If you are the last person to have posted in a thread, use the edit function instead of creating a new post.

Third (I know, I said two). Do not make personal appeals. It is okay to identify the person you are responding to, but please do make direct appeals for assistance.

Some EFI implementations are horrible and are only tested to the point where they will boot some obscure operating system from the Pacific Northwest portion of the United States.
You might try using the EFI menu to change the boot order. My last laptop was an HP (and my last HP laptop, but I digress). It had a said horrible EFI implementation, and the only way to get it to stick was through the EFI setup menu.

Omarz2012 · 2024-11-04 02:03:20

sorry about the things ive done. What is the EFI menu, and why was I able to install arch on my original SSD with archinstall but not on this new one the real way?

Last edited by Omarz2012 (2024-11-04 03:17:32)

kermit63 · 2024-11-04 04:46:07

Let me make a wild guess: Maybe you did not install it correctly?

1. V1del asked you for more info: 4 of them in fact, and you provided 1.

2. The best way to show remorse for your mistakes is to correct them. For example, you can use the edit option in your old posts to link to images instead of keeping them embedded.

3. Narratives and diagrams are nice to provide context to the problem, but actual data like the ones V1del asked for and detailed explanation of how you installed the system will go a long way towards solving the problem. There are some really good helpers here on this forum, but as far as I know, none of them possess extra sensory perception.

4. archinstall script was meant as a convenience tool for people who already know how to install the system manually. Just because you were able to cheat your way into installing arch using the script doesn't mean you possess the basic understanding of how arch works. It all boils down to reading, and more importantly, understanding the wiki.

Last edited by kermit63 (2024-11-04 04:48:18)

V1del · 2024-11-04 11:05:07

Is the HDD0 in this screenshot your original HDD? Everything you posted so far points to the symptoms I've explained in the first reply and these should stick if you properly go through the steps as I mentioned them.

The alternative would be to get a "SSD" boot entry, which you can achieve by running the corresponding grub-install command you used with the --removable flag (or copying $espmountpoint/EFI/GRUB/grubx64.efi to $espmountpoint/EFI/BOOTx64.efi as detailed in https://wiki.archlinux.org/title/Unifie … ble_drives )

Omarz2012 · 2024-11-04 18:13:13

yes, hdd0 is my original HDD, I will try to see if it works with secure boot once I get home

V1del wrote:

Is the HDD0 in this screenshot your original HDD? Everything you posted so far points to the symptoms I've explained in the first reply and these should stick if you properly go through the steps as I mentioned them.
The alternative would be to get a "SSD" boot entry, which you can achieve by running the corresponding grub-install command you used with the --removable flag (or copying $espmountpoint/EFI/GRUB/grubx64.efi to $espmountpoint/EFI/BOOTx64.efi as detailed in https://wiki.archlinux.org/title/Unifie … ble_drives )

update: tried allowing the boot entries but they don't show up, what i have found is that the "yes" boot option was created from me messing with allowing boot entires and selecting a random boot entry i found back when i used hackBGRT. the grub article on the arch wiki says that maybe the computer can only show a certain amount of boot entries, should i delete "yes"?

edit: it worked

Last edited by Omarz2012 (2024-11-05 00:38:22)

Omarz2012 · 2024-11-04 18:17:28

1. ok I will post the outputs once I get home
2.ok
3. I partitioned the disk with a 16mb partition called nvme1n1p1 so window can recognize the disk, a 1gb boot partition mounted on /boot/efi with the file system fat32 called nvme1n1p2. and my root partition is 930gb with the file system ext4 and is called nvme1n1p3. I installed grub with the commander

grub-install /dev/nvme1n1

.
4. that's not what I mean, I mean that how did archinstall work with my original SSD but not when I actually try to install, my computer just hides the boot entry and trying to make it show up just goes back once I reboot

kermit63 wrote:

Let me make a wild guess: Maybe you did not install it correctly?
1. V1del asked you for more info: 4 of them in fact, and you provided 1.
2. The best way to show remorse for your mistakes is to correct them. For example, you can use the edit option in your old posts to link to images instead of keeping them embedded.
3. Narratives and diagrams are nice to provide context to the problem, but actual data like the ones V1del asked for and detailed explanation of how you installed the system will go a long way towards solving the problem. There are some really good helpers here on this forum, but as far as I know, none of them possess extra sensory perception.
4. archinstall script was meant as a convenience tool for people who already know how to install the system manually. Just because you were able to cheat your way into installing arch using the script doesn't mean you possess the basic understanding of how arch works. It all boils down to reading, and more importantly, understanding the wiki.

Last edited by Omarz2012 (2024-11-04 18:33:08)

ewaller · 2024-11-04 18:29:40

Please don't redact your posts. It makes it impossible for the next person with this problem to use this as a resource -- which is the goal.

Have you booted to Windows during any of this debacle? Did it update itself? It has a really bad habit of crapping the sandbox in which others are playing without any regard. Expect it to screw with your boot order any time you boot that OS, especially when it undergoes it's periodic mutation.

Omarz2012 · 2024-11-04 21:47:57

i moved all the information to my 4th post, also once i find the solution(hopefully with your guys help) i will post the solution.

ewaller wrote:

Please don't redact your posts. It makes it impossible for the next person with this problem to use this as a resource -- which is the goal.
Have you booted to Windows during any of this debacle? Did it update itself? It has a really bad habit of crapping the sandbox in which others are playing without any regard. Expect it to screw with your boot order any time you boot that OS, especially when it undergoes it's periodic mutation.

nope

Last edited by Omarz2012 (2024-11-04 21:54:17)

Omarz2012 · 2024-11-04 22:10:09

V1del wrote:

Acers tend to have a weird UEFI. if you're sure you ran the proper grub-install command but it still not showing up, go into your UEFI, enable secureboot, reboot, go back into your UEFI, mark the grubx64.efi file on your ESP as "trusted", reboot, go back into the UEFI and disable secureboot. You should now have an entry for GRUB.
As for the Windows detection issue, make sure that the Windows ESP is mounted "somewhere" (doesn't matter where, but don't mask the ESP for your Arch install) and recheck, os-prober should find it.
If neither of these help, post details of your setup, e.g. mount all the partitions like you think they are correct and post your
lsblk -f
mount
efibootmgr -uv
cat /boot/grub/grub.cfg
https://wiki.archlinux.org/title/List_o … n_services

here is the rest of the information
for the lsblk thing

nvme0n1                                                                                      
├─nvme0n1p1 vfat   FAT32 ESP             0EC5-D87C                                           
├─nvme0n1p2                                                                                  
├─nvme0n1p3 ntfs         Windows         30F2C6BEF2C68814                                    
├─nvme0n1p4 ntfs         System Reserved 52003CD7003CC3AF                                    
├─nvme0n1p5 vfat   FAT32                 C5DC-2C7B                             791.2M    23% /boot
└─nvme0n1p6 ext4   1.0                   0c91e27f-87b4-4b43-9438-7c48a21b833b   97.9G    30% /
nvme1n1                                                                                      
├─nvme1n1p1                                                                                  
├─nvme1n1p2 vfat   FAT32                 6BC3-779C                                           
└─nvme1n1p3 ext4   1.0                   01f8c9b5-46f9-4688-94f0-0ac4582b5f77

grub.cfg

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root 01f8c9b5-46f9-4688-94f0-0ac4582b5f77
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=60
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=60
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-01f8c9b5-46f9-4688-94f0-0ac4582b5f77' {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_gpt
        insmod ext2
        search --no-floppy --fs-uuid --set=root 01f8c9b5-46f9-4688-94f0-0ac4582b5f77
        echo    'Loading Linux linux ...'
        linux   /boot/vmlinuz-linux root=UUID=01f8c9b5-46f9-4688-94f0-0ac4582b5f77 rw  loglevel=3
        echo    'Loading initial ramdisk ...'
        initrd  /boot/amd-ucode.img /boot/initramfs-linux.img
}
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-01f8c9b5-46f9-4688-94f0-0ac4582b5f77' {
        menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-01f8c9b5-46f9-4688-94f0-0ac4582b5f77' {
                load_video
                set gfxpayload=keep
                insmod gzio
                insmod part_gpt
                insmod ext2
                search --no-floppy --fs-uuid --set=root 01f8c9b5-46f9-4688-94f0-0ac4582b5f77
                echo    'Loading Linux linux ...'
                linux   /boot/vmlinuz-linux root=UUID=01f8c9b5-46f9-4688-94f0-0ac4582b5f77 rw  loglevel=3
                echo    'Loading initial ramdisk ...'
                initrd  /boot/amd-ucode.img /boot/initramfs-linux.img
        }
        menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-01f8c9b5-46f9-4688-94f0-0ac4582b5f77' {
                load_video
                set gfxpayload=keep
                insmod gzio
                insmod part_gpt
                insmod ext2
                search --no-floppy --fs-uuid --set=root 01f8c9b5-46f9-4688-94f0-0ac4582b5f77
                echo    'Loading Linux linux ...'
                linux   /boot/vmlinuz-linux root=UUID=01f8c9b5-46f9-4688-94f0-0ac4582b5f77 rw  loglevel=3
                echo    'Loading initial ramdisk ...'
                initrd  /boot/amd-ucode.img /boot/initramfs-linux-fallback.img
        }
        menuentry 'Arch Linux, with Linux linux (recovery mode)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-recovery-01f8c9b5-46f9-4688-94f0-0ac4582b5f77' {
                load_video
                set gfxpayload=keep
                insmod gzio
                insmod part_gpt
                insmod ext2
                search --no-floppy --fs-uuid --set=root 01f8c9b5-46f9-4688-94f0-0ac4582b5f77
                echo    'Loading Linux linux ...'
                linux   /boot/vmlinuz-linux root=UUID=01f8c9b5-46f9-4688-94f0-0ac4582b5f77 rw single 
                echo    'Loading initial ramdisk ...'
                initrd  /boot/amd-ucode.img /boot/initramfs-linux-fallback.img
        }
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/25_bli ###
if [ "$grub_platform" = "efi" ]; then
  insmod bli
fi
### END /etc/grub.d/25_bli ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
if [ "$grub_platform" = "efi" ]; then
        fwsetup --is-supported
        if [ "$?" = 0 ]; then
                menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
                        fwsetup
                }
        fi
fi
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###

will change the efi output in the other post to -uv instead of --unicode

Omarz2012 · 2024-11-05 00:39:20

fixed it by deleting "yes" boot entry. If you have this problem: delete unnecessaryy boot entries

V1del · 2024-11-05 08:17:55

Please mark the issue as [SOLVED] by editing the title in your first post.

Omarz2012 · 2024-11-05 20:00:07

how do I edit titles

V1del wrote:

Please mark the issue as [SOLVED] by editing the title in your first post.

edit:got it

Last edited by Omarz2012 (2024-11-05 20:01:04)

Arch Linux

#1 2024-11-03 14:46:11

[SOLVED]Arch boot entry not showing up

#2 2024-11-03 18:04:14

Re: [SOLVED]Arch boot entry not showing up

#3 2024-11-03 18:36:09

Re: [SOLVED]Arch boot entry not showing up

#4 2024-11-03 19:52:36

Re: [SOLVED]Arch boot entry not showing up

#5 2024-11-03 20:43:39

Re: [SOLVED]Arch boot entry not showing up

#6 2024-11-03 22:24:51

Re: [SOLVED]Arch boot entry not showing up

#7 2024-11-03 22:41:14

Re: [SOLVED]Arch boot entry not showing up

#8 2024-11-03 22:56:25

Re: [SOLVED]Arch boot entry not showing up

#9 2024-11-03 22:59:49

Re: [SOLVED]Arch boot entry not showing up

#10 2024-11-03 23:26:13

Re: [SOLVED]Arch boot entry not showing up

#11 2024-11-04 01:30:30

Re: [SOLVED]Arch boot entry not showing up

#12 2024-11-04 02:03:20

Re: [SOLVED]Arch boot entry not showing up

#13 2024-11-04 04:46:07

Re: [SOLVED]Arch boot entry not showing up

#14 2024-11-04 11:05:07

Re: [SOLVED]Arch boot entry not showing up

#15 2024-11-04 18:13:13

Re: [SOLVED]Arch boot entry not showing up

#16 2024-11-04 18:17:28

Re: [SOLVED]Arch boot entry not showing up

#17 2024-11-04 18:29:40

Re: [SOLVED]Arch boot entry not showing up

#18 2024-11-04 21:47:57

Re: [SOLVED]Arch boot entry not showing up

#19 2024-11-04 22:10:09

Re: [SOLVED]Arch boot entry not showing up

#20 2024-11-05 00:39:20

Re: [SOLVED]Arch boot entry not showing up

#21 2024-11-05 08:17:55

Re: [SOLVED]Arch boot entry not showing up

#22 2024-11-05 20:00:07

Re: [SOLVED]Arch boot entry not showing up

Board footer