* ALSA error on finding "working profile" for a USB MIDI device.
[not found] <1603213986151724100-webhooks-bot@alsa-project.org>
@ 2020-10-20 17:13 ` GitHub issues - edited
0 siblings, 0 replies; 2+ messages in thread
From: GitHub issues - edited @ 2020-10-20 17:13 UTC (permalink / raw)
To: alsa-devel
alsa-project/alsa-lib issue #89 was edited from radiobla:
TL;DR: After upgrading alsa-* packages yesterday, on the next reboot, systemd (apparently, pulseaudio.service) begun to show an error message related to "module-alsa-card" not finding a "working profile" for a USB MIDI device I have connected. Despite the error message, the device is working fine (through "raw MIDI" and also with jack2). Anyway, I want go further and find the root cause of this problem, since it's very annoying to see the Sound Service failing on every reboot.
Here is my pacman.log from yesterday:
**[ALPM] upgraded alsa-topology-conf (1.2.3-1 -> 1.2.4-1)
[ALPM] upgraded alsa-ucm-conf (1.2.3-2 -> 1.2.4-1)
[ALPM] upgraded alsa-lib (1.2.3.2-1 -> 1.2.4-1)
[ALPM] upgraded alsa-utils (1.2.3-2 -> 1.2.4-1)
[ALPM] upgraded lib32-alsa-lib (1.2.3.2-1 -> 1.2.4-1)**
After a reboot, the Sound Service could start, but begun to show an error message.
Taking a look on the systemd logs with
journalctl -xe --user-unit pulseaudio
I found this:
systemd[1027]: Starting Sound Service...
...
**pulseaudio[1037]: Failed to find a working profile.
pulseaudio[1037]: Failed to load module "module-alsa-card" (argument: "device_id="3" name="usb-Roland_A->
pulseaudio[1037]: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from>
systemd[1027]: Started Sound Service.**
I disabled the "load-module module-rescue-streams" on the default.pa, but the other issue persists. They seem not be related, IMO. I wanted to rule out that chance anyway.
By stopping pulseaudio service through systemd and running
pulseaudio -vvv
manually, I got more verbose information.
**E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-Roland_A-Series_Keyboard-00" card_name="alsa_card.usb-Roland_A-Series_Keyboard-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
I: [pulseaudio] module-udev-detect.c: Card /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/sound/card1 (alsa_card.usb-Roland_A-Series_Keyboard-00) failed to load module.**
Regarding specifically to the following error message...
**E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.**
What does it mean it is not finding a "working profile"? How could I investigate it further?
It worth mentioning that the device (an USB Keyboard Controller) is working
perfectly with jack2. I tested it with an "aseqdump".
$ aseqdump -l
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
20:0 A-Series Keyboard A-Series Keyboard Keyboard
$ aseqdump -p20:0
Waiting for data. Press Ctrl+C to end.
Source Event Ch Data
20:0 Note on 0, note 41, velocity 76
20:0 Note on 0, note 40, velocity 82
Although the device is working even with the error message, it's very annoying to see a "failed service" on initialization.
Thanks!
More occurrences of this error were provided on Arch Linux [forum](https://bbs.archlinux.org/viewtopic.php?pid=1932801)
Issue URL : https://github.com/alsa-project/alsa-lib/issues/89
Repository URL: https://github.com/alsa-project/alsa-lib
^ permalink raw reply [flat|nested] 2+ messages in thread
* ALSA error on finding "working profile" for a USB MIDI device.
[not found] <1603213714749353886-webhooks-bot@alsa-project.org>
@ 2020-10-20 17:08 ` GitHub issues - opened
0 siblings, 0 replies; 2+ messages in thread
From: GitHub issues - opened @ 2020-10-20 17:08 UTC (permalink / raw)
To: alsa-devel
alsa-project/alsa-lib issue #89 was opened from radiobla:
TL;DR: After upgrading alsa-* packages yesterday, on the next reboot, systemd (apparently, pulseaudio.service) begun to show an error message related to "module-alsa-card" not finding a "working profile" for a USB MIDI device I have connected. Despite the error message, the device is working fine (through "raw MIDI" and also with jack2). Anyway, I want go further and find the root cause of this problem, since it's very annoying to see the Sound Service failing on every reboot.
Here is my pacman.log from yesterday:
**[ALPM] upgraded alsa-topology-conf (1.2.3-1 -> 1.2.4-1)
[ALPM] upgraded alsa-ucm-conf (1.2.3-2 -> 1.2.4-1)
[ALPM] upgraded alsa-lib (1.2.3.2-1 -> 1.2.4-1)
[ALPM] upgraded alsa-utils (1.2.3-2 -> 1.2.4-1)
[ALPM] upgraded lib32-alsa-lib (1.2.3.2-1 -> 1.2.4-1)**
After a reboot, the Sound Service could start, but begun to show an error message.
Taking a look on the systemd logs with
journalctl -xe --user-unit pulseaudio
I found this:
systemd[1027]: Starting Sound Service...
...
**pulseaudio[1037]: Failed to find a working profile.
pulseaudio[1037]: Failed to load module "module-alsa-card" (argument: "device_id="3" name="usb-Roland_A->
pulseaudio[1037]: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from>
systemd[1027]: Started Sound Service.**
I disabled the "load-module module-rescue-streams" on the default.pa, but the other issue persists. They seem not be related, IMO. I wanted to rule out that chance anyway.
By stopping pulseaudio service through systemd and running
pulseaudio -vvv
manually, I got more verbose information.
**E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-Roland_A-Series_Keyboard-00" card_name="alsa_card.usb-Roland_A-Series_Keyboard-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
I: [pulseaudio] module-udev-detect.c: Card /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/sound/card1 (alsa_card.usb-Roland_A-Series_Keyboard-00) failed to load module.**
Regarding specifically to the following error message...
**E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.**
What does it mean it is not finding a "working profile"? How could I investigate it further?
It worth mentioning that the device (an USB Keyboard Controller) is working
perfectly with jack2. I tested it with an "aseqdump".
$ aseqdump -l
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
20:0 A-Series Keyboard A-Series Keyboard Keyboard
$ aseqdump -p20:0
Waiting for data. Press Ctrl+C to end.
Source Event Ch Data
20:0 Note on 0, note 41, velocity 76
20:0 Note on 0, note 40, velocity 82
Although the device is working even with the error message, it's very annoying to see a "failed service" on initialization.
Thanks!
More occurrences of this error were provided on Arch Linux forum: [](https://bbs.archlinux.org/viewtopic.php?pid=1932801)
Issue URL : https://github.com/alsa-project/alsa-lib/issues/89
Repository URL: https://github.com/alsa-project/alsa-lib
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-10-20 17:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <1603213986151724100-webhooks-bot@alsa-project.org>
2020-10-20 17:13 ` ALSA error on finding "working profile" for a USB MIDI device GitHub issues - edited
[not found] <1603213714749353886-webhooks-bot@alsa-project.org>
2020-10-20 17:08 ` GitHub issues - opened
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).