all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: sirgazil <sirgazil@zoho.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Guix System 1.0: No audio
Date: Sun, 5 May 2019 14:07:48 +0200	[thread overview]
Message-ID: <20190505120748.bnu6mhrc7nspblmf@pelzflorian.localdomain> (raw)
In-Reply-To: <16a87d6bf80.d65ddb9c37050.8615000726088250703@zoho.com>

On Sun, May 05, 2019 at 06:52:39AM -0500, sirgazil wrote:
> Florian, for some reason, the speakers worked today. I'm not sure if running alsamixer yesterday after your instructions had anything to do with it or booting without the headphones plugged. Those are the only different things (related to sound) that I've done before starting the machine today. GNOME even displays some information when I plug the headphones. It didn't do this before.
>

On my father’s PC booting with or without audio 3.5mm plug headphones
makes a difference.


> One thing I noticed when booting is an error that says something like this:
> 
>    Error: "pcspkr" is already registered, aborting.
> 

I see this too.

> I wonder if that is related. Although the speakers worked anyways.
> 
> Thank you, Florian.
> 

I am happy to help (and happy that Linux-libre is unrelated). :)

Regards,
Florian

  reply	other threads:[~2019-05-05 12:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-04 22:00 Guix System 1.0: No audio sirgazil
2019-05-04 22:29 ` pelzflorian (Florian Pelz)
2019-05-04 23:24   ` sirgazil
2019-05-05  6:33     ` pelzflorian (Florian Pelz)
2019-05-05 11:52       ` sirgazil
2019-05-05 12:07         ` pelzflorian (Florian Pelz) [this message]
2019-05-05 22:25           ` Tobias Geerinckx-Rice
2019-05-06 17:38           ` sirgazil
2019-05-05 21:26 ` Mark H Weaver
2019-05-05 22:09   ` sirgazil

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

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

  git send-email \
    --in-reply-to=20190505120748.bnu6mhrc7nspblmf@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=help-guix@gnu.org \
    --cc=sirgazil@zoho.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.