ALSA Driver no longer found.

kitman · November 2, 2019, 6:59am

Hi. For some reason after booting today, my alsa driver no longer loads causing issues with my jack server.

Extract from /var/log/messages

2019-11-02T13:31:20.923390+08:00 asus-roc pulseaudio[2035]: E: [pulseaudio] module-jack-sink.c: jack_client_open() failed.
2019-11-02T13:31:20.923725+08:00 asus-roc pulseaudio[2035]: E: [pulseaudio] module.c: Failed to load module “module-jack-sink” (argument: “”): initialization failed.
2019-11-02T13:31:20.925953+08:00 asus-roc pulseaudio[2035]: W: [pulseaudio] module-jack-source.c: JACK error >Cannot connect to server socket err = No such file or directory<
2019-11-02T13:31:20.926335+08:00 asus-roc pulseaudio[2035]: W: [pulseaudio] module-jack-source.c: JACK error >Cannot connect to server request channel<
2019-11-02T13:31:20.935234+08:00 asus-roc pulseaudio[2035]: Could not open component .so ‘/usr/lib64/jack/jack_alsa.so’: /usr/lib64/jack/jack_alsa.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
2019-11-02T13:31:20.935460+08:00 asus-roc pulseaudio[2035]: Could not open component .so ‘/usr/lib64/jack/jack_alsa.so’: /usr/lib64/jack/jack_alsa.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
2019-11-02T13:31:20.935542+08:00 asus-roc pulseaudio[2035]: jack_get_descriptor : dll jack_alsa.so is not a driver
2019-11-02T13:31:20.935609+08:00 asus-roc pulseaudio[2035]: jack_get_descriptor returns null for ‘jack_alsa.so’
2019-11-02T13:31:20.935681+08:00 asus-roc pulseaudio[2035]: Could not open component .so ‘/usr/lib64/jack/jack_alsarawmidi.so’: /usr/lib64/jack/jack_alsarawmidi.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
2019-11-02T13:31:20.935827+08:00 asus-roc pulseaudio[2035]: Could not open component .so ‘/usr/lib64/jack/jack_alsarawmidi.so’: /usr/lib64/jack/jack_alsarawmidi.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
2019-11-02T13:31:20.935908+08:00 asus-roc pulseaudio[2035]: jack_get_descriptor : dll jack_alsarawmidi.so is not a driver
2019-11-02T13:31:20.935975+08:00 asus-roc pulseaudio[2035]: jack_get_descriptor returns null for ‘jack_alsarawmidi.so’
2019-11-02T13:31:20.938991+08:00 asus-roc pulseaudio[2035]: no message buffer overruns
2019-11-02T13:31:20.941696+08:00 asus-roc pulseaudio[2035]: no message buffer overruns
2019-11-02T13:31:20.942910+08:00 asus-roc pulseaudio[2035]: Could not open component .so ‘/usr/lib64/jack/jack_alsa.so’: /usr/lib64/jack/jack_alsa.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
2019-11-02T13:31:20.943108+08:00 asus-roc pulseaudio[2035]: Could not open component .so ‘/usr/lib64/jack/jack_alsarawmidi.so’: /usr/lib64/jack/jack_alsarawmidi.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
2019-11-02T13:31:20.945753+08:00 asus-roc pulseaudio[2035]: no message buffer overruns
2019-11-02T13:31:20.946483+08:00 asus-roc pulseaudio[2035]: Unknown driver "alsa"
2019-11-02T13:31:20.946572+08:00 asus-roc pulseaudio[2035]: jackdmp 1.9.13

I have reinstalled all alsa packages and rebooted but to no avail.

I know my soundcard is working because I can play audio via pulseaudio, but I need jack for my audio workstation and jack won’t work without alsa.
/home/chris/Pictures/YaST2 - Sound — YaST2 - sound @ asus-roc.lan_110.png

