<samueldr> I just hope I can finally work on new stuff this week
wavirc22 has quit [Ping timeout: 250 seconds]
wavirc22 has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
h0m1 has quit [Ping timeout: 246 seconds]
h0m1 has joined #nixos-aarch64
wavirc22 has quit [Read error: Connection reset by peer]
wavirc22 has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
pbb has quit [Ping timeout: 272 seconds]
pbb has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
lovesegfault has quit [Ping timeout: 246 seconds]
Danct12[m] has quit [Ping timeout: 260 seconds]
lovesegfault has joined #nixos-aarch64
Danct12[m] has joined #nixos-aarch64
lovesegfault has quit [Quit: WeeChat 2.7.1]
zarel has quit [Ping timeout: 250 seconds]
zarel has joined #nixos-aarch64
ZoomZoomZoom has quit [Ping timeout: 246 seconds]
zupo has joined #nixos-aarch64
tilpner_ has joined #nixos-aarch64
tilpner has quit [Ping timeout: 246 seconds]
tilpner_ is now known as tilpner
jtojnar_ has joined #nixos-aarch64
kai_w has quit [Quit: Konversation terminated!]
kai_w has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jtojnar_ has quit [Quit: jtojnar_]
jtojnar_ has joined #nixos-aarch64
jtojnar_ has quit [Quit: jtojnar_]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 250 seconds]
zupo has joined #nixos-aarch64
kai_w has quit [Ping timeout: 246 seconds]
kai_w has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
zupo has quit [Ping timeout: 250 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<flokli> samueldr: any experience with mtk-su?
<samueldr> no
<flokli> hurrr… I'm trying get a proper rom onto a fire 7 tablet…
<flokli> it's painful
<samueldr> amonet may be easier
<samueldr> I do have one of the fire 7, that I was thinking of trying this onto
<samueldr> but ugh, hardware that locks you out
<samueldr> that should be illegal
<flokli> okay, seems I /have/ to crack open the case
<flokli> well, so be it
<samueldr> AFAIK it's safe, as in, you can always fix a brick that way, though my memory may be wrong here
<samueldr> one thing that is highly annoying: their naming scheme
<flokli> this thing seems to be a "mustang"
<samueldr> yeah
<samueldr> it's sooo annoying since you only see "hd 7" or "7" in forum posts
<flokli> oh wat, they made it even more annoying to crack open
<flokli> no way
<samueldr> hm?
<samueldr> I haven't looked at all that in details yet
<flokli> the plastic cover now goes all around over the back
<flokli> instead of as described in https://www.youtube.com/watch?v=bPrGX7U3zb4
<samueldr> ah, though that's not the mustang
<samueldr> each revision name like that is quite different
<samueldr> I don't know that there is an amonet for mustang though
<samueldr> ah, there may be, looking at something else
<flokli> screw it, I'll just return it
<samueldr> that's the proper thing to do imo if you still can
<samueldr> they have interesting hardware, especially at the price point, but dang it, the bootloader situation is bad :(
<flokli> well, I planned to prepare this as a video call device for a family member and ship it there configured
<flokli> but as it has playstore and I won't use skype, it's just going back.
<flokli> s/has/has no/
<samueldr> yep
<flokli> I complained in the "reasons for returning" field
<flokli> maybe a human eventually reads that.
zupo has joined #nixos-aarch64
ZoomZoomZoom has joined #nixos-aarch64
lordcirth__ has quit [Remote host closed the connection]
lordcirth_ has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
<samueldr> :/ I'm concerned my pinephone broke somehow
<gchristensen> oops.... ow... what happened? :(
<samueldr> I don't know
<samueldr> it stayed unused for over a week
<samueldr> tried to boot it and it doesn't
<andi-> battery dead?
<samueldr> it should work without one
<samueldr> that was my first thought
<andi-> Any kinds of signs?
<samueldr> I let it sit for 15 minutes
<samueldr> none at all
<andi-> ouch
<samueldr> serial access silent
<samueldr> I can't remember if I did or did not erase its emmc
<samueldr> so I'll download a non-mobile-nixos image to validate
<samueldr> in the off-chance that somehow my fresh image doesn't boot
<samueldr> and no magic smoke smell either
<andi-> lesson learned: state in hardware is evil :)
<samueldr> it's concerning since it would mean that I have no way to progress
<samueldr> and more conerning: what kind of failure happened here??
<samueldr> the only thing I have in mind is the crazy static electricity here
<gchristensen> :/
<samueldr> never had anything dying though
cidkid has joined #nixos-aarch64
<cidkid> So
<cidkid> is there a way to use a different compiler for kernel then gcc6
<cidkid> for nixos-mobile
<samueldr> yes
<cidkid> gcc6 just spits out errors and stops when building mainline
<samueldr> just "kernel-builder" will use the current default stdenv's gcc
<cidkid> ooh
<cidkid> thank you
<cidkid> will keep that in mind
<cidkid> I'll try getting mainline booting tomorrow
<samueldr> asus-dumo uses a mainline kernel, too, if you want to look
<cidkid> as thats when I get my new PSU
<cidkid> *mainline booting on nix I mean
<cidkid> oh yeah and linux-firmware can just be enabled in local.nix yeah?
<cidkid> as bluetooth works but requires firmware from linux-firmware
<samueldr> there's some firmware stuff in asus-dumo
<cidkid> alright I'll take a look
<samueldr> huh
<samueldr> two different kind of power supplies didn't work
<samueldr> but A-to-C on my computer did
<gchristensen> huh
<samueldr> same non-PD dumb power supply, different cable, worked
<samueldr> fun!
<gchristensen> :|
<samueldr> I suspect the cable I was using first was power-only
<samueldr> like, two connectors only
<samueldr> while I know the red cable shipping with the pinephone is not power only
<samueldr> though weird how it failed to boot with a PD compliant charger
<samueldr> it mustn't be able to negociate
<cidkid> hmm
<cidkid> does asus-dumo build a boot img or is it different
<samueldr> different
<cidkid> ah okay
<samueldr> but the stage-1 stuff is the same even though there's no boot.img
<samueldr> the implementation detail of depthcharge vs. android-based boot are abstracted away
<cidkid> alright in theory it's added
<cidkid> don't have time atm to build
<cidkid> does the dtb=""; do anything in the device default.nix
<samueldr> I don't think it does anymore
<samueldr> I've not cleaned those up yet since it's a bigger task that's incoming
<samueldr> now that I have a good variety of devices, and experience, I should be able to inventory and redo those
<misuzu> cmake build failed for armv7l https://hydra.nixos.org/build/114972279/nixlog/1/tail
<misuzu> > build flags: -j16 -l16 SHELL=/nix/store/403iv0rgpjwdcvb28a9ya3aclm6h73hi-bash-4.4-p23/bin/bash
<{^_^}> error: syntax error, unexpected ':', expecting ')', at (string):289:12
<samueldr> >> g++: fatal error: Killed signal terminated program cc1plus
<samueldr> that's weird
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<samueldr> I'll restart the build, see
<misuzu> on my 2G orange pi it's building fine
<cidkid> Hm, how do I define what dtb to build then for my device?
<misuzu> probably failing because of -j16 -l16
<samueldr> cidkid: oh, right, that's what you'd use
<samueldr> so I guess it's still in use
<cidkid> dtb = "${kernel}/arch/arm64/boot/dts/qcom/msm8998-dumpling.dts"; should work yeah?
<samueldr> if that's the path of the dts once built :)
<samueldr> oops
<samueldr> that should be a dtb
<samueldr> wait
<samueldr> no
<samueldr> I'm even more confused
* samueldr checks correctly
<samueldr> hmmm
<samueldr> I don't know about non-vendor kernels
<samueldr> can you make Image.gz-dtb ?
<samueldr> if you can, that's how it works
<cidkid> I will try when I get my new PSU
<samueldr> otherwise, it would need the dtb to be handled by mkbootimg I figure
<samueldr> vendor kernels deal with the dtb for recent devices
<samueldr> peeking at how postmarketOS does is another option to see what's needed
<cidkid> postmarketOS uses their envkernel.sh to do everything for mainline
<cidkid> so
cidkid has quit [Remote host closed the connection]
<samueldr> weird
<samueldr> misuzu: if you see other weird killed failures like so tell me/us
<misuzu> probably some other memory-hungry builds are interfering
kai_w has quit [Remote host closed the connection]
kai_w has joined #nixos-aarch64
<samueldr> Finished at: 2020-03-20 17:29:18 (21:29 UTC)
<samueldr> (noting since it'll disappear)
<samueldr> restarted + bumped up
<samueldr> Finished at: 2020-03-20 17:39:57 (21:39 UTC)
<samueldr> so it's not one thing
dtz has quit [Ping timeout: 246 seconds]
<colemickens> What browser works best on aarch64 from nixpkgs?
<colemickens> firefox? firefox-nightly-bin from mozilla-nixpkgs? a chromium build?
<colemickens> Can you chain boot into PXE? Does that question even make sense?
<colemickens> Like a super minimal SD card image that just boots into a bootloader that can download the image and boot into it? Or that can point to a custom PXE server without router config?
<samueldr> colemickens: u-boot does pxe
<samueldr> so yeah
<samueldr> Finished at: 2020-03-20 17:29:18 (21:29 UTC) sams as the first one
<samueldr> restarted kitty, it fails, but for a real reason
<samueldr> wait, that log was transitively linked
<samueldr> restarted bash-completion