Turgus

Armbian_20.05.0-trunk_Arm-64_bionic_current_5.5.1_desktop_20200213.img.xz also runs & installs nicely like before on my x96mini 2/16 s905w p281 testbox as always with ethernet connection and analogue usb sound. Box works as it should (for me)!..

As I got no issues with video output via hdmi and these crappy, tiny tv speakers are off usually, the distortion is no issue for me. So that means, the internal av-port could be "activated" via cheap & bad HDMI cable? I didn't test for long time, but is then sound via cvbs 3.5mm jack available again too?! That would be my perfect scenario: video via hdmi and sound via analogue internal 3.5mm jack-that would mean one usb available(1of2 is taken by keyboard always) for storage or other stuff because no usb sound is needed..

..just a quick report: Armbian_20.05.0-trunk_Arm-64_bionic_current_5.5.1_desktop_20200212.img.xz also runs & installs nicely like before on my x96mini 2/16 s905w p281 testbox as always with ethernet connection and analogue usb sound.

Thanks to balbes for his work and providing the rich variety of all these aml, multi & aw-images! Armbian_20.05.0-trunk_Arm-64_bionic_current_5.5.0-rc6_desktop_20200211.img.xz runs & installs nicely on my x96mini 2/16 s905w p281 testbox. Depending on chip -I got several different hw-versions of x96m- even wifi works with AP6255(this pcb has imprint "Q6X V4.0 17392"), but I use ethernet cable anyway. Because I forgot to mute TV after some other test-scenario I got signal not only via analogue amp as usual. HDMI sound seems to be little overdriven/distorted on desktop-test-video without user regulation on box(TV was set just at 3 of 40 which is usually "near muted"..), while usb sound sends perfect and clean signal to old '93s Kenwood Stereo-Amp via 3.5mm jack. By the way: I'll try this build on my creepy, stubborn, un-cooperative (flowfon/eachlink) H6mini 4/32 box next days too-would be nice if it works(on other, zero-overwritten card, with aw u-boot and aw changes), but I doubt it on this some kind of enchanted device which booted le for tx6 exactly one time and then never any armbian or LE again(no success with uart-reading other than garbage, found no working u-boot/dtb to boot from sd, usb or sd & usb together..)..

After problems with the 19.11.5 images, Armbian_20.02.0-rc1.032_Arm-64_bionic_dev_5.5.0-next-20200131_desktop.img.xz boots, runs and installs again as it should(and I was used to) on my x96mini 2/16 test box with usual eth connection and usb sound. Thanks @balbes150 for his good work and making s905(w) boot with new builds again!

..if you want use pure kodi, pop in a card with libreelec installed, or maybe use android..consider armbian on these boxes as sbc for server tasks or as tiny low cost and low-medium performance desktop mini-pc with just basic multimedia features with built in and patched mpv player..

While newest LE builds boot and all armbian images up to 19.11.4 (I tested) work(and install) nice -like always with usb sound and ETH- on x96mini 2/16 test box, I didn't manage to get any of the 19.11.5 builds working..on the earlier .5 builds device booted(with usual meson-gxl-s905w-p281.dtb set) but there was no usb keyboard working. On newer builds I get just black screen flickering slightly for some seconds until tv switches to "no signal". Is there any trick to get the video output back like the video=HDMI-A-1:e tweak on (some) allwinner h6 devices? Until now I also had no luck booting any build on the flowfon f1 4/32 H6 box I got. The pcb is 3rd revision of H6mini board used also on Eachlink H6mini, Eachlink H6max(yes same board, but on max always 4 gb ram) and several other petrel-p1-h6 boxes. Just once after an alert that cpu is too hot I could boot tanix' tx6 LE from card. Everything I tested worked(HDMI + sound, network, playback, radio/tv streams..), but I never could get the card reboot again. Like on other builds (LE/armbian)I tried try to boot from card, it give just blank screen(no signal). Maybe it is the odd ram timing this device uses-when comparing dts files extracted from tx6 android rom and from a rom that works on this device there are slight differences, but could also be u-boot. Are there any (working) dtb's for these h6mini boards or other approaches to get this beast boot anything useful?!

For me on the x96mini work all/most versions until 19.11.4 (the 19.11.5s I tried didn't boot or booted but had no usb working) with the meson-gxl-s905w-p281.dtb For me worked to boot via toothpick method after doing the fake update(there was the footer error, but afterwards balbes' Libreelec booted from card..). Afterwards I can boot any of the armbian images before 19.11.05 on the x96mini 2/16. Install on eMMC works too, but for newer (universal boot images) install has to been done not via armbian config tool like on 5.9x-builds, but via install script in root directory. To get the install successful you need to delete rk and aw u-boots on card as boot partition on eMMC is just 128mb but with all u-boots it is more. For newer builds 19.11.5 and on I have to ask in mulit platform thread, why those doesn't boot for me with same dtb settings I use for years on that device..

Thank you! ..I searched for long time via file manager and search, but -not thinking enough- just as normal user.. ;-)

Okay, where are these scripts (esp. for amlogic platform) located? Would be nice to replace older armbian(should be 5.98 or similar) on internal with the newer 19.11.04 version working well, to boot and test LE from card occasionally like usual..

