this post was submitted on 03 Mar 2024
15 points (85.7% liked)

Selfhosted

40296 readers
239 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

My dearest,

I just got myself a lil' HP Elitedesk 800 G2 mini and am all set to run my home server on there. But I have troubles entering the UEFI menu. I don't know what they did with Windows 10, but I can't get there the usual way (i.e., hitting random f-buttons or esc during startup). I checked out the online Windows support and found this link with options to access the UEFI menu from within Windows:

https://www.isunshare.com/windows-password/four-methods-to-access-uefi-bios-setup.html

However, even when the computer is supposed to reboot into UEFI, it always sends me back to the normal login screen. By now, I ran out of ideas what to try.

Did anyone experience similar problems?

Edit: Got it working with different keyboard/display combination. The reboot from within Windows thing still didn't work, but starting from powered off and hitting f10 a few times did it this time. I think the main problem was with my displayport to HDMI converter at home, which apparently caused some delays - and maybe the fact that it's connected to a TV at home, not a regular display. Also, if you don't stop hitting f10 at some point, apparently you get sent back to normal booting. I didn't investigate that problem further though.

you are viewing a single comment's thread
view the rest of the comments