DietPi-Software | cargo fails on 32-bit RPi images with 64-bit kernel #6306
Labels
External bug 🐞
For bugs which are not caused by DietPi.
Raspberry Pi 4
Workaround available 🆗
Workaround is available/has been implemented, but a definite solution should be found when possible.
Milestone
Comments
|
ok some questions,
your kernel version
Your kernel is within 64bit mode, however you are running a 32bit image. Is this intentionally? Was this a fresh install of DietPi image? If yes, I would recommend to start with a ARMv8 image. |
I have done a reboot, might do another for good measure.
I think this was a weird workaround to a OOM reaper comment I found. I will roll that back to 32 bit thanks for bringing it to my attention, I think it was either faulty hdd or memory leak issue. #4622
No it isn't, but might try the above and see if there is any change. |
|
Ok so have removed the 64bit and ran a dietpi update and as there is no available update even after a couple reboots it is still stuck on
Any other way to force update the kernel? Should this resolve the issue do we think? |
|
No, the kernel update will not solve the problem, as these are two different issues. But you should be able to do the installation now. Ok let's clean Rust to get correct version and install one package in addition. |
|
However, let's also check why the kernel is stuck at a version of Buster while you're on Bullseye: cat /etc/apt/sources.list.d/raspi.list
apt policy raspberrypi-kernel |
Ok it looks like that file doesn't exist. What do I need to populate the raspi.list with? |
echo 'deb https://archive.raspberrypi.org/debian/ bullseye main' > /etc/apt/sources.list.d/raspi.list
apt update
apt full-upgrade |
shouldn't it be |
|
Right (fixed). |
Okay updating now then I will try the install afterwards, thank you for your assistance |
|
Still having the problem Logfile attached. Click to expand![FAILED] DietPi-Software | Unable to continue, DietPi-Software will now terminate. |
|
It tries to install cat /etc/os-release
cat /etc/apt/sources.list
dpkg --print-architecture |
|
cat /etc/os-release cat /etc/apt/sources.list dpkg --print-architecture |
|
Did you perform all steps to clean the install? #6306 (comment) AAAHHH and he is running RPi4. Means after kernel update to 6.1.21, the fancy change of RPI developer might have an influence as kernel is forced to 64bit mode by default now. Pls can you add following to the end of your |
|
I will do that now, rebooting and will come back with an update. Thanks |
Additional logs:Logfile attached. Click to expand!Still no luck |
|
Looks like I did another clean removal from the #6306 (comment) and it looks to be progressing, will keep an eye on it. |
|
Looks to of been resolved. Will mark this as fixed. Must've been the 64bit causing the issue. |
|
Let me reopen as I like to discuss some parts with @MichaIng Looks like the Rust installer was using incorrect architecture 64bit instead of 32bit. This as well can be caused by the new kernel feature RPI developer introduced, switching all 32bit RPI4 into 64bit mode by default. Something we need to check how to work around and how we could ensure correct architecture used, at least for Rust. |
|
That's fine, can you please let me know the login details? my ssh user and password isn't working and can't see any other info to use. |
Which login details you are looking for? For Home Assistance? |
Yes Home Assistant app |
|
First complete the initial install process as describe on our online docs https://dietpi.com/docs/software/home_automation/#home-assistant Once done, login to web interface and create your own individual admin account. There are no default credentials. |
I've ran the |
|
you are connecting via web interface or some app? |
|
You can check for available user And to reset login as root via SSH/CLI |
|
Thanks that got the username all sorted now. |
MichaIng
changed the title
|
I have similar issue when trying to update homeassistant on 32bit dietpi installation. Python: 3.10.11 |
|
pls open an own issue and fill the related bug report. As well, you would need to attach the entire output of HA update process (not just some lines) |
|
Re-reading this, I'm still unsure at which stage/which part exactly pulls the wrong architecture, hence unsure how to solve:
So if it is really I'll try to replicate the issue on another |
|
Yeah that's correct |
|
Strange: The rustup installer pulls 32-bit rustup default stable-armv7-unknown-linux-gnueabihfOr directly on install: curl -sSf https://sh.rustup.rs | sh -s -- --profile minimal --default-host armv7-unknown-linux-gnueabihfNot sure why but "syncing channel updates" currently takes ages. With this, hopefully also EDIT: And here is the related report on rustup GitHub repo already: rust-lang/rustup#3307 |
|
Dammit, this is the reason why it hangs: rust-lang/rust#60605 This repeats every 5 seconds. Could one of you test this on RPi 4 (with 32-bit userland + 64-bit kernel), the second command posted above? I'm currently testing it on Odroid N2. Hopefully this is a platform specific issue. EDIT: Workaround: export RUSTUP_USE_CURL=1EDIT2: Nope, the above solves the binary "download", but then cargo is "installed", the same happens: Next workaround: echo 'abi.cp15_barrier=2' > /etc/sysctl.d/98-dietpi-cp15_barrier.conf
sysctl -p /etc/sysctl.d/98-dietpi-cp15_barrier.confFound it here, which lists another potentially required setting: https://www.tal.org/tutorials/booting-64-bit-kernel-raspberry-pi-3 |
MichaIng
added a commit
that referenced
this issue
Apr 19, 2023
- DietPi-Software | Home Assistant/HTPC Manager/microblog-pub/Synapse: Resolved an issue where the install on RPi 4 with 32-bit image failed since rustup/cargo tried to compile for 64-bit. The issue occurred since the 64-bit kernel is used on RPi 4 by default since Linux 6.1, even if the OS/userland is 32-bit. Many thanks to @josh3003 for reporting this issue: #6306
|
PR up: #6325 Side note: Synapse does run well with this, we'll see whether the same is true for Home Assistant. |
MichaIng
added
Workaround available 🆗
MichaIng
added a commit
that referenced
this issue
Apr 19, 2023
- DietPi-Software | Home Assistant/HTPC Manager/microblog-pub/Synapse: Resolved an issue where the install on RPi 4 with 32-bit image failed since rustup/cargo tried to compile for 64-bit. The issue occurred since the 64-bit kernel is used on RPi 4 by default since Linux 6.1, even if the OS/userland is 32-bit. Many thanks to @josh3003 for reporting this issue: #6306
MichaIng
added a commit
that referenced
this issue
Apr 20, 2023
- DietPi-Software | Home Assistant/HTPC Manager/microblog-pub/Synapse: Resolved an issue where the install on RPi 4 with 32-bit image failed since rustup/cargo tried to compile for 64-bit. The issue occurred since the 64-bit kernel is used on RPi 4 by default since Linux 6.1, even if the OS/userland is 32-bit. Many thanks to @josh3003 for reporting this issue: #6306
This was referenced Apr 30, 2023
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Creating a bug report/issue
Required Information
DietPi version | G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=16
G_DIETPI_VERSION_RC=2
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
Distro version | bullseye 1
Kernel version |
Linux DietPi 5.10.103-v8+ #1529 SMP PREEMPT Tue Mar 8 12:26:46 GMT 2022 aarch64 GNU/LinuxSBC model | `RPI4)
Power supply used |Official rpi4 power supply )
SD card used | (EG: SanDisk high endurance)
Additional Information (if applicable)
Steps to reproduce
Expected behaviour
Actual behaviour
-errors out and cancels install
Failed to build bcrypt cryptography
ERROR: Could not build wheels for bcrypt, cryptography, which is required to install pyproject.toml-based projects
Extra details
`
Details:
Linux DietPi 5.10.103-v8+ #1529 SMP PREEMPT Tue Mar 8 12:26:46 GMT 2022 aarch64 GNU/Linuxsudo -u homeassistant dash -c . /home/homeassistant/pyenv-activate.sh pyenv install 3.10.11 pyenv local 3.10.11 pip3 install -U pip setuptools wheel [ -z '' ] || pip3 install exec pip3 install homeassistantSteps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs:
Logfile attached. Click to expand!
The text was updated successfully, but these errors were encountered: