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
dlg has quit [Remote host closed the connection]
dlg has joined #aarch64-laptops
nothorseface has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
nothorseface has quit []
nothorseface has joined #aarch64-laptops
nothorseface has quit []
nothorseface has joined #aarch64-laptops
nothorseface has quit [Read error: Connection reset by peer]
nothorseface has joined #aarch64-laptops
nothorseface_ has joined #aarch64-laptops
nothorseface_ has quit [Remote host closed the connection]
nothorseface has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
nothorseface has quit []
nothorseface has joined #aarch64-laptops
nothorseface has quit [Ping timeout: 480 seconds]
<_mike>
i'm fairly certain there should be no reason why compiling openwrt should cause my snapdragon to power down
<_mike>
i believe it's being tampered with
<_mike>
i should be able to use all cores just like i do for anything else
<_mike>
maybe it's a bastille thing cos i'm using ebpf/llvm
<abby>
yes, it's being tampered with by heat
<abby>
it probably did a thermal overload shutdown
tobhe_ has joined #aarch64-laptops
<HdkR>
"My CPU is being tampered with" is a fun way to say I'm abusing it by compiling all the code.
tobhe has quit [Ping timeout: 480 seconds]
<_mike>
abby: yeah valid. i have the air conditioning running in the car with the empty fuel light on
<_mike>
but hang on
<_mike>
it shouldn't really overheat even if i'm only using 8 cores
<_mike>
or 12
<_mike>
it should be designed to cope
<_mike>
although it is summer here and it's been hot and the AC indoors isn't really working
<_mike>
but I have had WAY too many technical issues in the property i'm stuck at atm
nothorseface has joined #aarch64-laptops
sally has quit [Quit: sally]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
sally has joined #aarch64-laptops
<kuruczgy[m]>
linux does not do proper thermal throttling yet on x1e afaik, I also have the same issue, have to prop up the laptop when compiling the kernel for better airflow.
alfredo has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
nothorseface has quit []
checkfoc_us9 has quit []
checkfoc_us9 has joined #aarch64-laptops
checkfoc_us9 has quit []
checkfoc_us9 has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
_mike: you're on the asus aswell right? There is no working fan curve right now (at least on mine), so you may have noticed that the fans never spin up under linux
<SpieringsAE>
they do under windows, so yeah, that in combination with no proper throttling can cause some issues
<SpieringsAE>
I've not managed to run into it myself, but I do tend to put it somewhere where the fans are least obstructed when I do a long compile
<SpieringsAE>
haven't had it get over 85 ish degrees, but yeah, it is quite cool here in the netherlands
nothorseface has joined #aarch64-laptops
SpieringsAE has quit [Remote host closed the connection]
nothorseface has quit [Remote host closed the connection]
nothorseface has joined #aarch64-laptops
kirill_ has joined #aarch64-laptops
kirill_ is now known as Guest5590
<Guest5590>
folks, I'm working on DTS for Honor Magicbook Art 14 Snapdragon and I need help. A user need to physically connect webcam and on the OS without DTD it works. Used USB HUB has an addres which is mapped into usb_2 in x1e80100.dtsi, but all attempts to define it in my DTS fails. System reads it, but webcam doesn't start. I feel that I had missed small pice, but I do it the first time, and can't figure out. Everything is here
<Guest5590>
I build it on v6.13-rc6-dts-raw
<JensGlathe[m]>
Guest5590: MAybe this atch is missing, if we're really talking about usb_2 which would be USB2 only, internal. And you need the ptn3222 definition for it, too as is in the newest dts versions for the T14s. They connect a fingerprint reader with it.
<Guest5590>
I have no idea does it USB2 or not. But an address of a hub to which connected webcam is 0xa200000 and it matches usb_2_dwc3, and I assume that it is true, special for the USB webcam only port
nothorseface has quit []
<JensGlathe[m]>
yeah that sounds about right. You need the eusb5_repeater though
<anonymix007[m]>
macc24: these *.so.1 modules are basically what drives A2DP Hardware Offload in Android. Windows can also use these, so aptX Adaptive works there
<craftyguy>
jhovold: this suspend issue has been happening for me for many months. I just don't use s2idle/suspend 🙁
<craftyguy>
Like, at least a year
<JensGlathe[m]>
... and there they are, HTC Rx errors on the EL2 box with msi-map disabled. Maybe it is a viable workaround to trigger a firmware reset (if that's possible) ) when it gets detected in the Rx handler.
<craftyguy>
Will that drop the wifi connection?
<JensGlathe[m]>
no idea
<craftyguy>
and are we sure that we are both using the same dts patch to remove the msi-map? 😛
<craftyguy>
(I can share mine later when at laptop)
<JensGlathe[m]>
no ofcourse not. But I'm quite confident on this matter
<craftyguy>
what if you drop all of the msi-map things (i.e. revert that whole patch from earlier)
<craftyguy>
Since I re-removed it yesterday after confirming the issue returns when it's there... no errors at all for me in like 15hrs. Bizarre
<JensGlathe[m]>
you don't use gic-its at all?
<JensGlathe[m]>
now that's something
<JensGlathe[m]>
interesting what o1 has to say to this
<JensGlathe[m]>
okay I will remove the msi-map for a test
<JensGlathe[m]>
this might explain why there's a higher probability of hitting it in EL2 - arm-smmuv3 is using it as msi-parent, also using gic-its. and this one is enabling the dma transfers on PCIe. So let's do both, arm-smmuv3 has spi interrupt lines, too
<travmurav[m]>
yeah I guess cmd works but data don't
<travmurav[m]>
very weird
<travmurav[m]>
but uh it's not timeout
<travmurav[m]>
weird
<JensGlathe[m]>
maybe this is no-mmc, no-sdio properties?
<travmurav[m]>
nah
<travmurav[m]>
those should just disable some software checks
<travmurav[m]>
i.e. linux just won't bother sending commands to check if the inserted card is emmc or sdio, and only assume sd
<travmurav[m]>
(no-emmc is a bit sad IMO I guess since one can use emmc->microsd adapter but whatever)
<travmurav[m]>
I wonder if restricting it to legacy/hs modes would do anything
<jhovold>
craftyguy: ah, ok. and it wasn't you who disabled some audio bits in the uefi setup?
<jhovold>
either way, it shouldn't be related to the possible new regression we have in 6.13-rc
<jhovold>
but would be interesting to know what differs in your setup (besides the modem), and suspend has been working fine here (and for most people it seems)
srinik has quit [Ping timeout: 480 seconds]
kmeaw has joined #aarch64-laptops
<kmeaw>
Hi. Where can I find an alsaucm config for T14s (21N1CTO1WW)?
<JensGlathe[m]>
these are all messages regarding sdhc
<craftyguy>
JensGlathe[m]: sorry maybe you misunderstood, I use GIC but not for pcie4. I'll post the patch I am using that eliminates those HTC errors
<craftyguy>
jhovold: No I haven't touched fw config in months, and for audio I mostly just use bluetooth 😛
<craftyguy>
Yeah I have no clue why resuming is so broken for me, and not sure how to debug it further since the system is completely unresponsive when it happens
<JensGlathe[m]>
craftyguy: I just built with msi-map/msi-parent disabled. We'll see what comes off it
<JensGlathe[m]>
One wdk2023 completely on WLAN, booted on EL1 had no HTC Rx errors for >24hrs
<craftyguy>
if I apply that, I get no HTC Rx errors, wifi works fine for me for days. without that patch, lots of HTC errors and I frequently have to reload ath11k to get wifi connectivity working again
<JensGlathe[m]>
yeah that was my previous test
<craftyguy>
are you testing it on an x13s?
<craftyguy>
(you mentioned "el2 box" but I don't know what that is)
<JensGlathe[m]>
where I got lots of HTC Rx errors fast on X13s, and eventually also on wdk2023 with EL2
<JensGlathe[m]>
I test with 3 devices
<craftyguy>
when you tested it on the x13s, did it help?
<craftyguy>
I've been testing it on my x13s in el1 only, haven't tried el2 with that patch
* craftyguy
has to step away for a bit now
<JensGlathe[m]>
no it got worse for me, I am virtually HTC Rx error free with msi-map on
<JensGlathe[m]>
tests will continue until morale improves
<craftyguy>
haha. Which fw version are you using for wifi on the x13s you are testing
<JensGlathe[m]>
.41 everywhere
<JensGlathe[m]>
X13s is running now with completely msi-map disabled
<JensGlathe[m]>
wdk 2023 el1, too
jhovold has quit [Ping timeout: 480 seconds]
<steev>
1 day, 3 hours here, and 0 htc rx errors
<JensGlathe[m]>
wdk2023 el2 now too
<steev>
strictly el1 here, mostly because i only have an x13s and a lack of charging of the battery is a nogo for me
sally has quit [Quit: sally]
sally has joined #aarch64-laptops
proycon has quit [Remote host closed the connection]