• Registered: 2022-03-29
  • Posts: 2

Topic: [Solved] RME AVB Controller failed to start

Hi --

First of all, I would like to thank everyone and especially RME for their great support -- truly amazing!

I ran into an issue today, just after a perfect run -- the RME AVB Controller failed to start. I have tried:

(1) Updated the firmware to the latest of my device, RME Digiface AVB
(2) Reinstalled the driver
(3) Tried to start the controller from the terminal, and here are what I've found:

✖  /Applications/RME\ AVB\ Controller.app/Contents/MacOS/RME\ AVB\ Controller
2022-03-29 16:39:22.420 RME AVB Controller[905:8427] Warning: Column selection is not supported in view-based table and outline views (<NSTableView: 0x7f78d4851c00>).
Found Digiface AVB (vendor = 10809, product = 16369)
Digiface AVB = feth10002
Unable to open the adapter. feth10002 is not supported by pcap.
kein Digiface gefunden
!!!Network open!!!

and it exited..

The system is macOS 12.3.

I have managed to bypass this issue by promoting the privilege using sudo, however I do not feel this is the right way. Could anyone help me with this issue? Thank you so much in advance!!

Best Regard.

2 Reply by MC

  • MC
  • MC
  • Administrator
  • Offline
  • From: Germany/Thailand
  • Registered: 2007-04-06
  • Posts: 25,582

Re: [Solved] RME AVB Controller failed to start

Which netifc package did you install? The latest one includes a readme file '7'.

Which driver version and firmware version are used ('latest' is not a valid information)? Which AVB Controller version?

Regards
Matthias Carstens
RME

MC's Website

3 Reply by zhengnanlee (edited by zhengnanlee 2022-03-30 19:24:07)

  • Registered: 2022-03-29
  • Posts: 2

Re: [Solved] RME AVB Controller failed to start

Sorry, here are the versions:

* netifc: released 2021-05-19, and the readme file contains a '7'. MD5 of the pkg: 613f0818adb80ddb8e134b533c59b617
* Driver version v3.27
* Firmware: v244
* AVB Controller version: 0.9553

I found the answer to my question... the AVB Controller is not up-to-date... the problem is now resolved by updating the AVB Controller to 0.9566.

Sorry!