Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No audio (in/out) on Google Pixel 2015 (SAMUS) #100

Closed
reynhout opened this issue Dec 4, 2015 · 171 comments
Closed

No audio (in/out) on Google Pixel 2015 (SAMUS) #100

reynhout opened this issue Dec 4, 2015 · 171 comments

Comments

@reynhout
Copy link
Member

reynhout commented Dec 4, 2015

Reported on Reddit: https://www.reddit.com/r/GalliumOS/comments/3tb7ly/no_sound_on_pixel_2_and_accidentally_removed/

Possible solution? https://github.com/raphael/linux-samus

The internal mic is also not working on SAMUS. Possibly related, so it might make sense to track them together. Report: https://www.reddit.com/r/GalliumOS/comments/3xw2zm/audio_issues_on_pixel/

@welbinator
Copy link

Is there anybody out there who could break this "possible solution" down into a noob friendly tutorial? That link you provided makes a lot of assumptions regarding the reader's familiarity with Linux

@reynhout
Copy link
Member Author

reynhout commented Dec 6, 2015

Sorry, that link isn't a solution for users. There might (or might not!) be info in there that will help someone on the GalliumOS team debug the problem and roll the fix into a package update.

When we get it fixed, you will hopefully not need to do anything tricky at all -- just update the system via the usual apt-get update && apt-get dist-upgrade process.

@welbinator
Copy link

ahaha, ok. That makes a lot of sense. Thanks!

@ghost
Copy link

ghost commented Dec 6, 2015

Are we sure this is unrelated to #86 or #82?

@reynhout
Copy link
Member Author

reynhout commented Dec 6, 2015

Do you mean #66 instead of #86? If so, possibly -- but the new Pixel isn't a Bay Trail, so I decided to track this separately until we could confirm/deny the relationship.

#82 could be related, but I think the reports are that sound never worked on this model. There does seem to be a lot of confusion getting sound to work as expected though, much of which appears to be status quo in Linux. :(

@ghost
Copy link

ghost commented Dec 7, 2015

Oops, yes, you're right. I was referring to #66. My bad.

@reynhout
Copy link
Member Author

Some SAMUS customizations

@Pechnet
Copy link

Pechnet commented Dec 21, 2015

Hi all,

I just got my hands on Chrome Pixel 2015 LS. I also have the sound issue. Have you got any estimate on when this will be fixed within the new Gallium OS release? Otherwise I will need to look for alternative ways to patch it.

@reynhout
Copy link
Member Author

@Pechnet : we do not have an estimate at this time, sorry. We do not have a test device for this model.

The solutions above are reported to work, but have not been tested by us. If you are able to test them, please do and let us know how things go. With active assistance, we might be able to incorporate the fixes into a future release.

@Pechnet
Copy link

Pechnet commented Dec 21, 2015

OK thanks. Same goes for the track-pad right click?

@reynhout
Copy link
Member Author

@Pechnet right-click issues might just be touchpad driver config. Has the problem been reported elsewhere?

@welbinator
Copy link

somebody buy these guys a Pixel already =]

@Pechnet
Copy link

Pechnet commented Dec 21, 2015

@reynhout Thanks for clarifying and well done, apart from the sound issue Gallium OS is impressive. Yes it it's the #108. I tried to follow the recommended steps but I encounter an issue. I'm not an expert Linux user, going back to it after many years. I posted a follow up on that G+ thread.

@reynhout
Copy link
Member Author

@Pechnet I don't really understand what's going on in that other ticket. This is the wrong place to discuss it, but if you can add some detail there as to what the problem behaviour is, that would help. Right now that ticket reads like a mistaken report, so it would be difficult to work on.

@ghost
Copy link

ghost commented Dec 21, 2015

I would be very interested in working on the Pixel issues, but I need a Pixel first.

@reynhout reynhout changed the title No sound on Google Pixel 2015 (SAMUS) No audio (in/out) on Google Pixel 2015 (SAMUS) Dec 23, 2015
@caskaid
Copy link

caskaid commented Jan 13, 2016

Using the "Possible Solution" repository in the top post resulted in completed broken gallium instance after rebooting. Black screen, no tty, nothing.

@wamacdonald89
Copy link

@caskaid I can confirm this behavior as well. There may be a solution in there after changing some configs but ultimately we should not be suggesting this as a solution since it completely replaces the galliumos optimized kernel.

