La Otra Cuenta

It's the same one that works via USB. Attached is a screenshot with the exact message it gives me. My microSD is like the one in the picture.

Indeed, through the USB it does start. Is it possible to add the microSD unit to the dtb correctly? I have no experience with this issue. Actually, the microSD is reading it, but it can't find the second partition. Or, at least, I think so. Thank you

Hi, there. I have a problem with the Armbian_5.44_S9xxx_Ubuntu_Ubuntu_bionic_4.16.1_server_20180523.img I get the following message the first time I start from microSD: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) The device is Mini MX s905 2GB/16GB GbE I tried meson-gxbb-p200.dtb which is the one that starts. Thank you

Hello balbes150, I found problems when activating the UFW firewall in Armbian_5.34_S9xxx_Ubuntu_xenial_3.14.29_mate_20171104. Here is a list of the problems detected in the checkup, in case it helps to compile the kernel and include the necessary modifications for UFW to work properly. Thank you so much for the effort. $ sudo /usr/share/ufw/check-requirements Has python: pass (binary: python2.7, version: 2.7.12, py2) Has iptables: pass Has ip6tables: pass Has /proc/net/dev: pass Has /proc/net/if_inet6: pass This script will now attempt to create various rules using the iptables and ip6tables commands. This may result in module autoloading (eg, for IPv6). Proceed with checks (Y/n)? y == IPv4 == Creating 'ufw-check-requirements'... done Inserting RETURN at top of 'ufw-check-requirements'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: FAIL error was: iptables: No chain/target/match by that name. hashlimit: pass limit: pass ctstate (NEW): pass ctstate (RELATED): pass ctstate (ESTABLISHED): pass ctstate (INVALID): pass ctstate (new, recent set): FAIL (no runtime support) error was: iptables: No chain/target/match by that name. ctstate (new, recent update): FAIL (no runtime support) error was: iptables: No chain/target/match by that name. ctstate (new, limit): pass interface (input): pass interface (output): pass multiport: FAIL error was: iptables: No chain/target/match by that name. comment: pass addrtype (LOCAL): pass addrtype (MULTICAST): pass addrtype (BROADCAST): pass icmp (destination-unreachable): pass icmp (source-quench): pass icmp (time-exceeded): pass icmp (parameter-problem): pass icmp (echo-request): pass == IPv6 == Creating 'ufw-check-requirements6'... done Inserting RETURN at top of 'ufw-check-requirements6'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: FAIL error was: ip6tables: No chain/target/match by that name. hashlimit: pass limit: pass ctstate (NEW): pass ctstate (RELATED): pass ctstate (ESTABLISHED): pass ctstate (INVALID): pass ctstate (new, recent set): FAIL (no runtime support) error was: ip6tables: No chain/target/match by that name. ctstate (new, recent update): FAIL (no runtime support) error was: ip6tables: No chain/target/match by that name. ctstate (new, limit): pass interface (input): pass interface (output): pass multiport: FAIL error was: ip6tables: No chain/target/match by that name. comment: pass icmpv6 (destination-unreachable): pass icmpv6 (packet-too-big): pass icmpv6 (time-exceeded): pass icmpv6 (parameter-problem): pass icmpv6 (echo-request): pass icmpv6 with hl (neighbor-solicitation): pass icmpv6 with hl (neighbor-advertisement): pass icmpv6 with hl (router-solicitation): pass icmpv6 with hl (router-advertisement): pass ipv6 rt: FAIL error was: ip6tables: No chain/target/match by that name. FAIL: check your kernel and that you have iptables >= 1.4.0 FAIL: check your kernel and iptables for additional runtime support

Hi balbes150. First of all thank you for your work. I have two android boxes. One is an Acemax KIII 2GB / 16GB and the other a Beelink Mini MX 2GB / 16GB. The first carries a WiFi / BT chip BCM4335 and the second carries an AP6330. Can you give them Bluetooth support in your next version? I have been looking for how to do it, but it escapes my knowledge. I leave the link that I found to a thread where they get to operate the Bluetooth of the BCM4335 chip. Https://forum.libreelec.tv/thread-1408-post-29946.html#pid29946 If you need anything let me know. Thank you very much. (Google Translation)