Acer Chromebook CB5-311 mainline

[reey]

@vman if I try to compile linux-armv7 from my PKGBUILD from github (where I activated LPAE) I'm getting an error while compiling..
I'm not sure if I need to activate some more options.. I'm also asked for some missing options in my config, which I all just answered with [ENTER]..

edit: I removed some MELLANOX Ethernet options from my config and compiling works..
Uploaded Kernel 4.18.13 with LPAE here: https://github.com/reey/PKGBUILDs/releases/tag/v4.18.13

I can confirm that slow wifi.. I'm just getting about 20Mbit/s and with Chrome OS I can utilize my full internet bandwith at about 100Mbit/s.. I've tested this in my 5GHz wifi, I will try the same later in my 2,4GHz network..

[reey]

So I've compiled a working kernel 4.19 and uploaded it here: https://github.com/reey/PKGBUILDs/releases/tag/v4.19.0
I've compiled it with LPAE but for some reason I've only got 2GB of RAM..

This shows, that the kernel was compiled with LPAE:
$this->bbcode_second_pass_code('', '[alarm@alarm ~]$ cat /proc/config.gz | gunzip | grep LPAE
CONFIG_ARM_LPAE=y
# CONFIG_IOMMU_IO_PGTABLE_LPAE is not set
[alarm@alarm ~]$')

Any idea on what could have gone wrong?

[NoDiskNoFun]

Hey,

after i messed up my Arch installation i tried to reinstall linux. I used the script i provided before, but i am unable to start any acclerated app anymore. glxinfo shows that i am using nouveau driver but 0MB VRAM. I am on Mesa 18.2.5 now and i wanted to ask you if you updated your arch and if yes did it work anyway?

Apps that crashed:
Gnome-shell
chromium (core dumped/breakpoint dump)
kodi (unable to create gui)
xfce4 (Unable to load a failsafe session. Unable to determine failsafe session name. Possible causes: xfconfd isn't running (D-Bus setup problem); environment variable $XDG_CONFIG_DIRS is set incorrectly (must include "/etc"), or xfce4-session is installed incorrectly.)

Apps that do work:
glxgears (with vsync=off gives me 600fps but about 80% cpu load)

[edit]
after i updated kernel to 4.19 (from reey) glxinfo shows VMWare as Vendor and llvmpipe as device. Now i am really confused oO

[edit2]
seems like most programms gives segmantation fault. How could that be? I tried different kernels and disabled swap and zswap and re-enabled it again but no changes =/

[edit3] WTF! I commented last_scratches out and rerun that script. That did the trick. But how da fuq could that be? maybe it isnt a good idea to create a swapfile? every other change inside this function didnt seem to be heavy enough to brick half of the system. @vman @reey: would be nice if you could take a look at this section and tell me what i did wrong.

[edit4] After removing the lines that would create a swapfile the script runs flawlessly.

[mrala]

Hello,
again praise you for you effort. (I re-read the discussion from the begining.)

@reey please can you write in short how to make it work from SD/USB. I'll be so thankfull !
I promise to write in detail. (I have tried in the past without success.)
I see two "Works fine" (tm) here "v4.15.8" and "v4.18.13 with LPAE":
https://github.com/reey/PKGBUILDs/releases

https://patchwork.freedesktop.org/series/38712/
With this what are the chances this device is "officialy" supported Arch Linux Arm ?
(how one of the nicest chromebook is missed so far)

I want to do an image (xfce) that can be just flashed/dd-ed to SD/USB.
What do you think of that ?

Thank you very much. (Excuse my english.)

[reey]

@NoDiskNoFun
my Output of glxinfo looks like this:
$this->bbcode_second_pass_code('', '
$ glxinfo | head -n 100
name of display: :0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_no_error,
GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float,
GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample,
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB,
GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_no_config_context,
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read,
GLX_SGI_swap_control
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_context_flush_control, GLX_ARB_create_context,
GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness,
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB,
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age,
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read,
GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile,
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB,
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age,
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method,
GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read,
GLX_SGI_swap_control, GLX_SGI_video_sync
Extended renderer info (GLX_MESA_query_renderer):
Vendor: NVIDIA (0x10de)
Device: tegra (0x0)
Version: 18.2.3
Accelerated: yes
Video memory: 0MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.3
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: NVIDIA
OpenGL renderer string: tegra
OpenGL core profile version string: 4.3 (Core Profile) Mesa 18.2.3
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend,
GL_AMD_performance_monitor, GL_AMD_seamless_cubemap_per_texture,
GL_AMD_shader_trinary_minmax, GL_ANGLE_texture_compression_dxt3,
GL_ANGLE_texture_compression_dxt5, GL_ARB_ES2_compatibility,
GL_ARB_ES3_1_compatibility, GL_ARB_ES3_2_compatibility,
GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays, GL_ARB_base_instance,
GL_ARB_bindless_texture, GL_ARB_blend_func_extended,
GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture,
GL_ARB_clip_control, GL_ARB_color_buffer_float,
GL_ARB_compressed_texture_pixel_storage, GL_ARB_compute_shader,
GL_ARB_compute_variable_group_size, GL_ARB_conditional_render_inverted,
GL_ARB_conservative_depth, GL_ARB_copy_buffer, GL_ARB_copy_image,
GL_ARB_cull_distance, GL_ARB_debug_output, GL_ARB_depth_buffer_float,
GL_ARB_depth_clamp, GL_ARB_derivative_control, GL_ARB_direct_state_access,
GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend,
GL_ARB_draw_elements_base_vertex, GL_ARB_draw_indirect,
GL_ARB_draw_instanced, GL_ARB_enhanced_layouts,
GL_ARB_explicit_attrib_location, GL_ARB_explicit_uniform_location,
GL_ARB_fragment_coord_conventions, GL_ARB_fragment_layer_viewport,
GL_ARB_fragment_shader, GL_ARB_framebuffer_no_attachments,
GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB,
GL_ARB_get_program_binary, GL_ARB_get_texture_sub_image,
GL_ARB_gpu_shader5, GL_ARB_gpu_shader_fp64, GL_ARB_gpu_shader_int64,
GL_ARB_half_float_pixel, GL_ARB_half_float_vertex,
GL_ARB_indirect_parameters, GL_ARB_instanced_arrays,
GL_ARB_internalformat_query, GL_ARB_internalformat_query2,
GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment,
GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multi_draw_indirect,
GL_ARB_occlusion_query2, GL_ARB_pipeline_statistics_query,
GL_ARB_pixel_buffer_object, GL_ARB_point_sprite,
GL_ARB_polygon_offset_clamp, GL_ARB_program_interface_query,
GL_ARB_provoking_vertex, GL_ARB_query_buffer_object,
GL_ARB_robust_buffer_access_behavior, GL_ARB_robustness,
GL_ARB_sample_shading, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map,
GL_ARB_seamless_cubemap_per_texture, GL_ARB_separate_shader_objects, ')
I've got no experience using swap files, so I can't help you with that..

@mrala
Maybe I can write some instructions on the weekend for you on how to install to an SD card.
But actually there is not much of a difference than installing to the internal flash..
First of all I would start by creating a SD card with the kali image from here: https://images.offensive-security.com/a ... yan.img.xz (for some reason nyan is missing on this page: https://www.offensive-security.com/kali ... rm-images/)
And try to boot up that image. I know that you don't want to run kali, but this will give you a SD card with the correct partition layout.
Now you could try to run the script from here: https://github.com/RaumZeit/LinuxOnAcerCB5-311
make sure that you choose the correct device:
sudo bash archlinux.sh /dev/sda
or
sudo bash archlinux.sh /dev/mmcblk1

[NoDiskNoFun]

@reey thanks, but i fixed it already. Seems like chromeos wont create a swapfile rather than doing some magic ***** which breaks some other stuff, dunno. Anyways. Removing these two lines from the script did it. Script is now working fine and also there are now three versions of it. One for Gnome, one for KDE und one for XFCE4.


@mrala
Here is my fork which is more updated than RaumZeit's script
https://github.com/NoDiskNoFun/LinuxOnAcerCB5-311

[vman]

@mrala: Working images that can just be flashed to a card or stick are nice for experiments, and to try out how well things are working - but for a proper setup I very much prefer scripts/ instructions. Advantages: you can see what's happening, and the sources they're installing stuff from probably have higher reputation than "some guy from a forum" (don't take this personal!). Also such methods don't have to be updated that often, while, if not broken, still giving you an up-to-date system.

@reey
Talking kernels: I'm still running 4.18.0 compiled on 28 September. I'd like to try something new, and see if I'd also run into the 2 GByte/ LPAE problem, but I'm too busy with other stuff right now. Also, I'm not expecting too much of an improvement from a slightly newer kernel. The system is pretty much doing what it is supposed to be doing right now. Things like perfect video playback (like in ChromeOS), standby-mode, or reliable fast wifi might just never be working with proper GNU/Linux on our hardware.

[vman]

Hi @reey and everyone,

this weekend I thought I'd give Linux 4.20 a shot, since it's almost finished. Here are my logs from 4.20rc6:

https://www.freimarkt.org/nouveau/journal.4.20rc6.html

I used unpatched kernel source, and it still booted with a blank screen. In addition I also encountered the problem with 2 GByte RAM only. It's a shame, because I still like the feel of this device!

[reey]

I had some time today and created linux-nyan and a linux-nyan-rc package in my PKBUILD.
Kernel 4.19.10 and 4.20-rc7 are both compiling fine with the drm-don-t-link-DP-aux-i2c-adapter-to-the-hardware-device-node.patch patch and are booting up fine without a blank screen..
The i2c-of-Try-to-find-an-I2C-adapter-matching-the-parent.patch patch, @vman linked some time ago as a replacement for the other patch, isn't solving the blank screen issue for me..

The only problem at the moment is, that I'm still only able to access 2 of my 4GB of memory when compiling with LPAE..
I don't know what is causing this with 4.18 I had the 4GB..

[mrala]

Thank you all.
Kali images work.I wish there was Arch images that just work (tm) like that - dd and done.

Unfortunately I don't understand this 2000+ line of code scripts.

My assumptation was to :
1. create gpt as per the archlinuxarm.org instructions (or use the kali one)
2. put precompiled kernel in the kernel partition.
3. put ready-made rootfs in the rootfs partition.
4. boot

https://github.com/RaumZeit/LinuxOnAcerCB5-311
Isn't this installing the 3.10 ChromeOS kernel ?

If something that used to work is broken in later kernel it is regression why you don't report it here:
http://lists.infradead.org/mailman/list ... arm-kernel ?
Or comment on the two patches ?

Are you guys applying just 1 patch to a kernel from kernel.org ?
If such patch is merged - what is stoping ArchLinuxArm from (officialy) supporting this device ?

Sorry for the dumb question but what are the files listed here:
https://github.com/reey/PKGBUILDs/releases/
And how are they used to make a working system ?

Huge thanks.