yusefnapora/pixelbook-linux

pixelbook-linux's Issues

19.10 Video Issue

When I try to install 19.10 on my pixelbook, the video on the screen is upside down. Does the config script correct the issue or is there something else that needs to be done?

TPM errors spam

There are a lot of tpm errors and complains. They seem to happen every two seconds in the klog.

$ dmesg | grep tpm
[    0.355647] tpm tpm0: A TPM error (256) occurred attempting get random
[    0.367915] tpm tpm0: A TPM error (256) occurred attempting get random
[    0.375008] tpm tpm0: A TPM error (256) occurred attempting get random
[    2.994841] tpm tpm0: A TPM error (256) occurred attempting get random

kpartx -av can generate two digit loopback mapper devices causing ansible to fail a regexp match

When creating a loopback image of eve_recovery_image, kpartx -av can create a device whose loopback id contains two digits. This causes the regular expression Ansible uses (loop[0-9]p3) to fail to find a match in the stdout of kpartx. The solution is to match for any number of digits greater than or equal to 1 e.g., loop11p3, using the regexp: (loop[0-9]+p3)

``
diff --git a/ansible/roles/eve-recovery-files/tasks/main.yml b/ansible/roles/eve-recovery-files/tasks/main.yml
index eb8f863..8debc75 100644
--- a/ansible/roles/eve-recovery-files/tasks/main.yml
+++ b/ansible/roles/eve-recovery-files/tasks/main.yml
@@ -35,7 +35,7 @@
set_fact:
mapper_device: "{{ kpartx_output.stdout | regex_search(regexp, '\1') | first }}"
vars:

• regexp: '(loop[0-9]p3)'

• regexp: '(loop[0-9]+p3)'

• debug:
  msg: "mapper device: {{ mapper_device }}"
  ``

Stops at the end

TASK [eve-recovery-files : Map recovery image to loopback device] *********************************
fatal: [localhost]: FAILED! => {"changed": false, "cmd": "kpartx -av /opt/eve-linux-setup/chromeos_11647.154.0_eve_recovery_stable-channel_mp.bin", "msg": "[Errno 2] No such file or directory", "rc": 2}
to retry, use: --limit @/home/mrhaydendp/pixelbook-linux/ansible/playbook.retry

disk, dsm, kbl-rt5514-hotword-support and touch not found in the recovery image

Can't get past "OS Verification is OFF" after Ubuntu 19.1 install

I made it through the install step and when restarting the Pixelbook it took me to the "OS verification is OFF" page. I tried reinstalling Ubuntu again with no luck. I've search for help but couldn't find a similar issue.

Edit - I also tried starting out with 19.04 first and got stuck at the same point so maybe I missed something in the tutorial. I tried using the google repair tool to fix the original OS with no luck.

Broken UFW under the chromium kernel

When running under the chrome kernel, UFW doesn't work:

ERROR: problem running ufw-init
iptables-restore: line 75 failed
iptables-restore: line 42 failed
ip6tables-restore: line 142 failed
ip6tables-restore: line 42 failed

Problem running '/etc/ufw/before.rules'
Problem running '/etc/ufw/user.rules'
Problem running '/etc/ufw/before6.rules'
Problem running '/etc/ufw/user6.rules'

This then causes ALL traffic to be blocked.

Running under the standard (5.x.x) kernel, ufw DOES work.

sorry I have a mistake

TASK [eve-recovery-files : Find mapper device to use for mounting image] *******
fatal: [localhost]: FAILED! => {"msg": "Unexpected templating type error occurred on ({{ kpartx_output.stdout | regex_search(regexp, '\\1') | first }}): 'NoneType' object is not iterable"}
to retry, use: --limit @/home/lgs/pixelbook-linux/ansible/playbook.retry

PLAY RECAP *********************************************************************
localhost : ok=8 changed=1 unreachable=0 failed=1

Does this work with Fedora?

I noticed you had a Fedora task, but all of the kernel files are in .deb format. I'm a little deep into a Fedora install now that I realized that. I'm a newby.

Ansible fails on: "TASK [eve-tweaks : Copy libinput touchpad pressure tweak file]"

Hello,

Fails as follows:

TASK [eve-tweaks : Copy libinput touchpad pressure tweak file] *****************
fatal: [localhost]: FAILED! => {"changed": false, "checksum": "9cb56d667cd390aa928d9d760bb5739b4f0d9c1d", "msg": "Destination directory /etc/libinput does not exist"}
	to retry, use: --limit @/home/sk/Research/pixelbook-linux/ansible/playbook.retry

PLAY RECAP *********************************************************************
localhost                  : ok=74   changed=27   unreachable=0    failed=1   

Running script from start, so not sure why any requirements are missing.
Thanks!

ubuntu 20.04 update

Has anyone tried to update to 20.04?

