Acer C720/C720P Chromebook

Strike0 · 2014-03-03 20:46:16

Hi, I am interested in the device, have been skimming over this thread and also read the (already great) wiki page about the device.

I have one question. Should be an easy one, but I could not picture it from what I read: Take it some of you have installed Arch as a dual boot. I understand you have to press " CTRL-L" to get to the seabios, ok. Is that still in developer mode or can you turn developer mode _off_ again, after having installed the dual-boot Arch?

TheBiloi · 2014-03-04 05:33:18

Strike0 wrote:

Hi, I am interested in the device, have been skimming over this thread and also read the (already great) wiki page about the device.
I have one question. Should be an easy one, but I could not picture it from what I read: Take it some of you have installed Arch as a dual boot. I understand you have to press " CTRL-L" to get to the seabios, ok. Is that still in developer mode or can you turn developer mode _off_ again, after having installed the dual-boot Arch?

You just need to press enter or space or whatever instead of Ctrl+L and it'll take you through some simple prompts to easily go back to Chrome OS if you so choose.

Strike0 · 2014-03-04 06:46:59

Thanks for your quick answer. To clarify: being able to press "CTRL+L" (or not) to make that choice means that developer mode stays enabled?

TheBiloi · 2014-03-05 05:49:08

If you do not press Ctrl+L, instead choosing to reinstall Chrome OS, you will leave developer mode and have a clean Chrome OS install. From there, you'll have to re-enable developer mode.

tumas · 2014-03-05 12:41:36

Well u guys are obviously talking past each other
Yes you need to have developer mode enabled in order to press the ctrl + l combination. Anyway if you choose to disable developer mode the chromebook would reset itself. So there is no point in doing this.

By the way: Did anyone notice any difference since the last past updates of the system? I did an update yesterday and all the special keys seems to be sort of "newly detected".

Last edited by tumas (2014-03-05 12:46:58)

Strike0 · 2014-03-05 19:02:20

Thanks TheBiloi and tumas. I get it now.

