I used Armbian Imager to flash Armbian 26.8.1 XFCE onto my Le Potato AML-S905X-CC-V1.0-A.

Problem:

On boot of the Le Potato, I could see the setup text via HDMI output on my monitor.

But after setup was complete, the HDMI output would stop and my monitor would go to sleep. There was no longer HDMI output after initial boot.

Solution:

So I needed to SSH in over ethernet and run these commands to resolve this issue:

echo "blacklist simpledrm" | sudo tee /etc/modprobe.d/blacklist-simpledrm.conf
sudo update-initramfs -u
sudo reboot

This fixed my HDMI output issue and I can use my Le Potato board with my HDMI display now!

Also as a note to beginners like myself, you cannot leave your passwords blank if you want to SSH into the board.

I left the passwords blank for root and user to start and lost time troubleshooting why I could not SSH in.

https://github.com/mozilla/geckodriver/issues/2167

It appears the bl30 blob is the only non free software file required for the le potato. What can you tell about the bl30 blob? Can it get reverse engineered? Where can you get the bl30 file? Thanks.

It says open-source support.

Free software is software you may use, share, modify and redistribute. Can le potato run entirely on free software, such that there is no piece of non free software on the computer? If so are the armbian le potato images free software images?

https://www.armbian.com/lepotato/

Thank you.

In my network there is an DHCP server that serve the IP address and route to the client.
The server is _isc-dhcpd-4.1.1-P1_.
In my network there are multiple OS like Debian 12, ArchLinux, MacOS and Windows, 
all the clients get the IP configurations via DHCP without problems.

The issue is reported only on the Armbian client and it concerns the configuration of the IP route.
In the Armbian device is not created the default route and there are two IP route that not be exist and are also wrong. 
In the DHCP server I have the configuration for serve the default route and other additional route, option 121.
The IP routes served via option 121 are present but the default route no.
Furthermore there are two route about DNS that not be exist and if I delete it, these routes appear again soon.

This is the output of `ip route`:
 

**1.1.1.1 dev wlx012ab3456789 proto dhcp scope link src 10.X.X.100 metric 600** 
**8.8.4.4 dev wlx012ab3456789 proto dhcp scope link src 10.X.X.100 metric 600** 
X.0.0.0/24 via 10.x.x.10 dev wlx012ab3456789 proto dhcp src 10.X.X.100 metric 600 
10.X.X.0/24 dev wlx012ab3456789 proto kernel scope link src 10.X.X.100 metric 600 
10.x.x.10 dev wlx012ab3456789 proto dhcp scope link src 10.X.X.100 metric 600 
10.y.0.0/24 via 10.x.x.10 dev wlx012ab3456789 proto dhcp src 10.X.X.100 metric 600 
10.x.x.0/24 via 10.x.x.10 dev wlx012ab3456789 proto dhcp src 10.X.X.100 metric 600 
192.z.0.0/24 via 10.x.x.10 dev wlx012ab3456789 proto dhcp src 10.X.X.100 metric 600

As you can see there is no _default route_ and exists two route about DNS host that are also wrong.
Even if I put the default route manually the two routes about DNS server host prevent it to be reached, so I must remove these two routes manually, but these two route appear again after few minutes. 

If I sniff the traffic during the DHCP request, the response is ok:
 

17:35:07.031609 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 353)
    10.x.x.10.67 > 10.x.x.100.68: BOOTP/DHCP, Reply, length 325, xid 0x67291d40, secs 1499, Flags [none]
          Client-IP 10.x.x.100
          Your-IP 10.x.x.100
          Server-IP 10.x.x.10
          Client-Ethernet-Address 01:2a:b3:45:67:89
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message (53), length 1: ACK
            Server-ID (54), length 4: 10.x.x.10
            Lease-Time (51), length 4: 600
            Subnet-Mask (1), length 4: 255.255.255.0
            Default-Gateway (3), length 4: 10.x.x.1
            Domain-Name-Server (6), length 8: 1.1.1.1,8.8.4.4
            Domain-Name (15), length 11: "dnsname.lan"
            Classless-Static-Route (121), length 32: (10.x.x.0/24:10.x.x.10),(192.z.0.0/24:10.x.x.10),(x.0.0.0/24:10.x.x.10),(10.y.0.0
/24:10.x.x.10)

How can I fix it?

Le Potato AML-S905X-CC-V1.0-A

I've tried two different methods to make this happen.

Method 1

I tried installing this image:  Armbian_24.8.1_Lepotato_bookworm_current_6.6.47_cinnamon-backported-mesa_desktop.img.xz

Method 2

I tried installing this image:  Armbian_24.8.1_Lepotato_noble_current_6.6.47_gnome-kisak_desktop.img.xz

and then tried installing Cinnamon with apt.

In both cases, when I got logged in to the Cinnamon desktop, HDMI output went away.

I can ssh into the machine and do whatever, but no video on the monitor.  Please let me know what you need if you think you can help!

Thanks,

Rich

I have been using the Le Potato for a while, and was able to save Armbian on an eMMC and boot from it. Then I tried putting another OS onto it but now it's no longer able to boot or recognize the eMMC module even when I go to Armbian settings.

Please help me be able to use it again to continue tinkering around with it.

Thanks very much!

I've tried putting boot_delay=0 as well as console=serial in armbianEnv.txt in hope of shortening the time in u-boot, but these didn't change anything.

I've also tried building this image with no initramfs and no loadable module support.

running apt update ; apt upgrade ; reboot it drops to 862M

How can I reclaim the remaining memory? This is mostly a headless server i do not need any GPU. just basic hdmi output for troubleshooting purposes.

before: 

Welcome to Armbian 23.8.1 Bookworm with Linux 6.1.50-current-meson64

System load:   8%               Up time:       4 min
Memory usage:  13% of 927M       IP:          
CPU temp:      48°C               Usage of /:    4% of 29G

After:

Welcome to Armbian 24.2.1 Bookworm with Linux 6.6.16-current-meson64

System load:   19%               Up time:       1 min
Memory usage:  13% of 862M       IP:          

dpkg: cannot write to log file '/var/log/dpkg.log': No space left on device

Digging into /var/log reveals that the ./journal directory is responsible; with 48 Mb.

Any idea how to prevent this? Currently, I just remove the directory below ./journal.

I tested it does not work on LePotato and Orangepi3B, but works on Rock 5B so I think this is more general than specific board, but not affecting all boards.

On the other hand, the program executes correctly when I run it through SSH with X forwarding. It also works with vendor provided image on Orangepi3B and Rock 4B.

Some answer in the stackoverflow page suggests that "HW cursor size seems to be actually reported by video driver, so you can probably just try another one, like recent xf86-video-fbdev." So I am not sure if this is related to how armbian or graphic drivers handle certain information. Maybe it is as simple as changing a default cursor size can fix it? I just don't know where to look.

This might be more general than specifically LePotato board.

I would appreciate any hint / suggestions!

I have been using armbian jammy on my potato without issues.

But since the weekend it only boots to initramfs and says can't find mmcblk1p1

I put the sdcard a live gparted and partitions are and verified.

In initramfs I can find in /dev the mmcblk0p1 but not the mmcblk1p1

Now how can I change the boot or the name of the device?

Thanks,

Rich

It's a pretty old thread, but it seems to still be doing it, at least in the version of jammy I downloaded today. Not a dealbreaker for me, since I only really need 1 port, I can use one of the other 3 and it works fine, but thought maybe someone would want to know if you didn't already know. I DID confirm that it's not the board/port. If I put Ubuntu on it, I can see the drive just fine in blkid even when it's plugged into that pesky USB port.

This is how I did on my raspberry pi(, that fried recently after about 7 years of service)!

However, I can not turn off display.

