01:01 <steev> nothing (afaik) has been submitted yet

01:01 <steev> you would need to get the firmware from either $vendor support website, or from the driverstore on windows

01:03 <strongtz[m]> it's quite easy to get from windows driverstore

01:06 <steev> yep, it was on the x13s before we got most of the firmware into there

01:06 <steev> and the flex5g, and the c630

01:06 <strongtz[m]> robclark: I personally think my config would be handy for testing, because I don't build anything as module :p

01:06 <strongtz[m]> https://github.com/edk2-porting/linux-next/blob/work/sakuramist-x1e80100/arch/arm64/configs/x1e80100_defconfig

01:08 <robclark> yeah, it is just merging it with whatever things fedora wants that is the issue.. I did get further, it is finding rootfs and then rebooting.. but I'll look more over the weekend

08:34 <quinine> clover: https://github.com/ironrobin/x13s-alarm/blob/trunk/linux-x13s/PKGBUILD#L76 we also need to remove conflict with linux package.

08:37 <quinine> and vmlinuz-linux may need to be added as a suffix

13:21 <robclark> abelvesa, strongtz[m]: btw, what do we need in the way of bootargs.. ie. do we need clk_ignore_unused, etc? arm64.nopauth?

13:23 <jhovold> robclark: clk_ignore_unused pd_ignore_unused efi=noruntime

13:24 <jhovold> omitting the last one no longer triggers a hypervisor reset on reboot, but avoids some errors

13:29 <robclark> thx

13:31 <robclark> ok, if I init=/bin/sh I can get to a shell prompt.. so whatever was making it reboot was something later in init

13:58 <frolfer-n-a-tux> Hello. I'm trying to get linux running on a Lenovo Flex 5g. postmarket os works great but can only run it from an external disk I haven't been able to boot from internal disk. On debian I finally got installer to boot using efi shell but keyboard doesn't work. I can also boot a fedora workstation image but also no keyboard

13:59 <frolfer-n-a-tux> Any experiences with the lenovo flex 5g?

13:59 <jenneron[m]> frolfer-n-a-tux: the problem is kernel, not a distribution

14:00 <frolfer-n-a-tux> I'm guessing only the postmarketos has all your patches so far?

14:00 <frolfer-n-a-tux> *kernel

14:00 <jenneron[m]> i had been maintaining 6.1.x lts branch with working UFS and audio https://gitlab.com/sc8180x-mainline/linux/-/commits/v6.1.x/?ref_type=heads, but i'm not working on it anymore

14:00 <jenneron[m]> frolfer-n-a-tux: if you want you can take my master branch and send a MR to pmOS to upgrade kernel

14:01 <jenneron[m]> won't give UFS, but will give working headphones

14:01 <frolfer-n-a-tux> Ok so UFS is why I cannot boot from an internal install

14:01 <jenneron[m]> booting from UFS works, maybe i need to add a deviceinfo variable in pmOS

14:02 <jenneron[m]> the problem is that it crashes on high load

14:02 <jenneron[m]> unless using ancient kernel

14:04 <jenneron[m]> so fixing deviceinfo isn't worth it unless you want to debug UFS issues

14:08 <frolfer-n-a-tux> The whole I thought EFI was going to be my only problem with internal disk

14:08 <frolfer-n-a-tux> *time

14:09 <frolfer-n-a-tux> I have a nice install on an external nvme thats really fast compared to running off of flash drives

14:12 <robclark> jhovold: any idea where I find the gmu/sqe fw in the windows partition? Or have they been posted somewhere? I found the zap fw

14:19 <frolfer-n-a-tux> jenneron: I am a long time linux user but not a long time git user lol. MR are still outside my comfort zone

14:21 <jenneron[m]> frolfer-n-a-tux: kernel development is out of my comfort zone either

14:21 <jenneron[m]> at this point i decided for myself that i need a new laptop rather than this

14:21 <jenneron[m]> most likely x86 this time

14:23 <frolfer-n-a-tux> I had an x86 chromebook but put chromeos back on so one of the kids could use it for college

14:23 <jenneron[m]> although merge requests are straightforward if you can create a branch and commit there

14:24 <frolfer-n-a-tux> But then I saw all the recent activity on getting qualcomm suport in linux and went out an bought an arm laptop

14:24 <jenneron[m]> recently?

14:24 <jenneron[m]> do you mean flex 5g?

14:25 <jenneron[m]> totally recommend to return it back, heh

14:25 <frolfer-n-a-tux> Well 2023/2024 google searches showing all your commit activity

14:25 <jenneron[m]> uh

14:26 <frolfer-n-a-tux> I had ordered a x13s but buyer never shipped so then I saw the flex 5g

14:26 <jenneron[m]> that was me upstreaming some changes to kernel

14:26 <jenneron[m]> without audio and touchscreen though

14:26 <robclark> as far as qc laptops, the x13s is pretty well supported with a few known issues.. later in the year I expect the x1 laptops to be pretty well supported, but it is really early stages now

14:26 <jenneron[m]> but i'm not upstreaming anything else, so it's probably correct to say that no one works on flex 5g anymore

14:27 <frolfer-n-a-tux> Ah ok

