Jump to content

SteeMan

Moderators
  • Posts

    1442
  • Joined

  • Last visited

Posts posted by SteeMan

  1. First off read:

     

    4 hours ago, KMfoliographics said:

    Now I will run Armbian_5.67_Aml-s805_Ubuntu_bionic_default_3.10.108_desktop_20181207 from @Balbes150

    You are asking about a build that is over three years old, for a kernel that is much older than that from a developer that has stopped working on amlogic tv boxes.  This isn't likely to lead to the results you are looking for.  The best advise I can give you is to read this thread:

    which contains the historic info about supporting the s805 cpu

  2. Which dtb are you using?

     

    Since you found someone who apparently got these things working, you would probably be best served by reaching out to them to see what they did to get wifi/sound working on this box.  It looks like they forked their build from armbian a while back and here is a link to the diff between the base armbian they forked from and their set of changes: https://github.com/armbian/build/compare  (Your answers are somewhere in that diff).  Since I don't own that box, there isn't much I can do beyond pointing you in these directions.

  3. Since there is no mainline linux kernel support for the s905x4 that I am aware of, I suspect that coreelec is using the android based kernel.

    Note that currently the boot environments for coreelec and armbian are incompatible.  So if you install coreelec, you will need to reflash android in order to use armbian.

    Also note that the armbian amlogic environment uses the native firmware (android installed) boot loader.

    You have an ambitious task ahead of you, good luck.

    Since Armbian is community based, anything want to submit to the project as a result of your efforts would be welcomed.  If you need advice on PR submittal, I'd be happy to help.

     

  4. @Gaaf What version did you originally have installed (file name and download location)?  How did you upgrade from 22.11.0 to 23.2.0?  It looks like you are switching from the current stable kernel to the unstable edge kernel?  How did you switch?  Is that what you intended?  Basically I need more information about your environment and how you have upgraded it, to be able to explain what you are seeing.

     

  5. I'm going to point you to the following two FAQ posts: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

    https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus

     

    But then tell you that no one has worked on s8xx cpu TV box builds for years around here.  So digging through the archives for some build that is a couple of years old will be your best bet, but it won't get any kernel updates, so you will be stuck on whatever version of the kernel you might get running.

  6. You are not using Armbian.  You have downloaded software from a site that is a fork of Armbian and uses the Armbian name without permission.  They do not participate in Armbian development, nor do they participate in these forums.  We can't help you here as we don't produce the code you are running.  You need to log your question with those you downloaded your software from.

  7. Another factor is that at least as far as the armbian builds go, there is no uboot suitable for your box available.  It isn't feasible/possible to build uboots for the hundreds of different tv box hardware configurations out there (and the tv box manufacturers don't release their source for their android uboots), so the uboot on the armbian build sd card is basically just a place holder (generic uboot that 100% is guaranteed not to work for your box).  The whole armbian amlogic tv box strategy is to use the uboot that comes with the tv box on emmc.  So if you are trying to get something working from sd, it isn't going to be armbian unless you can get your emmc working again.

  8. 16 minutes ago, stut said:

    Is there a thing I can do to always make it both from sd card?

    If your emmc is not working, I don't think you can.  My understanding is that these amlogic boxes basically are hard coded to look for uboot on emmc.  That is why the aml-s9xx-box builds use the emmc uboot to then chain load the distribution from sd/usb/etc.  It is always using the emmc uboot initially.  If your emmc is working, you should use recovery to reinstall the android uboot and then you could move on from there.  But in your case you have already tried that, and it didn't work (likely indicating that your emmc is not working).  Based on your comments, it sounds like you have previously reinstalled the android firmware, so you know that process used to work (the reason I am stating this, is that sometimes different boards/firmware combinations require specific versions of the amlogic burning tool)

  9. @Juan C. Guarnizo B I would first point you to this FAQ item on status of TV boxes under Armbian: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

    Second I would point out that the builds you reference are old (the newest is over a year old).  No one that I am aware of is currently spending any time on TV boxes under allwinner with armbian, and the builds you reference are not official Armbian builds, but builds produced by a community developer outside official Armbian distribution channels.

    So unless someone else from the community responds, you will need to have the skills to figure this out on your own, given the work jernej has provided.

  10. armbian-install will not work on amlogic tv boxes.  Please follow the instructions here: https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus

     

    Also, why did you abort the first run setup steps?  You may have left your box in an incomplete state that could cause issues in the future.

    On further thought, I think your box has the s905 cpu.  And installation to emmc isn't possible on this cpu.  The next generation amlogic cpus (s905x) are supported for internal emmc install.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines