mdel

yes i have commented the docker command in your vegas script so now it boots fine. And have added the usb bus power command for my second usb port on this a95x box. i've also added cpufreq-set -g ondemand to activate dynamic frequencies, for some reason the default init "interactive" governor does not work and cpu is always at "2.02 GHz". here's the output of the "docker daemon" command : root@vegas95:~ docker daemon INFO[0000] New containerd process, pid: 3728 ERRO[0001] Failed to built-in GetDriver graph btrfs /var/lib/docker ERRO[0001] Failed to built-in GetDriver graph devicemapper /var/lib/docker INFO[0002] Graph migration to content-addressability took 0.00 seconds INFO[0002] Firewalld running: false INFO[0002] Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address WARN[0004] Your kernel does not support cgroup blkio weight WARN[0004] Your kernel does not support cgroup blkio weight_device WARN[0004] mountpoint for pids not found INFO[0004] Loading containers: start. INFO[0004] Loading containers: done. INFO[0004] Daemon has completed initialization INFO[0004] Docker daemon commit=1.11.2 graphdriver=overlay version=1.11.2 INFO[0004] API listen on /var/run/docker.sock the command does not go to background, so that's why the boot process got stuck. I don't know if it's normal or not, and if you should change your command to "docker daemon &" i will try a second sd card to see if the first.run script manages to resize the partition. One last thing that annoys me a lot, during my configuration i'm getting boot problems because of fstab mounts (i don't know why yet), and the problem is that when it happens i can't ssh into the box and the display is black. I can still use the keyboard ctrl+alt+del to reboot cleanly the system, but i can't see the boot error on screen. i see that there's a lot of hdmi config in the boot process, including in the c2_init.sh script and i don't know if that's required to show the boot message but it would be nice to get a more reliable hdmi output when the linux boot stops early.. is there a way to fix that ? thx

another thing with your armbian 5.17 image, after a few reboots and installing services (nfs, openvpn..), i still get a boot error message about "LSB first run" asking to "wait and don't shut down" and have a look at systemctl "systemctl status firstrun.service" here's the output : root@vegas95:~# systemctl status firstrun.service ◠firstrun.service - LSB: PLEASE BE PATIENT AND DO NOT INTERRUPT THE FIRST REBOOT Loaded: loaded (/etc/init.d/firstrun) Active: failed (Result: exit-code) since Thu 2016-09-08 01:38:24 MSK; 7h ago Process: 802 ExecStart=/etc/init.d/firstrun start (code=exited, status=1/FAILURE) Sep 08 01:38:24 vegas95 firstrun[802]: Error: /dev/mmcblk0: unrecognised disk label Sep 08 01:38:24 vegas95 firstrun[802]: Error: /dev/mmcblk0: unrecognised disk label Sep 08 01:38:24 vegas95 firstrun[802]: /etc/init.d/firstrun: line 135: d/mmc + 1 : division by 0 (error... 1 ") Sep 08 01:38:24 vegas95 systemd[1]: firstrun.service: control process exited, code=exited status=1 Sep 08 01:38:24 vegas95 systemd[1]: Failed to start LSB: PLEASE BE PATIENT AND DO NOT INTERRUPT THE FIR...BOOT. Sep 08 01:38:24 vegas95 systemd[1]: Unit firstrun.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full. another thing, i don't know if it changed in recent armbian versions, but the first boot did not resize the sd card ROOTFS partition. I resize it manually. and to clarify, i'm back using an sd card (no usb hdd). the error do seem to point to do_expand_rootfs(), that's probably why it didn't resize my ROOTFS partition, but then the firstrun script did not complete and stays there.. if you want to debut the script here's my block device table : (after i resized it manually) root@vegas95:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0rpmb 179:64 0 512K 0 disk mmcblk0boot0 179:32 0 4M 0 disk mmcblk0boot1 179:48 0 4M 0 disk mmcblk0 179:16 0 7.3G 0 disk mmcblk1 179:0 0 14.9G 0 disk ├─mmcblk1p1 179:1 0 64M 0 part /boot └─mmcblk1p2 179:2 0 14.8G 0 part / i'll test by adding a /root/.no_rootfs_resize and see what happens.

@balbes150 thx for your answer i didn't read it before adding my other message above. i understand now, it was just a test, i've moved back to SD card boot because i have USB power problem at boot and can't boot from USB reliably.

@hugo yes i believe it is, although other users have reported the same kind of error using dvb dongles, and some solved the problem by upgrading their kernel. the dongle seems to work with my (long) iperf / netcat tests, i'll have a better idea when using it in real world applications. @balbes150 having all kinds of problems with my current armbian i installed your latest armbian 5.17 jessie docker image and the first boot got "stuck" with a message "waiting for rc.local script ..." you can ssh into the box, and i saw that "/bin/sh /etc/vegas95_init.sh" was running so i killed it and then the boot sequence could finish. i assume the problem comes from the "docker daemon" command in your script (docker is running).

i believe the WARN messages come from my Gigabit Ethernet dongle, don't know if it's a driver or hardware (power supply) fault.. The dongle seems to work fine though, i'll know more after using it this week..

thx for your answer. sorry i was doing something a bit stupid and probably didn't explain well enough. i was booting from SD card (BOOT and ROOTFS) then decided to move only ROOTFS to USB (BOOT still on sdcard), and it didn't work but i may have not renamed my label properly as i saw my USB partition was labeled ROOT (not ROOTFS). Maybe you can tell me if it's possible to have BOOT on SDcard and ROOTFS on USB, then i'll try again. Anyways i moved both partitions to USB now and removed the SD card completely and it boots fine. One thing that surprises me is that boot from USB is much (10 times) slower than sd card boot. The "uboot splash screen" stays visible for 30 seconds or more, whereas from sd card it stays on only for 2 seconds or less, the usb hdd led is active during that time. Looks like uboot has some speed problems from USB or maybe there are some timeouts as it's suposed to try sd card before usb. But after booting is done, the system seems more responsive than from sd card. one last thing that i noticed is that i do get a lot of those messages in the logs : [36062.666215] WARN::hc_xfer_timeout:2690: hc_xfer_timeout: timeout on channel 4 [36062.685513] WARN::hc_xfer_timeout:2692: start_hcchar_val 0x00989200 [36062.703841] WARN::hc_xfer_timeout:2697: chn-4,ep2-IN:type:2,speed:2,len:24576,addr2 [36099.265635] WARN::hc_xfer_timeout:2690: hc_xfer_timeout: timeout on channel 7 [36099.284923] WARN::hc_xfer_timeout:2692: start_hcchar_val 0x00989200 [36099.303182] WARN::hc_xfer_timeout:2697: chn-7,ep2-IN:type:2,speed:2,len:24576,addr2 it's not related to sd card or usb hdd, as it happens from both boots, i believe it's related to USB kernel drivers.

sorry i'm still having problems with freaktab so i'll keep posting here. so i have your armbian s905 running fine on sdcard, fixed the usb and cpufreq init (the cpufrequtils init.d script doesn't seem to work so i simply called cpufreq-set -g ondemand from rc.local). now i'm trying to migrate the ROOTFS to my USB HDD but for some reason it does not work. your s905_autoscript has the following config : setenv bootargs "root=LABEL=ROOTFS rootwait rootflags=data=writeback rw ${condev} no_console_suspend hdmimode=${m} m_bpp=${m_bpp} fsck.repair=yes net.ifnames=0" so i was assuming that swapping LABEL from the SD ROOTFS to USB ROOTFS would work but it doesn't. The USB partition has been rsynced from the (live) SD ROOTFS as described in other usb migration threads and the filesystem is ext4. I can see the disk is being accessed at boot and keeps being triggered at regular intervals but it won't boot, and unfortunately i don't have any screen output and have not connected serial to that board so far. So is ROOTFS label swap enough (maybe my rsync failed) of should i change the boot script to point directly to PARTUUID or /dev/sda1 to achieved the migration ? thx

still doing some more tests. i've switched to an s905 tv box Nexbox A95X, in order to get an idea of possible limitations of the H3 soc. It's running a custom desktop armbian image (legacy kernel) from bable150, from which i removed all the desktop components. I'll try to use the official armbian ordoid C2 image later (once i get the trick to get rid of that boot.ini). So that box has only two usb ports, two root hosts, i'm using one for the Gbe adapter and a second for an USB3 HDD (not SSD). For the Gbe i'm getting this time 215Mbps upstream and 245Mbps downstream, which is not too bad i guess. So i did tests running iperf3 up / down, along with 4GB dd read / writes to the HDD. The good thing is that in any combination the results are very consistent, i never got a test that would deviate of 5Mbps on the network or 2MB/s on the HDD. The network speeds are always as mentioned above, and for the HDD speeds i get a steady 38-40MB/s. That would pretty much match up any of the tests done on the H3 on this thread. The ondemand governor almost never went up to the full 2GHz and happily stayed at the 1.5/1.75GHz frequencies, with a cpu load barely going over 20% with some spikes at 60% on one core but most probably caused by the monitoring scripts (htop, glances..). So as seen with the H3, the s905 cpu is clearly not a bottleneck and the same kind of nas setup should be achievable. USB2 still feels really weak compared to current day bandwidths (or even poor native sata2), but as long as you don't really expect Gbe speeds to your storage device it should suffice. I'm quite interested to see how the Allwinner R40 will perform, it could shuffle the cards again. My current setup is still using an old A20 running 1 sata HDD, and moved the vpn work to a second device (old s805 tv box) with real Gbe performance.. Doing laptop repairs i also got the idea to use old eeepc motherboards that can be found at ridiculous prices (~35e), they are basically the same thing as an arm dev board (with sata), the problem is identifying the ones that do have Gbe. I haven't done much test on those weak atoms cpus so i'm expecting performances issues when it comes to high speed vpn, but for regular storage it should really work fine, we'll see..

@balbes150 i've flashed your Armbian_5.17_Vegas95_Debian_jessie_3.14.73_desktop_20160729.img.xz, and i'm testing it on a nexbox A95X (s905). i'm "auto booting" your s905_autoscript by renaming to to aml_autoscript and running recovery mode with "toothpick", so it boots directly and i don't have to modify my stock android uboot env which i'm not sure how to restore after i touch it. So your armbian booted fine, i also have some hdmi problems (broken image) and need to unplug it after boot to fix it.. I have a couple of questions, why are there so many dtb directories on that images (dtb/, dtb-3.14.73-vegas95/ dtb-3.14.73-vegas95.old/), is there a dynamic loading of dtb files from the boot partition ? I see your script use the dtb auto loading from memory if there's no dtb.img file, but that dtb.img should be on the root of the boot partition not in a directory right ? Anyways, i'm wondering what's going on because that armbian image has some problems on my a95x : - not important but cpufreq doesn't seem to work. i can change scaling governors but it won't change frequencies at least according to armbianmonitor (which doesn't seem to read temperatures well either, so maybe the frequency reading is also wrong).. - then more important, one of the two usb ports won't work on armbian (nothing is detected, nothing in the logs when i plug a dongle), it works fine in android. The second port works fine. root@vegas95:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@vegas95:~# lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M That's why i'm wondering about a wrong dtb file loading. I've also tried to place my dtb.img file on the boot partition but the usb problem stays the same. I haven't tested anything else, i think wifi is not working but that's okay, and i'll care about multimedia stuff later. Finally i would be very interested in getting a non desktop ubuntu (possibly xenial) armbian image, if you have something like that. At some point i'll test armbian C2 xenial image with a modified boot method, but the C2 has some specifics that i don't really want to mix in my tests.. thx

@tkaiser did you try ipv6 on your gbe adapter bandwidth tests ? Out of curiosity (and frustration) i tested iperf3 ipv6 and the results were quite catastrophic, i can barely get above 100Mbps in both directions.. I'm wondering if i screwed something up along the way, didn't test other devices yet. I'm still wondering why we get so different performances using the same gbe adapter on various hosts / systems (laptops, win 7 10), is it related to drivers or usb2/3 performance of the host ? And basically is the mention of "gigabit" only for the sticker or should some of those adapters actually provide Gbe ? thx

how do you read lsusb outputs to know if your devices are plugged on different physical usb hosts or on a single host through an integrated usb hub ? thx

quick followup For some reason my AX88179_178A shows dramatically different performances depending on the way you do the iperf / nfs tests. When the boards acts as the client then the speed drops to 95Mbps on the opi pc and 104Mbps on the pcduino nano. I tested that adapter on another device to make sure it was not related to the driver i downloaded, the pcduino has the armbian vailla 4.6 kernel with built in driver. If it's related to my local network, in both cases the board is connected to my desktop through a manageable BGe switch. But i can do 980Mbps in bot directions from that pc to another local server, through that same switch. i now use the same JMicron enclosure as tkaiser used in it's UAS test, although i'm not doing UAS test yet and i've populated that enclosure with a 250G evo750 SSD. So, local performances on that usb-ssd, using an ext4 partition are pretty close to what tkaiser had in his test, speeds around 35MB/s (although dd claims it's 45MB/s) and iozone tests are pretty close (a little higher considering i'm using a SSD). i then setup nfs4 and tested transfering numerous large files >2GB, i'm using the Gbe USB3 on the otg port in order to avoid sharing usb hosts as i'm not sure what's populated on the opi pc (3 usb + otg). Writing files to the SSD on the opi worked fine, i'm getting the "full" 35MB/s write speed and with some caching in the background, the client sees a speed around 42MB/s. Unfortunately due the that Tx low speed identified above with iperf, reading from the opi is always capped at around 95Mbps. Using a ramfs partition, i can max out Rx speed at 340Mbps, but Tx is still not working properly. Not sure what's going on with that Gbe adapter. One quick note though, i started doing network read/write tests using the -F "file" option of iperf3 but the disk access is extremely slow and shows speeds around 17MB/s, but as it's only happening with iperf i assume it's due to its way of writing data, so don't use that..

well i've ditched my pc3duino3 nano which is simply a complete mess when it comes to USB. Using xenial vanilla kernel, i'm trying to use my Orange Pi PC with an usb3 Gbe adapter which is that one : Bus 003 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet and its driver should be built as module according to /boot/config-3.4.112-sun8i : CONFIG_USB_USBNET=m CONFIG_USB_NET_AX8817X=m but that module is nowhere to be found in /lib/modules, am i missing something ? thx -- humm that 3.4.112 kernel is missing CONFIG_USB_NET_AX88179_178A -- okay the official "android" sources seem to work out of the box : http://www.asix.com.tw/FrootAttach/driver/AX88179_178A_LINUX_DRIVER_v1.14.4_SOURCE.zip That USB2-Gbe link gives me a steady bi directional 340Mbps (iperf) which is not bad i guess. tests with performance or interactive governors gave the same result, performance gives a steady 340Mbps. i didn't expect to get the full 480Mps but i'm not sure how high you can aim. tkaiser got 270-300Mbps on his opi lite from the otg port so it'll probaby be the range of speeds you can expect. here's where i bought that adapter (sunsky-online), a bit expensive : http://www.sunsky-online.com/product/default!view.do?subject.id=219254

@zador.blood.stained thx it worked as you described. Unfortunately having to leave the otg cable in place won't help me much as it certainly can't drive a USB hdd and so won't let my disks power up. Back to square one. @tkaiser yeah you're right i should be getting the full 1A on any of the two USB ports. I can get one of my usb3 enclosures to power up but only with a dual USB cable, which would indeed point out that those usb tracks can't drive 1amp on their own, not really a design flaw but still not very DiY friendly. Placing the sd card port right on the opposite side of the usb/rj45 ports was another fun idea. Anyways, i'll order some dual usb3 cables to see if it can solve the problem and in the meantime i'll power that usb cable directly from the DC rail. thx for the additional info, i was interested in learning more about that AXP209 power monitoring so it'll be for a future session.

hi, having power problems with the two usb ports of my pcduino3 nano, i checked the schematics and it appears the otg port is not powered by the USB_5V rail but directly from the VCC_5V input rail, so i was hoping it would solve my problem. Unfortunately it seems the port acts as an OTG port by default and i can't find a way to restore the otg host mode as advertised in the vanilla kernel features. The documentation only details how to use various OTG modes but not how to revert it back to host. I'm using xenial vanilla image. thank you.

Yeah you'll have to be "careful" with usb sata bridges on those boards i guess. I wanted to try something on my pcduino3 nano (A20) but the two usb host ports don't seem to be able to power any of my 2.5 hdd enclosures, i can only get one of my ssd to be powered from there. I'm using a bench power supply to avoid any problems, and tried from the default usb power plug, and gpio +5 DCin pin but no luck. Using an usb hub with external power works but that's a lot of things i don't want to add. I'm a bit surprised, although i haven't used that board a lot and only with its sata connector and an external hdd power supply so i didn't really test the usb ports with power devices.. Anyways those linksprite boards never inspired me much confidence, and they are a bit pricy, so i think i'll just ditch them and turn to H3 boxes or boards. I have no problem powering those hdd enclosures with my beelink x2 or opi pc with a stock 2A supply..

ok i've tested cpuburn-a7, it seems to trigger some temperature throttling as seen below. 10:18:09: 240MHz 1.12 0% 0% 0% 0% 0% 0% 41°C 10:18:14: 240MHz 1.03 0% 0% 0% 0% 0% 0% 41°C 10:18:19: 1200MHz 0.95 0% 0% 0% 0% 0% 0% 64°C 10:18:25: 1008MHz 1.03 0% 0% 0% 0% 0% 0% 67°C 10:18:40: 1008MHz 1.69 0% 0% 0% 0% 0% 0% 69°C 10:18:45: 816MHz 1.88 0% 0% 0% 0% 0% 0% 69°C 10:18:50: 816MHz 2.13 0% 0% 0% 0% 0% 0% 70°C 10:18:55: 1008MHz 2.41 0% 0% 0% 0% 0% 0% 68°C -- 10:19:52: 816MHz 3.37 0% 0% 0% 0% 0% 0% 71°C 10:19:57: 1008MHz 3.42 0% 0% 0% 0% 0% 0% 69°C 10:20:02: 1008MHz 3.46 0% 0% 0% 0% 0% 0% 69°C 10:20:07: 816MHz 3.51 0% 0% 0% 0% 0% 0% 69°C 10:20:12: 240MHz 3.23 0% 0% 0% 0% 0% 0% 54°C 10:20:17: 240MHz 2.97 0% 0% 0% 0% 0% 0% 48°C 10:20:33: 240MHz 2.31 0% 0% 0% 0% 0% 0% 45°C Surprisingly the system is much more responsive than with other tests, but cpu load is 100% on all cores unlike other tests. it will not go over 72°c after a 10min run but will stay in the 800-1000MHz range. the x2 thermal pad is not very efficient (or too thick) as expected, seeing the very fast temperature drop when the stress test stops, and you can't really trust the values above as my x2 case is opened and upside down (the cpu / "heatsink" are on the bottom side, under the board). but it still didn't kill my x2 =)

thx sorry i missed that i'll test on my opi pc (with smallish heatsink) well now that you say i could kill my x2, i must say i'll probably be tempted to test it on it too =)

neither of those two stress tests killed my x2 on my current xenial 5.16 image, using the "cheap" power supply that was powering it. stress seems to be more violent too as the box is much less responsive while it runs. armbianmonitor shows the temp jumping from 40 to 60°c (after 10min stress) and a steady 1200MHz clock, i checked the cpu load running htop. but to make sure i'll plug it into my bench power supply when i solder the serial later this week.

i'm wondering what kind of mainline images are you using on your h3 devices ? I haven't seen any on the armbian download pages, are there some beta images i could test ? thx

yup my images integrity are all valid according to gpg. thx for the comments i'll check cpufrequtils, i was monitoring dmesg and didn't get too many errors so i was happy with that. I've also seen the /var/run/.machine.id, mentionned in previous posts but i don't know where it's generated from, also /etc/machine-id which is some kind of hash. now check this : i've taken my freshly flashed x2 desktop image that will not boot on the x2 (led flashes red, then purple, never goes blue, no hdmi out) i put it in my opi pc, it boots right away no problem (haven't even changed script.bin symlink, it will crash on reboot until i fix script.bin). i complete the x2 image install on my opi, then i fix back script.bin, put it in the x2 and it boots, no problem ! But it seems i can also "corrupt" the sd (it's not actually corrupted at least fsck.ext4 sees nothing wrong) when doing a shutdown -h or -r, or upgrade on the x2. Once the sd gets corrupted there's nothing i can do with it in the x2. Also sometimes the reboot (shutdown -r, "hot start") will not work and stay purple, i have to power cycle the x2 to boot again (happened only one once without "corrupting" the card). I'm currently running the x2 xenial image, 1st run not booting on x2, so installed on opi with script.bin swap method, upgraded to 5.16 on opi, then back in the x2. on the beelink x2 with that same non "1st run booting" sd card : - in xenial i've done some iozone tests (same ones as on your NAS/UAS thread), made some dd 4GB writes, never got an i/o error message in the logs. - copied some multi GB files in android, from usb to the sd, no problem armbianmonitor shows 45 to 50c. i'll still solder a serial later this week and reproduce the boot problem to see what it says, maybe you'll find that useful. I have no idea what's going on, i still hope it's an sd card compatibility issue but maybe my x2 is a bit faulty. But the errors are really too easy to reproduce : - 5.14 freshly flashed images will never boot on my x2, they will always boot on the opipc (tested 5 different sd cards, brands and classes). - then after 1st run is passed (2nd run completed), the card will always boot on the x2. - once an "installed" card gets "non bootable" (reboot / halt / upgrade on the x2), then i can never get it to boot again on the x2 (not sure what happens on the opipc). @Édgar Mondragón well knowing myself, it was entirely in the realm of possibilities, but my beelink x2 do have a chip labeled H3 on the board, although i can also read "made in china" down there, so who knows.. Although i did scratch my head at some point, trying to install arm64 packages thinking the H3 was a 64bit cpu, but i'm playing too much with s905 boards at the moment, that's all. Oh and in my previous description i forgot to say that the pcb wifi antenna on that x2 board is really funky too. Finally a couple of things unrelated to my problems : - minor bug : the upgrade does not keep the display (h3disp) setting, i understand it replaces the beelinkx2.bin - feat request : for the desktop image, would there be a way to get other resolutions like 1920x1200p or is it all defined in the closed driver ? - feat request : after a halt, would there be a way to keep the device alive so it can still receive IR remote commands ? well only "power on" i guess, is this defined in the uboot environment or is it a standby power level where the IR logic can trigger a poweron/reset pin ? thx again for your work

Okay i'm moving forward a bit and something does not work with my x2 and current 5.14 images in the download section. So no image would boot on my x2, i flashed on the same card the 5.14 desktop orange pi pc image and let it install, no problem. I then replaced the /boot/script.bin symlink for one pointing to bin/beelinkx2.bin, and put the sdcard in my x2. And of course it booted directly into the desktop, i'm currently writing this from the beelink x2 box. I just have 30 mins to play, so i can't do a lot more right now, i'll reflash the 5.14 x2 image on that sd card to make sure it still doesn't boot and if that's the case i'll solder a serial and see what happens.. In case i can't solve the problem and still want to use my x2 with armbian, i wanted to know if changing the script.bin is the only thing to do to switch an armbian install from one device to another ? thx

yeah nothing boots here on my E237212 94V-0 1542 board (SN X2H3CACE10205) but something is definitely going on (from one image to the other, the power led is not the same color, with armbian download it seems both blue/red are on). i'm still hoping for a sd card issue but i highly doubt it's the case, tested 3 so far which should work perfectly fine. Who knows maybe i have a different board configuration, maybe it doesn't have an H3 inside, that would be fun =) And i didn't remember there was a nice smiling sheep in there, is that what's the "bee" in beelink stands for ? Anyways i was hoping for a quick test, i don't have time to debug that in the next days, i'll come back to it with an uart cable connected next week. In the meantime if someone can simply point me to a post explaining how to extract your fex / script.bin that would help, sorry i don't have much experience with alwinner images. thank you

i'm a bit at a loss here, i can't get my beelink x2 to boot current armbian images, i feel i've missed something obvious. i've downloaded the 5.14 armbian images for jessie desktop and xenial server, flashed them with dd in linux, plugged the sdcard and then power. The led turns instantly blue ("on", stays red whithout sdcard) but nothing seems to happen, no video output, no eth link. In my memory i have not tempered with that beelink x2 much, probably only installed a different version of kodi in android, and haven't used it in a while. Android still boots fine and the sd card can be browsed in the file manager (plugged after android boot). I'm using a 32G Samsung Evo HC1, i'll try another one. thx

yes sorry i was talking about my desktop amd64 kernel, i'm testing the enclosures there before moving one to my A20 or H3 boards for further tests. i'll continue investigating my desktop UAS support.