00:17 <steev> seems right

00:18 <_`[m]1> harder to find than I anticipated

00:20 <steev> it's not official yet, so it makes sense

01:11 <pzc> Thanks for that link, Im going to give it a go on my c630 also.

01:12 <pzc> Did i read right, still no hope for wifi drivers?

01:24 <steev> ?

01:38 <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

01:39 <steev> the x13s has proper board file now too, as of 11 days ago, it was merged into upstream linux-firmware repo

02:10 <pzc> Thanks, I tried the aarch64 github guide for Ubuntu 18.04, I guess no shock wifi didn't work on that.

02:11 <pzc> that's awesome on the x13s, so awesome that's upstreamed

02:12 <pzc> I downloaded the lunar lobster iso, can't wait to try it out.

03:08 <clover[m]> <steev> "the x13s has proper board file..." <- Nice so I can remove manual step from my firmware pkgbuild?

03:09 <steev> if you have the upstream linux-firmware yeah

03:09 <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

03:16 <clover[m]> is the symlink step still needed? i.e., ln -s hw2.0/ hw2.1

05:00 <steev> i think the symlink is upstream? i dunno what arch does though; but yes

05:00 <steev> 2.1 should point to 2.0, or the files from 2.0 should also be in 2.1

08:10 <steev> on debian, they do 2 separate directories and the files themselves are symlinks

10:38 <xnox> note the above concept image is for X13s only

10:38 <xnox> we haven't yet done a multi platform iso for multiple laptops simultaniously.

13:25 <_`[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

13:26 <_`[m]1> you're like c devs?

14:10 <jenneron[m]> <hexdump0815> "jenneron: thanks a lot for the..." <- no services at initrd, just firmware

14:11 <jenneron[m]> the moment of usb powercut is loading firmware, not starting userspace services

15:43 <steev> _`[m]1: i just read the kernel sources, honestly.... and i look at what others do that are similar, or a generation before

20:27 <HdkR> C devs but a different part of the stack :P

20:45 <_`[m]1> <steev> "(⊙_◎): i just read the kernel..." <- very modest?!

20:46 <steev> no... it's literally what i did

20:46 <steev> https://lore.kernel.org/all/20230326233812.28058-1-steev@kali.org/

20:47 <_`[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

20:47 <steev> i can read it better than i can write it

20:50 <HdkR> Most of the kernel is in C. Most people can ignore the assembly parts

20:50 <_`[m]1> learn c -> just read the book yo 🙂

20:52 <HdkR> Probably not the best source the drop in to if you're going to use it as a learning source

20:52 <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)

20:53 <HdkR> My secret is to pester steev to do the work

21:00 <steev> jokes on him though, because i have no idea what i'm doing

21:08 <HdkR> Big same

21:09 <qzed> I can't say I have much of a clue most of the time either, but I can recommend https://elixir.bootlin.com/linux/latest/source for browsing through the sources

21:11 <qzed> I think this is also pretty decent (but I haven't done more than skim over it): https://sysprog21.github.io/lkmpg/

21:12 <qzed> other than that:

21:12 <qzed> knowing the very basics of C helps (forget the standard library stuff, most of that is kernel specific anyways)

21:13 <qzed> and for me getting started was really reading a lot of code... think like 99% reading for every 1% writing or so

21:16 <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.

21:17 <HdkR> Defect in the M.2 screw the extender provided I should say

21:47 <szclsya[m]> does the sn740 run hot?

21:48 <szclsya[m]> thinking about grabbing one too

21:48 <HdkR> Not sure, but the X13s does have a copper heatsink for the backside of the M.2 drive to pull away heat

21:52 <HdkR> According to the datasheet it can have transient spikes up to 6.3W but averages 65 mW

21:53 <HdkR> But considering this won't even operate at PCIe Gen 4, it won't even be getting maxed out :P

21:59 <clover[m]> Why a short one? X13s takes a full length m.2 or no?

21:59 <HdkR> clover[m]: The number of choices for 2242 drives is like...three

22:00 <HdkR> and the SN740 is the highest performing drive including both 2242 and 2230

22:01 <HdkR> The Sabrent 2242 drive I'm currently using is also double-sided, which doesn't fit in the laptop without modifications

22:07 <HdkR> clover[m]: Oh, and if by "full length" you mean 2280. No, it doesn't take those. It takes 2242

22:08 <clover[m]> Oh

23:28 <HdkR> SN740 definitely runs a bit spicy under load

23:42 <HdkR> https://docs.google.com/spreadsheets/d/1SIxqR8bJpMg7ESaAlR_6lN7A4tIEdn9FI6FQBSCap3I/edit#gid=344325347 Not a bad showing in fio bench

23:42 <HdkR> and I bet if I didn't mangle my laptop's SSD heatsink it would be fine :P

23:47 <HdkR> Roughly double the read perfand 50% more IOPs is a pretty nice improvement