F5F Stay Refreshed Software Operating Systems The installation isn't visible in the bootloader.

The installation isn't visible in the bootloader.

The installation isn't visible in the bootloader.

R
RoxXmaster
Member
206
07-16-2016, 03:35 AM
#1
Hello, I attempted to convert an old laptop into a home theatre PC for streaming from my main machine using Steamlink. Because I live with others, I wanted a solid controller setup so multiple people could use it easily. After testing Chimera OS, I encountered a GPU-related issue since the laptop uses an Nvidia 700 series card. Eventually, I discovered Nobara, which seemed suitable for my needs until SteamOS updates arrived. I transferred it to a USB drive and followed the installation steps. The swap option was set to hibernate, which I wasn’t sure was necessary. The process went smoothly until a restart was required. After that, I hit a problem: the system doesn’t recognize my USB drive as a bootable device. As long as I have the USB in, it boots normally. Removing it forces me back to the BIOS menu. I tried both HTPC and standard versions, installing it multiple times without success. Anyone have suggestions on how to resolve this?
R
RoxXmaster
07-16-2016, 03:35 AM #1

Hello, I attempted to convert an old laptop into a home theatre PC for streaming from my main machine using Steamlink. Because I live with others, I wanted a solid controller setup so multiple people could use it easily. After testing Chimera OS, I encountered a GPU-related issue since the laptop uses an Nvidia 700 series card. Eventually, I discovered Nobara, which seemed suitable for my needs until SteamOS updates arrived. I transferred it to a USB drive and followed the installation steps. The swap option was set to hibernate, which I wasn’t sure was necessary. The process went smoothly until a restart was required. After that, I hit a problem: the system doesn’t recognize my USB drive as a bootable device. As long as I have the USB in, it boots normally. Removing it forces me back to the BIOS menu. I tried both HTPC and standard versions, installing it multiple times without success. Anyone have suggestions on how to resolve this?

B
Backstaber970
Senior Member
435
07-19-2016, 03:49 AM
#2
Are you checking if both legacy and UEF are set as boot options in the BIOS? It seems likely that since Nobara aims for a gaming-focused build, EFI will be the standard boot method. Your guess is accurate.
B
Backstaber970
07-19-2016, 03:49 AM #2

Are you checking if both legacy and UEF are set as boot options in the BIOS? It seems likely that since Nobara aims for a gaming-focused build, EFI will be the standard boot method. Your guess is accurate.

H
Hulireum
Junior Member
3
07-24-2016, 05:59 PM
#3
The BIOS is configured for UEFI mode.
H
Hulireum
07-24-2016, 05:59 PM #3

The BIOS is configured for UEFI mode.

X
Xenuon
Junior Member
4
07-24-2016, 10:35 PM
#4
The installer offers features to explore the EFI partition and check its status, so you won’t just have a standard installation.
X
Xenuon
07-24-2016, 10:35 PM #4

The installer offers features to explore the EFI partition and check its status, so you won’t just have a standard installation.

C
C_M
Junior Member
31
07-25-2016, 11:11 PM
#5
After numerous attempts and repeated installations to avoid errors, I finally got it functioning. It turns out the installer in the live setup completed everything, but it didn’t add a boot entry to efibootmgr. Here’s my fix: Launch a console in the live environment and use tzpe with the command (make sure to pick the correct drive, like sda) then run: sudo efibootmgr -c -w -L Nobara -d /dev/sda -p 1 -l /EFI/fedora/shim.efi. This command manages UEFI boot entries and ensures the correct entry is created.
C
C_M
07-25-2016, 11:11 PM #5

After numerous attempts and repeated installations to avoid errors, I finally got it functioning. It turns out the installer in the live setup completed everything, but it didn’t add a boot entry to efibootmgr. Here’s my fix: Launch a console in the live environment and use tzpe with the command (make sure to pick the correct drive, like sda) then run: sudo efibootmgr -c -w -L Nobara -d /dev/sda -p 1 -l /EFI/fedora/shim.efi. This command manages UEFI boot entries and ensures the correct entry is created.

W
WaterLily2003
Senior Member
648
07-27-2016, 05:19 PM
#6
W
WaterLily2003
07-27-2016, 05:19 PM #6

E
enzo91o
Member
56
07-28-2016, 01:57 AM
#7
Sharing the answer and staying active in the discussion are both great approaches.
E
enzo91o
07-28-2016, 01:57 AM #7

Sharing the answer and staying active in the discussion are both great approaches.