From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Getting WiFi to work
Date: Thu, 11 Apr 2024 16:18:51 +0100 [thread overview]
Message-ID: <2484654.jE0xQCEvom@rogueboard> (raw)
In-Reply-To: <5770823.DvuYhMxLoT@cube>
[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]
On Thursday, 11 April 2024 16:15:52 BST Peter Humphrey wrote:
> On Thursday, 11 April 2024 16:08:35 BST Michael wrote:
> > On Thursday, 11 April 2024 13:49:18 BST Peter Humphrey wrote:
> --->8
>
> > > I decided to establish a firm, clean system to fall back to after
> > > messing
> > > about with the various wifi packages, so I built a fresh system building
> > > on the merged-usr stage-3. I was surprised to find that kde-plasma/
> > > powerdevil now insists on installing Network Manager unless I set USE=-
> > > wireless against it.
> > >
> > > Why has this happened? Can't the poor power devil cope with any other
> > > way
> > > of running WiFi?
> >
> > The USE="wireless" flag on powerdevil is needed to save energy when the
> > bluetooth/wireless chip is idle. This function could be useful with
> > laptops running on battery.
> >
> > If you set USE="-networkmanager" in make.conf and USE="-wireless" for the
> > powerdevil package you won't be bothered by this again.
>
> I already had USE="-networkmanager" in make.conf.
>
> This is not a laptop and it has no battery. Nowhere on the system is there
> any hint to the contrary, so I still think this has not been thought
> through. The logic should have included alternatives to Network Manager.
Yes, I agree wholeheartedly. However, these decisions are taken upstream,
where there is a tendency of convergence to monoculture.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-11 15:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 13:23 [gentoo-user] Getting WiFi to work Peter Humphrey
2024-04-09 13:44 ` Paul Sopka
2024-04-11 12:49 ` Peter Humphrey
2024-04-11 15:08 ` Michael
2024-04-11 15:15 ` Peter Humphrey
2024-04-11 15:18 ` Michael [this message]
2024-04-11 15:24 ` Peter Humphrey
2024-04-09 14:56 ` Wojciech Kuzyszyn
2024-04-11 15:16 ` Peter Humphrey
2024-04-12 12:51 ` Peter Humphrey
2024-04-12 13:35 ` Michael
2024-04-12 15:05 ` Peter Humphrey
2024-04-12 15:39 ` Michael
2024-04-13 14:49 ` Peter Humphrey
2024-04-13 17:28 ` Michael
2024-04-19 16:02 ` SOLVED: " Peter Humphrey
2024-04-21 22:30 ` Wol
2024-04-21 22:58 ` Peter Humphrey
2024-05-28 14:08 ` Peter Humphrey
2024-05-28 14:52 ` Dale
2024-05-28 15:58 ` Peter Humphrey
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=2484654.jE0xQCEvom@rogueboard \
--to=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