Commands I used on RPI do not work. Tried all kinds of various methods to turn off display

- xset

- vcgencmd

- xscreensaver

- tvservice

- All of the above as my <username> as well as "sudo"

All of them either don't do anything or blanks the screen but does not turn it off.

For some of the above commands it complains regarding

- VCHI initialization failed

I tried various things including sudo as well as adding my username to the video group, etc.

Nothing works.

Any help is greatly appreciated before I decide to return the board.

Thank you.

Does anyone have any tips for programs or configuration to get reliable 1080 video running, ideally without having to use something inside of xwindows ?

I am using the armbian image. 

I used armbian-config to enable the serial ports and both show up as /dev/TTYAML0 and /dev/ttyAML6. Nonetheless I am unable to communicate on the serial ports even when connecting jumpers and a USB serial converter. 

I later tried to modify the divorce tree by hand. No change. 

Is there something else I could try to get the serial port on pins 8 and 10 working? 

I've got a Le Potato, and a Tritium (I like the Tritium better, but I "feel" that Le Potato is a little bit quicker for longer). I've had them for about a week, I am a daily *nix user, and run several RBPi's around my home - 3D printers, Motion Cameras, Christmas Lights, and one is even a back up web server. My notebook runs Arch, my server runs Gentoo, and my workstation usually runs RebornOS or ZeroArch depending on my mood).

When I started using these Libre Boards, I was happily impressed but using them as a desktop (my intention is/was to get my kids a 3D printer, and use these to do double duty as slicers, and basic desktops (I've got a few RPi Zero 2 W's for OctoPrint).

*

My question (finally), is it possible to get AppLauncher to work on Armbian (Running Jammy Luna XFCE currently)? I've installed AppLauncher, and it makes a link to the ~/Applications folder like it should, but no AppImages run (Etcher and Cura 5.2.2 anyhow). I'm not at my desk right now, but running them in command line they don't seem to have everything they need to run. I did install Cura 4.what.ever but that lacks so many features my kid's will need, I don't want to bother with it. 

I tried to use Prusa-Slicer as well, but the poor little SBC gets fussy when it has burned through all of its ram before we've even clicked "Slice". Cura 4.what.ever is next to useless too (it did slice, I did get a print from it, but it wasn't pretty).

Either way, tinkering around on the little guys with web cruising (Chromium usually), editing conky files (with NANO usually), playing with XFCE themes, or shopping Amazon, they only last around 45 minutes to an hour before they stop responding for tens of minutes at a time, and need to be "sudo shutdown -rF now" via ctl+F1. I have heat sinks on them, and the hottest I've seen them get is 70c but that was only for a few seconds. They seem to hang out in the mid 60's most of the time.

Looking into the DTS, it seemed like there was consideration made for analog audio ( e.g. analog-amplifier).

Was this ever working?

"Armbian 22.11.1 Lepotato jammy 5.19.17 xfce desktop" image which comes with lightdm windows manger and wayland xserver.

I want to use https://github.com/debauchee/barrier but it does not support wayland, so I want to switch to xorg.

So far I've tried installing xorg using apt and adding the following line to /etc/lightdm/lightdm.conf 

xserver-command=Xorg

but when I do 

 sudo systemctl restart lightdm

the display manager hangs forever with blank screen and blinking cursor.

Are there any webcams that the Le Potato supports on Armbian?

Thanks for the assistance!

Any info that can point me in the right direction is welcome.

In case it helps: https://paste.armbian.com/wepugikade

1. On first boot, text was cropped left and bottom, had to press enter a couple of times to get the prompt to show at least so I could make the right selections.

2. After it booted, jumped right on to Chromium and was super laggy.  Installed Firefox as an alternative but it's still kinda laggy while loading page, but it works great after page loads.  I would like to have Chromium instead though.

