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)
<steev> seems right
<_`[m]1> harder to find than I anticipated
<steev> it's not official yet, so it makes sense
Lucanis has joined #aarch64-laptops
Lucanis0 has quit [Ping timeout: 480 seconds]
<pzc> Thanks for that link, Im going to give it a go on my c630 also.
<pzc> Did i read right, still no hope for wifi drivers?
<steev> ?
<steev> wifi has been working on the c630 since... forever? the issue comes from the fact that it needs services running and the debian installer can't start them but ubuntu doesn't use d-i afaik
<steev> the x13s has proper board file now too, as of 11 days ago, it was merged into upstream linux-firmware repo
hightower4 has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
<pzc> Thanks, I tried the aarch64 github guide for Ubuntu 18.04, I guess no shock wifi didn't work on that.
<pzc> that's awesome on the x13s, so awesome that's upstreamed
<pzc> I downloaded the lunar lobster iso, can't wait to try it out.
laine has joined #aarch64-laptops
<clover[m]> <steev> "the x13s has proper board file..." <- Nice so I can remove manual step from my firmware pkgbuild?
<steev> if you have the upstream linux-firmware yeah
<steev> the tplg can be built, if you really wanna, i dunno waht the deal is there. there seems to be a tplg repo on alsa but idk if stuff is supposed to get submitted there or what
<clover[m]> is the symlink step still needed? i.e., ln -s hw2.0/ hw2.1
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
kettenis has quit [Remote host closed the connection]
kettenis has joined #aarch64-laptops
<steev> i think the symlink is upstream? i dunno what arch does though; but yes
<steev> 2.1 should point to 2.0, or the files from 2.0 should also be in 2.1
laine has quit [Remote host closed the connection]
<steev> on debian, they do 2 separate directories and the files themselves are symlinks
godvino has joined #aarch64-laptops
godvino1 has joined #aarch64-laptops
godvino has quit [Ping timeout: 480 seconds]
godvino1 has quit [Read error: Connection reset by peer]
godvino1 has joined #aarch64-laptops
<xnox> note the above concept image is for X13s only
<xnox> we haven't yet done a multi platform iso for multiple laptops simultaniously.
godvino1 has quit []
hightower4 has quit []
indy has joined #aarch64-laptops
rfs613 has quit [Ping timeout: 480 seconds]
rfs613 has joined #aarch64-laptops
<_`[m]1> so anyone can advise some resource to read to understand what you guys are doing high level and/or specifically - I'm really interested but am too noob to know where to start
<_`[m]1> you're like c devs?
<jenneron[m]> <hexdump0815> "jenneron: thanks a lot for the..." <- no services at initrd, just firmware
<jenneron[m]> the moment of usb powercut is loading firmware, not starting userspace services
alpernebbi_ has joined #aarch64-laptops
alpernebbi has quit [Remote host closed the connection]
<steev> _`[m]1: i just read the kernel sources, honestly.... and i look at what others do that are similar, or a generation before
<HdkR> C devs but a different part of the stack :P
<_`[m]1> <steev> "(⊙_◎): i just read the kernel..." <- very modest?!
<steev> no... it's literally what i did
<_`[m]1> but you can write c? I don't even know how to try to start to get into this, but I'm sure reading the sources won't cut it
<steev> i can read it better than i can write it
<HdkR> Most of the kernel is in C. Most people can ignore the assembly parts
<_`[m]1> learn c -> just read the book yo 🙂
<HdkR> Probably not the best source the drop in to if you're going to use it as a learning source
<steev> my secret is, i just ask people i know, to do the work, and then pester them (not so often as they start to ignore me, but enough that it stays on their mind)
<HdkR> My secret is to pester steev to do the work
<steev> jokes on him though, because i have no idea what i'm doing
<HdkR> Big same
<qzed> I can't say I have much of a clue most of the time either, but I can recommend for browsing through the sources
<qzed> I think this is also pretty decent (but I haven't done more than skim over it):
<qzed> other than that:
<qzed> knowing the very basics of C helps (forget the standard library stuff, most of that is kernel specific anyways)
<qzed> and for me getting started was really reading a lot of code... think like 99% reading for every 1% writing or so
<HdkR> steev: Cloning my X13s drive over to the SN740 now. The little M.2 30->42 extender had a defect in the threads so I'm just going to capton tape the drive down once cloned.
<HdkR> Defect in the M.2 screw the extender provided I should say
<szclsya[m]> does the sn740 run hot?
<szclsya[m]> thinking about grabbing one too
<HdkR> Not sure, but the X13s does have a copper heatsink for the backside of the M.2 drive to pull away heat
<HdkR> According to the datasheet it can have transient spikes up to 6.3W but averages 65 mW
<HdkR> But considering this won't even operate at PCIe Gen 4, it won't even be getting maxed out :P
<clover[m]> Why a short one? X13s takes a full length m.2 or no?
<HdkR> clover[m]: The number of choices for 2242 drives is like...three
<HdkR> and the SN740 is the highest performing drive including both 2242 and 2230
<HdkR> The Sabrent 2242 drive I'm currently using is also double-sided, which doesn't fit in the laptop without modifications
<HdkR> clover[m]: Oh, and if by "full length" you mean 2280. No, it doesn't take those. It takes 2242
<clover[m]> Oh
pbsds has quit [Ping timeout: 480 seconds]
<HdkR> SN740 definitely runs a bit spicy under load
<HdkR> and I bet if I didn't mangle my laptop's SSD heatsink it would be fine :P
hightower2 has joined #aarch64-laptops
<HdkR> Roughly double the read perfand 50% more IOPs is a pretty nice improvement