New Pinebook Pro - no sound
#1
Sad 
Hello all,

Just received my PBP yesterday. I typically use Ubuntu, so the desktop will take a little getting used to. However, I created a new sudo user acct, which does not have sound playback at all. The default "rock" user does have sound playback.

I searched the forums and found a post about the alsamixer / selecting the correct sound device, but this did not work. How do I get sound playback for accounts other than the default "rock" user?

Thanks!
#2
(01-15-2020, 11:05 AM)vve1505 Wrote: Hello all,

Just received my PBP yesterday. I typically use Ubuntu, so the desktop will take a little getting used to. However, I created a new sudo user acct, which does not have sound playback at all. The default "rock" user does have sound playback.


Welcome to Poettering's world

https://www.freedesktop.org/wiki/Softwar...ystemWide/
#3
(01-15-2020, 11:38 AM)Der Geist der Maschine Wrote:
(01-15-2020, 11:05 AM)vve1505 Wrote: Hello all,

Just received my PBP yesterday. I typically use Ubuntu, so the desktop will take a little getting used to. However, I created a new sudo user acct, which does not have sound playback at all. The default "rock" user does have sound playback.


Welcome to Poettering's world

https://www.freedesktop.org/wiki/Softwar...ystemWide/
 
      Not sure I follow those instructions,

     So ?  is this what we put into terminal  ?
Code:
sudo systemctl --global disable pulseaudio.service pulseaudio.socket
      LINUX = CHOICES
         **BCnAZ**
               Idea
   Donate to $upport
your favorite OS Team
#4
You might find it easier to simply rename the rock user.

https://wiki.pine64.org/index.php/Pinebo...ame.2C_etc...
#5
(01-16-2020, 05:42 AM)ioo Wrote: You might find it easier to simply rename the rock user.

https://wiki.pine64.org/index.php/Pinebo...ame.2C_etc...
 
    Actually,  should I do both ?

   one to correct the sound,    the second for the user account ?
      LINUX = CHOICES
         **BCnAZ**
               Idea
   Donate to $upport
your favorite OS Team
#6
(01-16-2020, 06:37 AM)bcnaz Wrote:
(01-16-2020, 05:42 AM)ioo Wrote: You might find it easier to simply rename the rock user.

https://wiki.pine64.org/index.php/Pinebo...ame.2C_etc...
 
    Actually,  should I do both ?

   one to correct the sound,    the second for the user account ?

My wild guess is that the newly created user is missing some groups privileges as the user rock.

Here is what I found from my pbp:

Code:
rock@Debian-Desktop:~$ id rock
uid=1000(rock) gid=1000(rock) groups=1000(rock),4(adm),27(sudo),29(audio),44(video),46(plugdev),106(input),111(ssh)

rock@Debian-Desktop:~$ cat /etc/group | grep rock
adm:x:4:rock
sudo:x:27:rock
audio:x:29:rock,pulse
video:x:44:rock
plugdev:x:46:rock
input:x:106:rock
ssh:x:111:rock
rock:x:1000:

So in order to have the same user profile as the user rock, one has to add those groups as secondary group to the newly created user.

For example, if I created a new user as newuser, I have to do the following:

Code:
$ sudo usermod -a -G adm, sudo, audio, video, plugdev, input, ssh newuser


or add them one by one

Code:
$ sudo groupmod -a -G adm newuser
$ sudo groupmod -a -G sudo newuser
$ sudo groupmod -a -G audio newuser
$ sudo groupmod -a -G video newuser
$ sudo groupmod -a -G plugdev newuser
$ sudo groupmod -a -G input newuser
$ sudo groupmod -a -G ssh newuser

or some people would like to use the adduser command instead

Code:
$ sudo adduser newuser adm
$ sudo adduser newuser sudo
$ sudo adduser newuser audio
$ sudo adduser newuser video
$ sudo adduser newuser plugdev
$ sudo adduser newuser input
$ sudo adduser newuser ssh

Chip
#7
I was having the same issue, despite being in The sound group.

I tried bogamul's suggestion here: https://askubuntu.com/questions/1086658/...u-18-04lts

And it seemed to solve my audio problems.
#8
(01-16-2020, 04:18 PM)chip ling Wrote:
(01-16-2020, 06:37 AM)bcnaz Wrote:
(01-16-2020, 05:42 AM)ioo Wrote: You might find it easier to simply rename the rock user.

https://wiki.pine64.org/index.php/Pinebo...ame.2C_etc...
 
    Actually,  should I do both ?

   one to correct the sound,    the second for the user account ?

My wild guess is that the newly created user is missing some groups privileges as the user rock.

Here is what I found from my pbp:

Code:
rock@Debian-Desktop:~$ id rock
uid=1000(rock) gid=1000(rock) groups=1000(rock),4(adm),27(sudo),29(audio),44(video),46(plugdev),106(input),111(ssh)

rock@Debian-Desktop:~$ cat /etc/group | grep rock
adm:x:4:rock
sudo:x:27:rock
audio:x:29:rock,pulse
video:x:44:rock
plugdev:x:46:rock
input:x:106:rock
ssh:x:111:rock
rock:x:1000:

So in order to have the same user profile as the user rock, one has to add those groups as secondary group to the newly created user.

For example, if I created a new user as newuser, I have to do the following:

Code:
$ sudo usermod -a -G adm, sudo, audio, video, plugdev, input, ssh newuser


or add them one by one

Code:
$ sudo groupmod -a -G adm newuser
$ sudo groupmod -a -G sudo newuser
$ sudo groupmod -a -G audio newuser
$ sudo groupmod -a -G video newuser
$ sudo groupmod -a -G plugdev newuser
$ sudo groupmod -a -G input newuser
$ sudo groupmod -a -G ssh newuser

or some people would like to use the adduser command instead

Code:
$ sudo adduser newuser adm
$ sudo adduser newuser sudo
$ sudo adduser newuser audio
$ sudo adduser newuser video
$ sudo adduser newuser plugdev
$ sudo adduser newuser input
$ sudo adduser newuser ssh

Chip

So my question is, why can't the system just have sound for all users. I'm going to read the SystemWide link now, but this whole thing seems kind of ridiculous to me.
#9
 
  I am not sure about following all these different paths...

    I only see a Few posts where the users are running the OEM Debian/Mate and have the "NO SOUND"  problem.

   If I had changed the OS or made some major changes,  then maybe Making major changes to the OS could make sense.

    BUT,    I feel like I have a brand new car,     and I am being told   I MUST rebuild the engine. ?

   ** ***   If every new Pinebook Pro had the "NO SOUND"  problem,  maybe that could be true.     ***

     There must be a software switch or such that needs to be set properly or something like that.

     > Going to alsamixer through terminal and changing that setting from default to   ' es 8316-spk-sound '

              Seemed to be a partial fix,  I can hear most videos and some ads on youtube after that change,  but the controls

                 are still grayed out in preferences, and the 'Test Sound'  option does not work.

                                           ?   ?

      
      LINUX = CHOICES
         **BCnAZ**
               Idea
   Donate to $upport
your favorite OS Team
#10
This is a different case.

The machine did arrive with sound and it is working under the user rock.

The thread poster tried to create a new user and the newly created user does not have sound.

The original user rock did have sound.


Possibly Related Threads…
Thread Author Replies Views Last Post
  Cellular module for Pinebook Pro Lotech 1 243 03-05-2024, 05:40 AM
Last Post: KC9UDX
  Screen on pinebook stays black but can ssh into machine tuxxpine 0 220 02-23-2024, 04:22 PM
Last Post: tuxxpine
  Sale my ANSI PineBook Pro cuthbertdavies 0 202 02-14-2024, 09:12 PM
Last Post: cuthbertdavies
  Compiling with -j6 on the Pinebook Pro (Overheat) KC9UDX 0 141 02-14-2024, 09:01 AM
Last Post: KC9UDX
  Pinebook Pro in EU for Sale - €90 jan_vdk 2 524 02-07-2024, 02:12 AM
Last Post: 23Ro
  Pinebook Pro for sale tomekdev 2 580 02-01-2024, 11:35 AM
Last Post: tomekdev
  looking to buy one pinebook pro (mainland China) duanduan 2 1,756 01-11-2024, 01:07 AM
Last Post: winecork
  Video Editing Is Possible On The PineBook Pro! ImmyChan 10 7,134 12-17-2023, 09:29 PM
Last Post: insideau786
  Brand new Pinebook Pro doesn't boot after Manjaro update johnboiles 8 1,943 12-15-2023, 02:11 PM
Last Post: wdt
  Happy eMMC and SDcard OS usage for Pinebook Pro Newbies... Paulie420 42 58,784 11-20-2023, 06:22 PM
Last Post: wdt

Forum Jump:


Users browsing this thread: 1 Guest(s)