PRO:   My rtl8821CU which was not working on any distro of Le Potato is finally working.  I'm guessing it's a Kernel issue?  This has kernel 5.x and other distros (even Raspbian 10) have Linux 6.x   KEEP IT AT 5.x PLEASE!

armbianmonitor -u is here: https://pastebin.com/UVbLxVH0

Trying to use I2c to drive a SSD1306 type oled screen.

All wires have been tested for continuity and are good.

Screen is connected as follows:

Screen SDA -> Pin 27

Screen SCL -> Pin 28

Screen VCC -> Pin 4

Screen GND -> Pin 6

ive enabled i2c-a and i2c-b via armbian-config

i2cdetect -y 0

  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --          

i2cdetect -y 1

 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- -- 

and finally lsmod | grep i2c shows nothing

What am I doing wrong here?

What might the problem be here?

HDMI shows no output, using Armbian Jammy made for the tato.

I have tried at least 10 times today with both images. Every time I end up in the same situation unable to edit the sd card.

orerlays = spi-spidev
param_spidev_spi_bus = 0

I've tried changing the bus to 1

None of these actions have helped.

Any advice would be greatly appreciated.

But I have no idea how to test further.

I've tried cheese:
 

cheese

** (cheese:4159): ERROR **: 13:06:46.007: cheese-application.vala:89: Unable to initialize libcheese-gtk
Trace/breakpoint trap (core dumped)

cheese -d [total guess at device] 

same as above

And libcam-hello:

libcam-hello
-bash: libcam-hello: command not found

I've tried installing libcam following what I found Googling, but I just keep digging a deeper hole.

I am lost. The camera works fine with Raspbian Bullseye in CSI mode, but my limited knowledge doesn't tell me whether the messages I'm seeing with Armbian mean much. What should I do next?

Thanks.

Sep. 29 2017 - HDMI hotplug script/udev added for Mainline.  Switching monitors no longer results in a necessary reboot.

Nov. 22 2017 - Dev updated to 4.14 with Libretech patches

Nov. 23 2017 - Next updated to 4.14.y with Libretech patches  <- wait for nightly, not on download page Active download

Dec. 18 2017 - Patch uploaded to fix Ethernet instability: commit

Feb. 04 2018 - Ethernet LED's fixed in repo. commit

July. 08 2018 - Next is kernel 4.17, HDMI audio fixed

[bug] Dec. 20 2017 - Init 0 results in reboot

[bug] July 8 2018 - Kernel 4.17 cpufreq throwing errors setting clock speeds, even after BayLibre patch. (board was initially unbootable, patch fixed that)

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!

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? 

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

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

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?

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 fixed the following issue for my own system for now, but wanted to let you know:

After upgrading the LaFrite from Armbian Buster 20.08 to 20.11 using "apt upgrade" it didn't boot anymore. It showed a message "Ramdisk image is corrupt or invalid", so I checked /boot/uInitrd and it linked to uInitrd-5.9.6-meson64, which didn't exist.

I fixed it by downloading the latest image and replacing everything in /boot except armbianEnv.txt with what was inside the image. Afterwards it booted again. I replaced everything, because the image apperently still is on linux 5.9.6, while vmlinuz and other files on my system showed 5.9.10.

I also realized that initrd.img was missing, too.

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).

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

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 .

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?

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?

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

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.

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

Does Le Potato accelerate Kodi? I don't see 'multimedia' image, does it standard image with vanila kernel?

Thanks Radius

