ARM64 Raspberry Pi with Debian - Illegal instruction (core dumped) #2858
Comments
|
Are you running on armv8 or armv7 ? If the latter, use the armv7 binary. |
|
It's raspberry Pi 3 model B, and it is running 64bit kernel (aarch64). |
|
raspberry Pi 3 can't run our armv8 binaries since we use AES instructions and the pi 3 CPU doesn't implement them. Use the ARMv7 binary. |
|
+invalid |
|
@hyc I get this error when I run armv7 version binary: It will be great to add software AES support on |
|
You can use the |
|
Will RPi 3 CPU run AES code with aarch64 Linux kernel? Is it presented in hardware? http://www.tal.org/tutorials/raspberry-pi3-build-64-bit-kernel |
|
@Zenitur no. I stated that explicitly already in #2858 (comment) Pi 3 is worthless for Monero. |
|
Pi2 runs it fine. Arm 64 is not the correct build. Need arch 7
…On Dec 12, 2017 5:19 PM, "hyc" ***@***.***> wrote:
@Zenitur <https://github.com/zenitur> no. I stated that explicitly
already in #2858 (comment)
<#2858 (comment)>
Pi 3 is worthless for Monero.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2858 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AgV3MzgQf6kHoG3bJgQcoQtTBUe8HblVks5s_xgRgaJpZM4QpnpE>
.
|
This is 100% false information. I ran a Monero full node on my Pi 3b+ very successfully until yas broke it in v16. Worthless for mining, sure. But as a full node contributing to the network it is fantastic, 15w max power draw means I can keep it on 24/7 for minimal expense and contribute to the P2P network, and importantly, it serves me as a trusted node for my Cake wallet. So what you are saying is 100% incorrect and I suspect it's dunces like yourself spouting this misinformation that has steered the project away from having proper Pi support. |
|
And I was the one who ported the Monero code base to ARM and raspberry pi 1 in the first place. Of course it runs, but Pi is still worthless junk. Get an Odroid or a Pine64. |
This is a biased opinion. As I said it worked wonderfully on my 3b+. The fact that you don't like the hardware is irrelevant. Having a quick look at Pine64 I'm not seeing anything matching my Pi4 8GB |
|
No Pi processor has hardware AES support - that's a simple fact. Every Pi device up to Model 3 ships with a 32bit OS, that's also a fact. Every Pi up to Model 3 has a total I/O bandwidth of only 20MB/s, again simple fact. These facts together mean that every Pi will use more electricity than any other comparable ARM64 device and operate more slowly. Too slowly to be useful as network activity grows. While we measure other CPUs in Hashes per second, on Pis we measure in seconds per hash. |
And yet when I'm looking at the PineAP I am seeing it is using the same Arm-cortex-v72 CPU as the Pi 4 (or at least the ROCKPro64 which I'm guessing is the flagship?). What do you need AES-NI for when you are not mining anyway? You will never mine successfully on a single board so the comparison is absolutely pointless. |
|
The crypto portion is optional, and the Pi 4 does not have that optional extension in the CPU. The AES instructions are still used for block verification. You can do a custom build with AES instruction disabled. |
|
You're clearly too stupid to be having this conversation. AES-NI is an optional part of the Cortex instruction set. Raspberry/Broadcom cheaped out and didn't license it for their chips. Every other ARM64 vendor supports it though. Raspberry/Broadcom is literally the bottom of the barrel implementation of Cortex. And you still need AES for validating incoming blocks. Try syncing the blockchain from scratch on a Pi. I finally gave up on my Pi when I calculated it would never catch up to the network. Try catching up after being offline for only 1 day. And - on other machines like RockPro64, you can mine, and the power efficiency is better than Intel chips so no, the comparison is not pointless. |
LOL
Demonstrating that you have no clue what you are talking about. My Pi 3b+ as I mentioned, worked as a full node completely fine without AES-NI.
I did exactly this on my pi 3b+. Just because you are too useless to make it work doesn't mean it doesn't work for others. And I could have my node down for a month and bring it up and it would sync, take some time sure but that's fine, I don't expect a Pi to be a trail blazer, long as it works, which it does.
You can mine on the Pi too..... but doesn't mean you're going to, it's pointless you'd be lucky to make 10 cents. |
Thanks yes that's what I'm trying now. Is the compiler smart enough to detect no AES-NI and disable it automatically or do I have to set flags? |
Haha you're funny. I'm the guy who made it work on ARM64 in the first place. 69b5918#diff-1791ca6db56ff6236c17c6b8c2d6bc1516adbf806345d2e0ffc3b3a1b60e8287 Since you've never contributed any code here, you're in no position to be calling actual developers useless. |
Yet you could not get it to work properly for you, where others have had great success. Instead you gave up and called the Pi 3 worthless.
I disagree. Contributing code doesn't grant you immunity from uselessness. |
|
No, the code works fine. I wrote support for ARM64 both with and without AES-NI, so of course it works. But Pis are still too slow to be useful, and other systems are better, for about the same price. The only reason you're able to use it is because I wrote the code that supports it. Both with and without crypto extensions I've tested on Allwinner, Amlogic, HiSilicon, Mediatek, Qualcomm, Rockchip , (and of course Broadcom) - basically every ARM64 maker that consumers can get their hands on. All of them perform better than Broadcom, all of them perform better than Pis, and they're all readily available. You're just a non-contributing complainer. |
They are useful as a full node. And also these words are useless for anyone who receives a Pi for xmas or already has one. It's true that it takes some time to sync, but once it syncs it's fine. I can run an XMR full node and PMS from the one Pi Simultaneously (without video transcoding) no problems at all. Or at least I could until v16, which is when I'm guessing AES-NI started being forced on the binaries
Disagree, I think that wanting to run a full node 24/7 and support the network is contributing.
Which for some reason isn't compiled and supplied to the community as a bin. Probably because of your rubbish misconceptions that the Pi is useless, as I've said. |
|
For anyone coming across this in the future wanting to run a full node on their Pi, follow the install instructions on the monero repo however before running your make command, edit the If you have a Pi 4b 8GB I recommend running |
No idea how to fix this. Using the binary from https://downloads.getmonero.org/cli/linuxarm8.
The text was updated successfully, but these errors were encountered: