00:20 <steev> derzahl: yeah, there are a ton of options enabled that you'd.... never use... for the most part

00:31 <obeliskblack> anyone using sd835 lenovo miix 630 daily driver linux?

01:25 <steev> not i

01:25 <steev> c630s here which are sdm850s

14:53 <steev> bamse: could you maybe open a ticket in y'all's jira for srinivas that the volume control doesn't actually control volume? you only get 100% volume or 0% volume

14:58 <steev> also, despite the modem working on 5.13... i couldn't seem to get gps to get a lock

14:59 <bamse> steev: i'll ping srini and see what's up with the volume controls

14:59 <steev> :)

14:59 <steev> also mention to him that oftc exists :P

14:59 <bamse> steev: i haven't tested recently, but i am under the impression that as soon as i get a fix i stop receiving nmea updates

14:59 <steev> well the json does say nmea: false

14:59 <bamse> hehe, he is aware of oftc now, he's in our team channel :)

15:02 <steev> oh duh, it's your work, you'd definitely know the gps stuff better than me

15:03 <steev> but also, i can't stay on 5.13 for too long because of the encoder bug

15:03 <steev> so i haven't spent toooo much time testing it

15:03 <steev> i should have pinged you this weekend, i was up at the domain because coworker wanted to check out chairs at the herman miller store

15:53 <bamse> steev: well, i wrote the gpsd patch...i have no idea what happens in the black box and why it stops sending me messages after ~15 mintues

15:53 <bamse> steev: and the 15 minutes does correlate nicely with the point when the working platforms starts telling us that it has found something in the sky

21:02 <derzahl> well getting closer and closer to zfs booting i think

21:03 <derzahl> is there anything we can use on these things as a replacement for bcfg? like...anything?

21:04 <derzahl> does anyone remember what the default boot entry is before you set it to dtbloader.efi?

21:26 <derzahl> and when, say, \EFI\debian\Dtbloader.efi, is the only entry how does dtbloader know what grub instance to call next? it appears to be calling \EFI\debian\grubaa64.efi, but why?

21:27 <derzahl> theres also an \EFI\debian\dtbloaderdebug.efi file, how does it know not to call that?

21:32 <derzahl> but yeh, if i set bcfg boot 00 to \EFI\debian\grubaa64.efi none of the kernels boot, so i think it mustve been set to something different

21:36 <robclark> dtbloader isn't a shim, but a "driver".. so it doesnot use BOOTxx

21:36 <robclark> hmm, or did that get changed?

21:37 <robclark> heh, ok, ignore me.. I did change that :-P

21:45 <derzahl> robclark: hm, so what is the c630 boot 00 entry set to by default?

21:46 <derzahl> i wonder if there are any workarounds that can replace efibootmgr

21:56 <robclark> https://github.com/aarch64-laptops/edk2/commit/25c3e55cd9a66d1766c18384f45f56daa1bd8706

22:00 <derzahl> ah, thanks

22:00 <derzahl> that explains how its finding what to launch

22:02 <derzahl> now i just need to remember what the default boot entry is. because the dtbloader combo isnt workto boot my arch kernel for some reason

22:36 <steev> arch should work, i'm pretty sure bamse uses it

22:37 <steev> hard to tell though because he doesn't show up every day and mention that he uses arch btw

22:57 <derzahl> lol. im going to have to report back to the authorities on him. hes clearly violating the once per day mention code

23:12 <derzahl> steev: does your windows boot loader uefi entry point to EFI\debian\grubaa64.efi ?

23:13 <derzahl> or is did it before switching to dtbloader?

23:13 <derzahl> trying to figure out why i cant boot without dtbloader anymore, just with specifying the devicetree files

23:17 <steev> no

23:17 <steev> why would windows point at grubaa64?

23:17 <steev> oh

23:17 <steev> uefi

23:18 <steev> it looked like whatever shows as what shawn saw when he wrote the docs

23:26 <derzahl> yeh, but i just realized the doc cut off what it was actually pointing to

23:26 <derzahl> and i dont member now

23:31 <steev> ah

23:31 <steev> i don't either, i didn't really look

23:43 <steev> robclark: hm, i have figured out a way to force the encoder issue to come up

23:43 <steev> it seems like it happens whenever i compile a rust app, so... heavy cpu usage?