No sound from internal soundcard (Sound BlasterX AE-5 Plus)

Hello Everyone,

two weeks ago I started using Linux. My first distribution was Fedora 35.
Everything worked fine, but my internal soundcard did not. I began researching, and found out my soundcard should have support with Linux 5.11 kernel. I followed many forum posts that stated solutions to problems like mine, but even after installing many packages (through dnf) I never got it working.

I gave up on Fedora and wanted to try different distributions to check if it is working there. Besides Fedora I tried Pop_OS, Debian, QubesOS and MX Linux. Only MX Linux, even though it is using Linux Kernel 5.10, got my soundcard working. I just had to use alsamixer to change the output device of my soundcard to headphones instead of speakers.

All distributions I’ve used yet all named my soundcard "Sound Core3D [Sound Blaster Recon3D / Z-Series]. It is named like that on 5.4 kernel, on 5.10 kernel or on 5.14 kernel.

All people having problems with this card, were pointed to using a distribution with 5.11 kernel. But I just cannot get it working.
I saw that a new PipeWire update 0.3.40 is out. After installing it my soundcard disappeared from pavucontrol. After launching alsamixer and changing an option forth and back, the soundcard was back on pavucontrol but still no sound.

lspci:
05:00.0 Audio device: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] (rev 01)

I hope somebody can help me and others with this problem. Also I really don’t want to be using MX Linux.
If you need any information about my system I will be giving them to you as fast as I can. But I want to point out that this is a stock os problem.

Greetings

Edit (Some things I rembered after posting):
-I tried every jack-in of my soundcard
-In pavucontrol I can see that I should have sound, as the dB bar is jumping up and down as sound plays
-Fedora detects if headphones are plugged in or not in pavucontrol

Hello, welcome to the community! Please do take a few minutes to go over the introductory posts in #start-here when you have the time. They contain lots of useful information.

Could you check:
systemctl --user status "pipewire*"
and
systemctl --user status "wireplumber*"

if either of them isn’t running try
systemctl --user restart "thingthatisnotrunning"

2 Likes

Hi grumpey,

wireplumber was not running. I used the restart command and checked if it is running now, and it is.

I still have no sound. I forgot to mention that in pavucontrol I can see that the program detects my headphones being plugged it. When I pull them out it says unplugged and vice versa.

I will check the introductory posts.

Edit:
Okay I was a little bit too fast here, I’m sorry. I’ve looked again in my terminal, and with PipeWire everything seems fine. With wireplumber I get the following output, even after restarting:

● wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-11-23 19:54:25 CET; 16min ago
Main PID: 5289 (wireplumber)
Tasks: 4 (limit: 19092)
Memory: 5.9M
CPU: 700ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
└─5289 /usr/bin/wireplumber

Nov 23 19:54:25 fedora systemd[1551]: Started Multimedia Service Session Manager.
Nov 23 19:54:50 fedora wireplumber[5289]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply

Try pipewire-media-session
sudo dnf swap wireplumber pipewire-media-session

Thanks

1 Like

I thank you grumpey!

I swapped wireplumber with pipewire-media-session. No working sound.
I rebootet my system, looked into pavucontrol and couldn’t find my soundcard, like it was when I installed PipeWire 0.3.40.
I ran alsamixer, selected my soundcard and it shows up in pavucontrol again.

I ran systemctl --user status "pipewire*" again:

● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; vendor preset: disabled)
Active: active (running) since Tue 2021-11-23 21:33:05 CET; 7min ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 2392 (pipewire-pulse)
Tasks: 2 (limit: 19092)
Memory: 37.7M
CPU: 3.985s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
└─2392 /usr/bin/pipewire-pulse

Nov 23 21:33:05 fedora systemd[2005]: Started PipeWire PulseAudio.

