From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Sound on Chromebook
Date: Mon, 2 Sep 2024 00:24:29 -0500 [thread overview]
Message-ID: <39d69da7-f8f7-3cbc-f64e-1f29192865a3@gmail.com> (raw)
In-Reply-To: <0066F7EB-5B6F-4432-AA70-30DC8BD7AA4D@gmail.com>
Joe wrote:
> Hi,
>
> Has anyone got sound working on a Chromebook say 2020-Newer ?
>
> Could you please tell me the steps.
>
> Followed this with no luck.
> <https://forums.gentoo.org/viewtopic-t-1166746-highlight-.html>
>
> Thanks
>
> Joe
>
>
I use Firefox and Seamonkey myself but if you use KDE and the new
pipewire, make sure you check all volume levels. Linux, every distro
I've ever used, has the volume muted by default in every sound control
program. Why they don't default to say 30% or something I don't know.
At least you know the drivers and hardware is working with that setting
and it won't blow up your speakers like it did on Back to the Future in
the beginning of the movie. Back to pipewire, each app has its own
setting. You could have other apps turned up to normal and Chrome still
muted or set real low. Don't forget to check both Devices and
Application tabs in pipewire. Also, check alsa, Kmix and others as
well. If any one of them is muted or set to a real low setting, it will
make it look like no sound. Oh, I use pipewire as my main volume
control. I set all others to 100% and then use only pipewire from then
on. That way I only have one place to check.
Now that you mention something Google related, I want to switch email
providers again. :/
Dale
:-) :-)
next prev parent reply other threads:[~2024-09-02 5:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 2:35 [gentoo-user] Sound on Chromebook Joe
2024-09-02 5:24 ` Dale [this message]
2024-09-02 6:33 ` Joe
2024-09-02 18:43 ` Dale
2024-09-03 21:13 ` Joe
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=39d69da7-f8f7-3cbc-f64e-1f29192865a3@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.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