(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:

1. An x86_64 PC/Laptop/Workstation running Linux, preferably Ubuntu 18.04 but anything else should be OK, as long as it's recent.
2. A Le Potato.
3. An SD-card
4. 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 would like to Power ON or Wake the Board by IR Remote.
However I cannot find instructions anywhere on how to enable the IR wake or what the code is for wake etc.

Can you please point me in the right direction?

From: https://loverpi.com/blogs/news/first-look-at-libre-computer-board-aml-s905x-cc-le-potato-hardware-overview

it states: 

Quote

Other great features include the IR receiver. You can set the IR receiver to wake the board up with remotes provided you set the software bits up.

IR Shutdown works but then I cannot wake the board by IR.

Thank you for any help and for all the time the developers donate to this.
Much appreciated.

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?

Anyway to fix this under the new kernel?

thanks,.

John

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?

[  292.242434] usb 1-2: new full-speed USB device number 7 using xhci-hcd
[  302.562341] xhci-hcd xhci-hcd.0.auto: xHCI host not responding to stop endpoint command.
[  302.583217] xhci-hcd xhci-hcd.0.auto: Host halt failed, -110
[  302.583231] xhci-hcd xhci-hcd.0.auto: xHCI host controller not responding, assume dead
[  302.583287] xhci-hcd xhci-hcd.0.auto: HC died; cleaning up
[  302.583527] usb usb1-port2: couldn't allocate usb_device
[  302.583578] usb 1-1: USB disconnect, device number 2

Is this a known issue?  I looked areound and didn't see any other reports like it.

I switched to a 4.18.5 nightly, and all 4 ports work fine there.  Interestingly the 'bad' port enumerates as '1-2', where the others enumerate as 1-1.1 - 1-1.3 (I was expectng either '1-1.0' or '1-1.4'), and  the current port '1-1' appears to be:

Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub

So I it looks like the top-left USB port is not hooked up to the usb hub on the le-potato?

I have 4 Le Potatoes, all connected to a 100 mbps switch. Each of them have a 32 GB Samsung SD Card EVO.

Initially, the problem was that my SSH session would hang at random usually when I download something. I can't SSH again unless I reboot the PI (I didn't bother waiting longer than 5min)

Initially, I thought SD Cards were bad, I moved them around, done reinstalls. I'm also using SD Formatter to format them and Etcher to install them.

Still, this freezing problem had no consistent behavior according to PI hardware or the SD cards..

For Power, I'm using Anker 40W 4-Port USB Wall Charger, which it should (I think) be enough power. I've checked all the cables using my phone to verify.