chris@asus-roc:/var/log> aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC1220 Analog [ALC1220 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC1220 Digital [ALC1220 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I’ve gone around in circles for hours trying to sort this out. Any tips on how to further debug what’s happened to alsa?

Thanks,
Chris.

deano_ferrari · November 2, 2019, 8:07am

I know little about using jack, but I wanted to know are you using qjackctl to configure/start it? Have you tried restarting it?

Something else to try, restart pulse audio with

pulseaudio -k

You can also disable and enable (as root) with

sudo setup-pulseaudio --disable
sudo setup-pulseaudio --enable

Try loading the relevant pulseaudio modules…

pactl load-module module-jack-source

If this fails with

Failure: Module initialization failed

repeat the command again, then do

pactl load-module module-jack-sink

Check…

ps -A|grep jack

The jackd daemon should be present.

Does it now work as expected?

kitman · November 2, 2019, 10:06am

Hi Deano,
I use cadence to configure/control jack. https://paste.opensuse.org/99032900 but from it’s settings the ALSA driver is no longer available https://paste.opensuse.org/42353901.

There is no issue with jack and pulseaudio together -

chris@asus-roc:/var/log> ps -A|grep jack
 2377 ?        00:00:03 jackdbus

The two modules module-jack-source and module-jack-sink are loaded automatically as they are set in /etc/pulse/default.pa as

load-module module-jack-sink
load-module module-jack-source

BTW - running

chris@asus-roc:/var/log> sudo pulseaudio -k
[sudo] password for root: 
E: [pulseaudio] main.c: Failed to kill daemon: No such process

never works.

chris@asus-roc:/var/log> ps -A|grep pulseaudio
22501 ?        00:00:41 pulseaudio

It’s the missing alsa driver that is the issue.

Thanks.

deano_ferrari · November 2, 2019, 10:08am

That’s because you run it as user (not with sudo)

deano_ferrari · November 2, 2019, 10:11am

Yes, I got that already, but I had read that sometimes the PA modules can fail for whatever reason and that is why I had you try reloading them manually just to see if that worked ok.

deano_ferrari · November 2, 2019, 11:06am

The Cadence image shows less backends than I would expect given the following are included via jack…

dean@linux-4k1z:~> ls -l /usr/lib64/jack/
total 568
-rwxr-xr-x 1 root root  48088 Mar 18  2019 audioadapter.so
-rwxr-xr-x 1 root root  10328 Mar 18  2019 inprocess.so
-rwxr-xr-x 1 root root  60704 Mar 18  2019 jack_alsarawmidi.so
-rwxr-xr-x 1 root root 115944 Mar 18  2019 jack_alsa.so
-rwxr-xr-x 1 root root  18744 Mar 18  2019 jack_dummy.so
-rwxr-xr-x 1 root root  43928 Mar 18  2019 jack_firewire.so
-rwxr-xr-x 1 root root  14640 Mar 18  2019 jack_loopback.so
-rwxr-xr-x 1 root root  64736 Mar 18  2019 jack_netone.so
-rwxr-xr-x 1 root root  47960 Mar 18  2019 jack_net.so
-rwxr-xr-x 1 root root  35488 Mar 18  2019 jack_proxy.so
-rwxr-xr-x 1 root root  43904 Mar 18  2019 netadapter.so
-rwxr-xr-x 1 root root  44048 Mar 18  2019 netmanager.so
-rwxr-xr-x 1 root root  14760 Mar 18  2019 profiler.so

How does that compare with your system?

Are you using jack or jack2?

zypper se -s jack

kitman · November 2, 2019, 11:08am

Sorry, didn’t mean to nag :o

As a further test, I removed the two source and sink module entries from /etc/pulse/default.pa and rebooted.

I ran manually

chris@asus-roc:~> pactl load-module module-jack-source
Failure: Module initialization failed
chris@asus-roc:~> pactl load-module module-jack-source
Failure: Module initialization failed
chris@asus-roc:~> pactl load-module module-jack-sink
Failure: Module initialization failed
chris@asus-roc:~> pactl load-module module-jack-sink
Failure: Module initialization failed
chris@asus-roc:~>

always failing.

But when I checked

chris@asus-roc:~> ps -A|grep jack
 2390 ?        00:00:00 jackdbus

The jackd daemon is not running even though cadence tells me it is.

Tried to run jackd manually -

chris@asus-roc:~> jackd
jackdmp 1.9.13
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2019 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Could not open component .so '/usr/lib64/jack/jack_alsa.so': /usr/lib64/jack/jack_alsa.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
Could not open component .so '/usr/lib64/jack/jack_alsa.so': /usr/lib64/jack/jack_alsa.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
jack_get_descriptor : dll jack_alsa.so is not a driver
jack_get_descriptor returns null for 'jack_alsa.so'
Could not open component .so '/usr/lib64/jack/jack_alsarawmidi.so': /usr/lib64/jack/jack_alsarawmidi.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
Could not open component .so '/usr/lib64/jack/jack_alsarawmidi.so': /usr/lib64/jack/jack_alsarawmidi.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
jack_get_descriptor : dll jack_alsarawmidi.so is not a driver
jack_get_descriptor returns null for 'jack_alsarawmidi.so'
no message buffer overruns
no message buffer overruns
Could not open component .so '/usr/lib64/jack/jack_alsa.so': /usr/lib64/jack/jack_alsa.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
Could not open component .so '/usr/lib64/jack/jack_alsarawmidi.so': /usr/lib64/jack/jack_alsarawmidi.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
no message buffer overruns

Usage: jackdmp  --no-realtime OR -r ]
                --realtime OR -R  --realtime-priority OR -P priority ] ]
      (the two previous arguments are mutually exclusive. The default is --realtime)
                --name OR -n server-name ]
                --timeout OR -t client-timeout-in-msecs ]
                --loopback OR -L loopback-port-number ]
                --port-max OR -p maximum-number-of-ports]
                --slave-backend OR -X slave-backend-name ]
                --internal-client OR -I internal-client-name ]
                --internal-session-file OR -C internal-session-file ]
                --verbose OR -v ]
                --clocksource OR -c  h(pet) | s(ystem) ]
                --autoconnect OR -a <modechar>]
                 where <modechar> is one of:
                   ' ' - Don't restrict self connect requests (default)
                   'E' - Fail self connect requests to external ports only
                   'e' - Ignore self connect requests to external ports only
                   'A' - Fail all self connect requests
                   'a' - Ignore all self connect requests
                --replace-registry ]
                --silent OR -s ]
                --sync OR -S ]
                --temporary OR -T ]
                --version OR -V ]
         -d master-backend-name  ... master-backend args ... ]
       jackdmp -d master-backend-name --help
             to display options for each master backend

