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
phire_ has joined #aarch64-laptops
phire is now known as Guest912
phire_ is now known as phire
Guest912 has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #aarch64-laptops
<steev>
my understanding is that they aren't reaching a point where they can ls it?
<steev>
i believe you could try regulator_ignore_unused as well, perhaps it won't turn the display off
<bamse>
does dtb= on commandline work these days?
<bamse>
on sc8280xp it would just complain that secureboot was on (or something like that) and ignore it
<bamse>
anonymix007[m]: try using your bootloader to load the dtb instead of the efi-stub
<steev>
it should only complain that secureboot is on, if it's on
<steev>
afaik, clover does it that way
iivanov has joined #aarch64-laptops
<bamse>
steev: well, i might have given it 2 seconds of attention, but that's what the log told me...
<steev>
i don't actually know :( i put mine on the efi partition not on boot
<robclark>
anonymix007[m], bamse: dtb on cmdline works.. that is what I use. it should be in esp and path is relative to esp
<steev>
oh
<bamse>
steev: i also have no idea which device this was on, so it might not be a relevant data point...hence my question
<bamse>
robclark: cool!
<robclark>
ie. put it in /boot/efi/foo.dtb and use dtb=foo.dtb
<steev>
bamse: t14s iirc
* bamse
has entered the future and uses UKIs!!!
<robclark>
(I've been using dtb= cmdline exclusively.. no idea if fedora's grub supports doing it the other way)
<steev>
robclark: if it's remotely modern it *should* support devicetree=/path/to/it
<robclark>
idk if grub is still a massive pile of distro patchstack on top of upstream like it was a few years ago
<steev>
grub itself supports it, but afaik unless you have a patchset, it doesn't set it up automagically (pmOS and ubuntu do iirc)
<robclark>
but dtb= on cmdline is easy and simple
<steev>
this is true
<steev>
bamse: oh, i have a patch for you, i should submit it. just a minor thing to add wakeup-source to keyboard/touchpad for the flex because i was tired of shutting it and opening it back up to wake it up
<bamse>
if you put DeviceTree=/boot/dtbs/xyz.dtb in your /etc/kernel/uki.conf...then as mkinitcpio generates the uki, it will include that devicetree
<steev>
wtf is uki
<bamse>
steev: it's a package of kernel + ramdisk + optional dtb + optional splash + optional siguature stuff...baked as an efi application
<steev>
ahh
<bamse>
steev: so, you inject all your pieces into one file...and just chainload that from your bootloader
<bamse>
and per mkinitcpio.conf and uki.conf, as i install the kernel with pacman, it generates the uki, with the right dtb and it shows up in systemd-boot automagically
<bamse>
steev: yeah, i don't do the secure thing...but it looks interesting
iivanov has quit [Ping timeout: 480 seconds]
<steev>
i was really hoping old.reddit.com would make that readable but somehow it seems worse
<bamse>
so much manual craziness
<steev>
i believe that's just for doing it as part of the installer
<bamse>
steev: install systemd-ukify...so mkinitcpio has something to use...then you should have a /etc/mkinitcpio.d/*.preset for your kernel... this defines your default_image etc...comment out default_image, uncomment default_uki...then put "[UKI]\nDeviceTree=/boot/dtbs/foo.dtb" in /etc/kernel/uki.conf...your kernel commandline in /etc/kernel/cmdline...and run mkinitcpio -p <kernel-name> (the basename of the preset)
<bamse>
out comes a .uki file in the default_uki path...then just chainload that
<steev>
i may give it a whirl
<bamse>
or if you're running systemd-boot, just place it in /boot/EFI/Linux and systemd-boot will find it automagically, not entries needed
<steev>
that's spiffy
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
alfredo has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Read error: No route to host]
iivanov has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #aarch64-laptops
iivanov has quit [Quit: Leaving...]
<jhovold>
Here's an updated wip branch for the X13s:
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
jlinton has quit [Quit: Connection closed for inactivity]
<anonymix007[m]>
bamse: this is what I already do, dtb is passed via grub's `devicetree=` parameter. Either way, it's quite painful to use a keyboard in grub since it constantly registers double clicks and doesn't even support holding keys.
<anonymix007[m]>
The issue is that after this screen just turns black and never comes back
alpernebbi has joined #aarch64-laptops
<Jasper[m]>
Has anyone had their Arrow order ship yet?
<Jasper[m]>
<anonymix007[m]> "The issue is that after this..." <- Do you have FDE configured? Could you turn on a ssh service and remote in to fetch logs?
<anonymix007[m]>
No, I don't. How would I do that? I don't have a usb-ethernet dongle and wifi probably won't work yet
<Jasper[m]>
Ah the usb dongle would be a way to do it
<anonymix007[m]>
Is there a way to set up RNDIS USB Gadget early and ssh into this machine from a second PC via USB?
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
weirdtreething_ has joined #aarch64-laptops
weirdtreething has quit [Ping timeout: 480 seconds]
weirdtreething_ is now known as weirdtreething
alpernebbi has quit [Ping timeout: 480 seconds]
mlau has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
alpernebbi has joined #aarch64-laptops
<mlau>
Hello, can anyone please provide a download for a working kernel for the lenovo yoga slim 7x ?
<mlau>
my self built kernels based on jhovold-6.11 tree don't work very well
<mlau>
ath12k throws lots of pcie aer errors, sound drivers are loading but don't register with alsa
<mlau>
while nvme, usb, console and keyboard/touchpad do work quite reliably
<mlau>
also I noticed that the probe of pcie4 itself causes lots of spontaneous reboots
<mlau>
and is it normal that lspci cannot decode the ath12k pci device?
iivanov has quit [Remote host closed the connection]
<kuruczgy[m]>
mlau: You probably also want to extract the modules from the initramfs. But first I would just recommend booting it normally, see if it works, before doing the extraction :)
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
clover[m] has joined #aarch64-laptops
<clover[m]>
6.10.5 pushed to ironrobin repos
<robclark>
jhovold: btw mesa 24.2.0 is released now.. so I guess it would be ok to drop the gpu chipid hack
<alx___>
someone seen this error before? pcie_3a_gdsc status stuck at 'off'
<steev>
i've been seeing a *lot* of the wmi tlv parse failures yesterday and today
<steev>
clover[m]: sorry :( i meant to push 6.10.6 yesterday and didn't
<clover[m]>
No problem. I've been playing catch up. Just got back from a two week cruise in Greece
<steev>
clover[m]: pushed 6.11-rc4 as well, based on johan's rc4, dropping the RELR change, since binutils 2.43 is out, and it only affected binutils > 2.42 and < 2.43, adding in the rgb sensor for the webcam, and using the power sequencer for the wifi, with the caveat that i *might* not enable the powerseq driver, and you might need to enable PCI_PWRCTL_PWRSEQ (not sure, i need to check)
<steev>
enable/module (i have it as a module here)
<steev>
sorry no, POWER_SEQUENCING_QCOM_WCN=m
iivanov has quit [Remote host closed the connection]
<mlau>
kuruczgy[m]: what source did you build this kernel from? the dtb is quite a bit larger than the one from my own builds
<kuruczgy[m]>
Even if you don't know nix, you should be able to make out the relevant parts, but ask if anything is unclear.
<kuruczgy[m]>
NixOS does add a bunch of other random config options too over `johan_defconfig`, I can dump my `/proc/config.gz` if you want.
<kuruczgy[m]>
Were you able to boot with my kernel? Did it resolve any of the issues you were having?
<mlau>
Yes the nixos kernel boots, and even wlan seems stable.
<mlau>
I'm at the moment trying to figure out where the differences are
<mlau>
I took johan_defconfig, and made everything built-in, but that is really wonly
<mlau>
*wonky
<mlau>
i.e. pcie4 with wlan is unstable, and I noticed that the dtb in your iso is 20% larger
<kuruczgy[m]>
But we are building from the same kernel commit? That sounds quite interesting... I don't think NixOS should do anything funny with the dtb
<bamse>
robclark: just do right instead...then you don't need sanitizers...
<HdkR>
valgrind asan rather than llvm asan?
<robclark>
I'm using llvm asan.. are there two libasan's?
<konradybcio>
well oryon and hot/cold-codenamed cores are probably the only non-cortex higher-than-armv8.2 ones.. so there may be some assumptions in some point of the food chain
<HdkR>
I guess valgrind doesn't call itself asan
<HdkR>
if it captures under gdb that would be cool
<HdkR>
Since I've used llvm asan a decent amount on these, haven't had a chance for Oryon
<jannau>
fedora package version suggest libasan comes from gcc, should be the library though
<konradybcio>
jannau: can m1n1 trap sigill and print out the details?
<konradybcio>
well.. the architectural thing that invokes sigill anyway
<robclark>
huh, libasan from gcc?
<jannau>
not out of the box, same behavior as running on baremetal
<jannau>
rpm -qf /usr/lib64/libasan.so.8
<jannau>
libasan-14.2.1-1.fc40.aarch64
<HdkR>
Couldn't systemd-coredump also get the SIGILL context in this state?
<jannau>
yes, it does. just remembered this as well