unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauermann@kolabnow.com>
To: Paxton Evans <paxton@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: No sound on laptop after linux-libre 5.15
Date: Sat, 05 Feb 2022 03:32:00 -0300	[thread overview]
Message-ID: <87sfsxakjn.fsf@kolabnow.com> (raw)
In-Reply-To: <e9f309cb3921151003fc0bda9563cf6a@riseup.net>


Hello Paxton,

Paxton Evans <paxton@riseup.net> writes:

> On 2021-12-08 23:05, Leo Famulari wrote:
>> On Wed, Dec 08, 2021 at 11:34:24PM -0300, Thiago Jung Bauermann wrote:
>>> Em quarta-feira, 8 de dezembro de 2021, às 01:55:13 -03, Paxton Evans
>>> escreveu:
>>> > Rolling back to linux-libre 5.14.21 (guix
>>> > ea7233befb9570cce47e5ca71725b285a580cd22) totally fixes this issue.
>>> >
>>> > Troubleshooting sound issues on GNU/Linux is such a nightmare that I'm
>>> > hoping this list can help me, as I don't really know much about how
>>> > sound on our favorite OS really works, and don't have enough information
>>> > to file a bug. Can anyone give me pointers on where to start looking?
>>> > dmesg on 5.15.6 didn't seem to report anything strange.
>> 
>> Thanks for your report. Everything Thiago said is important, and it
>> would also help if you told us what you had tried to do. That is, what
>> are you using to make sound?
>> 
>> My basic sound test is to use mpg123 to play an MP3 file. You can use
>> the --output option to choose which output to play through, to be sure.
>> And you can use --list-modules to see what's available.
>> 
>> On Guix System, we aim to make applications use Pulseaudio by default,
>> so you can use `mpg123 --output pulse file.mp3` to test that. You can
>> also use `mpg123 --output alsa file.mp3` if you'd rather test ALSA.
>> 
>> Unfortunately I currently cannot test sound on Guix System with
>> linux-libre. However, it does work for me on a computer using Guix
>> System with a custom kernel.
>
> In case anyone finds this later, I wanted to update and say that this
> was indeed a kernel bug, and fixed in Linux commit
> 7f6e3cbbd60044102373f5a7f86d5f4e89a99747 (included in 5.15.17 in both
> vanilla and linux-libre).

Thank you for the update! It’s always nice to avoid https://xkcd.com/979/

-- 
Thanks
Thiago


      reply	other threads:[~2022-02-05  6:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08  4:55 No sound on laptop after linux-libre 5.15 Paxton Evans
2021-12-09  2:34 ` Thiago Jung Bauermann
2021-12-09  4:05   ` Leo Famulari
2022-02-04 22:04     ` Paxton Evans
2022-02-05  6:32       ` Thiago Jung Bauermann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfsxakjn.fsf@kolabnow.com \
    --to=bauermann@kolabnow.com \
    --cc=help-guix@gnu.org \
    --cc=paxton@riseup.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).