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
<enyalios> has anyone used redshift on an x13s? it doesnt seem to change at all, i wonder if the video driver doesnt support color temp changes or something
<HdkR> enyalios: Problem is there are multiple properties to support this and Adreno doesn't support the one that redshift is using
<HdkR> Or at least likely doesn't support the correct one. That tends to be the issue :)
<enyalios> redshift is supposed to support a few different methods for changing things, but none of them seemed to do anything for me
<enyalios> it lists drm, randr, vidmode, and dummy as methods
<HdkR> Yea, looks like GAMME_LUT isn't a supported xrandr property
HaikuUser has joined #aarch64-laptops
HaikuUser has left #aarch64-laptops [#aarch64-laptops]
<enyalios> :-(
sally[m]1 has joined #aarch64-laptops
sally[m]12 has joined #aarch64-laptops
ellyq_ has joined #aarch64-laptops
ellyq__ has quit [Ping timeout: 480 seconds]
Lucanis has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops
krei-se has joined #aarch64-laptops
krei-se- has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
<HdkR> https://www.phoronix.com/news/Ubuntu-Snapdragon-X1-Begins firmware bug fixed for 64GB? Where's the patch?
<Jasper[m]> <enyalios> "redshift is supposed to support..." <- The blue light filter? I think the one in KDE works
srinik has joined #aarch64-laptops
bryanodonoghue has joined #aarch64-laptops
apalos has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
bryanodonoghue has quit [Ping timeout: 480 seconds]
apalos has quit [Ping timeout: 480 seconds]
indy has quit [Ping timeout: 480 seconds]
indy has joined #aarch64-laptops
bryanodonoghue has joined #aarch64-laptops
apalos has joined #aarch64-laptops
pneuhardt has joined #aarch64-laptops
vkoul has joined #aarch64-laptops
lumag has joined #aarch64-laptops
mani_s has joined #aarch64-laptops
<HdkR> Ah, I thought they found the firmware bug and fixed it rather than rolling that workaround
<JensGlathe[m]> whatever works. In that regard: Is there also a fix for getting grub to have working keyboard on the hp X14? Fighting my way through sd-boot because of this
<tobhe> HdkR: I wish :( only a workaround for now
<HdkR> Haven't gotten back to testing a grub with that workaround yet. Low prio until the OLED screen problem gets resolved
srinik has joined #aarch64-laptops
wizzard has quit [Remote host closed the connection]
srinik has quit [Ping timeout: 480 seconds]
<JensGlathe[m]> HP X14s: it boots from sst with systemd-boot
<JensGlathe[m]> s/X14s/X14/
<JensGlathe[m]> s/X14s/X14/, s/sst/ssd/
srinik has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
weirdtreething has quit [Remote host closed the connection]
<JensGlathe[m]> Installing with sd-boot is a PITA though
<JensGlathe[m]> to make it work you need qseecom for the laptop you have enabled
<JensGlathe[m]> and... no idea how I can do this in a chrooted env... get a valid install (working would suffice, too) of systemd-boot with its access to efivars and whatnot
<travmurav[m]> Uh can't you just place it at the usual bootaa64.efi spot?
weirdtreething has joined #aarch64-laptops
<travmurav[m]> I guess it would be a problem if you want to dual boot install it along with some other bootloader on the same esp but you can't do that without poking efivars no matter what bootloader it is
<JensGlathe[m]> yeah that was the working part.
<travmurav[m]> But @ pmos we just throw it into the default spot since we generate system images offline
<JensGlathe[m]> using sd-boot was necessary bc X14 UEFI has no keyboard with grub
* travmurav[m] mumbles something about driver loading dir in sd-boot
<JensGlathe[m]> JosDehaes[m]: For the fun of it X14 goes to 24.10 now
<JensGlathe[m]> then I should create an X14 dtb I guess
<JensGlathe[m]> oh wonder
<JensGlathe[m]> 24.10 has working keyboard with the X14
<JensGlathe[m]> I feel a little having had
<JensGlathe[m]> kekse42.
<JensGlathe[m]> argh
<pikkumunkki[m]> Has anyone ever built or tried to build an Android bootable image for one of the aarch64 laptops, like the X13s?
<JensGlathe[m]> Hmm the 24.10 (2.12-5ubuntu4) can't boot Windows, so its not clean, but kb works, and first try of booting Linux works, too
alfredo has joined #aarch64-laptops
<freekurt[m]> <pikkumunkki[m]> "Has anyone ever built or tried..." <- I don't think so, but GloDroid probably would accept such a port into their project if you decided to make one. https://github.com/GloDroidCommunity
<steev> why would you want to make the x13s less useful?
<anonymix007[m]> pikkumunkki: I've done a shallow research on booting Android and I think it's doable. There's a project similar to GloDroid: https://github.com/raspberry-vanilla
<anonymix007[m]> There's even AOSP 15 already.
alfredo has quit [Quit: alfredo]
<anonymix007[m]> Actually, Linaro guys publish articles about running AOSP with mainline kernels on Snapdragon QRDs basically each year. They probably have something to say about this.
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops
pine_appl3 has joined #aarch64-laptops
<pine_appl3> does this include RPIs?
<steev> the link from anonymix does seem to be a rpi based aosp
<steev> anonymix007[m]: do you happen to know (i'm assuming you've at least played with it?) if they have any zero2w work?
<steev> or is the 512MB a non-starter for android these days
<pine_appl3> i meant the pi 3, 4 etc
<freekurt[m]> Well GloDroid already has mainline AOSP for Qualcomm Snapdragon devices right here: https://github.com/GloDroidCommunity/qcom-msm8916-series
leland[m] has joined #aarch64-laptops
<leland[m]> I've been trying to get Ubuntu 24.10 installed on my x13s without luck - wbu? I'm getting an rsync return code of 23 during install
<abby> 23 - Partial transfer due to error
<abby> very useful
<abby> thanks rsync
<leland[m]> Appears there's a read error of /tmp/tmpa_mru7n2/mount/use/lib/aarach64-linux-gnu/libjavascriptcoregtk-6.0.so.1.3.5
<abby> probably something to ask the ubuntu people about
<anonymix007[m]> freekurt: these are _very_ old Snapdragon devices, so probably not very useful here
<anonymix007[m]> steev: 512MB isn't enough for many DEs, and a lot of Android codebase is in Java which doesn't really help for low memory consumption
<steev> which is a bit ironic considering how many dumb phones run java
<anonymix007[m]> But as per https://source.android.com/docs/compatibility/15/android-15-cdd you should be good to go with qHD screen
<anonymix007[m]> steev: afaik that's a specialized version of Java which is even called "Micro Edition"
<steev> Sure, I’m not saying it’s the full Java experience, just commenting on how inefficient software gets because “devices have the resources, just use them”
<anonymix007[m]> Isn't that basically what Linux is known for? https://www.linuxatemyram.com
pine_appl3 has quit []