Jump to content

SteeMan

Moderators
  • Posts

    1446
  • Joined

  • Last visited

Posts posted by SteeMan

  1. Since this should be a community, and I don't have access to a box that has your issue (both of my m96mini's work with the default dtb).  I would encourage you to put together a PR in github for this change and contribute to the community.  However instead of modifiying the existing dtb, I would recommend your patch create a new dtb for your box.  It would also be helpful if you took pictures of the motherboard to see what chips you do have to be compared to what I have to see the differences.  This could also be accomplished through a dtb overlay as well, but I'm not sure how that would work with the extlinux.conf file as standard armbian support for overlays uses the armbianenv.txt file.

  2. 45 minutes ago, 0xNLC099 said:

    So, i'm actually very noob trating about this matter of android/kernel/linux

    You might want to consider either getting something that is supported or using a usb ethernet dongle.  Otherwise you have a steep learning curve ahead of you.

    I've personally never needed to extract a dtb from android, so I can't provide any guidance beyond what I have mentioned above.

  3. First please read the following TV Box FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

     

    Second, of the three major TV Box CPU families (Rockchip, Amlogic and Allwinner) Allwinner has the least support within the community.  There are a couple of allwinner knowledgeable people who occassionally post in this sub-forum, but there is little effort towards TV Boxes on allwinner cpus.

     

    Third, my best guess is that you need to either find or modify a dtd file to be specific to your hardware.  If you are using the legacy linux kernel you might be successful in extracting the dtb from android and trying that one.

  4. They have forked from Armbian and added additional layers.  They do not participate in Armbian core development nor post in the forums, so other than taking our code (which this is open source so that is fine), they have no relationship  with the Armbian community.  But because they continue to use the Armbian name, people come here for support, but since we don't make the builds or really know what they contain we can't support code we don't produce.

     

    5 minutes ago, JayJay said:

    as long as I use a kernel that has the <box_name>.dtb in it, it should be able to boot right?

    Not necessarily.  TV Box manufacturers have a habit of changing hardware (to produce the lowest cost devices) but reuse the same marketing names for the devices.  The internal components can vary significantly and therefore a dtb may or may not work for any given box.

     

    7 minutes ago, JayJay said:

    Can I pick something from https://github.com/armbian/community that says `aml-s9xx-box` instead and see if that works instead?

    Sure, that is what those builds are for.  https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus

     

  5. First please read the following TV Box FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

     

    Second, of the three major TV Box CPU families (Rockchip, Amlogic and Allwinner) Allwinner has the least support within the community.  There are a couple of allwinner knowledgeable people who occassionally post in this sub-forum, but there is little effort towards TV Boxes on allwinner cpus.

  6. First read the FAQ post about Armbian and TV Boxes: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

     

    Second, DTB files are kernel version specific since they are the mapping from the hardware to the kernel code.  So you can't take a dtb from an old kernel and expect it to work on a new one (especially when the old kernel is a heavily patched/android based kernel and the new one is mainline - as they will have very different implementations of basic support for these boards).

  7. Worked for me:

    [ o.k. ] U-Boot file name [ linux-u-boot-edge-nanopiduo_23.02.0-trunk_armhf.deb ]           [ o.k. ] Kernel file name [ linux-image-edge-sunxi_23.02.0-trunk_armhf.deb ]                [ o.k. ] Runtime [ 31:31 min ]                [ o.k. ] Repeat Build Options [ ./compile.sh  BOARD=nanopiduo BRANCH=edge RELEASE=jammy BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img  ]

  8. 10 hours ago, prutka said:

    You mean that I need to pass all those variables from this chapter to not have UI popup

    If you were to run this on a normal environment (it is designed to run on a PC (x86) running Ubuntu Jammy) you would see that at the end of the UI it prints out the command line equivalent of what you just entered through the UI,  So the UI is only invoked if a particular parameter isn't passed on the command line.  Experiment around and see how this works.

  9. On 11/26/2022 at 11:26 PM, winnt5 said:

    I am using 'Armbian_22.11.0-trunk_Aml-s9xx-box_kinetic_edge_6.0.9_xfce_desktop.img.xz' in https://github.com/armbian/community

    If you are still using this image, there is a script in /root that is used to copy the image to emmc. (It is part of the instructions for that build posted here:  https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus ) It brute forces some of the stuff you and hexdump have been discussing.  But as far as what and how to copy over, this can be a guide.

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines