SteeMan

Members
  • Content Count

    116
  • Joined

  • Last visited

Reputation Activity

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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).
  8. 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).
     
     
  9. Like
    SteeMan got a reaction from Diamond 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).
  10. 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).  
  11. 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:~$
  12. 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).
  13. 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).
  14. 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.
  15. 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.
  16. 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.
  17. 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.
  18. Like
    SteeMan got a reaction from amirul 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.
  19. Like
    SteeMan got a reaction from Werner 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.
  20. Like
    SteeMan got a reaction from balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    Success!  Native build on TX3 X3 (s905x3) emmc of bionic server image took 208 minutes
  21. Like
    SteeMan got a reaction from balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    I was just happy it succeeded.  I will be trying other combinations over the next few days (I am doing a test from sd on the same box I ran last night right now).  I'll report more data points when I can.
  22. Like
    SteeMan got a reaction from balbes150 in Armbian for Amlogic S905X3   
    You have done a lot of things wrong and not mentioned many other important steps.  For example you are mixing and using pieces of old information that are unnecessary  at best, or problematic at worst.  For example don't use the files from NicoD, as everything you need is incorporated into the current RK + AML + AW builds.  You are also mixing builds, the build you started with is from February and it is now May.  The multiboot process evolves overtime and what got installed into your emmc by multiboot when you first tried may not be compatible with current builds.  Most importantly the key to success is the dtb file.  In your initial post you don't even mention what dtb you are trying.  The general rule is that you should try every dtb file compatible with your cpu (which in the case of the s905x3 would be all g12 and sm1 dtbs) to find the one that works best.
    Here is my recommendation: start fresh.  Start simple then build from there.  By this I mean don't worry about things like the color issue at all at the beginning, as that may not even be an issue for you.  Even if you have the color issue, the system is still usable.  Then once you have a baseline knowledge of what works and what doesn't, then try to get the remaining items working for your needs.  Be prepared to go back to a clean environment (i.e. back to fresh android firmware) multiple times in this process.
    I have a s905x3 based TX3X3 that I am now running happily (as a server without wifi or bt) but I have needed to restore the android firmware multiple times and started over when things just stop working for no apparent reason after I made changes to the box.  
    Finally,  set your expectations low.  You should be able to get a box that boots, has ethernet, hdmi and can be used as a server.  Everything else (wifi, bt, usable desktop, etc) is something that you may get with luck and a lot of hard work.  Unfortunately that is the situation with armbian on these android tv boxes since the device manufacturers  provide no support (in terms of source code or documentation) on their products so there is very little ability to get things working with armbian in any supportable way. (especially true with aml based boxes which is why balbes150 is no longer investing time into their support).
  23. Like
    SteeMan got a reaction from balbes150 in H96 Max dead - Can I revive it ?   
    I would repeat what balbes150 said above.  For working with amlogic based boxes, I would highly recommend that you get familiar with the USB Burn tool.  I have unbricked many a box with this after experimenting with something that failed.  To use this tool you will need an original android firmware image for your box from the manufacturer.  Generally a quick google search will lead you to one.  Then for less severe problems having a backup of the emmc using the ddbr tool within armbian will give you an easy mechanism to restore your emmc as long as you can still boot armbian from usb/sd.  I have a set of android firmwares for all the amlogic boxes I own and periodically make ddbr backups when I have something on the emmc that I don't want to lose.
  24. Like
    SteeMan got a reaction from Seb_Lz in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    The patch you are looking at is part of base armbian, it is not included in balbes150's arm-64 build.  (The patch is from meson64-dev and you are building arm-64-dev).  So even if the build did work, you wouldn't see the result you were looking for.
     
    The build for arm-64-dev is currently pointing to the linux kernel next branch, which is in the midst of the open merge window ahead of 5.7, this code will be unstable for a while, that is likely the reason for the build failures you are seeing.
  25. Like
    SteeMan got a reaction from aaditya in Infrastructure needed for releasing new kernels for Armbian for TV Boxes   
    Are you willing to take on this task and do this work?  I would say it is clear that the current maintainers here do not see this as a good investment of their time.  This is open source, and the best way to get something you need in open source is to step up and do the work and then contribute it back to the community.
     
    A couple of additional thoughts on your request:
    1) From what I have observed and know of the state of android on these TV boxes is that the dtb's from android are fairly worthless in helping getting things working under mainline kernels with armbian.  Everyone assumes this is not the case, but I haven't seen anything to indicate otherwise.  The gulf between ancient android based kernels and drivers (without source code in most cases) and modern mainline kernels is vast.
    2) You are making an assumption that "pushing adoption" is a good thing.  The way things currently stand, there are not sufficient people on these forums with the desire and knowledge to provide end user support for the existing new users much less a larger quantity of new users in the future.  What is needed now is people willing to answer the basic questions that new users post here, and to work on high quality documentation and tutorials (and maintain them as things change), so that the core developers can be relieved of the burden of providing this information so that they can spend more time moving the project forward.