I plugged HDMI into them, and see if they were still running after those SSH crashes. (why didn't I do this earlier) I ssh'd into them and see what happened when the "crash" behavior happened.

After SSH hangs, I check the PI, and the computer is still running as usual.

I reboot the PI, and I start doing some downloads, and then now I see the network hang I get from ssh. To me it seems like the ethernet driver is crashing or something.

I'm not sure what else to try for debugging / what the problem is.  Send Help.

Version: ARMBIAN 5.34.171017 nightly Ubuntu 16.04.3 LTS 4.13.7-meson64
Using Le Potato 2GB Version.

Currently the only way I can get more than 1 device online is to use a different Linux flavour each time. My IP's are not becoming static for some reason in the armbain version but even with a static IP set on the Ubuntu image, any other ubuntu image would just lock up as soon as I try and use it.

Any help would be appreciated

I'm trying to use the GPIO pins on the board. Starting with baby steps, I'm looking to just simply turn on/off an LED via GPIO. I've been searching and poking around the /sys filesystem to try to understand how this works, but I'm having a hard time understanding which pins to expose via the export file, and what physical pins those map to.

I see /sys/class/gpio/ has two chips, 0 and 10. I see gpiochip0 has 10 pins, and gpiochip10 has 101. Is there a document which maps which of these corresponds to the physical pins available? If I write "8" to the export file /sys/class/gpio/export, does that expose pin 8 on the board (UART_A_TX)? Am I understanding this right or am I way off? For my purpose, which pin would be the right one to start with to turn an LED on?

Side note: I also noticed on the schematic for the board that several of the pins are labelled WIFI, are these interface pins for the SOC wifi module? 

Apologies if these are dumb questions. I'm just trying to find the info to learn what does what on this board.

    Le Potato aml-s905x-cc 1gb found some useful items for this neat piece of hardware:

ADAFRUIT INDUSTRIES 954 USB-TO-TTL SERIAL CABLE, RASPBERRY PI (1 piece) (excellent cable for console access)

comes with 4 wires (Black - GND, White - TX, Green - RX, Red - Power), using the power adapter, leave the red connector off

Use a terminal program (PuTTY, etc) and set the baud at 115,200, 8 data bits, 1 stop bits, and no parity, no flow control

Need good wireless adapter which works:

MK electronics 150 Mbps USB Wi-Fi Adapter Network Wlan Adapter Stick Windows Mac Linux Desktop PC Notebooks 150 MBit - Ralink 5370 chipset

This works fine when plugged into the USB of the Le Potato, and you can use 'nmtui' to configure the adapter, and make sure that 'automatically connect' and 'enable for all users' are selected.  I also turned off IPv6 configuration for 'wlan0'.   Also, for the IP addressing, make sure you use the form <IP ADDR/Netmask in CIDR>, i.e. 192.168.1.20/24 (which will set the netmask at 255.255.255.0)

Hope this information helps someone getting their Le Potato up and running...

Anyone else find items which work well with Le Potato, post replies here so that everyone can benefit

DWC2, which I am used to from RPi Zero is missing, but I guess it's because there is a DWC3.

However, if I just modprobe gadget driver, let's say g_ether, nothing happens - no new interface in ifconfig, no detection on the host.

Should I somehow reconfigure DWC3 to operate OTG in a peripheral mode?

# lsusb -tv

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/0p, 5000M

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M

    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

    |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M

    |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M

    |__ Port 2: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M

Here's the GitHub : https://github.com/leeadama/htop/tree/lepotato

See the Readme for Build Instructions.

Once you have it built and installed, you add the temp and frequency display like any other meter.  I.E. press F2, arrow all the way to the right and choose Temperature Sensors, press Enter to add it and Enter to confirm.

Then just repeat the process for the FreqMeter.

Tested on Ubuntu Desktop - Mainline Kernel

Linux lepotato 4.14.32-meson64 #2 SMP PREEMPT Thu Apr 5 19:31:23 CEST 2018 aarch64 aarch64 aarch64 GNU/Linux

Thanks

Lee

Their website refers to the LoveRPi Forum and this forum. It is impossible to sign up to the LoveRPi Forum due the confirmation email not being sent.

This might not be the appropriated place to ask this question, but since this appears to be the only place where I can ask, I'll ask it anyway here.

If I am to power up the board, I would like to know something about the connections.  I would like to know how to connect the UART for a serial console to boot the board up. Is this the connector next to the HDMI connector  (as it has markings TX RX and GND) Furthermore, I would like to know the voltage level of this interface. Is a TTL 3.3 Volt UART interface acceptable or do I need a different voltage level?  Is there any documentation about the GPIO header available anywhere?

    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)

i've tried the actually armlogic Image for my six le potatos. (https://dl.armbian.com/lepotato/Ubuntu_xenial_next_desktop.7z)

In the first step it looks ok.

But then i found you, that there is missing a xfs Module. I need this for a ceph test deployment.

After some research i found out, that you can compile you own kernel with this description:

https://docs.armbian.com/Developer-Guide_Build-Preparation/

I tried it and copy the kernel to the le potatos. But then a lot of strange things happens.

Some of them where starting, some not, and when they started after some time the whole system brokes (looks like the sd card was missing).

Is there a secret way for do it right? Which packages i should install? At the moment i'm installing the following, and after this and a reboot everything brokes:

linux-image-next-meson64_5.41_arm64.deb
linux-dtb-next-meson64_5.41_arm64.deb
linux-headers-next-meson64_5.41_arm64.deb
linux-u-boot-next-lepotato_5.41_arm64.deb

Then i thougt, i will use the daily image perhaps there is a xfs module includes.  https://dl.armbian.com/lepotato/nightly/

The latest "daily" image is from 19.11.2017 and with a 4.13 kernel.

