Hi!

I'm in the market for a new laptop and I'd like to consult with the community about what's being recommended on the year 2026.

This is a laptop that I intend to use for both playing games and using as a mobile coding platform so battery and horsepower are the main points that I'd take into consideration, prioritising battery power.

I do not care if it's otherwise bulky.

I am currently encountering issues with AMD hardware on my main machine so just having a guarantee that the hardware is not gonna flop on me would be a big plus.

All in all! Thanks for giving my post a read and any answer would be appreciated, specially in the 900€ range.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 2 points 10 months ago (5 children)

I went to the LTS version and it didn't really go away. I found that the issue seems to be worked on in here https://gitlab.freedesktop.org/drm/amd/-/issues/4765 which is very similar to what I'm having

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 10 months ago (4 children)

    Hmm. If you don't mind sharing, when you hit the problem, were you concurrently running a video game and an LLM on the card? That seems to be what the guy there was doing.

  • source
  • parent
  • hideshow 4 child comments
  • [–] [S] 3 points 10 months ago (3 children)

    Nope, just running the game. But I am running kde with a lot of fancy shit on and I'm switching kernels around and they all have the same issue. I might need to do my own issue. Tried, 6.18-zen,6.17-hardened, 6.12-lts. I'll try a few more kernels tomorrow but I'm a bit stumped

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 10 months ago (2 children)

    Hmm. Kinda a long shot, but if it's easy to reproduce and you're looking for switches to try throwing, the amdgpu driver does have a number of options.

    $ /sbin/modinfo -p amdgpu
    

    Might try rebooting, and at GRUB, editing the kernel command line, and disabling some features, seeing if things magically go away.

    Like, the bug report there is talking about some ring timeout. Maybe irrelevant, but could try amdgpu.async_gfx_ring=0 on the kernel command line.

  • source
  • parent
  • hideshow 2 child comments