Igor

Yes, those are different areas. Forget about .fex when you are using Vanilla kernel. FEX settings are used in old 3.4 kernel and enabling in .fex and loading touch driver is usually enough.

Additional modules are usually added when: - we found a reason - user request is noticed on the forum - user request is added via Github issues or (best) a merge request ... This one was noticed and added by Zador few hours ago. Our official kernel will be updated soon, week or two - we are doing last fixes, otherwise self compilation ...

And cleaned Cubietruck page. http://www.armbian.com/cubietruck/

Specifics information moved to docs for CT and Opi+2e ... check if this way is O.K.

- conf added - Cubietruck MALI test test/test EGL Version: "1.4 Linux-r3p0-04rel0" EGL Vendor: "ARM" EGL Extensions: "EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_lock_surface EGL_KHR_lock_surface2 " Surface size: 480x480 GL Vendor: "ARM" GL Renderer: "Mali-400 MP" GL Version: "OpenGL ES 2.0" GL Extensions: "GL_OES_texture_npot GL_OES_compressed_ETC1_RGB8_texture GL_OES_standard_derivatives GL_OES_EGL_image GL_OES_depth24 GL_ARM_rgba8 GL_ARM_mali_shader_binary GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_format_BGRA8888 GL_EXT_blend_minmax GL_OES_EGL_image_external GL_OES_EGL_sync GL_EXT_multisampled_render_to_texture GL_EXT_discard_framebuffer GL_OES_get_program_binary GL_EXT_shader_texture_lod "

I'll test on A20 asap ... btw: we are missing this in xorg.conf ... how to add this new packaging system? I am not sure for H3 but this is a must on A10 / A20. Section "Monitor" Identifier "Monitor0" Option "DPMS" "false" EndSection Section "ServerFlags" Option "BlankTime" "0" Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" EndSection

Serial console has it's own header. Connect there, 3pins only, RX, TX, GND.

It's not working because current installer does not support UUID ... while new one will. It's already fixed but will work when we will push out updated images.

It's your call. It should work in both, CLI and desktop.

Strange. Can you try this image: http://mirror.igorpecovnik.com/test/Armbian_5.18_Orangepipcplus_Debian_jessie_3.4.112_desktop.zip You need to wait few seconds before HDMI is lit up. If you have a serial console, boot log would be nice to see, since it looks like it stuck at boot loader. The main difference between our and old stock images is boot loader. We use mainline and it could stuck at boot when some "bad" USB keyboard is attached or noise via serial console. But here you don't have them.

This is what you need to check if you want to add something to the image: http://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-image-customization-script But rather start at the beginning; http://docs.armbian.com/Developer-Guide_Build-Preparation/ Nobody knows everything so don't worry about. Just try and if you fail, try discover why its failing, do it again, read docs, do it again, ... ask here and enjoy doing it.

Our desktop is already lightweight as possible. There are only few applications, which you might not need: libreoffice-writer thunderbird icedove Uninstall them if you thing it's urgent to do so. I never built Asterix but since Armbian desktop is Debian based, I would check guides like this: https://www.howtoforge.com/tutorial/how-to-install-asterisk-on-debian/

Disconnect keyboard and reboot.

I compiled kernel from latest sources and this can't be reproduced. It does not crash. Will be pushed to repository ASAP.

PACKAGE_LIST_DESKTOP="xserver-xorg xserver-xorg-video-fbdev gvfs-backends gvfs-fuse xfonts-base xinit nodm x11-xserver-utils xfce4 lxtask xterm mirage radiotray thunar-volman galculator \ gtk2-engines gtk2-engines-murrine gtk2-engines-pixbuf libgtk2.0-bin gcj-jre-headless xfce4-screenshooter libgnome2-perl gksu bluetooth \ network-manager network-manager-gnome xfce4-notifyd gnome-keyring gcr libgck-1-0 libgcr-3-common libgcr-base-3-1 libgcr-ui-3-1 p11-kit p11-kit-modules \ pasystray pavucontrol pulseaudio paman paprefs pavumeter pulseaudio-module-gconf pulseaudio-module-zeroconf" @zador.blood.stained This is the left over diff to desktop-test, other changes were pushed to master. What else prevent us to merge?

@Zador Yes, that helped. @svkatielee Without using gnome-keyring / having one password storage for all users would be fine. It must be doable somehow ... Maybe setting null password non interactive by default? I did briefly seek for how to do this, but haven't got anywhere. Let's stick to network manager and fix possible problems within.

There is one problem regarding MPV and HDMI audio, perhaps any app and (via pulseaudio) HDMI audio? Test subject: Orange Pi PC+ legacy, jessie desktop with Network manager and Pulseaudio (pasystray pavucontrol pulseaudio paman paprefs pavumeter pulseaudio-module-gconf pulseaudio-module-zeroconf). When playing 1080p_H264_AAC_25fps_7200K.MP4 on HDMI audio out playing is stuttered but it's normal when playing via analogue jack. I just noticed but can't focus any more to find out what is causing this. If anyone can replicate this would be helpful. Add: This is the exact image which I use.

Than let's provide one dedicated CLI image, Xenial server and voila.

Or if we only provide a lime2emmc uboot for apt-get ? ("in case of troubles / recommended"?) ... or going lower for all?

Nice. I am also testing Network manager and ... Pulse Audio all day and haven't found any serious problems yet.

Than we could solve it this way? http://www.armbian.com/banana-pi-plus/

I am fine with Pine legacy. Can be included in next batch ... With Lime2 -> the diff is uboot and DTB?

This is about to be fixed with this commit ... and will be in action within next image / first proper one. Current one is officially called prerelease, since we just got the boards.

We can simply ask on user creation: "Do you want to have access to GPIO?" ... with some brief description what that means.

It's possible but I can only give you a hint since I never try this to make it work. You need to do two things, enable LCD in u-boot and add this to Banana device tree. At least you know what you need to look for.