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
KREYREN_ has quit [Remote host closed the connection]
<agl>
steev: What version have your newest kernel?
<steev>
whatever is in the linux-6.7.y
<steev>
swamped with work, haven't had a chance to look at 6.8 stuff; technically i applied patches, but never tested so never pushed
<agl>
I'am back at home from the hospital. I have 6.7.3 on my x13s. Its two days ago that you have made a new version on linux-6.7.y. I will compile tomorrow your newest kernel. Now I'am going to bed. It's 01:23 o'clock here in Europe/Germany. Good night.
<_[m]123>
much appreciated all the work done, it's come a long way ❤️
minecrell has quit [Quit: Ping timeout (120 seconds)]
minecrell has joined #aarch64-laptops
sjs_ has joined #aarch64-laptops
sjs_ has quit [Read error: No route to host]
sjs_ has joined #aarch64-laptops
sjs_ has quit [Ping timeout: 480 seconds]
KREYREN_oftc has joined #aarch64-laptops
jelly has quit []
jelly has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
abcdw has quit [Write error: connection closed]
abcdw has joined #aarch64-laptops
sjs_ has joined #aarch64-laptops
systwi has quit [Ping timeout: 480 seconds]
systwi has joined #aarch64-laptops
systwi has quit [Remote host closed the connection]
systwi has joined #aarch64-laptops
jglathe_x13s has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
<HdkR>
I saw sc8280xp has tsens for the GPU wired up now. Does that let it thermal throttle now, or does it need more for that?
<jhovold>
HdkR: not yet, there's one more piece missing
<HdkR>
Alright
<HdkR>
Is it exposed to userspace so it can be read?
<jhovold>
yes, and there is a critical trip point so it should shut down the machine too if you hit that limit I think
<jhovold>
gpu_thermal-virtual-0
<jhovold>
Adapter: Virtual device
<jhovold>
temp1: +27.5°C
<HdkR>
I've definitely hit those before without the tsens wired up :D
<HdkR>
Nice, so once there is a way to get the GPU device from fdinfo, I'll be able to expose that information through nvtop
<jhovold>
HdkR: I know you mentioned that, but I think that may have been via the CPUs getting too warm
<HdkR>
oh, haha. GPU baking the CPU cores, that's funny
sjs_ has quit [Ping timeout: 480 seconds]
abcdw has quit [Remote host closed the connection]
abcdw has joined #aarch64-laptops
abcdw has quit [Remote host closed the connection]
abcdw has joined #aarch64-laptops
abcdw has quit [Remote host closed the connection]
abcdw has joined #aarch64-laptops
iivanov__ has quit [Remote host closed the connection]
jglathe_sdbox2 has quit [Remote host closed the connection]
jglathe_sdbox2 has joined #aarch64-laptops
jglathe_sdbox2 has quit [Remote host closed the connection]
<jhovold>
HdkR: correction, that should actually be the skin temperature getting too high
<HdkR>
jhovold: I see, I don't think I'm running the patch that raised Skin_T up to 65c anymore
<jhovold>
the critical skin temperature trip point it set to 73 degrees, so that's when you'd see the shutdown
<jhovold>
the CPUs would throttle at 55, but that doesn't help when you're torturing the GPU currently
<jhovold>
or rather, throttling the CPUs is not sufficient
iivanov has joined #aarch64-laptops
jglathe_sdbox2 has joined #aarch64-laptops
jglathe_sdbox2 has quit [Remote host closed the connection]
jglathe_sdbox2 has joined #aarch64-laptops
jglathe_sdbox2 has quit [Remote host closed the connection]
sjs_ has joined #aarch64-laptops
<jhovold>
alsa-ucm-conf 1.2.11 has now been packaged by arch, finally bamse will have audio
<jhovold>
(as long as he uses pulseaudio... ;)
f_ has quit [Ping timeout: 480 seconds]
jglathe_sdbox2 has joined #aarch64-laptops
<HdkR>
jhovold: Yea, Since I'm running games I'm constantly hammering the GPU since it can't keep up
<HdkR>
1200p is a bit much for a690 and AAA games
<Bioxvirizm-x13s[m]>
<jhovold> "alsa-ucm-conf 1.2.11 has now..." <- Hello. Do I understand correctly that now we have fully working sound with a microphone?
<jhovold>
yes, with pulseaudio, there are still unresolved issues capturing sound with pipewire
f_ has joined #aarch64-laptops
<_[m]123>
what games you run?
iivanov has quit [Remote host closed the connection]
<Segfault[m]>
<jhovold> "the CPUs would throttle at 55..." <- do we know what temperature it starts to throttle at in windows? iirc even 55 is on the high side of what's normally allowed for surface temperatures
sjs_ has quit [Ping timeout: 480 seconds]
<jhovold>
Segfault[m]: I think we got the current limits from lenovo so it should be the same as on Windows
<jhovold>
the actual skin temperature may be lower (or higher I guess) than the sensor reading
<jhovold>
I don't think anyone has actually measured the surface temperature
<_[m]123>
do they literally mean, the temp at which you'd burn your knees?
<_[m]123>
no more graphical issues now on kde 6.7.3+ weirdzz
<jhovold>
_[m]123: we want to make sure we throttle the CPUs (and GPU) before the the surface gets that warm
<jhovold>
we currently start throttling when the sensors we use for this hits 55 degrees C
<jhovold>
sensor*
<Jasper[m]>
_[m]123: Hmmm
<Jasper[m]>
Interesting
<_[m]123>
ofc meanwhile they're back haha
<_[m]123>
and not seeing wireless connections
<_[m]123>
mullvad vpn still working though
<exeat>
Some time ago I measured the bottom cover temperature with a thermal camera and the sensor reading was spot on (N=1 and all that)
<_[m]123>
ill boot 6.7.1
<Jasper[m]>
@dgilmore any idea what Fedora's policy is regarding kernel upgrades on Rawhide? It's been stuck at "6.8.0-rc0" since January 12th.
<_[m]123>
vpn working
<Jasper[m]>
I'd love to have working audio 😅
<Segfault[m]>
Jasper[m]: i'm not sure about when they update the package but i do know the git repo is on a commit from after 6.8-rc3 now
<_[m]123>
audio worked before though
<Jasper[m]>
Segfault[m]: Exactly why I asked if he knew what their policy is. I'm sure there's a reason for it
<Jasper[m]>
_[m]123: Default setup for fedora is extremely high gain on the 3.5mm jack and very soft speaker volume
<Jasper[m]>
In the meantime alsa-ucm-conf got updated and now it misses the needed kernel changes
<jhovold>
exeat: nice, thanks!
sjs_ has joined #aarch64-laptops
<Jasper[m]>
* kernel changes to make everything function safely
<_[m]123>
werid, mullvad says connected but no internet
<_[m]123>
and stopping the gui didn't kill the daemon which it does on other kernel
<_[m]123>
I wish I knew more about these kernel modules
<dgilmore>
Jasper[m]: there will be a rc3 today. There is some automated was that runs on every kernel build, it was hitting a bug in the driver for the video card they use in the vm
martiert has quit [Quit: WeeChat 4.2.1]
<Jasper[m]>
dgilmore: Interesting, thanks for the heads up!
<_[m]123>
ok still get input lag on 6.7.1 too
<_[m]123>
but I can enable ufw 🙂
<_[m]123>
but so can I build 6.8 rc3 with the 6.7.1 config?
<jhovold>
_[m]123: essentially, yes
<jhovold>
copy laptop_defconfig from steev's 6.7 branch and put in under arch/arm64/configs
<jhovold>
and run make laptop_defconfig
<_[m]123>
I did build rc3 with laptop_defconfig before
<_[m]123>
and it booted to black screen but meanwhile I've had that too on your config
<_[m]123>
reboot fixed, I lacked perseverance
<_[m]123>
let me try
<jhovold>
there is a regression in the display drivers in 6.8-rc1 that can lead to no display on boot
<jhovold>
I've hit that twice now
<jhovold>
But there's a clear indication of this in dmesg when this happens
<_[m]123>
oh ok yeah, me too, twice
<_[m]123>
you got to tty?
<jhovold>
[drm:drm_bridge_attach [drm]] *ERROR* failed to attach bridge /soc@0/phy@88eb000 to encoder TMDS-31: -16
<jhovold>
nope, but I can ssh in
<_[m]123>
oh yeah
<_[m]123>
you get an ip before login?
<jhovold>
i use a usb ethernet adapter
<jhovold>
which gets a dhcp lease on boot
sjs_ has quit [Ping timeout: 480 seconds]
<_[m]123>
I can burn my skin rn on the laptop lol
<_[m]123>
anyone wants to buy x13s 😉
<jhovold>
_[m]123: have you verified that thermal throttling is enabled in you config, it's possible to disable it if you're missing the required drivers
<janrinze>
jenneron[m]: what was the change that helped booting fron sdcard vs usb boot?
<jenneron[m]>
janrinze: idk
<_[m]123>
I understood from ema that it's not enabled in experimental debian kernel
<bamse>
jhovold: scary, but here goes pacman -U linux-6.8.rc3.xz && pacman -Syu && reboot
<jhovold>
my x13s indeed gets warm, but I haven't actively tried to burn my fingers by holding them there ;)
<jhovold>
bamse: woho!
<_[m]123>
it's gotten cooler now, but this skin temp got me thinking
<jhovold>
bamse: make sure you're not using pipewire, i think that may be the default on arch these days
<bamse>
jhovold: i'm not cool enough for that
<jhovold>
good
<bamse>
jhovold: fun, my headphone volume started at 100%, my speaker was at 155%
<ema>
_[m]123: I'll open a merge request to get the change in sid today and keep you posted
<jhovold>
bamse: yeah, you may have some old state that should ideally have been cleared out
<jhovold>
can be used to restore the alsa state, but you may also need to delete your pulseaudio config
<jhovold>
e.g. rm ~/.local/pulse/*
<jhovold>
sorry, rm ~/.config/pulse/* i meant
<jhovold>
and that's after stopping pulseaudio... audio is fun
<_[m]123>
ema: it's all good - I need to run 6.8-rc3 anyway seemingly
<_[m]123>
booted not in black screen, check
<jhovold>
clearing out as described above, should bring headphone level to 28% and speaker to 89%
<jhovold>
but you can just set it to that manually too of course
<jhovold>
it's good to clear out the alsa state though, as that speaker codec bug I fixed, may have left the digital gain setting either much too low or too high
jglathe_sdbox2 has quit [Remote host closed the connection]
<_[m]123>
[ 322.026408] usb 1-1.1.1.2: 2:2: cannot get freq (v2/v3): err -32
<_[m]123>
it's so weird because the laptop recognises and uses external screen but somehow it's not sending the signal ?
jglathe_sdbox2 has joined #aarch64-laptops
jglathe_sdbox2 has quit [Remote host closed the connection]
jglathe_sdbox2 has joined #aarch64-laptops
<_[m]123>
changed usbc input port, works
<jhovold>
hmmm, some sound artefact on right speaker after resetting alsa state, plugging in headphones and unplugging them made the problem go away
<jhovold>
feared I'd damaged my speakers there for a moment
* jhovold
adds a note to the evergrowing todo list
<janrinze>
jenneron[m]: okay. I have this weird issue. After I ran pmOS with your image from USB stick, my Debian image on SDcard boots again. But after a shutdown of Debian (SDcard) it won't boot from the sdcard again (Not a valid image). My guess is that pmOS sets some flag that makes it okay to reboot but Debian does not.
<_[m]123>
thanks @ema 🙂
<_[m]123>
<jhovold> "adds a note to the evergrowing..." <- > * <@_oftc_jhovold:matrix.org> adds a note to the evergrowing todo list
<_[m]123>
constantly advise people to put in a jack and disconnect hahaha
<_[m]123>
so mullvad vpn is working 🎉
<jhovold>
_[m]123: that's just the temporary workaround for now, and should only be needed after clearing the alsa state (i.e. once)
<jhovold>
unfortunately, it may also affect first boot...
<Jasper[m]>
Hmm weird, dgilmore, my headers update, but the kernel package doesn't
<Jasper[m]>
And it looks like the new build got released according to packages.fedoraproject.org
<dgilmore>
Jasper[m]: looks like todays compose failed. headers came out a few days ago, they are a seperate RPM
<Jasper[m]>
Ah, I figured they'd update in lockstep
jglathe_sdbox2 has quit [Remote host closed the connection]
hightower4 has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
hightower3 has joined #aarch64-laptops
hightower4 has quit [Ping timeout: 480 seconds]
<bamse>
jhovold: got side tracked, so that reboot took 6 hours...
<bamse>
jhovold: first reboot the machine once again crashed around the time of the login prompt (or when i get display or whatnot)
<bamse>
jhovold: then i realized that you said i might need another reboot for the ucm stuff to kick in
<bamse>
jhovold: and no i have some sweet music in my speakers :)
<jhovold>
bamse: was that with or without external display connected?
<jhovold>
but glad to hear you got audio finally
<jhovold>
the alsa-ucm-conf package was the last one I had built myself
<jhovold>
not counting the kernel obviously...
<_[m]123>
eDP mysteries 🙂
jglathe_sdbox2 has joined #aarch64-laptops
<jglathe_sdbox2>
is eDP the culprit? external monitor would be USB-C
<_[m]123>
that's just the connector no?
<_[m]123>
now encountering some weirdness - nm applet not showing wireless networks
<_[m]123>
but I am connected lol
<jglathe_volterra>
ath11k woes appear to be resolved with the .37 firmware, btw. No occurrences since applying on either X13s or Volterra
<_[m]123>
general vpn and p2p vpn working now \0
<_[m]123>
s/0/o//
<_[m]123>
jglathe_volterra: yeah I had installed that new firmware
zdykstra has quit [Quit: WeeChat 4.2.1]
<_[m]123>
oh wait lol I'm unable to connect to my mobile hotspot haha I"m just in my local network
xroumegue has quit [Ping timeout: 480 seconds]
<_[m]123>
Error: Connection activation failed: No suitable device found for this connection (device wlP6p1s0 not available because device is not available).
xroumegue has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]
jglathe_volterra has joined #aarch64-laptops
hightower4 has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
<bamse>
jhovold: without
<bamse>
jhovold: charger connected nothing else...booted to console
todi has quit [Ping timeout: 480 seconds]
jglathe_ has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]