<andi->
Any modern notebook has probably a better power efficiency :/
<andi->
(not criticism just saying) :)
<DigitalKiwi>
that's what it's always been?
<andi->
I think they started out with 1.5A
<andi->
and 2A if you have power hungry external devices
<DigitalKiwi>
the 3 at least was that
<gchristensen>
(pasted because their website is fairly down right now)
<DigitalKiwi>
do you know the price of the different ram
<sphalerite>
$35 for 1, $45 for 2, $55 for 4
samrose has joined #nixos-aarch64
<DigitalKiwi>
huh that's not bad
<sphalerite>
what I find interesting is that it has PCIe, but apparently that's how the USB3 controller is connected and I'm not sure it can be repurposed?
<tilpner>
I would buy one if I could use it as a backup target :/
<tilpner>
Hmm, I guess two USB3 external drives might be Fine™?
<tilpner>
Not sure about power delivery, but they apparently improved that
<DigitalKiwi>
i always use a powered usb hub for HDDs
<tilpner>
That probably depends a lot on the hub, but those supposedly cause corruption
kvaster_ has quit [Ping timeout: 246 seconds]
<DigitalKiwi>
never heard of that and never had a problem
<DigitalKiwi>
maybe i'm lucky or have good hubs *shrug*
<DigitalKiwi>
i've had more problems with computer not giving enough power without a hub
<thefloweringash>
Is there a hydra jobset for release-19.03 that builds aarch64 packages? I've been using 19.03 fine but just noticed auto upgrade failed due to test timeouts and wondered why it wasn't cached, and couldn't find any matching build in hydra.
jtojnar has joined #nixos-aarch64
adisbladis1 is now known as adisbladis
<samueldr>
thefloweringash: indeed, a mistake, I was made aware of this a couple weeks ago and never circled back re-asking what we should be doing
<samueldr>
I thought that limited supported would build everything, but turns out it doesn't
<samueldr>
(I thought hydra built everything for i686)
<samueldr>
about rpi4: wondering if it's USB PD, didn't find any confirmation yet
<samueldr>
and if it's PD, if it will help with providing more power to the USB devices
<samueldr>
though, considering it's supposed to be working with a non-PD power supply, with a mini to type-c converter, it means that it won't _require_ PD
<samueldr>
hm, Thra11 left; I think their issue could have been that the storage has a block size different than 512, which I couldn't test against :/
<samueldr>
I feel the 1/2/4 GB split could end up hurting some adopters who only shell out for 1, but (all-in-on) "product" distros being developed on the more capcious ones
<samueldr>
>> The Pi4B requires a good quality USB-C power supply capable of delivering 5V at 3A. If attached downstream USB devices consume less than 500mA, a 5V, 2.5A supply may be used.
<samueldr>
sounds not-PD
<timokau[m]>
Does anyone know if it'll use a mainline kernel?
<andi->
I hope so. They have managed to do that in the past.
orivej has quit [Ping timeout: 272 seconds]
<samueldr>
I don't think they ever did?
<samueldr>
and the working of the release makes me think they won't
<samueldr>
this smells of "latest LTS whenever we started working on our things"
<samueldr>
when combined with "many drivers upstreamed"
<andi->
indeed no line for bcm6611 in master of the kernel :/
<andi->
*bcm2711
ryantrinkle has joined #nixos-aarch64
<timokau[m]>
:( Why don't people just use mainline? Wouldn't it be easier for them? Especially for someone with as much community as raspberry pi
<samueldr>
it might not make it easier for them, since kernel subsystems change along the way
<samueldr>
and for distros using the rpi foundation fork, it makes it less of a moving target
<samueldr>
kind of like an LTS kernel
kvaster_ has joined #nixos-aarch64
<timokau[m]>
Couldn't they just use an actual LTS kernel for that?
<samueldr>
I think they did, but LTS kernels I guess won't accept "new things" in
<timokau[m]>
Hm, makes some amount of sense
<timokau[m]>
Still annoying
<samueldr>
yes
<gchristensen>
LTS kernels accept whatever their silly machine learning backport bot decides to backport
<samueldr>
(yeah :/)
<gchristensen>
I'm honestly not sure what LTS means to the kernel any more
<samueldr>
though, I *hope* that their new fork for the rpi4 uses the same interfaces are upstream does, making it easier for upstream
ryantrinkle has quit [Ping timeout: 272 seconds]
<samueldr>
I'm also concerned they still use their bizarro boot chain, that relies on the sd card, instead of relying on another device internal to the pi
<samueldr>
though I guess that like the 3B+, it will ship with usb boot unlocked, so less of an issue
<samueldr>
it's just that I feel it would have been better to have some way to store that on an internal storage to have either u-boot or tianocore onboard, rather than on the booting media
<samueldr>
it's still a kind of lock-in to their boot chain, supporting it means a bit more work than booting more standard EFI images
<samueldr>
that would have been great if u-boot was flashable to an internal storage, so it could have supported some protocol to push images
<samueldr>
yet as in the lower levels like the rpi3, AFAICT
<samueldr>
but AFAICT no onboard dedicated storage for firmwarey bits
<samueldr>
no uefi boot
<samueldr>
and obviously they released the dang thing while I was sleeping
<samueldr>
so couldn't order one
<samueldr>
as always, they sell out so quickly :/
<samueldr>
if anyone has some time to look at #63147, pretty non-invasive, adding kernel modules to the initrd is safe, they're only availableKernelModules, and the kernel option AFAICT is safe too
<samueldr>
only I don't want to merge it without someone else taking a look, if possible :)
<gchristensen>
lgtm samueldr
<samueldr>
thanks
<samueldr>
I'll try and remember to look at the next sd-image from nixos-unstable
<gchristensen>
<3
<samueldr>
two big changes, with fat-free and graphical changes; though hopefully this means there will be less confusion with the initial stage-1 steps taking some time
zupo has joined #nixos-aarch64
orivej has joined #nixos-aarch64
kvaster_ has quit [Ping timeout: 245 seconds]
zupo has quit [Ping timeout: 248 seconds]
zupo has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 252 seconds]
kvaster_ has joined #nixos-aarch64
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]