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
mcbridematt has quit [Quit: Leaving]
jglathe_ has quit [Remote host closed the connection]
jglathe_ has joined #aarch64-laptops
<zdykstra>
I had sound work for me once today, all subsequent reboots had deferred loading issues just like abby (which isn't surprising, we're running the same kernel config + firmware)
Lucanis has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops
systwi has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<abby>
i think the key is "33c0000.pinctrlqcom-sc8280xp-lpass-lpi-pinctrl: Failed to get clk 'core'"
ahmed has joined #aarch64-laptops
ahmed has quit []
iivanov has joined #aarch64-laptops
martiert_work has joined #aarch64-laptops
jelly has quit [Remote host closed the connection]
jelly has joined #aarch64-laptops
<steev>
are you booting with clk_ignore_unused ?
jglathe_x13s has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
<abby>
yes
<abby>
ok changing CONFIG_PINCTRL_SC8280XP and CONFIG_PINCTRL_SC8280XP_LPASS_LPI from m to y worked
jglathe_x13s has joined #aarch64-laptops
<krzk>
abby: then probably modules or FW is missing from your initrd.
<krzk>
abby: BTW, not all firmware is in linux-firmware package, at least for newer boards.
<abby>
even with the modules for those config options in the initrd it didn't work, i needed to make them builtin
<abby>
and the clock error persisted even though sound worked
<krzk>
hm, ok, that's something new
<krzk>
abby: all your first error messages (I had to scroll up) about deferred probe are typical for missing FW files (ADSP, topology), your current now is quite different, so shall I aassume previous errors are gone?
jglathe_x13s has quit [Ping timeout: 480 seconds]
<abby>
the probe errors were all still there
<abby>
so yeah i bet it's firmware not in the initrd
<jhovold>
abby, krzk: all required fw for the X13s is in linux-firmware (the exception is venus but support for that is not in mainline either)
<krzk>
ok, then maybe something is placed incorrectly?
<krzk>
abby: when your user-space boots finally, what do you have in `grep . /sys/class/remoteproc/remoteproc*/state`
<krzk>
and if something is not as started, then you can start it with: echo "start" > /sys/class/remoteproc/remoteproc0/state
<krzk>
One of the files in remoteproc sysfs entries tells which FW is being used, so you can check if you really have that FW file in your /lib/firmware/qcom/....
<abby>
good to know, will try in a sec
<abby>
all remoteproc* report running
<abby>
0 says qcadsp8280.mbn and 1 say qccdsp8280.mbn
<abby>
which both exist in lib/firmware/...
<abby>
should I try adding those to my initrd?
jhovold has quit [Quit: WeeChat 4.2.1]
jhovold has joined #aarch64-laptops
<krzk>
abby: and sound card is running? So maybe there is no error just expected deferred probes?
<abby>
yes, it seems so
<abby>
i believe this does slow down boot, it takes ~100 seconds to go from the deferred probe messages to boot continuing
<abby>
jhovold: so the venus fw (qcvss8280.mbn) and bluetooth fw (hpnv21.b8c) that some distros are packaging isn't necessary?
<jhovold>
abby: not with mainline, no. You should make sure you have the venus fw in place if you run my wip branches that have the patches adding venus support (as this could prevent reaching the interconnect sync state otherwise depending on you config)
<jhovold>
as I mentioned in the wiki, we are indeed still missing a board file for the bluetooth, but what's in (a previous version) of linux-firmware works pretty well:
<jhovold>
abby: and distro's should not be packaging those files as they have not been released yet...
<abby>
as far as fw goes, we're reliant on lenovo/qcom/whoever contributing them to linux-firmware.git, right6
<abby>
s/6/?
jglathe_x13s has joined #aarch64-laptops
<jhovold>
right, lenovo pushes fw to linux-firmware when qcom says it's ok, but qcom has been stalling when it comes to venus and bluetooth fw
<abby>
ok the devices deferred go away after a bit and the soundcard enumerates, but it takes a bit, after boot reaches getty
<jhovold>
the bluetooth boardfile may need to be pushed by qcom directly to keep it in sync when they update the fw, which is used also for some related chips
mjeanson has quit [Ping timeout: 480 seconds]
jglathe_ has quit [Remote host closed the connection]
jglathe_ has joined #aarch64-laptops
KREYREN_oftc has joined #aarch64-laptops
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
jglathe_x13s has quit [Ping timeout: 480 seconds]
xroumegue has quit [Ping timeout: 480 seconds]
xroumegue has joined #aarch64-laptops
mcbridematt has joined #aarch64-laptops
KREYREN_oftc has quit [Remote host closed the connection]
<HdkR>
That's implying there is still a steamwebhelper.json somewhere
<HdkR>
did the rm not take in /usr/share because of permissions?
<_[m]123>
oh fck long day you're right 💤
<_[m]123>
thanks a lot ❤️
<HdkR>
https://github.com/FEX-Emu/FEX/pull/3482 Valve updated how they execute Steamwebhelper back in February and it broke our app config. Very silly situation
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #aarch64-laptops
KREYREN_ has joined #aarch64-laptops
KREYREN_oftc has quit [Remote host closed the connection]