● pipewire-media-session.service - PipeWire Media Session Manager
Loaded: loaded (/usr/lib/systemd/user/pipewire-media-session.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-11-23 21:33:05 CET; 7min ago
Main PID: 2391 (pipewire-media-)
Tasks: 2 (limit: 19092)
Memory: 9.4M
CPU: 1.614s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-media-session.service
└─2391 /usr/bin/pipewire-media-session

Nov 23 21:33:05 fedora systemd[2005]: Started PipeWire Media Session Manager.
Nov 23 21:33:31 fedora pipewire-media-session[2391]: spa.bluez5: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply

● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: disabled)
Active: active (running) since Tue 2021-11-23 21:33:05 CET; 7min ago
TriggeredBy: ● pipewire.socket
Main PID: 2389 (pipewire)
Tasks: 2 (limit: 19092)
Memory: 14.2M
CPU: 7.997s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─2389 /usr/bin/pipewire

Nov 23 21:33:05 fedora systemd[2005]: Started PipeWire Multimedia Service.

● pipewire-pulse.socket - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-11-23 21:33:04 CET; 7min ago
Triggers: ● pipewire-pulse.service
Listen: /run/user/1000/pulse/native (Stream)
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire-pulse.socket

Nov 23 21:33:04 fedora systemd[2005]: Listening on PipeWire PulseAudio.

● pipewire.socket - Multimedia System
Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-11-23 21:33:04 CET; 7min ago
Triggers: ● pipewire.service
Listen: /run/user/1000/pipewire-0 (Stream)
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire.socket

Nov 23 21:33:04 fedora systemd[2005]: Listening on Multimedia System.

Restarting Pipewire, I get all active (running), even pipewire-media-session:

