10:19 a.m.
Dell Precision M6800 worked fine for a year. Some recent change has
caused the sound cards to disappear.
Hitting the volume control buttons on my (Logitech K350 or laptop
built-in) keyboard or digging through the settings of my Gnome
desktop for Sound shows that "Dummy Output" is my only option. While
its opinion of me isn't wrong, I could use some help getting this
working. It had been working well for years, upgraded in place to
Fedora 35. It was working after the big dnf system-upgrade, but sound
disappeared after a later update.
Internal laptop speakers make no noise, plugging headset into the
headset jack shows no dialog for "you just plugged something in" nor
makes sound.
Basic troubleshooting pointers on what to search for would be appreciated.
Machine: Dell Precision M6800: i7, 16Gb RAM, dual 1TB 5400rpm hdds,
intel video and AMD FirePro M6100 graphics.
Current kernel:
Linux jupiter.in.tedroche.com 5.19.4-100.fc35.x86_64 #1 SMP
PREEMPT_DYNAMIC Thu Aug 25 17:41:09 UTC 2022 x86_64 x86_64 x86_64
GNU/Linux
lspci -v shows:
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor HD Audio Controller (rev 06)
Subsystem: Dell Device 05cd
Flags: bus master, fast devsel, latency 0, IRQ 41
Memory at f7d34000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset
High Definition Audio Controller (rev 04)
Subsystem: Dell Device 05cd
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at f7d30000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
12:19 a.m.
New subject: "Dummy output" instead of sound card options, was working, now
gone.
On Sat, 3 Sep 2022 11:19:27 -0400
Ted Roche <tedroche(a)gmail.com> wrote:
Dell Precision M6800 worked fine for a year. Some recent change has
caused the sound cards to disappear.
Hitting the volume control buttons on my (Logitech K350 or laptop
built-in) keyboard or digging through the settings of my Gnome
desktop for Sound shows that "Dummy Output" is my only option. While
its opinion of me isn't wrong, I could use some help getting this
working. It had been working well for years, upgraded in place to
Fedora 35. It was working after the big dnf system-upgrade, but sound
disappeared after a later update.
Internal laptop speakers make no noise, plugging headset into the
headset jack shows no dialog for "you just plugged something in" nor
makes sound.
Basic troubleshooting pointers on what to search for would be
appreciated.
aplay -l
should show any devices that alsa recognizes. If alsa doesn't
recognize a device, you won't be able to use it. If alsa knows about
the device, I would then use pavucontrol to activate it by setting it
as default.
I think that f35 was still using pulseaudio as the default sound
controller on top of alsa, and that pipewire didn't become the default
until f36. If both are installed, it can lead to issues with sound as
they compete for the hardware. Pick one, and remove the other.
Machine: Dell Precision M6800: i7, 16Gb RAM, dual 1TB 5400rpm hdds,
intel video and AMD FirePro M6100 graphics.
Current kernel:
Linux jupiter.in.tedroche.com 5.19.4-100.fc35.x86_64 #1 SMP
PREEMPT_DYNAMIC Thu Aug 25 17:41:09 UTC 2022 x86_64 x86_64 x86_64
GNU/Linux
lspci -v shows:
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor HD Audio Controller (rev 06)
Subsystem: Dell Device 05cd
Flags: bus master, fast devsel, latency 0, IRQ 41
Memory at f7d34000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [70] Express Root Complex Integrated Endpoint,
MSI 00 Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset
High Definition Audio Controller (rev 04)
Subsystem: Dell Device 05cd
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at f7d30000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint,
MSI 00 Capabilities: [100] Virtual Channel
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
I think that this device should be the default. Because they are both
hda-intel using snd_hda_intel, I wonder if their recognition during
boot hasn't changed lately, and your default is now the first instead
of the second. pavucontrol can fix this, but you can also set up a
sound configuration file assigning positions to the devices, though
that might not work for the built in audio on the CPU.
It is possible that the sound device has developed hardware issues. I
have had a sound device fail, but usually it won't be recognized as
yours is when that happens.
1:44 p.m.
On Sun, Sep 4, 2022 at 1:19 AM stan via users
<users(a)lists.fedoraproject.org> wrote:
On Sat, 3 Sep 2022 11:19:27 -0400
Ted Roche <tedroche(a)gmail.com> wrote:
>
> Basic troubleshooting pointers on what to search for would be
> appreciated.
aplay -l
should show any devices that alsa recognizes. If alsa doesn't
recognize a device, you won't be able to use it. If alsa knows about
the device, I would then use pavucontrol to activate it by setting it
as default.
aplay -l only seems to find HDMI devices:
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: HDMI_1 [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: HDMI_1 [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: HDMI_1 [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: HDMI_1 [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: HDMI_1 [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: HDMI_1 [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0: subdevice #0
attempting to start pavucontrol pops up a window with the message
"Establishing connection to PulseAudo. Please wait..." and nothing
happens.
12:31 p.m.
New subject: "Dummy output" instead of sound card options, was working, now
gone.
On Sun, 4 Sep 2022 14:44:11 -0400
Ted Roche <tedroche(a)gmail.com> wrote:
On Sun, Sep 4, 2022 at 1:19 AM stan via users
<users(a)lists.fedoraproject.org> wrote:
>
> On Sat, 3 Sep 2022 11:19:27 -0400
> Ted Roche <tedroche(a)gmail.com> wrote:
> >
> > Basic troubleshooting pointers on what to search for would be
> > appreciated.
>
> aplay -l
> should show any devices that alsa recognizes. If alsa doesn't
> recognize a device, you won't be able to use it. If alsa knows
> about the device, I would then use pavucontrol to activate it by
> setting it as default.
aplay -l only seems to find HDMI devices:
I think that is your problem. If alsa doesn't recognize the device,
when it used to, then there is probably a hardware error. To be sure,
you should check when alsa-lib was installed,
rpm -qi alsa-lib
If that was around the time your device stopped working, it could be a
regression in the library. They do happen, but it isn't common. You
can try a downgrade to an earlier alsa-lib by downloading the packages
you have installed from here,
https://koji.fedoraproject.org/koji/packageinfo?packageID=410
and install them with
dnf -C downgrade [list of binary rpms]
in the directory to where you downloaded them.
If it is a discrete sound device, you could try reseating it, in case
it is no longer making good contact. Do you have another sound device
you can install as a check?
If you run
journalctl -b0
to look at the last boot, what does it show for sound device
initialization? Is there any kind of error when it tries to activate
the device that is no longer working?
5:04 p.m.
On 5 Sep 2022, at 18:32, stan via users
<users(a)lists.fedoraproject.org> wrote:
On Sun, 4 Sep 2022 14:44:11 -0400
Ted Roche <tedroche(a)gmail.com> wrote:
>> On Sun, Sep 4, 2022 at 1:19 AM stan via users
>> <users(a)lists.fedoraproject.org> wrote:
>>
>> On Sat, 3 Sep 2022 11:19:27 -0400
>> Ted Roche <tedroche(a)gmail.com> wrote:
>>>
>>> Basic troubleshooting pointers on what to search for would be
>>> appreciated.
>>
>> aplay -l
>> should show any devices that alsa recognizes. If alsa doesn't
>> recognize a device, you won't be able to use it. If alsa knows
>> about the device, I would then use pavucontrol to activate it by
>> setting it as default.
> aplay -l only seems to find HDMI devices:
I think that is your problem. If alsa doesn't recognize the device,
when it used to, then there is probably a hardware error. To be sure,
you should check when alsa-lib was installed,
rpm -qi alsa-lib
I would expect that the hardware support is in the kernel.
I thought alsa-lib did not have hardware specific code.
Maybe try booting an older kernel to see the device comes back?
Barry
If that was around the time your device stopped working, it could be
a
regression in the library. They do happen, but it isn't common. You
can try a downgrade to an earlier alsa-lib by downloading the packages
you have installed from here,
https://koji.fedoraproject.org/koji/packageinfo?packageID=410
and install them with
dnf -C downgrade [list of binary rpms]
in the directory to where you downloaded them.
If it is a discrete sound device, you could try reseating it, in case
it is no longer making good contact. Do you have another sound device
you can install as a check?
If you run
journalctl -b0
to look at the last boot, what does it show for sound device
initialization? Is there any kind of error when it tries to activate
the device that is no longer working?
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
5:37 p.m.
New subject: "Dummy output" instead of sound card options, was working, now
gone.
On 9/5/22 5:04 PM, Barry wrote:
I would expect that the hardware support is in the kernel.
I thought alsa-lib did not have hardware specific code.
Maybe try booting an older kernel to see the device comes back?
If booting into an older kernel doesn't help...
When hardware seems to disappear, I'd suggest doing a cold boot: shut
down, wait for power off, and turn power back on. Every so often I see
hardware go into a weird state that doesn't get reinitialized with a
(warm) reboot but does with a cold boot.
Dave
635
days inactive
637
days old
5 comments
4 participants
participants (4)
-
Barry -
Dave Ulrick -
stan -
Ted Roche