Problems installing on Pi B+

[HansR]

When removing mono and then reinstalling, you see all kinds of information.
Among that output you must see lines saying it is recompiling something.

[SamiS]

If you are really using an RPi 1 (i.s.o. e.g. an RPi 3B+) and you can't get CMX to run then your exercise may lead to the conclusion that CMX cannot run on that machine (or it may be broken?) and may need a newer one (e.g. an RPi 3B+) or simply do not use the image to install and try to install from scratch (OS + updates + mono + CMX).

Based on wikipedia, Pi1 and Pi zero use the same cpu, so there really should not be problems regarding that detail, because afaik there are several users of pi zero here. Of course there is a small possibility that the problem is related only to the newest builds and we haven’t figured that out yet… but not very likely imho.

[HansR]

Based on wikipedia, Pi1 and Pi zero use the same cpu, so there really should not be problems regarding that detail, because afaik there are several users of pi zero here. Of course there is a small possibility that the problem is related only to the newest builds and we haven’t figured that out yet… but not very likely imho.

OK.

[jonmiles]

When removing mono and then reinstalling, you see all kinds of information.
Among that output you must see lines saying it is recompiling something.

the output is as follows:

Code: Select all

cmx@raspberrypi:~ $ sudo apt install mono-complete
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
  mono-llvm-support
The following NEW packages will be installed:
  mono-complete
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 32.5 kB of archives.
After this operation, 62.5 kB of additional disk space will be used.
Get:1 https://download.mono-project.com/repo/debian stable-raspbianbuster/main armhf mono-complete armhf 6.12.0.182-0xamarin1+raspbian10b1 [32.5 kB]
Fetched 32.5 kB in 1s (39.3 kB/s)
Selecting previously unselected package mono-complete.
(Reading database ... 48075 files and directories currently installed.)
Preparing to unpack .../mono-complete_6.12.0.182-0xamarin1+raspbian10b1_armhf.deb ...
Unpacking mono-complete (6.12.0.182-0xamarin1+raspbian10b1) ...
Setting up mono-complete (6.12.0.182-0xamarin1+raspbian10b1) ...
cmx@raspberrypi:~ $

[SamiS]

That output suggests that it did not recompile anything, unless it is happening on the ”setting up” phase and not shown on screen. So this did not solve your crash? I wonder if the package manager does something stupid when it is reinstalling a package that is already cached on system. You could use

sudo apt purge mono-complete
sudo apt autoclean

before reinstalling and see if there is a difference.

[jonmiles]

thanks everyone for their help.

i tried the purge and auto clean, same result when reinstalling:

Code: Select all

cmx@raspberrypi:~ $ sudo apt install mono-complete
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
  mono-llvm-support
The following NEW packages will be installed:
  mono-complete
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 32.5 kB of archives.
After this operation, 62.5 kB of additional disk space will be used.
Get:1 https://download.mono-project.com/repo/debian stable-raspbianbuster/main armhf mono-complete armhf 6.12.0.182-0xamarin1+raspbian10b1 [32.5 kB]
Fetched 32.5 kB in 1s (43.4 kB/s)
Selecting previously unselected package mono-complete.
(Reading database ... 48075 files and directories currently installed.)
Preparing to unpack .../mono-complete_6.12.0.182-0xamarin1+raspbian10b1_armhf.deb ...
Unpacking mono-complete (6.12.0.182-0xamarin1+raspbian10b1) ...
Setting up mono-complete (6.12.0.182-0xamarin1+raspbian10b1) ...
cmx@raspberrypi:~ $

i tried to verify the version too:

Code: Select all

cmx@raspberrypi:~ $ mono --version
Mono JIT compiler version 6.12.0.182 (tarball Tue Jun 14 22:53:32 UTC 2022)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
        TLS:           __thread
        SIGSEGV:       normal
        Notifications: epoll
        Architecture:  armel,vfp+hard
        Disabled:      none
        Misc:          softdebug
        Interpreter:   yes
        LLVM:          yes(610)
        Suspend:       preemptive
        GC:            sgen (concurrent by default)
cmx@raspberrypi:~ $

if i try to run culumus i using:

Code: Select all

cd /opt/CumulusMX
sudo mono CumulusMX.exe

i get

Code: Select all

cmx@raspberrypi:~ $ cd /opt/CumulusMX
cmx@raspberrypi:/opt/CumulusMX $ sudo mono CumulusMX.exe

=================================================================
        Native Crash Reporting
=================================================================
Got a UNKNOWN while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

=================================================================
        Native stacktrace:
=================================================================
         (No frames)


=================================================================
        Telemetry Dumper:
=================================================================
Entering thread summarizer pause from 0x3069258432x
Finished thread summarizer pause from 0x3069258432x.
Failed to create breadcrumb file (null)/crash_hash_0x15b1c4952

Waiting for dumping threads to resume

=================================================================
        External Debugger Dump:
=================================================================
[New LWP 736]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
0xb6b85034 in __GI___wait4 (pid=738, stat_loc=0xbee05034, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
27      ../sysdeps/unix/sysv/linux/wait4.c: No such file or directory.
  Id   Target Id                                 Frame
* 1    Thread 0xb6f12ac0 (LWP 735) "mono"        0xb6b85034 in __GI___wait4 (pid=738, stat_loc=0xbee05034, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
  2    Thread 0xb5fff400 (LWP 736) "SGen worker" futex_wait_cancelable (private=0, expected=0, futex_word=0x40d290) at ../sysdeps/nptl/futex-internal.h:186

Thread 2 (Thread 0xb5fff400 (LWP 736) "SGen worker"):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x40d290) at ../sysdeps/nptl/futex-internal.h:186
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x0, cond=0x40d268) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x40d268, mutex=0x0) at pthread_cond_wait.c:638
#3  0x002f510c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb6f12ac0 (LWP 735) "mono"):
#0  0xb6b85034 in __GI___wait4 (pid=738, stat_loc=0xbee05034, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
#1  0x0009cfe8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Inferior 1 (process 735) detached]

=================================================================
        Basic Fault Address Reporting
=================================================================
Memory around native instruction pointer (0xb4513360):0xb4513350  00 00 00 ea d4 d7 66 00 00 00 9f e7 10 00 8d e5  ......f.........
0xb4513360  5b f0 7f f5 10 00 9d e5 00 10 80 e5 18 d0 8d e2  [...............
0xb4513370  00 81 bd e8 40 41 2d e9 1c d0 4d e2 00 60 a0 e1  ....@A-...M..`..
0xb4513380  10 10 8d e5 00 00 56 e3 0d 00 00 0b 08 10 86 e2  ......V.........

=================================================================
        Managed Stacktrace:
=================================================================
          at System.Exception:.cctor <0x00038>
          at System.Object:runtime_invoke_void <0x0007f>
          at <unknown> <0xffffffff>
          at System.SystemException:.ctor <0x0001b>
          at System.OutOfMemoryException:.ctor <0x0001b>
          at <Module>:runtime_invoke_void__this___object <0x0010b>
=================================================================
Aborted
cmx@raspberrypi:/opt/CumulusMX $

[freddie]

Is this a clue?

Code: Select all

System.OutOfMemoryException:.ctor

(from the log in the previous post - although I had seen it in an earlier post but forgot to comment!)

[SamiS]

Only idea I have left is that you could try running a little older build of cumulus. You don’t need a full reinstall, just unzip an older version over the current one.

[SamiS]

Is this a clue?

Code: Select all

System.OutOfMemoryException:.ctor

(from the log in the previous post - although I had seen it in an earlier post but forgot to comment!)

That could be a good catch. The earliest pi1:s have had only 256MB of memory, and probably that won’t be enough. If it is a 512MB model, I would chevk how much memory is allocated to gpu and tweak it as low as posdible. Also stopping unnecessary services could be worth a try.

[HansR]

Ah... out of memory. Could be yes.
It could also be useful to increase swap space to 2*<physical mem>

[jonmiles]

Thanks to everyone that has tried to help.

I tried changing the swap file, but still not difference.

I gave up and installed Raspberry PI OS Lite and then followed the instruction in the pinned post for installing cumulusmx and that has worked fine.

I suspect it is me using a very basic pi to try to run it and the image not playing nicely

[philpugh]

That would make sense as the 'desktop' version of 'BULLSEYE' would have many other processes running = which aren't needed for running CumulusMX.

Glad to see you got it running !

[SamiS]

That would make sense as the 'desktop' version of 'BULLSEYE' would have many other processes running = which aren't needed for running CumulusMX.

Glad to see you got it running !

Other explanation could also be that the image does have some other packages (besides mono), that would need reinstall to work properly on armv6.

I’m also glad that it is sorted now. Just have to remember this if some other user also hits the brick wall with the image on old pi or pi zero.