At the moment i really desperated, because the solution is so near, but nothing seems to work in the near future.

What the best way for a fully integrated kernel?

I need some other modules as well.

Best Regards

Thomas

Basic information is on the link above, here's the TL;DR:

• Raspberry Pi 2 form factor clone, with 64-bit quad-core Amlogic S905X
• 1 or 2 GB RAM
• eMMC and SD support
• HDMI 2.0 for 4k support
• 100 Mb Fast Ethernet
• Extra headers for I2S, UART, etc (nice feature I think)
• IR receiver
• Advertised to have low power consumption
• Powered via micro-USB

• based on: Amlogic P212 reference board

Use Case:  Media Player (retro gaming?)

I've been using a board now for a few weeks, I have kernels 4.13 and 3.14 running, however 3.14 does not yet have a proper device tree so it's a bit rough around the edges (display support is not really there)

http://sprunge.us/GUgX  - eMMC was not installed for this, it has boot preference over the SD.

Pros:  

• Familiar form factor for a lot of people
• The board isn't doing anything "fancy", no real "gimmicks"
• eMMC should be a boost to performance. (Untested so far on my part)
• S905X, 4K and built-in IR should make for a good multimedia machine
• Dedicated fast ethernet, not sharing USB bandwidth like the Pi.

Cons:

• micro-USB powered, although so far the board seems to live up to its low consumption promise.  Still has the potential issue if the 4x USB's are loaded.
• Fast Ethernet, this board will not be a server.  
• Mali 450 (only really a con if gaming is on your To-Do list)
• No wifi/BT (that's a con for some people, for others it's a pro)
• USB Hub.  My understanding is not all 4 ports come from 1 hub, but there is no indication of which ports are which
• IR sensor position makes using Pi cases a bit more problematic (my favorites are the solid aluminum ones)
• U-boot blob (U-boot source available, but compilation in-script is problematic (2015.01 U-Boot) )

Yes, Fast ethernet is a pro and a con.  It isn't on the USB like the pi, pro.  It's only Fast ethernet, con.  Using the built-in phy keeps the component count down.  

Power Consumption:

• Using 5.25 Volts 2000 mA supply. (Reading at GPIO header, wireless mouse, keyboard.)
  • 5.28 V Idle
  • 5.22 V Youtube video with no acceleration (minerd won't compile, I haven't debugged)
  • 5.11 V Youtbe video + spinning disk 2.5" HDD on USB (it did not initially want to spin up, even hooked to 2 ports)
• Not bad, must be an above-average micro-USB socket.

first, as being new here: Many thanks to all the work that went into this!

Now, here's my problem on Le Potato, which I have with armbian and LibreELEC: As soon as I copy anything large to any media, some services (SSH, Samba, Kodi, tvheadend - all of them network dependent) crash after writing something between 200 and 700 MB - not always at the same point. So anything like

cp /some/huge/file /home/me

crashes the services. Something like this:

cp /some/huge/file /dev/null

is no problem. I tried writing to SD as well as to USB, and I tried via network (scp from another machine into Le Potato) and locally (copying fom USB to SD, but still using ssh to run the command). Always crash. To make sure it's not an issue of LibreELEC, I now picked armbian (Ubuntu from here: https://www.armbian.com/lepotato/). And I did this instead of copy:

#!/bin/bash
LARGEFILE="/home/potato/largefile.txt"
# Clean up any old file
rm $LARGEFILE
# Create a string of 4096 bytes
MAKE4K=""
for i in `seq 1 4096`;
do
  MAKE4K="${MAKE4K}A"
done
# Write the 4096 byte string a million times --> 4G file
for j in `seq 1 1000000`;
do
  echo $MAKE4K >> $LARGEFILE
done

I SSH'd into the machine, started the script, and *boom* SSH down and out at about 250 MB written - all three sessions I had open. BUT: Script seems to keep running: Local console login survived, and file keeps growing, until it finally reached the target 4 GB. Closer inspection showed:

