public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 00:21:31 +0100	[thread overview]
Message-ID: <2953235.e9J7NaK4W3@cube> (raw)
In-Reply-To: <4347395.mogB4TqSGs@rogueboard>

On Thursday 5 September 2024 22:29:14 BST Michael wrote:

> At a simple level you can check this file for any obvious problem:
> 
> ~/.local/share/sddm/wayland-session.log
> 
> Your symptom could be related to software rendering used by the kwin
> compositor, as opposed to OpenGL.  Mesa with appropriate USE flags should
> provide what your graphics need.  Have a look in kinfocenter, or run:
> 
> qdbus6 org.kde.KWin /KWin supportInformation
> 
> and check the section under Compositor, Compositor Type is not showing
> Xrender or software rendering.

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.

> Beyond this I think you're into compiling stuff with debugging symbols and
> trying to understand where code fails:
> 
> https://community.kde.org/KWin/Debugging

Thanks to those who helped.

-- 
Regards,
Peter.





  reply	other threads:[~2024-09-05 23:21 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 [this message]
2024-09-06  0:33             ` Peter Humphrey
2024-09-06  9:10               ` Michael
2024-09-06  9:45                 ` Peter Humphrey
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=2953235.e9J7NaK4W3@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