02:05 <push> i think i figured it out, if a usb drive is plugged in, it starts running on battery

02:12 <enyalios> is there any way to get the steam client installed? i dont see an aarch64 binary from valve anywhere

02:15 <steev> that... doesn't seem right push, i have usb drive plugged in almost non stop and no issues with battery here

02:15 <steev> but i do also plug the charger in to the "charge" port

02:16 <push> it has done it with two different usb drives

02:16 <steev> are you on the latest firmware?

02:16 <push> 1.57

02:16 <steev> i have no idea if that's the latest :D

02:16 <push> xD

02:16 <push> i think so

02:18 <push> enyalios: i wouldn't hold out for arm64 support from valve, most of their games havent even been updated for 64bit

02:18 <enyalios> i dont actually care if any games run, i just used to use streaming on my old laptop to play games that are running on my windows pc

02:19 <enyalios> but i obviously cant do that if i cant get the client installed

05:22 <HdkR> enyalios: You need to use emulation. Alternatively you can try the SteamLink for Pi application, never tried it though.

06:29 <jhovold> push: what do mean by having a usb drive plugged in, are you using an adapter with charging and a (usb-a) port?

06:30 <jhovold> if so, that can potentially break charging as bits of the usb PD protocol are not yet implemented

06:30 <jhovold> plugging in a USB driver in the other port should not make difference

06:30 <jhovold> and as people already said, charging works with both ports

06:31 <jhovold> even if i've also hit the won't charge above 90% that konradybcio once, plugging and replugging a number of times seemed to make that go away eventually

06:31 <jhovold> smells like a fw bug

06:33 <jhovold> steev: the endianess fixes make no difference on little-endian machines, basically cleanups to shut some of the test robots up

06:35 <steev> jhovold: ah... my experience with the robots (aside from the valid bugs) was that... big endian felt ignored (i haven't checked recently but i seem to recall back when i wanted to play around with arm64 big endian, i checked the odroid-c2 because i have plentiful and it should have worked but wasn't, and looking in the kernel ci for the big endian of it, was reporting success but looking at the logs of the ci, it was failing)

06:36 <steev> i should look again sometime but i'm not sure i wanna go through all the work i did the first time to get an arm64 big endian rootfs

06:37 <jhovold> some of the robots run sparse which is a static checker that will warn about potential endianess issues (which could break a big-endian machine)

06:38 <jhovold> i don't think they actually build or boot test big-endian

06:38 <steev> i'm surprised if theres anyone but me who even runs arm64 big endian, and i only did it cuz aircrack was having issues

06:39 <jhovold> but drivers should still work if anyone were to try

06:39 <jhovold> and sometime driver are shared between archs too

06:40 <steev> it looks like it does do boot

06:40 <jhovold> drivers*

06:40 <jhovold> boot-test big-endian aarch64?

06:40 <steev> https://groups.io/g/kernelci/topic/32746667?p=Created,,,20,2,0,0::,,,0,0,0,32746667 (kernel ci mailing list i assume)

06:40 <steev> yeah, looks like clang was broken but gcc should have been working, in 2019

06:41 <steev> i really only did it because aircrack, like mentioned, the dev used to be a coworker and asked me what the cheapest big endian would be since he was getting bug reports but no way to test as they wouldn't give him access and he needed to see

06:42 <jhovold> that link doesn't seem to say that the builds bots boot-tests big-endian aarch64

06:42 <jhovold> only that you can boot it

06:42 <jhovold> right?

06:43 <jhovold> but that's probably what you meant by "looks like it does do boot", i misread that to refer to the bots

06:44 <steev> there was at one point

06:45 <jhovold> ok

06:51 <steev> it's not a big deal, i'm sure there are some people out there doing it somewhere for some reason, just... yeah

06:51 <steev> i'd ended up doing it on a nanopi neoplus2 (mostly because they custom built me some with 32GB of storage instead of the base 8GB models)

06:52 <jhovold> yeah, and the drivers should still work, if anyone wants to

09:18 <Dylanger> Anyone know how/if it's possible to get a hold of someone at Collabora? I'd like to ask them some questions about the mt8195-tracking-master-rolling branch

10:49 <_[m]1> was it in the end possible for europeans to get their hands on that 2tb disk meant for that steam console?

11:14 <exeat> The new WD_BLACK SN770M seems obtainable from www.westerndigital.com

11:20 <Jasper[m]> Nice! Guess it'll trickle down to other retailers soon

11:20 <Jasper[m]> Time for an upgrade...

14:10 <push> jhovold: I have the charger straight into the furthest port and a usb-c to usb-a adapter in the second, it doesnt do it every time

14:11 <push> is the nvme drive in the x13s actually upgradable? I'm so used to apple "yeah, its removable, but its not upgradable"

14:12 <clover[m]> Yes, I upgraded to a 2TB drive that Framework sells

14:35 <jhovold> push: ok, thanks for clarifying. sounds very odd indeed

14:36 <jhovold> i have a usb-ethernet dongle instead of a mass-storage device plugged in most of the time and haven't noticed any such issues

14:39 <push> funny thing is, it still says its charging, but the time to full charge just keeps going up

15:23 <jhovold> push: hmm, that actually do sound like the issue I hit for the first time last week

15:24 <jhovold> battery reports that it is still charging, but rate slowly drops to 0 (and broke my custom battery status script)

15:25 <jhovold> stopped at 90% charge, finally got it to charge after disconnecting and reconnecting and rebooting a few times, not sure what happened still

15:25 <jhovold> sounded like konradybcio has hit this a few times as well

16:00 <push> okay, as long as im not the only one, it was doing it again this morning but i didnt have anything plugged in this time

16:01 <push> i was able to catch it before it totally died, replugging the power cable is all it takes to fix it

22:46 <clover[m]> If anyone wants to see a naked x13s cpu

22:46 <clover[m]> and here it is with some new PTM 7950

22:47 <clover[m]> I had a bit leftover so I also covered my 2 TB nvme

22:56 <push> ive had it open and it looked to me like it should be possible to use double stick tape to mount a normal length nvme drive, has anyone tried that?

22:56 <HdkR> It would work but you wouldn't be able to close the shell

22:57 <HdkR> Matrix says bye bye

22:58 <steev> rest in peace matrix bridge, sleep well sweet prince