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
todi_away has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
hipboi has joined #aarch64-laptops
ellyq_ has joined #aarch64-laptops
ellyq__ has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
actrawave has joined #aarch64-laptops
actrawave has left #aarch64-laptops [#aarch64-laptops]
actrawave has joined #aarch64-laptops
actrawave has quit [Remote host closed the connection]
actrawave has joined #aarch64-laptops
actrawave has quit []
actrawave has joined #aarch64-laptops
actrawave has quit []
actrawave has joined #aarch64-laptops
actrawave has quit []
actrawave has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
actrawave has quit [Ping timeout: 480 seconds]
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
actrawave has joined #aarch64-laptops
actrawave has quit []
hipboi has quit [Quit: hipboi]
ellyq_ has quit []
chrisl has quit [Ping timeout: 480 seconds]
ellyq_ has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hipboi has quit []
alfredo has quit [Ping timeout: 480 seconds]
iivanov has quit [Ping timeout: 480 seconds]
gwolf has quit [Ping timeout: 480 seconds]
gwolf has joined #aarch64-laptops
<gwolf>
Humh... I feaer I did something wrong WRT Alexey Klimov's patch for sound on the C630, or am missing a step somewhere :-(
<gwolf>
The system now detects a sound card, and pavucontrol seems happy to regulate it \o/
<gwolf>
But I'm still unable to hear anything, either on the speakers or via the headphones port ☹
hipboi has joined #aarch64-laptops
hipboi has quit []
<gwolf>
The only relevant things I see when booting is a set of five lines -- «qnoc-sdm845 1500000.interconnect: sync_state() pending due to 1e40000.ipa»
<gwolf>
(repeated but with interconnect at 1620000, 1380000, 1700000, 17900000)
hipboi has joined #aarch64-laptops
hipboi has quit []
iivanov has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<JensGlathe[m]>
Oh Advance Shipment Notice
<JensGlathe[m]>
From Reno, Nevada... hmm
jhovold has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<HdkR>
Oh, are the dev kits actually shipping out?
<JensGlathe[m]>
Documents indicate it, yeah
hipboi has quit [Quit: hipboi]
chrisl has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov has quit [Read error: Connection reset by peer]
chrisl has quit [Ping timeout: 480 seconds]
todi has joined #aarch64-laptops
todi_away has quit [Ping timeout: 480 seconds]
hogliux has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
it even lists parts in stock again on the arrow website
<SpieringsAE>
strangely the price and order button are missing tho lol
iivanov_ has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
ellyq__ has joined #aarch64-laptops
ellyq has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
<maz>
I just paid the import duty for the devkit, so *something* is really happening, and the box is rumoured to land at my door tomorrow. guess I'm not going to the office! :)
<SpieringsAE>
Im still on the fence, on the one hand the performance multicore seems to be about equal to the vivobook I had, and I heard from jeff that the fan is noisy af
xroumegue has quit [Ping timeout: 480 seconds]
<SpieringsAE>
I kinda just want one to solder the unsolder components on to, to see if they can be made to work, like the pcie slot and the dissapearing hdmi port
<SpieringsAE>
Would love to design a new daughter board with just DP instead of hdmi, because hdmi was kinda dumb in the first place imo
<maz>
I'm more inclined to get rid of the wifi card and hook a PCIe switch there.
<SpieringsAE>
that is most likely to work yeah
<SpieringsAE>
but only 4x2 or something I guess
<maz>
but first, EL2. if I don't get that, this box has no purpose for me.
<SpieringsAE>
Really need to learn more about the ARM exception levels, I don't really have any idea what benefit that would have lol
<SpieringsAE>
Is it hypervisor stuff?
<SpieringsAE>
for running vms?
<maz>
yup
<macc24>
there's gunyah running which you can use with patches for both qemu and linux
<SpieringsAE>
yeah that seems cool to be able to do
<macc24>
SpieringsAE: EL0 = normal applications, EL1 = kernel and stuff, EL2 = hypervisor, EL3 = trustzone
<macc24>
usually*
<macc24>
you can run kernel in el2 with vhe
<maz>
macc24: for obvious reasons, I'm not exactly interested in gunyah.
<macc24>
maz: those reasons are not so obvious to me
<maz>
macc24: let's just say that I may have some ties to another hypervisor.
xroumegue has joined #aarch64-laptops
<macc24>
oh you're kvm developer, ok that'd make sense
hipboi has quit [Quit: hipboi]
srinik has joined #aarch64-laptops
crimars is now known as crisma
hipboi has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
<JensGlathe[m]>
maz: According to travmurav slbounce should work with x1e when you have a newer tcblaunch.exe. I will test this later on for giggles on the HP X 14
chrisl has joined #aarch64-laptops
<SpieringsAE>
from what I read slbounce can only launch a pretty neutered kernel that is missing a bunch of firmware to interact with
<JensGlathe[m]>
yes that's true. no adsp, cdsp, gpu (ZAP), venus (not relevant on x1e).
chrisl has quit [Ping timeout: 480 seconds]
<maz>
as long as I have PCIe, memory and serial, I'm OK.
<travmurav[m]>
Gpi should work
<travmurav[m]>
Gpu
<travmurav[m]>
Zap doesn't matter in el2
<JensGlathe[m]>
But what I've read its more a matter of how they are loaded and activated
<travmurav[m]>
Since linux knows how to handle el2 for grub, which is not the case for most other remoteprocs
<JensGlathe[m]>
How do I specify the firmware without zap? Just in the gpu node?
<macc24>
does the gpu even need any other firmware than the zap shader?
<travmurav[m]>
Yes, gmu and microcode
<travmurav[m]>
I think those are generic anyway
<JensGlathe[m]>
yes and tey get loaded on EL2
<JensGlathe[m]>
and no need for the signed one?
<travmurav[m]>
So in dt only the signed zap shader is specified but in el2 we can just poke the protected register ourselves
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
srinik has quit [Quit: Leaving]
srinik has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
iivanov has quit [Quit: Leaving...]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
x1e battery / suspend update: I had the X14 suspended (closed) for almost 2 days, 66% battery left
<travmurav[m]>
Jens Glathe: is this windows or linux?
<JensGlathe[m]>
Linux (Ubuntu 24.10)
<JosDehaes[m]>
well that's a lot better than on the yoga 😅. I closed mine yesterday evening at 80%, and in the morning only 35% left...
<travmurav[m]>
Jens Glathe: heh, I thought pm is broken on x1e too, but ~0.5Wh/hr sounds reasonable even
<travmurav[m]>
Jens Glathe: or hm was it hibernated maybe?
<JensGlathe[m]>
no not hibernated
<travmurav[m]>
very nice then
<JensGlathe[m]>
its instant on
<JensGlathe[m]>
but very odd warnings in dmesg that need investigation
<travmurav[m]>
at least the soc thinks it didn't fully sleep
<travmurav[m]>
so I guess good news it could go lower? xD
<JensGlathe[m]>
I haven't put any effort into this, just observed, and with 6.12-rc2 it seems to be way better
<travmurav[m]>
actually idk what apss is but perhaps this is the cpu cores themselves, so it killed the arm cluster but didn't go down to ram self refresh I guess?
<travmurav[m]>
(afaiu "ddr" counter is for ram self refresh level)
<travmurav[m]>
Jens Glathe: did you suspend it 10 times exactly? xD
<JensGlathe[m]>
nah no idea, I've booted it, used it, colesed it a few times, moved it around since sunday. Since this works quite well you don't think about it much. And yes I wanted to know how the battery holds up.
<JensGlathe[m]>
oh nice Ubuntu has a livefs-editor
<JensGlathe[m]>
Aim Higher I guess
<maz>
JensGlathe[m]: core getting killed is normal. that's the normal suspend procedure.
<JensGlathe[m]>
okay, good to know
<travmurav[m]>
I should admit that tho I still assume the platform side is broken since it didn't tick ddr, I'm /very/ impressed how low the board went
<JensGlathe[m]>
but the SMMU fails look like wrong power sequence or something
<travmurav[m]>
I was pretty pessimistic about suspend on those new things so I guess this is very cool to see it didn't choke like most people here report
<tobhe>
JensGlathe[m]: makes it so much easier to quickly fix installer images
<JensGlathe[m]>
... or possible at all
<tobhe>
I'm also planning to do a post on how to do offline image builds using the same scripts launchpad uses
<tobhe>
which has arguably been a bit of a pain point too
<MrCatfood[m]>
i will give it a try on my vivobook
<tobhe>
you might have to manually specify the device tree on that one for now since I haven't tested that yet
<tobhe>
should be in /casper
<MrCatfood[m]>
okay
<JensGlathe[m]>
I will try this one out, too.
* travmurav[m]
wonders if his grub patch for driver loading got ignored
<JensGlathe[m]>
by whom
<JensGlathe[m]>
My experience with building grub myself was sub-optimal so far
<travmurav[m]>
no idea what grub development flow is but my patch on grub lists didn't really get any comments, tho they seem quite active on other threads
<tobhe>
JensGlathe[m]: MrCatfood[m]: If you test on hardware we don't have a bug for yet please free to add a bug for them at https://bugs.launchpad.net/ubuntu-concept
alfredo has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
as in bug == feature?
<JensGlathe[m]>
thedt needs to be upstream?
alfredo1 is now known as alfredo
<tobhe>
yeah, just a wishlist report
<tobhe>
ideally with dmidecode output
<tobhe>
I'm using that to identify the machine and pick the correct dtb on boot
<JensGlathe[m]>
okay, you're using dtbloader?
<tobhe>
doing it via grub config
<tobhe>
nice, i hadn't seen dtbloader yet. cool stuff travmurav[m]
<travmurav[m]>
tobhe: yeah that's what "grub seems to ignore me" was about ;D
<tobhe>
aha, it all starts to make sense
<JensGlathe[m]>
grub being able to load slbounce is also a plus, just saying
<travmurav[m]>
I also still need to get my hands to adding dpp decoder to provision wifi/bt mac in a generic way
iivanov has joined #aarch64-laptops
<travmurav[m]>
was a bit sick last week
chrisl has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
<macc24>
<JosDehaes[m]> "well that's a lot better than on..." <- if you didn't manually suspend it never went to sleep
chrisl has quit [Ping timeout: 480 seconds]
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
hipboi has quit [Quit: hipboi]
alfredo has quit [Ping timeout: 480 seconds]
sri has joined #aarch64-laptops
<JosDehaes[m]>
macc24: of course I put it to sleep manually 😁
SpieringsAE has quit [Quit: Leaving]
<JosDehaes[m]>
and I do have your EC patch
srinik has quit [Remote host closed the connection]
<macc24>
:<
chrisl has joined #aarch64-laptops
fossdd has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
ellyq__ has quit []
ellyq has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ellyq has quit []
ellyq has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
iivanov has quit [Remote host closed the connection]
erebion[m] has joined #aarch64-laptops
<erebion[m]>
By the way, why does the battery only last ~7 hours on the X13s, while Lenovo quote ~28 hours..?
<macc24>
shouldn't slim7x dts have output-high in both pinctrls at &lpass_tlmm?
chrisl has joined #aarch64-laptops
<steev>
erebion[m]: because we aren't hitting the lowest power states
chrisl has quit [Ping timeout: 480 seconds]
<erebion[m]>
Yeah, but why? What does that mean?
<abby>
someone has to write the code to talk to the various cpus and controllers to get them to go into their lowest power-usage states
<craftyguy>
abby: in the kernel, or userspace, or both?
<abby>
kernel, i believe
<craftyguy>
dang
Dylanger[m] has joined #aarch64-laptops
<Dylanger[m]>
I was wondering this with my Acer aarch64 Chromebook, expected more battery life and it's average
<gwolf>
steev: thanks, I'll look into that this evening when I'm with my laptop handy
<erebion[m]>
Hopefully someone with the right knowledge does that, it'd be awesome to have 28 hours battery life :D
* gwolf
has ~10hr battery life in the C630 and is very happy :-)
<gwolf>
Now, if only suspend was more power-efficient... ;-)
* abby
gets like 15 hours on x13s
<erebion[m]>
Wait, abby, how do you get 15 hours?
<abby>
well, idk if it's actually that, but the discharge rate calculates out to 11-15 hrs
<abby>
i'm usually only running irc client + i3 + a few terminals
<abby>
maybe a browser
<craftyguy>
ya I'm not super hopeful if it requires kernel work. probably only like 3 people in the whole world know where to even begin, and they're probably all working on the next gen SOC 😅 (it would be cool if more people somehow learned how to do this stuff!)
iivanov has joined #aarch64-laptops
<craftyguy>
(I'm super grateful of all the hard kernel work done to support things!!! I'm just disappointed that OEMs are still pumping/dumping SOCs and not concerned with investing in better linux support)
<JensGlathe[m]>
4% market share
iivanov has quit []
<craftyguy>
right
<craftyguy>
they have different motivations than I do :P
<robclark>
qcom and linaro are still posting patches for x1e, so they haven't completely moved on to the $next_thing yet.. I'm not entirely sure what all is missing to hit the lowest power states, but I guess probably folks from qcom/linaro do (bamse?)
<craftyguy>
I understand why the situation is what it is, but I can still be disappointed about it :P
<robclark>
I think it is too early to be disappointed yet ;-)
<robclark>
power is hard
<JensGlathe[m]>
a little more accessible documentation would be nice.
<steev>
the other thing is, it should be generic enough that it holds for all of them, and isn't specific to one
<craftyguy>
robclark: ok, fair enough, I'll be patient :) ya I've been in an OEM doing PM debug/enabling and can appreciate how hard it is
<JensGlathe[m]>
anyway, there is quite some work done (thermal management in 6.10 iirc). Unfortunately, you need to live the rc kernels to detect bugs and fix / get them fixed. And yes, power is incomprehensibly hard.
srinik has quit [Ping timeout: 480 seconds]
<steev>
gwolf: you should be getting more than that, but, yes, something is draining more power on the c630 than it used to
<steev>
i definitely used to get around 53 or so hours suspend, and now i'm lucky if i get 36
<robclark>
my guess is once we no longer need clk_ignore_unused pd_ignore_unused, things will be in a better state.. although there might also still be something on the cpu side (iirc HdkR was claiming that a WFE loop was using the same power as a NOP loop, which kinda implies the cpu isn't going to lowest power state)
<gwolf>
right, I'd also point towards the ~40hr range
<gwolf>
which is usually fine for me... but would be better to have some more
<HdkR>
WFE loop thing could just be measurement limits from full system load
<erebion[m]>
@abby: I only use Sway and Firefox, idling a bit. 7 hours.
<erebion[m]>
wtf
<HdkR>
Actually no, on Oryon WFE power difference is probably the fact that WFE behaves like a nop
<craftyguy>
erebion[m]: I have an almost identical env (sway + ff + tui text editors), I usually get at least 10hr on my x13s. my guess is firefox is to blame, maybe you have some tab that's doing something stupid in the background :P
<craftyguy>
I added a waybar thing to show a red notification icon when the laptop temp rises above 45C. it's usually firefox (when I'm not actively compiling something)