t.munzer

@Kusa, thanx a lot for your image. My previous one was 3 year and half old! All that time running 7/7 24/24 PiHole, Domoticz and some script managing Amazon Dash Buttons. IMHO a decent use case for a (16€) useless tv box (according to TK ). Everything fine (eemc boot) , and reboot do not need anymore to unplug! By the way, with my previous image (eemc installed), it was impossible to boot from *any* SD Armbian image. But... I could boot with H3Droid image, install H3Droid on eemc, then I could boot with an Armbian SD.

As much I can remember, I had the same issue : trying to *upgrade* kernel failed but fresh install succeded.

I'm curious, does log2ram works differently with mainline kernel ? My pi-Hole setup on Orange PI PC and Sunvell R69 hungs every 2/3 hours/days with legacy kernel, but runs smoothly for weeks along Domoticz with a mainline kernel.

Well, I know there is no support for these testing version, but for information, since last update if I run apt-get upgrade on a running Armbian_5.34.171121_Beelinkx2_Debian_stretch_next_4.13.14. image, update process went fine, but after reboot that poor little thing seems lost (not even a DHCP request on my router log). I reproduce the scenario on a system, with pi-hole, installed on emmc and running flawlessly for nearly a month but also with a fresh image burned minutes before.

I'm testing Beelink Debian Strech 4.13 server image on the R69. Results are very satisfying for my use case. With legacy image (even on orange pi pc) I never get stability running pi-hole,either pihole web server ran but dnsmasq was stopped, or the whole beast stopped responding even with SSH ; sometimes it stopped afted one day, other times after less than one hour. With mainline I ran for 6 days without a glitch. So I'm Happy... ...But I do not find how to replicate in mainline/dtb context what I do in legacy/fex, changing sdc_detmode parameter to have access to µsd card when booting from emmc. In fact I do not need at all using it, but I do not like not being able to do so !!!

Thanx a lot.

In download section for X2 Beelink there is no image for Server stretch test as advertised on download page, only for desktop. Is it normal ? (tm)

For me it isn't my level but my league. Do I need to worry about that ? root@sunvellr69:~# armbianmonitor -v Starting package integrity check. This might take some time. Be patient please... It appears you may have corrupt packages. This is usually a symptom of filesystem corruption caused by SD cards or eMMC dying or burning the OS image to the installation media went wrong. The following changes from packaged state files were detected: /lib/modules/3.4.113-sun8i/modules.dep /lib/modules/3.4.113-sun8i/modules.dep.bin /lib/modules/3.4.113-sun8i/modules.alias /lib/modules/3.4.113-sun8i/modules.alias.bin /lib/modules/3.4.113-sun8i/modules.symbols /lib/modules/3.4.113-sun8i/modules.symbols.bin

Well I used the emmc install to create the link ! in fact echo "heartbeat" > /sys/class/leds/green_led/trigger blinks a little red led. Case closed it's only lightly visible through the case's vent... if the case is upside down ! Well, as notice by Sven K in his Facebook report, the box engineers seems to have a strange physics. where heat went down and it's logical to put led where nobody can see it !

Install to emmc went fine. Setup Wifi, reboot disconnecting Ethernet, and test accessing iperf server on a orange pi pc (with ethernet connection) root@sunvellr69:~# iperf3 -R -c 192.168.0.240 Connecting to host 192.168.0.240, port 5201 Reverse mode, remote host 192.168.0.240 is sending [ 4] local 192.168.0.36 port 44822 connected to 192.168.0.240 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 1.53 MBytes 12.8 Mbits/sec [ 4] 1.00-2.00 sec 1.68 MBytes 14.1 Mbits/sec [ 4] 2.00-3.00 sec 1.73 MBytes 14.5 Mbits/sec [ 4] 3.00-4.00 sec 2.12 MBytes 17.8 Mbits/sec [ 4] 4.00-5.00 sec 1.51 MBytes 12.6 Mbits/sec [ 4] 5.00-6.00 sec 2.40 MBytes 20.1 Mbits/sec [ 4] 6.00-7.00 sec 1.78 MBytes 14.9 Mbits/sec [ 4] 7.00-8.00 sec 1.81 MBytes 15.2 Mbits/sec [ 4] 8.00-9.00 sec 2.54 MBytes 21.3 Mbits/sec [ 4] 9.00-10.00 sec 675 KBytes 5.52 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 20.1 MBytes 16.9 Mbits/sec 1 sender [ 4] 0.00-10.00 sec 18.3 MBytes 15.3 Mbits/sec receiver iperf Done. root@sunvellr69:~# iperf3 -c 192.168.0.240 Connecting to host 192.168.0.240, port 5201 [ 4] local 192.168.0.36 port 44824 connected to 192.168.0.240 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 1.22 MBytes 10.3 Mbits/sec 1 96.2 KBytes [ 4] 1.00-2.00 sec 535 KBytes 4.38 Mbits/sec 2 73.5 KBytes [ 4] 2.00-3.00 sec 255 KBytes 2.09 Mbits/sec 4 46.7 KBytes [ 4] 3.00-4.00 sec 153 KBytes 1.25 Mbits/sec 4 18.4 KBytes [ 4] 4.00-5.00 sec 423 KBytes 3.47 Mbits/sec 3 32.5 KBytes [ 4] 5.00-6.00 sec 1.79 MBytes 15.0 Mbits/sec 0 157 KBytes [ 4] 6.00-7.00 sec 2.15 MBytes 18.0 Mbits/sec 0 274 KBytes [ 4] 7.00-8.00 sec 1.95 MBytes 16.3 Mbits/sec 0 369 KBytes [ 4] 8.00-9.00 sec 2.31 MBytes 19.3 Mbits/sec 0 467 KBytes [ 4] 9.00-10.00 sec 2.61 MBytes 21.9 Mbits/sec 0 584 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 13.4 MBytes 11.2 Mbits/sec 14 sender [ 4] 0.00-10.00 sec 13.0 MBytes 10.9 Mbits/sec receiver iperf Done. root@sunvellr69:~# iwconfig wlan0 wlan0 IEEE 802.11bgn ESSID:"9bxchodk_guest" Mode:Managed Frequency:2.427 GHz Access Point: C6:6E:1F:2C:F5:CF Bit Rate=39 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=50/70 Signal level=-60 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:187 Invalid misc:0 Missed beacon:0

@tkaiser, Thanks, I apply @guidol correction and successfully boot.

Is it fixed the link given in your previous post ? Because using version downloaded five minutes ago, i'm stuck with Starting kernel...

To access µSD card inserted after booting from emmc , using Beelink X2 standard Jessie Image, it's necessary to edit script.bin (using bin2fex/fex2bin cf supra) to change sdc_detmode = 3 to sdc_detmode = 1

Using standard Beelink X2 jessie image, disabling HDMI (h3consumption -g off) decreases idle CPU temp by 6 degrees (circa 60 down to 54 °C). I think temperature variation I notice between standard fex and first tkaiser provided fex was only due to HDMI enabling in tkaiser fex file.

Just to be clear, I DID not ask for help or support. At start I just report what I see as a successful install. And I (fruitfully as I learn some tricks along the way) spent my spare time to test the fex file you post. Yes at 16€ delivered it was the cheapest way to have an armbian solution with emmc. I'm happy with my Orange Pi PC running Domoticz, but I see many user's reports (not related with armbian) complaining of uSD card crash on the long run. And, I guess, speaking of TV Box, that Beelink X2 wasn't supported... until it was. (tm)