Roland Mobile UA-M10 USB dac/sound device stopped working after a random update

About 6/7 weeks ago (beginning of October), my sound-card stopped being detected in Gnome’s Sound Output menu options.

I did a fresh install of Fedora 37 yesterday, but the problem persisted.

If I check with sudo dmesg -w, I get this reported:

[ 6378.882116] usb 2-1.7: USB disconnect, device number 5
[ 6383.661870] usb 2-1.7: new high-speed USB device number 6 using ehci-pci
[ 6383.962349] usb 2-1.7: New USB device found, idVendor=0582, idProduct=0199, bcdDevice= 1.05
[ 6383.962360] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6383.962363] usb 2-1.7: Product: UA-M10
[ 6383.962365] usb 2-1.7: Manufacturer: Roland
[ 6383.962367] usb 2-1.7: SerialNumber: MBUA0a7636f2b0242ef0ac6ab6e0ac5c

I tried different USB port, and got a slightly different report:

[ 6466.806437] usb 3-4: new high-speed USB device number 4 using xhci_hcd
[ 6467.057890] usb 3-4: New USB device found, idVendor=0582, idProduct=0199, bcdDevice= 1.05
[ 6467.057899] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6467.057903] usb 3-4: Product: UA-M10
[ 6467.057906] usb 3-4: Manufacturer: Roland
[ 6467.057908] usb 3-4: SerialNumber: MBUA0a7636f2b0242ef0ac6ab6e0ac5c

So the system seems to detect the device correctly, but doesn’t adopt it as a suitable sound device.

Welcome to ask.fedora @ariaan

This could be while we made the change from kernel 5.x.x to 6.x.x.

Do you have still an 5.x.x kernel to enter while booting and check what drivers the system uses for your device?
inxi -Ja should reveal that.

No it was shortly before the kernel moved to version 6. I remember this distinctly, because I was surprised that 37 beta at the time was also still on Kernel 5.“something”.

Anyway, this is what inxi gave me:

 Device-2: 3-4:3 info: Roland UA-M10 type: <vendor specific>
    driver: snd-usb-audio interfaces: 7 rev: 2.0 speed: 480 Mb/s power: 500mA
    chip-ID: 0582:0199 class-ID: ff00
    serial: MBUA0a7636f2b0242ef0ac6ab6e0ac5c

Are you on the latest firmware?
It seams that there is a version 2.02 on Rolands webpage

Not aware, also no Idea how to get it on there. But would that be the reason why it suddenly breaks?

You might have to check, find it out, searching etc.

Overflying the page I linked, I saw some instructions. Checking and verifying is up to you.

Nobody said it is broken, for me it looks like that there where some changes made before Kernel 6.0.x has been introduced. Fedora Linux is very dynamic, things change. Gnome got updated to V.43 and even if F37 is stable now it not means that everything works as it worked by F36.

I have a suspicion Gnome 43 might be the culprit to be honest. Since that was one of the major differences between F36 & F37.

I’ll see if I can update the firmware through a different device. Thank you for your help so far.

1 Like

Hmm, strange. I managed to update the firmware successfully (If I’d to believe the update tool) but inxi still reports the same output for the device:

  Device-2: 3-4:4 info: Roland UA-M10 type: <vendor specific>
    driver: snd-usb-audio interfaces: 7 rev: 2.0 speed: 480 Mb/s power: 500mA
    chip-ID: 0582:0199 class-ID: ff00
    serial: MBUA0a7636f2b0242ef0ac6ab6e0ac5c

It should be on 2.02 now…
At a first glance, dmesg’s output also didn’t change:

[  113.845791] usb 3-4: USB disconnect, device number 3
[  124.381640] usb 3-4: new high-speed USB device number 4 using xhci_hcd
[  124.633496] usb 3-4: New USB device found, idVendor=0582, idProduct=0199, bcdDevice= 1.05
[  124.633504] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  124.633507] usb 3-4: Product: UA-M10
[  124.633509] usb 3-4: Manufacturer: Roland
[  124.633511] usb 3-4: SerialNumber: MBUA0a7636f2b0242ef0ac6ab6e0ac5c

Oh, and ofcourse, it’s still not recognized as an audio device.

Okay, this is weird… it’s also not mentioned on ALSA’s supported device list

Have a look if you have pavucontrol installed. Would like to know if you can see it there.

If not, it might be an idea if you try a live iso with a spin like Mate/Xfce desktop. Just to know if it is really because of Gnome.

It’s not showing up in pavucontrol. Also, I noticed alsamixer also doesn’t detect the device.

I don´t know what changed, but the last Fedora update fixed it, it’s back! \o/

1 Like

If you’re interested in what was updated.

sudo dnf history --reverse
sudo dnf history info ID will tell you was installed.

If you’re using gnome software I believe you can also do:
pkcon get-transactions

2 Likes

thank you, that helped… I’m following the crumbs right now, seems alsa updated to:

alsa-lib-1.2.8-1.fc37.i686

However I can’t exactly seem to pin point where it might’ve influenced my install:
https://www.alsa-project.org/wiki/Changes_v1.2.7.2_v1.2.8

https://www.alsa-project.org/wiki/Detailed_changes_v1.2.7.2_v1.2.8

I’m mostly just happy it’s back :slight_smile:

1 Like