They say that doing the same thing repeatedly, while expecting
a different result, is a sign of madness.
I've been trying to discover why my MOTU Ultralite AVB doesn't
work on Linux Mint 19.3 (5.3.0-40-generic) and see the following
in /var/log/syslog, which confirms, a total of 240 times, that:
"usb 1-14: clock source 1 is not valid"
I'm trying to dual boot. (Kernel 'thinks' my gaming wheel is a
mouse, so I had to make a udev rule for that.) and the MOTU is
usually synced to an external optical source at 48kHz. The boot
process appears to switch it to 192kHz briefly and then to 44.1k
which isn't going to be a good source because it's 48kHz.
Anyone using a MOTU with a modern Linux ubuntu flavour could help?
Relevant part of syslog below sig separator.
--
Thanks in advance.
/var/log/syslog:
Mar 5 20:40:40 mint01 kernel: [ 423.774917] usb 1-14: new high-speed USB device number 9 using xhci_hcd
Mar 5 20:40:40 mint01 kernel: [ 423.944393] usb 1-14: New USB device found, idVendor=07fd, idProduct=0005, bcdDevice= 2.00
Mar 5 20:40:40 mint01 kernel: [ 423.944398] usb 1-14: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 5 20:40:40 mint01 kernel: [ 423.944402] usb 1-14: Product: UltraLite AVB
Mar 5 20:40:40 mint01 kernel: [ 423.944405] usb 1-14: Manufacturer: MOTU
Mar 5 20:40:40 mint01 kernel: [ 423.944407] usb 1-14: SerialNumber: munged
Mar 5 20:40:40 mint01 mtp-probe: checking bus 1, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-14"
Mar 5 20:40:40 mint01 mtp-probe: bus: 1, device: 9 was not an MTP device
Mar 5 20:40:40 mint01 kernel: [ 423.970417] mc: Linux media interface: v0.10
Mar 5 20:40:40 mint01 kernel: [ 423.994249] usb 1-14: clock source 1 is not valid, cannot use
Mar 5 20:40:41 mint01 kernel: [ 424.832923] usb 1-14: clock source 1 is not valid, cannot use
Mar 5 20:40:41 mint01 kernel: [ 424.844172] usbcore: registered new interface driver snd-usb-audio
Mar 5 20:40:41 mint01 upowerd[1340]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-14
Mar 5 20:40:41 mint01 upowerd[1340]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.1
Mar 5 20:40:41 mint01 upowerd[1340]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.3
Mar 5 20:40:41 mint01 upowerd[1340]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.4
Mar 5 20:40:41 mint01 upowerd[1340]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.2
Mar 5 20:40:41 mint01 upowerd[1340]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0
Mar 5 20:40:41 mint01 kernel: [ 424.881343] usb 1-14: clock source 1 is not valid, cannot use
(previous line repeated 40 times)
Mar 5 20:40:44 mint01 pulseaudio[1302]: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
Mar 5 20:40:44 mint01 pulseaudio[1302]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-MOTU_UltraLite_AVB_0001f2fffe005ded-00" card_name="alsa_card.usb-MOTU_UltraLite_AVB_0001f2fffe005ded-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed.
(all repeated 6 times)
Mar 5 20:40:44 mint01 pulseaudio[1302]: [pulseaudio] module-udev-detect.c: Tried to configure /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/sound/card1 (alsa_card.usb-MOTU_UltraLite_AVB_0001f2fffe005ded-00) more often than 5 times in 10s
Hi list,
another general linux audio question:
I've been using realtimeconfigquickscan [1] for years to tweak systems
for better audio. Lately I wonder if the suggestions it gives are all
still valid and up-to-date with current operating system defaults, SSD
memory, etc.
Anyone else using this script and what are your observations?
For reference my output looks like this:
$ perl realTimeConfigQuickScan.pl
== GUI-enabled checks ==
Checking if you are root... no - good
Checking filesystem 'noatime' parameter... 5.3.18 kernel - good
(relatime is default since 2.6.30)
Checking CPU Governors... CPU 0: 'performance' CPU 1: 'performance' CPU
2: 'performance' CPU 3: 'performance' CPU 4: 'performance' CPU 5:
'performance' CPU 6: 'performance' CPU 7: 'performance' - good
Checking swappiness... 10 - good
Checking for resource-intensive background processes... none found - good
Checking checking sysctl inotify max_user_watches... >= 524288 - good
Checking access to the high precision event timer... readable - good
Checking access to the real-time clock... readable - good
Checking whether you're in the 'audio' group... yes - good
Checking for multiple 'audio' groups... no - good
Checking the ability to prioritize processes with chrt... yes - good
Checking kernel support for high resolution timers... found - good
Kernel with Real-Time Preemption... not found - not good
Kernel without real-time capabilities found
For more information, see
http://wiki.linuxaudio.org/wiki/system_configuration#installing_a_real-time…
Checking if kernel system timer is high-resolution... found - good
Checking kernel support for tickless timer... found - good
== Other checks ==
Checking filesystem types... ok.
I use a lowelatency kernel, not a rt-kernel hence the "not good" there.
[1] https://github.com/raboof/realtimeconfigquickscan
I'm a bit concerned that this is going to be just about the expected peak of the
Covid-19 infections. I hope we are still good to go.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
