mdel

Awesome, had no idea montjoie git was already in armbian scripts. So i'll try to build an armbian image directly and see how it works.

montjoie has updated his crypto engine dev page and pointed some bad news for those Allwinner socs, including the H5 but looking at his project table it seems that the AES-CBC for H3 is labeled "OK", so i'd like to test the performance on my vpn link. I've tried to build his sun8i-ce-experimental branch but unfortunately i can't get it to boot on my opi pc (kernel panic), it's most probable that i didn't build it properly as i'm not quite experienced in building dev trees. Maybe someone can point to the proper steps to build that 4.9 source. Then if the results are decent, i don't expect much regarding my previous single thread openvpn tests, i'd like to know if it would be possible to include that driver in an armbian image, as i see there's no mainline image for the opi pc at the moment. thx

ordered one yesterday. i was wondering how the H5 will perform compared to the H3 with openvpn cryptos. Gigabit at 20e is quite a bargain in the realm of those boards.

@@balbes150 just wanted to say that i'll be back testing your images on my beelink MXQ S85 as soon as i can, been busy past weeks but i'll get back to it.

@@Kevin Kreger it's not quite clear what you're asking about. In doubt i'll try to clarify : Armbian is a Linux distribution (desktop or server), not an Android. So if your idea is to find a better Android version for your opi device or any other device, you're not in the right place, there's no android work done here. Then if i did misunderstand your comments and you're actually looking to run something else than android, you'll be glad to learn that Armbian should be working quite smoothly on your Orange pi devices. And so you absolutely don't need an X2 tv box. You can download images for your devices from the main Armbian website, tutorials to brun/use those images can be found on the download pages.

armbian firstrun autoreboot is normal. @@balbes150 do you know if the modifications you've made for dilligaf's boot could also work for my s85 box with kernel crash ? if you want me to test please give me the latest links/images i have to use. thx

@@balbes150 if you're looking for testers, i also have one s905x device here, can't remember its specs or name, i bought it by error and haven't opened it yet. And maybe for the sake of clarity i would suggest you open another thread for s905x images. it's already complicated enough that we have devices like my nexbox a95x that has both a s905 (first) and s905x (later) versions.. i saw your box on aliexpress it looks nice but the s905x 2g/16g is a bit too expensive and i'll probably never need 2G of ram. do you know if it's a Gbe or 100Mbps model ? the s905x has Mac and PHY Gbe right ?

humm it seems it can't even load uInitrd, not the same problem i have.

@@dilligaf yes to get messages from the boot, if you don't get anything on screen, you need to solder a serial to usb adapter (3.3v version). All the boards should have the serial header somewhere, if it's a well known board you'll probably find pictures on forums, otherwise you can take a picture of both sides and we'll find that right away.

@@dilligaf here's your dtb and dts files : https://mega.nz/#F!CNcBgZqY!j4PqPItAj5XPOYr5VaQHgA "dilligaf-boot.img-second.gz" is actually your "dtb.img" file (simply rename it), it is named after the boot sequence of the arm cpu. i have used the "split_bootimg.pl" script on linux, you can learn more about it here : http://www.cnx-software.com/2014/05/12/how-to-extract-a-device-tree-file-from-android-firmware-files/ http://www.cnx-software.com/2015/12/06/how-to-run-headless-linux-on-amlogic-s905-devices-such-as-mini-mx-or-k1-plus/ the dts file is an uncomplied text version of your dtb.img, it's of no direct use to you, but a good test to make sure that your dtb.img is correct. I use the dtc tool from the "device-tree-compiler" package. It describes your board hardware so if at some point your have a doubt you can always check in there, so far it was only helpful to me to fix some gpio (leds) problems on some boxes.

my beelink x2 has an ap6181, i can do a test with your build if it can help. also having the systematic reboot problem with current armbian 5.20, i blacklisted my wifi driver but it didn't make a difference.

@@dilligaf i also have problems with balbes150's s805 images (kernel panic), so if it fails on your box it may be normal. i have libreelec working fine on my s805 box so (not with my own dtb) i think balbes150 will be able to fix it, i will also try to build his git for my box.

1) you can boot android and use adb to connect to your android shell or use a terminal app directly in android but i like adb then adb connect ip.of.your.box adb shell box>su (to make sure you're root) box>strings /dev/block/env this will print your current uboot env and there you can see if s805_autoscript is present, that means the multiboot has been installed. 2) then you can also grab your dtb with some additional tools. box>dd bs=1M if=/dev/block/boot of=/path/of/your/sdcard/boot.img (wait it can be long) box>exit your box dtb is inside that boot.img blob, on linux i use a script to extract it, i don't know how it works on windows. to make sure your dtb is properly extracted you should try to decompile it with an appropriate tool and get the text dtc version without errors.

@@dilligaf try a small FAT partition on your SD card, 32MB for example when it worked for me i used the very small "BOOT" partition from one of my armbian SD Card (it has nothing to do with the aml_autoscript update, but i just grabbed a SD card with a FAT partition).

thx, my stats are more or less the same with -elapsed maybe it does not affect as much the non accelerated benchmarks

can you please tell me which image you're using exactly ? thx

okay i have put your s805_autoscript on the LE BOOT partition, here's the serial log : http://paste.ubuntu.com/23249899/ Your s805_autoscript was loaded and LE booted to kodi without problem, i did a proper "kodi shutdown" at the end. i'm not sure i understand what you wanted to do here, i see you have only copied the "setenv librefromsd" from their aml_autoscript. But can you explain what's going on with the dtb on that LE image ? i renamed the dtb.img, present in the BOOT partition, to something else and it booted fine, so the boot is not really using any dtb.img file. i see they are using a dtd patch in projects/S805/patches/linux/meson8b_mxq_dtd.patch, so is it built into the kernel image ?

tried your minicom command but it didn't make a difference, i can still interrupt boot by spamming "enter" and get to the prompt but then can't input anything. I tried soldering the tx wire to the last header pin but then i can't interrupt boot anymore so i guess the tx wire is correct. I'll try to take pictures tomorrow. My adapter is working fine, i've used it on a beelink x2 and i can type okay. Anyways i've tested a libreelec image this morning so you can have a source of a working linux on my device : freaktab thread : http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/23766-rom-unofficial-openelec-for-mk808b-and-mxq the image i installed on sd card : http://sx05.eu/libreelec/7.0.2.5/SD/LibreELEC-S805.MXQ.arm-7.0.2.5.img.gz kszaq github : https://github.com/kszaq/LibreELEC.tv the device name on his github is "MXQ", this is my beelink s85 (Nexteon board) he has various builds for different boards, and other members also have many other (oe/le) separate builds for other devices, so i guess there's no "universal" build for s805 .. here's a serial log of that libreelec firstboot (no mention of dtb loading ??) : http://paste.ubuntu.com/23246244/

thx for the info, the PINE A64+ looks like a cheap alternative in the Gbe category. doing more tests on my s905 i noticed something concerning those openssl "benchmarks" : openssl speed -evp bf-cbc aes-128-cbc The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes aes-128 cbc 54843.79k 61923.57k 65516.71k 66136.41k 66311.51k bf-cbc 35550.99k 44486.87k 47452.67k 48311.30k 48567.64k i was using blowfish on my system and seeing those figures i decided to switch to aes-128-cbc, expecting better speeds or lower cpu load, but it doesn't seem to be the case. I get more or less the same (realworld) speed (65-70 Mbps) with both encryptions but aes-128-cbc is apparently more taxing on the cpu. Also aes-128 seems to generate a much larger overhead than blowfish. So i was reading those tests as bandwidth capabilities but it doesn't seem to scale to realworld application. Still i will try to test H3 sun8i-ce driver when it becomes available.

interesting link but obviously 119.99$ +20$ shipping is a fair price. and i didn't know hackers could pick passwords with their dark fingers, scary ! okay i'm getting completely confused, what kind of features does that R18 soc has compared to an H3, besides being a Cortex-A53 vs Cortex-A7 ? that looks pretty impressive : The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes aes-128 cbc 104979.10k 152962.08k 178409.00k 185506.59k 188549.29k then i've tried to understand what he's talking about but it's a bit beside me i must admit. what does he mean by : what kind of optimizations is he talking about, is it the same thing as the hardware encryption engine worked on by montjoie or something else ?

well yeah that was my idea to repurpose that cheap box to do many things, but frankly in terms of stability and probably also performance, if my h3 vs s905 openvpn tests prove to be right, my favorite choice at the moment is an s905 box, the cheapest being the nexbox a95x (21-25$). Armbian runs extremely smoothly on it, no problems whatsoever (if not for one of the two usb port not being powered at boot). So the x2 is still on my radar, i always like to have an alternative, maybe the orange pi pc would be a better choice if you don't need wifi, well the x2 wifi is probably quite miserable anyways. and i managed to get one clean reboot on my x2 so there is hope =) @@tkaiser i'll check the loaded modules when i can get back to it. Do you mean unloading the modules early during the shutdown process and not let the system handle that ?

i've split my dtb to keep only the m8b_m201_1G part, but i still get kernel panics. with some of your dtb i can get to the linux prompt but then it also ends up with a kernel panic a few moments later.. I can try to check which openelec image did work fine on that box and see if there's something interesting there ?

which one is the hq18, the mxq one ? With my dtb i get a kernel panic, with the HD180 it seems to have booted the firstrun, i get to the linux prompt but can't type. I don't know if it's because the system is unresponsive or because my serial is not correctly soldered as i can never type anything when i manage to interrupt the boot.. there's a massive S85 thread on 4PDA : http://4pda.ru/forum/index.php?showtopic=621980 but i can't read russian and haven't found a picture of the serial connector yet. I didn't plug the network cable for the first boot but plugging it now, the network won't dhcp. So i will leave it and wait for a message. Also i know why my dtb is twice as big, it's because there are in fact 2 dtb inside, one m8b_m201_1G and one m8b_m201C_512M, i will try to split it correctly, or do you know how that works ?

yeah not sure what went on either, the network seems to work fine. here's a last log of a complete armbian 5.20 firstrun boot with auto reboot (which failed but finished with a power cycle ) : http://paste.debian.net/841990/ Everything looks fine if not for the failed reboot. Also, it seems that the usb serial adapter has a influence on the board state when power cycling, i noticed it when trying to boot android and it wouldn't. So i have to unplug the usb adapter before i can do a proper power cycle. Also, there's no hdmi connected to the box during mys tests, if it makes any difference. Anyways as a final test, i disconnected the serial adapter (left only the ground pin) and it still failed to boot a few times before it finally decided to boot. And a reboot almost always fails, i don't think it rebooted fine once with 5.20. So overall it seems to cold boot better than before (i had to try dozens of times before getting it to boot with my previous image), but there's still a reboot problem.

done, unfortunately it doesn't seem to have solved my boot problems. here's a log with various attempts, the first failure was from 5.14 which i flashed by error. http://paste.ubuntu.com/23233336/ i will try to flash to another sd card with etcher to make sure there's no foul play. a couple of other comments : - when the first boot finally started it actually resized the sd card this time. - plugging the ethernet cable after boot doesn't seem to trigger a dhcp request so the network stays "down". simply calling "dhcclient eth0" works fine.