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
<jdb[m]>
deathmist: sure, with pleasure, feel free to ping me again if I forget (it's now on my TODO list)
<tobhe[m]>
jdb: I am looking forward to that! Probably one of the most requested machines on discourse
<steev>
tobhe[m]: after manually adding the oled variant to the db, it does the correct thing for me - that said... audio doesn't work, should some of the sound modules be in the initramfs? because i'm seeing some but not all, and snd-x1e80100 is failing with -22 - oddly there is no deferred devices
<d0pefish>
deathmist: that was me about an hour ago :)
<steev>
so far though, i've been able to reboot a few times without having it go back to the grub menu
<alexVinarskis[m]>
steev: do you have snd_soc_x1e80100.i_accept_the_danger in cmdline? Ubuntu flavor kernels need that, else they error out, that may be the reason for -22. But even without -22 no sound here as well.
<tobhe[m]>
oh right there's that. but I assume if it worked on 6.14 you might have that already
<steev>
Oh, interesting - I don’t think I had that on 6.14 either
<steev>
On my own 6.16.0-rc6, aside from the weird wcd938x module not loading, I do get audio, so it *should* work
<steev>
i see the same as alex, no audio with the cmdline option added - no deferred devices
<tobhe[m]>
same here actually. Didn't notice it because I don't use audio much
<steev>
on my x13s, when audio was being brought up, i added a desktop-login addition to the sound theme so that it would play audio on login, and i'd know quickly if it was broken :)
<steev>
the funny thing is... that's the sound that played when you would test if audio was working for the game, so it makes it even better
chrisl has joined #aarch64-laptops
<steev>
but yeah, i just downloaded it with ytdlp, converted to oga, and then... had to put it somewhere in my ~ because i could not for the life of me get it to work in /usr/share
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
patrickm has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
patrickm has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
patrickm has quit [Read error: Connection reset by peer]
chrisl has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
patrickm has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
tobhe 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]
chrisl has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
sally has quit []
sally has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
davidinux has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
zetam has quit [Quit: going out!]
eluks has quit [Remote host closed the connection]
eluks has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
icecream95 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<icecream95>
Nice to see people discussing *95 things.
<icecream95>
People seem to keep thinking that the 95 in my username is the year I was born, rather than the first version of Windows that I used.
<icecream95>
(Not that I can remember the occasion.)
<icecream95>
An ASPM regression in 6.15 would definitely explain why I was seeing higher power consumption with newer kernels
<icecream95>
deathmist: slbounce has worked fine for me in the past but I haven't tested it recently. I might try again tonight
chrisl has joined #aarch64-laptops
<JensGlathe[m]>
Hmm just booted 6.16-rc6 on the HP Omnibook and sound is still there
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<steev>
oh that sounds terrible :P
chrisl has joined #aarch64-laptops
<JensGlathe[m]>
There’s no trust in this world
chrisl has quit [Ping timeout: 480 seconds]
<HdkR>
icecream95: I thought you just loved ice cream 95/100, best food ever.
<steev>
valpackett: that patchset should be in -rc6 already
<steev>
oh wait
<steev>
no, that part isn't
<steev>
only 4 of the 6 look like they are in -rc6
chrisl has quit [Ping timeout: 480 seconds]
<icecream95>
HdkR: Well I am in the country with the highest per-capita ice cream consumption, so predicting that would be reasonable
<HdkR>
:D
<deathmist>
icecream95: certainly take backup of the tcblaunch.exe, maybe it'll work for me as well if I try with the copy you have
<deathmist>
currently on latest UEFI 366 fwiw
chrisl has joined #aarch64-laptops
<steev>
alexVinarskis[m]: kicked off a build, but i need to head to bed
<icecream95>
deathmist: Which version of tcblaunch.exe are you using? I tested current slbounce git with the 26100.4351 tcblaunch.exe from WinSxS and sltest.efi still works (with 366 firmware as well)
chrisl has quit [Ping timeout: 480 seconds]
<deathmist>
icecream95: I mentioned the sha256sums a few days back but they were 6ebd501a16af0f66117ff822abaae5f255f822dcc566c3cafb16e3fb62953aba & f6fc6ac7b408b01ca79f53a5f3d72b907c5a580ea7db6c4827d37b4e4a858aed
<deathmist>
first from original windows.old install and latter from canary insider 27891.1000 (both sourced from system32) tested with git slbounce as well as the latest release artifacts, guess I'll check the WinSxS ones too
<icecream95>
I am using the efi-shell-aa64 Ubuntu package, chainloaded from grub
<travmurav[m]>
I suddenly recall some efi shell builds were messing with ebs
chrisl has quit [Ping timeout: 480 seconds]
<icecream95>
deathmist: I can still get sltest to work when using that shell binary
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<jdb[m]>
deathmist: thanks to d0pefish: <- ah looks like someone already did it
<jdb[m]>
I didn't realize that the Surface Laptop 7 (romulus) 2 models haven't been added yet
chrisl has joined #aarch64-laptops
pabs has quit [Remote host closed the connection]
<jdb[m]>
For the Surface Pro 11, let's keep in mind that there are a few variants (OLED vs. LCD, X Elite vs. X Plus), so far the devicetree we're proposing upstream is for the X1E OLED variant
pabs has joined #aarch64-laptops
<jdb[m]>
as this is the model both d0pefish: and I have
<deathmist>
icecream95: tried with the plucky efi-shell-aa64 binary and yeah same result including when chainloaded from grub instead. I assume your tcblaunch.exe hash matches one of mine or?
chrisl has quit [Ping timeout: 480 seconds]
<deathmist>
jdb[m]: hm sure, added a note to the tracking issue regarding that
<travmurav[m]>
I guess yall should hope microsoft doesn't rotate signing keys in the next version of mssecapp
<deathmist>
time to never boot windows or update firmware :)
<deathmist>
and hope qcom makes booting EL2 natively a thing starting with X2
* travmurav[m]
sincereely doubts it will be fixed in x2
<travmurav[m]>
tbh doubt it will be fixed in x3
<\[m]>
Jens Glathe I must say the install dance failed so far, windows keep overwriting the bootloader -_- weren't you one of the view that got systemd boot working? I honestly never even used but in dualboot it seems impossible?
<JensGlathe[m]>
oof.
<JensGlathe[m]>
yes I got sd-boot running - still shivering
<\[m]>
*few 💤
<angelthorns>
deathmist: oh yeah what is the problem regarding EL2 by the way, just got a snapdragon laptop, what is the reason linux cant use it without giving up other features?
<\[m]>
I think maybe grub and then add bootloader entry in windows ? or nuke it ugh, do you need still for firmware updates? not sure if that extraction-way worked consistently
<JensGlathe[m]>
I have the same on the devkit - using an sdxc to boot with windows
<deathmist>
angelthorns: you get thrown under EL1 of Gunyah by default, https://github.com/TravMurav/slbounce explains the dance windows does, and it seems they've just locked it down to be truly Windows-only going forward
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
but the slim5x doesn't support booting from sdxc, ts pcie3 connected
<JensGlathe[m]>
s/ts/its/
<deathmist>
mainline seemingly also rejected the proposal to hack the Gunyah-specific interface to be exposed via KVM so it may be a per-project task to make them specifically target gunyah instead, no idea how that'll pan out so ig I'll just wipe my disk and make the machine Linux-only for the time being
<angelthorns>
what the hell qualcomm :(
<valpackett>
crosvm supports gunyah (unsurprisingly), it's one of the best vmms out there imo..
<valpackett>
but afaik we don't have the gunyah driver in mainline linux?
<deathmist>
angelthorns: unfortunately this is nothing new, no EL2 boot on qcom has been a longstanding pet peeve of mine which depending on the upcoming aarch64 laptop/desktop competition is guaranteed to make me look elsewhere provided there's proper mainline support
<angelthorns>
yeah
<lynxy>
\: oh, it's a systemd-boot issue? i've always used it, and i've always been frustrated by windows messing up dual boots when i can be bothered to try- i ended up wiping windows completely a couple of days ago after experiencing io1_initialization errors out of the blue..
<travmurav[m]>
imagine buying hardware where only Microsoft can decide whether you can use half of your ram or not
<angelthorns>
i bought a lenovo yoga slim 7x recently mostly for programming/ stuff that isnt too complex, and its a good laptop i like it, just a shame there are issues like that but i dont think its a complete deal breaker
<angelthorns>
not for my usage*
chrisl has joined #aarch64-laptops
<deathmist>
it's not that big of a deal, but it's just the longstanding stance of "you can't do that on your hw because we say so" which really pisses me off
<lynxy>
closely followed by "you're not allowed to do that for 'security reasons' :pensive:"
<lynxy>
why do you get to decide- it's my device
<angelthorns>
yeah it is the attitude aswell yeah, they did promise "first class linux support" but yknow, qualcomm
chrisl has quit [Ping timeout: 480 seconds]
<icecream95>
Guess it's time to start looking for vulnerabilities in tcblaunch/Hyper-V/EL3/IOMMU etc. then?
<tobhe[m]>
alexVinarskis: good to know, I found that yesterday and backed it out but didn't have time to build a test kernel yet. Thanks Val Packett!
<Jasper[m]>
@SpieringsAE same, but I'm hoping they continue trying to upstream their stuff and maybe even improve their ACPI tables
chrisl has joined #aarch64-laptops
reng has quit [Ping timeout: 480 seconds]
reng has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<icecream95>
Oh fun, not another "freeze for 30 seconds then reboot"...
jglathe_angrybox 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]
chrisl has joined #aarch64-laptops
<lynxy>
ohh my b580 might actually be useful :eyes:
chrisl has quit [Ping timeout: 480 seconds]
<anonymix007[m]>
SpieringsAE, lynxy: probably won't work on B580 as per this comment:
<anonymix007[m]>
> For SRIOV to work on BMG also correct, SRIOV-enabled IFWI must be flashed on the BMG card.
<lynxy>
i had assumed as much x)
<lynxy>
but we're a step closer
<anonymix007[m]>
I assume this will be limited to "professional" cards like B60, so this step is towards a wall (unless firmware is interchangeable)
chrisl has joined #aarch64-laptops
<\[m]>
> I have the same on the devkit - using an sdxc to boot with windows
<\[m]>
you mean your bootloader is on an sd card?
ungeskriptet 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]
ungeskriptet has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<JensGlathe[m]>
The one I use when I want to use Windows, yes. Sounds odd, but prevents the other EFI on the SSD from being tampered with. Maybe also possible with USB key
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<d0pefish>
jdb[m], deathmist: following on from documenting the SP11 hwids for dtbloader, I've been testing dtbloader and you're probably not going to like this: the SP11 doesn't seem to have a SHA1 implementation in the UEFI, so dtbloader fails with an 'Unsupported' error. If I hack in a SHA1 implementation borrowed from OpenSSL, I can get a match and it
<d0pefish>
loads the DTB. But then systemd-boot fails to load vmlinuz with another 'Unsupported' error. :(
<JensGlathe[m]>
only uncompressed image?
ungeskriptet has quit [Ping timeout: 480 seconds]
<\[m]>
what do you lose in terms of functionality again when you run el2 dtb?
<\[m]>
like no sound?
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
no sound via internal speakers /
<JensGlathe[m]>
if you manage to keep the lite firmware up from power-on, you actually keep dp altmode and battery loading as it seems
<d0pefish>
JensGlathe[m]: That was it :) it boots an uncompressed kernel fine now
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
icecream95 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
chrisl has quit [Ping timeout: 480 seconds]
craftyguy has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
ungeskriptet has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
sgerhold has quit [Quit: :/]
minecrell has quit [Quit: :/]
sgerhold has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<bylaws>
robclark: hmm I think it's a separate issue I'm having, with anything using x11
<bylaws>
Ghidra and wine UI elements are black until I mouse over, and then flicker back and forth
<bylaws>
And glxgears goes black and stutters for a brief period when resizing
<robclark>
hmm, haven't seen anything like that
<robclark>
maybe try a different compositor?
chrisl has quit [Ping timeout: 480 seconds]
ungeskriptet has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
pbrobinson has quit [Remote host closed the connection]
pbrobinson has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<AlekseiNosachev[m]>
<jdb[m]> "For the Surface Pro 11, let's..." <- And let's not forget the 5G lineup
<steev>
alexVinarskis[m]: yeah, reverting that does seem to work here as well, also just increasing the playback_max_period_size back to 65536 (leaving min 6144) works as well
<alexVinarskis[m]>
great, thanks for confirming. Easy fix to tobhethen (if its not already included in the monring build?)
<tobhe[m]>
already included but launchpad seems to have some technical problems today
<tobhe[m]>
so I'm still waiting for the build to get scheduled
<tobhe[m]>
a fix for flash-kernel is also in the queue
SpieringsAE has quit [Read error: Connection reset by peer]
<steev>
and i have mine plugged in and powered it off when you asked the question
<JensGlathe[m]>
Using X11 here because of sporadic reboots
<steev>
JensGlathe[m]: i only see those with yours
<steev>
i have not had mine spontaneously reboot or lock up
<JensGlathe[m]>
hmm interesting
<JensGlathe[m]>
On X11 I don't have much of these
<JensGlathe[m]>
like, none
<JensGlathe[m]>
But I didn't activate the T14s yet
<steev>
i'm on wayland (but i'm also on the oled 64gb variant)... still waiting on bamse to get an answer from the firmware guys :(
<steev>
s/guys/peeps
<mani_s>
steev, same behavior on johan's 6.16-rc4 branch
<steev>
that is 2 weeks old sir. rc6
<mani_s>
trying -rc6 now, but I couldn't spot any obvious patch in the branch
ravikant_ has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<mani_s>
steev, same behavior even with -rc6
<kuruczgy_>
travmurav[m]: What's mssecapp? How careful should we be with windows updates, could one (irreversibly) break our existing working tcblaunch.exe-s?
<mani_s>
I'm wondering if it is the BIOS version or something else. definitely not kernel as we've found out
<travmurav[m]>
kuruczgy_: mssecapp is a TZ trustlet that runs inside qcom's tz
<mani_s>
I'll check internally tomorrow
<travmurav[m]>
basically OEM signs the trustlet with their key, so it runs in firmware, and contains windows signing keys
<travmurav[m]>
which is how chain of trust OEM->Microsoft happens
<travmurav[m]>
can probably just look at the last illustration
<travmurav[m]>
as far as keys are concerned, I doubt OEMs would update the trustlet on x1 devices, but if MS issues a new one for x2 bsp, then they could as well deny older versions of tcblaunch.exe
<kuruczgy_>
do we know where this trustlet is stored? disk, uefi firmware, or some other non-volatile memory?
<JensGlathe[m]>
Yeah. That's in the future, though.
<travmurav[m]>
somewhere on spi flash (so inside firmware package), but it's signed
<JensGlathe[m]>
I root for the automotive team, break the secrecy
<travmurav[m]>
so you can't replace it, at least unless you have a device with hardware sb-off (though seems like even that is not as useful nowdays due to double signing)
<kuruczgy_>
travmurav[m]: Hm so really this could in theory even come through an UEFI update, even without windows ever being booted?
<travmurav[m]>
yes
<travmurav[m]>
all WoA devices to date are vendor locked to Microsoft
<kuruczgy_>
I do wonder if doing that is even legal in the EU...
chrisl has quit [Ping timeout: 480 seconds]
<Jasper[m]>
They never got shit for it with the RT devices hahahaha
<Jasper[m]>
neither does Apple with the iPhones
<Jasper[m]>
(not on an OS level anyway)
<steev>
mani_s: it does seem as if x1e devices can be.... special
<maz>
I never thought I'd say that, but I'm quite pleased that the devkit will never see any update.
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
ungeskriptet has joined #aarch64-laptops
<steev>
mani_s: btw, the ath stuff you sent earlier, does that need the aspm fixes you sent earlier or replace?
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
ravikant_ has quit [Ping timeout: 480 seconds]
<kuruczgy_>
EL2 booting seems to be broken for me on 6.16-rc*, screen goes black or initrd cannot find the root disk. Seems fine on 6.15, has anyone else had issues?
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<maz>
kuruczgy_: all good for me, but I'm strictly using upstream, no additional patches (other than my own patch queue).
<maz>
I also haven't updated the DT in... a very long time.
chrisl has quit [Ping timeout: 480 seconds]
<steev>
hm
<steev>
JensGlathe[m]: on your t14s, what kind of numbers do you get when you run https://github.com/andersson/mybw ? i'm seeing about half the speed as the X13s here on my T14s
<steev>
yeah, those are the kind of numbers i'd expect, and tobhe sees them...
chrisl has joined #aarch64-laptops
<JensGlathe[m]>
yes, read
<JensGlathe[m]>
but Linux will take a day or 5 until I have some time
<steev>
double checked that it wasn't the cutmem/grub badram stuff, still same numbers with 64gb
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
odd
chrisl has joined #aarch64-laptops
<steev>
tobhe[m]: what model is yours?
<tobhe[m]>
this is a 21N2ZC5QUS with 64GB and LCD
<steev>
i have a 21N1CTO1WW
<deathmist>
kuruczgy_: I think I'm also seeing that, haven't got slbounce with EL2 dtb booting 6.16 properly on X1E Vivobook myself yet, though I made a 6.15 EL2 entry as well with the dtbo applied on top but basically same result
chrisl has quit [Ping timeout: 480 seconds]
<kuruczgy_>
Hm... maybe now I need to use the upstreamed -el2 dtb-s? I am still only applying the old dtbos
<deathmist>
I see a bit of kernel log before indefinite blank screen and that's it, ctrl+alt+delete reboots at least
<deathmist>
kuruczgy_: I'm seeing this on the 6.16 -el2 dtb as well
<kuruczgy_>
Ah ok. And for you 6.15 is also borked? For me 6.15 is fine.
<tobhe[m]>
Can't think of anything special in my setup either. Ubuntu 25.04 with the ppa kernel that broke audio
<kuruczgy_>
Seems like another bisect angle... But I don't have good bisect setup right now, probably I should figure that out first.
<steev>
checked with the ubuntu kernel as well, and same numbers here (roughly) - definitely not the numbers you see, nor the numbers that jens sees on the t16
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
kalebris has quit [Remote host closed the connection]
kalebris has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has quit []
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<jdb[m]>
For anyone using the ThinkPad X13s with an external screen, does the built-in display switch off when you close the lid?
<steev>
dunno, the lid is closed :P
<steev>
i can't check at the moment as i put my external display away yesterday so i had more room on my desk :(
<jdb[m]>
:-) no worries, I'm curious because I can still see the light being emitted so it's not working for me
<jdb[m]>
I would like to know if this is a known issue or simply a problem in my own setup
<jdb[m]>
I'm using Gnome/Wayland on Debian Trixie
<jdb[m]>
even trying to disable the built-in screen from the Gnome Control Panel doesn't work for me (without closing the lid I mean)
<jdb[m]>
I still have a picture displayed, I can't click on the confirmation window, so the settings are automatically reverted back after X seconds
<kuruczgy_>
deathmist: re 6.16 el2 issue: it seems that downgrading only the device tree to the 6.15 one resolves the issue for me. Were you also testing with the 6.15 device tree?
<deathmist>
hm I should've been but I've also got dtbloader in the situation, perhaps I'll try excluding it from the equation in a bit to see if anything different happens
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
ungeskriptet_ has quit [Ping timeout: 480 seconds]
ungeskriptet has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<steev>
jdb[m]: did you try moving the settings window to the external display first?
chrisl has joined #aarch64-laptops
Daanct12 has joined #aarch64-laptops
Danct12 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<valpackett>
audio testing update: PLAYBACK_MIN_NUM_PERIODS patch does not improve anything (checking mainly headphone jack distortion)
<tobhe[m]>
I also got around to test my build with the change backed out and can report that sounds does indeed work again
<tobhe[m]>
updates should show up soon
<steev>
but the change is needed due to distortion with pulseaudio?
<steev>
asking because i followed the link in the bug tracker but couldn't quite follow why the change was requested
<valpackett>
i haven't tested pulse but with pipewire i've *never ever* gotten any underruns anywhere
<valpackett>
the ubuntu hack patch predates the landing of the rest of the underrun related series
<valpackett>
i just tested the playback constants from there and it doesn't improve anything
<steev>
i haven't tested headphones, but the playback itself was fine with 5/6 "applied" (manually changed because i was lazy)
<valpackett>
speakers and mic are fine for me without those changes
<valpackett>
and headphone is still terrible, i.e. no change
<valpackett>
it's probably just some kind of settings tuning somewhere that i don't know how to access?? because the badness is volume dependent
<valpackett>
there's a veeery narrow volume range where the headphone output is okay, and below it all goes into the left channel while above it's all distorted to hell