david and I am spending too much time trying(

I know right!

david I get the impression that PCs are more robust with Bela perhaps?

Not that I am aware of...

david Sorry should have indicated that it simply worked at some point without recourse to this.

Is there still a program running on boot? If yes, I strongly recommend you follow the instructions above.

When you get the BELABOOT drive on your mac, can you open it and oepn the file "bela.version" with textedit? What is the version number reported in there?

        Today it is not working on either computer so I looked at those instructions - my Bela is incorporated in a case with a number of connectors. A number of pins are mentioned to be grounded but I do not see them listed on the pin diagram (https://learn.bela.io/pin-diagram/). Where is the BELABOOT drive?

          I have just tried with a brand new Bela board out of the box and it give the same error
          'This site can’t be reached
          bela.local’s server IP address could not be found.'

          Does this still suggest I need to go through the process above?

            david I have just tried with a brand new Bela board out of the box

            good try!

            david Does this still suggest I need to go through the process above?

            First we need to figure out whether you are running a version of the Bela image that is compatible with your very new OS. That information is in bela.version in BELABOOT.

            david Where is the BELABOOT drive?

            It should show up on your desktop or inside the /Volumes folder. You can see the content of bela.version after the board is connected to your computer by running:

            cat /Volumes/BELABOOT/bela.version

            in the terminal.

                  OK tried this and it returned:

                  dmh8@Davids-Air-10 ~ % cat /Volumes/BELABOOT/bela.version
                  BELA_IMAGE_VERSION=""
                  dmh8@Davids-Air-10 ~ %

                  Not sure what to make of that!

                  Right, that's an old version so I think you need a newer image than the one you currently have in order to support Monterey.

                  Just to confirm this is the case, could you please show the output of running ifconfig on your terminal?

                  This is what I got:

                  dmh8@Davids-Air-10 ~ %
                  dmh8@Davids-Air-10 ~ % ifconfig
                  lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
                  options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
                  inet 127.0.0.1 netmask 0xff000000
                  inet6 ::1 prefixlen 128
                  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
                  nd6 options=201<PERFORMNUD,DAD>
                  gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
                  stf0: flags=0<> mtu 1280
                  en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
                  options=400<CHANNEL_IO>
                  ether d0:81:7a:ac:9b:e0
                  inet6 fe80::18e9:45e4:1756:9f5b%en0 prefixlen 64 secured scopeid 0x4
                  inet 192.168.8.106 netmask 0xffffff00 broadcast 192.168.8.255
                  inet6 fda8:e544:6171:4300:1806:6fe3:d011:14e1 prefixlen 64 autoconf secured
                  nd6 options=201<PERFORMNUD,DAD>
                  media: autoselect
                  status: active
                  en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
                  options=460<TSO4,TSO6,CHANNEL_IO>
                  ether 82:18:47:e5:fa:00
                  media: autoselect <full-duplex>
                  status: inactive
                  bridge0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
                  options=63<RXCSUM,TXCSUM,TSO4,TSO6>
                  ether 82:18:47:e5:fa:00
                  Configuration:
                  id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
                  maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
                  root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
                  ipfilter disabled flags 0x0
                  member: en1 flags=3<LEARNING,DISCOVER>
                  ifmaxaddr 0 port 5 priority 0 path cost 0
                  media: <unknown type>
                  status: inactive
                  p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
                  options=400<CHANNEL_IO>
                  ether 02:81:7a:ac:9b:e0
                  media: autoselect
                  status: inactive
                  awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484
                  options=400<CHANNEL_IO>
                  ether ea:54:0d:0f:1b:34
                  inet6 fe80::e854:dff:fe0f:1b34%awdl0 prefixlen 64 scopeid 0x8
                  nd6 options=201<PERFORMNUD,DAD>
                  media: autoselect
                  status: active
                  llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
                  options=400<CHANNEL_IO>
                  ether ea:54:0d:0f:1b:34
                  inet6 fe80::e854:dff:fe0f:1b34%llw0 prefixlen 64 scopeid 0x9
                  nd6 options=201<PERFORMNUD,DAD>
                  media: autoselect
                  status: active
                  utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
                  inet6 fe80::f6c0:1246:8e03:2edd%utun0 prefixlen 64 scopeid 0xa
                  nd6 options=201<PERFORMNUD,DAD>
                  utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
                  inet6 fe80::10af:d46d:1a97:c522%utun1 prefixlen 64 scopeid 0xb
                  nd6 options=201<PERFORMNUD,DAD>
                  utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000
                  inet6 fe80::ce81:b1c:bd2c:69e%utun2 prefixlen 64 scopeid 0xc
                  nd6 options=201<PERFORMNUD,DAD>
                  utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1400
                  en9: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
                  options=404<VLAN_MTU,CHANNEL_IO>
                  ether be:1a:b7:96:bd:1c
                  nd6 options=201<PERFORMNUD,DAD>
                  media: autoselect (none)
                  status: inactive
                  dmh8@Davids-Air-10 ~ %

                  Let's get in touch via email and organise a zoom session like the one from 2 years ago so we can solve this more readily

                  OK that sounds good. Would anytime on Monday work?

                  2 years later

                  Hi again. My last login issue simply resolved itself(!) and I am up and running again. Question: I work in Pd and have 64 oscillators working OK but when I try 72 it makes odd sounds (not sinewaves) on its own. Could this be asking too much for real-time operation?

                    Sorry should have indicated this is on a Bela Beast.

                    david K but when I try 72 it makes odd sounds (not sinewaves) on its own. Could this be asking too much for real-time operation?

                    It could be, though it should be accompanied by dropout errors printed in the console. Try adding --high-performance-mode to the "User Command Line Arguments:" textbox in the settings tab to get some % of extra CPU. Note that when that's enabled - and exploited - you'll most likely need to press the button on the cape to stop the running program.

                      Thanks, I shall try this.