ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
mbuhl has quit [Remote host closed the connection]
mbuhl has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump02 has quit [Ping timeout: 480 seconds]
davidinux has quit [Read error: Connection reset by peer]
davidinux has joined #aarch64-laptops
hexdump02 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
sally has quit [Read error: Connection reset by peer]
sally has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
baozich has quit [Remote host closed the connection]
baozich has joined #aarch64-laptops
davidinux has quit [Quit: WeeChat 4.3.1]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
krei-se- has joined #aarch64-laptops
krei-se has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
minecrell has quit [Quit: Ping timeout (120 seconds)]
minecrell has joined #aarch64-laptops
<bryanodonoghue> seeing a fair bit of ghosting on arch linux x1e with wayland on gnome and hyprland - looks like some kind of buffer switching problem per plane
<bryanodonoghue> OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.0.1-arch1.2
<bryanodonoghue> is there a missing mesa update ?
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE> I'm on the same mesa, not noticing anything weird on hyprland
<SpieringsAE> I do have that config tweak, don't know if it is still necessary
<SpieringsAE> render {
<SpieringsAE> explicit_sync = 0
<SpieringsAE> explicit_sync_kms = 0
<SpieringsAE> >
<SpieringsAE> }
<SpieringsAE> I believe that mr got accepted to fix it but don't know if it is already in the current hyprland version
<bryanodonoghue> hmm ok appreciated let me give that a go
<SpieringsAE> yeah this one I believe: https://github.com/hyprwm/Hyprland/pull/9398
<SpieringsAE> yeah thats 11 days after the last release so its not in yet
<SpieringsAE> bryanodonoghue: did it fix it for you on hyprland?
<anthony25> yep, I had glitches because hyprland on the last release didn't check if explicit sync was supported by the driver
<anthony25> and msm doesn't expose explicit sync
<bryanodonoghue> hmm it looks better now I think
<anthony25> so either you can disable explicit_sync in your hyprland config, or build Hyprland with this patch, or expose the explicit sync attribute in msm
<anthony25> (I wrote this patch for Hyprland)
<anthony25> msm supports explicit sync, but there was a bug in an older version of mesa that has been fixed since, so it has been disabled in the driver
<SpieringsAE> bryanodonoghue: it was night and day in some applications, halloy was barely usable without this fix, it flickered constantly
<SpieringsAE> for me at least
<anthony25> same, I use keepassxc in a scratchpad, and the pop-ups were flickering a lot
<anthony25> but this patch disable explicit sync if the driver doesn't support it, so "render.explicit_sync = 0" and this patch do the same thing
<robclark> another option would be to cherry-pick https://patchwork.freedesktop.org/series/145438/ on the kernel side, fwiw
<robclark> (that is in msm-next for v6.15)
<SpieringsAE> nice!
<bryanodonoghue> seems to do the same fix for me
<bryanodonoghue> I wonder if this will help with the ghosting i saw in gnome
ungeskriptet_ has joined #aarch64-laptops
ungeskriptet has quit [Ping timeout: 480 seconds]
ungeskriptet_ has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
<robclark> hmm, I hadn't seen any similar issues, or any issues, in gnome-shell wayland (f41).. but not quite sure what mean by ghosting?
<anthony25> robclark: ha you re-enabled explicit sync?
<anthony25> Nice!
<robclark> yeah, well the mesa fix was over a year ago.. so I decided enough time had elapsed.. if you are using an ancient mesa and bleeding edge kernel, that is a you problem ;-)
<anthony25> haha, I agree :p
<anthony25> and the distribution can always revert this if needed
<robclark> is this the ath12k issue that folks have been complaining about.. every now and then my laptop dies, and it seems to start with this:
<JensGlathe[m]> one of them
<JensGlathe[m]> apparently its a bunch
<jhovold> robclark: looks like this one: https://bugzilla.kernel.org/show_bug.cgi?id=219796
<robclark> ahh, could be.. I tend to notice it when I show up in the office.. which unsurprisingly has a different wifi network from home ;-)
<jhovold> steev, JensGlathe[m]: how many msdu_done warnings do you see per day roughly?
<JensGlathe[m]> Between 0 and 20
<JensGlathe[m]> Usually maybe 5
<jhovold> perhaps you can help me test a fix over the weekend then, will post in a bit
tudorel has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
tudorel has quit []
tudorel has joined #aarch64-laptops
tudorel has quit [Quit: WeeChat 4.3.1]
<bryanodonoghue> robclark
<bryanodonoghue> only happened once
tudorel has joined #aarch64-laptops
<robclark> huh, weird.. but does look like something is out of sync
chrisl has joined #aarch64-laptops
SpieringsAE has quit [Quit: SpieringsAE]
chrisl has quit [Ping timeout: 480 seconds]
<craftyguy> jhovold: no ath11k issues at all with your rc7 :)
<craftyguy> feel free to add my t-b
<jhovold> craftyguy: thanks again for testing, could you reply to the fix with your t-b?
<craftyguy> ohhh ya I see now that you cc'd me on it, sorry!
chrisl has joined #aarch64-laptops
laine__ has quit [Quit: (╯°□°)╯︵ ┻━┻]
laine has quit [Quit: (╯°□°)╯︵ ┻━┻]
<jhovold> craftyguy: thanks!
Kelsar has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
Kelsar has joined #aarch64-laptops
<JensGlathe[m]> Re WCN7850 crashes, NULL pointer derefs, and the like
<JensGlathe[m]> I sort of accidentally pulled the whole branch for [this patch](https://lore.kernel.org/all/20250226113118.7626-1-quic_lingbok@quicinc.com/), which were about 100 ath related commits, apparently most of them not in ath-next. Built it, tested it here, published as 6.14-rc7-2, and it seems actually the most stable fix for the WCN7850 mess. Reports on the Ubuntu Concept X1E discourse seem to concur.
<anthony25> Does it fix the bluetooth disconnections?
<JensGlathe[m]> never had any... didn't pay attention to it
<steev> jhovold: enough that i was willing to simply comment it out
<steev> but it's far greater than 5
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
cyrinux9 has quit []
cyrinux9 has joined #aarch64-laptops
tudorel has quit [Quit: WeeChat 4.3.1]
chrisl has joined #aarch64-laptops
<JensGlathe[m]> Fans of the Thinkbook are trying to go supersonic
JJMajor9 has joined #aarch64-laptops
JJMajor9 has quit [Ping timeout: 480 seconds]
jhovold has quit [Ping timeout: 480 seconds]
xroumegue has quit [Ping timeout: 480 seconds]
xroumegue has joined #aarch64-laptops