- This topic has 5 replies, 2 voices, and was last updated 1 week, 5 days ago by
.
-
Posts
-
Hi all,
Struggling to run NoMachine on an old laptop (Dell XPS m1330) running amd64 Ubuntu MATE V22. Crashes following any attempt to input data when defining a new connection (hence I never get to the stage of opening a connection). I regularly run NX on more modern hardware. Have tried disabling hardware graphics acceleration as suggested for similar problems but no effect. After crash system reports a ‘system error’ but I haven’t analysed that.
Thanks for any help, Geof
Can you send us the logs from that Ubuntu machine? Compress the archive of the .nx directory in the user’s home and send to us at forum[at]nomachine[dot]com.
Many thanks. A few points: 1. While doing this the machine hung during boot, I had to use the ‘recovery’ startup to get it going. This might suggest the machine has a hardware fault, so if your diagnostics point that way I won’t be upset! 2. I only need the client (nx player). It is not clear to me whether I should have the server running at the same time, or not (I have tried both) 3.The ‘nomachine service’ gui seems to work fine. Regards, Geof. PS I am impressed by this service!
Follow up: I had a look at the syslogs and found the attached in kern.log. I had tried the NoMachine Gui at 21:00. Does this help?
Being rather impatient I reverted to a 32bit version of Ubuntu and installed the 32bit version of NoMachine (i386). It works! So my conclusion is that while you may be able to run 64bit Ubuntu on a 32bit machine, you won’t be able to run 64bit NoMachine.
This didn’t take very long so if you want me to do some tests I don’t mind.
Regards, Geof
Ah so Dell m1330 has a 32-bit architecture! The general rule is that when HW architecture is 32-bit, you need to install NoMachine 32-bit packages. You cannot install 64-bit packages (including NoMachine) on 32-bit architecture.
Instead, NoMachine 32-bit packages can be installed on a 64-bit OS or 64-bit architecture provided you have the necessary 32-bit compatibility layer in place.
Good to know it’s now working 🙂
You must be logged in to reply to this topic. Please login here.