<aminechikhaoui> Hi, shouldn't the rpi4 kernel be built in hydra ? not sure why it's rebuilding for me using the 20.3 channel
<samueldr> it might have failed to build for random reasons, e.g. timeout
<aminechikhaoui> don't even see it in the list of jobs though
<samueldr> oh, right, 20.03 aarch64 is maybe a bit broken
<samueldr> like, other than the basic tested set, nothing is being built
<samueldr> cc gchristensen who looked at it briefly last week
<aminechikhaoui> ah bummer
<aminechikhaoui> ah wait I wasn't looking at the aarch64 channel anyway
<aminechikhaoui> now I see it has been failing https://hydra.nixos.org/build/112530293
<samueldr> still, it's stuck since the 16th
<aminechikhaoui> yeah that too
<samueldr> oh, and here it is, that dreaded random timeout :)
<samueldr> I think with the changes that were done since the 16th it's less likely to happen
<samueldr> I hope, is more of the right word
<aminechikhaoui> hm why would the build be faster ? did we change aarch64 builders or the rpi4 kernel build had some wrong config somehow
<samueldr> not faster, less crowded server
<aminechikhaoui> ah ok
<samueldr> not 100% positive of the explanation and if it worked out
lordcirth_ has joined #nixos-aarch64
<blackriversoftwa> samueldr: I hadn't seen NixOS mobile before. That's neat! Does it run on the PinePhone?
<samueldr> "kind of"
<samueldr> unverified on the final hardware still, I think
<samueldr> well, braveheart hardware
<samueldr> and anyway it needs to be updated
<samueldr> it works/worked with the devkit
<samueldr> (though my devkit grew a fault with its type-c connector that made it really awkward to develop on, that didn't help me prioritize it)
<blackriversoftwa> Ah ok.
<blackriversoftwa> What's your main dev hardware?
<samueldr> I don't have a "main" dev hardware, to try to make sure it's not becoming accidentally too attached to that platform
<samueldr> of these, the Xiaomi A1 and the Pixel XL I don't own
<samueldr> (nexus 7 2013 has not been tested working for a while)
<samueldr> though I do/did focus heavily on android-based hardware
<samueldr> I figure it's better people use hardware they already have laying around
<samueldr> and also, people may just dig in their drawer for their previous phone
<blackriversoftwa> Neat ok. I have a pixel 2 but it's my main phone... Don't think I'll be flashing it juuuust yet.
<blackriversoftwa> I have several Samsungs lying around
<samueldr> it's not ready yet :)
<samueldr> you must be based in north america, or else it's getting late for you, right?
<samueldr> (you're not forced to answer)
<blackriversoftwa> If I can ever find time to play with it
lovesegfault has joined #nixos-aarch64
<blackriversoftwa> Yeah I'm in US Eastern Time
<samueldr> right
<samueldr> so, here, we have to deal with bad telcos, both in Canada and in the United States
<blackriversoftwa> Don't I know it
<samueldr> you may not be able to bootloader unlock devices you could elsewhere
<blackriversoftwa> I think my Samsungs are unlocked but I'll check if/when I get to playing with them
<samueldr> samsung devices I haven't investigated yet, their boot chain, even with qualcomm SoC, differs
<samueldr> though it should all be possible
<blackriversoftwa> One was on Bell Canada, other was on ATT
<samueldr> though, a good rule of thumb is if lineageos runs, it should be possible to run Mobile NixOS
<clever> blackriversoftwa: ive not noticed any major problems with bell/aliant
<samueldr> corollary to this is if there is an official TWRP build, it's also generally a good indication
<blackriversoftwa> My techie brother (runs Linux on everything but not a programmer) was asking about OSS phones because he hates the "assistant" snooper-mics
<blackriversoftwa> clever: ok good to know
<samueldr> clever: the problem is the phone they sell
<clever> samueldr: ive not tried to root mine seriously yet, and i dont want to loose the data on it
<samueldr> any recent samsung phone of the galaxy range will not bootloader unlock
<samueldr> I think since the S7
<samueldr> it's all across the two northernmost north american countries
<samueldr> you just can't buy an exynos or unlockable qualcomm samsung device here
<samueldr> (in the galaxy range)
<clever> i think mine is an S5 neo
<samueldr> that may still be in the unlockable times
<samueldr> 64 bit, good
<samueldr> exynos, so most likely unlockable
<samueldr> though, gsmarena does list a different model number for Canada
<samueldr> G903W, which could be a cause for alarm
* clever looks
<samueldr> should be fine
<samueldr> Supported: SM-G903W
<clever> samueldr: `uname -a` under connectbot says armv8l
<samueldr> that wasn't a question, it's a cortex-a53, so it is aarch64
<samueldr> though that uname makes me think they shipped a 32 bit kernel
<samueldr> CPU: arm64
<samueldr> Android: arm
<samueldr> confirmed by the lineageos wiki
<samueldr> oof
<samueldr> "arm" in android-speak is 32 bit ARM
<clever> samueldr: cpuinfo says aarch64 exynos7580
<samueldr> it might be better to treat it like a 32 bit device, unless you see the developers community has stepped up and made a 64 bit build
<samueldr> yep, it *is* a 64 bit CPU
<samueldr> but your kernel is likely 32 bit
<samueldr> and here samsung joins the ranks of motorola and LG
<clever> oh, interesting, free shows 2gig of ram (as the wiki claimed) but also 1gig of swap!
<samueldr> zram most likely
<samueldr> or zswap
<clever> samueldr: /dev/block/vnswap0
<samueldr> it must be zswap
<clever> SM-G903W
<clever> thats what it says in the device status
<samueldr> yep, it was unlikely you had another model of it
h0m1 has quit [Ping timeout: 240 seconds]
h0m1 has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
lovesegfault has quit [Quit: WeeChat 2.7.1]
lovesegfault has joined #nixos-aarch64
orivej has joined #nixos-aarch64
lovesegfault has quit [Ping timeout: 256 seconds]
lovesegfault has joined #nixos-aarch64
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
lovesegfault has quit [Quit: WeeChat 2.7.1]
Acou_Bass has quit [Quit: ZNC 1.7.4 - https://znc.in]
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
Acou_Bass has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
h0m1 has quit [Quit: WeeChat 2.7.1]
h0m1 has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
vcunat has joined #nixos-aarch64
vcunat has left #nixos-aarch64 [#nixos-aarch64]
zupo has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 255 seconds]
chiefgoat has quit [Remote host closed the connection]
ryantrinkle has joined #nixos-aarch64
<blackriversoftwa> flokli: I should finally not have any tabs in my commit. I love neovim but trying to get it to pick up the `expandtab` setting has been annoying.
<blackriversoftwa> flokli: also I split the commits, put the actual fix first so it doesn't depend on the cleanup
<flokli> blackriversoftwa: okay cool, thanks! Will take a look later today :-)
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ilios has quit [Ping timeout: 260 seconds]
ilios has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 255 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
orivej has quit [Ping timeout: 268 seconds]