Jump to content

SteeMan

Moderators
  • Posts

    2028
  • Joined

  • Last visited

Posts posted by SteeMan

  1. Get an SD card.  That is what 95% of people use on these boxes.

     

    Also if you want help, you need to be a lot more detailed than 'but reported it couldn't find the installation package'.  Logs/Screenshots are needed to even begin to help.

  2. 15 minutes ago, confuseruser said:

    Do you have any recommendations?

    Have you tried all of the uboot binaries as I suggested above?

     

    Also, you didn't answer my question about SD card.  Does the box have an SD card slot and have you tried that?

     

     

  3. Does the box have an sd card slot and have you tried booting from that?  (That is the common method).

     

    Also are you sure the box has an s905x3?  Have you opened the box and inspected the chip?  You might want to try all the uboot binaries just in case.

  4. I don't own that box so I can only give you generic help.  You really would need to hook up a usb-uart adapter to access the uboot debug output to see what is happening.

    The second thing I would say is that I have no idea what ophub builds do as they are not Armbian builds, ophub is a fork, they don't contribute to Armbian development nor do they participate in these forums.  So per the Armbian amlogic TV box instructions, the boot environment must be a clean android boot environment.  Installing or running any other distribution may cause Armbian to not boot.  So I'd recommend either reinstalling a clean Android image to test from, or investigate any differences in boot scripts to see what might be going on.  But again getting access to the new boot serial console would help a lot.

  5. 8 hours ago, chairman said:

    compiled u-boot with newer sources

    You need to apply the patch to newer sources to build a newer uboot.  But the patch will need to be modified (ported) to newer sources as code in uboot changes.  That is the whole point of the suggestions I'm this thread.  Port the patch to newer uboots and build them to see if newer uboots fix the problem.

  6. On 3/23/2026 at 6:44 PM, wedok said:

    can you please say, where i can find: Armbian_community_25.11.0-trunk.413_Aml-s9xx-box_plucky_edge_6.18.0-rc3.img

    truck.xxx builds are daily/weekly rolling release builds and are not archived. 

  7. 17 minutes ago, wedok said:

    Minix Neo U1
    Armbian_community_26.2.0-trunk.606_Aml-s9xx-box_trixie_current_6.18.18_minimal.img
    win32diskimager to sandisk 16gb sdcard
    extlinux.conf -> fdt /dtb/amlogic/meson-gxbb-wetek-play2.dtb
    =NOBOOT!!!

    First some logs would be helpful.  You may have to solder a usb-uart connector to the debug uart pads on your board to get boot log information.  Without knowing what is going on, diagnosis is difficult.

     

    Second, you don't say which u-boot you are using.  Can you provide that information?

     

    Finally, why are you using the wetek-play2.dtb for this box?

     

  8. 37 minutes ago, James Lewis said:

    a distinction between a server and desktop image...

    That is true that there are images that target server vs. desktop.  But they share the same kernel.

     

    I find what you are working on an interesting idea.  Good luck getting it working.

  9. 23 minutes ago, Bug Hunter said:

     

    Hello everyone,

     

    I have two identical-looking "arm-64" Amlogic TV boxes (S805X-based, meson-gxl-s805x-p241.dtb),

    In the world of TV boxes "identical looking" means nothing, as manufacturers build each batch with the lowest cost components available at the time.  There are many cases where identical looking boxes even contain different cpus ( ie amlogic vs rockchip).

    My recommendation would be first to verify the markings on the boards (there is usually some sort of board identifying text on the board)to really see if they are the same under the  hood.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines