nachoparker
commented
5 years ago Hi,
You are certainly right, armv6 doesn't work anymore since the introduction of PHP7.2.
This is a duplicate of https://github.com/nextcloud/nextcloudpi/issues/722 and https://github.com/nextcloud/nextcloudpi/issues/667
As stated before, we chose PHP7.2 over armv6 support, because Raspbian messes up with what is considered armhf and because it is not worth it to stay in 7.0 just to support slow devices where NC doesn't work well anyway.
In any case, if there were somebody willing to help support this, the code modifications would be minimal, just change the PHPVER variable during build to 7.0, if armv6 Raspbian is detected.
This would have to be taken into account in possible update scripts.
Regarding Wifi, last time I tested this it was working fine in a RPi3, if this is any different in a Zero W PRs are accepted.
Cheers!
I have tried to tinker with nextcloudpi on a Raspberry Pi Zero W, without successs. I did download the image from https://ownyourbits.com/downloads/NextCloudPi_RPi_11-22-18/ flashed that onto an SD card and then copied 2 required files
ssh(to enable ssh on the Zero) andwpa_supplicant.conf(to link the Zero into my network) onto it.Upon starting the Zero with the thus prepared SD card, I can ssh into it alright. However, accessing http://nextcloudpi via browser results in an error ERR_CONNECTION_REFUSED. I figured that I had to enable the WebUI first via
ncp-configon the Zero. Afterwards, http://nextcloudpi brought up a login prompt that I filled with the standard credentials (ncp, ownyourbits). On submit, the browser presents the following message:Several hours, attempts and SD card rewrites later, I came up with the following possible explanation: Apache was complaining that one of its mods wasn't operating and it needed a restart. Doing so resulted in an error blaming php-fpm7.2 for not being started.
systemctl status php7.2-fpm.serviceproduced the following output:Trying to run the offending command manually resulted in:
pi@nextcloudpi:~ $ sudo /usr/sbin/php-fpm7.2 --nodaemonize --fpm-config /etc/php/7.2/fpm/php-fpm.confI then checked the binary for its target architecture:
pi@nextcloudpi:~ $ readelf -A /usr/sbin/php-fpm7.2 | egrep -i 'cpu_name|cpu_arch'This seems to indicate that php-fpm7.2 was compiled for ARMv7-CPUs, whereas my Zero -of course- is utilizing an ARMv6-CPU:
pi@nextcloudpi:~ $ egrep -i 'model|hardware' /proc/cpuinfoSince ARMv6 was the CPU for all the 1st generation Raspberry Pis, this means users of the following models should run into similar problems:
To my awareness, they are all based on a BCM2835, just like the Zero W I am running.
During my extensive trials, I observed the dreaded 'Illegal instruction' quite a few times (I think it was when trying to execute nc-init via
ncp-config). I have not investigated this further, but it might very well be that other binaries are also not ARMv6-friendly, and this might be related to other issues (e.g. https://help.nextcloud.com/t/nextcloudpi-on-raspberry-pi-just-isnt-working/40137/8 ) as well.On a side note:
ncp-config's wifi setup is not operational on a Zero W that is connected by WLAN only. After enabling wifi, I presume it is trying to list all available WLAN-SSIDs for the user to choose from, but unfortunately disconnects from WLAN first. Since the existing WLAN connection was servicing the remote ssh session, the user never gets to see the list. What's worse is that even a hard restart doesn't allow the user to re-login, since both ssh and wpa_supplicant.conf have been removed. So its pulling that sd card off the Zero, writing the two files back via my workstation, then back into the Zero... This behaviour would affect all systems that are connected by WLAN only, not just the Zero W.