on 14.2.1 I am not at all sure those drivers would work ... However, on 0.3.8a the networking should work even without drivers. Does the network interface come up at all? Can you post here the result of the ifconfig command ran in your terminal about 1 minute after plugging in the board?

Thanks so much for your help. Phil

I don't know how to put this in a window or something. Here is the ifconfig....

galanter@galanter-mac-16 ~ % 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
en5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether ac:de:48:00:11:22
	inet6 fe80::aede:48ff:fe00:1122%en5 prefixlen 64 scopeid 0x4 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (100baseTX <full-duplex>)
	status: active
ap1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
	options=400<CHANNEL_IO>
	ether fa:ff:c2:50:90:23
	media: autoselect
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
	ether f8:ff:c2:50:90:23
	inet6 fe80::1876:33b7:a6ff:5cfb%en0 prefixlen 64 secured scopeid 0x6 
	inet 192.168.0.210 netmask 0xffffff00 broadcast 192.168.0.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
awdl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
	ether 5e:d3:99:2e:5f:f0
	inet6 fe80::5cd3:99ff:fe2e:5ff0%awdl0 prefixlen 64 scopeid 0x7 
	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 5e:d3:99:2e:5f:f0
	inet6 fe80::5cd3:99ff:fe2e:5ff0%llw0 prefixlen 64 scopeid 0x8 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether 82:64:cf:e5:40:00
	media: autoselect <full-duplex>
	status: inactive
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether 82:64:cf:e5:40:05
	media: autoselect <full-duplex>
	status: inactive
en4: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether 82:64:cf:e5:40:04
	media: autoselect <full-duplex>
	status: inactive
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=460<TSO4,TSO6,CHANNEL_IO>
	ether 82:64:cf:e5:40:01
	media: autoselect <full-duplex>
	status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=63<RXCSUM,TXCSUM,TSO4,TSO6>
	ether 82:64:cf:e5:40:01
	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 12 priority 0 path cost 0
	member: en2 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 9 priority 0 path cost 0
	member: en3 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 10 priority 0 path cost 0
	member: en4 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 11 priority 0 path cost 0
	nd6 options=201<PERFORMNUD,DAD>
	media: <unknown type>
	status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
	inet6 fe80::7f62:1545:d139:f235%utun0 prefixlen 64 scopeid 0xe 
	nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::d749:998d:2ffe:61fe%utun1 prefixlen 64 scopeid 0xf 
	nd6 options=201<PERFORMNUD,DAD>
utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
	inet6 fe80::82fd:3bed:b404:eeb5%utun2 prefixlen 64 scopeid 0x10 
	nd6 options=201<PERFORMNUD,DAD>
utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000
	inet6 fe80::ce81:b1c:bd2c:69e%utun3 prefixlen 64 scopeid 0x11 
	nd6 options=201<PERFORMNUD,DAD>
utun4: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::84f7:8377:3989:dd95%utun4 prefixlen 64 scopeid 0x12 
	nd6 options=201<PERFORMNUD,DAD>
utun5: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
	inet6 fe80::bffd:4c5:e37:d73a%utun5 prefixlen 64 scopeid 0x13 
	nd6 options=201<PERFORMNUD,DAD>
