robclark 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
bryanodonoghue6 has joined #aarch64-laptops
broonie_ has joined #aarch64-laptops
adamcstephens_ has joined #aarch64-laptops
jlinton_ has joined #aarch64-laptops
robclark_ has joined #aarch64-laptops
enyalios_ has joined #aarch64-laptops
mani_s- has joined #aarch64-laptops
bamse_ has joined #aarch64-laptops
mjeanson has quit [resistance.oftc.net larich.oftc.net]
craftyguy has quit [resistance.oftc.net larich.oftc.net]
paddymahoney has quit [resistance.oftc.net larich.oftc.net]
mani_s has quit [resistance.oftc.net larich.oftc.net]
bryanodonoghue has quit [resistance.oftc.net larich.oftc.net]
spawacz has quit [resistance.oftc.net larich.oftc.net]
enyalios has quit [resistance.oftc.net larich.oftc.net]
robclark has quit [resistance.oftc.net larich.oftc.net]
einar has quit [resistance.oftc.net larich.oftc.net]
pundir has quit [resistance.oftc.net larich.oftc.net]
jlinton has quit [resistance.oftc.net larich.oftc.net]
leiflindholm has quit [resistance.oftc.net larich.oftc.net]
ardb has quit [resistance.oftc.net larich.oftc.net]
adamcstephens has quit [resistance.oftc.net larich.oftc.net]
dgilmore has quit [resistance.oftc.net larich.oftc.net]
broonie has quit [resistance.oftc.net larich.oftc.net]
bamse has quit [resistance.oftc.net larich.oftc.net]
jlinton_ is now known as jlinton
adamcstephens_ is now known as adamcstephens
adamcstephens is now known as Guest1939
ardb has joined #aarch64-laptops
mjeanson has joined #aarch64-laptops
craftyguy has joined #aarch64-laptops
einar has joined #aarch64-laptops
pundir has joined #aarch64-laptops
spawacz has joined #aarch64-laptops
dgilmore has joined #aarch64-laptops
leiflindholm has joined #aarch64-laptops
paddymahoney has joined #aarch64-laptops
craftyguy is now known as Guest1968
enyalios_ is now known as enyalios
robclark_ has quit []
robclark has joined #aarch64-laptops
rfs613 has quit [Ping timeout: 480 seconds]
rfs613- has joined #aarch64-laptops
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #aarch64-laptops
bamse_ is now known as bamse
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
echanude has quit [Ping timeout: 480 seconds]
<travmurav[m]>
William Goodspeed: the os still needs access to whatever LUN has the EFS (modem settings) partitoins since there is a daemon that relays them to the modem core. Can probably block the bootloader luns though
<travmurav[m]>
hexdump0815: any chance you'd have time to cleanup and submit whatever you /did/ get working? :)
jhovold has joined #aarch64-laptops
<jhovold>
dgilmore, steveej[m] (and anyone else): could you confirm that the dp hotplug detect issues you had since 6.8-rc1 are gone with 6.8-rc7 (or since my rc6 wip branch)?
<jhovold>
the resets on disconnect issue is still there, but the revert in rc7 appears to make hotplug itself work roughly as well as it did with 6.7
<jhovold>
steev: ok, thanks, looks like you're drive does not support L0s, so whatever error you're seeing are at least not related to that
<Jasper[m]>
jhovold: Someone mentioned that it worked better
<Jasper[m]>
It was @adamcstephens
<Jasper[m]>
<adamcstephens> "i just did some testing with..." <- This^, yesterday
<jhovold>
Jasper[m]: thanks, yeah, I saw his comment but seems he's not online
<jhovold>
currently
<steveej[m]>
jhovold: updating to 6.8-rc7 as i type so i can let you know later this morning.
<steveej[m]>
unrelated but notable: i've had very frequent (every few minutes) wifi drops on 6.7.0
<jhovold>
steveej[m]: are you running the latest ath11k fw?
<Guest1968>
sorry I assumed you were talking about x13s wifi xD
<steev>
i'd check kvallo's repo on github, sometimes he has some there that are still testing if you want to try latests
<Guest1968>
hmm ok, let me see if I can find that
<steev>
should be github.com/kvalo/ath11k-firmware or some such
<Guest1968>
I've always had latency/drop issues on wifi with this adapter, only "fixed" by disabling power_save, and it seems to only happen on select APs
<Guest1968>
I've seen various complains on lenovo forums, and fedora's bug tracker for this wifi adapter that seem to match my experience
<Guest1968>
steev: do you know which fw files ath11k loads for the QCNFA765?
<steev>
if it's the x13s, that's the wcn6855 ones
<steev>
i *hate* the qcom versioning of the wifi/bluetooth
<steveej[m]>
interestingly when i received the x13s with windows on it i couldn't connect to my wifi AP. when i switched to linux it worked so i didn't bother debugging wifi on windows. my AP is based on a bpi-r3 with hostapd.
<Guest1968>
thanks. yeah, not confusing at all /s lol
<steev>
but i think 37 is in the upstream firmware repo?
<steev>
he usually pushes there a few months before pushing to upstream
<Guest1968>
hmm I must have "36" installed
<steev>
it'll say in the dmesg output
<steveej[m]>
this is in my dmesg: ath11k_pci 0006:01:00.0: wcn6855 hw2.1
<steev>
should be more than that, try looking for SILICON
<Guest1968>
steev: I have to reboot to get that info, my dmesg is currently filled with these messages lol... "ath11k_pci 0006:01:00.0: msdu_done bit in attention is not set"
<steev>
also, fwiw, i did just see that ath11k had hibernation support posted yesterday
<steev>
i see that message too, but it's not as spammy as yours, apparently
<Guest1968>
I just want PM enabled with no dropouts :P
<Guest1968>
ya looking at my dmesg, that message shows up about once per 1-3 minutes
<jhovold>
my last comment was meant for steveej[m] (possible new regression in .37?)
<jhovold>
steveej[m]: have you tried disabling power_save as Guest1968 had to?
<steveej[m]>
i don't see the msdu_done message anywhere in the entire journalctl history
<jhovold>
me neither, depends on the AP
<steev>
Guest1968: fwiw, i see it here, connected to at&t fiber's wifi router
<steveej[m]>
a reboot fixes the wifi dropouts for me it seems
<steveej[m]>
i'm not sure when they come back. maybe after suspend, i'll try to observe that more precisely
<Guest1968>
does disabling PM "fix" it too? just curious
<steveej[m]>
i've tried just unloading and loading ath11k_pci and ath11k and then the wifi interface didn't even come back.
<steveej[m]>
Guest1968: i'll try it next time before i reboot. is that timing what you mean?
<Guest1968>
it might be unrelated to the issue I see, but I just do this to "fix" it without reloading the module or anything else: iw wlan0 set power_save off
<Guest1968>
is there some place more appropriate than the linux wireless ML for reporting this issue?
<steev>
ath11k or linux-wireless, or the bugzilla
<Jasper[m]>
<Guest1968> "I've always had latency/drop..." <- Me and @craftyguy had a similar issue with a similar fix
<Jasper[m]>
Across many firmware versions
<Jasper[m]>
I also installed iw which works kinda well, though I still haven't figured out how to make autoconnect work
hightower3 has joined #aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
matthias_bgg has quit [Ping timeout: 480 seconds]
matthias_bgg has joined #aarch64-laptops
bryanodonoghue6 is now known as bryanodonoghue
KREYREN_oftc has joined #aarch64-laptops
Guest1939 is now known as adamcstephens
<adamcstephens>
jhovold: i'm actually here, but apparently need to fix my bouncer to identify me
<adamcstephens>
i could not get the x13s to crash on rc7 when hotplugging
adamcstephens has quit [Remote host closed the connection]
adamcstephens has joined #aarch64-laptops
<adamcstephens>
if there's something specific you want me to test, just let me know
adamcstephens has quit [Remote host closed the connection]
adamcstephens has joined #aarch64-laptops
adamcstephens is now known as Guest2024
Guest2024 has quit [Remote host closed the connection]
adamcstephens_ has joined #aarch64-laptops
adamcstephens_ has quit [Remote host closed the connection]
adamcstephens_ has joined #aarch64-laptops
adamcstephens_ is now known as adamcstephens
echanude has joined #aarch64-laptops
hightower2 has joined #aarch64-laptops
<jhovold>
adamcstephens: and no hotplug detect issues at all? did you have such problems since rc1?
<jhovold>
external display is detected and comes up on first connect attempt (with rc7)?
hightower3 has quit [Ping timeout: 480 seconds]
<konradybcio>
fwiw i have no obvious issues on your rc7 jhovold
<konradybcio>
other than an odd crash-on-boot but it's rare
<konradybcio>
jhovold and jfyi i resolved my headphones issue and im ready to be a real user now ;)
hightower3 has joined #aarch64-laptops
<jhovold>
konradybcio: there should not be any crash on boot, however rare
<jhovold>
the only such issue I've seen is the one that the drm rework in rc1 exposed in the rpmhpd driver, and which has now been fixed
<jhovold>
do you have any patches on top of my rc7 branch?
<jhovold>
and have you really seen a crash with my rc7 branch since Monday?
hightower2 has quit [Ping timeout: 480 seconds]
<konradybcio>
I'm sure a crash on boot ("failed boot") happened at least once
<konradybcio>
I only have my two devicetree patches enabling eas and adding more thermal things
<jhovold>
hmm, hopefully related to those patches then, try gather some data if you hit it again
rfs613- is now known as rfs613
<jhovold>
like how it manifests itself (does the machine just reset)? or do you see something on the console?
f_ has quit [Ping timeout: 480 seconds]
<adamcstephens>
jhovold: yes i had problems with hard reboots on earlier 6.8 RCs. external display worked on first and every plug in.
<adamcstephens>
as mentioned before i did have a problem with xhci getting confused and the USB hub no longer being detected, even after replugging
<adamcstephens>
but that's clearly not drm related
<jhovold>
adamcstephens: ok, so you never had any issues with hotplug detect? "just" the resets on disconnect?
f_ has joined #aarch64-laptops
<adamcstephens>
i'll run some more tests, i still have a few kernels installed
<steveej[m]>
jhovold: hotplugging the dock with HDMI output worked 2/2 times on 6.8-rc7, thanks for the update!
jhovold has quit [Ping timeout: 480 seconds]
jglathe__ has quit [Remote host closed the connection]
jglathe_sdbox2 has joined #aarch64-laptops
<_[m]123>
on 6.8rc7 now, on boot -> no dpe through dock, then direct yes, now through dock immediately worked 🙂
<steev>
i wouldn't follow its instructions, just copy the files, but, i can understand why someone would
<steev>
debian doesn't symlink the directory, they symlink the files inside of it
<hexdump0815>
travmurav[m]: galaxy book go dts cleanup is not forgotten - just time and energy are currently too short for doing much in this area sadly
<_[m]123>
was anyway already on 37 yeah
<_[m]123>
I haven't had resets on boot anymore for a while
<_[m]123>
maybe it's subjective, but the lenovo logo screen takes longer than before
broonie_ has quit []
broonie_ has joined #aarch64-laptops
broonie_ is now known as broonie
<steev>
[16578.027950] wlan0: deauthenticating from d0:fc:d0:47:4d:48 by local choice (Reason: 3=DEAUTH_LEAVING)
<steev>
[16579.124876] PM: suspend entry (s2idle)
<steev>
[16579.148152] Freezing user space processes