SteeMan

  • Posts

    448
  • Joined

  • Last visited

Reputation Activity

  1. 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).
  2. 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! 
     
     
  3. 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.
     
     
     
     
  4. Like
    SteeMan got a reaction from TRS-80 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.
     
  5. Like
    SteeMan got a reaction from TRS-80 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.
     
  6. 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.
     
     
  7. 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.
  8. Like
    SteeMan got a reaction from jeanrhum 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.
  9. Like
    SteeMan got a reaction from jeanrhum 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.
  10. Like
    SteeMan got a reaction from jeanrhum 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.
  11. Like
    SteeMan got a reaction from tripole 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.
  12. Like
    SteeMan got a reaction from tripole 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.
  13. Like
    SteeMan got a reaction from jeanrhum 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.
  14. Like
    SteeMan got a reaction from jeanrhum 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.
  15. Like
    SteeMan got a reaction from Werner in Moderating question   
    I need to correct my last statement, as the post I was referring to was not deleted: "is to lazy to help any of us with the same problem ".  But I will still say that balbes150 is offended by language like this.
     
    Everyone needs to realize that Armbian on Android TV boxes (especially balbes150's builds) are not supported by the Armbian project.  And particularly the s905x3 cpu isn't supported by even balbes150.  Posting in these forums demands for support or calling others lazy for not providing support isn't in the spirit of the armbian community.  We all wish there was better support of mainline linux on all of these boxes, but without active support by the device manufacturers that isn't a reality.  The volunteers here do the best they can (and they do some amazing things when you think about it).
  16. Like
    SteeMan reacted to balbes150 in Best TVBOX for armbian used as micro services server   
    This information is already outdated and does not correspond to the current market situation.
     
    Make a mistake, rk3399 now has one of the best support in the main kernel (not to be confused with specific models of SbS or TV boxes, chip support and ready-made device support are not the same).
     
     
  17. Like
    SteeMan got a reaction from usual user in X96 Air (4/32 Go) and Wireless driver for RTL8822cs   
    I don't see anything in the links you have provided that this would be a solution to your problem.  Are you sure that you have the that chip on your board?  (i.e. have you opened the case and inspected?).  In order to get things working, you need to have your dtb, driver and hardware all in sync.  The dtb is the mapping between the hardware and the kernel, I would expect that this is the real source of your problems that your dtb is referencing different hardware than what you have installed on your board.  The problem with armbian for android tv boxes is that while there are only a few different reference dtbs available, but there are hundreds of different boards with different components from all the manufacturers.  So most of the boards will not work in some way because of the mismatch between their hardware and the dtbs that are available (sometimes you get lucky and everything you need works, but rarely does everything work).  As I have said in other threads, no one should approach armbian for these tv boxes expecting that everything will work (especially wifi and bluetooth - none of my boxes have working wifi or bluetooth) because that is not a reasonable expectation, unless the board manufacturer is supporting their boards by getting code into the mainline kernel.
     
    Having said all of that, it wouldn't hurt to try what you reference in the links above, and I suspect it is likely that the 5.6.1 based code would still work on a 5.7 kernel.
     
    You should also consider the long term support issues even if you do finally get something working.  You will likely find yourself in the position that at some future point in time when a new kernel update with important security fixes gets pushed out that it is no longer compatible with your custom built driver and then you will need to choose between security of your system or breaking your wifi support.  If you need wifi, I would recommend getting a cheap usb wifi adapter that has mainline kernel support as over the long run that will be best.
     
    However if your goal in all of this is to get your solution into future armbian builds (which really means getting it into mainline kernel) then keep hacking away.  But I would suspect that because you have already found a git repository that contains driver code that isn't in the mainline kernel (I am assuming this, but haven't verified), that that path has already been tried by others and rejected (lack of support of the code, poor code quality, or any number of other reasons).
  18. Like
    SteeMan got a reaction from Gaurav in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    If you have an A95X Max box as you say in a previous post, then you should have an Amlogic s905x2 cpu.   For that CPU per the instructions you should not be needing to do anything with uboot.  Just write the image to the sd card, edit the uEnv.txt file and boot from the sd card (toothpick method should work).  
  19. Like
    SteeMan got a reaction from thanxx in Armbian for Amlogic S905X3   
    blind@TX3X3:~$ free
                  total        used        free      shared  buff/cache   available
    Mem:        3684488      859436     2103944       24008      721108     2643560
    Swap:       1842240           0     1842240
    blind@TX3X3:~$
     
    This is on a TX3 with s905x3 using meson-sm1-sei610.dtb
     
    And on a H96 Max with s905x2 using meson-g12a-u200.dtb:
     
    blind@H96MaxX2:~$ free
                  total        used        free      shared  buff/cache   available
    Mem:        3365644      216796     1203640       21244     1945208     2966404
    Swap:       1682820           0     1682820
    blind@H96MaxX2:~$
  20. Like
    SteeMan got a reaction from balbes150 in Armbian for Amlogic S905X3   
    It is theoretically possible.  But I haven't seen this successfully done.  To undertake a task like this you need access to source code and support from the underlying device manufacturers, which generally doesn't exist.  (This is part of the reason that balbes150 doesn't support the s905x3 cpus as Amlogic does not provide support for their products under mainline kernels).
  21. Like
    SteeMan got a reaction from usual user in X96 Air (4/32 Go) and Wireless driver for RTL8822cs   
    I don't see anything in the links you have provided that this would be a solution to your problem.  Are you sure that you have the that chip on your board?  (i.e. have you opened the case and inspected?).  In order to get things working, you need to have your dtb, driver and hardware all in sync.  The dtb is the mapping between the hardware and the kernel, I would expect that this is the real source of your problems that your dtb is referencing different hardware than what you have installed on your board.  The problem with armbian for android tv boxes is that while there are only a few different reference dtbs available, but there are hundreds of different boards with different components from all the manufacturers.  So most of the boards will not work in some way because of the mismatch between their hardware and the dtbs that are available (sometimes you get lucky and everything you need works, but rarely does everything work).  As I have said in other threads, no one should approach armbian for these tv boxes expecting that everything will work (especially wifi and bluetooth - none of my boxes have working wifi or bluetooth) because that is not a reasonable expectation, unless the board manufacturer is supporting their boards by getting code into the mainline kernel.
     
    Having said all of that, it wouldn't hurt to try what you reference in the links above, and I suspect it is likely that the 5.6.1 based code would still work on a 5.7 kernel.
     
    You should also consider the long term support issues even if you do finally get something working.  You will likely find yourself in the position that at some future point in time when a new kernel update with important security fixes gets pushed out that it is no longer compatible with your custom built driver and then you will need to choose between security of your system or breaking your wifi support.  If you need wifi, I would recommend getting a cheap usb wifi adapter that has mainline kernel support as over the long run that will be best.
     
    However if your goal in all of this is to get your solution into future armbian builds (which really means getting it into mainline kernel) then keep hacking away.  But I would suspect that because you have already found a git repository that contains driver code that isn't in the mainline kernel (I am assuming this, but haven't verified), that that path has already been tried by others and rejected (lack of support of the code, poor code quality, or any number of other reasons).
  22. Like
    SteeMan got a reaction from Teddybee in Armbian for Amlogic S905X3   
    You didn't follow the instructions correctly.  The instructions say to "copy" the u-boot.sd file, not rename.  The install to emmc uses the u-boot.sd file so if it doesn't exist because you renamed it you would see the problems you are having.  Fix this situation on your sd card and redo the install to emmc.
  23. Like
    SteeMan reacted to balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    1. I don't owe anything.
    2. if you Want to get detailed documentation and dedicated resources for posting materials for download, pay 5000 to donate Armbian.
    3. I have a very negative attitude to those who use someone else's development for free (in which a lot of work\money\time of different people is invested), absolutely do not help this project in any way and at the same time make claims.
  24. Like
    SteeMan reacted to usual user in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    A devicetree is basically a standardized representation of the schematic of a board design. It provides parameters about the components used that drivers need to operate, or tell the kernel which driver to use in the first place. You can only recycle a DT if your device is a exact clone of an original device. Otherwise non matching components won't function properly.
    This is not the right way to proceed. This is as if you are using a disassembly of a binary program to rewrite the entire program. When compiling the original sources, information has been lost that cannot be reproduced during disassembly.
    The proper way is:
    You are the board designer with access to the reference documentation of all used components.
    You learn the syntax of DTS files.
    You write a board specific DTS with mainline binding documentation as reference.
    If your board design is based on e.g. a reference design from an SOC provider, you may be able to use his DTS as a template where you have only to adopt your modifications.
    When this is done, contribute it to mainline and it will work for all your customers out of the box. Of course, the kernel build must have enabled all required drivers.
                                 
    But I guess you are not in this situation So you have to do reverse engineering:
    Collect as many board details as possible.
    Learn the syntax of DTS files.
    Write a board specific DTS with mainline binding documentation as reference.
    You can use the original sources of meson-gxl-s905x-khadas-vim.dtb as a template and customize the differences (board model, compatible, Wi-Fi bindings, ...).
    Android DTs can only be used for hints, the bindings used are most likely proprietary and do not match those of the mainline kernel. Copying them over will not magically insert code into the kernel drivers to make use them.
    When this is done, contribute it to mainline and it will work for all. Armbian will probably pull it for early adoption if you provide a PR, as bringing it to mainline may take some time.
  25. Like
    SteeMan got a reaction from jock in Good Box for Linux?   
    There is a reason that the android TV boxes are so cheap.  They generally lack support by the manufacturers for main line linux especially for the items on your must have list (wifi, hardware video decoding/encoding).  In my opinion cheap should not be your deciding factor in what you choose to purchase as you might find that a regular SBC (raspberry pi or other, that has known support of the features you are looking for) may be the best fit and best supported option for you needs.  But if you want to explore and try things out, the android TV boxes are fun to work with, and if you go in understanding that something you want won't work well on the box you end up with, you are approaching these boxes with the right expectations. 
    For example I have four different types of boxes and wifi doesn't work on any of them.  But since I primarily use them as servers it works for me to use wired ethernet.
    I am sure that boxes exist that meet all of your criteria, but they are not likely to be the cheap boxes and you will need to spend a bit more money to get what you want and spend a lot of time researching.
    One final comment about the cheapest boxes is that identically labeled boxes with the same external markings can contain very different internal hardware.  My example is that I have two different TX3 mini's one has emmc for internal storage (which is what it is supposed to have) and the other has nand, unfortunately mainline kernels don't support internal nand storage so I ended up not being able to use the second box in the way I had intended.  But the manufactuer of the second box was able to save a bit of money by using components that cost them less and for most people using these for their intended purpose of Android wouldn't know the difference.