Now I’m scratching the other side of my head.

deano_ferrari · November 2, 2019, 11:22am

What happens if you try starting it with

jackd -r -d alsa

or

jackd -r -d alsa -r 44100

kitman · November 2, 2019, 11:50am

Same nonsense.

chris@asus-roc:~> jackd -r -d alsa -r 44100
jackdmp 1.9.13
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2019 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Could not open component .so '/usr/lib64/jack/jack_alsa.so': /usr/lib64/jack/jack_alsa.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
Could not open component .so '/usr/lib64/jack/jack_alsa.so': /usr/lib64/jack/jack_alsa.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
jack_get_descriptor : dll jack_alsa.so is not a driver
jack_get_descriptor returns null for 'jack_alsa.so'
Could not open component .so '/usr/lib64/jack/jack_alsarawmidi.so': /usr/lib64/jack/jack_alsarawmidi.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
Could not open component .so '/usr/lib64/jack/jack_alsarawmidi.so': /usr/lib64/jack/jack_alsarawmidi.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
jack_get_descriptor : dll jack_alsarawmidi.so is not a driver
jack_get_descriptor returns null for 'jack_alsarawmidi.so'
no message buffer overruns
no message buffer overruns
Could not open component .so '/usr/lib64/jack/jack_alsa.so': /usr/lib64/jack/jack_alsa.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
Could not open component .so '/usr/lib64/jack/jack_alsarawmidi.so': /usr/lib64/jack/jack_alsarawmidi.so: undefined symbol: _ZN4Jack10JackEngine21PortSetDeviceMetadataEjPKc
no message buffer overruns
Unknown driver "alsa"

