From: Pierre Neidhardt <ambrevar@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: pcspkr only loaded after waking up from sleep
Date: Wed, 18 Apr 2018 14:00:36 +0530 [thread overview]
Message-ID: <87604o6hn7.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
My laptop only rings the error bell (the PC speaker) after waking up
from sleep. It does not after a fresh boot. Or maybe the issue happens
at random.
It seems that pcspkr fails to register properly on boot:
--8<---------------cut here---------------start------------->8---
> dmesg | grep pcspkr
[ 2.109740] input: PC Speaker as /devices/platform/pcspkr/input/input5
[ 2.127371] Error: Driver 'pcspkr' is already registered, aborting...
[ 2.281487] Error: Driver 'pcspkr' is already registered, aborting...
...
[19213.561915] Modules linked in: msr [...] pcspkr [...]
--8<---------------cut here---------------end--------------->8---
19213 is after waking up from sleep, the modules get re-linked I
suppose. It works from then on.
Anyways, I'd like to turn it off for good. Is the following the right
way to go?
(kernel-arguments '("modprobe.blacklist=pcspkr"))
--
Pierre Neidhardt
Anti-trust laws should be approached with exactly that attitude.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2018-04-18 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 8:30 Pierre Neidhardt [this message]
2018-04-18 16:47 ` pcspkr only loaded after waking up from sleep Alex Kost
2018-04-18 18:24 ` Pierre Neidhardt
2018-04-19 19:33 ` Alex Kost
2018-04-20 10:38 ` Pierre Neidhardt
2018-04-21 19:31 ` Chris Marusich
2018-04-22 6:07 ` Pierre Neidhardt
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=87604o6hn7.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
/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).