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)
<shawnguo> Linux on cost effective Devkit 2023 - https://fileserver.linaro.org/s/5J4xCccbBJppEzQ
<shawnguo> Do not ask. Nothing really works yet except USB and efifb, but hey, it's booting without a DTB.
<HdkR> Time to wire up that DTB :)
<shawnguo> I would leave that to someone else. What I need is just an arm64 build box, and ACPI seems fine for me :)
<HdkR> Here's hoping all the reclocking mechanisms work
<shawnguo> yeah, seems lucky so far with the peripherals for basic booting
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
mcbridematt has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
laine has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
matthias_bgg has quit [Ping timeout: 480 seconds]
matthias_bgg has joined #aarch64-laptops
<abelvesa> upowerd[182588]: USB power supply /sys/devices/platform/pmic-glink/pmic_glink.power-supply.0/power_supply/qcom-battmgr-usb without usb_type property, please report
<abelvesa> any ideas?
<ardb> shawnguo: are you using ethernet over usb ?
<shawnguo> ardb: yes, the ethernet port on the box is a rt8153 usb nic
<ardb> shawnguo: ah interesting
<ardb> shawnguo: and the storage?
<shawnguo> ardb: the storage is on an usb ssd for now
<ardb> hmm ok
<ardb> so that would be the first thing to attack then
<shawnguo> yeah, NVMe storage would be the priority, but this is a weekend project, so ...
<ardb> so it's nvme/pcie based?
<shawnguo> yeah, the spec says: 32GB LPDDR4x RAM and 512GB fast NVMe storage
<ardb> not bad
<shawnguo> yeah, quite not bad at $599 :)
<shawnguo> and the uefi on this box seems got improved, at least I do not need 'efi=novamap' to boot up the device. Or x13s doesn't need either?
<ardb> shawnguo: recent kernels have that as the default
<shawnguo> ah, ah :)
<shawnguo> ardb: and recent kernel fixes broken EFI reboot/poweroff calls too?
<ardb> i wasn't aware of any issues there
<ardb> were they ever reported?
<shawnguo> but maybe that's only Flex 5G?
<ardb> ah ok
<qzed> not just flex but Surface Pro X and X13s too
<ardb> so it crashes when using resetsystem() ?
<shawnguo> so devkit seems improved on that, both poweroff and reboot just worked
<ardb> ah excellent - good to know
<ardb> that looks like some region is just missing from the EFI runtime map
<ardb> could anyone with access to such a machine run it with efi=debug and post the kernel log somewhere (from the start until the end of the crash)
<qzed> I can do that some time this evening
<ardb> excellent
<qzed> just need to do some day-time work now :-)
<ardb> qzed: please use v6.1 or earlier, i.e., without e8dfdf3162eb549d064
<qzed> okay
<ardb> although actually, for resetsystem it probably does not make a difference
<ardb> anyway, it would be good if we could correlate the faulting address with an entry in the EFI memory map (hence the efi=debug)
<qzed> yeah, I can test without that commit
<abelvesa> steev: thanks!
<steev> abelvesa: i was gonna submit it once the pmic glink patches got accepted, i wasn't sure if i should have sent something like that as a review?
<abelvesa> steev: no rush, I was just wondering if someone has already looked into it
<steev> iirc, clover had something that was complaining about it
iivanov has quit [Remote host closed the connection]
<leezu> hexdump0815: I've noticed that as of 6.1.2 / 8d89cf6ff229ff31cd4f73f5b3928564b81fc41e we need to ensure SOUNDWIRE, SOUNDWIRE_QCOM, SND_SOC_QCOM_COMMON and SND_SOC_SC7180 are enabled to have working audio on lazor. Previously at least the SOUNDWIRE options were (mistakenly) not required
hexdump0815 has quit [Quit: WeeChat 1.9.1]
hexdump0815 has joined #aarch64-laptops
<hexdump0815> leezu: thanks a lot for this info - i have added them to my config options - it looks like SND_SOC_QCOM_COMMON will come in automatically via dependency
Lucanis0 has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops
<hexdump0815> leezu: btw. did you see this message for you - not sure if you were online back then: https://oftc.irclog.whitequark.org/aarch64-laptops/2022-12-23#31746964
<hexdump0815> btw. in case someone is in the us and interested in another nice and powerful arm laptop besides the x13s: a large online store seems to have it around for 499 right now ... there is a mainline tracking chromeos kernel tree for it (i.e. v6.1) and the gpu should be supported by panfrost
<hexdump0815> according to geekbench numbers performance should be around 2/3 of the x13s i guess
<hexdump0815> proper mainlining for it is ongoing as part of the usual google chromebook mainlining efforts
<hexdump0815> its called acer cp513-2h, has 8gb ram, 128gb emmc
<qzed> ardb: unfortunately I wasn't able to capture a full log, but here is the log from boot to multi-user.target: https://paste.debian.net/1267458/
<qzed> and here is the crash on shutdown:
<qzed> so there's a part missing inbetween, I hope that's not too bad
<qzed> ^ hopefully less compressed
<qzed> let me know if you need anything else
<Caterpillar> [19:40] <steev> unlike x86 machines, just having the support in the kernel doesn't mean your machine will work, arm* need device tree files written for your device || exactly. It's Phoronix fault if I bought a X13s thinking that it was already fully working. ->> https://www.phoronix.com/news/Linux-5.20-SoCs-8cx-Gen3-Arm "With the Qualcomm Snapdragon 8cx Gen3 support is also adding the Lenovo ThinkPad X13s
<Caterpillar> laptop and reference board support. "
<steev> `but now the Linux support is getting underway.` - you didn't read the full article
<steev> getting underway does not even remotely come close to meaning fully working
<steev> could be a translation error though
<HdkR> Getting underway could have been as far as a person booting Linux through ACPI. Effectively nothing done but it gets the clicks :P
<ardb> qzed: thanks
<ardb> so 0x9b7f45a8 is in a 'boot data' region
<ardb> and the firmware should only access regions with 'RUN' in the first column (as per the EFI memory map printed at the start of the log)
<ardb> if this happens on x13s, it should be reported to Lenovo, and not papered over with a hack
<ardb> anyway, bed time ...
<qzed> have a good night
<qzed> and thanks for your insights
<qzed> steev: any idea why I might get a null-pointer error early at boot on next-20230113 (on the SPX)?
<steev> qzed: i do not, but i was getting it (i assume) as well; i skipped 13, and waited for 16
<steev> 16 boots here
<qzed> ah, neat, guess I'll give that a try then
<qzed> thanks
<steev> i say i assum because with 13 my thinkpad just sat at the grub screen showing the kernel/initrd load messages and nothing else
<qzed> so 16 boots further... but I guess something with the display/gpu goes wrong...
Evaia6310 has quit [Quit: Hack the Gibson]
<qzed> alright, 6.2-rc4 works at least
Evaia6310 has joined #aarch64-laptops