14:28 <jenneron[m]> frolfer-n-a-tux: if you don't need a powerful device, you can check out 7c and mt8183 chromebooks

14:28 <frolfer-n-a-tux> so ufs issues is specific to the flex 5g and the ufs driver

14:28 <jenneron[m]> cheap and well supported in linux

14:28 <jenneron[m]> frolfer-n-a-tux: they might be specific to all sc8180x devices, but i don't know

14:29 <frolfer-n-a-tux> I forgot I still have another x86 device

14:29 <jenneron[m]> i have issues with an sdm845 phone too, i wouldn't be surprised if every device had this problem but no one noticed

14:29 <frolfer-n-a-tux> the one I am using to chat

14:29 <jhovold> robclark: no, and afaik they haven't been posted anywhere so not sure where strongtz[m] got them

14:29 <frolfer-n-a-tux> c720 peppy

14:29 <jhovold> I think qzed extracted the gmu fw for the X13s from some win binary

14:30 <jhovold> before qcom released it

14:30 <jenneron[m]> nevermind, i have another sdm845 device without problems

14:31 <robclark> jhovold: ok.. well I'll try random android fw for now

14:31 <frolfer-n-a-tux> So the x13s and flex-5g are both 8cx but different soc?

14:31 <strongtz[m]> robclark: tbh I extracted them from the linaro debian demo image

14:31 <strongtz[m]> https://git.codelinaro.org/linaro/qcomlt/demos/debian-12-installer-image/-/blob/master/debian-12-installer.img

14:31 <robclark> ahh

14:32 <robclark> I forgot about that

14:33 <frolfer-n-a-tux> where's the best place to track kernel commits

14:34 <strongtz[m]> frolfer-n-a-tux: x13s is 8cx gen3 (sc8280xp)

14:35 <jenneron[m]> and x13s doesn't use UFS afaik

14:35 <frolfer-n-a-tux> yeah it doesn't

14:35 <frolfer-n-a-tux> i should have waited longer for the x13s to ship lol

14:36 <frolfer-n-a-tux> jenneron: i do appreciate all the work you've done so far on sc8180x

14:36 <robclark> strongtz[m]: btw, did you keep the windows partition? Normally I would remove it and give the whole disk to linux, but I guess there is still other signed fw files that I'll eventually need

14:36 <robclark> I guess maybe I could just tar up the windows install..

14:37 <frolfer-n-a-tux> its a resource i can use if i want to scratch that itch of doing some code and submiiting MR

14:37 <jenneron[m]> frolfer-n-a-tux: i think it needs more, a maintainer in kernel who will be fixing issues that appear

14:37 <jenneron[m]> because recent kernel broke UFS and partially broke GPU, and no one cares

14:38 <jenneron[m]> i also don't have time to debug or bisect it

14:38 <frolfer-n-a-tux> i understand

14:38 <strongtz[m]> robclark: Yeah of course I've kept Windows, to me linux is more like an experiment.

14:38 <robclark> ahh, ok

14:39 <strongtz[m]> And still it's only possible to get firmware update through windows update

14:39 <jenneron[m]> robclark: you can take install.wim from recovery partition which is basically windows install

14:39 <robclark> hmm, for boot fw (not stuff loaded from win partition) we had a soln for that for x13s

14:39 <konradybcio> the MBNs are shipped with WU drivers

14:39 <strongtz[m]> I would always do a full driver backup on such laptops anyway

14:40 <konradybcio> you should have a couple .mbn files couple dirs into C:\Windows\system32

14:40 <robclark> I'm hoping for the linux-fimrware stuff, lenovo will be cool again and post to linux-firmware

14:40 <robclark> strongtz[m]: jfyi if you are going to post yoga dts as well:

14:40 <robclark> https://www.irccloud.com/pastebin/x7vSpn6s/

14:42 <strongtz[m]> Thanks! Though I would probably upstream the asus laptop only for now, since that one is the most tested

14:44 <robclark> I guess for that it would be "qcom/x1e80100/ASUS/$first_part_of_dmi_string/qcdxkmsuc8380.mbn"

14:52 <strongtz[m]> robclark: the kernel shows `DMI: ASUSTeK COMPUTER INC. ASUS Vivobook S 15 S5507QA_S5507QAD/S5507QAD, BIOS S5507QAD.305 06/11/2024` when booting

14:52 <strongtz[m]> I'm using qcom/x1e80100/ASUSTeK/vivobook-s15 in the dt that I'm trying to upstream though

14:53 <robclark> that sounds like it should work

14:54 <robclark> tbh, I'm guessing that all the fw from a given OEM are signed with same key so having laptop model in the path is probably overkill.. but I guess we could confirm that when someone gets a t14 or multiple different laptops from same OEM

14:58 <konradybcio> signatures is one thing.. per-device configs are another

14:58 <konradybcio> e.g. sensors, electrical..

14:59 <strongtz[m]> and adsp might including battery configuration

15:01 <robclark> yeah, that might be the case for dsp fw.. it shouldn't be for zap fw (or probably venus fw)

15:01 <robclark> anyways, I guess in places where we are too specific with the path, symlinks can be used

15:15 <konradybcio> sg