No clock available

[prldm]

Hi,

I’m trying to get Inferno running on Fedora 43, but I keep hitting no clock available, no matter what I try. Statime is running in PTPv2 mode, so I assume Inferno should be able to provide the clock / act as master, right? At the moment the only Dante device on the network is DVS. I know I can’t really route audio without an AES67-capable device, but I expected Inferno to at least show up in Dante Controller.

Am I missing something here?

log.txt

[MeestorX]

Does it work properly with ptpv1?

[prldm]

Produces exactly the same issue but I guess that's normal as no clock leader is present in my network atm.

[MeestorX]

I'm not sure that matters, just going to check. Did it EVER work for you?

[prldm]

No, never. I saw your issues and found your Discord, I sent a request.

[MeestorX]

Ok, I think you're right about needing a Dante device for ptpv1 to work. I just tried using DVS only and no luck.
Do you have statime running? Did you edit inferno-ptpv2.toml?

[prldm]

Yes, it is running as root, you can see my inferno-ptpv2 config in the log.txt I attached above. Also I turned off SELinux to avoid permission errors.

[MeestorX]

Copy. What's the output from statime showing?

[prldm]

statime log.txt

[teodly]

Ok, I think you're right about needing a Dante device for ptpv1 to work. I just tried using DVS only and no luck.

That's true. It will be difficult to get working with DVS only because DVS doesn't support PTPv2 at all and PTPv1 leader/master, and Statime doesn't support PTPv1 leader/master. To make it work without additional devices in the network:

• use DVia instead of DVS, or
• dig old linuxptp code before PTPv1 was removed, try to compile it and run it in VM/container/different IP than Statime

[MeestorX]

Is there a way to check for a valid dante clock? I see the errors from pipewire, but just curious if there's a way before running pw to check before?

[2026-02-11T17:33:33.158582Z INFO  inferno_aoip::device_server] clock path: None
[2026-02-11T17:33:33.159251Z INFO  inferno_aoip::device_server] waiting for clock
[2026-02-11T17:33:33.159750Z INFO  inferno_aoip::device_server] clock ready
[2026-02-11T17:33:33.160385Z INFO  inferno_aoip::device_server] all common tasks spawned
[2026-02-11T17:33:33.162845Z DEBUG asound_module_pcm_inferno] started receiver
[2026-02-11T17:33:33.174219Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:34.174288Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:35.174005Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:36.174584Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:37.173860Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:38.167490Z ERROR asound_module_pcm_inferno] no clock available (timeout waiting for overlay update)
[E][10:33:38.168787] spa.alsa     | [      alsa-pcm.c: 2370 spa_alsa_set_format()] set_hw_params: Connection timed out
[E][10:33:38.170660] pw.node      | [     impl-node.c:  473 node_update_state()] (Inferno_source-55) suspended -> error (Start error: Connection timed out)
[2026-02-11T17:33:38.174960Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:39.173404Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:40.173531Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:41.174182Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:42.173888Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:43.174802Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:44.174465Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:45.174653Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available
[2026-02-11T17:33:46.174696Z DEBUG inferno_aoip::device_server::info_mcast_server] no clock available

[teodly]

@MeestorX yes, our fork of Statime exports /tmp/clock-stats.* and we're using it to get master clock MAC address

It is, however, updated, only when master clock changes, not when it disappears.

Statime also offers monitoring API which may be more robust, but I don't exactly remember how useful it would be, I was testing it long time ago: https://github.com/teodly/statime/blob/inferno-dev/statime-linux/bin/statime-metrics-exporter.rs