From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Wayland and CPU load
Date: Fri, 06 Sep 2024 10:45:26 +0100 [thread overview]
Message-ID: <12533769.O9o76ZdvQC@cube> (raw)
In-Reply-To: <3311358.aeNJFYEL58@rogueboard>
On Friday 6 September 2024 10:10:47 BST Michael wrote:
> On Friday 6 September 2024 01:33:04 BST Peter Humphrey wrote:
> > On Friday 6 September 2024 00:21:31 BST Peter Humphrey wrote:
> > > I think I know what it is: the kernel's list of firmware blobs is empty.
> > > I
> > > don't know where they all went, but it shouldn't be too hard to find
> > > them.
> >
> > Indeed it was so. Now fixed and working fine.
>
> Without all requisite firmware for your graphics the Kwin compositor will
> fall back to software rendering. As you've experienced without hardware
> acceleration Kwin will eat up CPU cycles.
>
> Emerging sys-kernel/linux-firmware and configuring your system to use it
> fixes the problem by providing the necessary code for the graphics card to
> do the heavy lifting:
Yes, I know, and I had it set up from when I acquired the machine. The mystery
is why it was missing from my two most recent kernels.
--
Regards,
Peter.
next prev parent reply other threads:[~2024-09-06 9:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 6:32 [gentoo-user] Wayland and CPU load Peter Humphrey
2024-09-05 7:50 ` Michael
2024-09-05 12:47 ` Peter Humphrey
2024-09-05 14:43 ` Peter Humphrey
2024-09-05 19:00 ` Peter Humphrey
2024-09-05 21:29 ` Michael
2024-09-05 23:21 ` Peter Humphrey
2024-09-06 0:33 ` Peter Humphrey
2024-09-06 9:10 ` Michael
2024-09-06 9:45 ` Peter Humphrey [this message]
2024-09-06 10:41 ` Michael
2024-09-06 11:30 ` Peter Humphrey
2024-09-05 22:14 ` Mark Knecht
2024-09-05 15:08 ` Peter Humphrey
2024-09-05 16:27 ` Michael
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=12533769.O9o76ZdvQC@cube \
--to=peter@prh.myzen.co.uk \
--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