● pipewire-media-session.service - PipeWire Media Session Manager
Loaded: loaded (/usr/lib/systemd/user/pipewire-media-session.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-11-23 21:46:44 CET; 7s ago
Main PID: 3555 (pipewire-media-)
Tasks: 2 (limit: 19092)
Memory: 4.2M
CPU: 387ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-media-session.service
└─3555 /usr/bin/pipewire-media-session

Sound is not fixed though. Going to restart now and edit then.

Edit after restart:

Sound is not working after restart. But pipewire-media-session was working before after a restart, now it is not anymore.
This is now the thing:
systemctl --user status "pipewire*" output:

Those are working:

pipewire-pulse.service
pipewire-media-session.service
pipewire service
pipewire-pulse.socket
pipewire.socket

Not working:

pipewire-media-session

Nov 23 22:14:10 fedora systemd[1599]: Started PipeWire Media Session Manager.
Nov 23 22:14:44 fedora pipewire-media-session[3901]: spa.bluez5: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply

I restard pipewire, and check pipewire status a few seconds after:
pipewire-pulse.service
pipewire-media-session.service
pipewire service
pipewire-pulse.socket
pipewire.socket
all working, but no sign of pipewire-media-session.

After a few seconds I check status of pipewire again, and pipewire-media-session gives me the NoReply error. It seems like it doesn’t start anymore even after restarting pipewire.

Edit:
Sound is still working fine on everything that is not this soundcard.

1 Like

pipewire-media-session.service is the systemd service that is running pipewire-media-session

Can you try on a new user please and thanks.

Edit you may also want to double check alsamixer and see what the volume is for that card.

1 Like

Same problem on new user. Maybe something interesting. If you want to see it, scroll down.

systemctl --user status "pipewire*"

● pipewire-pulse.socket - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; vend>
Active: active (running) since Tue 2021-11-23 22:43:26 CET; 3min 16s ago
Triggers: ● pipewire-pulse.service
Listen: /run/user/1001/pulse/native (Stream)
CGroup: /user.slice/user-1001.slice/user@1001.service/app.slice/pipewire-p>

Nov 23 22:43:26 fedora systemd[6492]: Listening on PipeWire PulseAudio.

● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; ve>
Active: active (running) since Tue 2021-11-23 22:43:28 CET; 3min 14s ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 7053 (pipewire-pulse)
Tasks: 2 (limit: 19092)
Memory: 7.6M
CPU: 1.284s
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewi>
└─7053 /usr/bin/pipewire-pulse

Nov 23 22:43:28 fedora systemd[6492]: Started PipeWire PulseAudio.

● pipewire-media-session.service - PipeWire Media Session Manager
Loaded: loaded (/usr/lib/systemd/user/pipewire-media-session.service; enab>
Active: active (running) since Tue 2021-11-23 22:43:28 CET; 3min 14s ago
Main PID: 7052 (pipewire-media-)
Tasks: 2 (limit: 19092)
Memory: 4.3M
CPU: 711ms
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewi>
└─7052 /usr/bin/pipewire-media-session

Nov 23 22:43:28 fedora systemd[6492]: Started PipeWire Media Session Manager.
● pipewire-pulse.socket - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; vend>
Active: active (running) since Tue 2021-11-23 22:43:26 CET; 3min 16s ago
Triggers: ● pipewire-pulse.service
Listen: /run/user/1001/pulse/native (Stream)
CGroup: /user.slice/user-1001.slice/user@1001.service/app.slice/pipewire-p>

Nov 23 22:43:26 fedora systemd[6492]: Listening on PipeWire PulseAudio.

● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; ve>
Active: active (running) since Tue 2021-11-23 22:43:28 CET; 3min 14s ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 7053 (pipewire-pulse)
Tasks: 2 (limit: 19092)
Memory: 7.6M
CPU: 1.284s
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewi>
└─7053 /usr/bin/pipewire-pulse

Nov 23 22:43:28 fedora systemd[6492]: Started PipeWire PulseAudio.

● pipewire-media-session.service - PipeWire Media Session Manager
Loaded: loaded (/usr/lib/systemd/user/pipewire-media-session.service; enab>
Active: active (running) since Tue 2021-11-23 22:43:28 CET; 3min 14s ago
Main PID: 7052 (pipewire-media-)
Tasks: 2 (limit: 19092)
Memory: 4.3M
CPU: 711ms
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewi>
└─7052 /usr/bin/pipewire-media-session

Nov 23 22:43:28 fedora systemd[6492]: Started PipeWire Media Session Manager.
Nov 23 22:44:02 fedora pipewire-media-session[7052]: spa.bluez5: GetManagedObje>

● pipewire.socket - Multimedia System
Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; vendor pre>
Active: active (running) since Tue 2021-11-23 22:43:26 CET; 3min 16s ago
Triggers: ● pipewire.service
Listen: /run/user/1001/pipewire-0 (Stream)
CGroup: /user.slice/user-1001.slice/user@1001.service/app.slice/pipewire.s>

Nov 23 22:43:26 fedora systemd[6492]: Listening on Multimedia System.

● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor p>
Active: active (running) since Tue 2021-11-23 22:43:28 CET; 3min 14s ago
TriggeredBy: ● pipewire.socket
Main PID: 7051 (pipewire)
Tasks: 2 (limit: 19092)
Memory: 6.6M
CPU: 3.556s
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewi>
└─7051 /usr/bin/pipewire

Nov 23 22:43:28 fedora systemd[6492]: Started PipeWire Multimedia Service.

systemctl --user restart "pipewire"
systemctl --user status "pipewire*"

● pipewire-pulse.socket - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; vend>
Active: active (running) since Tue 2021-11-23 22:43:26 CET; 5min ago
Triggers: ● pipewire-pulse.service
Listen: /run/user/1001/pulse/native (Stream)
CGroup: /user.slice/user-1001.slice/user@1001.service/app.slice/pipewire-p>

Nov 23 22:43:26 fedora systemd[6492]: Listening on PipeWire PulseAudio.

● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; ve>
Active: active (running) since Tue 2021-11-23 22:43:28 CET; 5min ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 7053 (pipewire-pulse)
Tasks: 2 (limit: 19092)
Memory: 4.1M
CPU: 2.224s
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewi>
└─7053 /usr/bin/pipewire-pulse

Nov 23 22:43:28 fedora systemd[6492]: Started PipeWire PulseAudio.

● pipewire-media-session.service - PipeWire Media Session Manager
Loaded: loaded (/usr/lib/systemd/user/pipewire-media-session.service; enab>
Active: active (running) since Tue 2021-11-23 22:48:29 CET; 24s ago
Main PID: 9035 (pipewire-media-)
Tasks: 2 (limit: 19092)
Memory: 4.2M
CPU: 544ms
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewi>
└─9035 /usr/bin/pipewire-media-session

Nov 23 22:48:29 fedora systemd[6492]: Started PipeWire Media Session Manager.

● pipewire.socket - Multimedia System
Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; vendor pre>
Active: active (running) since Tue 2021-11-23 22:43:26 CET; 5min ago
Triggers: ● pipewire.service
Listen: /run/user/1001/pipewire-0 (Stream)
CGroup: /user.slice/user-1001.slice/user@1001.service/app.slice/pipewire.s>

Nov 23 22:43:26 fedora systemd[6492]: Listening on Multimedia System.

● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor p>
Active: active (running) since Tue 2021-11-23 22:48:29 CET; 24s ago
TriggeredBy: ● pipewire.socket
Main PID: 9031 (pipewire)
Tasks: 2 (limit: 19092)
Memory: 3.8M
CPU: 61ms
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewi>
└─9031 /usr/bin/pipewire

Nov 23 22:48:29 fedora systemd[6492]: Started PipeWire Multimedia Service.

systemctl --user status "pipewire*" (Wait 10-15 seconds after restart)

systemctl --user status “pipewire*”
● pipewire-pulse.socket - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; vend>
Active: active (running) since Tue 2021-11-23 22:43:26 CET; 6min ago
Triggers: ● pipewire-pulse.service
Listen: /run/user/1001/pulse/native (Stream)
CGroup: /user.slice/user-1001.slice/user@1001.service/app.slice/pipewire-p>

Nov 23 22:43:26 fedora systemd[6492]: Listening on PipeWire PulseAudio.

● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; ve>
Active: active (running) since Tue 2021-11-23 22:43:28 CET; 6min ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 7053 (pipewire-pulse)
Tasks: 2 (limit: 19092)
Memory: 4.1M
CPU: 2.224s
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewi>
└─7053 /usr/bin/pipewire-pulse

Nov 23 22:43:28 fedora systemd[6492]: Started PipeWire PulseAudio.

● pipewire-media-session.service - PipeWire Media Session Manager
Loaded: loaded (/usr/lib/systemd/user/pipewire-media-session.service; enab>
Active: active (running) since Tue 2021-11-23 22:48:29 CET; 1min 12s ago
Main PID: 9035 (pipewire-media-)
Tasks: 2 (limit: 19092)
Memory: 4.2M
CPU: 544ms
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewi>
└─9035 /usr/bin/pipewire-media-session

Nov 23 22:48:29 fedora systemd[6492]: Started PipeWire Media Session Manager.
Nov 23 22:48:55 fedora pipewire-media-session[9035]: spa.bluez5: GetManagedObje>

● pipewire.socket - Multimedia System
Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; vendor pre>
Active: active (running) since Tue 2021-11-23 22:43:26 CET; 6min ago
Triggers: ● pipewire.service
Listen: /run/user/1001/pipewire-0 (Stream)
CGroup: /user.slice/user-1001.slice/user@1001.service/app.slice/pipewire.s>

Nov 23 22:43:26 fedora systemd[6492]: Listening on Multimedia System.

● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor p>
Active: active (running) since Tue 2021-11-23 22:48:29 CET; 1min 12s ago
TriggeredBy: ● pipewire.socket
Main PID: 9031 (pipewire)
Tasks: 2 (limit: 19092)
Memory: 3.8M
CPU: 61ms
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewi>
└─9031 /usr/bin/pipewire

Nov 23 22:48:29 fedora systemd[6492]: Started PipeWire Multimedia Service.

After a bit of editing my post, I saw that the copy paste from my terminal is cut off, so I wanted to type in the commands again and paste again. Then I saw this big red chunk in the terminal:

systemctl --user status "pipewire*"

● pipewire-pulse.socket - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-11-23 22:43:26 CET; 24min ago
Triggers: ● pipewire-pulse.service
Listen: /run/user/1001/pulse/native (Stream)
CGroup: /user.slice/user-1001.slice/user@1001.service/app.slice/pipewire-pulse.socket

Nov 23 22:43:26 fedora systemd[6492]: Listening on PipeWire PulseAudio.

● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; vendor preset: disabled)
Active: active (running) since Tue 2021-11-23 22:43:28 CET; 24min ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 7053 (pipewire-pulse)
Tasks: 2 (limit: 19092)
Memory: 13.9M
CPU: 4.696s
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewire-pulse.service
└─7053 /usr/bin/pipewire-pulse

Nov 23 22:43:28 fedora systemd[6492]: Started PipeWire PulseAudio.

● pipewire-media-session.service - PipeWire Media Session Manager
Loaded: loaded (/usr/lib/systemd/user/pipewire-media-session.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-11-23 22:50:39 CET; 17min ago
Main PID: 9457 (pipewire-media-)
Tasks: 2 (limit: 19092)
Memory: 4.5M
CPU: 2.826s
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewire-media-session.service
└─9457 /usr/bin/pipewire-media-session

Nov 23 22:50:39 fedora systemd[6492]: Started PipeWire Media Session Manager.
Nov 23 22:51:05 fedora pipewire-media-session[9457]: spa.bluez5: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply
Nov 23 22:51:49 fedora pipewire-media-session[9457]: spa.loop: 0x55f7bb201110: failed to read timer fd 32: Die Ressource ist zur Zeit nicht verfügbar
Nov 23 22:52:06 fedora pipewire-media-session[9457]: spa.bluez5: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply
Nov 23 22:54:14 fedora pipewire-media-session[9457]: spa.bluez5: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply
Nov 23 22:56:45 fedora pipewire-media-session[9457]: spa.bluez5: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply

● pipewire.socket - Multimedia System
Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-11-23 22:43:26 CET; 24min ago
Triggers: ● pipewire.service
Listen: /run/user/1001/pipewire-0 (Stream)
CGroup: /user.slice/user-1001.slice/user@1001.service/app.slice/pipewire.socket

Nov 23 22:43:26 fedora systemd[6492]: Listening on Multimedia System.

● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: disabled)
Active: active (running) since Tue 2021-11-23 22:50:39 CET; 17min ago
TriggeredBy: ● pipewire.socket
Main PID: 9452 (pipewire)
Tasks: 2 (limit: 19092)
Memory: 5.2M
CPU: 4.622s
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice/pipewire.service
└─9452 /usr/bin/pipewire

Nov 23 22:50:39 fedora systemd[6492]: Started PipeWire Multimedia Service.

The bolt text is all in red, except for

spa.loop: 0x55f7bb201110: failed to read timer fd 32: Die Ressource ist zur Zeit nicht verfügbar

which is in yellow. After fd 32: is german and says “This resource is currently not available”


systemctl --user status session.slice

and see if pulseaudio is still running

ref: Common F35 bugs - Fedora Project Wiki

you could also switch back to pulse:
sudo dnf swap --allowerasing pipewire-pulseaudio pulseaudio

If you switch back be sure and remove pipewire and wireplumber.

1 Like

systemctl --user status session.slice

● session.slice - User Core Session Slice
Loaded: loaded (/usr/lib/systemd/user/session.slice; static)
Active: active since Tue 2021-11-23 22:43:28 CET; 43min ago
Docs: man:systemd.special(7)
Tasks: 6
Memory: 23.9M
CPU: 21.774s
CGroup: /user.slice/user-1001.slice/user@1001.service/session.slice
├─pipewire-media-session.service
│ └─9457 /usr/bin/pipewire-media-session
├─pipewire-pulse.service
│ └─7053 /usr/bin/pipewire-pulse
└─pipewire.service
└─9452 /usr/bin/pipewire

seems right

Edit:

Swapped pulseaudio for pipewire-pulseaudio, and uninstalled pipewire. Wireplumber was already uninstalled. No sound from soundcard. Even after restarting.

Is it normal that I cannot open alsamixer anymore? It says when I want to open it “Error with opening the mixer-device: This PC is not active” (Translated from german, original output was: Fehler beim Öffen des Mixer-Gerätes: Der Rechner ist nicht aktiv)

If you don’t have another idea, I could boot Fedora via Live-USB and give you some information, or even liveboot MX Linux and give you some information. But only if you want to.

does it show up in aplay -l

you may need to do alsamixer -c <card_number>

1 Like

aplay -l (extract)

Karte 2: Creative [HDA Creative], Gerät 0: CA0132 Analog [CA0132 Analog]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 2: Creative [HDA Creative], Gerät 1: CA0132 Digital [CA0132 Digital]
Sub-Geräte: 1/1

yes I can open alsamixer the alsamixer -c <card_number> way.

I will try those two live os’s now.

Are you certain that this device driver is in the kernel >5.11 ? All the post I’m reading, some one wrote a driver, patched the kernel & recompiled. The device seems to be very buggy otherwise on Linux.

@hamrheadcorvette
I am sadly not very experienced in this whole compile, commit, submit thing or whatever ^^
But from what I remember reading 2 weeks ago it is in Kernel 5.11 and higher.
When I read this post I also get this impression:

and this one:

Quote from the manjaro forum: “I really dont understand your problems. As stated above, the card works fine from kernel 5.11+. The only problem is the stereo output instead of surround.”

Back to topic:

MX Linux doesn’t have pipewire or wireplumber or gstream or jack installed.
It seems like it runs PulseAudio 14.2 and Alsamixer 1.2.4.
Will try Fedora 35 live now, and then Fedora 34 live.

Edit: It would be very nice of you if you could tell me what also to check on MX Linux. What is not installed and what is installed so I can recreate the audio programs as good as I can in Fedora 35. I don’t really know what to look for.

Edit2: No soundcard sound on Fedora 34 and Fedora 35 live boots. Both use pipewire. Will now try to construct same installed audio programs with same version as in MX Linux on Fedora 35.

Edit3: Will update tomorrow, and tell you if I had success.

inxi -Axx

and compare them.

I’m at a bit of a loss here.

2 Likes

inxi -Axx extracts:

On Fedora 35:

Device-3: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
driver: snd_hda_intel v: kernel bus-id: 05:00.0 chip-id: 1102:0012
Sound Server-1: ALSA v: k5.14.18-300.fc35.x86_64

On MX Linux 21:

Device-3: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
driver: snd_hda_intel v: kernel bus-id: 05:00.0 chip-id: 1102:0012
Sound Server: ALSA v: 5.10.0-9-amd64

Only difference seems to be that on Fedora it is called Sound Server**-1** and it is another version

I tried hours now and searched for many solutions but it is just so time consuming.
After installing many packages I came to the point to compile PulseAudio 14.2 with meson, but there seems to be a problem with newer versions of meson.
This thread regression on -current with pulseaudio told me to use meson 0.57.2 to build PulseAudio 14.2.

Also reference: Enable Disabled Auto python 3.9 · Issue #8749 · mesonbuild/meson · GitHub

I just can’t get 0.57.2 installed. Using pip install --user meson , and trying latest version of meson also gave me an error.
The error is:

FAILED: src/modules/module-echo-cancel.so.p/echo-cancel_adrian-aec.c.o

Is this the right thread to ask or should I open a new one?
I could probably do it on my own, but with help it probably would go way faster. Also even if I get PulseAudio 14.2 installed, there seem to be so many configurations to make I don’t know how long it will take and if it ever will work.
I think this could be a solution to many. I saw some threads having audio problems. But I don’t really know.

Maybe try the LTS kernel COPR?

Thanks

It is not a different ALSA version.
It is a different kernel, thus possibly a different driver module. F35 is using 5.14.18 and MX is using 5.10.0-9. I suspect that is the real difference in what works and what does not.

Fedora uses pipewire (and f35 adds wireplumber) where I think MX is still using pulseaudio.

But it seems neither work, and this driver has been known to be buggy. >5.11 is suppose to have the reversed engineered driver that can only output Stereo and nothing else.