1. Forum
  2. fsxNet
  3. FSX MYS

  • Mystic for Raspberry Pi 4

    From roovis@21:4/165 to All on Monday, February 15, 2021 16:25:30
    I am trying to run Mystic for Raspberry Pi 4. I get a command not found when trying to run mystic (from the correct directory). mide and mplc run just
    fine, but mystic does not.

    I downloaded an older version of mystic, and it seems to work fine.

    Is there a problem with the latest build that doesn't run correctly on RPi 4? (I have 8 gig model)

    Anyone have any insight on this?

    -roovis

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: w0pr.win (21:4/165)
  • From Oli@21:3/102 to roovis on Tuesday, February 16, 2021 09:10:25
    roovis wrote (2021-02-15):

    I am trying to run Mystic for Raspberry Pi 4. I get a command not found when trying to run mystic (from the correct directory). mide and mplc run just fine, but mystic does not.

    I downloaded an older version of mystic, and it seems to work fine.

    Is there a problem with the latest build that doesn't run correctly on
    RPi 4? (I have 8 gig model)

    Anyone have any insight on this?

    Could you post what you see on the command line. What is the output if you type

    $ file mystic

    ?

    ---
    * Origin: . (21:3/102)
  • From bcw142@21:1/145 to Oli on Tuesday, February 16, 2021 09:25:15
    First question is the OS 32 bit or 64 bit? Is it Raspbian? Quick check for
    that is "cat /etc/issue" (checking issue message). Mine shows:
    Raspbian GNU/Linux 8 \n \l
    as an example of a 32 bit Raspbian on a Pi3. I don't see anything that shows 64bit, we used to assume 32bit which all mine are. The Pi4 should do either. Ubuntu would tell you with "uname -a", but not Raspbian from what I see. There isn't a release 64bit Mystic for Pi.

    --- Mystic BBS v1.12 A47 2021/02/01 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From roovis@21:4/165 to Oli on Tuesday, February 16, 2021 11:51:25
    mplc: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, for GNU/Linux 2.0.0, stripped

    mystic: ELF 32-bit LSB executable, ARM EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armf.so.3, for GNU/Linux 2.0.0, stripped

    Ran it against mplc which runs. Appears one is statically linked, and the
    other dynamically linked.

    Thanks for looking at this Oli. :)

    -roovis

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: w0pr.win (21:4/165)
  • From x1pepe@21:1/150 to Oli on Tuesday, February 16, 2021 22:02:54
    I ran my board on a Raspberry Pi 4 also.
    I have no problem.
    :(

    telnet sotanomsxbbs.org:23
    *The last Msx user in Ibiza*

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: Sotano Msx BBS (21:1/150)
  • From paulie420@21:2/150 to roovis on Tuesday, February 16, 2021 19:19:45
    I am trying to run Mystic for Raspberry Pi 4. I get a command not foun when trying to run mystic (from the correct directory). mide and mplc just fine, but mystic does not.

    I downloaded an older version of mystic, and it seems to work fine.

    Anyone have any insight on this?

    Don't take this the wrong way, but are you putting the ./ in front of your command? In Linux to run a command in the directory yer in you'd type:

    ./mystic -cfg or
    ./mis server or
    ./mystic -l

    ... etc etc.
    ??



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A47 2021/01/26 (Raspberry Pi/32)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From Oli@21:3/102 to roovis on Wednesday, February 17, 2021 08:56:47
    roovis wrote (2021-02-16):

    mplc: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, for GNU/Linux 2.0.0, stripped

    mystic: ELF 32-bit LSB executable, ARM EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armf.so.3, for GNU/Linux 2.0.0, stripped

    Ran it against mplc which runs. Appears one is statically linked, and the other dynamically linked.

    on my Raspbian 10 Buster I get this:

    pi@raspberrypi:~ $ ls -la /lib/ld-linux-armf.so.3
    ^^^^
    ls: cannot access '/lib/ld-linux-armf.so.3': No such file or directory

    pi@raspberrypi:~ $ ls -la /lib/ld-linux-armhf.so.3
    ^^^^
    lrwxrwxrwx 1 root root 30 Apr 3 2020 /lib/ld-linux-armhf.so.3 -> arm-linux-gnueabihf/ld-2.30.so


    try "ldd mystic", is /lib/ld-linux-armf.so.3 found?

    ---
    * Origin: . (21:3/102)
  • From roovis@21:4/165 to paulie420 on Wednesday, February 17, 2021 11:31:24
    Not taken the wrong way. :)

    Yes. I have no issues launching some of the binaries; some don't launch.

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: w0pr.win (21:4/165)
  • From roovis@21:4/165 to Oli on Wednesday, February 17, 2021 11:41:10
    ldd mystic returns

    not a dynamic exectutable

    (Spaces in front)

    The only ld- file in /lib/ is ld-linux-aarch64.so.1 -> aarch64-linux-gnu/ld-2.28.so

    I'm running Debian Buster 10, aarch64

    Kernel 5.9.0-0.bpo.5-arm64

    I'm using an image I got a few days ago from the official Raspberry Pi @ raspi.debian.net

    Yet, if I run it from Raspberry Pi OS (formerly Raspian); the same downloaded package from mystic works fine. So, I'm guessing something is missing from
    the "real" Debian build vs Raspberry Pi OS.

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: w0pr.win (21:4/165)