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)
FizzBuzz has joined #aarch64-laptops
FizzBuzz has quit []
derzahl has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
pg12_ has quit [Ping timeout: 480 seconds]
pg12_ has joined #aarch64-laptops
derzahl has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
<bamse> steev: unfortunately i haven't paid much attention to the audio situation lately...
<steev> well.. it works on one... and not the other and i'm just so fucking lost
<steev> userland is identical
<steev> bamse: fwiw... since it does work on one - with the 5.12 (maybe it got into 5.13 and was backported -either way, with that patch and the patch from shawn to fix the gpio in the dts, it should work now with the normal userland stuff already installed)
<bamse> i need to respin the backlight patches, will see if i have audio while doing that...
<steev> pls :)
<steev> well, the respin regardless :D
<steev> am about to test 5.13.3 but i doubt anything has changed there
<steev> bamse: it's also weird because on the c630 that doesn't have working audio, the ipa device doesn't seem to probe automatically... but on the one that does work, it does. i tried restoring windows and then re-installing just on the off chance the hardware got into a weird state, but with the 5.11 kernel from the installer, audio works perfectly
<steev> and srini still doesn't seem to have moved to oftc :(
<bamse> steev: if ipa doesn't probe automatically then your dt isn't updated...
<steev> hm
<steev> maybe it's an issue with dtbloader?
<bamse> steev: it's just a platform driver that need to be enabled in the dts for it to probe...it just used to not work after that
<bamse> steev: but with that patch i think it would probe a few versions back
<steev> i'm assuming the grep matching means its in the dtb that is loaded?
<steev> the one where everything works does *not* use dtbloader, grub loads the dtb file
<bamse> what's the content in soc@ipa../status ?
<steev> disabled
<bamse> and on your other machine?
<steev> good question, lets check
<steev> okay
<steev> though, 5.12 it says okay, but i don't get the device, only on 5.13+ do i get the device
<bamse> perhaps there's some dependency that i'm forgetting about...
<steev> should just be rmnet
<steev> in fact, when ipa doesn't work, it at least complains that it can't find the firmware
<bamse> rmnet depends on ipa, not the other way around
<steev> oh, interesting
<bamse> so iirc having just ipa working should give you rmnet_ipa0
<bamse> and with that you can link rmnet_data* interfaces ontop, which requires the rmnet driver
<steev> okay, we're on to something!
<steev> forcing loading the dtb from grub via "devicetree" entry, does give me the ipa module loading
<bamse> and audio?
<steev> not sure just yet - https://paste.ubuntu.com/p/32M2qqGdxj/
<steev> well, there's not the audio errors but there's also no audio output
<steev> does just give dummy output :/
<steev> hm
<steev> i do have to actually modprobe -r ipa and then modprobe ipa after booting for it to load the firmware; maybe i should shove it into the initrd
<steev> and i still dunno which firmware i'm supposed to be using here - on one, where it's "ipa_fws.mdt.orig" that is a file size of 6.7K, on the other it's ipa_fws.mdt.elf which is 33K
<steev> oh, interesting, i see
<steev> the 6.7k one is one that pulls in all the b0X ones, and the 33K is one that has all of them combined
<steev> because i copied only the 6.7K mdt into the initrd, and it complained it couldn't load ipa_fws.b02
<steev> yeah, okay so use the 33K size one, and throw it into the initrd, and then it'll actually come up, otherwise the module probes before the firmware is available and doesnt seem to retry at all
<steev> oh, and audio worked this boot
<steev> shawnguo: okay so... how the heck do i go about debugging why loading the dtb via dtbloader isn't working properly, but when forcing grub to via 'devicetree /usr/lib/linux-image-5.13.3/sdm850-lenovo-yoga-c630.dtb' works
<robclark> steev: did the \dtb\$sha.dtb not get updated for new kernel?
<steev> no idea
<steev> i would assume it did, but who knows
<steev> i have 2 kernels, but 3 dtbs in there?
<steev> okay, 2 of them match the 5.11 kernel, and the last one... no idea wtf it matches because both of them say they differ
<steev> robclark: i don't suppose you have some non-edk cli tool to get the chid
<robclark> hmm, I think fwupd has something?
<robclark> 3 dtb's means three separate devices supported, not three separate kernels, fwiw
<robclark> I have 12c0e5b0-8886-5444-b42b-93692fa736df.dtb and 30b031c0-9de7-5d31-a61c-dee772871b7d.dtb .. one is c630 and one should be flex5g
<steev> ah yeah mine matches the 30b...
<steev> `fwupdtool hwids` is the command to spit them all out
<steev> okay so, for some reason, dpkg -i linux-image-5.13.3blah.deb isn't updating the dtb in there
<steev> lets test manually copying
<robclark> I guess you can hack in a print to that script to show the actual chid
<steev> yeah, that did it
<steev> okay, so... is install-dtbs.py supposed to be run as a post kernel install hook?
<steev> hm, audio doesn't error out, but definitely doesn't come up every time in 5.13.3
<robclark> I guess it could run as post install hook.. I'd kinda envisioned it as being run to generate a "dtbloader fw update" (but then never had time to write a fwupd pluging to install those fw updates)
<steev> well, now that i know i need to update the dtb manually... :D
<robclark> you kinda want to only move forward, ie. if downgrading the kernel keep newer dtb..
<steev> yeah, i'm fine with that :D
<steev> i just wanted to get off the 5.11 kernel but thought the dtb got updated automatically
macc24 has quit [Quit: WeeChat 3.2]
macc24 has joined #aarch64-laptops
<derzahl> man, so seeing i put everything back from /dev/sdf the way it was and windows wifi now works. i cant figure out wth is causing grub not to automatically boot. so when grub-mkconfig runs, it thinks the /dev/sda is hd0, but when grub actually boots it thinks its hd5 and drops me to a shell. how i force grub to use hd5? its gotta be more than just changing referencers in grub.cfg, right?
<steev> i have no idea, i've never seen that
<steev> robclark: did we ever come to a conclusion about those enc frame timeouts?
<steev> ah, from the looks of it... i never pasted when i ran into it again
<robclark> I don't think so, but also haven't had a chance to try and repro or debug it.. haven't noticed anything like that on sc7180 but not sure if that is down to some sdm845 vs sc7180 thing or some difference between our userspaces..
<steev> i do happen to be using x11 (again), sdaly
<steev> oh happy day, i do still have the dumpstack hack in
<robclark> hmm, it's called from a timer.. ok, so that is a bit less useful
<steev> it does spam the ever loving shit out of... everything, when it happens
<derzahl> does the grub version built into debian-cdimage not support specifying devicetree in the boot stanza? i seem to recall something like that
<derzahl> so many crazy things happening. after doing a fresh install of https://github.com/aarch64-laptops/debian-cdimage rel4(latest), it setup that dtbloader thing that i havent used in forever. but then after recompiling steevs 5.11rc7, neither kernel boots(hangs like wrong or no device tree is loaded). tried removing dtbloader and just speicfying 'devicetree correct.dtb' from the kerne package and that gives the same results
<steev> you can specify devicetree in grub with it, that's grub, not specific to the cdimage
<steev> it has been in grub for a long time, what is missing is the ability to automatically add it to the config; ubuntu patches that, but upstream hasn't moved on it and/or ubuntu hasn't passed the patch up, i don't remember which
<derzahl> well im lost then. why do things keep changing on me? lol
<steev> well
<steev> as i said, or maybe you already took off - 5.11.0-custom is *not* the same as my 5.11-rc7
<steev> 5.11.0-custom is based on aarch64-laptops/linux's 5.11
<derzahl> nah,i saw that that
<derzahl> makes sense
<steev> while the dtb *should* work, no idea
<derzahl> thatswhy i compiled your 5.11rc7, so id have a working kernel with headers
<steev> 5.12 works pgood
<derzahl> and i know dtbs change per kernel, so i always try to use the one that comeswith the kernel
<derzahl> well. 5.12 works well except....doesnt let me type my password to unlock encrypted root
<derzahl> while 5.11.rc7 does
<derzahl> go figure
<steev> oh right, i forgot you're doing that weird zfs shit
<derzahl> well trying
<derzahl> always soo close
<derzahl> gonna try a fresh install. does anyone else have that /boot/Persisted_capsules.bin file? not sure if it came from winsows or linux
<steev> its from windows
<steev> afaiui, it's so that things will update next time you reboot while on mains, since it won't upgrade the bios or ec firmware if mains aren't applied
<steev> which is kinda... moot since there hasn't been an update to either since 2019
<derzahl> ah
<derzahl> thanksfor the background
<derzahl> its like 1/3rd of the efi partition
<steev> that's just my understanding. doesn't mean i'm correct
<derzahl> well at least I shouldbeableto safely back it up somewhere
<steev> i guess, really, it's for capsule updates, but that's why they wouldd exist?
<derzahl> not sure what a 'capsule' even is myself
<derzahl> so if i use dtbloader, do you know if it have some mechanism to update dtbs when with new kernels? it seems kinda static, and i know Ive has issues in the past using old dtbs with newer kernels or vice versa
<steev> nope, you have to copy them in yourself, i just learned that myself earlier :D
<steev> that's kinda the issue tho... because of a gpio change, 5.12+ dtb won't work with 5.11
<steev> well, they will but audio won't work
<steev> typically tho, newer dtb with older kernel is fine, but not vice versa
<derzahl> can you just specify a static dtb at grub install though? or is that broken
<derzahl> the option is there
<derzahl> grub-install --dtb=FILE embed a specific DTB
<derzahl> i had added on to grub.d/10_linux to check for a variable in /etc/default/grub and add the devicetree line. forgot to back it up tho:(
<derzahl> one more question and then im done bothering you for now. is there one already, or would it be relatively easy for me to make from your 5.11rc7 sources, a later version of the 5.11 kernel?
<steev> disclaimer: i suck at git, but you might be able to pull it down, add stable as a remote, then `git merge --rebase stable/linux-5.11.y` - i'm JUST guessing though
<steev> and then fix up anything that's broken along the way
<steev> sometimes it's just a matter of applying the patch manually and adding the files and running git am --continue or maybe it would be git merge --continue, not sure
<derzahl> oh, you know what. i just remembered that zfs 2.1.0 has any easy 'make deb-pkg' or similar option
<derzahl> so i can use 5.12.y:)
<derzahl> the zfs-dkms version in sid still doesnt support 5.12
<derzahl> but ill try that if i need to
<steev> probably
<steev> doesn't zfs have a way to make a patch that you apply to the kernel?
<derzahl> ok, one more thing i PROMISE:) wheres they latest most stripped down config for 5.12.y.
<steev> uhhh
<derzahl> i keep running into problems using my arch build config that works fine on arch, on debian
<steev> dunno how stripped down it is, but this is the one i use https://paste.ubuntu.com/p/pbXMbZGxvJ/
<derzahl> i dont think they maintain one anymore
<derzahl> since linus got upset
<derzahl> awesome. ty
<steev> i used to talk to ryao about it a bit back when i was still a gentoo dev, trying to get him to fix arm 32bit but gave up at how long it was taking
<steev> i dunno why but i absolutely positively have to use that config on the ubuntu (origins) c630, but as of 5.13, i just use shawn's distro_defconfig
iivanov has quit [Remote host closed the connection]
<derzahl> im pleasently surprised how well zfs runs on arm64
<derzahl> not sure if itd be worth it on arm32
<derzahl> especially if theres not enough ram
<derzahl> but it runs great on my pi4
<derzahl> which is why im so deadset in getting it as my root on the c630
<derzahl> the debian-cdimage config?
<derzahl> its pretty big
<derzahl> lot of stuff can be removed
<derzahl> even the one on arch i has stripped down had tons of bloat still thati never got around to removing. since id always go too far and then it wouldnt boot for some reason
<derzahl> whewww 5.11.17 slready
<derzahl> any exciting news on more powerful arm laptops coming out?
<derzahl> oh, looks like alot of progress with the m1
Guest1429 has joined #aarch64-laptops
Guest1429 has left #aarch64-laptops [#aarch64-laptops]
obeliskblack has joined #aarch64-laptops
<derzahl> damn. nobooty on 5.12.17
<derzahl> hangs for a bit and then black screens after xhci-hcd
<obeliskblack> Prebuilt images seem to brick the usb key after first boot? are these live cd isos or supposed to be flashed on eMMC built on the device
<obeliskblack> sd835 miix 630 accelerated graphics still a no go on those?
<derzahl> this is a newly compiled kernel on a working c630 ssd
<derzahl> well 5.12.14 that i previously compiled but didnt work, works now
<derzahl> yay
<derzahl> which is funny, cuz i was just telling steev that my prior custom config wasnt working on debian
<derzahl> oh well egrep '=m|=y' config-5.12.14-custom | wc -l
<derzahl> 3086
<derzahl> about 1000 less enabled options