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)
<bamse>
initramfs or rootfs?
<jenneron[m]>
i think this is error not from getty, but from openrc which tries to run getty
<jenneron[m]>
initramfs step passes fine, but when it goes to rootfs (on USB) and loads adsp firmware these I/O errors appear
<bamse>
ahh, i see
<bamse>
it's plausible that your usb link somehow gets reset when loading adsp...
<bamse>
but i haven't looked into that, so i don't know
<jenneron[m]>
yeah this is annoying
<bamse>
and you're running off a dumb usb stick?
<jenneron[m]>
fully working DT boot is not possible from USB like this
<jenneron[m]>
yes, USB stick
<bamse>
no hub?
<jenneron[m]>
i tried 2 USB sticks, i also tried 2 different OTG adapters (one is from flex 5g box, another is dumb 1 USB-C > 1 USB-A)
<bamse>
i was just wondering if there was any indication of it being a USB issue or a PD issue...
<bamse>
okay, that's what i wanted to know...thanks
<jenneron[m]>
bamse: I connected it this way: OTG > USB HUB with external power supply > USB
<jenneron[m]>
this way it works
<jenneron[m]>
so the problem has to be USB losing power for a moment
<bamse>
jenneron[m]: ahh, yeah that would explain it
<bamse>
jenneron[m]: and the vbus supply is controlled by the adsp firmware...
<jenneron[m]>
do you have any ideas?
<bamse>
regarding how to fix the problem?
<jenneron[m]>
yes
<bamse>
i don't know, will have to talk to the remoteproc team
<bamse>
but i wouldn't hold my breath...install your system on the internal storage device instead ;)
<jenneron[m]>
bamse: i have system on UFS, but it took efforts to prepare it. i want a way to bootstrap a fully working DT-installation on USB in several minutes in case i mess up something
<jenneron[m]>
i have an idea to move related modules and adsp firmware to initramfs, so it would load before rootfs from USB is mounted
<bamse>
jenneron[m]: i can see the benefit of that...
<jenneron[m]>
loaded on initramfs stage and booted rootfs from USB
<HdkR>
Does the M.2 slot work on the S8G2 HDK yet? Curious since it will be a nice upgrade from my 888 board's bugged USB and non-working M.2 slots
<HdkR>
And since the board removes the two Host-A USB ports I will need a new solution for storage anyway
<bamse>
HdkR: i don't have a 8550 hdk upstream yet, but the mtp has 2 pcie controllers enabled
<bamse>
HdkR: that said, i did pick up support for the m.2 slot in sm8350-hdk for 6.3...in addition to hdmi support and a few other things
<HdkR>
Sadly I'm running some kernel given to me on the 8350 so I don't know how viable upgrading to 6.3 is
<HdkR>
Fairly old 5.15 kernel since I haven't upgraded it
<bamse>
any specific features you're in need of?
<HdkR>
On 8350 I would enjoy the idea of booting off NVMe because currently moving the mouse locks the system up, including IO until I stop
<HdkR>
er, booting off whatever doesn't matter, mounting my storage to nvme is the main thing
<HdkR>
And the nvme on the 8350 board just...doesn't show up
<HdkR>
Becomes more of a pressing issue on 8550 since it loses two fo the USB ports
<bamse>
hmm, not using nvme might not be optimal, but the system shouldn't lock up because you're moving the mouse :)
<bamse>
i haven't tried the m.2 support on the 8350 hdk myself...just assumed that the person posting the patches tested it...
<HdkR>
I agree that it shouldn't lock up. It's a pain when testing games with mouse movement though :P
<bamse>
i had a similar thing on one of the laptops for a while...had the wrong irq specified for some device...
<bamse>
too bad that i gave away my spare 8350 hdk
<HdkR>
I'll be mostly moving away from the 8350 once X13s has GPU
<HdkR>
So the problem will go away once that happens :P
<jenneron[m]>
bamse: btw when you will work on flex 5g, can you share your /lib/firmware/qcom? i want to make sure that yoga 5g and flex 5g firmware signed with the same keys
<jenneron[m]>
i mean i want to try to load flex 5g firmware on yoga 5g
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
<steev>
jhovold: is it common for the rtc to be 1 second fast?
<steev>
but can confirm that i get rtc on the x13s here
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
steev_ has joined #aarch64-laptops
steev_ has quit [Remote host closed the connection]
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
alfredo has quit [Quit: alfredo]
<mani_s>
steev, that's what we are guessing. I have already seen couple of differences between mine and johan's CRD. So most likely the firmware.
<mani_s>
One more difference is, my device runs off nvme compared to ufs on johan's device
<mani_s>
but that shouldn't make any difference atleast for efivars case
<jhovold>
steev: the rtc on my x13s is running a little fast too, adds up to ten seconds over a week or so iirc. still using ntp as well