(last thread question please see post #80 above)
edit: for a typo

Last edited by Strike0 (2014-03-07 20:19:31)

tumas · 2014-03-06 19:12:35

Everything is working fine on my system (HP Chromebook 14 with KDE) but i am unable to get bluetooth to work. Am i the only one with this issue or could it be an hp specific problem?!

vanboxel · 2014-03-07 03:47:49

@madx: Did you get a chance to test out the internal microphone? I've found that it only records if I set the "Internal Mic Boost" to 0 in alsamixer. I suspect this is releated to the issue mentioned here about the sound card doing things in a funny way. They seem to have resolved it, but I'm not sure how to translate that back into Arch. Only being able to record at very low volume (with substantial background noise) is somewhat limiting.

Has anyone else run into this, and did you have any workarounds? I'm toying with installing pulseaudio as I saw that seemed to work for a similar issue with Chrubuntu on the C720, but I haven't gotten that working. So I'm open to ideas or confirmation.

Xenphor · 2014-03-07 11:39:15

I think the sound card and alsa/pulse have some issues because with either one I seem to have problems. I've tried just using alsa with no configuration other than what is in the wiki:

/etc/modprobe.d/alsa.conf
options snd_hda_intel index=1

I get sound and everything but I can't help but notice an occasional pop or skip in the audio. It's hard to know for sure because of the bad speakers but I don't notice it that often.

Another thing is that I've been getting these errors in the console when using mame and dosbox:
lib pcm.c:7843:(snd_pcm_recover) underrun occurred

I still haven't found out how to fix that or if it's some issue with sdl. It seems like a similar problem found here http://ubuntuforums.org/showthread.php?t=2033089 so I tried messing with dsnoop and dmix values but couldn't get the error to go away. I did notice that using aoss with mame seemed to prevent any errors.

I tried installing pulseaudio but again, I couldn't help but notice the occasional hiccup in audio so I'm not sure if it's actually helping anything.

I also tried installing oss but the osstest command couldn't detect my sound card.

Last edited by Xenphor (2014-03-07 11:39:58)

NewChromebook · 2014-03-13 21:06:19

You can make the Seabios by default and don't need to use Ctrl L at boot and this is supposed to work in other chromebooks as well

Divulged this evening by Duncan Laurie on the coreboot mailing list:

If you want to boot SeaBIOS by default and you have unlocked the SPI flash write protection you can set flags in the (write protected) “GBB” flash region that will make it boot legacy mode by default.

In Chrome OS there is a script called set_gbb_flags.sh that will do this for you. Run the script with no arguments to get a list of possible flags and then to enable short dev mode screen (1 second timeout) followed by default legacy mode boot you could use these flags:

GBB_FLAG_DEV_SCREEN_SHORT_DELAY 0×00000001
GBB_FLAG_FORCE_DEV_SWITCH_ON 0×00000008
GBB_FLAG_FORCE_DEV_BOOT_LEGACY 0×00000080
GBB_FLAG_DEFAULT_DEV_BOOT_LEGACY 0×00000400

set_gbb_flags.sh 0×489

if you try this let me know and leave feedback at http://www.newchromebook.com/how-to/mak … acer-c720/

SORE-LOSER · 2014-03-14 22:24:27

So is the touchpad module in the kernel officially now? I rolled back to 3.12 and have been skipping kernel upgrades.

The wiki page still mentions using the Touchpad Kernel Module script...

tumas · 2014-03-15 17:28:58

NewChromebook wrote:

You can make the Seabios by default and don't need to use Ctrl L at boot and this is supposed to work in other chromebooks as well
Divulged this evening by Duncan Laurie on the coreboot mailing list:
If you want to boot SeaBIOS by default and you have unlocked the SPI flash write protection you can set flags in the (write protected) “GBB” flash region that will make it boot legacy mode by default.
In Chrome OS there is a script called set_gbb_flags.sh that will do this for you. Run the script with no arguments to get a list of possible flags and then to enable short dev mode screen (1 second timeout) followed by default legacy mode boot you could use these flags:
GBB_FLAG_DEV_SCREEN_SHORT_DELAY 0×00000001
GBB_FLAG_FORCE_DEV_SWITCH_ON 0×00000008
GBB_FLAG_FORCE_DEV_BOOT_LEGACY 0×00000080
GBB_FLAG_DEFAULT_DEV_BOOT_LEGACY 0×00000400
set_gbb_flags.sh 0×489
if you try this let me know and leave feedback at http://www.newchromebook.com/how-to/mak … acer-c720/

I would really love to try this out, but i have one question left: If i have chrome os and archlinux as dualboot, will i be still able to use chrome os?

EDIT: I just set the flags on my hp chromebook 14 and this is working great! Thanks a lot. For those who are also curious: After this step you can still boot chrome os by hitting the ctrl + d combination.

Last edited by tumas (2014-03-17 15:51:39)

nariox · 2014-03-19 03:51:32

NewChromebook wrote:

You can make the Seabios by default and don't need to use Ctrl L at boot and this is supposed to work in other chromebooks as well
Divulged this evening by Duncan Laurie on the coreboot mailing list:
If you want to boot SeaBIOS by default and you have unlocked the SPI flash write protection you can set flags in the (write protected) “GBB” flash region that will make it boot legacy mode by default.
In Chrome OS there is a script called set_gbb_flags.sh that will do this for you. Run the script with no arguments to get a list of possible flags and then to enable short dev mode screen (1 second timeout) followed by default legacy mode boot you could use these flags:
GBB_FLAG_DEV_SCREEN_SHORT_DELAY 0×00000001
GBB_FLAG_FORCE_DEV_SWITCH_ON 0×00000008
GBB_FLAG_FORCE_DEV_BOOT_LEGACY 0×00000080
GBB_FLAG_DEFAULT_DEV_BOOT_LEGACY 0×00000400
set_gbb_flags.sh 0×489
if you try this let me know and leave feedback at http://www.newchromebook.com/how-to/mak … acer-c720/

Nice!
By the way, is there a way of running this command on Arch? I've wiped ChromeOS... ):
I'll try running from a ChromiumOS live USB and will report the results.

nariox · 2014-03-20 12:50:05

nariox wrote:

I'll try running from a ChromiumOS live USB and will report the results.

No luck, seems like they don't pack the necessary scripts and files on generic Chromium OS builds...

EDIT: Word of caution. I've tried to use the recovery media and chroot to run these commands, but they've rendered my system unbootable ):
I'll add how to make the legacy boot default to the wiki.

