hexdump0815 has joined #linux-cros-arm
hexdump01 has quit [Ping timeout: 481 seconds]
hexdump01 has joined #linux-cros-arm
hexdump0815 has quit [Ping timeout: 480 seconds]
bonfire_ has quit [Server closed connection]
bonfire_ has joined #linux-cros-arm
deathmist has joined #linux-cros-arm
<deathmist> o/
<bonfire_> deathmist: ahoy
hexdump01 has quit [Quit: WeeChat 1.9.1]
hexdump0815 has joined #linux-cros-arm
<bonfire_> jenneron[m]: to follow up, upon trying to build my kernel I see some WARNING msgs https://bpa.st/LA3A
<bonfire_> that's being run from pmaports HEAD ~ fc08a804bc514e07c3f3883a58b367e34cb00620
<bonfire_> after zap'ing everything
<bonfire_> as you can see at bottom now it's failing... it did not do this previously with your patch
<bonfire_> so I had assumed it worked (then) and i'm just documenting my methods here so hopefully I can test and better understand
<bonfire_> (currently just trying to add crypto support to kernel for wireguard)
<jenneron[m]> bonfire_: wireguard should work after https://gitlab.com/postmarketOS/pmaports/-/merge_requests/3667
robclark has joined #linux-cros-arm
hpag[m] has joined #linux-cros-arm
<hpag[m]> bonfire_: hey, do you have developer mode on your duet?
<jenneron[m]> yes, he has pmOS on it
<jenneron[m]> not doable without developer mode
<hpag[m]> I wonder if the bootloader still has that annoying screen where you have to select boot from external disk to boot the tablet
<jenneron[m]> are you sure ctrl + d doesn't work on tablets?
<hpag[m]> As I saw, it doesn't. Not exactly sure tho
<jenneron[m]> you can try it, anyway you can disable developer mode whenever you want
<jenneron[m]> bonfire_: does booting with Ctrl + D / Ctrl + U work for you?
<hpag[m]> jenneron[m]: But it formats the device yet again
<jenneron[m]> yes
<bonfire_> hpag[m]: yes I had to enable developer mode in Chrome OS to flash PMOS and yes it still has that annoying screen
<hpag[m]> damn
<hpag[m]> bonfire_: I have the snapdragon version but I don't really want to bother with that boot screen. Is there no workaround for that?
<bonfire_> there is probably some super l33t hax0r out there who can make it work without the bootscreen. I am not that person.
<bonfire_> but yes, doing Ctrl+D at that bootscreen boots from "Internal Disk"
<hpag[m]> bonfire_: wait, does the keyboard case work on the boot screen?
<bonfire_> yes
<hpag[m]> well that's kinda nice
<bonfire_> yah it's not that big of a deal hitting up/down arrows a few times. but Crtl+D is even better :)
<hpag[m]> How's pmos on it btw?
<hpag[m]> I'm currently using it with chromeos
<bonfire_> mmm I can't quite get it to daily driver yet, but overall very promising
<jenneron[m]> bonfire_: is it because of screen issue or anything else?
<hpag[m]> bonfire_: it's a nice device I think, something I'd carry around with me rather than a bulky laptop
<bonfire_> jenneron[m]: FDE was one blocker, now wireguard is the last!
<jenneron[m]> bonfire_: FDE works as we discovered
<jenneron[m]> wireguard should work after recent upgrade too, run apk upgrade -a to get it
<bonfire_> yes I got it working with unl0kr :)
<bonfire_> oh wow, lots to upgrade!
<hpag[m]> bonfire_: does gpu and sound work?
<jenneron[m]> he has mt8183 one
<jenneron[m]> not 7c
<hpag[m]> Ah right, I forgot. Sorry
<jenneron[m]> gpu should work, 6xx are the best supported adreno in mesa
<bonfire_> sound works and gpu seems to work
<jenneron[m]> hpag: i will let you know once i have anything to test
<hpag[m]> Like what
<jenneron[m]> like pmaports branch with kernel and device packages
<hpag[m]> You have the same duet?
<jenneron[m]> no
<jenneron[m]> i still can maintain it
<jenneron[m]> well as far as i can not having a device
<hpag[m]> Oh nice
<jenneron[m]> i would like to have support for all mainlined arm chromebooks in pmos
<hpag[m]> I think tablets are pretty underrated in terms of mainline support
<bonfire_> huzzah wireguard works now :))
<hpag[m]> They would be more useful than mainlining phones
<bonfire_> I was noticing powerdrain is pretty harsh. even when powered "off"
<bonfire_> weren't you discussing this above jenneron[m] ?
<jenneron[m]> it happens on 2 of my devices
<jenneron[m]> one of them is mt8173c
<bonfire_> huh. i wonder if this would help "cpupower frequency-set -g conservative"
<jenneron[m]> doubtful
<jenneron[m]> power off issue is most likely not properly implemented power off
<jenneron[m]> or hardware issue
<bonfire_> yah at that stage for sure, but even when running device it drains rather fasst
<bonfire_> what it feels like after "poweroff" is that the device is in some state of "sleep" whereby a subtle touch of power button and i'm instantly at the boot screen
<hpag[m]> <bonfire_> "I was noticing powerdrain is..." <- really? how bad is it
<bonfire_> I get probably 1.5-2 hrs per full charge
<bonfire_> maybe less depending on what i'm doing
<hpag[m]> WHAT
<hpag[m]> bonfire_: Just reflash chromeos dude, it's not worth it
<hpag[m]> that thing has 7000mah battery and can only last 2hrs?
<bonfire_> yeah... i'm pretty close to that. but I just. despise google.
<bonfire_> and also having control over my device is of utmost importance
<bonfire_> i'll see how this cpupower tool works
<bonfire_> but it's also fun contrib and learning more :)
<hpag[m]> Well battery life is important for me, since my main reason to buy it was bringing it to places with me
* bonfire_ nods
<hpag[m]> While it would be cool to have full blown linux on it, I guess the linux container works too
<bonfire_> well that's the point of PMOS :)
<jenneron[m]> <bonfire_> "I get probably 1.5-2 hrs per..." <- it shouldn't do that even in suspend
<jenneron[m]> <bonfire_> "i'll see how this cpupower..." <- i bet on hardware issue, but also may be kernel bug
<bonfire_> hrm. yah it does feel odd