-
-
Save botter-nidnul/241b1d654d3e4f953d6714698f175c47 to your computer and use it in GitHub Desktop.
| ~ | |
| urbit 0.10.8 | |
| boot: home is /home/pi/sda2/0.10.8/fes | |
| loom: mapped 2048MB | |
| lite: arvo formula 50147a8a | |
| lite: core 590c9d56 | |
| lite: final state 590c9d56 | |
| boot: downloading pill https://bootstrap.urbit.org/urbit-v0.10.8.pill | |
| lmdb: failed to open event log: Cannot allocate memory | |
| disk: failed to initialize databaseaddress 0x40 out of loom! | |
| loom: [0x200000000 : 0x280000000) | |
| Assertion '0' failed in noun/events.c:129 | |
| bail: oops | |
| bailing out | |
| urbit: noun/manage.c:677: u3m_bail: Assertion `0' failed. | |
| Aborted |
They increased the mapsize to something AArch64 can't handle. Fixed here: botter-nidnul/urbit@507cff9#diff-2915e2cee5be906d4442b423ed4831a1
You can just use my aarch64 static binaries or build from my urbit-v0.10.8-aarch64 branch. I'll put in a pull request to urbit/urbit with the modifications soon.
tried w/ the static binaries and from the branch after removing and reinstalling nix, still out of loom...will keep messing around w/ it
are you sure you're running the static binaries? how are you invoking them? ./urbit or using urbit from your $PATH, which would be the broken version?
You didn't say what kind of rpi you have, which makes me wonder - maybe you just don't have enough ram? I'm not sure what that kind of error would look like. Maybe try creating a swap file?
and you're right, running make install on the urbit-v0.10.8-aarch64 branch produces a binary that generates this error...🤔
ok, thanks for bringing that up. fixed now. it was a single character flaw in the CPU detection method. botter-nidnul/urbit@f1951cb
booting up now...thx!
ran into this today trying to boot on a rpi... do you think this is unique to 0.10.8?