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> anyone keep win10 on their laptop? know of any good scripts that strip out all the BS?
<derzahl> if i can get the base system to be ~5GB like this one stripped down installer im using for a VM i might just a 10-15GB partition for it
derzahl has quit [Remote host closed the connection]
derzahl has joined #aarch64-laptops
<derzahl> uh oh. i restored windows from the usb and now my wifi isnt being found...
<derzahl> maybe it doesnt restore all those weird disk devices
iivanov has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
iivanov has left #aarch64-laptops [#aarch64-laptops]
iivanov has joined #aarch64-laptops
<steev> derzahl: does device manager show it at all?
<steev> robclark: only took a day to get it to happen again :D https://bpa.st/O2MQ
<steev> i'm guessing it's something to do with high cpu usage? because thinking about it, i'm hitting it when i'm running pixz against a ~8.5GB file
<steev> robclark: and i set it off to the side, ssh'd in to get that paste above... i just noticed it has finally blanked the screen, and when i run dmesg I get the following: https://bpa.st/SHXQ
<macc24> amstan: can you test 5.14 on lazor?
<derzahl> steev: I didnt install linux again yet. just messing with windows. was trying to reinstall the network driver manually last night, I dont suppose anyone knows how to get out of S mode without signing into MS? otherwise i need to make an account
<derzahl> then i can try to install the driver and see if maybe that rewrite the partitions/device
<derzahl> I have no reason to think wifi wont work again in linux - it seems to be happy once i recreated the partition table and put back the partition labels. but windows might be more picky. I have the partition types set as "linux filesystem", but they were showing as "unknown" before. might need your help later with sfdisk to get the guid of the partition types that they are actually set to
<steev> derzahl: no i mean, in the windows device manager - does it show up
<derzahl> oh. no it doesnt
<steev> i'm not even sure how to install the drivers manually, they should come from windows update
<steev> i would have thought that the usb restore would have reset all the partitions as well, not just installed windows
<derzahl> yeh, i dont know. they use the ath10k module in linux
<derzahl> but on lenovos site they say its an intel 8265 chipset
<derzahl> unless thats some generic screenshot. it was under the c630 support section though
<derzahl> if installing the windows driver does work ill boot debian usb and see if fdisk still has the partitions listed as 'linux' type
<derzahl> *doesnt
<steev> there is a c630 *chromebook* that is *not* arm64
<steev> maybe others, but it's definitely an ath10k module
<robclark> iirc there is also an "acer spin 513" that isn't a chromebook and isn't arm64
<steev> bamse: so, while trying to figure out why sound is broken on one of my c630's, i blacklisted a few of the snd modules, and after loading them manually... i get... https://bpa.st/LEVA
<derzahl> yeh, saw that. i made sure i was looking at the qualcomm snapdragon page
<steev> [limitless ~] > lsmod | grep ath
<steev> ath10k_snoc 49152 0
<steev> ath10k_core 397312 1 ath10k_snoc
<steev> ath 40960 1 ath10k_core
<steev> mac80211 798720 1 ath10k_core
<steev> cfg80211 737280 3 ath,mac80211,ath10k_core
<steev> qmi_helpers 28672 4 ath10k_snoc,qcom_sysmon,slim_qcom_ngd_ctrl,pdr_interface
<derzahl> so yeh, the intel driver utility didnt find shit. that must have just been a generic screenshot on their site
<derzahl> bluetooth is detected though
<derzahl> it looks like ath10k is a unified wifi/bluetooth device?
<steev> yes
<derzahl> if so, then its gotta that device i wrote zfs headers over
<derzahl> dammit
<steev> maybe bamse or shawnguo might know something about how to fix that, but i ddefinitely don't
<derzahl> almost tempted to ask you to dd the modemst1 and modenst2 partitions individually and try to restore them that way
<derzahl> since the device partition structure has already been recreated
<derzahl> but id be super scared of breaking wifi on linux
<derzahl> and being completely boned
<derzahl> yeh, hopefully bamse or shawnguo have a better idea:)
<derzahl> man win10 home is nearly unusable. no RDP even
<derzahl> wonder how hard it would be to get pro without paying $99
<steev> i had a spare pro license so idk
<derzahl> oh hm. a normal license works on ARM?
<derzahl> i probably have a bunch of corporate licenses i can dig up at my office
<derzahl> *would require going into the office tho*
<derzahl> or i could just ping windows guy. that sounds easier:)
<derzahl> so do you just put in a new key and it upgrades to pro? or do you need to upgrade to trial of pro or something and then add the key?
iivanov has quit []
<steev> should be able to just enter a key
<steev> i didn't even have to do that though, i just logged in to my microsoft account and it accepted whatever was in there
<bamse> steev: that kfree crash looks like a double free...presumably some error handling that went bonkers
<bamse> derzahl: bluetooth and the rf portion of wifi are implemented in the same chip, wifi firmware runs as an "app" on the modem processor (mpss)
<bamse> derzahl: if your modemst[12] are broken then it's not unreasonable to believe that the modem gets upset and is causing you issues
<bamse> derzahl: that said, modemst[12] are (supposedly) encrypted using a device specific key, so you shouldn't be able to make use of steev's files
<steev> it's still really weird that this is the case, considering audio works fine on one, but not the other
<bamse> steev: and you don't have any lingering ucm files or such? /etc/asound*?
<steev> i don't even have any kind of asound in /etc, and an rsync from the working to non-working, shows them to have no differences in the /usr/share/alsa/ directory
<derzahl> bamse: hmm. so i accidentally ran 'zpool create' on /dev/sdf which contained the modemst1/2 partitions. my wifi broke on linux. then i got the partition layout of sdf from steve and recreated it with fdisk
<derzahl> then i labeled the modemst1 and modemst2 partitions accordingly
<derzahl> that seemed to be good enough for linux since wifi started working again
<steev> bamse: actually, one thing i noticed on the non-working system, but i don't think it should matter is... /var/lib/alsa didn't exist
<derzahl> but windows is still upset
<derzahl> the only thing i think i am missing is the "partition type" originally it just showed an 'unknown' in fdisk, but since you have to select from a list of partition types in fdisk to change it, i just left it as the default 'linux filesystem'
<derzahl> steev, can you please send me the output of "sfdisk --dump /dev/sdf"?
<derzahl> i think i can use the gpt guid from that to change the type of those partitions back to what it should be
<derzahl> thanks man, you rock
<derzahl> that should be the missing piece. now i need to put linux back on and try it
<derzahl> trying to shrink down my windows install so i can justify keeping it
<derzahl> i have this FBConanWin1021H1CompactandSuperLite.iso for win10 that i used to make a VM. its footprint is about 6GBs
<derzahl> if i can figure out how to get windows on the c630 down to around there then ill just keep it as an option
<steev> no idea there... i was actually just kinda looking at that because i noticed that the machine that isn't really working... the rootfs is only about 36GB and the one where audio is working, my rootfs is about 75gb
<steev> i keep windows around on both though
<steev> mostly because... i've never been able to successfully get rid of it entirely
<steev> this really makes no sense - my windows is only taking up 12GB but windows is like "you can't shrink the disk past 77GB"
<derzahl> you probably have to defrag and then create a file full of 0's until it fills up the filesystem
<derzahl> then delete it and you should be able to shrink it down to the amount of used space