@welbinator
Copy link

We should ask pitch in and buy these guys a pixel

@welbinator
Copy link

all* pitch in

@caskaid
Copy link

caskaid commented Jan 28, 2016

Additional Testing:

In booting a stock Ubuntu 15.10 from SD and loading raphael/linux-samus from above, I was able to successfully get working audio out from both speakers and headphone. Had to reboot a couple of times and it still complained about pulseaudio not starting. Trackpad completely stops working however, but might just be some additional reconfiguration.

Added Bonus: Microphone was also detected and appeared to be working. Will be testing other items related to the linux-samus set, but wanted to keep the emphasis here on audio related items.

Trying to install the linux-samus set ~ 2 weeks ago ON GalliumOS resulted in a non-booting system. Not sure if I should try again. I am also not able to reach grub no matter what timeout/display settings I set for grub and I get screen distortion while trying to boot linux-samus from SD, but it eventually boots after around 20 seconds. Couldn't read what it was actually hanging on, will update comment if I can with updated information.

@coolstar
Copy link

I'd also be willing to look into the Pixel 2, but unfortunately it's quite expensive. Otherwise I'd be up for building a full coreboot ROM and getting the chromebook working fully in both Linux and Windows just like I did on the Acer C720, C740 and other Haswell/Broadwell chromebooks.

@fortes
Copy link

fortes commented Feb 9, 2016

FWIW, I just did a clean install of Gallium and cannot get sound to play. The only output device is HDMI.

I previously have installed Debian on the Pixel 2 and was able to get sound running via https://github.com/raphael/linux-samus -- but it does require jumping through some hoops (see their README)

@hugegreenbug
Copy link
Member

@fortes We are aware of the issue. The pixel 2 still isn't officially supported. We plan on porting the changes from raphael's kernel soon.

@hugegreenbug
Copy link
Member

I ported the pixel2 sound module to the GalliumOS kernel, which appears to just be this file: https://github.com/raphael/linux-samus/blob/master/build/linux/sound/soc/intel/boards/bdw-rt5677.c . I haven't uploaded the code anywhere yet since I have no idea if it works. I have built a test kernel: https://drive.google.com/file/d/0B6zPD2kAJoTJWGlyVGk4WldTTDg/view?usp=sharing .

This kernel will need the firmware and you will need to run the setup script from Raphael's linux-samus kernel https://github.com/raphael/linux-samus/tree/master/scripts/setup/sound . If the kernel and the script works, then I can make a pixel2 package that has the modified config files and firmware.

@hugegreenbug
Copy link
Member

I forgot to mention that acpid isn't included in GalluimOS, so you would need to install it for the sound setup script to work.

@caskaid
Copy link

caskaid commented Feb 27, 2016

Tried to test kernel without luck. All I did was ensure I was in fact booted into the right kernel, copied the appropriate "IntcSST2.bin" firmware to /lib/firmware/intel and rebooted, then attempted to run the sound.sh script which fails.

aplay -l does not list bdw-rt5677 at all. Nothing in dmesg regarding it, same for kern.log and syslog Spoke with ehegnes over at #linux-samus and he thought that things might not have been patched properly, but wont know until he can do a diff against linux-samus and inspect the important sound parts.

@hugegreenbug
Copy link
Member

I will check it in later today

@reynhout
Copy link
Member Author

@supasebie Oh, that's unfortunate. Do you get the same problem in headphones?

@chepurko
Copy link

I've installed ubuntu-desktop and there are a couple of observations with audio in the Unity desktop. The mic again doesn't work and doesn't show up in Gnome's audio control, so I have to use pacmd or edit /etc/pulse/default.pa with the following items uncommented near the bottom:

### Make some devices default
set-default-sink 1
set-default-source 2

Basically this has the effect of clicking the default checkmark buttons for the bdw-rt5677 in output and input. The Gnome audio settings just lack this.

@reynhout In pacmd I discovered the port analog-input-headset-mic which has available: no under the source alsa_input.platform-bdw-rt5677.analog-stereo. So if you pacmd set-source-port 2 analog-input-headset-mic this does the same as the switch in pavucontrol and the headset mic doesn't work. Do you know why the port is unavailable? Is it more of a kernel issue or just a flip of the switch in pulse or alsa?

@reynhout
Copy link
Member Author

reynhout commented Aug 29, 2016

New kernel pkgs: linux-image-4.7.2-galliumos and linux-firmware-image-4.7.2-galliumos added to galliumos-testing. Appears OK in limited testing.

  • Linux kernel 4.7.2
  • Updated SAMUS audio patches

No important new features or compatibility expected -- just updating the substrate, hopefully without adding bugs. Please report any issues.

@doscero
Copy link

doscero commented Aug 31, 2016

Ever since switching to kernel 4.7.0 , samus is not able to wake from suspend. This occurs by suspending via closed lid or the power button menu. Going back to 4.4.6 I am able to wake up from suspend. This could be an isolated issue unless someone else has encountered the same problem. The symptoms are similar to raphael/linux-samus#122 .

Update: I am no longer experiencing the issue in 4.7.2

@coolstar
Copy link

coolstar commented Aug 31, 2016

Tested with both 4.7.0-galliumos and 4.7.2-galliumos gets ipc timeout errors on both Linux Mint 18 and Ubuntu 16.04.1.

Audio is non-functional on the Pixel 2 LS and dmesg has ipc timeout errors.

[    9.085960] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x87000000
[    9.385479] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x86020000 isr 0x00000000 ipcd 0x47000000 imrx 0x7fff0000
[    9.385484] haswell-pcm-audio haswell-pcm-audio: error: failed to reset stream 2
[    9.686434] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x86020000 isr 0x00000000 ipcd 0x47000000 imrx 0x7fff0000
[    9.686438] haswell-pcm-audio haswell-pcm-audio: error: stream commit failed
[    9.686441]  System PCM: error: failed to commit stream -110
[    9.686443] haswell-pcm-audio haswell-pcm-audio: ASoC: haswell-pcm-audio hw params failed: -110
[    9.686445]  System PCM: ASoC: hw_params FE failed -110
[    9.986430] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x86020000 isr 0x00000000 ipcd 0x47000000 imrx 0x7fff0000
[    9.986434] haswell-pcm-audio haswell-pcm-audio: error: stream commit failed
[    9.986436]  System PCM: error: failed to commit stream -110
[    9.986438] haswell-pcm-audio haswell-pcm-audio: ASoC: haswell-pcm-audio hw params failed: -110
[    9.986440]  System PCM: ASoC: hw_params FE failed -110

@reynhout
Copy link
Member Author

@coolstar I don't know why it's not working for you in Ubuntu and Mint, but have you tried the GalliumOS kernel in GalliumOS?

@benjaminnyc
Copy link

This is probably noobish, but after installing kernel 4.7.0 and typing this:

sudo samus-alsaenable-speakers

I get this:

sudo: samus-alsaenable-speakers: command not found

Without sudo, I get this:

bash: samus-alsaenable-speakers: command not found

How do I execute this command?

Thanks!

@reynhout
Copy link
Member Author

reynhout commented Sep 2, 2016