Last edited by nariox (2014-03-20 13:54:33)

nariox · 2014-03-21 03:26:26

Silly me, I forgot that I had the write-protect screw on. Instead of writing the flags, it was corrupting it. Removing the screw solved it for me.

Since I corrupted it, I had to recover my system and reinstall it. I've ran the script and my system now boots after 1 second directly into Arch!
My guess then is that you could run the command from a chroot (as long as you bind proc, sys etc), but I can't guarantee.

daxofdeath · 2014-03-22 20:34:56

With the changes from post #70, the touchpad script fix ran all the way through with no errors, but the touchpad is still not working. I'm on an HP 14. Anyone else have this problem?

ciarlill · 2014-03-24 14:40:54

Is anyone else still having issues with the sound card coming back from suspend? I have setup the cros-acpi-wakeup.conf tmpfile and and the cros-sound-suspsend system-sleep script as suggested on the wiki. Also have tpm_tis.force=1 in my boot parameters.

Still maybe 80% of the time the machine comes back from suspend the card is not active.

Just wondering if anyone else is experiencing this.

nariox · 2014-03-24 15:34:24

ciarlill wrote:

Is anyone else still having issues with the sound card coming back from suspend? I have setup the cros-acpi-wakeup.conf tmpfile and and the cros-sound-suspsend system-sleep script as suggested on the wiki. Also have tpm_tis.force=1 in my boot parameters.
Still maybe 80% of the time the machine comes back from suspend the card is not active.
Just wondering if anyone else is experiencing this.

Have you tried the solution from the wiki? Create "/etc/modprobe.d/alsa.conf" with

output=options snd_hda_intel index=1

I haven't noticed any issues with sound playback, but I can't increase the Microphone Boost. There seems to be a DC Bias that prevents the microphone from being boosted beyond a certain point.

Last edited by nariox (2014-03-24 15:35:13)

ciarlill · 2014-03-24 17:39:19

nariox wrote:

Have you tried the solution from the wiki? Create "/etc/modprobe.d/alsa.conf" with
output=options snd_hda_intel index=1
I haven't noticed any issues with sound playback, but I can't increase the Microphone Boost. There seems to be a DC Bias that prevents the microphone from being boosted beyond a certain point.

Yes but mine reads exactly like the one in the wiki:

options snd_hda_intel index=1

Again the only time there is a problem is coming back from suspend. When I open the laptop I cannot even launch alsamixer. I also tried manually echoing the codes from cros-sound-suspend.sh and get "device not found".

nariox · 2014-03-25 01:19:42

ciarlill wrote:

nariox wrote:
Have you tried the solution from the wiki? Create "/etc/modprobe.d/alsa.conf" with
output=options snd_hda_intel index=1
I haven't noticed any issues with sound playback, but I can't increase the Microphone Boost. There seems to be a DC Bias that prevents the microphone from being boosted beyond a certain point.
Yes but mine reads exactly like the one in the wiki:
options snd_hda_intel index=1
Again the only time there is a problem is coming back from suspend. When I open the laptop I cannot even launch alsamixer. I also tried manually echoing the codes from cros-sound-suspend.sh and get "device not found".

