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)
derzahl has quit [Remote host closed the connection]
derzahl has joined #aarch64-laptops
gwolf has quit [Ping timeout: 480 seconds]
gwolf has joined #aarch64-laptops
<steev> dear lord
<steev> shawnguo: would you accept a pull request to include either wget or curl on the installer? when the firmware install script fails, it's incredibly frustrating not having those installed :P
pinskia has quit [Remote host closed the connection]
pinskia has joined #aarch64-laptops
<steev> bamse: shawnguo: what's the secret to flex 5g wifi? the module is loading but there is absolutely no error whatsoever, and i'm not getting a device
<steev> also bamse, you moved the firmware on me :( it was in LENOVO/82AK and now it's in sc8180x?
derzahl has quit [Remote host closed the connection]
alpernebbi has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
<steev> [ 3123.381523] BUG: sleeping function called from invalid context at mm/util.c:761
iivanov_ has quit [Ping timeout: 480 seconds]
<steev> mailing list thread says "it's already fixed" but no link to any kinda commit :/
<macc24> well somehow i got minecraft java edition to launch on a lazor... only 40fps though
macc24 has quit [Ping timeout: 480 seconds]
jordie has joined #aarch64-laptops
jordie has quit []
<bamse> steev: we should include 82AK in the path there, i just didn't know the numbers at the time of writing that
<bamse> steev: check that the modem is up using qrtr-lookup and see that you have services on Node 0 - otherwise remoteproc probably isn't finding your firmware, then check if "ATH10k WLAN firmware service" is there - otherwise pd-mapper and tqftpserver doesn't do their job
<bamse> steev: with that you should get something from ath10k
<bamse> steev: i did hit that mm/util.c issue as well, after a few days of uptime...didn't spend any time debugging it
iivanov has quit []
<steev> bamse: ah, hm, pd-mapper definitely isn't doing it's job... it just says "no pd maps available"
<bamse> steev: then you need some .jsn files in the directory where you have the remoteproc firmware
<bamse> steev: for wifi it seems you can just borrow the modemuw.jsn from c630
<steev> ohh
<steev> yeah the jsn files are in qcom/LENOVO/82AK, i didn't think about putting them into sc8180x
<steev> now i have the wifis
<steev> okay, i'll let it sit and see if i come back to a login prompt :)
<bamse> steev: and you will need this new thing https://hastebin.com/amatejalul.json to get external display working
<bamse> i call it "charger.jsn"
<steev> okay
<bamse> reworking the ucsi_glink driver so that it can be automatically loaded (and upstreamed)...but i will respin and repost all the other things first
<steev> i'm just using your sc8180x... next branch for now
<bamse> right, so add the charger.jsn and then modprobe ucsi_glink and you should get external display working
<steev> [ 184.995947] PDR: service lookup for tms/servreg failed: -6 - guessing because i don't have anything plugged in
<bamse> hmm, no that's either that you don't have the .jsn file or that pd-mapper isn't there
<bamse> did you restart pd-mapper before modprobing?
<steev> ah, no
<bamse> i think it will say "found mux at" to signal that it found the graph link to the dp node (if i didn't remove that code)...and then i don't think it will say anything
<steev> looks right now. though i still don't have external display, just a usb-c dock thing that has an hdmi port in it
<bamse> what happens if you plug something into that then?
<bamse> i've not tested with one of those...but sboyd et al do test using that on sc7180
<bamse> steev: thanks for digging that up
<steev> it sees a usb device was plugged in, sees the ethernet adapter on it, usb ports work (plugged in a usb->sdcard adapter with a 32gb card in there), but hdmi just reports no valid signal, and i don't see anything there
<broonie> Is the USB display normally supported with Linux?
<bamse> broonie: it's not USB display, it runs DP and USB in parallel over USB-C
<broonie> Ah, I see.
<bamse> steev: so likely i need to find myself one of them dongles and see what signals we get and if i poke the DP code properly
<bamse> steev: i've only tested using a USB-C -> DP cable and a USB-C -> MST HUB -> single DP display...
<steev> this dongle is from pine64
<steev> i should probably get a better one, i don't think i've ever tested it at all
<gwolf> steev: I have just been enlightened. Thanks!
<gwolf> (i.e. about DP being run in parallel over USB-C)
<steev> gwolf: that's bamse not me that knew :D
<bamse> gwolf: there's 4 lanes, you can do 4 lanes for either function, or 2+2
<gwolf> this is -- I expected USB-C to be just a port rearrangement, and fumed at USB-C display devices not working on a USB3.0 A port
<gwolf> Oh, bamse -- then thank you as well :)
<gwolf> sorry for mixing up names
<steev> :) he's the smart one
<gwolf> bamse: However, USB3.0 also has eight lanes..?
<steev> [ 1324.030816] ath10k_snoc 18800000.wifi: failed to synchronize thermal read
<steev> also, oddly, for bluetooth, it seems to be looking for hci0: QCA Failed to request file: qca/crbtfw01.tlv - but at least Windows on it, uses crbtfw21.tlv
<bamse> gwolf: iirc on usb3 we have a single legacy lane and 2 superspeed lanes...on type-c we have a single legacy lane and four superspeed lanes
<bamse> steev: yes, i don't know why we read 01 as the ROM version...i symlinked 01 to 21 and that works fine
<steev> seems like that's just... an error message - i created the symlink too, but haven't reprobed or anything, but loading up bluetooth it sees devices
<gwolf> https://en.wikipedia.org/wiki/USB_3.0#Pinouts -- 3.0 has separate TX and RX in SuperSpeed pairs
<bamse> steev: hmm, i didn't think it would work without the firmware
<steev> it sees my ring and a few devices
<gwolf> but anyway -- I take your word on this. USB-C tunnels other "stuff" in it.
<bamse> gwolf: right, ssrx[+-] and sstx[+-]
<steev> able to connect to the ring too, although, honestly i don't know why i did...
<steev> ring being an oura
<bamse> gwolf: if you look at the type-c connector you have two sstx and two ssrx
<gwolf> OK, fair enough!
<steev> bamse: yep, same thing happens here, nothing in the logs before the reboot, just a bunch of ^@ characters
<steev> bamse: for shits and giggles, i took your patches and put them on top of latest next. there were a couple that i probably screwed up though, namely 58 and 66. drm-msm-dp-Add-missing-drm_device-backpointer.patch and drm-msm-dp-Allow-attaching-a-drm_panel.patch
<steev> compile testing now, while i clean up one of the c630s
* gwolf rubs hands greedily...
<steev> lets see what blows up
<steev> well that wasn't good heh, it booted to busybox prompt :(
derzahl has joined #aarch64-laptops
alpernebbi has quit [Quit: alpernebbi]
ndec has quit [Ping timeout: 480 seconds]
steev has quit [Ping timeout: 480 seconds]
steev has joined #aarch64-laptops
<steev> of course i'd have a typo *sigh*
<steev> bamse: disabling sleep has seemed to cause the spontaneous reboot to stop happening here - that's good. however it seems after a time, wifi breaks, and there's no more name resolution either, so running sudo takes a bit to time out resolving the hostname
<steev> bamse: are these thermals right? i was just curious to compare, so i built bottom on both the c630 and the flex, and the c630 hits that nice 89-90c, and builds it in 5m (with LMH), meanwhile the flex only gets up to about 40c and builds it in 6 minutes 24 seconds
<steev> bamse: robclark: i recall some back chat about a mesa that actually supports the gpu in the flex? maybe a merge request that hasn't happened yet?
<steev> am not finding it though
<steev> just the python file needs to be changed?
<robclark> yup
<steev> wow
<robclark> everything that is diff btwn 680 and other things was already parameterized in the dev-info table
<robclark> kinda like I was expecting to add a680 at some point :-P
<steev> :D
<steev> but still no support for the efikamx's gpu :P (i'm joking, i have no idea if it's supported or not)
<robclark> I believe it is.. that was a200 or a205, iirc?
<steev> 200 pretty sure
<steev> it has beeen a veeeeeeeeeeeeeeeeeeeeeeeeerrrrrrrrrrrrrrrry long time since i've looked at it
<steev> the smartbook just sits on my tv stand, mocking me for not getting it supported in mainline
<steev> i think i run a 3.7 kernel on it
<robclark> flto and cphealy got upstream kernel running on *some* imx5 device(s) at one point
<robclark> (along with mesa)
<steev> yeah, i'd love to drive up to austin and sit with matt for a day or so and get it into mainline
<steev> blah, bamse it seems like when the wifi "dies"/hostname resolution starts failing, that stupid invalid context is happening
<steev> i should really figure out what patch fixes taht