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]
Lucanis has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
derzahl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #aarch64-laptops
mbuhl has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jglathe_volterra has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]
jglathe_volterra has joined #aarch64-laptops
pbrobinson has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
mbuhl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hl` has joined #aarch64-laptops
pbrobinson has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Caterpillar has quit [Quit: Konversation terminated!]
<deathmist>
valpackett: nah it's something else since there's no meaningful CPU activity at all, perhaps something to do with power management being wack in general or the pd_ignore_unused clk_ignore_unused cmdline args which are "required" apparently still. the 8W drain still remains also after stopping NetworkManager service
<deathmist>
could also be something up with the X1E Vivobook dts which always keeps some high power regulators running
josch has joined #aarch64-laptops
<deathmist>
at least similar regulator-always-on props seem to be shared with slim7x so who knows, I don't even know what I should be expecting to see at this point or if it's just normal
chrisl has joined #aarch64-laptops
<josch>
Hi all _o/ Is this channel specific to snapdragon laptops (as the topic suggests) or are other aarch64 laptops (MNT Reform and MNT Pocket Reform in my case) also on topic? Thank you! :)
chrisl has quit [Ping timeout: 480 seconds]
<valpackett>
josch: i'm sure there are better channels for mnt things
<valpackett>
deathmist: that's like 2x than what i get though, with pd_ignore_unused clk_ignore_unused and everything
<josch>
valpackett: okay, thank you
josch has left #aarch64-laptops [#aarch64-laptops]
luca020400 has quit [Quit: WeeChat 4.6.1]
luca020400 has joined #aarch64-laptops
luca020400 has quit []
luca020400 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
SpieringsAE_sff has joined #aarch64-laptops
SpieringsAE_sff has quit []
chrisl has quit [Ping timeout: 480 seconds]
<deathmist>
valpackett: hm yeah this is rather strange then.. I've not compared to the same machine on a systemd distro to see if that somehow makes a difference, I'm just more or less running https://gist.github.com/JamiKettunen/7c2a25688976c09af819eebc9fbb8396 + plasma-desktop etc not really worth documenting there most likely
<deathmist>
this seems to also happen when it's powered off so I guess it's a firmware issue
<kuruczgy[m]>
Would anyone have a clue about what kind of light sensor the slim7x (or any x1 laptop for that matter) might have? (The lenovo PSREF claims that it's a "Ambient color sensor", I guess that's just a fancier light sensor.)
<kuruczgy[m]>
(Hopefully it's something with an accessible datasheet, or if we are really lucky a driver already exists.)
<kuruczgy[m]>
deathmist: if I had to guess when it reaches charge_control_end_threshold it just disconnects the battery and powers the system directly for AC. That would be logical, that should put the least amount of wear on the battery. Not sure about the "slowly charging past charge_control_end_threshold" part though, I did not observe that in my testing.
<deathmist>
it's very slow fwiw, I think since I started testing yesterday and after powering on the laptop again today it was ~2% past my set 55% end limit, but still worth noting I think since I haven't really see it try go back down to the limit, will see how it behaves as I continue testing
<deathmist>
(I've had the device plugged in this whole time)
<kuruczgy[m]>
Hm ok I only tested it for a couple hours so far. Will report back once I do an overnight test too.
<deathmist>
I may have also left a chromium compile running for 5 hours overnight so not sure if that contributed somehow as well :D
<kuruczgy[m]>
deathmist: Wait you can compile chromium in 5h on an X1E laptop? Which one? Do you need 64GB RAM for that?
<kuruczgy[m]>
Also I am seeing that after I reboot, the sysfs charge_control_* values report 0, but the charge limit is still in effect (as expected)
<kuruczgy[m]>
Looking at the code I don't see any logic for actually reading the values from the firmware, it just remembers the last values written to sysfs.
<deathmist>
for me it doesn't remember them after reboot; I made /etc/rc.local write them back on each boot
<kuruczgy[m]>
You mean that after you reboot, it actually charges to 100%?
<deathmist>
on poweroff it remembers the state from previous boot, but upon booting without setting them (and them reporting 0 when read from sysfs) it starts charging over the limit likely because the driver resets themn
<kuruczgy[m]>
I just tested it again, set the charge limit, rebooted, sysfs reports 0 for the values, but the charging still stops at the value I set previously
Grabunhold has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<deathmist>
odd.. wonder why it behaves differently for us. maybe I should setup ubuntu or something as well just so I have a systemd (and glibc) comparison point in general for stuff like this
<Jasper[m]>
@steev @amstan should be able to ban them or from irc
Alisa[m] has left #aarch64-laptops [Kicked by @amstan:hypertriangle.com ]
amstan has joined #aarch64-laptops
<amstan>
Jasper: thanks, done
<Jasper[m]>
No thank you
<Jasper[m]>
* No, thank you!
chrisl has joined #aarch64-laptops
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
agl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
agl_ has joined #aarch64-laptops
agl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
FAQ_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
agl_ has quit [Ping timeout: 480 seconds]
agl has joined #aarch64-laptops
agl has quit []
agl has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
dvhart has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
dvhart has quit [Quit: Leaving]
dvhart has joined #aarch64-laptops
<dvhart>
Hi all, new to the channel. Working on a ThinkPad T14S Snapdragon Elite (32G/IPS - 21N1). Installed Ubuntu 25.04 + the concept snaps for mesa and gnome, and their x1e kernel (6.14.0-35-qcom-x1e). I think everything that is supposed to work works with one exception.
<dvhart>
Things that don't work that I think are known not to work yet: screen brightness, audio, suspend/resume. Correct?
<dvhart>
Things that don't work that I haven't seen reported elsewhere: It seems to successfully boot about 50% of the time, usually returning to a frozen grub menu after printing that it is loading the dtb.
<dvhart>
I haven't found anything that deterministically leads to a successful boot, just reboot and try again. Is this a known issue?
<Jasper[m]>
audio and suspend/resume is a somewhat common problem iirc, sleep should work I think
<Jasper[m]>
Screen brightness sounds a bit weird though
<Jasper[m]>
Could you send a dmesg of a working boot?
<Jasper[m]>
I'm not sure about the succesful boot, do you have the dtb specified in grub config?
<dvhart>
working on the dmesg, couple minutes...
<dvhart>
yes the grub config points to the absolute path of the dtb
<dvhart>
oh no, sorry, grub points to a symlink named for the kernel version
<dvhart>
and yeah, the dtb does work (or it would not boot consistently). It seems more like some kind of inconsistent system state that isn't set to a known good state at boot.
<dvhart>
This happens with both x1e kernel as well as the default kernel (6.14.0-15-generic)
<Jasper[m]>
the efi one is not set and might be a good one to at least configure
<Jasper[m]>
But I'm not sure how much that does in this case
<Jasper[m]>
Don't see anything particularly weird in dmesg, also checked @jhovold's wiki and Audio should work up to some point, but idk if that's upstream
<dvhart>
I can reboot to check that manually now. I haven't seen this documented anywhere yet, so I'm probably missing a resource. Is there some project/docs I should go read up on? (I've mostly found information on Reddit and the Ubuntu Concept x1e forums so far).
<dvhart>
(I admittedly haven't tried scouring lkml yet)
<dvhart>
Excellent, thank you, I'll read up on what's there before asking more questions. And I'll try the efi=noruntime now. biab.
<dvhart>
That wiki is just what I was missing as a kernel developer vs a casual linux user - thanks, that will give the context I need.
dvhart has quit [Quit: Leaving]
<Jasper[m]>
Ahh you're a kernel developer?
Caterpillar has joined #aarch64-laptops
dvhart has joined #aarch64-laptops
<dvhart>
@Jasper[m], thank you very much, the efi=noruntime add to grub made both the x1e kernel and the stock 25.04 kernel both consistently boot successfully. My custom built v6.15 kernel fails still, but that is certainly on me. I'll read up on the wiki and go from there. Really appreciate the help.
<dvhart>
I did look for something like "start here" docs in the topic, wonder if adding this wiki to the topic would be helpful for others too?
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<Jasper[m]>
I know some distro's have their own info page for these things, but not sure about ubuntu
<Jasper[m]>
As fas as getting your own kernel booting goes, you should probably get Johan's config or Ubuntu's as a base and enable/disable whatever you (don't) need
<dvhart>
Ubuntu does, but it isn't this complete
<dvhart>
Yeah, I'll be starting from his. I just built v6.15 localmodconfig to see where that ended up - clear now there are enough WIP branches I need to include in the build still.
<JensGlathe[m]>
dvhart: If its an ips model and not OLED then x1e78100-lenovo-thinkpad-t14s should be the right one. Since you say backlight brightness isn't working, I'd suggest to try x1e78100-lenovo-thinkpad-t14s-oled
<dvhart>
I would have thought that would have some conflicting descriptions in there... but happy to try. Thanks.
<JensGlathe[m]>
Ubuntu does not yet distinguesh between these two files and selects the non-OLED by default
<dvhart>
Ah, gotcha.
<JensGlathe[m]>
I guess you will find out. The IPS panels have PWM backlight by default. The OLED has DP AUX backlight control.
<JensGlathe[m]>
And I won't be surprised if there are even other variants.
<Jasper[m]>
JensGlathe[m]: I did not see a kernel splat for unknown panel in the dmesg so I thought it'd work
<Jasper[m]>
but he has an IPS panel
<dvhart>
Yes, this is the IPS panel for sure.
<JensGlathe[m]>
Oh and I would actually suggest to go all-in on the kernel version - 6.15.0-jg-4 has good support for T14s both variants.
<dvhart>
(I tried to get the OLED but couldn't find it anywhere :-)
<dvhart>
@JensGlathe[m], where would I find that tag?
<valpackett>
deathmist: oh cool, chimera is what i have on my x86 laptop
<valpackett>
hm. ControlPortOverNL80211=false does make iwd work for you, for me it didn't
erebion_muc[m] has left #aarch64-laptops [User left]
dvhart has joined #aarch64-laptops
FAQ_ has quit [Remote host closed the connection]
<dvhart>
@deathmist @JensGlathe[m] nice, thank you
chrisl has joined #aarch64-laptops
<deathmist>
valpackett: iwd worked with that in my very brief testing anyway, I don't normally use it
<deathmist>
also yeah the name seemed oddly familiar heh
chrisl has quit [Ping timeout: 480 seconds]
agl has quit [Ping timeout: 480 seconds]
dvhart has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
The HP Omnibook X14 is the first box here where 4 lanes dp altmode is working on both type-c ports, any orientation, without replug issues. One has the PS8830 retimer, one doesn't. And the debug messages seem to mitigate the "can't read display capabilities, screen comes up with 640x480 if at all" issue. Not seen yet.
<valpackett>
yeah somehow i have a more cursed ath12k than everyone else it seems (0.o)
<JensGlathe[m]>
I removed mine from the Dev Kit. And the RTL8125 card, too. Nice uptimes now
<valpackett>
not removable here hahah
<JensGlathe[m]>
Actually I have no issues with the WCN7850 on the ThinkBook 16
<valpackett>
i mean, mine generally works well, it's very stable, it just has this weird spinlock cpu spike when networkmanager checks up on it every 6 sec, and iwd did not work even with ControlPortOverNL80211
agl has joined #aarch64-laptops
<steev>
valpackett: check the linux-wireless list, there are a number of ath12k patches on there