en7: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
	options=404<VLAN_MTU,CHANNEL_IO>
	ether be:1a:ff:8a:19:5c
	media: autoselect (none)
	status: inactive

    galanter en7: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
    options=404<VLAN_MTU,CHANNEL_IO>
    ether be:1a:ff:8a:19:5c
    media: autoselect (none)
    status: inactive

    ok, this is one of Bela's network interfaces. I think it's the one that's supported natively (not through the added driver). Unsure why status is inactive, maybe it was manually disabled in System Preferences -> Network ? Try running sudo ifconfig en7 up in the terminal, enter your password and that may fix it? See what happens after that if you re-run the ifconfig command after a few seconds.

        giuliomoro

        Hi. I tried this. After Salt/Bela booted up I did a "sudo ifconfig en7 up" but trying http://192.168.7.2 in the browser it still times out even though ifconfig yields in part...

        en7: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=404<VLAN_MTU,CHANNEL_IO>
        ether be:1a:ff:8a:19:5c
        media: autoselect (100baseTX <full-duplex>)
        status: active

        I might be away for a couple days, but will be following up for sure.

        thanks, Phil

        p.s. I also have a Bela Mini that behaves exactly the same way. I think it's an early unit because the file "bela version" says "BELA_IMAGE_VERSION="""

        ifconfig with the Bela Mini yields...

        en7: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
        options=404<VLAN_MTU,CHANNEL_IO>
        ether be:1a:ad:dd:72:aa
        media: autoselect (none)

          I would recommend updating the bela image on both. Version v0.3.8h works just fine for me without drivers on 14.3 . I thought v0.3.8a should already be supported (it was the first one to support built-in drives on Catalina and following), but at this point it's 4 years old and not worth wasting any more time on that or earlier versions considering v0.3.8h just works.

            giuliomoro

            OK I'll give that a try. I'll work on the Bela Mini first as it's a little more convenient. If I get that working I'll then try the Salt module.

            Thanks! Will report back here in a couple or four days.

              6 days later

              OK, still trying to get my Bela Mini working. I installed v0.3.8h and judging by the Blinky lights it looks like it's working. However, launching the IDE still results in server not responding.

              I note that the downloaded file is bela_image_v0.3.8h.img.xz but the Bela version file says BELA_IMAGE_VERSION="v0.3.8g". Perhaps that's just a typo at this point, but I thought I should mention it.

              I have a recent Mac mini. It dawns on me now that I should try it there and see if that makes a difference.

              Any other ideas?

                OK, on my Mac Mini both my Bela Mini and Salt module are able to launch the IDE. Here are the details about the Mac Mini that works:

                Mac mini / Apple M2 Pro / 32 GB / MacOS Sonoma Version 14.3.1 /

                Here is the laptop I want to use that doesn't work with either the Mac mini or Salt module:

                MacBook Pro / 2.3 GHz 8-Core Intel Core i9 / 32 GB / macOS Sonoma Version 14.2.1

                Next I'll update the MacBook MacOS to see if that shakes something loose.

                UPDATE: Updating the MacBook Pro to 14.4.1 made no apparent difference.

                To get various connectors I have to use this device. Could it be part of the problem?
                www.amazon.com/create-JCD382-Type-C-Multi-Dock-MacBook/dp/B07BJT7QZW

                The Bela Mini does seem to show up in the USB Bus. The following is from the System Information under Hardware/USB.

                USB 3.1 Bus:

                Host Controller Driver: AppleIntelCNLUSBXHCI
                PCI Device ID: 0xa36d
                PCI Revision ID: 0x0010
                PCI Vendor ID: 0x8086

                USB2.1 Hub:

                Product ID: 0x0610
                Vendor ID: 0x05e3 (Genesys Logic, Inc.)
                Version: 6.54
                Speed: Up to 480 Mb/s
                Manufacturer: GenesysLogic
                Location ID: 0x14300000 / 1
                Current Available (mA): 500
                Current Required (mA): 100
                Extra Operating Current (mA): 0

                USB 2.0 Hub:

                Product ID: 0x0801
                Vendor ID: 0x1a40 (TERMINUS TECHNOLOGY INC.)
                Version: 1.00
                Speed: Up to 480 Mb/s
                Location ID: 0x14340000 / 2
                Current Available (mA): 500
                Current Required (mA): 100
                Extra Operating Current (mA): 0

                BillBoard Device:

                Product ID: 0x2171
                Vendor ID: 0x0bda (Realtek Semiconductor Corp.)
                Version: 1.a1
                Serial Number: 123456789ABCDEFGH
                Speed: Up to 12 Mb/s
                Manufacturer: Realtek
                Location ID: 0x14342000 / 3
                Current Available (mA): 500
                Current Required (mA): 0
                Extra Operating Current (mA): 0

                Bela:

                Product ID: 0x0104
                Vendor ID: 0x1d6b (The Linux Foundation)
                Version: 1.02
                Serial Number: bela
                Speed: Up to 480 Mb/s
                Manufacturer: Augmented Instruments Ltd
                Location ID: 0x14330000 / 5
                Current Available (mA): 500
                Current Required (mA): 500
                Extra Operating Current (mA): 0
                Media:
                File-Stor Gadget:
                Capacity: 70.6 MB (70,631,936 bytes)
                Removable Media: Yes
                BSD Name: disk2
                Logical Unit: 0
                Partition Map Type: Unknown
                S.M.A.R.T. status: Verified
                USB Interface: 4

                  galanter BELA_IMAGE_VERSION="v0.3.8g". Perhaps that's just a typo

                  Yes, that image was done "manually" and that was left out. Even if it was g it would work the same.

                  galanter Version 14.2.1

                  I suspect/hope it's all down to this. I hope it's not that apple broke the drivers on intel devices on Sonoma. Or it could be a security/privacy permission issue...

                  galanter should have mentioned that on my Mac I installed the latest drivers linked on the

                  Also try removing these

                        OK, things are working now on my MacBook Pro as well as Mac mini.

                        (1) After looking up how to remove the drivers I discovered they weren't installed in the first place. Trying the installer again, it fails under Sonoma 14.4.1 (23E224). But it turns out it's not needed.

                        (2) I'm not sure how I missed it, but the answer was here:

                        https://github.com/BelaPlatform/Bela/wiki/Getting-started-with-Bela#troubleshooting---macos

                        Making the needed changes in the Preferences/Network control panel did the trick. And apparently I only needed to do this the one time. It seems to remember from one login to the next.

                        Thanks for your help, and I apologize for overlooking what I should have tried in the first place.

                          galanter 1) After looking up how to remove the drivers I discovered they weren't installed in the first place. Trying the installer again, it fails under Sonoma 14.4.1 (23E224). But it turns out it's not needed.

                          yup, that sounds reasonable.

                          That's weird. It shouldn't be necessary because I don't need it in my case. FWIW, I think the command line equivalent of that would be ifconfig en7 up 192.168.7.1, but that wouldn't persist a reconnect.