orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 268 seconds]
jackdk has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 245 seconds]
ryantrinkle has quit [Ping timeout: 250 seconds]
zupo has joined #nixos-aarch64
exarkun has joined #nixos-aarch64
exarkun is now known as Guest58681
Guest58681 is now known as exarkun
kai_w 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
ryantrinkle has joined #nixos-aarch64
st4ll1 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mthst has quit [Quit: the bouncer died]
mthst has joined #nixos-aarch64
orivej has quit [Ping timeout: 245 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
<
mthst>
no idea what the problem was, but it seems to work now :D with the same setup
<
sphalerite>
mthst: probably not enough power
<
samueldr>
looking at the log, might be on the cusp of receiving enough power :/
<
mthst>
how do you tell?
<
sphalerite>
raspberry pis tend to be powered by phone chargers, which don't usually deliver quite enough power for HDDs
<
sphalerite>
and the device disappearing and reappearing is quite a typical symptom of not enough power
<
sphalerite>
I think
<
samueldr>
yeah, the way it times out if it is "SABRENT"
<
samueldr>
that's what I would intuit from the log
<
mthst>
sphalerite: but there is a
_powered_ usb hub in between
<
samueldr>
yeah, that's the part that annoys me in the intuition
<
samueldr>
though some cheap (not saying yours is) powered usb hubs are powered mostly for show :/
<
mthst>
that may be it actually
<
samueldr>
it's been invaluable in figuring out things for the raspberry pi
<
samueldr>
mostly vetting chargers
<
mthst>
the usb hub's spec says it provides up to 900mAh and the HDD says it needs 800mAh
<
samueldr>
:/ 900mAh for a "powered" usb hub sounds weird to me
<
samueldr>
though yeah, those numbers could explain how is looks like it's on the cusp
<
samueldr>
starting the disk in some cases is what "kills" the thing
<
samueldr>
from stop to spinning, it needs more powere than sustained draw
<
samueldr>
800mAh could be the sustained draw
<
samueldr>
I know the one drive I use is also on the cusp and sometimes doesn't start
<
samueldr>
(directly to the pi though)
<
samueldr>
but once started it's smooth sailing
<
samueldr>
all that because of physics!
<
mthst>
ugh, maybe i can still return it
<
samueldr>
do note that I'm working on a big pile of assumptions :)
<
mthst>
i need one of those usb power testers
<
samueldr>
at least two of different models to check if the numbers are around the same ballpar :) (or a known good fancy brand$$)
mthst has quit [Quit: the bouncer died]
mthst has joined #nixos-aarch64
orivej has joined #nixos-aarch64
<
mthst>
can i make my pi boot from the hdd? is there a guide for provisioning on the pi?
<
sphalerite>
depends on the model
<
samueldr>
though most of the time HDDs will respond too slow to boot entirely from HDD
<
samueldr>
3B+ and up, (so, maybe 3A+ if it even exists) will boot from usb devices natively
<
samueldr>
3B (and 3A) will need to do a irreversible change by burning an efuse
<
samueldr>
but, if you're willing to have a mostly read-only sd card, you can instead install the bootloader there
<
samueldr>
it should allow more flexibility, like more leniency in startup time for the attached usb hard drive
<
samueldr>
two main options, (1) installing u-boot to it, (2) installing tianocore to it
<
samueldr>
(3) untested, no guide, but I guess a kexec solution could also be made
<
samueldr>
oh, looks like they pushed binary artifacts, that's good
<
samueldr>
pbatard was working on getting it upstreamed
<
samueldr>
I believe it was, though not entirely sure what this entails
<
samueldr>
when using tianocore, the raspberry pi will act like a mostly standard UEFI boot flow
<
mthst>
samueldr: awesome.
<
samueldr>
so the installation instructions are mostly similar to the x86_64 one, using the aarch64 iso image
<
samueldr>
it will
_not_ boot sd_image
<
samueldr>
(though, could with some work I think)
<
mthst>
what about nixos-install?
<
samueldr>
that's what I did, use nixos-install
<
samueldr>
that's what the future of ARM boards will probably be
<
samueldr>
that's what the present of ARM boards can be
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<
samueldr>
:/ can't say, it's been a while since I did it, for me it just worked
<
samueldr>
to test it I used a standard usb drive and flashed our sd_image to it, the raspberry pi picked it up just like it would an SD card
<
samueldr>
(do note that not
_all_ usb drives will be able too boot, hard to know beforehand)
<
clever>
mthst: is the first fat32 partition mounted at /boot/ ?
zupo has joined #nixos-aarch64
<
mthst>
clever: it's not mounted at all. is that a problem? i also copied config.txt to "/" to be certain
<
clever>
mthst: the rpi firmware only looks for config.txt on the fat32 partition, likely the 1st one
<
clever>
so you need to mount tht somewhere, and put the config.txt on it (or update the existing one)
<
mthst>
clever: ah thanks
mthst has quit [Quit: the bouncer died]
mthst has joined #nixos-aarch64
<
mthst>
clever: it worked!
ryantrinkle has quit [Ping timeout: 246 seconds]
ryantrinkle has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
jtojnar has joined #nixos-aarch64
st4ll1 has joined #nixos-aarch64
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-aarch64
<
gchristensen>
nice!
lopsided98_ has joined #nixos-aarch64
lopsided98 has quit [Ping timeout: 252 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jackdk has joined #nixos-aarch64