Re: Audio not working after updates F42

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 14/5/25 00:15, Frederic Muller wrote:
On 13/05/2025 18:55, George N. White III wrote:
On Tue, May 13, 2025 at 6:42 AM Frederic Muller <fred@xxxxxxxx> wrote:

    Hi!

    I installed F42 yesterday and the sound was working at first. Now that
    I've copied my old files and updated everything I have no sound. How can
    I figure out what's going on and eventually fix it (that'd be nice).


When reporting problems, you should provide enough detail to allow others with
similar hardware to reproduce the issue (e.g., output from "inxi -Fzxx".

Sound is often enabled before the linux kernel is loaded, so can be affected
by changes to UEFI/BIOS as well as user configuration settings.  Some updates
do introduce bugs.

Try creating another user login. If sound works there, your issue is probably some
setting in ~/.config files.

Using your own login, you may find helpful details using journalctl.

Sorry about that. I just booted from the USB live disk and there is no sound as well..

The driver is alsa-firmware.noarch 1.2.4-14.fc42 fedora and

lspci -k | grep -i audio
00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)
     Kernel driver in use: sof-audio-pci-intel-tgl

systemctl --user status pipewire
● pipewire.service - PipeWire Multimedia Service
      Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: >
     Drop-In: /usr/lib/systemd/user/pipewire.service.d
              └─00-uresourced.conf
              /usr/lib/systemd/user/service.d
              └─10-timeout-abort.conf

      Active: active (running)

and alsamixer sees the card very well.

When this happens to me I used "pulse Audio Volume Control" (pavucontrol) to confirm the correct Configuration and Output Device is set
and the volume is reasonable.

Eyal

Now there was a firmware update today as well for that X1 Carbon. Basically you're saying most likely this is the culprit. I'll try to check in the bios setup if there is anything but from the above Fedora is behaving like everything is working fine, which leads me to believe in a firmware bug then.

Thank you for the answers.

Fred

--
Eyal at Home (fedora@xxxxxxxxxxxxxx)
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux