Re: M-Audio Fast Track Ultra 8R
On Jul 07 18:03:56, h...@stare.cz wrote: > On Jul 01 15:07:48, a...@caoua.org wrote: > > On Sun, Jun 30, 2024 at 08:26:06AM +0200, Jan Stary wrote: > > > This is current/amd64 on a PC (full dmesg below). > > > I got my hands on an M-Audio Fast Track Ultra 8R, > > > an USB audio interface; eight tracks, 24/96, nice. > > > > > > It doesn't seem to be supported though: > > > it attaches as an ugen, but no uaudio. > > > > > > umidi0 at uhub4 port 2 configuration 1 interface 3 "M-Audio Fast Track > > > Ultra 8R" rev 2.00/1.51 addr 3 > > > umidi0: (genuine USB-MIDI) > > > umidi0: out=1, in=1 > > > midi0 at umidi0: > > > ugen0 at uhub4 port 2 configuration 1 "M-Audio Fast Track Ultra 8R" rev > > > 2.00/1.51 addr 3 > > > > > > This happens in any USB slot. > > > > > > What can I do to debug this? > > > Is anyone using this on OpenBSD? > > > > > > It is an USB-compliant audio device, > > > macOS and Windows use it just fine. > > > > It seems that the uaudio driver doesn't even try to attach. You could > > instrument the uaudio_match() kernel function, and try to figure out > > why it returns UMATCH_NONE for your device. > > For the record, it is _not_ a USB-compliant audio device. > I had another one plugged into mac by mistake (sorry), > and on win, it only works with the latest = 2014 drivers. But then again, it attaches like this on FreeBSD: ugen0.6: at usbus0 uaudio0 on uhub2 uaudio0: on usbus0 uaudio0: Play[0]: 96000 Hz, 8 ch, 24-bit S-LE PCM format, 2x4ms buffer. (selected) uaudio0: Play[0]: 88200 Hz, 8 ch, 24-bit S-LE PCM format, 2x4ms buffer. uaudio0: Play[0]: 48000 Hz, 8 ch, 24-bit S-LE PCM format, 2x4ms buffer. uaudio0: Play[0]: 44100 Hz, 8 ch, 24-bit S-LE PCM format, 2x4ms buffer. uaudio0: Record[0]: 96000 Hz, 8 ch, 24-bit S-LE PCM format, 2x4ms buffer. (selected) uaudio0: Record[0]: 88200 Hz, 8 ch, 24-bit S-LE PCM format, 2x4ms buffer. uaudio0: Record[0]: 48000 Hz, 8 ch, 24-bit S-LE PCM format, 2x4ms buffer. uaudio0: Record[0]: 44100 Hz, 8 ch, 24-bit S-LE PCM format, 2x4ms buffer. uaudio0: Single command MIDI quirk enabled uaudio0: MIDI sequencer. pcm3 on uaudio0 uaudio0: No HID volume keys found. But according to wiki, class 0xef (= 239) is "miscelaneous", i.e. not audio, which is 0x01, so I still don't believe it is a class-compliant device ... Jan
Re: M-Audio Fast Track Ultra 8R
On Jul 01 15:07:48, a...@caoua.org wrote: > On Sun, Jun 30, 2024 at 08:26:06AM +0200, Jan Stary wrote: > > This is current/amd64 on a PC (full dmesg below). > > I got my hands on an M-Audio Fast Track Ultra 8R, > > an USB audio interface; eight tracks, 24/96, nice. > > > > It doesn't seem to be supported though: > > it attaches as an ugen, but no uaudio. > > > > umidi0 at uhub4 port 2 configuration 1 interface 3 "M-Audio Fast Track > > Ultra 8R" rev 2.00/1.51 addr 3 > > umidi0: (genuine USB-MIDI) > > umidi0: out=1, in=1 > > midi0 at umidi0: > > ugen0 at uhub4 port 2 configuration 1 "M-Audio Fast Track Ultra 8R" rev > > 2.00/1.51 addr 3 > > > > This happens in any USB slot. > > > > What can I do to debug this? > > Is anyone using this on OpenBSD? > > > > It is an USB-compliant audio device, > > macOS and Windows use it just fine. > > It seems that the uaudio driver doesn't even try to attach. You could > instrument the uaudio_match() kernel function, and try to figure out > why it returns UMATCH_NONE for your device. For the record, it is _not_ a USB-compliant audio device. I had another one plugged into mac by mistake (sorry), and on win, it only works with the latest = 2014 drivers.
Re: M-Audio Fast Track Ultra 8R
On Sun, Jun 30, 2024 at 08:26:06AM +0200, Jan Stary wrote: > This is current/amd64 on a PC (full dmesg below). > I got my hands on an M-Audio Fast Track Ultra 8R, > an USB audio interface; eight tracks, 24/96, nice. > > It doesn't seem to be supported though: > it attaches as an ugen, but no uaudio. > > umidi0 at uhub4 port 2 configuration 1 interface 3 "M-Audio Fast Track Ultra > 8R" rev 2.00/1.51 addr 3 > umidi0: (genuine USB-MIDI) > umidi0: out=1, in=1 > midi0 at umidi0: > ugen0 at uhub4 port 2 configuration 1 "M-Audio Fast Track Ultra 8R" rev > 2.00/1.51 addr 3 > > This happens in any USB slot. > > What can I do to debug this? > Is anyone using this on OpenBSD? > > It is an USB-compliant audio device, > macOS and Windows use it just fine. It seems that the uaudio driver doesn't even try to attach. You could instrument the uaudio_match() kernel function, and try to figure out why it returns UMATCH_NONE for your device.
Re: M-Audio Fast Track Ultra 8R
On Jun 30 03:55:00, kolip...@exoticsilicon.com wrote: > On Sun, Jun 30, 2024 at 08:26:06AM +0200, Jan Stary wrote: > > What can I do to debug this? > > usbdevs -vv Thanks, full output below > > uhub4: device problem, disabling port 2 > > Is this error reported each time you connect the device, or was it just > co-incidence that it happened this time? This particular USB port says thta from time to time, with various devices. It is one of the two front USB ports. But I have tried the MAudio in all the other USB ports too, the result is always the same. > If it does appear each time, does it make any difference booting with it > connected verses hotplugging? I was hotplugging it, but booting with the device connected and powered results in the same. Jan Controller /dev/usb0: addr 01: 8086: Intel, EHCI root hub high speed, self powered, config 1, rev 1.00 driver: uhub0 port 01: .0503 connect enabled power port 02: .0500 power addr 02: 8087:0024 Intel, Rate Matching Hub high speed, self powered, config 1, rev 0.00 driver: uhub3 port 01: .0100 power port 02: .0100 power port 03: .0100 power port 04: .0100 power port 05: .0303 connect enabled power port 06: .0303 connect enabled power addr 03: 046d:c31c Logitech, USB Keyboard low speed, power 90 mA, config 1, rev 64.00 driver: uhidev0 driver: uhidev1 addr 04: 0458:003a Genius, Optical Mouse low speed, power 100 mA, config 1, rev 1.00 driver: uhidev2 Controller /dev/usb1: addr 01: 1b6f: Etron, xHCI root hub super speed, self powered, config 1, rev 1.00 driver: uhub1 port 01: .0503 connect enabled recovery port 02: .02a0 power Rx.detect port 03: .02a0 power Rx.detect port 04: .02a0 power Rx.detect addr 02: 0763:2081 M-Audio, Fast Track Ultra 8R high speed, self powered, config 1, rev 1.51 driver: umidi0 driver: ugen0 Controller /dev/usb2: addr 01: 8086: Intel, EHCI root hub high speed, self powered, config 1, rev 1.00 driver: uhub2 port 01: .0503 connect enabled power port 02: .0500 power addr 02: 8087:0024 Intel, Rate Matching Hub high speed, self powered, config 1, rev 0.00 driver: uhub4 port 01: 0001.0100 power port 02: 0001.0100 power port 03: .0100 power port 04: .0100 power port 05: .0100 power port 06: .0100 power port 07: .0100 power port 08: .0100 power
Re: M-Audio Fast Track Ultra 8R
On Sun, Jun 30, 2024 at 08:26:06AM +0200, Jan Stary wrote: > What can I do to debug this? usbdevs -vv would be interesting. > uhub4: device problem, disabling port 2 Is this error reported each time you connect the device, or was it just co-incidence that it happened this time? If it does appear each time, does it make any difference booting with it connected verses hotplugging?
M-Audio Fast Track Ultra 8R
This is current/amd64 on a PC (full dmesg below). I got my hands on an M-Audio Fast Track Ultra 8R, an USB audio interface; eight tracks, 24/96, nice. It doesn't seem to be supported though: it attaches as an ugen, but no uaudio. umidi0 at uhub4 port 2 configuration 1 interface 3 "M-Audio Fast Track Ultra 8R" rev 2.00/1.51 addr 3 umidi0: (genuine USB-MIDI) umidi0: out=1, in=1 midi0 at umidi0: ugen0 at uhub4 port 2 configuration 1 "M-Audio Fast Track Ultra 8R" rev 2.00/1.51 addr 3 This happens in any USB slot. What can I do to debug this? Is anyone using this on OpenBSD? It is an USB-compliant audio device, macOS and Windows use it just fine. Jan OpenBSD 7.5-current (GENERIC.MP) #152: Wed Jun 26 20:42:02 MDT 2024 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8285454336 (7901MB) avail mem = 8011190272 (7640MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (36 entries) bios0: vendor Award Software International, Inc. version "F3" date 03/31/2011 bios0: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 acpi0 at bios0: ACPI 1.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET MCFG ASPT SSPT EUDS MATS TAMG APIC SSDT acpi0: wakeup devices PCI0(S5) PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) PEX4(S5) PEX5(S5) PEX6(S5) PEX7(S5) HUB0(S5) UAR1(S3) USBE(S3) USE2(S3) AZAL(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 acpimcfg0: addr 0xf400, bus 0-63 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 3492.10 MHz, 06-2a-07, patch 002f cpu0: cpuid 1 edx=bfebfbff ecx=17bae3ff cpu0: cpuid 6 eax=77 ecx=9 cpu0: cpuid 7.0 edx=9c000400 cpu0: cpuid a vers=3, gp=4, gpwidth=48, ff=3, ffwidth=48 cpu0: cpuid d.1 eax=1 cpu0: cpuid 8001 edx=28100800 ecx=1 cpu0: cpuid 8007 edx=100 cpu0: MELTDOWN cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 3492.14 MHz, 06-2a-07, patch 002f cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 3492.21 MHz, 06-2a-07, patch 002f cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 3492.25 MHz, 06-2a-07, patch 002f cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 3492.41 MHz, 06-2a-07, patch 002f cpu4: smt 1, core 0, package 0 cpu5 at mainbus0: apid 3 (application processor) cpu5: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 3492.27 MHz, 06-2a-07, patch 002f cpu5: smt 1, core 1, package 0 cpu6 at mainbus0: apid 5 (application processor) cpu6: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 3492.29 MHz, 06-2a-07, patch 002f cpu6: smt 1, core 2, package 0 cpu7 at mainbus0: apid 7 (application processor) cpu7: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 3492.37 MHz, 06-2a-07, patch 002f cpu7: smt 1, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins, remapped acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus 2 (PEX0) acpiprt4 at acpi0: bus -1 (PEX1) acpiprt5 at acpi0: bus -1 (PEX2) acpiprt6 at acpi0: bus -1 (PEX3) acpiprt7 at acpi0: bus 3 (PEX4) acpiprt8 at acpi0: bus 4 (PEX5) acpiprt9 at acpi0: bus 5 (PEX6) acpiprt10 at acpi0: bus 6 (PEX7) acpibtn0 at acpi0: PWRB acpipci0 at acpi0 PCI0 acpicmos0 at acpi0 com0 at acpi0 UAR1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo acpicpu0 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu4 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu5 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu6 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu7 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), C1(1000@1 mwait.1), PSS cpu0: using VERW MDS workaround (except on vmm entry) cpu0: Enhanced SpeedStep 3492 MHz: speeds: 3701, 3700, 3600, 3500, 3400, 3300, 3200, 3100, 3000, 2900, 2800, 2700, 2600, 250