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
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
martiert_work has quit [Remote host closed the connection]
martiert_work has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
skymage23 has joined #aarch64-laptops
mumed_onion has joined #aarch64-laptops
skymage23 has quit [Quit: Leaving]
mumed_onion has quit []
ChristopherNugent[m] has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
<JensGlathe[m]> Oh new "System Hardware Update" from HP
<JensGlathe[m]> and new adsp firmware blob as it seems
alfredo has joined #aarch64-laptops
<JensGlathe[m]> it re-enable secure boot and boot order
<JensGlathe[m]> I like his "we know what's best for you" attitude
krzk has quit [Quit: leaving]
krzk has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE> Can you actually change the boot order from windows? I remember that on my Asus I had to usb boot and then efibootmgr to fix it. Or at least I found no other way to do it in the firmware.
<SpieringsAE> seems there is, msconfig
macc24 has joined #aarch64-laptops
macc24 has quit [Quit: WeeChat 4.4.2]
<JensGlathe[m]> It's in the UEFI BIOS. It got updated by the patches
<craftyguy> bamse: enabling the crypto user stuff got some of the algos to show up in that utility. disk encryption/LUKS still appears to be unaccelerated/slow, so maybe qce is still needed for that? (i have no clue yet how this stuff works)
<JensGlathe[m]> The hotkeys work
macc24 has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
macc24 has quit [Ping timeout: 480 seconds]
macc24 has joined #aarch64-laptops
juergh has quit [Quit: ZNC 1.8.2+deb2ubuntu0.1 - https://znc.in]
alfredo has quit [Quit: alfredo]
macc24 has quit [Ping timeout: 480 seconds]
macc24 has joined #aarch64-laptops
macc24 has quit [Ping timeout: 480 seconds]
SpieringsAE has quit [Remote host closed the connection]
patrickm has quit [Ping timeout: 480 seconds]
crisma has joined #aarch64-laptops
patrickm has joined #aarch64-laptops
macc24 has joined #aarch64-laptops
macc24 has quit [Ping timeout: 480 seconds]
macc24 has joined #aarch64-laptops
macc24 has quit [Quit: WeeChat 4.4.2]
macc24 has joined #aarch64-laptops
<kuruczgy[m]> My yoga 7x is shutting down due to thermal panic (reaching 110 °C) on one of the cores while kernel compiling. I was already getting this last week, then it randomly fixed itself, but today I am getting it again. (Today it's `cpu2-0-btm-thermal`, I think last week it was a different cluster.)
<kuruczgy[m]> Isn't the kernel just supposed to throttle the frequency to keep the temp below 95 °C? What could be causing this issue?
<Nios34[m]> tweak the governor strategy maybe?
<HdkR> Whoa, that's neat, I couldn't get mine to throttle at all
<HdkR> Does the fan ramp to the moon?
<kuruczgy[m]> Yeah, the fan seems to ramp up, but I think that's controlled by the EC and not the kernel?
<gabertron> I noticed that the yoga when placed on a flat surface is struggling to get enough airflow.. so when compiling stuff I either put on something that gives more space under it or put on its side and I’ve been able to build stuff for hours
<kuruczgy[m]> William Goodspeed: I mean sure I could tweak it but IMO it should not be reaching the critical temp no matter the governor
<kuruczgy[m]> Ok so based on what you guys are saying it seems that thermal throttling is not completely fleshed out yet, and I was just getting lucky so far when it was not overheating...
<macc24> oh that's weird, my unit never overheated
<kuruczgy[m]> Does anyone know how the thermal zone trip points work? E.g. what does it mean to have two "passsive" trip points at 90 and 95 °C?
<kuruczgy[m]> With the laptop propped up, the temp seems to have settled at around 94 °C. All the cores seem to be pegged at 3.4 GHz. Interesting, so this means that the cooling is able to keep up with the CPU, I was under the impression that thermals were the main perf bottleneck.
<macc24> maybe you can help document the EC so that fan profile switch can be added :D
<kuruczgy[m]> macc24: Well I wouldn't even know where to start, you seem to have much more knowledge about the EC than me.
<macc24> kuruczgy[m]: about 3 days ago i knew about the same amount as you do now
<kuruczgy[m]> macc24: Tbh I am still most interested in the lid switch issue. From what I gathered you poked around the EC registers a bit? How extensive was this? What are the leading theories, what would make sense to check next?
patrickm has quit [Ping timeout: 480 seconds]
patrickm has joined #aarch64-laptops
<macc24> kuruczgy[m]: i'm also interested in the lid switch issue but i feel like i am not making any progress so i'm doing anything to feel any resemblance of progress
<JensGlathe[m]> I would back up a bit and try CRD lid switch code only in the dts, and see what happens. I would assume that experienced engineers change as little as necessary from the CRD to get a shippable product soon.
todi_away has quit [Remote host closed the connection]
<kuruczgy[m]> Jens Glathe: Already tried that weeks ago, copied the `gpio-keys` block from the CRD, no luck. I even confirmed that it _is_ gpio92 on the yoga too, yet on linux the value of the gpio simply doesn't change no matter what...
jhovold has quit [Ping timeout: 480 seconds]
<JensGlathe[m]> maybe its not powered up, but I guess that's been suggested before
<macc24> i compared the regulators and those that weren't enabled in slim7x dts are unrelated
<kuruczgy[m]> Yeah, that's an attractive theory, but the range of things that could be "powering it up" is quite large. (So far I checked most GPIOs and AFAIK macc24 checked most EC registers.)
<kuruczgy[m]> If only we had schematics...
<macc24> kuruczgy[m]: now it's at "all EC registers documented in DSDT"
<JensGlathe[m]> I'm a bit at a loss re regulators. I have copied all from the CRD I could find, and removed only those where I would be sure they shouldn't be there (like rtmr2 in my case).
<JensGlathe[m]> and no idea where the hall sensor is powered
<JensGlathe[m]> abelvesa: seems to be only one ptn3222 here, i2c5@47
<JensGlathe[m]> but the whole bus has devices @0c, 1d, 61, 6a too, not listed
* macc24 shrugs
<JensGlathe[m]> can you see regulators in dsdt / acpi? I had the feeling you could when looking at the whole USB4 mess
baryluk6 has joined #aarch64-laptops
<macc24> yeah
patrickm has quit [Ping timeout: 480 seconds]
<baryluk6> Hey. Have been lurking for few months. I see t14s 64GB OLED now mostly works. Any deal breakers (wifi, suspend issues, usb not working?), should know before I order one next week?
<zdykstra> I'm curious too, as that's a dream laptop there
altacus__ has quit [Remote host closed the connection]
crisma has left #aarch64-laptops [WeeChat 4.4.1]
<JensGlathe[m]> Hmm got the type-A single port on the HP X14 completely up, working with USB2 and USB3 now. But it's still 2 ports, since it is usb_mp_dwc3. But it works.
<macc24> <joke> it's a multiport co
<macc24> conrtoller of course it won't do one port
<JensGlathe[m]> yeah. But they used it since it's type-a
<JensGlathe[m]> you have a usb_2_dwc3 controller, too, but its USB2 only
<JensGlathe[m]> for the T14s they seem to use 2 ports, but only one of each phy
hexdump0815 has quit [Quit: WeeChat 3.8]
hexdump0815 has joined #aarch64-laptops
<hexdump0815> JensGlathe[m]: regarding regulators and acpi maybe have a look at https://oftc.irclog.whitequark.org/aarch64-laptops/2022-10-18#31531766 and on from there
<hexdump0815> the expired dpaste there was https://pastebin.com/raw/8akaXSbu
<JensGlathe[m]> oh thx
Lucanis has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops
macc24 has quit [Quit: WeeChat 4.4.2]
patrickm has joined #aarch64-laptops
fparent- has quit [Ping timeout: 480 seconds]