Just got arch up and running on a C710. Touchpad doesn't work though. I used GrayMatter's install script - is there an additional step I need to take to enable the touchpad?
For what it's worth, the device shows up in xinput, and mouse clicks work. I just can't move the cursor.
Installed kcm-touchpad and it's working.
Do you know of a way off the top of your head to differentiate C7 from the C710 from inside the OS?
]]>For what it's worth, the device shows up in xinput, and mouse clicks work. I just can't move the cursor.
Installed kcm-touchpad and it's working.
]]>Hi guys, I installed Bridge Linux 64 Bit LXDE on a coreboot flashed c710 (C710-10074G01ii) with no real hiccups except for a few:
Suspend: Reboot instead of resume, I tried some of the methods listed from the guide below with no luck.
https://wiki.archlinux.org/index.php/Ac … ChromebookFn Keys: I used the hotkey guide listed in the same 720 wiki above and it didn't seem to do anything.
I know that this model of the c710 is unique, I was wondering if there was anyone who had similar issues for this model and had a fix or can point me in the right direction? It's a great piece of hardware for the price.
Extra note: I'm fairly experienced with *nix, I usually run LXDE but have some XFCE services running as well but I'd like to keep my distro light if possible.
Thanks guys! I've been lurking for a while but google has only taken me so far on these issues.
FYI; C7 != C710.
You probably want to start a new thread. These two models are drastically incompatible for the similarity in numbers.
But from what I know if `xev` doesn't see the Fn key (usually mod{1-4}) then you are probably out of luck. Some times the bios handles that conversion but you'll still see the correct keypress with xev.
]]>Suspend: Reboot instead of resume, I tried some of the methods listed from the guide below with no luck.
https://wiki.archlinux.org/index.php/Ac … Chromebook
Fn Keys: I used the hotkey guide listed in the same 720 wiki above and it didn't seem to do anything.
I know that this model of the c710 is unique, I was wondering if there was anyone who had similar issues for this model and had a fix or can point me in the right direction? It's a great piece of hardware for the price.
Extra note: I'm fairly experienced with *nix, I usually run LXDE but have some XFCE services running as well but I'd like to keep my distro light if possible.
Thanks guys! I've been lurking for a while but google has only taken me so far on these issues.
]]>Thanks again!
]]>The only problem is that it kernel panics upon shutdown, I'm guessing due to a version mismatch between the kernel and systemd
]]>Thanks for the script! I'm getting a shared library error from pacman when it's installing packages.
/usr/bin/pacman: error while loading shared libraries: libgssapi_krb5.so.2: cannot open shared object file: No such file or directory
Do you know when this appears? Before or after pacstrap runs?
]]>/usr/bin/pacman: error while loading shared libraries: libgssapi_krb5.so.2: cannot open shared object file: No such file or directory
(0) enable dev mode
(1) connect to wifi
(2) login as chronos then su for root in tty2
(3) # wget https://raw.github.com/GrayHatter/archC7/master/installarch.sh
(4) # bash installarch.sh
(5) reboot and wait for chromeOS to repair itself
(6) repeat steps 1-3
(7) done
If you use this script, let me know. Especially if you have problems/comments/solutions!
]]>I'm running Ubuntu via Crouton for now on my C7, with upgraded SSD to 256GB (Crucial M4).
As for your question, yes with X and Chromium PLS!!
]]>I'm torn between installing X and chromium, or doing nothing and leaving a super basic install (the arch way). It'd be no contest to leave it basic, but I've been thinking that anyone who would use this script (vs installing it themselves) would want to use X on the C7.
Thoughts?
]]>Thanks for your reply. I was able to successfully compile the kernel after changing the CFlag as you recommended. I was also able to get vbutil to create and verify the new package. I think your problem--assuming you got the "Error reading kernel file" message--is that the script is looking for the new kernel in /boot. So I changed the "--vmlinux" argument to "--vmlinux vmlinux" since the compiled kernel file was sitting in my current directory (/usr/src/kernel-next).
After that everything seemed fine except the resulting kernel is too large for my /dev/sda6 partition, which lsblk reports as 16M. The current 3.4.x kernel is under 17M so the partition size is fine. I've tried recompiling the new kernel using localmodconfig, thinking that I was building it with way more device,etc. support than I needed. This, however only reduced the size ~ 400Kb. The latest build is still clocking in at 241.7M...
Do you mind sharing your compiled kernel size? I'm hoping I'm doing something wrong at this point, possibly with my kernel config, rather than being SOL because of my kernel partition size...
-JLR
]]>Been a long time lurker but never really bothered registering until today, so here goes first post.
Thought I'd respond here seeing as I'm using Arch on my Chromebook C7. I've installed another 2GB of DDR3 and replaced its HDD with an old 60GB SSD from my main PC. Runs nice and snappy, perfect for uni work.
Anyway I was originally using ChrUbuntu and switched to Arch back in May or whenever I first saw this guide: https://wiki.archlinux.org/index.php/Acer_C7_Chromebook
It was around the same time I started using Arch on my main rig as I moved from Linux Mint (thought I could do with going with an unstable/rolling release distro so I can learn how to fix things and get myself out of problems).
I kinda went away on a holiday and got back and wanted to play some movies on my chromebook and noticed then that the graphics performance was terrible. Not sure about this but I'd go to play a game like Minecraft for example and I'd get something like:
Gen6+ requires Kernel 3.6 or later.
Anyway figured I'd need to update my kernel as I was using 3.4.0 so I tried following the steps to compile kernel 3.8.11 as discussed on the wiki talk page. I got a couple of steps further than jlreid above with his problem:
Hey all,
I've been running an Arch 64-bit build on my acer C7 for some time now--somehow I managed to install it with less fuss than the wiki instructions but that's for later. What I'm trying to do is update the kernel from 3.4.0 to 3.8.x but keep getting a toolchain error when using the instructions on the wiki discussion page. Has anyone recently done this kernel update? I'm sure I'm missing something obvious.
Were you having a problem where it was compiling marking warnings as errors? I managed to get past that problem by changing -Werror to -Wno-error in the Makefile under CFLAGS.
Also I had to install i386 packages for libssl and libc6. Can't remember the names of those packages for Arch. See here: http://superuser.com/questions/583269/c … tead-3-4-0
Anyway, kernel compiled fine after that but I couldn't vbutil_kernel on the output, kept up coming up as an invalid file.
I got frustrated with the device after that and figured I'd go ahead and try and flash it with the coreboot supplied by John Lewis.
I supposed if I broke the device I guess I'd go ahead and buy a bus pirate and learn how to JTAG the device. (In first year Computer Engineering and Computer Science so I'd figured I should probably learn to do this).
Worked straight up and got SeaBIOS running on it. I'd recommend giving it a go if you are not worried about the risk of bricking the device (not sure if that's the right term as you can still fix it with the right tools), although in my frustration on trying to update the kernel I ended up loosing my Arch partition and used flashrom in Chrome OS.
Anyway all happy now and I've got Arch with the latest upstream kernel 3.12.1-3, when I installed a window manager (I like E17) I had problems with the touchpad simply not working.
I fixed this by adding the following modules:
cat /etc/modules-load.d/modules.conf
loop
lp
i2c-i801
i2c-dev
chromeos-laptop
cyapa
And its all happy days.
Actually funny story about the device, a mate first bought it at the beginning of this year thinking he could install Windows 7 on it himself. He saw it was running an Celeron 847 and put two and two together thinking it'd just act like a normal laptop and usb boot a Windows installer. I've yet to convert him to use Linux instead but he ended up convincing me to buy it off him for $100. I needed a new laptop anyway for uni, so I took and thought I'd have a play around on it. Can't complain for the price. But I guess now I could sell it back to him seeing as its capable of doing what he originally wanted. But nah it's brilliant for my needs now.
Been seeing a few C710s pop up on ebay for around $100-$150, thinking of getting some and re-selling them to mates in my programming class with SeaBIOS and Arch and maybe with an SSD and a little more RAM.
TL;DR: Tried to update kernel by getting 3.8.11 to /dev/sda6, failed, got annoyed and flashed it with http://johnlewis.ie/coreboot-parrot-sea … 102013.rom and it worked perfectly. Essentially just another success story of using coreboot on the device.
]]>