From: Alan Grimes <alonzotg@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Login manager occasionally fails to show
Date: Tue, 11 Feb 2025 12:20:34 -0500 [thread overview]
Message-ID: <f5a817a0-2cc3-b97c-fe93-aff8a6b46be8@verizon.net> (raw)
In-Reply-To: <2978603.e9J7NaK4W3@rogueboard>
Login manager?!?!?!!? Are you nuts?! I mean it almost makes sense as a
concept but X11 is inherently unreliable and cannot be trusted to work
at system bootup, the only solution is to boot to text mode, log in, and
then start x11 (with the opportunity to switch to a secondary vterm and
solve whatever issues crop up...). I have never attempted to use
anything other than simple text-mode login in the last 20 years, and
then when the system is up, just run it for several months without ever
turning it off or making any change. I'm currently 51 days into a run
without any attempt at system maintenence. The only issue I have is that
the CPU frequency manager likes to clock my CPU down to about 550 mhz
making the system unusably unresponsive despite low CPU temps and high
load average. =\ I changed a kernel setting for user-space frequency
management but have been too lazy to reboot.
--
You can't out-crazy a Democrat.
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.
prev parent reply other threads:[~2025-02-11 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 21:41 [gentoo-user] Login manager occasionally fails to show Markus Gustafsson
2025-01-26 11:18 ` Peter Humphrey
2025-01-26 12:33 ` Michael
2025-01-29 21:19 ` Markus Gustafsson
2025-01-30 8:06 ` Michael
2025-02-02 11:09 ` Markus Gustafsson
2025-02-02 13:11 ` Michael
2025-02-07 20:56 ` Markus Gustafsson
2025-02-08 10:02 ` Michael
2025-02-08 11:02 ` Michael
2025-02-11 17:20 ` Alan Grimes [this message]
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=f5a817a0-2cc3-b97c-fe93-aff8a6b46be8@verizon.net \
--to=alonzotg@verizon.net \
--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