Raspberry Pi bookworm install errors

[oldeflyer]

Hello,

System: Raspberry Pi 4 running 32 bit Bookworm

Downloaded file: nomachine_8.10.1_1_arm64.deb

Using dpgk per the installation, the install threw several errors:

Selecting previously unselected package nomachine:arm64.
(Reading database … 198926 files and directories currently installed.)
Preparing to unpack …/nomachine_8.10.1_1_arm64.deb …
Unpacking nomachine:arm64 (8.10.1-1) …
Setting up nomachine:arm64 (8.10.1-1) …
NX> 700 Starting installation at: Thu, 28 Dec 2023 10:18:33.
NX> 700 Using installation profile: Debian.
NX> 700 Installation log is: /usr/NX/var/log/nxinstall.log.
NX> 700 Installing nxrunner version: 8.10.1.
NX> 700 Installing nxplayer version: 8.10.1.
NX> 700 Installing nxnode version: 8.10.1.
NX> 700 ERROR: Error in CUDA initialization..
NX> 700 Node install completed with warnings.
NX> 700 Please review the install log for details.
NX> 700 Installing nxserver version: 8.10.1.
NX> 700 ERROR: Cannot validate license file.
NX> 700 Cannot add installation data to database.
NX> 700 Failed to run ‘/usr/NX/bin/nxkeygen’.
/usr/bin/sed: can’t read /var/NX/nx/.ssh/authorized_keys: No such file or directory
/usr/bin/sed: can’t read /var/NX/nx/.ssh/authorized_keys: No such file or directory
/usr/bin/sed: can’t read /var/NX/nx/.ssh/authorized_keys2: No such file or directory
/usr/bin/sed: can’t read /var/NX/nx/.ssh/authorized_keys2: No such file or directory
NX> 700 Cannot set egl capture..
NX> 700 Server install completed with warnings.
NX> 700 Please review the install log for details.
NX> 700 Installation completed with errors at: Thu, 28 Dec 2023 10:19:04.
NX> 700 NoMachine was configured to run the following services:
NX> 700 NX service on port: 4000

sudo ss -tunl command does not show port 4000 listening, the Windows client cannot connect.  The Windows client is being used successfully connect to a Linux Mint desktop.

Any fixes appreciated.

Wayne

[Britgirl]

Hi, what you can try is installing the armhf packages rather than the aarch64 specific ones. Try the packages here and let us know: https://downloads.nomachine.com/download/?id=106&distro=Raspberry&hw=Pi4

[oldeflyer]

Thanks for the reply and link, Britgirl

Not to be a stickler, but that link leads to a download that is not on the NoMachine downloads page for RPi.

Additionally it is marked Buster and that was two RPi OS versions ago.

How did you come up with that link?

[Britgirl]

You are right that Buster is outdated, and this information will be updated. We are currently making changes to the website in general, including the download pages which should facilitate finding the right packages. These modifications to the website are planned for the release of v9 of the software, but in the meantime the current website can of course be updated with more recent OS information.

How did you come up with that link?

The link is available from the main page for Raspberry (not sure why you were not able to find it).

Click NoMachine for Raspberry in the menu which takes you here: https://downloads.nomachine.com/linux/?id=29&distro=Raspberry

Then select “NoMachine for Raspberry ARMv7 DEB”, under Raspberry Pi 4. And it takes you to https://downloads.nomachine.com/download/?id=106&distro=Raspberry&hw=Pi4.

NoMachine should block the installation if you are installing an incompatible package (in your case package for 64-bit kernel being installed on 32-bit system), so we are checking what can be improved on our side.

[oldeflyer]

Britgirl,

In spite of misgivings about the download, I installed the recommended package.  It installed with errors.

I have attached the install log.

[Britgirl]

Some feedback about this – in checking the latest image of Raspberry Pi OSarmv7 (Bookworm), there is a 64-bit kernel. This is why uname -m command shows aarch64. However, the libraries in Bookwork are for armv7 and that’s why you need to install a package for armv7. So the folks at Raspberry will probably need to fix this in a later update.

On normal systems or older Raspberry devices we block the installation, like here:

sudo dpkg -i /tmp/nomachine_8.10.1_1_arm64.deb
dpkg: error processing archive /tmp/nomachine_8.10.1_1_arm64.deb (–install):
package architecture (arm64) does not match system (armhf)
Errors were encountered while processing: /tmp/nomachine_8.10.1_1_arm64.deb

If you are running Wayland, please use X.org instead. There is a Trouble Report already open which you can track using this link:

Wayland doesn’t work on Raspberry boards
https://kb.nomachine.com/TR10U11031

[Author]

Posts