From: Alan Grimes <alonzotg@verizon.net>
To: gentoo-user@lists.gentoo.org, Michael <confabulate@kintzios.com>
Subject: Re: [gentoo-user] Grub: for the love of almighty Zardoz the magniicent....
Date: Thu, 2 Jul 2020 00:20:19 -0400 [thread overview]
Message-ID: <34381570-74ae-f419-f538-3673dfa6bb5d@verizon.net> (raw)
In-Reply-To: <4242826.LvFx2qVVIh@lenovo.localdomain>
Got the motherboard running, the motherboard was IGNORING the "UEFI
only" BIOS setting, it was attempting to boot my system in BIOS mode, I
found that I had to efibootmgr and tell the stupid BIOS what is what...
why the BIOS doesn't scan the first two directories under /EFI for *.efi
and list them, then allow the user to select the default is byond me...
I mean it would be much much too easy to do it that way. =\
The magic smoke had left my previous motherboard, literally a component
was burned off the board, so couldn't put it back in service even if it
could have been booted. The temporary build actually looks pretty nice.
It has an absolutely absurd amount of RGB on it...
hmm, I wonder how many of you good ppl have a similarly burned component
that you haven't detected for some reason... If your build is more than
~2 years old, I suggest a close visual inspection of all components...
The RGB on the ram does cause a serious heat issue when I have 4 sticks
stacked up on the threadripper, but on this temporary build I'm only
using two sticks and it looks very nice.
--
The vaccine is a LIE.
#TheHonklerIsReal
Powers are not rights.
next prev parent reply other threads:[~2020-07-02 4:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 21:19 [gentoo-user] Gentoo chroot with old glibc Hervé Guillemet
2020-06-21 17:06 ` Michael
2020-06-21 19:43 ` Hervé Guillemet
2020-06-21 20:03 ` Michael
2020-06-21 22:52 ` Hervé Guillemet
2020-06-30 8:26 ` Andreas K. Huettel
2020-06-30 16:29 ` Laurence Perkins
2020-07-01 1:40 ` [gentoo-user] Grub: for the love of almighty Zardoz the magniicent Alan Grimes
2020-07-01 8:15 ` Neil Bothwick
2020-07-01 8:45 ` Michael
2020-07-02 4:20 ` Alan Grimes [this message]
2020-07-01 1:30 ` [gentoo-user] Gentoo chroot with old glibc Thomas Mueller
[not found] ` <20200701013122.CE9C8E08AE@pigeon.gentoo.org>
2020-07-01 14:47 ` Andreas K. Huettel
2021-01-04 11:57 ` Thomas Mueller
[not found] ` <20210104115748.50A5EE0930@pigeon.gentoo.org>
2021-01-08 23:37 ` Andreas K. Hüttel
2020-06-21 21:08 ` Rich Freeman
2020-06-21 22:34 ` Hervé Guillemet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34381570-74ae-f419-f538-3673dfa6bb5d@verizon.net \
--to=alonzotg@verizon.net \
--cc=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox