Talk:Acer C710 Chromebook

From ArchWiki
(Redirected from Talk:Acer C7 Chromebook)
Jump to: navigation, search

This is a work in progress, the following are pages that I've used to get everything working all nice and neatly.

The mouse can be clicked while the screen is closed and wakes up from sleep, this is bad http://shallowsky.com/blog/linux/kernel/no-mouse-kbd-wakeup.html

most of these steps came from http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/cr-48-chrome-notebook-developer-information/how-to-boot-ubuntu-on-a-cr-48

test code for systemd job

/etc/systemd/system/disable.touch.wakeup.service 
[Unit] 
Description=disable-touchpad-wakeup

[Service] 
ExecStart=echo TPAD > /proc/acpi/wakeup

[Install] 
WantedBy=multi-user.target

the make output for the kernel

HOSTCC  scripts/basic/fixdep

root /usr/src/kernel-next # yes "" | make oldconfig

 HOSTCC  scripts/kconfig/conf.o
 SHIPPED scripts/kconfig/zconf.tab.c
 SHIPPED scripts/kconfig/zconf.lex.c
 SHIPPED scripts/kconfig/zconf.hash.c
 HOSTCC  scripts/kconfig/zconf.tab.o
 HOSTLD  scripts/kconfig/conf

scripts/kconfig/conf --oldconfig Kconfig drivers/net/Kconfig:6:warning: environment variable WIFIVERSION undefined

  • Restart config...
  • Keyboards

Keyboards (INPUT_KEYBOARD) [Y/n/?] y

 ADP5588/87 I2C QWERTY Keypad and IO Expander (KEYBOARD_ADP5588) [N/m/y/?] n
 ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander (KEYBOARD_ADP5589) [N/m/y/?] n
 AT keyboard (KEYBOARD_ATKBD) [Y/n/m/?] y
 Atmel AT42QT1070 Touch Sensor Chip (KEYBOARD_QT1070) [N/m/y/?] n
 Atmel AT42QT2160 Touch Sensor Chip (KEYBOARD_QT2160) [N/m/y/?] n
 DECstation/VAXstation LK201/LK401 keyboard (KEYBOARD_LKKBD) [N/m/y/?] n
 GPIO Buttons (KEYBOARD_GPIO) [Y/n/m/?] y
 Polled GPIO buttons (KEYBOARD_GPIO_POLLED) [N/m/y/?] n
 TCA6416/TCA6408A Keypad Support (KEYBOARD_TCA6416) [N/m/y/?] n
 TCA8418 Keypad Support (KEYBOARD_TCA8418) [N/m/y/?] n
 GPIO driven matrix keypad support (KEYBOARD_MATRIX) [N/m/y/?] n
 LM8323 keypad chip (KEYBOARD_LM8323) [N/m/y/?] n
 LM8333 keypad chip (KEYBOARD_LM8333) [N/m/y/?] n
 
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/zconf.lex.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --oldconfig Kconfig
drivers/net/Kconfig:6:warning: environment variable WIFIVERSION undefined
*
* Restart config...
*
*
* Keyboards
*
Keyboards (INPUT_KEYBOARD) [Y/n/?] y
  ADP5588/87 I2C QWERTY Keypad and IO Expander (KEYBOARD_ADP5588) [N/m/y/?] n
  ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander (KEYBOARD_ADP5589) [N/m/y/?] n
  AT keyboard (KEYBOARD_ATKBD) [Y/n/m/?] y
  Atmel AT42QT1070 Touch Sensor Chip (KEYBOARD_QT1070) [N/m/y/?] n
  Atmel AT42QT2160 Touch Sensor Chip (KEYBOARD_QT2160) [N/m/y/?] n
  DECstation/VAXstation LK201/LK401 keyboard (KEYBOARD_LKKBD) [N/m/y/?] n
  GPIO Buttons (KEYBOARD_GPIO) [Y/n/m/?] y
  Polled GPIO buttons (KEYBOARD_GPIO_POLLED) [N/m/y/?] n
  TCA6416/TCA6408A Keypad Support (KEYBOARD_TCA6416) [N/m/y/?] n
  TCA8418 Keypad Support (KEYBOARD_TCA8418) [N/m/y/?] n
  GPIO driven matrix keypad support (KEYBOARD_MATRIX) [N/m/y/?] n
  LM8323 keypad chip (KEYBOARD_LM8323) [N/m/y/?] n
  LM8333 keypad chip (KEYBOARD_LM8333) [N/m/y/?] n
  Maxim MAX7359 Key Switch Controller (KEYBOARD_MAX7359) [N/m/y/?] n
  MELFAS MCS Touchkey (KEYBOARD_MCS) [N/m/y/?] n
  Freescale MPR121 Touchkey (KEYBOARD_MPR121) [N/m/y/?] n
  Newton keyboard (KEYBOARD_NEWTON) [N/m/y/?] n
  OpenCores Keyboard Controller (KEYBOARD_OPENCORES) [N/m/y/?] n
  Stowaway keyboard (KEYBOARD_STOWAWAY) [N/m/y/?] n
  Sun Type 4 and Type 5 keyboard (KEYBOARD_SUNKBD) [N/m/y/?] n
  XT keyboard (KEYBOARD_XTKBD) [N/m/y/?] n
  ChromeOS EC keyboard (KEYBOARD_CROS_EC) [N/m/y/?] (NEW) *
* I2C Hardware Bus support
*
*
* PC SMBus host controller drivers
*
ALI 1535 (I2C_ALI1535) [N/m/y/?] n
ALI 1563 (I2C_ALI1563) [N/m/y/?] n
ALI 15x3 (I2C_ALI15X3) [N/m/y/?] n
AMD 756/766/768/8111 and nVidia nForce (I2C_AMD756) [N/m/y/?] n
AMD 8111 (I2C_AMD8111) [N/m/y/?] n
Intel 82801 (ICH/PCH) (I2C_I801) [Y/n/m/?] y
Intel SCH SMBus 1.0 (I2C_ISCH) [N/m/y/?] n
Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC) (I2C_PIIX4) [M/n/y/?] m
Nvidia nForce2, nForce3 and nForce4 (I2C_NFORCE2) [N/m/y/?] n
SiS 5595 (I2C_SIS5595) [N/m/y/?] n
SiS 630/730 (I2C_SIS630) [N/m/y/?] n
SiS 96x (I2C_SIS96X) [N/m/y/?] n
VIA VT82C586B (I2C_VIA) [N/m/y/?] n
VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900 (I2C_VIAPRO) [N/m/y/?] n
*
* ACPI drivers
*
SMBus Control Method Interface (I2C_SCMI) [N/m/y/?] n
*
* I2C system bus drivers (mostly embedded / system-on-chip)
*
CBUS I2C driver (I2C_CBUS_GPIO) [N/m/y/?] n
Synopsys DesignWare PCI (I2C_DESIGNWARE_PCI) [Y/n/m/?] y
Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C (I2C_EG20T) [N/m/y/?] n
GPIO-based bitbanging I2C (I2C_GPIO) [N/m/y/?] n
Intel Moorestown/Medfield Platform I2C controller (I2C_INTEL_MID) [N/m/y/?] n
OpenCores I2C Controller (I2C_OCORES) [N/m/y/?] n
PCA9564/PCA9665 as platform device (I2C_PCA_PLATFORM) [N/m/y/?] n
Simtec Generic I2C interface (I2C_SIMTEC) [N/m/y/?] n
Xilinx I2C Controller (I2C_XILINX) [N/m/y/?] n
*
* External I2C/SMBus adapter drivers
*
Diolan U2C-12 USB adapt  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/zconf.lex.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --oldconfig Kconfig
drivers/net/Kconfig:6:warning: environment variable WIFIVERSION undefined
*
* Restart config...
*
*
* Keyboards
*
Keyboards (INPUT_KEYBOARD) [Y/n/?] y
  ADP5588/87 I2C QWERTY Keypad and IO Expander (KEYBOARD_ADP5588) [N/m/y/?] n
  ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander (KEYBOARD_ADP5589) [N/m/y/?] n
  AT keyboard (KEYBOARD_ATKBD) [Y/n/m/?] y
  Atmel AT42QT1070 Touch Sensor Chip (KEYBOARD_QT1070) [N/m/y/?] n
  Atmel AT42QT2160 Touch Sensor Chip (KEYBOARD_QT2160) [N/m/y/?] n
  DECstation/VAXstation LK201/LK401 keyboard (KEYBOARD_LKKBD) [N/m/y/?] n
  GPIO Buttons (KEYBOARD_GPIO) [Y/n/m/?] y
  Polled GPIO buttons (KEYBOARD_GPIO_POLLED) [N/m/y/?] n
  TCA6416/TCA6408A Keypad Support (KEYBOARD_TCA6416) [N/m/y/?] n
  TCA8418 Keypad Support (KEYBOARD_TCA8418) [N/m/y/?] n
  GPIO driven matrix keypad support (KEYBOARD_MATRIX) [N/m/y/?] n
  LM8323 keypad chip (KEYBOARD_LM8323) [N/m/y/?] n
  LM8333 keypad chip (KEYBOARD_LM8333) [N/m/y/?] n
er (I2C_DIOLAN_U2C) [N/m/y/?] n
Parallel port adapter (light) (I2C_PARPORT_LIGHT) [N/m/y/?] n
TAOS evaluation module (I2C_TAOS_EVM) [N/m/y/?] n
Tiny-USB adapter (I2C_TINY_USB) [N/m/y/?] n
*
* Other I2C/SMBus bus drivers
*
ChromeOS EC tunnel I2C bus (I2C_CROS_EC_TUNNEL) [N/m/y/?] (NEW) #
# configuration written to .config
#

Working information on building a kernel

#
# Grab verified boot utilities from ChromeOS.
#
mkdir -p /usr/share/vboot
mount -o ro /dev/sda3 /mnt
cp /mnt/usr/bin/vbutil_* /usr/bin
cp /mnt/usr/bin/dump_kernel_config /usr/bin
rsync -avz /mnt/usr/share/vboot/ /usr/share/vboot/
umount /mnt

probably need this

pacman -S lib32-glibc

prep and make kernel

#
# Fetch ChromeOS kernel sources from the Git repo.
#
apt-get install git-core
cd /usr/src
git clone  https://git.chromium.org/git/chromiumos/third_party/kernel-next.git
cd kernel-next
git checkout origin/chromeos-3.8

#
# Configure the kernel
#
# First we patch ``base.config`` to set ``CONFIG_SECURITY_CHROMIUMOS``
# to ``n`` ...
cp ./chromeos/config/base.config ./chromeos/config/base.config.orig
sed -e \
  's/CONFIG_SECURITY_CHROMIUMOS=y/CONFIG_SECURITY_CHROMIUMOS=n/' \
  ./chromeos/config/base.config.orig > ./chromeos/config/base.config
./chromeos/scripts/prepareconfig chromeos-intel-pineview
#
# ... and then we proceed as per Olaf's instructions
#
yes "" |make oldconfig 

I then did a menuconfig and enabled some file systems support

Then I did a make

New Chrubuntu script + github.

I made some edits after confirming install using the latest official script- https://github.com/jay0lee/chrubuntu-script .

The "one to rule them all" script from Jay's blog is on Google Drive and has not been updated the last time I checked. The new updates/commits to the script support a 64bit filesystem as the Dev and possibly Beta channels(through chrome://help once logged in) provide the Acer C7 with a 64bit kernel and 32bit filesystem(kernel 3.8.11 x86_64 as of writing this).

Feel free to edit my changes. I was trying to update and shrink things a bit, but I am a Wiki newbie. I did not see any area to discuss modules / patches for a custom kernel or the C7 itself, even though it says patches are welcome in the Wiki. If someone could either provide that information to me or put on the Wiki itself, you would have my thanks. UserError (talk) 08:11, 18 September 2013 (UTC)

So there's no real way to 'submit' patches. once you get something working post it to thread on the forums. If you need hosting, and you get someone else to confirm that it works hit me up and I'll host it for you. You can always find me in IRC or on bbs.archlinux GrayHatter (talk) 22:20, 18 September 2013 (UTC)

https://dl.dropboxusercontent.com/u/7751918/youlied.png

it might worth taking the guide out of the c7 chromebook and into a generic solution for having Arch rootfs on Chromebooks without SeaBIOS payload

I've been doing some reading today on how to flash the coreboot seabios to the C7, I'm probably going to tackle some time in the next week. If I do it successfully I'm happy to write the guide for it. This tag is certainly correct, it's poorly written with too many caveats to list; it would be better to start fresh with an ACTUAL Arch installation guide. (( as suggested by User:Dhead )) GrayHatter (talk) 02:27, 21 September 2014 (UTC)

GrayHatter, please read Transitioning the page into a generic Chromebook installation guide. -- Dhead 08:36, 22 September 2014‎
GrayHatter, the Chromebook page now also covers the installation procedure on non SeaBIOS models as part of the general Chromebook#Installation guide so I removed duplicate content (that exist in the Chromebook page, Beginners guide or Grub) and some links that covered in the custom firmware topic. As I see it the C710 page should only cover model specific information like how to disable the hardware write protection, post installation configurations (touchpad xorg.conf.d, different tweaks) and known issues. Having a unified guide for Chromebook will help having one update guide and not countless outdated guides and also push to to collaboration between users if a patched kernel package needed to be maintained for a while. So I believe this is the way to go. Dhead (talk)