ping 192.168.1.1  --> destination unreachable

ifdown eth0

ifup eth0

ping 192.168.1.1 --> Success

And ssh is possible again. So my conclusion would be: network stack somehow gets corrupted.

/var/log/syslog does not show anything helpful.

Any idea? Is this reproducible by others?

Cheers

Get:30 http://ports.ubuntu.com xenial-security/main arm64 g++-5 arm64 5.4.0-6ubuntu1~16.04.9 [5,178 kB]
25% [30 g++-5 172 kB/5,178 kB 3%]                                3,792 kB/s 26s
everytime..

I used this image.

Armbian_5.34_Lepotato_Ubuntu_xenial_next_4.13.8

Is there at the moment or will be in the future a way to have an hardware accelerated MATE desktop using armbian on le potato?

And if there is/will be,  what limitations does/would it have? (opengl/window compositing/video decoding/video encoding...)

Thanks in advance

Since I didn't find numbers may I ask owners of the device ( @Igor, @TonyMac32 ?) to run 4 quick benchmarks? Two times openssl, 7-zip and tinymembench. Please comment also which clockspeeds and which distro you used (Xenial preferred).

Thanks!

libre-computer-board ntpd[1518]: parse: convert_rawdcf: start bit / parity check FAILED for "###############RADMLS1248124P124812P1248121241248112481248P??"

This was solved with the following kernel patch:

diff -Nru libretech-linux.old/drivers/tty/serial/meson_uart.c libretech-linux/drivers/tty/serial/meson_uart.c
--- libretech-linux.old/drivers/tty/serial/meson_uart.c	2017-10-24 19:49:30.776000382 +0200
+++ libretech-linux/drivers/tty/serial/meson_uart.c	2017-10-24 19:52:39.660000472 +0200
@@ -362,7 +362,7 @@
 
 	writel(val, port->membase + AML_UART_CONTROL);
 
-	baud = uart_get_baud_rate(port, termios, old, 9600, 4000000);
+	baud = uart_get_baud_rate(port, termios, old, 50, 4000000);
 	meson_uart_change_speed(port, baud);
 
 	port->read_status_mask = AML_UART_TX_FIFO_WERR;

No more errors in the logs but still no time:

root@libre-computer-board:/home/libre# ntpq -c as -c cv -c rv

ind assid status  conf reach auth condition  last_event cnt
===========================================================
  1 29169  8811   yes  none  none    reject    mobilize  1
  2 29170  802b   yes    no  none    reject clock_alarm  2
associd=0 status=0012 1 event, clk_bad_format,
device="RAW DCF77 CODE (Conrad DCF77 receiver module)",
timecode="-?#-#?-??---#--?-?-???---1??p1-?-?-?1--8-2--4-??-1?2-?1--8??_",
poll=24, noreply=0, badformat=1, baddata=0, fudgetime1=292.000,
stratum=0, refid=DCFa, flags=0, refclock_time="<UNDEFINED>",
refclock_status="", refclock_format="RAW DCF77 Timecode",
refclock_states="*BAD FORMAT: 00:24:38 (100.00%); running time: 00:24:38"
associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart,
version="ntpd 4.2.8p4@1.3265-o Thu Sep  7 20:45:44 UTC 2017 (1)",
processor="aarch64", system="Linux/4.13.3-v10-g019e61d-dirty", leap=11,
stratum=16, precision=-22, rootdelay=0.000, rootdisp=22.170, refid=INIT,
reftime=00000000.00000000  Thu, Feb  7 2036  7:28:16.000,
clock=dd99fe54.700d7c45  Tue, Oct 24 2017 20:00:52.437, peer=0, tc=3,
mintc=3, offset=0.000000, frequency=0.000, sys_jitter=0.000000,
clk_jitter=0.000, clk_wander=0.000

Any ideas?