00:31 <HdkR> steev: Did the GPU ever actually come up in the kernel btw? Is there a branch that I could try and tickle userspace on?

00:32 <HdkR> I've got a pair of devs that are hungry for a Vulkan device :P

05:33 <steev> sadly no, not yet

05:33 <HdkR> dangle

05:50 <HdkR> The waiting game continues

07:22 <steev> sorry :(

09:12 <steev> qzed: some changes came in to the scm driver so you'll need to make some changes before posting

09:12 <steev> 1120 has them

09:57 <qzed> Ah, thanks for the heads up

12:04 <Las[m]> Is there some centralised list of aarch64 (or really, non-x86) laptops?

15:07 <arnd> Las[m]: https://skinflint.co.uk/?cat=nb&v=e&hloc=at&hloc=de&hloc=pl&hloc=uk&hloc=eu&sort=t&bl1_id=30&xf=1482_ARM has a list of machines that you can currently buy in Germany, doesn't work as well for other countries

15:10 <arnd> https://skinflint.co.uk/?cat=nbtabl&xf=2174_Mediatek%7E2174_Qualcomm%7E2190_Tastatur has some more that are classified as "Tablet with keyboard" but that you may think of as laptops

15:27 <Las[m]> arnd: Thanks, works for me I presume as I'm in EU.

16:42 <Caterpillar> (X13s) any news if System power state S3 support is scheduled to be implemented?

16:50 <bamse> Caterpillar: s2idle is implemented and works...it just doesn't power all things down, so the power consumption is higher than it should be

16:52 <Caterpillar> bamse: according to windows prompt -> "powercfg /a" the only supported state is S0

16:53 <bamse> Caterpillar: isn't that because they only support "Modern Standby"?

16:54 <bamse> that is windows-things though, so i'm on thin ice...

16:55 <Caterpillar> bamse: here is explained well the difference https://www.youtube.com/watch?v=OHKKcd3sx2c

16:56 <bamse> i mean, on that level i know what it is...

16:58 <bamse> but regardless, there's no correlation between the output of powercfg /a and how well linux suspends on x13s...

16:58 <Caterpillar> bamse: mmh ok. In my case the machine was not suspended, it was supposed to be powered off

16:58 <Caterpillar> (on windows)

16:59 <HdkR> Nothing wrong about the device powering off. It just has power draw even when off.

17:00 <HdkR> Which an OS swap won't fix

17:02 <Caterpillar> HdkR: mmh

17:02 <Caterpillar> https://forums.lenovo.com/t5/ThinkPad-X-Series-Laptops/ThinkPad-X13s-drains-out-the-battery-when-the-system-is-off/m-p/5179307?page=2&sprinklrid=8685489475&linkId=198020539#5799688

17:03 <Caterpillar> damn I regret having bought this machine

17:06 <bamse> so it drains with the power cable attached?

17:09 <Caterpillar> bamse: not in my case, but so it seems according to the thread starter

17:10 <harvestz[m]> I recently let me x13s sit for over a month and didn't notice power drain

17:10 <harvestz[m]> s/me/my/

17:10 <harvestz[m]> though I don't have a battery indictor I guess lol. it turned on and worked for over an hour

18:41 <Caterpillar> dgilmore: do you know if one of the lastest Fedora ARM images is bootable on the X13s?

18:43 <dgilmore> Caterpillar: not that I am aware of. Grub in fedora seems to have a bug. I've only tried on my yoga c630

18:45 <Caterpillar> dgilmore: ok. Someone from Fedora devs told me the aim was to be ready to have a bootable image for F38, but I have forgotten his name

18:47 <javierm> dgilmore: did you talk with pjones ?

18:47 <javierm> I believe he has a MS dev kit so might help

19:24 <dgilmore> javierm: i pinged him about tips for debugging, but he hasn't responded

19:24 <dgilmore> Caterpillar: it's probably pbrobinson

19:33 <Caterpillar> dgilmore: thx, I will try pinging him

19:36 <dgilmore> Caterpillar: probably best to ask in #fedora-arm then others can participate also

19:36 <Caterpillar> dgilmore: yes, I have just done it

19:36 <dgilmore> :)

21:11 <clover[m]> wtf linux stopped working

21:11 <clover[m]> on my x13s

21:27 <harvestz[m]> rip. any initial thoughts on why?

21:27 <clover[m]> No I'm performing some system updates right now

21:31 <steev> what do you mean by "stopped working"

21:48 <clover[m]> Interesting I think my boot partition got completely wiped!

21:48 <clover[m]> No clue how

21:48 <Caterpillar> clover[m]: a windows update probably. My X13s Grub disappeared after a windows update

21:48 <clover[m]> Wtf

21:53 <clover[m]> OK Image is in the EFI partition though

21:53 <clover[m]> So I'm not sure why it can't find it

22:18 <clover[m]> Yeah it just suddenly can't find my Image file which is in the root of my EFI parituon. I even tried re installing systemd-boot, to no avail. This sux

22:18 <clover[m]> s/parituon/partition/

22:18 <clover[m]> Tried making a new entry, didn't work

22:25 <clover[m]> Interesting when I try to load Image.gz (the compressed kernel) it says unsupported

22:25 <clover[m]> But it doesn't say not found

22:28 <clover[m]> selmer443: are you having this issue?

22:54 <clover[m]> sort of fixed it. my EFI had some corruption so i went through the fsck prompts, then i deleted Image (one of the corrupted files according to fsck) and unzipped the compressed Image to replace it. this booted 6.2.0-rc1-0-x13s+ but now my battery levels arent working again lol

23:05 <clover[m]> rolled back to 6.0.10-1-x13s and battery levels working again

23:05 <clover[m]> Leo Shen: fyi

23:38 <szclsya[m]> hmm will check later

23:46 <steev> if the 6.2.0 rc1 is based on jhovold's, he doesn't have my patch that adds the present property to the battery