SteeMan

  • Posts

    393
  • Joined

  • Last visited

Reputation Activity

  1. Like
    SteeMan reacted to TRS-80 in Please Read First   
    This is an adaptation of something @SteeMan wrote in this post, but we need to refer to it often enough that I thought I would make it into a sticky.
     
    Amlogic (S9xx) Android based TV Boxes

    1. They are not supported.
    2. A single developer (@balbes150) had worked years on getting things to the state they are.
    3. As of October 14th, 2020 balbes150 removed support for Amlogic CPUs, so that is the last build that will maybe work on your box.
    4. There is a very small number of people on this forum/club that are able to provide any guidance.
    5. Most likely no one on this forum/club has ever seen your specific box.
    6. Expectations should be set low (i.e. don't expect anything to work) but if you do get the box to boot, get HDMI and wired ethernet to work, you are doing good.
    7. You really shouldn't expect things like Wi-Fi, bluetooth, remote control, etc. to work.
    8. If you get this working on your box, it will likely only be useful for server type tasks, maybe a little light graphical desktop usage, but certainly not video/multimedia.
     
    Other RockChip (rk3399, rk3328, rk3288) and Allwinner (H5, H6) based TV Boxes
     
    9. These will continue to be supported within the limits that are possible for the equipment the devs possess.
    10. They are (in fact, have always been) CSC which means Community Support only!  In other words, not officially supported by the Armbian project!
     
    So, why even have these forums?
     
    As a place for people to try and get together and help one another.  At least it is something.
     
    Also, there used to be a lot more (better supported) activity here while balbes150 was still releasing his fork of Armbian.
     
    What other options do I have?
     
    I (@TRS-80) recommend cutting your losses and starting over, and this time around using the list of Armbian Supported Devices as a starting point for researching purchasing some other device.  Taking this approach will result in a much easier time, less hassle, better support, and usually for a much longer period of time (assuming things for your device get mainlined into Linux kernel).
     
    Even using that list as a starting point, do your homework.  As any particular device can have some little quirks / gotcha(s).  There are a lot of resources available on the (wider Armbian) forums already, please use them!
     
    @SteeMan however takes a different view.  He lay out his arguments in favor of trying anyway (see below) in spite of all the above.
     
    If you choose to go that route, at least we can say we warned you now. 
     
    Why is situation like this?
     
    Source of following quote was Armbian official Twitter, on 2020-12-02 11:23 EST:
     
     
    SteeMan also touch on this in his excellent post, below.
     
    Now hopefully you at least understand why most people may not wish to spend their own valuable free time to help someone who chose an unsupported box, mostly because it was cheap (and possibly without even doing much research beforehand).  SteeMan (and a few other guys in here like jock and some others) being the rare exceptions who relish a challenge.
     
    Good luck!
  2. Like
    SteeMan got a reaction from Master One in Current status of Armbian for X96 Air P3 4/64GB (S905X3)?   
    Most likely it will be the dtb that is the issue.
  3. Like
    SteeMan got a reaction from lanefu in Please Read First   
    I fully agree with @TRS-80 comments above directing most users towards officially supported SBC hardware options.  However, I do want to add my own personal thoughts on why I choose to continue to use these Android TV boxes with unsupported armbian running on them:
     
    1) It is a challenge and therefore a learning opportunity.  I would never have learnt to build my own linux kernels from source if I was still exclusively using x86 hardware.  If you want a challenge you will find it here.
     
    2) Price vs specs.  The Android TV boxes are built to be cheap consumer devices.  They are produced in larger quantities which drives down the per unit price.  You will generally not be able to get the same level of hardware for the same price with a standard SBC.  But that cheapness with - no support by the manufacturers and potentially sub-standard components.  If the manufacturers goal is to sell the lowest price box they are likely cutting corners somewhere to make that happen.
     
    3) emmc is standard.  TV boxes always come with internal storage while most SBCs do not.  Again from a price/performance standpoint having internal emmc storage vs running off an SD card is a plus.  emmc storage *should* be faster and longer lasting than storage on an sd card.  The caveats here being that this is one of the areas that the manufacturers may cut corners.  For example I have two TX3 mini boxes that are supposed to have 16GB of emmc memory (like the other TX3 mini boxes I have), but they were instead manufactured with cheaper nand memory for which there is no mainline kernel support.  There is no visible difference between the identically packaged boxes that had emmc vs those that came with nand, other than opening the case and looking at the physical chips on the boards.
     
    4) cases come standard.  TV boxes always come with cases, whereas for SBCs that is an extra cost.  For my uses having a case is a big improvement vs not having one.  A downside if that these cases are not necessarily well designed to provide adequate cooling.  So depending on your use case, overheating might be a problem.
     
    While I own both SBCs and TV boxes, I personally find the TV boxes work best for my needs (running server based software) and I enjoy the challenge of getting them running and keeping them running with the great underlying work that the armbian project is doing to build on top of.
     
    I feel that if someone wants to use *unsupported* armbian on TV boxes and has the correct expectations (set your expectations low) and is looking to learn and is up for a challenge these are fun things to work with.  And I look forward to working with you on these forums.
  4. Like
    SteeMan got a reaction from TRS-80 in Please Read First   
    I fully agree with @TRS-80 comments above directing most users towards officially supported SBC hardware options.  However, I do want to add my own personal thoughts on why I choose to continue to use these Android TV boxes with unsupported armbian running on them:
     
    1) It is a challenge and therefore a learning opportunity.  I would never have learnt to build my own linux kernels from source if I was still exclusively using x86 hardware.  If you want a challenge you will find it here.
     
    2) Price vs specs.  The Android TV boxes are built to be cheap consumer devices.  They are produced in larger quantities which drives down the per unit price.  You will generally not be able to get the same level of hardware for the same price with a standard SBC.  But that cheapness with - no support by the manufacturers and potentially sub-standard components.  If the manufacturers goal is to sell the lowest price box they are likely cutting corners somewhere to make that happen.
     
    3) emmc is standard.  TV boxes always come with internal storage while most SBCs do not.  Again from a price/performance standpoint having internal emmc storage vs running off an SD card is a plus.  emmc storage *should* be faster and longer lasting than storage on an sd card.  The caveats here being that this is one of the areas that the manufacturers may cut corners.  For example I have two TX3 mini boxes that are supposed to have 16GB of emmc memory (like the other TX3 mini boxes I have), but they were instead manufactured with cheaper nand memory for which there is no mainline kernel support.  There is no visible difference between the identically packaged boxes that had emmc vs those that came with nand, other than opening the case and looking at the physical chips on the boards.
     
    4) cases come standard.  TV boxes always come with cases, whereas for SBCs that is an extra cost.  For my uses having a case is a big improvement vs not having one.  A downside if that these cases are not necessarily well designed to provide adequate cooling.  So depending on your use case, overheating might be a problem.
     
    While I own both SBCs and TV boxes, I personally find the TV boxes work best for my needs (running server based software) and I enjoy the challenge of getting them running and keeping them running with the great underlying work that the armbian project is doing to build on top of.
     
    I feel that if someone wants to use *unsupported* armbian on TV boxes and has the correct expectations (set your expectations low) and is looking to learn and is up for a challenge these are fun things to work with.  And I look forward to working with you on these forums.
  5. Like
    SteeMan got a reaction from TRS-80 in MyGica 1960 S912B trying hard to get Ubuntu installed   
    @FHam 
    First I want to restate some of the basics around armbian on android tv boxes.  1) They are not supported.  2) A single developer (balbes150) has worked years on getting things to the state they are.  3) As of October 14th balbes150 removed support for amlog cpus, so that is the last build that will maybe work on your box, 4) There is a very small number of people on this forum/club that are able to provide any guidance, 5) Most likely no one on this forum/club has ever seen your specific box, 6) Expectations should be set low (i.e. don't expect anything to work) but if you do get the box to boot, get hdmi and wired ethernet to work, you are doing good.  7) Really don't expect things like wifi, bluetooth, remote control etc to work.  8) If you get this working on your box, it will likely only be useful for server type tasks, maybe a little light graphical desktop usage, but certainly not video/multimedia.
     
    There is a lot of information in the two threads you have opened on your installation problems.  I think at this point it would make sense to start from the beginning and step through the basics to try to help you.  There were a couple of very important questions asked of you in the old closed thread that you didn't answer.  I am going to make some recommendations in an effort to try to help.
    1) Use the latest/last build that supports amlogic cpus: https://yadi.sk/d/_rQgn_FosYuW0g/20.10/20201014
    2) Follow the instructions (I agree that the instructions are often not clear) from the first post of this thread: 
    I recently wrote a post that attempted to help someone better understand the instructions for an amlogic cpu as he was having difficulty understanding the instructions from balbes150.  This may help you:
     
     
     
    3) Pay particular attention to the first sentence in red.  If you have ever tried to install other linux builds on this box, stop.  You will first need to restore the box with an original android firmware before continuing.  This is true even if the box is still running android.  The key here is if you have ever 'attempted' to install something else.  The installation process for some other firmwares will modify the booting environment in ways that cause the armbian install to no longer work.  The armbiantv installation is dependent on an unmodified default android environment.  I have more than once solved problems I have had by reverting a box to a clean fresh state by reinstalling the android firmware.  Note, when I say reinstall the android firmware, that doesn't mean using the android functionality to reset the box, it means going out and finding the correct manufactures firmware file and using the low level amlogic tools to install that on your box.  This is one of the questions asked in the previous thread that you didn't answer, which is why I am spending so much time on it.  It is critical that the state of the box be known and clean otherwise we are all just wasting time.
     
    4) In your previous thread you have a screen shot showing you trying to run aml_autoscript.zip from android recovery.  From my understanding if you find yourself in android recovery you are doing something wrong.  No part of the installation process uses android recovery.  I have always been successful with the 'toothpick' method and would recommend you stick with that.  
     
    5)  The extlinux.conf file you posted in the previous thread had a number of errors in it.  Please post the extlinux.conf file you are currently trying to use.
     
    You are working with a box that isn't common.  I have no experience with it.  But by correctly following the installation, you may yet be successful. 
  6. Like
    SteeMan got a reaction from FHam in MyGica 1960 S912B trying hard to get Ubuntu installed   
    @FHam 
    First I want to restate some of the basics around armbian on android tv boxes.  1) They are not supported.  2) A single developer (balbes150) has worked years on getting things to the state they are.  3) As of October 14th balbes150 removed support for amlog cpus, so that is the last build that will maybe work on your box, 4) There is a very small number of people on this forum/club that are able to provide any guidance, 5) Most likely no one on this forum/club has ever seen your specific box, 6) Expectations should be set low (i.e. don't expect anything to work) but if you do get the box to boot, get hdmi and wired ethernet to work, you are doing good.  7) Really don't expect things like wifi, bluetooth, remote control etc to work.  8) If you get this working on your box, it will likely only be useful for server type tasks, maybe a little light graphical desktop usage, but certainly not video/multimedia.
     
    There is a lot of information in the two threads you have opened on your installation problems.  I think at this point it would make sense to start from the beginning and step through the basics to try to help you.  There were a couple of very important questions asked of you in the old closed thread that you didn't answer.  I am going to make some recommendations in an effort to try to help.
    1) Use the latest/last build that supports amlogic cpus: https://yadi.sk/d/_rQgn_FosYuW0g/20.10/20201014
    2) Follow the instructions (I agree that the instructions are often not clear) from the first post of this thread: 
    I recently wrote a post that attempted to help someone better understand the instructions for an amlogic cpu as he was having difficulty understanding the instructions from balbes150.  This may help you:
     
     
     
    3) Pay particular attention to the first sentence in red.  If you have ever tried to install other linux builds on this box, stop.  You will first need to restore the box with an original android firmware before continuing.  This is true even if the box is still running android.  The key here is if you have ever 'attempted' to install something else.  The installation process for some other firmwares will modify the booting environment in ways that cause the armbian install to no longer work.  The armbiantv installation is dependent on an unmodified default android environment.  I have more than once solved problems I have had by reverting a box to a clean fresh state by reinstalling the android firmware.  Note, when I say reinstall the android firmware, that doesn't mean using the android functionality to reset the box, it means going out and finding the correct manufactures firmware file and using the low level amlogic tools to install that on your box.  This is one of the questions asked in the previous thread that you didn't answer, which is why I am spending so much time on it.  It is critical that the state of the box be known and clean otherwise we are all just wasting time.
     
    4) In your previous thread you have a screen shot showing you trying to run aml_autoscript.zip from android recovery.  From my understanding if you find yourself in android recovery you are doing something wrong.  No part of the installation process uses android recovery.  I have always been successful with the 'toothpick' method and would recommend you stick with that.  
     
    5)  The extlinux.conf file you posted in the previous thread had a number of errors in it.  Please post the extlinux.conf file you are currently trying to use.
     
    You are working with a box that isn't common.  I have no experience with it.  But by correctly following the installation, you may yet be successful. 
  7. Like
    SteeMan reacted to FHam in MyGica 1960 S912B trying hard to get Ubuntu installed   
    Thank You "TRS-80", I appreciate your response. 
     
  8. Like
    SteeMan reacted to pomelo in u-boot- files location.   
    I am very grateful that you replied to this topic.
    I had to wait 24 hours to reply to this post because I am a new user and I can only post 1 post per day. I am using a MXQPRO_II which is the name I see when I boot into recovery. It has 1GB Ram and has S905X Chip. I managed to boot into CoreELEC and LibreELEC.
    After going to the link you shared and using dd to write "Armbian_20.11_Arm-64_buster_current_5.9.8" I edited the extlinux.conf and selected the gxl212 dtb because in LibreELEC it worked.
    So flashed the image in the SD card and edited extlinux.conf and tried to boot by typing "recovery update" on a terminal emulator on the box. It didn't work. I could enter recovery but that's it. If I select either "Reboot to System" or "Reboot to bootloader", I boot into the default Android OS. 
     
    Can you suggest what I should do to get linux up and running on the MXQPro_II box(S905x, 1GB RAM)? I am planning on installing SNORT and using it as an intrusion detection system if I managed to run linux on it. 
    P.S. I probably won't be able to reply before 24 hours because I am a new user.
  9. Like
    SteeMan got a reaction from TRS-80 in Current status of Armbian for X96 Air P3 4/64GB (S905X3)?   
    Yes it is possible.  The dtb is the mapping of all the hardware to the software (not just the cpu).  So a dtb that isn't a perfect fit for the cpu may work overall better for the rest of the hardware on the board.  For amlogic cpus the differences between the s905x2 and s905x3 series are not major, so a dtb for an x2 board may work as good or better for your x3 based board.  So I would look at the meson-g12a-*.dtb files as well.
  10. Like
    SteeMan got a reaction from Master One in Current status of Armbian for X96 Air P3 4/64GB (S905X3)?   
    Yes it is possible.  The dtb is the mapping of all the hardware to the software (not just the cpu).  So a dtb that isn't a perfect fit for the cpu may work overall better for the rest of the hardware on the board.  For amlogic cpus the differences between the s905x2 and s905x3 series are not major, so a dtb for an x2 board may work as good or better for your x3 based board.  So I would look at the meson-g12a-*.dtb files as well.
  11. Like
    SteeMan got a reaction from TRS-80 in Current status of Armbian for X96 Air P3 4/64GB (S905X3)?   
    As long as you understand the limitations that dante6913 mentioned, and as long as you are only expecting to use it for server work, and I would add one additional item that you should only be expecting to use wired ethernet (wifi/bluetooth support is very spotty).
    I would recommend just trying the last build that supports amlogic cpus (The 5.9.0 October 14th 2020 build) and follow the instructions in the first post of this thread:
    Try the various dtbs for s905x3, sm1 (or s905x2, g12a) and see if any of them work well enough for your needs.  I have a TX3x3 box which contains a s905x3 and I use the meson-sm1-sei610.dtb for that box. 
     
    The one thing specific to the s905x3 that might be unclear from the instructions on that post is that you will need to copy the u-boot-s905x2-s922 file to u-boot.ext as there is no x3 specific version, but the x2 version should work (at least it does on my TX3x3 box).
  12. Like
    SteeMan got a reaction from Master One in Current status of Armbian for X96 Air P3 4/64GB (S905X3)?   
    As long as you understand the limitations that dante6913 mentioned, and as long as you are only expecting to use it for server work, and I would add one additional item that you should only be expecting to use wired ethernet (wifi/bluetooth support is very spotty).
    I would recommend just trying the last build that supports amlogic cpus (The 5.9.0 October 14th 2020 build) and follow the instructions in the first post of this thread:
    Try the various dtbs for s905x3, sm1 (or s905x2, g12a) and see if any of them work well enough for your needs.  I have a TX3x3 box which contains a s905x3 and I use the meson-sm1-sei610.dtb for that box. 
     
    The one thing specific to the s905x3 that might be unclear from the instructions on that post is that you will need to copy the u-boot-s905x2-s922 file to u-boot.ext as there is no x3 specific version, but the x2 version should work (at least it does on my TX3x3 box).
  13. Like
    SteeMan reacted to Tomas Catone in [SOLVED] Fix Eth or Wifi on T95z Plus   
    Thanks @SteeMan !!
     
    Still learning.  I was getting a quick error when enabling RDP inside the Armbian config.  Updated everything and reinstalled xrdp and the error went away.  A couple of reboots later and now RDP is working!!!  Success!!
     
    I have installed Teamviewer Host.  They have a .deb install file for ARM-32 (no 64 bit file available) so installation wasn't hard.  Not working exactly right yet... but wrenching on it but it lost priority now that RDP is working...
     
    When will I be able to post more than 1x a day?  Or a link?  It deleted my link in my earlier post.  Just asking.
     
    "Firmware" is inside Armbian config but after looking at it more closely it is "apt update and apt upgrade".  So I am doing it recursively until it says there is nothing more to upgrade.  Hope that doesn't mess anything up.
     
    "Freeze" inside Armbian config says it will disable the Armbian kernel upgrade.  Sounds wise since 20.11 doesn't support Amlogics cpu.  Agreed?

    Interesting tidbit - I changed the background to one of the blue xfce mice but for some reason it only stays for a little while and then goes back to the grey penguin.  Reboot brings back the blue for a little while.  Just odd. 
     
    Other progress:  I tested almost all Amlogic .dtb device tree files .  I appreciate the link to the work of @mumpitzstuff on compiling dtb files.  I compiled the one he used for my tv box - but it didn't work.  Then I tried pasting together a file of my own from a couple of stock dtb files - but that didn't fix anything.  The meson-gxm-vega-s96.dtb file is what I am using and it has working ethernet so that is what I NEED.  Meson-gxm-q200-n1.dtb shows a wifi symbol in the top left corner after boot but my mouse and keyboard don't work.  Meson-gxm-beelink-gt1 seems to have working Bluetooth.  I might work more on compiling my own dtb file but at this point I am moving onto Samba setup and Plex setup.  I think my homebrew dtb file idea is missing the actual drivers for the chips so even after defining the device tree I still need to somewhere somehow add the drivers?
     
    Well - that is the update for today.  Seem to be inching towards my goal. 
     
    Any tips/tricks or ideas are appreciated. 
     
    @Gio Giogio - sorry - I can't post links so the one I sent you got auto-deleted above.  But have a look for reddit getting_armbian_to_boot_on_sunvell_t95z_plus and I bet you can use that to get over the first hurdles. 
     
    Thanks again! 
     
     
  14. Like
    SteeMan got a reaction from TRS-80 in Is there an image for the Magicsee N5 Plus (S905X3)   
    Technically no android tv boxes are supported.  The work in these tv box forums is all experimental and unsupported by the official armbian project.  The balbes150 fork of armbian that is often referred to as armbian tv has never claimed to work on s905x3 cpus.  And after the Oct 14th build no longer will work with any amlogic cpus at all.  
    Having said that, I have a TX3 X3 box with an s905x3 cpu that is running armbian, so it isn't a lost cause.  But since each box is different, you may not be as lucky with your box.  There is a thread that discusses the s905x3 boxes as various people reported their successes and problems over time.
     
     
     
    If you want to give it a try, you can get follow the instructions in the first post of the following thread, using the Oct 14th kernel 5.9.0 build.
     
     
     
     
  15. Like
    SteeMan got a reaction from fuho in Can not find image to download for TX3 mini   
    Given that you do have general linux knowledge and rpi familiarity, here are my comments on your requests.
    I have 4 TX3 mini's three of which I run armbian on and one that I use the original android on.  I will mention that just because a box is labeled TX3 mini, doesn't mean the internals are the same.  The manufactures put identical external branding on boards that may be significantly different.  For example all TX3 minis claim they have emmc storage in them.  But only two of my TX3 minis have emmc storage, the other two come with nand storage (cheaper to manufacture that way).  Since mainline linux doesn't support nand I can only install armbian on internal storage on two of my boxes.
     
    From the above linked post you need to download an image file from any of the download locations.  The file you are looking for is the arm-64 version from October 14th 2020.  These are the last versions from balbes150 to support Amlogic cpus.  So be warned that when and if you get this running on your TX3 mini box, there is currently no path to get anything newer than this Oct 14 build with 5.9.0 kernel.  You will get updates from your chosen distribution (debian or ubuntu) just no kernel updates, unless someone else in the community picks up the ball and begins building/maintaining amlogic kernels.
     
    In the downloads directory you will find builds for debian (buster and bullseye) and ubuntu (bionic and focal), along with both a desktop and non-desktop version of each.
     
    Once you download your chosen build (for example  https://users.armbian.com/balbes150/arm-64/Armbian_20.10_Arm-64_focal_current_5.9.0.img.xz - ubuntu focal non-desktop build)
    You need to burn the image to an SD card.  Generally balenaEtcher is recommended (however I have only ever used dd on linux to create my sd cards, so I have no familiarity with that tool)
     
    Once you have the SD card with your chosen build, then you need to edit the boot configuration file on the SD card.  In the BOOT partition of the SD card there will be a file /boot/extlinux/extlinux.conf, that you need to edit. (In earlier builds this was done in the /boot/uEnv.txt file, so a lot of comments in these threads talk about that file, but in the latest builds it was changed to the extlinux.conf file)
     
    Your extlinux.conf file should look like:
    LABEL Armbian
    LINUX /zImage
    INITRD /uInitrd
    # aml s9xxx
    #FDT /dtb/amlogic/meson-gxbb-p200.dtb
    FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.dtb
    #FDT /dtb/amlogic/meson-gxm-q200.dtb
    #FDT /dtb/amlogic/meson-g12a-x96-max.dtb
    #FDT /dtb/amlogic/meson-g12b-odroid-n2.dtb
    APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
     
    Basically you need to have the correct dtb for your box and the correct boot command for your box, along with the top three environment variables set.  *Everything* else needs to either be deleted or commented out.  This is a common mistake where people uncomment out what they need, but leave other lines in the file not uncommented and thus they fail to boot.  The extlinux.conf file above is directly from my TX3 mini box.  Note that if you were using a different box than a TX3 mini, you would attempt to use different dtb files until you found the one that works the best for you boxes hardware (there are a bunch of dtb files in /boot/dtb/... to try depending on your cpu architecture and hardward).
     
    Next you need to copy the correct uboot for your box.  This is needed for amlogic cpus (other cpus have different uboot stuff to do).  For your TX3mini you need to copy u-boot-s905x-s912 to u-boot.ext (note I say copy not move).
     
    Once you have your SD card prepared, on an Amlogic box you need to enable multiboot.  There are different ways documented to do this, but for your TX3 mini box, you should use the toothpick method.  At the back of the audio/video jack connector is a hidden reset button.  By pressing that button with a toothpick or other such pointed device you can enable multiboot.  What you need to do is have the box unpluged, have your prepared sd card inserted, then press and hold the button while inserting the power connector.  Then after a bit of time you can release the button.  (I don't know exactly how long you need to hold the button after power is applied, but if it doesn't work the first time try again holding for longer or shorter times).
     
    You should now be booting into armbian/linux.
     
    If you want at this point, you can copy the installation to emmc (assuming your box has emmc).  You do this by running the appropriate shell script in /root, which for your case is /root/install-aml.sh.  Note that it is recommended that you make a backup of emmc first (use the ddbr tool that should be installed on your sd card).  Also be prepared if anything goes horribly wrong with your emmc install to reinstall the armbian firmware using the Amlogic USB Burning Tool to unbrick your device.  It is pretty easy to find TX3mini android firmwares on the internet and you can generally recover a bricked box using the Amlogic tool and an original firmware file.
     
    Finally, I have written this from memory and haven't been actually doing these steps as I am writing, so there might be something I forgot to say, so I make no promises that this is completely accurate, but I think it is.
     
    Also, don't expect that all parts of your TX3mini box will work.  You should have a working boot, working wired ethernet and working hdmi.  Don't expect things like wifi, bluetooth, infrared remote, box display to work.  The experimental armbian for these boxes is enough to get a basic server running and a light graphical display, but don't expect full functionality.
     
  16. Like
    SteeMan got a reaction from Mason in Can not find image to download for TX3 mini   
    Given that you do have general linux knowledge and rpi familiarity, here are my comments on your requests.
    I have 4 TX3 mini's three of which I run armbian on and one that I use the original android on.  I will mention that just because a box is labeled TX3 mini, doesn't mean the internals are the same.  The manufactures put identical external branding on boards that may be significantly different.  For example all TX3 minis claim they have emmc storage in them.  But only two of my TX3 minis have emmc storage, the other two come with nand storage (cheaper to manufacture that way).  Since mainline linux doesn't support nand I can only install armbian on internal storage on two of my boxes.
     
    From the above linked post you need to download an image file from any of the download locations.  The file you are looking for is the arm-64 version from October 14th 2020.  These are the last versions from balbes150 to support Amlogic cpus.  So be warned that when and if you get this running on your TX3 mini box, there is currently no path to get anything newer than this Oct 14 build with 5.9.0 kernel.  You will get updates from your chosen distribution (debian or ubuntu) just no kernel updates, unless someone else in the community picks up the ball and begins building/maintaining amlogic kernels.
     
    In the downloads directory you will find builds for debian (buster and bullseye) and ubuntu (bionic and focal), along with both a desktop and non-desktop version of each.
     
    Once you download your chosen build (for example  https://users.armbian.com/balbes150/arm-64/Armbian_20.10_Arm-64_focal_current_5.9.0.img.xz - ubuntu focal non-desktop build)
    You need to burn the image to an SD card.  Generally balenaEtcher is recommended (however I have only ever used dd on linux to create my sd cards, so I have no familiarity with that tool)
     
    Once you have the SD card with your chosen build, then you need to edit the boot configuration file on the SD card.  In the BOOT partition of the SD card there will be a file /boot/extlinux/extlinux.conf, that you need to edit. (In earlier builds this was done in the /boot/uEnv.txt file, so a lot of comments in these threads talk about that file, but in the latest builds it was changed to the extlinux.conf file)
     
    Your extlinux.conf file should look like:
    LABEL Armbian
    LINUX /zImage
    INITRD /uInitrd
    # aml s9xxx
    #FDT /dtb/amlogic/meson-gxbb-p200.dtb
    FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.dtb
    #FDT /dtb/amlogic/meson-gxm-q200.dtb
    #FDT /dtb/amlogic/meson-g12a-x96-max.dtb
    #FDT /dtb/amlogic/meson-g12b-odroid-n2.dtb
    APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
     
    Basically you need to have the correct dtb for your box and the correct boot command for your box, along with the top three environment variables set.  *Everything* else needs to either be deleted or commented out.  This is a common mistake where people uncomment out what they need, but leave other lines in the file not uncommented and thus they fail to boot.  The extlinux.conf file above is directly from my TX3 mini box.  Note that if you were using a different box than a TX3 mini, you would attempt to use different dtb files until you found the one that works the best for you boxes hardware (there are a bunch of dtb files in /boot/dtb/... to try depending on your cpu architecture and hardward).
     
    Next you need to copy the correct uboot for your box.  This is needed for amlogic cpus (other cpus have different uboot stuff to do).  For your TX3mini you need to copy u-boot-s905x-s912 to u-boot.ext (note I say copy not move).
     
    Once you have your SD card prepared, on an Amlogic box you need to enable multiboot.  There are different ways documented to do this, but for your TX3 mini box, you should use the toothpick method.  At the back of the audio/video jack connector is a hidden reset button.  By pressing that button with a toothpick or other such pointed device you can enable multiboot.  What you need to do is have the box unpluged, have your prepared sd card inserted, then press and hold the button while inserting the power connector.  Then after a bit of time you can release the button.  (I don't know exactly how long you need to hold the button after power is applied, but if it doesn't work the first time try again holding for longer or shorter times).
     
    You should now be booting into armbian/linux.
     
    If you want at this point, you can copy the installation to emmc (assuming your box has emmc).  You do this by running the appropriate shell script in /root, which for your case is /root/install-aml.sh.  Note that it is recommended that you make a backup of emmc first (use the ddbr tool that should be installed on your sd card).  Also be prepared if anything goes horribly wrong with your emmc install to reinstall the armbian firmware using the Amlogic USB Burning Tool to unbrick your device.  It is pretty easy to find TX3mini android firmwares on the internet and you can generally recover a bricked box using the Amlogic tool and an original firmware file.
     
    Finally, I have written this from memory and haven't been actually doing these steps as I am writing, so there might be something I forgot to say, so I make no promises that this is completely accurate, but I think it is.
     
    Also, don't expect that all parts of your TX3mini box will work.  You should have a working boot, working wired ethernet and working hdmi.  Don't expect things like wifi, bluetooth, infrared remote, box display to work.  The experimental armbian for these boxes is enough to get a basic server running and a light graphical display, but don't expect full functionality.
     
  17. Like
    SteeMan got a reaction from TRS-80 in Can not find image to download for TX3 mini   
    Follow the information in the first post in the following thread.  Note that the October 14, 2020 build of 5.9.0 is the last build that will have the necessary boot scripts to run on Amlogic boxes.
     
     
  18. Like
    SteeMan got a reaction from TRS-80 in Can not find image to download for TX3 mini   
    To answer this, you need to tell us what you are planning to do with your tx3 mini box.  Also if you could let us know your experience level with linux and different linux distributions that would be helpful as well.
  19. Like
    SteeMan got a reaction from Tucano2000 in Armbian for Amlogic S905X3   
    Technically Balbes never supported the s905x3. But it is true that he is now ending support of all amlogic cpus.  I already make my own kernel builds, and since I own a few different amlogic based boxes, I have an interest in seeing support continue in some form.  I have asked balbes in another thread if he would tag his public github repositories with a tag that corresponds to his last build supporting amlogic, which then can be a starting point for continued support by the community if there is enough interest.
  20. Like
    SteeMan got a reaction from fab6768 in Armbian for Amlogic S905X3   
    Technically Balbes never supported the s905x3. But it is true that he is now ending support of all amlogic cpus.  I already make my own kernel builds, and since I own a few different amlogic based boxes, I have an interest in seeing support continue in some form.  I have asked balbes in another thread if he would tag his public github repositories with a tag that corresponds to his last build supporting amlogic, which then can be a starting point for continued support by the community if there is enough interest.
  21. Like
    SteeMan got a reaction from KY69 in Armbian for Amlogic S905X3   
    Technically Balbes never supported the s905x3. But it is true that he is now ending support of all amlogic cpus.  I already make my own kernel builds, and since I own a few different amlogic based boxes, I have an interest in seeing support continue in some form.  I have asked balbes in another thread if he would tag his public github repositories with a tag that corresponds to his last build supporting amlogic, which then can be a starting point for continued support by the community if there is enough interest.
  22. Like
    SteeMan got a reaction from stut in Information for users of TV boxes on the Amlogic platform   
    @balbes150 If I could ask a favor of you.  Would it be possible to add a tag to your public github repositories that corresponds to your last build supporting AML?  With a tagged version of source code that corresponds to your final released build others can pick up where you have left off if they are capable and motivated.  I appreciate your dedication to armbian and respect your decision to end your support of Amlogic cpus.
  23. Like
    SteeMan got a reaction from Gausus in Information for users of TV boxes on the Amlogic platform   
    @balbes150 If I could ask a favor of you.  Would it be possible to add a tag to your public github repositories that corresponds to your last build supporting AML?  With a tagged version of source code that corresponds to your final released build others can pick up where you have left off if they are capable and motivated.  I appreciate your dedication to armbian and respect your decision to end your support of Amlogic cpus.
  24. Like
    SteeMan got a reaction from Gausus in Armbian for Amlogic S905X3   
    Technically Balbes never supported the s905x3. But it is true that he is now ending support of all amlogic cpus.  I already make my own kernel builds, and since I own a few different amlogic based boxes, I have an interest in seeing support continue in some form.  I have asked balbes in another thread if he would tag his public github repositories with a tag that corresponds to his last build supporting amlogic, which then can be a starting point for continued support by the community if there is enough interest.
  25. Like
    SteeMan got a reaction from tripole in Armbian for Amlogic S905X3   
    Technically Balbes never supported the s905x3. But it is true that he is now ending support of all amlogic cpus.  I already make my own kernel builds, and since I own a few different amlogic based boxes, I have an interest in seeing support continue in some form.  I have asked balbes in another thread if he would tag his public github repositories with a tag that corresponds to his last build supporting amlogic, which then can be a starting point for continued support by the community if there is enough interest.