<jenneron[m]>
ellyq: do you mean after applying the changes from MR?
<ellyq>
you haven't enabled serial or used PMOS_NOSPLASH so I can't grab logs
<ellyq>
yup
<jenneron[m]>
i'm not sure how
<jenneron[m]>
someone symlinked that firmware and it worked for them, audio appears in aplay -L
<jenneron[m]>
and how would ucm configs cause that
<ellyq>
keep in mind those devices have different codecs
<ellyq>
likewise, FDE doesn't work
<jenneron[m]>
ellyq: is that installation on SD or eMMC?
<jenneron[m]>
why FDE doesn't work?
<ellyq>
i type in password in unl0kr and it drops me back
<jenneron[m]>
interesting
<ellyq>
FDE eMMC, MR on USB NVME
<jenneron[m]>
can you boot from another storage and try opening an encrypted storage with cryptsetup command?
<jenneron[m]>
this way we can see what goes wrong
<ellyq>
unfortunately not, i'm out of time
<jenneron[m]>
hm?
<jenneron[m]>
oh, nevermind
<ellyq>
i'm leaving at 8AM tomorrow, will be back on Monday
<jenneron[m]>
take your time
<jenneron[m]>
FDE is probably broken on all devices using this kernel package
<jenneron[m]>
we're missing some kernel config most likely
<jenneron[m]>
in linux-postmarketos-mediatek-mt81xx
<jenneron[m]>
ellyq: if you want to "fix" your installation you can connect that USB storage to another device and remove /lib/firmware/mediatek/sof-tplg/sof-mt8186-google-steelix.tplg
<jenneron[m]>
if it doesn't help then this breakage is not caused by the MR
<jenneron[m]>
it might be caused by some linux-next problem corrupting file system or whatever
<weirdtreething[m]>
i wonder how that tplg would break the kernel that bad
<jenneron[m]>
yeah this is why i doubt it being the reason
<jenneron[m]>
especially considering those IO errors?
<weirdtreething[m]>
yeah that's quite strange
<jenneron[m]>
we should implement fsck in pmOS initramfs, because it is dumb to not do it
<jenneron[m]>
as well as it was dumb to mount partitions by label, not uuids
<ellyq>
i can backport patches to LTS in my free time
<jenneron[m]>
ellyq: it might be tricky
<ellyq>
most of what we need is in LTS anyway because platform is similar to 8183
<jenneron[m]>
but not for mt8192/mt8195?
<ellyq>
true that, Angelo and Nicolas are working on those as we speak
<ellyq>
Angelo has MT8195 and Nicolas has MT8192
<jenneron[m]>
maybe next lts
dcz_ has joined #linux-cros-arm
dcz_ has quit [Ping timeout: 480 seconds]
hexdump01 has joined #linux-cros-arm
hexdump0815 has quit [Ping timeout: 480 seconds]
dcz_ has joined #linux-cros-arm
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-cros-arm
KREYREN_oftc has quit [Remote host closed the connection]