ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
laine has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<martiert_work>
cenunix[m]: thanks for the links to your repo. I have some stuff to steal from that :) I do have lots of stuff working, and running on my computer atm, but want to make an installer as well. We'll see :)
martiert_work has quit [Quit: WeeChat 3.8]
jhovold has joined #aarch64-laptops
martin has joined #aarch64-laptops
martin is now known as Guest5528
ptitSeb has quit [Read error: Connection reset by peer]
<jhovold>
Here's an updated wip branch for the X13s based on 6.4.2:
<jhovold>
- add missing gdsc power-domains and flags
<konradybcio>
jhovold can you try shiping PWRSTS_OFF_ON without ALWAYS_ON instead of RET_ON? the power consumption diff should be very substantial and OFF_ON should work already
pneuhardt2 has joined #aarch64-laptops
<jhovold>
konradybcio: no, we know there is work left to be done and obvisouly we need to power down some of these gdscs at some point, but these patches reflect the state of what is currently in or queued for 6.5-rc
pneuhardt2 has quit []
<jhovold>
i'm still to see a patch explaining why powering off the pcie gdsc is correct as that should lead to the controller losing its state
baozich has quit [Remote host closed the connection]
baozich has joined #aarch64-laptops
baozich has quit [Remote host closed the connection]
baozich has joined #aarch64-laptops
baozich has quit [Remote host closed the connection]
baozich has joined #aarch64-laptops
baozich has quit [Remote host closed the connection]
baozich has joined #aarch64-laptops
baozich has quit [Remote host closed the connection]
baozich has joined #aarch64-laptops
baozich has quit [Remote host closed the connection]
baozich has joined #aarch64-laptops
baozich has quit [Remote host closed the connection]
baozich has joined #aarch64-laptops
baozich has quit [Ping timeout: 480 seconds]
pneuhardt4 has joined #aarch64-laptops
pneuhardt4 has quit []
<derzahl>
why does the x13s seem to have the majority of attention vs other much cheaper aarch64 laptops with similar specs that seem near to having full support - like the galaxybook S or Acer 513 for example?
<jenneron[m]>
what do you mean by attention?
<derzahl>
i know x13s goes up to 16GB ram while i think the 2 i listed may be 8GB max. x13s has NVME? or at least something better than UFS?
<derzahl>
dev attention, here
<danielt>
X13s has much greater compute performance than the older chips (and more RAM, NVME, etc).
<jenneron[m]>
acer 513 probably doesn't need attention
<jenneron[m]>
speaking of galaxy book s I think developers just work with what they have
<clover[m]>
x13s goes up to 32GB ram, and yeah it has a (small size) NVME
<derzahl>
doesnt the galaxy S have the 8cx just like x13s? And I thought the newer mediateks like the MT819x's like the Acer has even beats the 8cx
<jenneron[m]>
it is a different SoC
<jenneron[m]>
8cx and 8cx gen 3 or something
<derzahl>
oh, dang, 32gb would be a big idfference
<jenneron[m]>
mt8192/mt8195 are being worked on by vendors already
<jenneron[m]>
but only on kernel side, not on the side of distributions
<derzahl>
still difficult for me to justify the cost of an x13s being comparable to an m1 macbook air
<jenneron[m]>
at this point again developers work with what they have
<jenneron[m]>
in postmarketOS we will support chrome os devices up to qcom 7c, no mt8192/mt8195 support just because i don't have ones and they are too expensive for me
<derzahl>
jenneron[m]: mt8192/95 being worked on to run standard linux, not just chromeos?
<jenneron[m]>
derzahl: they are being worked on in kernel for chrome os, but it also contributes to linux support
<gwolf>
derzahl:O
<gwolf>
derzahl: (sorry) I'd say, because people like to play with bigger toys ;-)
<jenneron[m]>
linux support involves userspace part
<jenneron[m]>
also*
<gwolf>
When I first got here, everybody was paying attention to the machine I have, the Yoga C630. Which is still a _great_ machine.
<jenneron[m]>
for example alsa ucm configs, i think vendors don't work on it
<gwolf>
But I guess this is a group mostly pushed by interest for self use
<derzahl>
yup, i have the c630 as well
<gwolf>
So... The best hackers hack on what they have :-)
<derzahl>
but i broke it or the battery is ded
<derzahl>
so thinking of replacing it
<gwolf>
ugh :-(
* gwolf
loves the C630 battery life FWIW
<danielt>
derzahl: IIRC the C630 and the Acer Spin 513 are pretty close to each other in terms of compute performance (I don't have a Spin 513 but I do have something with the same SoC)
<derzahl>
in truth, i barely used it. use my m1 with asahi much more. but id like to spend a couple 100$ on something another aarch64 laptop, hopefully a bit snappier than the c630
<clover[m]>
maybe look into a pinebook pro?
<clover[m]>
idk anything else for you at that price point
<jenneron[m]>
there are probably better options if you're fine with ebay
<derzahl>
derzahl: i think the spin 513 has an mt8195 right? maybe just the newer ones?
<jenneron[m]>
derzahl: CP513 is qcom 7c
<derzahl>
bought a PBP right when they came out. the c630 blows it away in just about every way
<derzahl>
never had a acer though, not sure about build quality
<robclark>
not sure about the mtk spin 513's.. the 7c one is "nice for the price".. trackpad is nice, the screen part of the enclosure is aluminum, but the base is plastic. The x13s is legit _nice_ (but you'd expect that for the price).. very much different league from the chromebook
<derzahl>
how does 7c compare to sdm850?
<derzahl>
i believe its slower.... but yeh, they seem to be going for under $100
<robclark>
7c might have a bit higher single threaded perf but lower multithread (since 2big/6little vs 4/4)
<derzahl>
btw, anyone heard any whisperings of a BSD working on an aarch64 laptop mostly?
<derzahl>
i was surprised that fbsd14 boot loader came up on my c630
<derzahl>
using a usb drive
<derzahl>
but it freezes when trying to boot, even after loading the dtb
<derzahl>
oh thats cool. maybe ill have to get a x13s after all. maybe i can find one thats password protected for cheap and rewrite the eeprom:)
<derzahl>
speaking of pinebook pros, i would think its about time for them to refresh it. would super cool if they used a risc-v soc like the latest pinetab
<clover[m]>
given their history with Rockchip it will probably be a RK3588 SOC
<saekau[m]>
Anyone daily the x13s? Curious how stable things are
<clover[m]>
i daily drive it with endeavouros (basically arch) only thing i am waiting on is camera support, but i can dual boot windows in the meantime
<clover[m]>
maybe not the only thing but only annoying thing at the moment
<saekau[m]>
Ah I'd be interested in trying endeavourOS out
<clover[m]>
there are some soc limitations that surprise people like no virtualization
<clover[m]>
so you should know before buying that you won't be able to run VMs with it
<Stirl[m]>
I never managed to get my install up and running but I might revisit soon
<clover[m]>
what part did you get stuck on?
<clover[m]>
are you just running Windows 11 right now?
<Stirl[m]>
The endeavour os script was failing
<Stirl[m]>
I don't quite remember the nature of the failure
<Stirl[m]>
And yeah, just using windows when I use that laptop
<clover[m]>
oh. make sure you are on WiFi and that the clock is sync'd
<Stirl[m]>
I think the last time I tried the mistake was probably the clock not being synced
<clover[m]>
yeah that can lead to SSL errors annoyingly
<Stirl[m]>
It takes me a long time to go through the install though because I am not good at typing in qwerty and it doesn't seem like there is a workman layout available
<clover[m]>
not sure but once new systemd is released and sd-boot is un-borked i can try to generate an iso with alternate layout
<Stirl[m]>
That would be much appreciated
Bioxvirizm-x13s[m] has joined #aarch64-laptops
<Bioxvirizm-x13s[m]>
<clover[m]> "https://forum.endeavouros.com/t..."; <- Based on this manual, I installed arch. Is the sound really quiet? Or did I do something wrong somewhere in the manual? And bluetooth is not turned on.
<clover[m]>
Did you enable Bluetooth and set the bt address? Also using the upstream also config gives you a very quiet sound I'm not sure why they went with that
<Bioxvirizm-x13s[m]>
and it can't go to sleep so it doesn't waste battery power, huh? But compared to the deabian 12 option, the arch is faster and more stable.
<clover[m]>
I use sriniks also config x13s branch
<clover[m]>
s/also/alsa/
<clover[m]>
s/also/alsa/
<clover[m]>
S2idle should be supported s3 deep suspend is not supported yet. I think it's WIP though
<Bioxvirizm-x13s[m]>
Thank you for your reply, you are doing a great job. I am unfortunately far from development, but I can follow instructions. I added your repository, and updated, is it not automatically pulling up everything I need?
<clover[m]>
Steev do you know if anyone is working on s3 suspend?
<steev>
not yet, no
<clover[m]>
Bioxvirizm-x13s: all we get so far is a s2idle suspend which does things like turn off wifi to save a small amount of battery while the system is not in use
<Bioxvirizm-x13s[m]>
clover: Can I ask you to do a little more detailed commenting in your repository? I'm honestly trying to figure it out, but when there are no comments at all, it makes me sad at my stupidity and not understanding what to do next =).
<Bioxvirizm-x13s[m]>
<clover[m]> "Did you enable Bluetooth and set..." <- How?There's no word in your manual?
<clover[m]>
Bioxvirizm-x13s: I noticed if i install alsa-ucm-conf-git-x13s instead of alsa-ucm-conf with pacman that my sound is louder by default. maybe you can try that
<clover[m]>
pacman -S alsa-ucm-conf-git-x13s then follow the instructions then reboot
<Bioxvirizm-x13s[m]>
if it's not too much trouble, in your repository there are many mesa variants I have to install something besides automatic download by hand?clover:
<Stirl[m]>
Nice! Renewing my desire to get back on this
<Stirl[m]>
Windows 11 arm is a real headache
<Bioxvirizm-x13s[m]>
clover: Your instruction is great. i've been watching your ARCH development since september, but only the last instruction helped me understand how to start the arch.
<clover[m]>
happy to help and i can't take all credit thank steev and the kernel devs too because they make the system work in the first place
<Bioxvirizm-x13s[m]>
Stirl[m]: clover: Stirl I agree. i tried to use debian according to the instructions, but i couldn't get appimage to start. after grub update debian stopped starting. i deleted the partition, got used to the idea that i would see on windows11. but the arch instructions inspired me to try again. I'm happy now. I owe you a beer.)
<steev>
Was it an arm64 appimage?
<steev>
Just because an appimage exists doesn’t mean it is the correct architecture
<steev>
Not sure about the broken grub update with Debian though, haven’t seen that here at all
<Bioxvirizm-x13s[m]>
Of course, a big bow to all of you. But without instructions all the work is useless for the average user.
<clover[m]>
usually grub will "break" for me if i update the kernel and the name changes but i dont do the grub mkconfig thing to update my grub config
<steev>
It has never once broken for me here on my x13s
<clover[m]>
its gotta be slighly different, because myself and others have noted that the upstream alsa-ucm-git is way worse (see: quieter) than this
<steev>
Ah, the 500
<steev>
5000
<steev>
Iirc upstream doesn’t have that, at all
<clover[m]>
is it possible to merge that change into upstream? im assuming it was left out for good reason and not just an oversight
<steev>
srinik: ^^
<steev>
srini would know best since it is his repo
Jasper[m]1 has joined #aarch64-laptops
<Jasper[m]1>
Hi! I've been trying to install alarm on my X13s using ironrobin's repo and I'm running into a problem where it doesn't boot. I've let grub-mkconfig create a config file and added the dtb myself. It shows something for a split second and then the screen turns off while the device stays on. Any idea what's going on? it's worth mentioning that I'm trying to get disk encryption working aswell.
<clover[m]>
Oh I haven't tried disk encryption yet
<clover[m]>
What does your grub mkcinfig output look like?
<clover[m]>
s/mkcinfig/mkconfig/
<Jasper[m]1>
clover[m]: The output of the command or the file itself?
<clover[m]>
The output of the command
<Jasper[m]1>
Okay one sec, need to reboot back to archiso
<clover[m]>
You can also show the entire grub configuration, that might be helpful too. Just use pastebin or similar service to not spam the chat
<Jasper[m]1>
Was planning that, got a recommendation on how to get that from console to a paste service?
<Jasper[m]1>
Fedora has fpaste, don't know about arch
<clover[m]>
Good point. Maybe just take a pic heh
<Jasper[m]1>
Hahaha yeah
<Jasper[m]1>
One sec, will send it soon
<clover[m]>
You might have to reboot the archiso->mount your rootfs + ESP, chroot in with arch-chroot -> run grub-mkconfig -o /path/to/grub.cfg
<Jasper[m]1>
clover[m]: I was doing it that way before
<clover[m]>
you might need GRUB_ENABLE_CRYPTODISK=y uncommented in your /etc/default/grub
<Jasper[m]1>
It is^
<clover[m]>
edit this line to be: GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 efi=noruntime pd_ignore_unused clk_ignore_unused"
<clover[m]>
also add this line: GRUB_EARLY_INITRD_LINUX_CUSTOM="initramfs-linux.img"
<Jasper[m]1>
clover[m]: I used that before when booting, just so you know. But I will change it now
<clover[m]>
then rerun the mkconfig
<Jasper[m]1>
clover[m]: > <@clover:ironrobin.net> also add this line: GRUB_EARLY_INITRD_LINUX_CUSTOM="initramfs-linux.img"
<Jasper[m]1>
Also isn't this redundant with mkconfig finding it already?
<Jasper[m]1>
>
<clover[m]>
that's really odd that mkconfig was able to find it
<clover[m]>
i always had to add it in the default config file
<clover[m]>
what does your /boot look like?
<Jasper[m]1>
clover[m]: There's an array in /etc/grub.d/10_linux that checks if they exist in the folder grub.cfg is supposed to be in. If you add the filename to it, it will add it on mkconfig.
<clover[m]>
oh, interesting. TIL
<Jasper[m]1>
s/array/for loop/, you get the point
<Jasper[m]1>
clover[m]: Me too, had to look it up because of the kernel panic I got hahahha
<clover[m]>
we are forced to use GRUB right now because of a systemd-boot issue, until the next release
<clover[m]>
it's a loader im less familiar with
<steev>
if the screen is turning off, it's quite likely that you need to shove the gpu firmware into the initrd too
<clover[m]>
it should be in there if you do pacman -S linux-x13s and you have my repo in there
<clover[m]>
umm
derzahl has joined #aarch64-laptops
<Jasper[m]1>
clover[m]: Does "my" refer to "ironrobin" or Leon?
<clover[m]>
ironrobin
<Jasper[m]1>
Okay, your archiso repo refers to Leon's repo, but you host your own on github
<Jasper[m]1>
I picked the github one and did install linux-x13s and x13s-firmware with pacstrap
<clover[m]>
cool that should have sorted you with the linux and initrd
<clover[m]>
but maybe something with encrypted disk requires gpu earlier or something
<Jasper[m]1>
<clover[m]> "what does your /boot look like?" <- ^
<Jasper[m]1>
clover[m]: From the things I did with pmos: yes
<clover[m]>
looks pretty much like mine, dtb= parameter should not be needed if you have linux option switched on in the BIOS
<Jasper[m]1>
did that yeaj
<clover[m]>
someone else in the channel was doing disk encryption right steev? dont remember if they got it fixed?
<clover[m]>
will try scrolling up a bit
<Jasper[m]1>
There was one github issue on upstream x13s-alarm repo that mentioned it
<Jasper[m]1>
But otherwise no idea
<Jasper[m]1>
And I can't scroll up past my first message here so that doesn't work if you want extra input from me haha
<clover[m]>
"x13s Gen1. I have full disk encryption and if I wait a moment before entering the passphrase to unlock the disk, the screen goes all black. If I enter the passphrase, then it eventually comes back to normal with the usual login prompt on the console. Weird 😅. Anyways good enough for what I plan to do."
<Jasper[m]1>
I'm going to guess you'll need to load whatever module handles the panel and/or gpu to be included in the initramfs
<Jasper[m]1>
Not entirely familiar with the platform (neither alarm nor the x13s) yet, so idk how to do that
<Jasper[m]1>
It's a mkinitcpio config thing maybe?
<clover[m]>
what does your /etc/mkinitcpio.conf look like?
<Jasper[m]1>
clover[m]: Pretty big, anything in particular?
<Jasper[m]1>
If you happen to know what modules I need for the display and such I might be able to put them in MODULES
<clover[m]>
the other FDE guy removed the "kms" hook from his conf file
<clover[m]>
im not sure if that will help you but you might give it a go
<clover[m]>
then you will have to remake your initrd
<Jasper[m]1>
yes
<clover[m]>
i think you just do "mkinitcpio -P"
<derzahl>
dtb doesnt need to be set for x13s? Does it use acpi or something?
<Jasper[m]1>
derzahl: It does, ACPI in it's current form does not work very well on ARM devices
<clover[m]>
it doesn't need to be set if the dtb is sitting in the ESP and your have "Linux" option enabled. then the firmware can find it
<derzahl>
oh, it still needs it though. you mean dtbloder.efi?
<clover[m]>
bamse might know more about it. it's black magic afaik
<Jasper[m]1>
<steev> "if the screen is turning off, it..." <- Is loading these handled by msm?
<steev>
no
<steev>
msm is the module but it doesn't list the firmware because that comes from the dtb
<Jasper[m]1>
steev: Assuming the firmware is bundled (since I installed the right packages), what kernel modules would I need in the initramfs to get the display to stay working?
<steev>
msm, but you need the **firmware**
<steev>
the msm module is likely already in there, but when it tries to do the handover, because the gpu firmware isn't in the initrd, it fails to do anything and display goes off
<steev>
there's a kernel patch somewhere that tries to add it, but i can't recall the status
<Jasper[m]1>
I'll try to film whatever little output J cam get
<Jasper[m]1>
*can
<Jasper[m]1>
Then I'll go to sleep, it's kinda late here
<derzahl>
if youre talking about entering an unlock password at boot, ive always had the best luck running the systemd hooks in mkinitcpio. Id add the msm & drm modules but usually Id get a black screen after booting. as long as I included the input modules (i2c_hid i2c_hid_of i2c_qcom_geni, etc) id be able to enter my unlock pw blindly and it would boot and video would kick back in
<derzahl>
thats on the c630 though
<clover[m]>
here are some modules i've used before on x13s you can try:
<clover[m]>
i don't use any of them any more since i don't need them atm
<clover[m]>
if we can nail down the right config for FDE that'd be great, since you aren't the first and probably wont be the last person coming here with issues
<Jasper[m]1>
<derzahl> "thats on the c630 though" <- Genuinely sounds like the same problem
<Jasper[m]1>
I checked the slomo, there's an error about mounting an unknown file system. Don't know what that's about. I'll go over the configs again I guess
<derzahl>
problem for me would be different behavior with different kernels. id be getting an unlock prompt perfectly and then next kernel black screen etc. took me a long time to even try enter my password anyway - figured it was just crashed
<clover[m]>
seems like an issue with the rootfs? did you do something like mkfs.ext4 /dev/root-partition?
<Jasper[m]1>
clover[m]: I did, arch-chroot works fine
<derzahl>
i think mine was an issue with the display module
<clover[m]>
yeah good point. you have a good fs if you can chroot into it.
<derzahl>
i was using zfs - both native encryption and zfs on top of LUKS
<derzahl>
including the the key file in the initrd would always work though:)