You are not logged in.
I see. Thanks dhead and parched. I'll just wait and see what happens then.
Offline
parched, can you break down what are the differences in the 2 kernels that you've placed into the AUR (linux-chromebook and linux-mainline-chromebook)?
Will you continue to release precompiled kernels for linux-mainline-chromebook? I ask this because I see that you have 3.16-1 for linux-chromebook but not linux-mainline-chromebook precompiled at the download page you shared. Compiling on another system isn't an issue but would be more convenient to use if there were a precompiled binary around.
My bad, I thought I was sharing the latest version of linux-mainline-chromebook but I hadn't synced it, I will add it now. At the moment, the only difference between linux-chromebook and linux-mainline-chromebook is the mainline version doesn't have the default console log level changed. dhead is correct, I will next update mainline when 3.17rc1 is released.
Offline
@pegasus21 and anyone else who has been using a C720P (touchscreen) with linux-mainline-chromebook, (or linux-chromebook since the latest version (3.16)):
Has the touchscreen working fine? The only report I have had is from @pegasus21 early in 3.16 that it stopped working after a while. I ask because that patch is being added to 3.17 now, so I want to make sure it is working fine.
Offline
@pegasus21 and anyone else who has been using a C720P (touchscreen) with linux-mainline-chromebook, (or linux-chromebook since the latest version (3.16)):
Has the touchscreen working fine? The only report I have had is from @pegasus21 early in 3.16 that it stopped working after a while. I ask because that patch is being added to 3.17 now, so I want to make sure it is working fine.
Sorry, I haven't noticed if the issue is still present since I hardly use the touchscreen.
I've updated my kernel to linux-mainline-chromebook 3.16-1 due to an inability to suspend more than once on 3.16-rc7. Suspend works beautifully now on 3.16-1.
I'll try to give you some update on the touchscreen issue later.
*Edit* Ok. I've put the system through suspend and resume multiple times and the touchscreen is still working fine on 3.16-1 on extended use. I think it's all good now.
Last edited by pegasus21 (2014-08-15 07:58:03)
Offline
parchedas wrote:@pegasus21 and anyone else who has been using a C720P (touchscreen) with linux-mainline-chromebook, (or linux-chromebook since the latest version (3.16)):
Has the touchscreen working fine? The only report I have had is from @pegasus21 early in 3.16 that it stopped working after a while. I ask because that patch is being added to 3.17 now, so I want to make sure it is working fine.
Sorry, I haven't noticed if the issue is still present since I hardly use the touchscreen.
I've updated my kernel to linux-mainline-chromebook 3.16-1 due to an inability to suspend more than once on 3.16-rc7. Suspend works beautifully now on 3.16-1.
I'll try to give you some update on the touchscreen issue later.
*Edit* Ok. I've put the system through suspend and resume multiple times and the touchscreen is still working fine on 3.16-1 on extended use. I think it's all good now.
Did you have to add anything to the kernel boot params with this kernel? I am using linux-chromebook, but I can only suspend once. The two kernels should be pretty much the same.
Offline
Did you have to add anything to the kernel boot params with this kernel? I am using linux-chromebook, but I can only suspend once. The two kernels should be pretty much the same.
No, you shouldn't need any at all if you are using the latest linux-chromebook (3.16).
Offline
stratosmacker wrote:Did you have to add anything to the kernel boot params with this kernel? I am using linux-chromebook, but I can only suspend once. The two kernels should be pretty much the same.
No, you shouldn't need any at all if you are using the latest linux-chromebook (3.16).
Interesting. I see that tpm_tis is still loading (is this right?). I can get it to suspend (the second+ time) if I unload that module. Which is fine, I just am not sure if this is the correct functionality with the linux-chromebook kernel.
I AM using the patched rom.
Offline
Interesting. I see that tpm_tis is still loading (is this right?). I can get it to suspend (the second+ time) if I unload that module. Which is fine, I just am not sure if this is the correct functionality with the linux-chromebook kernel.
I AM using the patched rom.
Yes, that is correct, I have used a patch from @scot14 to fix the old problem. I haven't used the patched ROM so I can't comment on that, maybe Scot has some input?
Offline
Interesting. I see that tpm_tis is still loading (is this right?). I can get it to suspend (the second+ time) if I unload that module. Which is fine, I just am not sure if this is the correct functionality with the linux-chromebook kernel.
I AM using the patched rom.
Right, it isn't working with the patched rom's. I'd like to work with someone to make another patch to address the problem with the updated roms, so that the vanilla kernel will work with them without needing to blacklist modules, etc. If you have time, we could discuss by email (contact me through my profile), or if you prefer, we could start another thread?
Offline
stratosmacker wrote:Interesting. I see that tpm_tis is still loading (is this right?). I can get it to suspend (the second+ time) if I unload that module. Which is fine, I just am not sure if this is the correct functionality with the linux-chromebook kernel.
I AM using the patched rom.
Right, it isn't working with the patched rom's. I'd like to work with someone to make another patch to address the problem with the updated roms, so that the vanilla kernel will work with them without needing to blacklist modules, etc. If you have time, we could discuss by email (contact me through my profile), or if you prefer, we could start another thread?
PM'd you.
Offline
First, the good news... there might be a way to set developer mode without chromeos: https://sites.google.com/a/chromium.org … n-dev-mode
But this raises the question... Do the newer chromebooks forget they are in developer mode if the battery completely discharges?
Someone told me they let their HP 14 sit for a few weeks, discharging the battery, and then they plugged it in and booted, pressed Ctrl-L, and heard a double beep. But that was it, it didn't boot.
Offline
Yep, the 3.16-1 kernel still requires the blacklisting so the patch isn't working. Hopefully that'll be fixed soon.
Offline
I have got my Acer C720 Chromebook today. My plan is to install Arch linux on it. Only Arch linux, not dual boot.
I have read wiki page https://wiki.archlinux.org/index.php/Ac … Chromebook.
I want to make SeaBIOS default. So, I need to remove write protect screw. Yes I would do.
But the question is that which exactly step I should do it and do I have to power off (completely shut down) the machine (Acer C720 Chromebook).
What if I do it first (after completely shut it down) and turn on the machine to enable developer mode?
the next important question:
What about Acer C720 Chromebook's touchpad with stock kernel 3.16.1? (I mean, without any patch, out of box)
if not working, I am using it with mouse and waiting kernel 3.17.
Last edited by mshan (2014-08-18 08:20:15)
Amazing !
Offline
Although I haven't done it myself, I believe you can do it whenever you want to, just as long as it's before running the script to set SeaBIOS as default. And yes, you should always completely unplug and power off ANY electronic device you plan on opening up.
The touchpad code isn't in the 3.16 line without patches, so you will have to wait until 3.17.
Last edited by SolarBoyMatt (2014-08-18 14:04:25)
Offline
@mshan
And on top of @SolarBoyMatt post there's a tact switch that is kept pressed when the bottom cover is on.
Opening the cover will ensure a loss of power and you don't want for this to happen when your system is running.
Offline
Since ChromeOS works, a 64-bit Arch kernel might also recognize the 4GB. But I don't know. I haven't previously heard of anyone using the 32-bit kernel on newer chromebooks with more than 2GB, which would fit with no one seeming to be familiar with this problem. The wiki describes how to do a 64-bit install, which people here can help with if it doesn't work. Today I also did one using the https://wiki.archlinux.org/index.php/In … ting_Linux instructions, from a Finnix installation. It seems like Arch is the only distro with a non-functional 64-bit installer for the Chromebooks.
Finally had time to do a reinstallation. I did a 64-bit install following the Acer C720 wiki instructions and now htop shows I have 4GB of RAM.
If you contact me through my profile, I can probably work with you to get the kernel patched upstream so that the backlight will work. It would require some simple information from your logs, as well as the 64-bit kernel for testing. Once it's patched upstream, then the patch should flow back into the official arch kernels.
Emailing you now.
Offline
First of all, I want to thank everyone for their work on this, I cannot wait to run only Arch on my HP 14.
My biggest problem right now is the sensitivity of the touchpad. I have applied the settings mentioned early in this thread and it definitely improved, however, in Arch, my touchpad is nowhere near as nice as in Chromeos. In Arch, my touchpad is not sensitive enough to use the tip of my finger, whereas it works beautifully in Chromeos. Does anyone have any recommendations to improve that, or is that just a limitation of the driver at this point?
Offline
Emailing you now.
My response isn't being delivered, is that still a valid return address?
Offline
My response isn't being delivered, is that still a valid return address?
Oh, sorry. I've updated my email now.
Offline
Two things I've noticed today:
* VA-API is completely broken (at least when playing in totem), I think this probably introduced in kernel 3.16.
see https://bugzilla.kernel.org/show_bug.cgi?id=79261
and https://bbs.archlinux.org/viewtopic.php?id=184857
* Playing flash video in Chromium (chromium-pepper-flash) when SNA is set will freeze the browser every few minutes.
UXA is much better, the browser wouldn't freeze at all when flash is in fullscreen mode (but the browser will freeze once in a while with no regards to flash, see one of my previous posts).
Last edited by dhead (2014-08-19 06:13:28)
Offline
Two things I've noticed today:
* VA-API is completely broken (at least when playing in totem), I think this probably introduced in kernel 3.16.
see https://bugzilla.kernel.org/show_bug.cgi?id=79261
and https://bbs.archlinux.org/viewtopic.php?id=184857* Playing flash video in Chromium (chromium-pepper-flash) when SNA is set will freeze the browser every few minutes.
UXA is much better, the browser wouldn't freeze at all when flash is in fullscreen mode (but the browser will freeze once in a while with no regards to flash, see one of my previous posts).
I'm running xfce on SNA and it works perfectly on linux-mainline-chromebook 3.16-1.
Youtube videos are fully accelerated within firefox and playing without any freezing even with 1080p videos.
Last edited by pegasus21 (2014-08-19 13:23:45)
Offline
Hey guys,
After accidentally hitting the power button one too many times, I disabled that functionality in /etc/systemd/logind.conf, but it got me wondering if there is any way to imitate Chrome OS' behavior for the power button, where holding it will initiate a standard power off, and shorter hold does a suspend. I'm sure that GNOME or KDE can be configured to pull up a shutdown menu when the button is pressed, but not all of us use DE's. From skimming through the Chromium OS developer wiki and source code, it looks like Google baked this functionality into Chrome OS' power management stack, so it isn't really feasible to patch/import it in directly.
Does anyone have any idea if this is even possible to do on Arch? I've been looking into acpid since it's fairly scriptable, but I'm coming up short as far as anyone else trying to achieve this functionality on any machine at all. Another, simpler solution would have it check for two power key presses in a row, which I might try to do if pressing and holding turns out to be a dead end...
It's not vital for me by any means, but it would be nice to have a functional power button without it being so easy to trigger.
Thoughts?
Last edited by SolarBoyMatt (2014-08-19 16:56:53)
Offline
I'm running xfce on SNA and it works perfectly on linux-mainline-chromebook 3.16-1.
Youtube videos are fully accelerated within firefox and playing without any freezing even with 1080p videos.
Are you sure it's flash ? for quite a while Youtube is default to WEBM VP9.
Offline
pegasus21 wrote:I'm running xfce on SNA and it works perfectly on linux-mainline-chromebook 3.16-1.
Youtube videos are fully accelerated within firefox and playing without any freezing even with 1080p videos.
Are you sure it's flash ? for quite a while Youtube is default to WEBM VP9.
Do you have any sample url?
Offline
@pegasus21
I'm not sure why you want a link, but here:
GeekBeat Live #144 Uncut, it defaults to WEBM VP9, see image.
The latest EEVblog, it defaults to MP4 AVC probably because it's a more recent upload, see image.
Edit: forgot to emphasize that both are using the HTML5 tag so no flash player.
Last edited by dhead (2014-08-20 04:47:49)
Offline