deano_ferrari · November 2, 2019, 11:54am

Can you check post #6 and compare notes?

kitman · November 2, 2019, 12:07pm

Oh, I missed that post. But -

chris@asus-roc:~> ls -l /usr/lib64/jack
total 572
-rwxr-xr-x 1 root root  48088 Oct 31 14:56 audioadapter.so
-rwxr-xr-x 1 root root  10336 Oct 31 14:56 inprocess.so
-rwxr-xr-x 1 root root  60720 Oct 31 14:56 jack_alsarawmidi.so
-rwxr-xr-x 1 root root 120112 Oct 31 14:56 jack_alsa.so
-rwxr-xr-x 1 root root  18744 Oct 31 14:56 jack_dummy.so
-rwxr-xr-x 1 root root  43920 Oct 31 14:56 jack_firewire.so
-rwxr-xr-x 1 root root  14632 Oct 31 14:56 jack_loopback.so
-rwxr-xr-x 1 root root  68856 Oct 31 14:56 jack_netone.so
-rwxr-xr-x 1 root root  43856 Oct 31 14:56 jack_net.so
-rwxr-xr-x 1 root root  35488 Oct 31 14:56 jack_proxy.so
-rwxr-xr-x 1 root root  43912 Oct 31 14:56 netadapter.so
-rwxr-xr-x 1 root root  44048 Oct 31 14:56 netmanager.so
-rwxr-xr-x 1 root root  14752 Oct 31 14:56 profiler.so
chris@asus-roc:~>

Looks the same.
Using jack 2.

deano_ferrari · November 2, 2019, 12:11pm

Ok, but please also show

zypper se -si jack

For the purposes of assistance I have installed

i  | jack                    | package | 1.9.12-lp151.2.4     | x86_64 | openSUSE-Leap-15.1-Oss

deano_ferrari · November 2, 2019, 12:15pm

That likely explains the difference with the behaviour you’re encountering here. Which repo did you get this package from?

kitman · November 2, 2019, 12:21pm

deano_ferrari:

Ok, but please also show
zypper se -si jack
For the purposes of assistance I have installed
i  | jack                    | package | 1.9.12-lp151.2.4     | x86_64 | openSUSE-Leap-15.1-Oss

i+ | jack                    | package | 1.9.13-lp151.114.1      | x86_64 | multimedia:libs

deano_ferrari · November 2, 2019, 12:27pm

Ok, that confirms a different version to the one I have installed from OSS repo. Change to the version that I have and test again. You may need to file a bug report here.

kitman · November 2, 2019, 12:38pm

i+ | jack                    | package | 1.9.12-lp151.2.4        | x86_64 | Main Repository

No difference when downgraded. But I have used that newer version for a while now without issue. Would uninstalling alsa then reinstalling help?

EDIT: Forgot to reboot. ALSA now appears as a driver in the older version of jack!! I am mighty confused now. I’m double checking when jack got updated.
Thanks.

kitman · November 2, 2019, 1:41pm

It seems that the version giving me grief

i+ | jack                    | package | 1.9.13-lp151.114.1      | x86_64 | multimedia:libs

was updated on 31 Oct, so it must have been updated yesterday or this morning without me taking any notice - how ignorant of me to say I have used this version “for a while”.

So, I can go back and forth with testing versions of jack and if needs be lodge a bugzilla on the alsa issue it causes.

Thanks very much Dean, I can sleep now

deano_ferrari · November 2, 2019, 9:32pm

kitman:

It seems that the version giving me grief
i+ | jack                    | package | 1.9.13-lp151.114.1      | x86_64 | multimedia:libs
was updated on 31 Oct, so it must have been updated yesterday or this morning without me taking any notice - how ignorant of me to say I have used this version “for a while”.

Yes, I noticed the time stamps of the files you shared.

So, I can go back and forth with testing versions of jack and if needs be lodge a bugzilla on the alsa issue it causes.

Thanks very much Dean, I can sleep now

Yes, reads like some progress now.