Search the Community

Hello all. I'm obviously a newbie to this all and have a Libre Le Potato I just purchased. Put in Armbian Bullseye and got everything configured so my Python script runs on boot and writes the data it records by sending a byte string through the USB port to a device and records the parsed response. All is well there, but I needed to add an RTC to this and I have many DS3231 boards that I've integrated with Arduino boards recently and they all work well. I've soldered the connections to the 3.3V, GND, SDA, and SCK pins and matched those to the GPIO pins 1, 9, 3, and 5 respectively. I've gone into 'armbian-config' and enabled i2cA and updated everything. My problem is that when I run i2cdetect -l I get that there are two entries: i2c-1 which is listed as the DesignWare HDMI i2c-0 which is listed as Meson I2C adapter When I try to run i2cdetect -y 0 I don't see the RTC module when connected. Obviously something is not right. I'm trying to run 'armbianmonitor -u' but I'm getting odd responses where I get 'no results to fetch' so I don't have a URL for the log file to review. I've ordered 2 other boards and have the same results. I know the DS3231 boards are good because they work with Arduino boards without an issue. I'm missing something very obvious. Please help. Oh, kernel is 5.10.102-meson64 #22.02.1 This is frustrating and I don't see very clear step-by-step answers that explain what is happening.

I am attempting to install the v4l2loopback module for my device (Le Potato running Armbian 22.02.1 Bullseye) and am running to some issues. I installed linux-headers-5.10.102-meson64 since that matches the kernel image installed: marc@lepotato:/usr/src$ dpkg -l |grep linux-image ii linux-image-current-meson64 22.02.1 arm64 Linux kernel, armbian version 5.10.102-meson64 current marc@lepotato:/usr/src$ dpkg -l |grep linux-headers ii linux-headers-current-meson64 22.02.1 arm64 Linux kernel headers for 5.10.102-meson64 on arm64 current But when I try and install the v4l2loopback-dkms package I get the following: marc@lepotato:/usr/src$ sudo apt-get install v4l2loopback-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: caffeine python3-ewmh python3-xlib Use 'sudo apt autoremove' to remove them. Suggested packages: v4l2loopback-utils The following NEW packages will be installed: v4l2loopback-dkms 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/36.2 kB of archives. After this operation, 115 kB of additional disk space will be used. Selecting previously unselected package v4l2loopback-dkms. (Reading database ... 195673 files and directories currently installed.) Preparing to unpack .../v4l2loopback-dkms_0.12.5-1_all.deb ... Unpacking v4l2loopback-dkms (0.12.5-1) ... Setting up v4l2loopback-dkms (0.12.5-1) ... Loading new v4l2loopback-0.12.5 DKMS files... Building for 5.10.102-meson64 Building initial module for 5.10.102-meson64 Error! Bad return status for module build on kernel: 5.10.102-meson64 (aarch64) Consult /var/lib/dkms/v4l2loopback/0.12.5/build/make.log for more information. dpkg: error processing package v4l2loopback-dkms (--configure): installed v4l2loopback-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: v4l2loopback-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) Looking into the error logs I see: marc@lepotato:/usr/src$ cat /var/lib/dkms/v4l2loopback/0.12.5/build/make.log DKMS make.log for v4l2loopback-0.12.5 for kernel 5.10.102-meson64 (aarch64) Tue 10 May 2022 01:21:37 PM EDT Building v4l2-loopback driver... make -C /lib/modules/5.10.102-meson64/build M=/var/lib/dkms/v4l2loopback/0.12.5/build modules make[1]: Entering directory '/usr/src/linux-headers-5.10.102-meson64' CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.o MODPOST /var/lib/dkms/v4l2loopback/0.12.5/build/Module.symvers make[3]: *** No rule to make target 'scripts/module.lds', needed by '/var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.ko'. Stop. make[3]: *** Waiting for unfinished jobs.... CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.mod.o make[2]: *** [scripts/Makefile.modpost:130: __modpost] Error 2 make[1]: *** [Makefile:1726: modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.10.102-meson64' make: *** [Makefile:43: v4l2loopback.ko] Error 2 I googled around for that error and found a lot of posts about it and found a suggested solution of downloading the module.lds file from git using: sudo wget https://raw.githubusercontent.com/torvalds/linux/master/scripts/module.lds.S -O /usr/src/[your linux header version here]/scripts/module.lds sudo sed -i '$ d' /usr/src/[your linux header version here]/scripts/module.lds but when I try and reinstall the v4l2loopback module after that I now get the following: marc@lepotato:/usr/src$ sudo apt-get install v4l2loopback-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done v4l2loopback-dkms is already the newest version (0.12.5-1). The following packages were automatically installed and are no longer required: caffeine python3-ewmh python3-xlib Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up v4l2loopback-dkms (0.12.5-1) ... Removing old v4l2loopback-0.12.5 DKMS files... ------------------------------ Deleting module version: 0.12.5 completely from the DKMS tree. ------------------------------ Done. Loading new v4l2loopback-0.12.5 DKMS files... Building for 5.10.102-meson64 Building initial module for 5.10.102-meson64 Error! Bad return status for module build on kernel: 5.10.102-meson64 (aarch64) Consult /var/lib/dkms/v4l2loopback/0.12.5/build/make.log for more information. dpkg: error processing package v4l2loopback-dkms (--configure): installed v4l2loopback-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: v4l2loopback-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) marc@lepotato:/usr/src$ cat /var/lib/dkms/v4l2loopback/0.12.5/build/make.log DKMS make.log for v4l2loopback-0.12.5 for kernel 5.10.102-meson64 (aarch64) Tue 10 May 2022 01:27:58 PM EDT Building v4l2-loopback driver... make -C /lib/modules/5.10.102-meson64/build M=/var/lib/dkms/v4l2loopback/0.12.5/build modules make[1]: Entering directory '/usr/src/linux-headers-5.10.102-meson64' CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.o MODPOST /var/lib/dkms/v4l2loopback/0.12.5/build/Module.symvers CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.mod.o LD [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.ko ld:scripts/module.lds:6: ignoring invalid character `#' in expression ld:scripts/module.lds:6: syntax error make[3]: *** [scripts/Makefile.modfinal:40: /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.ko] Error 1 make[2]: *** [scripts/Makefile.modpost:130: __modpost] Error 2 make[1]: *** [Makefile:1726: modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.10.102-meson64' make: *** [Makefile:43: v4l2loopback.ko] Error 2 At this point I am stuck. Am I missing something obvious? Can someone point me in the right direction? Thanks in advance!

Hi, I installed/compiled different browsers that are based on QT (QtWebKit, QtWebEngine). Unfortunately, special characters, often necessary for typing in non-English languages, do not work. E.g. a Spanish accented 'e appears as 00e9 This makes all these really fast browsers with low memory footprint useless for multilanguage writing (e.g. in webmailers). The characters work fine in the terminal and other browsers such as Midori, Firefox and Chromium. Thus, I think, something went wrong in the compilation of QT libraries. Any idea how to solve that?

Before I give it a try, has anyone already tried to write armbian to eMMC of the Le Potato ? If not, can you give me a hint where I shall read in order not to destroy the storage? * Thank you * it gets interesting from page 2 onwards

Output of armbianmonitor -u: http://ix.io/2SDQ The latest released 21.02.3 Lepotato buster 5.10.21 with Xfce preinstalled is unable to start a desktop environment from a fresh image install. After booting up, the display goes to a black screen with a blinking cursor. Initial issue seems to be lightdm failing to start w@lepotato:~$ journalctl -u lightdm.service -- Logs begin at Sat 2021-03-13 05:51:27 UTC, end at Sat 2021-03-13 06:06:57 UTC. -- Mar 13 05:51:33 lepotato systemd[1]: Starting Light Display Manager... Mar 13 05:51:33 lepotato lightdm[2457]: Could not enumerate user data directory /var/lib/lightdm/data: Error opening directory '/var/lib/lightdm/data': No such file Mar 13 05:51:33 lepotato systemd[1]: Started Light Display Manager. Mar 13 05:51:35 lepotato systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Mar 13 05:51:35 lepotato systemd[1]: lightdm.service: Failed with result 'exit-code'. Mar 13 05:51:35 lepotato systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart. Mar 13 05:51:35 lepotato systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1. Mar 13 05:51:35 lepotato systemd[1]: Stopped Light Display Manager. Mar 13 05:51:35 lepotato systemd[1]: Starting Light Display Manager... Mar 13 05:51:35 lepotato lightdm[2489]: Could not enumerate user data directory /var/lib/lightdm/data: Error opening directory '/var/lib/lightdm/data': No such file Mar 13 05:51:35 lepotato systemd[1]: Started Light Display Manager. Mar 13 05:51:35 lepotato systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Mar 13 05:51:35 lepotato systemd[1]: lightdm.service: Failed with result 'exit-code'. Mar 13 05:51:35 lepotato systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart. Mar 13 05:51:35 lepotato systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2. Mar 13 05:51:35 lepotato systemd[1]: Stopped Light Display Manager. Mar 13 05:51:35 lepotato systemd[1]: Starting Light Display Manager... Mar 13 05:51:36 lepotato lightdm[2542]: Could not enumerate user data directory /var/lib/lightdm/data: Error opening directory '/var/lib/lightdm/data': No such file Mar 13 05:51:36 lepotato systemd[1]: Started Light Display Manager. Mar 13 05:51:36 lepotato systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Mar 13 05:51:36 lepotato systemd[1]: lightdm.service: Failed with result 'exit-code'. Mar 13 05:51:36 lepotato systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart. Mar 13 05:51:36 lepotato systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3. Mar 13 05:51:36 lepotato systemd[1]: Stopped Light Display Manager. Mar 13 05:51:36 lepotato systemd[1]: Starting Light Display Manager... Mar 13 05:51:36 lepotato lightdm[2592]: Could not enumerate user data directory /var/lib/lightdm/data: Error opening directory '/var/lib/lightdm/data': No such file or directory Mar 13 05:51:36 lepotato systemd[1]: Started Light Display Manager. Mar 13 05:51:36 lepotato systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Mar 13 05:51:36 lepotato systemd[1]: lightdm.service: Failed with result 'exit-code'. Mar 13 05:51:36 lepotato systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart. Mar 13 05:51:36 lepotato systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4. Mar 13 05:51:36 lepotato systemd[1]: Stopped Light Display Manager. Mar 13 05:51:37 lepotato systemd[1]: Starting Light Display Manager... Mar 13 05:51:37 lepotato lightdm[2647]: Could not enumerate user data directory /var/lib/lightdm/data: Error opening directory '/var/lib/lightdm/data': No such file or directory Mar 13 05:51:37 lepotato systemd[1]: Started Light Display Manager. Mar 13 05:51:37 lepotato systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Mar 13 05:51:37 lepotato systemd[1]: lightdm.service: Failed with result 'exit-code'. Mar 13 05:51:37 lepotato systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart. Mar 13 05:51:37 lepotato systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5. Mar 13 05:51:37 lepotato systemd[1]: Stopped Light Display Manager. Mar 13 05:51:37 lepotato systemd[1]: lightdm.service: Start request repeated too quickly. Mar 13 05:51:37 lepotato systemd[1]: lightdm.service: Failed with result 'exit-code'. Mar 13 05:51:37 lepotato systemd[1]: Failed to start Light Display Manager. Mar 13 05:51:37 lepotato systemd[1]: lightdm.service: Triggering OnFailure= dependencies. Mar 13 05:51:37 lepotato systemd[1]: lightdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found. Next, I tried startxfce4 to start xfce directly without lightdm, but got this error: Fatal server error: (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error I've attached the my full Xorg.0.log, but it basically has the same error. Has anyone else run into similar issues? Searching online for this "Cannot run in framebuffer mode" with x server, it seems that missing or broken firmware may cause this issue. So far the only configuration that I've done is: - create my user - connect to wifi using the armbian-config tool - Install full firmware using the armbian-config tool I haven't installed any other packages beyond what was already included in the image. Are there any additional debugging steps I could take? Thanks in advance if anyone can give me help Xorg.0.log

as described in: https://gitlab.freedesktop.org/mesa/mesa/issues/2377 it's possible to use meson HW video codec now, but in the URL, not very clear, does any one know how to use it?

I have a ToupTek MU300 USB2 camera that I was trying to get working with my LePotato. The camera does not have native kernel support, but the manufacturer provides an SDK with a pre-compiled lib for x86/arm, and additionally I have a kernel module which works on X86/X64 with this camera as well as userspace libusb based code to access the camera. The camera is very sensitive to having buffers available during bulk transfer, otherwise the image will be corrupted. Generally synchronous bulk transfer is not fast enough, and requires multiple buffers supplied in asynchronous mode. On x86-64 and Rpi3/4, everything works as expected. I can grab images via the vendor supplied SDK as well as with my libusb based code (and on x86-64 the kernel module...which is untested on RPi). However on the amlogic boards I have, the exact same code results in corrupted image frames being returned. The camera responds properly to control messages, and I do get data via bulk transfer, but the packets are not uniformly sized as they should be, and data is missing (converting the raw data to an image shows broken line alignment, indicating missing data) What I've tried: Tested 5.9.14 and 4.19 kernels Tested armhf and aarch64 Tested LePotato and ODroid-C4 Tested Kernerl-module, libusb, binary SDK Tested synchronous and asynchronous bulk transfers Tested with powered USB hub as well as directly plugged into SBC Tested with conservative and performance governors In all the above cases the camera performs the same way, yet there are no issues on RPi3, RPi4 or X86-64. I'm not sure what other options I might have to debug. I'm guessing it is something related to the USB stack, but it must be subtle, since I've seen no issues with other USB devices. I have looked at the traces in wireshark, and there is nothing obvious (besides that the bulk transfers are not uniformly the correct size) Does anyone have any ideas for other ways I may continue debug?

I have two Le Potato boards (http://ix.io/2ykP http://ix.io/2ykN), I installed Armbian Focal on them. One of the board has defective HDMI (board from Kickstarter?), it has no HDMI output. Other board was ordered from Amazon, a year later. It has HDMI output but colors are not right (white is green, black is purple, etc, HDMI image is not nice but it is usable; it is interesting that when I use HDMI to VGA adapter, colors are right; when board runs in low resolution, colors are right on HDMI too. But when resolution is high, 1950x1200, then HDMI colors are wrong - I swapped HDMI cable without any effect - is this known video driver issue??). So because only one board have working HDMI, I used that board with working HDMI to install Armbian to microSDHC card and then moved microSDHC to the other board (that is working but HDMI is broken). In few minutes I noted that both boards have the same MAC address (Ethernet). I have found that the MAC address in file /boot/armbianEnv.txt is unique for each board but they have the same MAC address 96:93:89:FF:90:C3 (and that MAC address is not in file armbianEnv.txt). Is this a bug? I fixed that by editing "/etc/NetworkManager/system-connections/Wired connection 1.nmconnection", I replaced MAC address "96:93:89:FF:90:C3" with address from armbianEnv.txt. After reboot each board has unique MAC address (and gets different IP address from local DHCP server).

Hi, i use a AML-S905X-CC board and since the last kernel update, something start moving on the hardware acceleration side, i got mpv hwdec working. I would like to make some tests and start using kodi for media reproduction, but i'm scared that 256M of default cma memory is not enough. I have tried to set the cma memory size from kernel parameters using armbian-config. I have tried to add "cma=350M" and "extraargs=cma=350M" to boot environment. Both commands does not work. The strange thing is that i'm sure "extraargs=cma=350M" pass the command to the kernel parameters because i have already used it to disable a faulty composition output. I have checked the syntax of the cma kernel parameter at the linux kernel documentation and SHOULD be ok, but i'm not sure 100%: I verify the cma allocation from dmesg, that report: [ 0.000000] Reserved memory: created CMA memory pool at 0x000000006b000000, size 256 MiB I also verify it by using "cat /proc/meminfo" and on the end there is: CmaTotal: 262144 kB CmaFree: 12772 kB So the question is: how can i change the cma allocation size, without recompile the kernel if possible? Is it possible that the cma size has been hardwritten at compile time and runtime changes are ignored? Thanks for the attention, have a good day

Hi, after the installation of the new kernel version (5.6.15-meson64) on my board (Le Potato), the display have ~1cm offset on the top of the monitor and ~1cm of non-visible element on the bottom. It is basically moved down by ~1cm from the center. I have already had this problem, but it "self solved" by updating the kernel, so i have no hint to solve the problem, only that it is very likely caused by something in the kernel. For the display i use an HDMI connector. I have attached the armbianmonitor log, if some more info are needed, you have only to ask. Thanks in advance for the time and dedicated effort. Have a good day! Edit: Wow, i don't know how i missed it. It seems that also the audio through HDMI does not work. Pulseaudio report that the audio is produced, but nothing come out from the speakers. If i'm not wrong i have had also this problem in the past at the same time with the monitor problem, but this was fixed by a patch from @lanefu: https://github.com/armbian/build/pull/1805 .

If I do i2cdetect -y 0 I don't see the device id I expect to 0x10 but I do see 0x30 and 0x50 which I shouldn't because there should only be one device at 0x10. I only see one i2c bus at /dev/i2c-0. Is that the i2c bus using header pins 3 and 5 which is where my device is attached? If not how would I enable the bus on pins 3 and 5?

I am running Armbian 5.38 LePotato Debian Stretch next 4.14.14 and noticing some weird activities going on. When checking the syslog it was full of this stuff: Feb 23 06:25:29 localhost systemd[1]: Stopped Serial Getty on ttyS0. Feb 23 06:25:29 localhost systemd[1]: Started Serial Getty on ttyS0. Feb 23 06:25:39 localhost systemd[1]: serial-getty@ttyS0.service: Service hold-o ff time over, scheduling restart. Feb 23 06:25:39 localhost systemd[1]: Stopped Serial Getty on ttyS0. Feb 23 06:25:39 localhost systemd[1]: Started Serial Getty on ttyS0. Feb 23 06:25:50 localhost systemd[1]: serial-getty@ttyS0.service: Service hold-o ff time over, scheduling restart. and this goes on forever.... filling the syslog with megabytes of text. What is going on and how to stop it? As far as I know there is no gadget attached to ttys0, I only have a keyboard, a DVB-T USB stick, CAT-5 ethernet cable and HDMI attached to the LePotato. The DVB-T stick is used as an ADSB receiver on Dump1090-mutabilitu and fr24feed is used to upload decoded positions of airplanes to Flightradar24.com Help?

Hello, I am having hard time installing hwclock 4PCS DS3231 on S905X-CC board. Can anyone please help?

Hi, first of all, thanks for all the good work on supporting all these single board computer. There no exist other disto that can do it. Indeed, this is the only general purpouse linux distro that officially support Le Potato. I would like to ask some help to solve these problems that i have encountered using my board. I have searched on the forum and i have not found any post on these problems. Sorry to be vague in the title, but all these bug appeared after the kernel update, so they may be caused by the same problem. I use a Libre Computer Le Potato inside a Sunfounder Raspad kit. The system is an Armbian Stable with apt linked to Debian Sid repository, so i receive stable updates from Armbian and unstable updates from Debian. I know that Sid is experimental and a lot of thing could not work, but i don't think these problem are related to this, but instead to something wrong in the kernel since these problems appeared after the kernel update, in November 2019, if i remember well. I will try to describe the problems accuratly as much as i can. If some more data is needed, i can provide all the informations. Impossible to use all the memory: I have noticed that the system does not use ram over 1GB, but instead start to allocate to the swap memory. I have tried to reduce the swappiness to 0,but it does not help. It is like there is an "hard limit" that does not allow the system to allocate more than 1GB of ram. I don't know if it can be helpful, but after some research i have noticed that on the /proc/meminfo, at the voice CmaTotal, the value is setted on 917504 kB. If i'm not wrong cma is a separate allocation system that reserve some of the system memory. On the armbianEnv.txt, the cma is setted on 512M; it is strange that the value is not the same. I have also tried to set a lower value, but nothing happen. Unable to use any kind of drm kms program: For a university project that i'm doing, i need to use the drm kms system, but seems that any kind of program that use that system does not work. I have tried: Removed the forced software rendering on Xorg (that make X use the drm system); the desktop appear, but blink continuously and after some moment become unresponsive GDM: Crash at startup Weston: Crash at startup kmscube: Start, but i get no signal from monitor until i terminate with CTRL-C the program Many other test programs found on drm test of mesa library have the same result I have also noticed that when i use some of the mentioned program, the dmesg report something like "alloc_contig_range: [X, Y) PFNs busy". From some research, it seems to be a problem in the memory allocation using the cma system, so the problem could be connected with the previous one. Before the kernel update, the drm system worked simply using software rendering. Now it does not work nor using gpu, nor using software. Audio problem: After the kernel update the audio sound like an old radio. I can hear what the audio is playing, but it is very confused and disturbed. The audio come from the HDMI. On the dmesg appear: [ 33.305753] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_hw_params() width 16 rate 44100 channels 2 [ 33.305788] meson-dw-hdmi c883a000.hdmi-tx: channels=2 sample_width=16 sample_rate=44100 [ 33.305877] __setup_desc: width=16 channels=2 desc=0 [ 33.305902] meson_aiu_i2s_dma_hw_params: physical_width=16 buffer_bytes=17664 period_bytes=4352 [ 33.306008] __dma_init_mem [ 33.348631] meson-aiu-i2s meson-aiu-i2s.3.auto: Failed to set sysclk to 0Hz Then also continuously appear: [ 33.362214] __hold: enable=1 [ 33.362280] __dma_enable: enable=0 [ 33.363573] meson-aiu-i2s meson-aiu-i2s.3.auto: Failed to set sysclk to 0Hz Lastly, i don't know if could be important, but before the February update, the monitor was not centered, but have an offset of half a centimeter that move the screen on the bottom. Like i said, this problem is now fixed with the last kernel update. I think it's all. If there are some question or missing data, i will provide anything is needed. Thanks again for the dedicated time and the effort invested on the Armbian project.

Well, no fancy introduction here, because this doesn't pretend to be a script for the general use, only for testers who want to try the current *very early* status of the media capabilities in the Armbian meson mainline kernel. Warning: It will replace your current kernel with a pre-compiled nightly 4.19.20. Instructions: Download, untar and run. If you need further instructions, then you are not ready for this script (again, it is very unpolished, not for general use). Download link: https://mega.nz/#!YvYUhayC!CI1fl52V4tV0G4oqUib4W-NlMpVSpLDp8kmo74g-V08 Things that you can try with this script, on a X session: Use a 1080p@30fps h264 video, and play it with "mpv -hwdec <filename>". You'll see in the logs that it is decoding through v4l-m2mcopy Install and run glmark2-es2 Use Chromium WebGL Play a 1080p@30fps video in YouTube in full-screen smoothly. I'm pretty sure it is not really using HW decoding as it claims (there is no initialization message in dmesg), but it's smooth for sure. Gstreamer is tested not to work, in some other forum I was told that Bionic version is not enough and I need to compile a newer one. Performance is not in any way good, but it is a starting point. Anyway, the first TO-DO is getting the mali module integrated into the kernel, so there is no need to compile it separately.

Just built some fresh le potato images from master. Error message is Wrong Ramdisk image format. Console dump here: http://ix.io/2c0y I think it's related to stuff going on here, but not sure how to troubleshoot yet https://github.com/armbian/build/blob/master/config/sources/families/include/meson64_common.inc#L34

Hello Le Potato hackers, I have a small favor to ask of you: I just wrote a Howto cross-compile mainline u-boot for your "Le Potato" (actually it's supposed to be for the La Frite when this starts shipping, but right now it's for the Le Potato) Here: http://wiki.loverpi.com/faq:sbc:libre-aml-s805x-howto-compile-u-boot Since I don't have a Le Potato I cannot verify that my HOWTO really produces a working u-boot, so I would be very grateful if any one of you could spend around 20 minutes of their (very valuable, without any doubt) time to follow the step-by-step instructions and check it out? What you need: An x86_64 PC/Laptop/Workstation running Linux, preferably Ubuntu 18.04 but anything else should be OK, as long as it's recent. A Le Potato. An SD-card A USB-to-serial converter to check that your you-just-compiled-it-yourself u-boot WORKS! Missing instructions on how to copy u-boot.bin.sd.bin to your SD card, assuming your PC/laptop sees it as mmcblk0: dd if=u-boot.bin.sd.bin of=/dev/mmcblk0 conv=fsync bs=1 count=442 dd if=u-boot.bin.sd.bin of=/dev/mmcblk0 conv=fsync bs=512 skip=1 seek=1 Thanks a bunch on any feedback!

I use mali kernel drivers from Neil https://github.com/superna9999/meson_gx_mali_450/tree/DX910-SW-99002-r9p0-01rel0_meson_gx All works just fine with 4.19 but it don't work with 4.20 it looks like there is some problem with memory allocation in this https://github.com/superna9999/meson_gx_mali_450/commit/2c9bd8ae57c0648045f7eaa48c120ec78db85d10#diff-2c0ef6f7db02daf8ed563376e846b873R312 Any idea?

I think it would make sense to rename the forum section here from "Amlogic S905(x)" to "Amlogic". It would make much more sense for me to talk here for example about the Armbian port of the Odroid C0/C1/C1+ (Amlogic S805) then in any other forum section.

I updated my Le potato to the new testing 4.18 kernel. everything works greats expect the no sound. The Alsa soujnd device is not visible . It shows a dummy output for sound device in the sound manager. I reinstalled the stable kernel and sound returned. Anyway to fix this under the new kernel? thanks,. John

hi dear all i am MS student and want to make my own development board for S905. if i purchase components from market and make a pcb then is it work? any one can answer my question?

I was curious if anyone had worked on power management for the S905X. My Le Potato was idling around 0.32A@5.1V = ~1.5W The LibreElec guys documented idle current ~2/3 of that here so I was curious what was going on. Of course I am running a 4.18 armbian kernel (I assume they were using a 3.14 kernel for their tests) so I was never going to match their numbers precisely, but 33% more power seemed like an awful lot. Then I realized I had a USB thumb-drive installed, so I did some experimentation... My numbers were generated using an inline USB power meter that measures pretty accurately compared to a bench meter. My initial findings: Idle with no USB connections: 0.215A Idle with 16GB USB3 stick in USB port 1: 0.291A Idle with 16GB USB3 stick in USB port 2-4: 0.323A Idle with USB2UART in USB port 1: 0.225A Idle with USB2UART in USB port 2-4: 0.257A Idle with 2 USB2UART adapters (ports are irrelevant)" 0.280A It should be noted that enabling autosuspend for USB: echo 'auto' > '/sys/bus/usb/devices/<...>/power/control'; Does drop the idle power back to 0.215 when USB is not in use. I don't need the thumb drive, but I do need 2 USB2UART adapters plugged in and running all he time, so autosuspend isn't very helpful for my use case. I may look into disabling the serial console and use that instead of one of the USB2UART adapters, which should be able to save me ~55mA. Does anyone else have any recommendations to lower the idle power? This box will sit at idle most of the time, and my goal is to be able to run it for 24hours from a ~100Wh battery. On the RPi, it is possible to disable LEDs and HDMI to save some power. Are there similar setting for the LePotato?

Anybody know how I can get the CPU temps for this CPU from Armbian? Armbian monitor seems to be missing that info and other common methods seem fruitless as well. I'm just trying to see if my cooling is being effective enough.

Hello All, Have a question, I see there is an option to use eMMC with the Le Potato aml-s905x-cc 1gb (which I got running yesterday), but what eMMC modules actually work with this board (I'm using a MicroSD card on my board at the moment)? Perhaps there should be a thread for Le Potato Hardware Options (just a thought)

This was briefly discussed in another topic, but the idea would be to make 4.14 the default kernel for Le Potato and K2, and change next to the newest stable kernel. The reason is, the 4.14 is the vendor kernel for Le Potato, K2 is only supported via it's similarity to C2 and Le Potato, and we currently don't have a "mainline" for Amlogic as everything moves forward. Consequences: Default build it yourself with the 3.14 will no longer be possible. We do not provide images of this build anyway. Next image users will get updated to the newest stable rather than staying on 4.14 This is what needs the discussion. I put a quick post on the Facebook group for Libre Computer I belong to, so far I've gotten half the community having seen the post and nothing but positive feedback on the change proposal. Looking to get any feedback available here. March 30, 2018 Status: Building "Default" image for either Le Potato or K2 will give you 4.14.y with Current BayLibre patches (K2 had other issues due to a board rename some time ago, broke u-boot process and boot script generation) Next still at 4.14.y waiting for 4.16