| View previous topic :: View next topic |
| Author |
Message |
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 168
|
 Posted: Tue Nov 26, 2024 5:34 pm Post subject: |
 |
|
| Nowa wrote: | | alecStewart1 wrote: | But I imagine I'll have to rename the vmlinuz-x.y.z-gentoo-dist file to bootx64.efi and run efibootmgr myself again. Hurray for differing specifications...
EDIT:
Although I could put a postinstall script at /etc/kernel/postinst.d to do this so I don't have to do it manually every time. |
There should be no need to rename, this is the part that uefi-mkconfig takes care of provided the UEFI supports boot entries and manipulating them from the OS. If it does not then you can make a copy of the vmlinuz-x.y.z-gentoo-dist.efi named vmlinuz.efi (and register that with the UEFI), sys-kernel/installkernel will automatically keep that copy up to date. |
Apologies, I should clarify more.
Initially, when using genkernel, I left the EFI file names alone and create boot entries with those names (vmlinuz-x.y.z-etc). Whenever I would reboot and press F11 a bunch to get the the boot menu to come up, the boot entries I created wouldn't be there in the list of available EFI files. Now, it's entirely possible I made some other mistake, in fact likely possible. But once I renamed files to bootx64.efi and recreated the entries with efibootmgr, I no longer had issues.
Does this sound a bit stupid? Yes, yes it does.
Do I personally think it's out of the realm of possibilities that a motherboard manufacturer that normally expects people to use Windows to have the motherboard specifically look for an EFI file with a specific name? Not really.
I'm just stating what worked for me at the time.
Again it's entirely possible I made some other mistake.
I'll try rebooting later without manually calling efibootmgr (aside from double checking if actual EFI entries were created) and simply just relying on what using the dist-kernel, installkernel, ugrd and uefi-mkconfig have provided. |
|
| Back to top |
|
 |
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 168
|
| Posted: Wed Nov 27, 2024 12:28 am Post subject: |
|
|
Okay...uh, I'm going to assume this wasn't Gentoo's doing, but now my PC can't even get the the boot menu. If I don't repeatedly press F11 to get to the boot menu, I'm met with a black screen. The display is on, just nothing happens unless I repeatedly press F11. In doing so, the computer is indefinitely stuck on
| Quote: | | Entering Boot Menu... |
To clarify, all I did when I got home was check if there was EFI boot entires with efibootmgr via
Which there were, and that's it. No re-emerging anything. No rearranging order of EFI boot entries. No removing any EFI boot entires. Nothing else besides closing all opened applications (just Wezterm and Librewolf) and restarting. So...I don't really know what to do. I don't know if I can even get to a Live USB. Maybe I could flash the BIOS...but that's all I think I can do, possibly. Guess I'll try that when I can.
EDIT:
Wow, I can't even get to the BIOS. DEL, F12, F10, etc. don't bring up the BIOS. Just a black screen and pressing F11 is the only thing that'll work. It's almost fascinating. Guess my PC is borked. |
|
| Back to top |
|
|
zen_desu
n00b
Joined: 25 Oct 2024
Posts: 53
|
| Posted: Wed Nov 27, 2024 12:55 am Post subject: |
|
|
Can you try clearing the CMOS if possible? I can't think of anything from the install which would prevent you from getting into the UEFI config/BIOS. If you can somehow clear config or restore defaults that could help get things working again.
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 168
|
| Posted: Wed Nov 27, 2024 1:00 am Post subject: |
|
|
| zen_desu wrote: | | Can you try clearing the CMOS if possible? I can't think of anything from the install which would prevent you from getting into the UEFI config/BIOS. If you can somehow clear config or restore defaults that could help get things working again. |
Oh yea! I forgot about the CMOS. It's been too long (well, ok, 2 years) since I've done anything hardware wise, so no better time than now I guess. 
A small part of me wants to start over from scratch anyway. |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 168
|
| Posted: Sun Dec 08, 2024 3:26 am Post subject: |
|
|
Sigh ok, clearing the CMOS didn't work. Still just a blank screen. Thought I could at least get to the BIOS, but no dice. Finger blasting DEL or F11 or F12 does nothing.
I installed the recent BIOS update for my MSI board, did the whole flash the bios process, realized I didn't format the USB to be vFAT/FAT32, tried, then later realized I rename the file MSI.ROM, tried again, and now I found out that the motherboard might not like the USB used.
I'm hoping that the issue was the BIOS wasn't up-to-date (I hadn't updated it in quite some time), and not a hardware issue, otherwise I'm SOL for a minute. |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 168
|
| Posted: Sat Dec 14, 2024 10:19 pm Post subject: Update - 14th of December, 2024 |
|
|
Okay, update for anyone curious:
Haven't gotten to using the MSI provided USB to flash the BIOS, but I'm formatting it now to VFAT, which MSI says it's supposed to be. Fun thing, the filesystem whenever I inserted it into the Mac I have was NTFS, not VFAT like MSI says it should be.
Currently the desktop is just chilling with the power off. The light where the USB port and "Flash BIOS" button is located is stuck on red. Hopefully that's not a sign of anything bad *knocks on wood*.
Hopefully this works, otherwise I might have to take the tower to Micro Center to see if they can tell me if one or more parts have failed so I can get replacements.
Reminder to keep your BIOS up-to-date, kids. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