While Armbian_19.11.4_Arm-64_bionic_current_5.4.1_desktop_20191228.img.xz works nice on my x96 mini 2/16 Test box with usb sound and ethernet(except I didn't find the point to install to internal in armbian config!?), Armbian_19.11.5_Aml-g12_bionic_dev_5.5.0-rc5-next-20200109_desktop.img.xz and Armbian_19.11.5_Aml-g12_buster_dev_5.5.0-rc5-next-20200109_desktop.img.xz boot, but I couldn't test further as on both usb keyboard doesn't work at all..so no login, new user etc....

..okay-maybe not the ideal way, but I had no android for the box here..so for me worked pretty well booting the armbian from card with pressed recovery button and just re-copying the system to emmc via armbian-config again..also 19 alpha Libreelec builds boot/work again as expected, but neither coreelec nor official built images boot, like it should be.. Just installed Armbian_5.99_Aml-g12_Ubuntu_bionic_dev_5.4.0-rc6_desktop_20191010.img.xz (is the timestamp 1010 correct or should it be 1110?!). No issues so far on my x96 mini p281 s905w 2/16 test box.

Hi, is there a way to re-install the proper bootloader (or whatever changes) after trying for example coreelec or older libreelecbuilds from card when armbian is installed on internal? I had the card from armbian install still available, so I could do a reinstall on emmc via armbian config. Is there a simple way to copy just the part coreelec or other systems "destroy"? Or is there even a simple way to change the boot-thing on the cards from the old one to the newer one working with armbian and the kodi 19 testing builds? By the way, Armbian_5.98_Aml-g12_Ubuntu_bionic_dev_5.4.0-rc4_desktop_20191025.img.xz works nice on the testing x96mini 2/16 s905w p281 box.

I always use armbian-config for install onto eMMC on x96mini 2/16. Dtb I use is always meson-gxl-s905w-p281.dtb. Never had problems that way! On desktop version of 20190708 bionic build installed system works like expected with USB-soundcard(because my screen got no speakers and internal AV doesn't work..) and eth or usb-wifi. Disco desktop works on x96mini basically too, but there I need to start every configuration tool (armbian-config, gnome-language-selector..) or anything with "sudo" within a terminal. So disco never found its way onto my eMMC just on card..

..is it right, that the images in 905-folder are named 912?!

Okay, on his box it is an micro-sd-card with libreelec, but a friend of mine just taped the slot with some black duct tape after inserting the card. It is nearly unvisible but prevents the kids disturbing the system when using their tv-box unattended... Maybe you do also a backup from the card on PC/Laptop after setting up the system to easily restore it when needed because kids messed around with the card..

Google translates it that way: This behavior was in all releases) IMHO, this is primarily due to the scaling video, with software scaling. With the 720p, soc still manages, in the "in window" mode with 1080p - already a problem. When playing the corresponding permission in fullscreen, you don’t need to sign anything, and accordingly there are no problems. P.S. I saw a mention about puppyrus, but I can’t persistently fail to register for puppyrus, the activation letter just does not come to the gmail box)

..after setup on card I installed Armbian_5.72_Aml-s905_Ubuntu_bionic_next_5.0.0-rc3-next-20190125-g494367cb5-dirty_desktop.img.xz onto eMMC. Boot takes a bit longer compared to previous installed version, but works pretty good on x96mini 2/16G with ethernet and usb sound.

..after a quick check on card I installed Armbian_5.71_Aml-s905_Ubuntu_bionic_next_5.0.0-rc3-desktop onto eMMC. Works like a charm so far on x96mini 2/16G. If there will be a release with k 5 in 5.72 versions, I'll test it too..

I tested 20190118-NEXT-Ubuntu-Desktop some hours from card and installed it via armbian-config successfully onto eMMC now. Works as expected pretty good with USB-Sound(hence I got no speakers on Monitor to provide HDMI-sound) and Ethernet LAN on 2/16GB x96mini. The system is responsive and runs smooth. Also start-up seems faster compared to older builds. @balbes150: After install I found the 20190122 images with kernel 4.20.2. What is new/changed in these builds?! As everything works pretty good on 5.0.0-rc2 for me, I'm not sure if I should downgrade kernel with newer version of image?!

..I guess @blakadder thought, that the deb files hosted with the images(which needs to be installed manually if needed) are some kind of Updatefiles to update in a similar way like the update on Libreelec!?.. To update the installed packages to newer versions sudo apt-get update sudo apt-get upgrade (or via Synaptic if installed) is the only way to do this properly. To update the whole Version (e.g. from 5.67 --> 5.71) you need to install the new image onto card to test and (if you want to) install it onto eMMC AFTER HAVING A WORKING SYSTEM ON CARD. If you backup your home directory before, it is much easier to get back your desired settings/files. Also a backup of the complete old system via ddbr is sometimes useful, if you install the new image to eMMC without testing enough or install fails somehow..

Did you try all possible USB Ports with and without Power supply for the box? It took for me also some time to find out which usb port on which laptop is usable for flashing with the usb burning tool. Even on two identical Thinkpads I need to use one of the usb 3.0 ports on the first laptop, but the other burns boxes only on the usb 2 port. Until I found the right ports burning also stopped at 7%, but at the "good" port it works mostly at first attempt. Once(after a power failure whilst flashing) I had to shorten a Pin on eMMC to get the box running again, but I'd try the different combinations of ports first because this bricked device was not recognized from burning tool at all. What about writing desired image onto sd card with amlogic boot card maker(or how it is called)and try to boot that?

..after creating the user it takes 2-5 minutes until login screen appears. I can reduce the time a bit by moving the mouse around while cursor is blinking. let the system work a little more time, it seems you are on the right path!.. btw. usually you need only to edit the uEnv.ini file to choose another dtb file..

..you are sure that you got eMMC on your box?!-many got problems if it is nand instead, which needs somehow another attempt..

Did you try to install it via the armbian-config tool? ..I always used that and got no problems to install..