When I updated to 19.04, it created a new kernel available on the boot load menu. That kernel did not take on the post-installation adjustments after re-running the ansible python script in the new kernel. All pixelbook-linux changes remain within the "4.4.178chromium-g4245c5e1" kernel.

How, complex is it to re-apply the ansible script adjustments to an updated kernel? (I'm using this as my primary work laptop while abroad so it's a little scary to guinea pig this request myself)

Display backlight is adjustable without Google's kernels

Hi, I am a Pixelbook user and I cannot appreciate your detailed instruction and scripts more. One thing that bothers me for a long time is that I can only adjust backlight in Google's 4.4 kernel, which is out-of-date from my perspective.

However, today I happened to find that the backlight is adjustable in latest kernels with the command-line interface (unfortunately not with GUI controls).

Laptop: i5 8+256
Distro: KUbuntu 19.04
DE: KDE Plasma (DE's config won't change brightness)
Kernel: 5.0.0-20-generic

I first find the display using xrandr -q | grep connected, which in my case is called eDP-1. Then I can adjust the brightness like xrandr --output eDP-1 --brightness 0.3, where the value of brightness goes from 0.0 to 1.0.

By strace-ing xrandr's behaviour, it seems pretty tricky because xrandr uses direct I/O interaction to adjust the backlight instead of writing the brightness value into a system config file. I don't know the exact reason behind this, but if this method works for everyone, we can write scripts to adjust backlight and bind them to keyboard shortcuts :D.

cras not installing linux mint

Trying to install the pixelbook script with Linux MInt 19.3, which is based on ubuntu 18.04. Everything seems to work fine except when it gets to Cras, and then it issues the following error message:

TASK [eve-audio : configure cras] ******************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["env", "CFLAGS=-I/usr/include/iniparser", "./configure", "--disable-dbus", "--disable-webrtc-apm", "--with-socketdir=/var/run/cras"], "delta": "0:00:00.001829", "end": "2020-04-26 08:10:51.684326", "msg": "non-zero return code", "rc": 127, "start": "2020-04-26 08:10:51.682497", "stderr": "env: ‘./configure’: No such file or directory", "stderr_lines": ["env: ‘./configure’: No such file or directory"], "stdout": "", "stdout_lines": []}
to retry, use: --limit @/home/john/pixelbook-linux/ansible/playbook.retry

can anyone provide some insight on how I can fix this? Other features on the pixelbook seem to work ok, just need cras to function so I have sound.

Thanks for any help in resolving this.

SELinux

I was a bit disappointed with the responsiveness of the system running Ubuntu and felt it wasn't right that it was so much slower than CrOS. Long story short, I realised that SELinux is enabled on 19.04, but given that we are running an older kernel and I was seeing errors I decided to disable it by creating /etc/selinux/config and adding

SELINUX=disabled

Big difference so far. Might be worth adding this to the playbook.

5.4

Anyone try building this yet?

ls /dev/tty* not enumerating USB devices

when a USB device is plugged in , it is recognized via dmesg and also under lsusb

however ls /dev/tty* does not create any usb serial devices.

therefore cannot communicate with the SuzyQ cable w adapter

any ideas? chromeOS is up to date

Script error

Hi, I'm getting this error when running the script. Any ideas on what to do to fix it? Thank you!

TASK [eve-recovery-files : Find mapper device to use for mounting image] *******
fatal: [localhost]: FAILED! => {"msg": "Unexpected templating type error occurred on ({{ kpartx_output.stdout | regex_search(regexp, '\\1') | first }}): 'NoneType' object is not iterable"}

TASK [eve-touchpad : Build libgestures]

Getting the below error, any ideas?

fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["make"], "delta": "0:00:00.035039", "end": "2020-03-12 22:35:29.399416", "msg": "non-zero return code", "rc": 2, "start": "2020-03-12 22:35:29.364377", "stderr": "Must specify package names on the command line\nMust specify package names on the command line\n/bin/sh: 1: g++: not found\nmake: *** [Makefile:177: obj/accel_filter_interpreter.o] Error 127", "stderr_lines": ["Must specify package names on the command line", "Must specify package names on the command line", "/bin/sh: 1: g++: not found", "make: *** [Makefile:177: obj/accel_filter_interpreter.o] Error 127"], "stdout": "mkdir -p obj .deps || true\ng++ -g -std=gnu++11 -fno-exceptions -fno-strict-aliasing -fPIC -Wall -Wempty-body -Wignored-qualifiers -Wmissing-field-initializers -Wmissing-format-attribute -Wmissing-noreturn -Wsign-compare -Wtype-limits -D__STDC_FORMAT_MACROS=1 -D_FILE_OFFSET_BITS=64 -DGESTURES_INTERNAL=1 -I.. -O1 -DVCSID="\"1234 TESTVERSION\"" --coverage -ftest-coverage -fprofile-arcs -I/usr/include/jsoncpp -MMD -c -o obj/accel_filter_interpreter.o src/accel_filter_interpreter.cc", "stdout_lines": ["mkdir -p obj .deps || true", "g++ -g -std=gnu++11 -fno-exceptions -fno-strict-aliasing -fPIC -Wall -Wempty-body -Wignored-qualifiers -Wmissing-field-initializers -Wmissing-format-attribute -Wmissing-noreturn -Wsign-compare -Wtype-limits -D__STDC_FORMAT_MACROS=1 -D_FILE_OFFSET_BITS=64 -DGESTURES_INTERNAL=1 -I.. -O1 -DVCSID="\"1234 TESTVERSION\"" --coverage -ftest-coverage -fprofile-arcs -I/usr/include/jsoncpp -MMD -c -o obj/accel_filter_interpreter.o src/accel_filter_interpreter.cc"]}

PLAY RECAP *********************************************************************
localhost : ok=57 changed=20 unreachable=0 failed=1 skipped=4 rescued=0 ignored=0

Can this be used for ubuntu USB drive installations?

First of all lots of "thank yous" for this impressive guide and the work that went into it!

As I am not ready to say good bye to chromeos, I already have a an usb drive ubuntu installation that works fairly ok. Seeing you made audio work makes me want to try your script (so just the stuff without the firmware flashing and WP disabling).
Just wanted to make sure your script does only work on the root partitions it is installed into, so it is not doing anything harmful to my chromeos partitions!?

As a sidenote: any idea why the uefi firmware has to break the abilty to start chromeos?

Thanks again for the great work and helping me out :)

vmware installation

Has anyone gotten VMware to install / run properly using the 4.4.178chromium kernel? I've tried so many different versions and online help articles without any luck.

Script success on Unbuntu 18.04?

anyone have any luck or success running the Pixelbook script on Ubuntu 18.04 LTS? Any details or comments would be appreciated before I attempt it.

Keyboard shortcuts in 19.10

I upgraded from 19.04 to 19.10 and the only thing to break was the custom eve keyboard layout. I couldn't get it to work again - *edit: see latest post below for fix.

bluetooth headphones not working

tested with beats solo3 and airpods 2
both can be paired and connected, but no sound emits...
Thanks to google's incompatibility with apple?

eve-audio-ctl.py: command not found

If I type in the terminal eve-audio-ctl.py as said in the documentation I get this error. It seems that the program is not in the path.

Does someone have the solution?

Re-running on installation to update, fails

I've run this on Disco and it's all good.

I come back to re-run it for any updates (e.g. on recovery image) and it fails:

TASK [eve-recovery-files : Unzip recovery image] ***************************************************************************
skipping: [localhost]

TASK [eve-recovery-files : Map recovery image to loopback device] **********************************************************
changed: [localhost]

TASK [eve-recovery-files : Find mapper device to use for mounting image] ***************************************************
fatal: [localhost]: FAILED! => {"msg": "Unexpected templating type error occurred on ({{ kpartx_output.stdout | regex_search(regexp, '\\\\1') | first }}): 'NoneType' object is not iterable"}
	to retry, use: --limit @/home/johnny/Downloads/pixelbook-linux/ansible/playbook.retry

PLAY RECAP *****************************************************************************************************************
localhost                  : ok=8    changed=1    unreachable=0    failed=1   

Really great!

Thanks for this. Very smooth install and everything works exactly as described. So nice to be back on a full system on such sweet hardware.

One question so far - how do you map Del key? On CrOS it was Alt-Backspace but I can't find any combination so far.

can yuo guys post a youtube video of the process? it would be a great help

I searched youtube but didnt find anything

gsctool unrecognized options

Hello,

Trying to setup a new Pixelbook, and when using "gsctool -a --ccd_open" I get "unrecognized option" for both -a and --ccd_open options. I also tried gsctool -a --ccd_info with the same result, "unrecognized option".

gsctool command is recognized, but it seems my option list is different than the options listed in the instructions.

This is a brand new pixelbook received 6/12/19, could there be a newer version of gsctool shipping with different option flags?

Ansible install fails on "TASK [eve-recovery-files : Find mapper device to use for mounting image]"

Hello,

I bought this pixelbook off ebay and someone had already follow your instructions to install ubuntu. However, the sound isn't working (no device is listed in the system menu & no audio plays when I watch videos) so the seller instructed I re-try installing the eve linux scripts.

So, running ./run-ansible.sh everything goes until:

TASK [eve-recovery-files : Map recovery image to loopback device] **************
changed: [localhost]

TASK [eve-recovery-files : Find mapper device to use for mounting image] *******
fatal: [localhost]: FAILED! => {"msg": "Unexpected templating type error occurred on ({{ kpartx_output.stdout | regex_search(regexp, '\\\\1') | first }}): 'NoneType' object is not iterable"}
	to retry, use: --limit @/home/sk/Research/pixelbook-linux/ansible/playbook.retry

PLAY RECAP *********************************************************************
localhost                  : ok=8    changed=1    unreachable=0    failed=1   ```

Which it fails.

sk@lixel:~/Research/pixelbook-linux$ lspci | grep audio
00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-LP HD Audio (rev 21)

sk@lixel:~/Research/pixelbook-linux$ ls -alh /opt/eve-linux-setup
total 3.7G
drwxrwxrwx  6 root root 4.0K May 13 00:45 .
drwxr-xr-x  6 root root 4.0K May 28 16:03 ..
drwxr-xr-x 15 sk   sk   4.0K May 13 00:43 adhd
-rw-r--r--  1 sk   sk   2.6G Apr 15 01:05 chromeos_11647.154.0_eve_recovery_stable-channel_mp.bin
-rw-r--r--  1 sk   sk   1.2G May 13 00:39 eve-recovery.zip
drwxr-xr-x 10 sk   sk   4.0K May 13 00:44 gestures
drwxr-xr-x  5 sk   sk   4.0K May 13 00:44 libevdev
drwxr-xr-x  8 sk   sk   4.0K May 13 00:45 xf86-input-cmt

sk@lixel:~/Research/pixelbook-linux$ sudo eve-audio-ctl.py -o speaker
Output Devices:
	hdmi2
	hdmi1
	headphone
active:	speaker

Input Devices:
	mic
active:	internal_mic
	post_dsp_loopback
	post_mix_pre_dsp_loopback

Even with that, sound still doesn't work. Any help is appreciated.

Ubuntu 19.04 end of life

with Ubuntu 19.04 at end of life, do you recommend still installing the 19.04 image running the correction scripts then upgrading or replacing 19.04 with 19.10 during initial set-up?

Flashed firmware, now white screen csnt reboot

I just finished flashing the firmware then powered off the laptop. It went into a white screen and the power button is unresponsive.

Do you have any idea how to Repair? I have a firmware backup.

Fedora 31

Has anyone had any luck using the script to install and run Fedora? I tried using Fedora 31 and there were issues with no sound, no bluetooth. There is a .yml file for Fedora but it seems to need some adjustments since it is looking for apt-get files, and it also will not install the updated boot loaders. Any help if you have had success would be appreciated.

On another note, any progress with the 5.4 kernel which seems to be in a Stale state? Perhaps the 5.4 kernel would fix some of these other issues with Fedora as well as with some other issues with Ubuntu I have read about?
Thx to all

Enabling cras for new user in Ubuntu

This may be easier than I'm thinking, but how do you enable Cras audio for a new user in Ubuntu? Do you have to re-run the script, or is there a simpler way?

updating to 19.10

The scripts worked wonderfully and I've enjoyed using 19.04 on my Pixelbook. However, the repositories are now deprecated and I'd like to be using an LTS. Will updating to 19.10 break the ansible script's changes or ican I simply update without any extra configurations?

I don't want to break my machine by updating to 19.10.

Debian 10 Buster issue

Running the ./run-ansible.sh script and recieving the following error.

./run-ansible.sh --limit @/home/cfuller/pixelbook-linux/ansible/playbook.retry
installing configuration with ansible. this may take a little while.
please enter your password when prompted.
SUDO password:
What keycode do you want the Search key to send? (see ansible/keycodes.txt)
[leftmeta]:
What keycode do you want the Assistant key to send? (see ansible/keycodes.txt)
[rightmeta]:

PLAY [all] *************************************************************************************************************************

TASK [Gathering Facts] *************************************************************************************************************
ok: [localhost]

TASK [Install pre-requisites] ******************************************************************************************************

TASK [common : install OS packages] ************************************************************************************************
fatal: [localhost]: FAILED! => {"reason": "Unable to retrieve file contents\nCould not find or access '/home/cfuller/pixelbook-linux/ansible/packages-Debian.yml' on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option"}
to retry, use: --limit @/home/cfuller/pixelbook-linux/ansible/playbook.retry

PLAY RECAP *************************************************************************************************************************
localhost : ok=1 changed=0 unreachable=0 failed=1

Can this work on Debian based on what you need to run git and python I thought this was a slamdunk.

cr50 firmware too old for CCD; struggling to update

Background

I purchased the SuzyQCable linked on the website, and followed all steps up to the "special cable time" procedure. When I run sudo gsctool -a --ccd_info, I see State: Opened (not State: Open as listed on the website--exact output pasted below.)

I then plugged the USB-A end of the SuzyQCable into a USB-A to USB-C adapter, and plugged the adapter into the right USB-C port on the Pixelbook. I plugged the USB-C end into the left port. When I list the devices in /dev, no USB devices appear. I flipped the left side over, but it had no effect.

The problem

Long story short, I was able to confirm that the device was detected as a Suzy Q Cable, but it was being disconnected immediately. I suspect, based on the official CCD documentation, that I need to update various pieces of software and firmware to make it work, but I am struggling to understand how to do so.

I was able to update the cr50 firmware using sudo gsctool -a /opt/google/cr50/firmware/cr50.bin.prod However, I cannot figure out what is meant by the following:

Help here, please!

Sync chroot to TOT (run repo sync in chromiumos directory) update servod and gsctool in chroot

  from chroot > sudo emerge hdctools ec-devutils servo-firmware
            chromeos-cr50 chromeos-cr50-scripts

Update servo v4 firmware

from chroot > sudo servo_updater -b servo_v4

I don't totally understand the chroot command., and I can't find a chromiumos directory. Any advice would be welcome.

Gory details

Actual output from sudo gsctool -a --ccd_info:

State: Opened
Password: None
Flags: 000000
Capabilities, current and default:
  UartGscRxAPTx   Y Always
  UartGscTxAPRx   Y Always
  UartGscRxECTx   Y Always
  UartGscTxECRx   Y IfOpened
  FlashAP         Y IfOpened
  FlashEC         Y IfOpened
  OverrideWP      Y IfOpened
  RebootECAP      Y IfOpened
  GscFullConsole  Y IfOpened
  UnlockNoReboot  Y Always
  UnlockNoShortPP Y Always
  OpenNoTPMWipe   Y IfOpened
  OpenNoLongPP    Y IfOpened
  BatteryBypassPP Y Always
  UpdateNoTPMWipe Y Always
  I2C             Y IfOpened
  FlashRead       Y Always
  OpenNoDevMode   Y IfOpened
  OpenFromUSB     Y IfOpened
  OverrideBatt    Y IfOpened
CCD caps bitmap: 0xfffff
Capabilities are default.

To make sure that the device was seen, I checked the logs. It showed that it was indeed found:

[ 1757.856183] usb 1-5: new high-speed USB device number 16 using xhci_hcd
[ 1758.051113] usb 1-5: New USB device found, idVendor=18d1, idProduct=501f, bcdDevice=32.99
[ 1758.051125] usb 1-5: New USB device strings: Mfr=10, Product=11, SerialNumber=12
[ 1758.051131] usb 1-5: Product: SuzyQable
[ 1758.051136] usb 1-5: Manufacturer: Google Inc.
[ 1758.051141] usb 1-5: SerialNumber: 0025000E0283
[ 1758.053201] hub 1-5:1.0: USB hub found
[ 1758.054876] hub 1-5:1.0: 4 ports detected
[ 1760.773136] usb 1-5.2: new full-speed USB device number 17 using xhci_hcd
[ 1760.863494] usb 1-5.2: New USB device found, idVendor=18d1, idProduct=5014, bcdDevice= 1.00
[ 1760.863506] usb 1-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=11
[ 1760.863512] usb 1-5.2: Product: Cr50
[ 1760.863517] usb 1-5.2: Manufacturer: Google Inc.
[ 1760.863522] usb 1-5.2: SerialNumber: 02014054-92D9C357
[ 1760.866713] usb_serial_simple 1-5.2:1.0: google converter detected
[ 1760.867862] usb 1-5.2: google converter now attached to ttyUSB0
[ 1760.868897] usb_serial_simple 1-5.2:1.1: google converter detected
[ 1760.869397] usb 1-5.2: google converter now attached to ttyUSB1
[ 1760.869862] usb_serial_simple 1-5.2:1.2: google converter detected
[ 1760.870205] usb 1-5.2: google converter now attached to ttyUSB2
[ 1761.295148] google ttyUSB0: google converter now disconnected from ttyUSB0
[ 1761.295204] usb_serial_simple 1-5.2:1.0: device disconnected
[ 1761.295475] google ttyUSB1: google converter now disconnected from ttyUSB1
[ 1761.295607] usb_serial_simple 1-5.2:1.1: device disconnected
[ 1761.295872] google ttyUSB2: google converter now disconnected from ttyUSB2
[ 1761.296237] usb_serial_simple 1-5.2:1.2: device disconnected

Possible workaround to apparent gcc 9.2 bug.

gcc version 9.2.1 20191008 complains about:

server/cras_rclient.c:628:6: error: taking address of packed member of ‘struct cras_config_global_remix’ may result in an unaligned pointer value [-Werror=address-of-packed-member] 628 | m->coefficient); | ~^~~~~~~~~~~~~ cc

The error seems to be spurious, (see openucx/ucx#3119 for others having the issue). One workaround is to ensure that gcc 8 is installed and to tell ansible to use that, e.g.

export CC=/usr/local/bin/gcc-8; ./run-ansible.sh

Trouble installing the Mr Chromebox firmware-util script

When I try to run the Mr Chromebox firmware util script I get the following error:

firmware-util.sh: warning: firmware-util.sh: warning: script from noexec mount; see https://chromium.googlesource.com/chromiumos/docs/+/master/security/noexec_shell_scripts.md
firmware-util.sh: line 38: warning: ./sources.sh: warning: script from noexec mount; see https://chromium.googlesource.com/chromiumos/docs/+/master/security/noexec_shell_scripts.md
firmware-util.sh: line 39: warning: ./firmware.sh: warning: script from noexec mount; see https://chromium.googlesource.com/chromiumos/docs/+/master/security/noexec_shell_scripts.md
firmware-util.sh: line 40: warning: ./functions.sh: warning: script from noexec mount; see https://chromium.googlesource.com/chromiumos/docs/+/master/security/noexec_shell_scripts.md
mount: /tmp/boot: wrong fs type, bad option, bad superblock on /dev/mmcblk0p12, missing codepage or helper program, or other error.
Error mounting boot partition; cannot proceed.

Unable to download cbfstool utility; cannot continue

Can anyone help me work out what's going wrong here? I've followed the steps as outlined in the readme and I have gotten the correct responses as per the readme.

I've even tried to remount the partition as exec but this doesn't seem to work either.

Error Building cras -> Pixelbook Speakers Undetected and Not Working

Each time I try to run the ansible script everything runs fine besides the Build Cras step. I get this error repeatedly:

fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["make"], "delta": "0:00:00.502450", "end": "2019-11-05 18:56:48.429219", "msg": "non-zero return code", "rc": 2, "start": "2019-11-05 18:56:47.926769", "stderr": "server/cras_rclient.c: In function ‘cras_rclient_message_from_client’:\nserver/cras_rclient.c:628:6: error: taking address of packed member of ‘struct cras_config_global_remix’ may result in an unaligned pointer value [-Werror=address-of-packed-member]\n 628 | m->coefficient);\n | ~^~~~~~~~~~~~~\ncc1: all warnings being treated as errors\nmake[1]: *** [Makefile:5031: server/libcrasserver_la-cras_rclient.lo] Error 1\nmake: *** [Makefile:459: all-recursive] Error 1", "stderr_lines": ["server/cras_rclient.c: In function ‘cras_rclient_message_from_client’:", "server/cras_rclient.c:628:6: error: taking address of packed member of ‘struct cras_config_global_remix’ may result in an unaligned pointer value [-Werror=address-of-packed-member]", " 628 | m->coefficient);", " | ~^~~~~~~~~~~~~", "cc1: all warnings being treated as errors", "make[1]: *** [Makefile:5031: server/libcrasserver_la-cras_rclient.lo] Error 1", "make: *** [Makefile:459: all-recursive] Error 1"], "stdout": "Making all in src\nmake[1]: Entering directory '/opt/eve-linux-setup/adhd/cras/src'\n/bin/bash ../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\\\"cras\\\" -DPACKAGE_TARNAME=\\\"cras\\\" -DPACKAGE_VERSION=\\\"0.1\\\" -DPACKAGE_STRING=\\\"cras\\ 0.1\\\" -DPACKAGE_BUGREPORT=\\\"[email protected]\\\" -DPACKAGE_URL=\\\"http://www.chromium.org/\\\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\\\".libs/\\\" -DHAVE_LIBASOUND=1 -DALSA_PLUGIN_DIR=\\\"/usr/local/lib/alsa-lib\\\" -DCRAS_CONFIG_FILE_DIR=\\\"/usr/local/etc/cras\\\" -DCRAS_SOCKET_FILE_DIR=\\\"/var/run/cras\\\" -DHAVE_SSE42=1 -DHAVE_AVX=1 -DHAVE_AVX2=1 -DHAVE_FMA=1 -I. -O2 -Wall -Werror -Wno-error=cpp -I../src/common -I../src/dsp -I../src/server -I../src/server/config -I/usr/include/iniparser -MT server/libcrasserver_la-cras_rclient.lo -MD -MP -MF server/.deps/libcrasserver_la-cras_rclient.Tpo -c -o server/libcrasserver_la-cras_rclient.lo test -f 'server/cras_rclient.c' || echo './'server/cras_rclient.c\nlibtool: compile: gcc -DPACKAGE_NAME=\\\"cras\\\" -DPACKAGE_TARNAME=\\\"cras\\\" -DPACKAGE_VERSION=\\\"0.1\\\" \"-DPACKAGE_STRING=\\\"cras 0.1\\\"\" -DPACKAGE_BUGREPORT=\\\"[email protected]\\\" -DPACKAGE_URL=\\\"http://www.chromium.org/\\\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\\\".libs/\\\" -DHAVE_LIBASOUND=1 -DALSA_PLUGIN_DIR=\\\"/usr/local/lib/alsa-lib\\\" -DCRAS_CONFIG_FILE_DIR=\\\"/usr/local/etc/cras\\\" -DCRAS_SOCKET_FILE_DIR=\\\"/var/run/cras\\\" -DHAVE_SSE42=1 -DHAVE_AVX=1 -DHAVE_AVX2=1 -DHAVE_FMA=1 -I. -O2 -Wall -Werror -Wno-error=cpp -I../src/common -I../src/dsp -I../src/server -I../src/server/config -I/usr/include/iniparser -MT server/libcrasserver_la-cras_rclient.lo -MD -MP -MF server/.deps/libcrasserver_la-cras_rclient.Tpo -c server/cras_rclient.c -fPIC -DPIC -o server/.libs/libcrasserver_la-cras_rclient.o\nmake[1]: Leaving directory '/opt/eve-linux-setup/adhd/cras/src'", "stdout_lines": ["Making all in src", "make[1]: Entering directory '/opt/eve-linux-setup/adhd/cras/src'", "/bin/bash ../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\\\"cras\\\" -DPACKAGE_TARNAME=\\\"cras\\\" -DPACKAGE_VERSION=\\\"0.1\\\" -DPACKAGE_STRING=\\\"cras\\ 0.1\\\" -DPACKAGE_BUGREPORT=\\\"[email protected]\\\" -DPACKAGE_URL=\\\"http://www.chromium.org/\\\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\\\".libs/\\\" -DHAVE_LIBASOUND=1 -DALSA_PLUGIN_DIR=\\\"/usr/local/lib/alsa-lib\\\" -DCRAS_CONFIG_FILE_DIR=\\\"/usr/local/etc/cras\\\" -DCRAS_SOCKET_FILE_DIR=\\\"/var/run/cras\\\" -DHAVE_SSE42=1 -DHAVE_AVX=1 -DHAVE_AVX2=1 -DHAVE_FMA=1 -I. -O2 -Wall -Werror -Wno-error=cpp -I../src/common -I../src/dsp -I../src/server -I../src/server/config -I/usr/include/iniparser -MT server/libcrasserver_la-cras_rclient.lo -MD -MP -MF server/.deps/libcrasserver_la-cras_rclient.Tpo -c -o server/libcrasserver_la-cras_rclient.lo test -f 'server/cras_rclient.c' || echo './'server/cras_rclient.c", "libtool: compile: gcc -DPACKAGE_NAME=\\\"cras\\\" -DPACKAGE_TARNAME=\\\"cras\\\" -DPACKAGE_VERSION=\\\"0.1\\\" \"-DPACKAGE_STRING=\\\"cras 0.1\\\"\" -DPACKAGE_BUGREPORT=\\\"[email protected]\\\" -DPACKAGE_URL=\\\"http://www.chromium.org/\\\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\\\".libs/\\\" -DHAVE_LIBASOUND=1 -DALSA_PLUGIN_DIR=\\\"/usr/local/lib/alsa-lib\\\" -DCRAS_CONFIG_FILE_DIR=\\\"/usr/local/etc/cras\\\" -DCRAS_SOCKET_FILE_DIR=\\\"/var/run/cras\\\" -DHAVE_SSE42=1 -DHAVE_AVX=1 -DHAVE_AVX2=1 -DHAVE_FMA=1 -I. -O2 -Wall -Werror -Wno-error=cpp -I../src/common -I../src/dsp -I../src/server -I../src/server/config -I/usr/include/iniparser -MT server/libcrasserver_la-cras_rclient.lo -MD -MP -MF server/.deps/libcrasserver_la-cras_rclient.Tpo -c server/cras_rclient.c -fPIC -DPIC -o server/.libs/libcrasserver_la-cras_rclient.o", "make[1]: Leaving directory '/opt/eve-linux-setup/adhd/cras/src'"]}

Everything else runs fine and I have Ubuntu running flawlessly otherwise. The battery is even far better than I'd expected it to be. I've tried rooting around the internet to find a solution elsewhere but nothing works. I did find a fork from another user who had an edit to their playbook.yaml for the audio drivers but their script also does not work. Anyone else run into the same problem and figure out how to solve it?

The script does not work with dual boot.

I attach the error generated in case it can help someone who is able to update the script to solve the problem.

error: https://www.dropbox.com/sh/dnovmtgz7jgnap9/AACvv5atVveR2sPVYlC6ObCoa?dl=0

P.S: I use RW_LEGACY and Fw WP is enabled

Error connecting Suzy-Q

When I connect my Suzy Cable (I thought the cable might be bad, so have tried two) I get no USB tty devides. dmesg gives me errors like this:

[88523.248287] usb 1-13.1.2: device not accepting address 43, error -71
[88523.516285] usb 1-13.1.2: new low-speed USB device number 44 using xhci_hcd
[88523.516387] usb 1-13.1.2: Device not responding to setup address.
[88523.719268] usb 1-13.1.2: Device not responding to setup address.
[88523.928287] usb 1-13.1.2: device not accepting address 44, error -71
[88523.928639] usb 1-13.1-port2: unable to enumerate USB device
[88524.105215] usb 1-13.1.2: new low-speed USB device number 45 using xhci_hcd
[88524.379288] usb 1-13.1.2: device descriptor read/64, error -71
[88524.757316] usb 1-13.1.2: device descriptor read/64, error -71
[88524.929284] usb 1-13.1.2: new low-speed USB device number 46 using xhci_hcd
[88525.205282] usb 1-13.1.2: device descriptor read/64, error -71
[88525.579234] usb 1-13.1.2: device descriptor read/64, error -71
[88525.688617] usb 1-13.1-port2: attempt power cycle

I get the same message when connecting the Pixelbook to itself and when using a separate machine running Linux. It does only appear when the cable is attached to the left port and oriented the right way.

I'm quite sure I've followed these steps precisely, any ideas? I'm betting either my pixelbook is broken, or I need to update some firmware or something? gsctool reports the EC firmware is a new enough version to do CCD.

Ubuntu 19.10 - Failed step: Find mapper device to use for mounting image

I have a fresh install of Ubuntu 19.10 and I receive the following error on the "Find mapper device to use for mounting image" step:

TASK [eve-recovery-files : Find mapper device to use for mounting image] *******
fatal: [localhost]: FAILED! => {"msg": "Unexpected templating type error occurred on ({{ kpartx_output.stdout | regex_search(regexp, '\\1') | first }}): 'NoneType' object is not iterable"}

PLAY RECAP *********************************************************************
localhost : ok=8 changed=1 unreachable=0 failed=1 skipped=1 rescued=0 ignored=0

cras eating a lot of CPU

I notice that the cras process continually uses ~25% CPU, even when no audio is being used.

strace shows it doing nothing more than polling. Any idea why this might be?

Python script not detecting inputs

When running eve_audio_ctl.py, no devices are detected even though cras_test_client detects all devices. This is on a non-eve device and on debian, I am using CORAL/BRUCE. I have the kernel installed and the audio devices detected in cras_test_client, but not in eve_audio_ctl.py.

Back to Chrome OS

Hello,

I really enjoy using Ubuntu on my pixelbook, but I was wondering if it's possible to now dual-boot Chrome OS on the same machine without completely wiping Ubuntu and switching back. There are certain uses that Chrome OS was just plain better for, but I would still like to benefit from the full use of Ubuntu.

Thank you

Sound stops working when plugging in headphone

Ubuntu 19.04, either Gnome or i3-wm.

Sound works great on the speakers. Nice and clear and loud. Plug in headphones in the jack, and no more sound, and anything to do with sounds seems to be blocking, ie videos will not play, etc.

Only way to clear up from what I have tried is to reboot.

Linux Mint Possible? (Ansible scripts)

Hi,

Thank you for all the great work you have done on this project! I know the Ansible scripts were written for use under Ubuntu 19.04, however, I was curious about running under Linux Mint 19.01 (which is basically Ubuntu 18.04). I tried running the Ansible script and after providing the alternate key assignments for the search key and assistant key I get the following error:

TASK [common : install OS packages] ***************************************************************************
fatal: [localhost]: FAILED! => {"reason": "Unable to retrieve file contents\nCould not find or access '/home/john/pixelbook-linux/ansible/packages-Linux Mint.yml'"}
to retry, use: --limit @/home/john/pixelbook-linux/ansible/playbook.retry

Any ideas or help would be great as I would love to run Mint.

ansible error

Hello,

While compiling the ansible script I get this error:

TASK [eve-recovery-files : Find mapper device to use for mounting image] *******
fatal: [localhost]: FAILED! => {"msg": "Unexpected templating type error occurred on ({{ kpartx_output.stdout | regex_search(regexp, '\\\\1') | first }}): 'NoneType' object is not iterable"}

Any advice?

Cannot turn off natural scroll

Hello,
so, it seems that I cannot turn off Natural Scroll, even if I chose it in the settings app.

Ubuntu 19.04, if that helps.

Let me know what I can do to help debug & then fix (if possible)

Login Screen is Black

I got most of your script working, but after rebooting, my login screen is black. I'm a still able to log in by typing my pw, just can't see anything. After this it works even if I log out and log back in, it seems to only happen when booting. I've tried setting up a scriptt to manually set the brightness on boot, but it didn't work. Is there anywhere this is set in your files?
I'm running mint, if that matters.
Thanks!