@benjaminnyc do you have the galliumos-samus package installed? (step 4 in #100 (comment))

@benjaminnyc
Copy link

I'm an idiot. I must have missed that step. Sound working now!

But now I have another problem. Everything on my system is GIANT! Default system font is huge, but so is every element of the desktop, including windows, etc.

It also wiped my keyboard shortcut for Whisker Menu (no big deal) and put Chomium back in my panel (also no big deal).

How can I get everything looking normal again?

Note that I am on 4.7.0. I see 4.7.2 is offered above. Should I install that? How?

Thanks, and sorry :(

@reynhout
Copy link
Member Author

reynhout commented Sep 2, 2016

@benjaminnyc Did you copy in the /etc/skel files from that list of instrux? They set several config files for HiDPI. This might be additive to configuration you did manually, and therefore making things huge? Those instructions assume no previous config.

So you can do a full-reset with something like this:

mv $HOME/.config $HOME/.config-old
cp -r /etc/skel/.config $HOME.config

And then if you have important config files, you can cherry pick them from .config-old. Might be a pain in the neck if you have lots of them. The other alternative is to figure out what conflicting config might exist, and fix it surgically.

@benjaminnyc
Copy link

Figured it out, I changed custom DPI setting in Appearance from where it was at about 170 down to 110. Now everything looks almost normal. Is that what was supposed to happen?

@reynhout
Copy link
Member Author

reynhout commented Sep 2, 2016

@benjaminnyc re: 4.7.2. I haven't received any reports of issues with the new kernel, so it's probably safe. But there are no major advances either, and this will not be the final 4.7.2 kernel pkg, so waiting is also appropriate. You would install with:

apt-get install linux-image-4.7.2-galliumos linux-firmware-image-4.7.2-galliumos

@benjaminnyc
Copy link

Yikes that COMPLETELY wiped my desktop and reverted me to the standard XFCE starting desktop! I rebuilt everything, I think. It even wiped my Evolution and InSync accounts, and I had to recreate them.

One thing I can't find is the Gallium OS/Xubuntu icon that you use for default on the Whisker menu. It's not in Application Icons anymore. I found a .jpg of it online, but it doesn't look that good.

Do you have a transparent .png of it that I can use so that the middle is clear and shows the dark panel underneath?

Thanks.

@reynhout
Copy link
Member Author

reynhout commented Sep 2, 2016

@benjaminnyc Right, that will start you from the GalliumOS defaults (not the Xfce defaults -- if you got that, something is wrong). But you can just copy the bits back over from .config-old that you need.

The GalliumOS logo menu icon should be in /usr/share/pixmaps/xubuntu-logo-menu.png.

@benjaminnyc
Copy link

It left me with complete XFCE default. But I've got it sorted. And working sound! Thanks for your help!

@reynhout
Copy link
Member Author

reynhout commented Sep 2, 2016

@benjaminnyc OK, that would mean that your installation is damaged -- probably some packages accidentally removed. If you'd like help fixing it, please drop into IRC: https://galliumos.org/irc

@benjaminnyc
Copy link

Thank you very much. It seems to be working OK right now though after I've rebuilt.

@reynhout
Copy link
Member Author

@benjaminnyc reports an issue with media key volume control and muting (notification appears, volume does not change). Can't repro here. Anyone else having issues?

ref: https://www.reddit.com/r/GalliumOS/comments/52e59x/kernel_472_bug_on_samus_not_obeying_media_keys/

@caskaid
Copy link

caskaid commented Sep 13, 2016

Can't reproduce either on 4.7.2

@ghost
Copy link

ghost commented Sep 22, 2016

@reynhout I use

amixer -c 0 cset name='Speaker Switch' off
amixer -c 0 cset name='Stereo DAC MIXL DAC1 R Switch' off
amixer -c 0 cset name='Stereo DAC MIXR DAC1 L Switch' off
amixer -c 0 cset name='Stereo DAC MIXL DAC1 L Switch' on
amixer -c 0 cset name='Stereo DAC MIXR DAC1 R Switch' on
amixer -c 0 cset name='OUT1 Playback Switch' on
amixer -c 0 cset name='OUT2 Playback Switch' on
amixer -c 0 cset name='Headphone Switch' on

This script to make my headphones work and it works great! Is there a command though to have GalliumOS use the microphone on headphones? In Volume Control -> Input Devices I see that it says Headset microphone but it sees it as unplugged. Thanks!

@reynhout
Copy link
Member Author

@Penetrance Unfortunately, I don't have a wired headset mic to test with. I'll see if I can find one.

@keorn
Copy link

keorn commented Oct 16, 2016

My headphones also do not work on 4.7.2 (just says unplugged in the Volume Control app). The script by @Penetrance makes them work.

@reynhout
Copy link
Member Author

@keorn that is the script in /usr/bin/samus-alsaenable-headphones. Switching between headphones and speakers (with /usr/bin/samus-alsaenable-speakers) is still manual for now.

@busera
Copy link

busera commented Nov 3, 2016

Hi again, I did a clean install last week, and my Pixel 2015 is still not playing any sound.

Defaulf Server: {...}unix:/run/user/1001/pulse/native
Default Sink: bdw-rt5677
Default Source: bdw-rt5677 Anlog Stereo

Output Devices: Port: Speakers (for bdw-rt5677)

Do I still need to install the "galliumos-samus" package separately?

UPDATE: Ok, installing the "galliumos-samus" package fixed the issue. Audio is back :-)

@reynhout
Copy link
Member Author

Closing as resolved.

New tickets for remaining details:

@glynhudson
Copy link

For anyone else like me who found this thread after install Gallium on SAMUS and experiencing no sound it's fixed by following the post install SAMUS steps on the Galliumwiki

https://wiki.galliumos.org/Installing/Samus#Post-install_Customization

Nice work Gallium team 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests