robclark 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
<steev> what kind of crashes, what kernels
louist103 has quit [Remote host closed the connection]
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
svarbanov has quit [Remote host closed the connection]
svarbanov has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
svarbanov_ has joined #aarch64-laptops
svarbanov has quit [Ping timeout: 480 seconds]
svarbanov_ has quit [Ping timeout: 480 seconds]
svarbanov has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
<pstef> weird, I took wip/sc8280xp-v6.8-rc7 from jhovold/linux, added config from Fedora Rawhide and "make -sj7 all" complains about pahole and suggests to disable CONFIG_DEBUG_INFO_BTF. I can do that, but how did compilation work for Fedora? I must be missing something that is not in any of the installation instructions
<jhovold> steev: ok, don't think there was anything ASPM related in 6.7.9, perhaps random changes in timing
<jhovold> adamcstephens: yeah, there are definitely still issues with the external display (e.g don't try disconnecting while suspended) but I don't think that is new
iivanov has joined #aarch64-laptops
iivanov has quit []
iivanov has joined #aarch64-laptops
svarbanov has quit [Ping timeout: 480 seconds]
svarbanov has joined #aarch64-laptops
flokli has quit [Read error: Connection reset by peer]
matthias_bgg has joined #aarch64-laptops
flokli has joined #aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
<_[m]123> <steev> "what kind of crashes, what..." <- system freeze, resets - kernel 6.8rc7
martiert has quit [Quit: WeeChat 4.2.1]
<jhovold> _[m]123: can you try disabling efivars and see if that helps? Just disable CONFIG_QCOM_QSEECOM
<jhovold> would be interesting to log any efivars accesses during boot of your distro as well
<jhovold> e.g. by slapping a printk in each of the qcom_efivar_ops
<jhovold> you and konrad both run debian/ubuntu, may or may not be relevant
<jhovold> konradybcio: ^
<jhovold> _[m]123: also is this with an external display, and are you using wayland or x?
<_[m]123> wayland, had 2 crashes, one in the night with lid closed ? and one just this morning without external screen on
<_[m]123> though it seems like the samsung screen somehow still communicates with the laptop even when it's turn off - very normal 🙂
martiert has joined #aarch64-laptops
Nios34 has joined #aarch64-laptops
<_[m]123> it says "source enabled" in the tv logs for reason why it's still on - weird
<_[m]123> > disable Anynet+ (HDMI-CEC).
<_[m]123> this should fix
KREYREN_oftc has quit [Remote host closed the connection]
Nios34 has quit [Ping timeout: 480 seconds]
jglathe_ has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
ellyq has quit [Ping timeout: 480 seconds]
Amber_Harmonia_ has quit [Ping timeout: 480 seconds]
jglathe_x13s has joined #aarch64-laptops
<steev> hrmpf
<steev> same wifi router/modem, moved it to the new place. instead of the mdsu bit insufficient, i now get spammed with htc rx: insufficient length
<_[m]123> <_[m]123> "> disable Anynet+ (HDMI-CEC)...." <- > <@nino:matrix.libre.brussels> > disable Anynet+ (HDMI-CEC).... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/AOGaCpCgaqthYyokGqcSXkgp>)
<_[m]123> * it didn't grrr crap software
<_[m]123> I only see kde related stuff in logs mm
<jhovold> Here's an updated wip branch for the X13s:
<jhovold> Changes include:
<jhovold> - fix serial console regression in 6.4 (CRD)
<jhovold> - disable pcie aspm l0s on all sc8280xp and derivative platforms
<jhovold> I also spent some more time tracking down the resets when disconnecting (or powering off) an external display. It looks like the HPD notify revert in rc7 indeed also fixed that regression even if the underlying bug is still there. Some more details here:
lollaritshe[m] has joined #aarch64-laptops
<pstef> jhovold: hey, thanks for the config, it looks pretty lean and I can see the compilation time greatly reduced. Just to confirm, the way I'm supposed to use it is this? make -sj7 johan_defconfig all; sudo make modules_install install dtbs_install; sudo dracut --kver ...; sudo reboot
<lollaritshe[m]> when i try to install linux-x13s i get an error "Errors occured, no packages were upgraded"
<lollaritshe[m]> im currently chrooting from the USB
<lollaritshe[m]> apparently haveing Linux-aarch64 and linux-firmware installed was the error
<pstef> jhovold: just to report some success, I executed that sequence of commands and at first it didn't boot, but then I noticed you had removed btrfs from the kernel, and I put it back in - now I can get to the desktop, thanks!
<adamcstephens> jhovold: haha, oops i just tried to disconnect while suspended on rc7 :)
<pstef> _[m]123: yes, according to a recent commit
<pstef> _[m]123: sorry, when I said "yes" I meant both to =yy
<pstef> single y
<lollaritshe[m]> Even with the linux-x13s kernel i dont get the option to boot it
<lollaritshe[m]> did i miss something?
<lollaritshe[m]> i used archinstall for the rest of the installation
<vadikas[m]> lollaritshe[m]: have you see ironrobin's instructions? https://github.com/ironrobin/archiso-x13s/wiki/EndeavourOS-Tutorial
<lollaritshe[m]> i was on the arch specific one
<vadikas[m]> is it arch-specific one
<lollaritshe[m]> maybe this is a bit more detailed 😅
<lollaritshe[m]> im on this one
<lollaritshe[m]> is it possible that systemdboot isnt supported?
<vadikas[m]> I don't know. But those instructions worked fine, and you can skip the custom os install to stay with generif arch/arm
<_[m]123> <pstef> "single y" <- jhovold asked just before to test with this disabled I think
<pstef> ah, sorry, I didn't notice that
<_[m]123> my question really was, should I disable the second var too
<lollaritshe[m]> <vadikas[m]> "I don't know. But those instruct..." <- will try
<steev> lollaritshe[m]: fwiw, those docs are clover[m]
<clover[m]> <lollaritshe[m]> "is it possible that systemdboot..." <- systemd-boot should work, you just have to use an uncompressed kernel IIRC
<lollaritshe[m]> how do i do that? sorry new to the aarch64 thing
<lollaritshe[m]> at least i can destroy my girlfriends windows on her x86 machine right now
<clover[m]> compressed kernel: vmlinuz-linux
<clover[m]> uncompressed kernel: vmlinux
<pstef> jhovold: on my x13s systemd-udevd is busy. sysctl status shows that it's in a loop of trying to "echo 4-0010 > /sys/bus/i2c/drivers/i2c_hid_of/bind" but if I run that I get "No such device or address". Indeed, I don't have the touchscreen. I've tried to disable it first by setting status="disabled" in the dts, then removing it. I do make dtbs_install, but that shows no change.
<clover[m]> if you just watch arch you can still follow the endeavourOS tutorial, lollar. at step 14 instead of installing endeavourOS you can just leave it and install whatever desktop packages you want manually
<vadikas[m]> clover BTW, your repository has mesa version older than in official repos, so patched mesa don't install being superseeded by official build
<vadikas[m]> I manually updated it, can make a PR if you want
jglathe_x13s has quit [Quit: Leaving]
<_[m]123> jhovold I compiled latest and turned those 2 vars off - we'll see, but I don't know how to put that print tho
<clover[m]> vadikas: i pushed Mesa 24.0.2 to my repo, can you check to see if done correctly?
jglathe__ has quit [Remote host closed the connection]
jglathe_x13s has joined #aarch64-laptops
<vadikas[m]> <clover[m]> "vadikas: i pushed Mesa 24.0.2 to..." <- pkgrel=0 , but should be >2 IMO
<vadikas[m]> > <@clover:ironrobin.net> vadikas: i pushed Mesa 24.0.2 to my repo, can you check to see if done correctly?
<vadikas[m]> * pkgrel=0 , but should be >2 IMO -- in stock repos mesa is 23.0.2-2 now
<vadikas[m]> I was thinking -- may be 690? :-)
<jglathe_x13s> X13s is on 6.8.0 now
<clover[m]> steev: will you push 6.8?
<steev> soon yeah
<clover[m]> vadikas, pkgrel has more to do with the packaging than the software version for example if a patch was added you bump the pkgrel
<vadikas[m]> yep, but they're compared directly, so larger the number the more precedence package has
<clover[m]> Yeah, but if you want my packages instead of upstream (which I recommend) you can just put the priority higher in the pacman.conf
<vadikas[m]> ok, make sense!
<steev> clover[m]: fwiw, I’m still waiting on stable to post the linux-6.8.y branch, kinda odd that it hasn’t yet
<clover[m]> Got it, ty for the update
systwi has joined #aarch64-laptops
<_[m]123> is this something relevant ?
Guest2481 has joined #aarch64-laptops