Funny, what DE are you using? I'm using GS with no problems on audio.

ciarlill · 2014-03-25 14:24:39

I am using BSPWM as Window Manager and SDDM as the Display Manager. Oddly enough I have not been able to reproduce this in the past day even though it has been plaguing me at random times before that. I am wondering if it might not be related to leaving a browser active during suspend, which might have control of the card. Just a shot in the dark though and not a real issue until I can more reliably reproduce it.

thanks

nariox · 2014-03-25 14:29:40

ciarlill wrote:

I am using BSPWM as Window Manager and SDDM as the Display Manager. Oddly enough I have not been able to reproduce this in the past day even though it has been plaguing me at random times before that. I am wondering if it might not be related to leaving a browser active during suspend, which might have control of the card. Just a shot in the dark though and not a real issue until I can more reliably reproduce it.
thanks

Hmm, that seems possible. I'm guessing you are not using pulseaudio. Have you tried reloading the alsa modules?

# rmmod snd-hda-intel && modprobe snd-hda-intel

krullig · 2014-03-31 14:34:40

New here...

Wondering if anyone is using Enlightenment 0.18?
I'm getting black windows.

nariox · 2014-03-31 14:43:06

krullig wrote:

New here...
Wondering if anyone is using Enlightenment 0.18?
I'm getting black windows.

Could you run E18 with:
exec enlightenment_start &> ~.e.log.txt

And paste the log into pastebin?

foolius · 2014-04-02 09:04:44

Hi,

I have trouble getting the wifi to run.
Do I have to install a driver or firmware to get it running?
I think this would be mentioned in the great wiki page, but it isn't so I'm not sure, if this is the correct way.

Thanks for your time!

Arch Linux

#76 2014-03-03 20:46:16

Re: Acer C720/C720P Chromebook

#77 2014-03-04 05:33:18

Re: Acer C720/C720P Chromebook

#78 2014-03-04 06:46:59

Re: Acer C720/C720P Chromebook

#79 2014-03-05 05:49:08

Re: Acer C720/C720P Chromebook

#80 2014-03-05 12:41:36

Re: Acer C720/C720P Chromebook

#81 2014-03-05 19:02:20

Re: Acer C720/C720P Chromebook

#82 2014-03-06 19:12:35

Re: Acer C720/C720P Chromebook

#83 2014-03-07 03:47:49

Re: Acer C720/C720P Chromebook

#84 2014-03-07 11:39:15

Re: Acer C720/C720P Chromebook

#85 2014-03-13 21:06:19

Re: Acer C720/C720P Chromebook

#86 2014-03-14 22:24:27

Re: Acer C720/C720P Chromebook

#87 2014-03-15 17:28:58

Re: Acer C720/C720P Chromebook

#88 2014-03-19 03:51:32

Re: Acer C720/C720P Chromebook

#89 2014-03-20 12:50:05

Re: Acer C720/C720P Chromebook

#90 2014-03-21 03:26:26

Re: Acer C720/C720P Chromebook

#91 2014-03-22 20:34:56

Re: Acer C720/C720P Chromebook

#92 2014-03-24 14:40:54

Re: Acer C720/C720P Chromebook

#93 2014-03-24 15:34:24

Re: Acer C720/C720P Chromebook

#94 2014-03-24 17:39:19

Re: Acer C720/C720P Chromebook

#95 2014-03-25 01:19:42

Re: Acer C720/C720P Chromebook

#96 2014-03-25 14:24:39

Re: Acer C720/C720P Chromebook

#97 2014-03-25 14:29:40

Re: Acer C720/C720P Chromebook

#98 2014-03-31 14:34:40

Re: Acer C720/C720P Chromebook

#99 2014-03-31 14:43:06

Re: Acer C720/C720P Chromebook

#100 2014-04-02 09:04:44

Re: Acer C720/C720P Chromebook

Board footer