Jump to content

SteeMan

Moderators
  • Posts

    1494
  • Joined

  • Last visited

Everything posted by SteeMan

  1. Moved to non-board specific forum, as this isn't a board specific question.
  2. I personally have multiple of that box, so I have no need for one. And currently no one else is contributing to the amlogic TV box code base in Armbian. So I'm not sure there is a need for them. But if someone wants one, they are welcome to respond to your post. Generally, however, TV boxes are cheap and easy to purchase, it is developers and their time that is expensive and in very short supply.
  3. @Maxxim Thanks for the report. The boot partition is created as vfat. I have noticed that s905x2 and s905x3 boxes are not booting with the 23.05 builds, but I thought the issue was with the u-boot files. Your report potentially points into a different direction. I don't know when I will have time to look into this. But this is community supported software so any contributions are appreciated.
  4. Since I don't have an s905l2 box, I'm not really in a position to integrate/test changes for such a box. If someone want to submit a PR that can test, I'd be happy to get it integrated. @Lavacat Note that your last post wasn't approved, because the site you mention is a fork of armbian that uses the Armbian name without permission and they do not contribute to the forums nor to armbian development.
  5. @callegar The 23.05 packages have not been released to the apt update repositories yet. There are issues being worked on. No ETA. The latest packages available are 23.02 based.
  6. Since you are installing a Ubuntu kernel not an Armbian kernel, (and these are Armbian forums), you should ask your question in a Ubuntu forum.
  7. Create a file named aml_autoscript.zip in the /boot directory and then try selecting that in recovery. The file should be empty. Since you are using the 23.05 builds, their are reports that the u-boot-s905x2-s922 file isn't working in that release. If you run into that issue you might want to go with an older build (something from 23.02). But first you need to get past the 'recovery' problem, before you will possibly run into the u-boot problem.
  8. First read this: Then you need to google and find out what CPU your box is using (note many boxes have the same/similar names), so start by finding boxes that look like yours and see if you can find spec listings that tell you the cpu. If that doesn't help, opening the box and looking at the physical chips. Once you determine the cpu then you can search the archives for others working on your type of box.
  9. You don't need to be 'accepted' to help. Anyone can submit PRs and contribute. I would recommend just getting active on the forum helping others, and any code improvements you can make for the device can be submitted as PRs.
  10. Moved to the correct forum. https://www.armbian.com/nanopi-neo
  11. If you submit a PR with the dtb changes they could be in base Armbian.
  12. You already have the answer to this question This is open source, you can report the problem and hope someone volunteers their time to research and fix (which is realistically unlikely to happen any time soon), you can dig in and fix it yourself and become part of the solution by contributing back to the open source communities, or you can pay for/hire someone to fix it for you. Those are realistically the only way things get fixed in open source. Complaining about something and calling into question the volunteer work others do to provide you something for free, isn't going to motivate anyone to help you.
  13. @2hry You should post your question in this thread:
  14. @2hry it looks like you are booting libreelec, these forums are for Armbian. Please ask in a forum site for Libreelec, we can't help you here
  15. The balbes150 builds where never upgradable. You need to use official builds for upgrades.
  16. Standard process, apt update/upgrade, assuming the kernel isn't frozen in armbian-config. armbian-config also has multiple options on switching kernels (current / edge, stable / nightly builds, etc)
  17. ? - What sbc are you working with? Generally you burn to SD card and then use armbian-config to move that install to emmc when you are happy with it.
  18. This forum is for Armbian not arch. This sub-forum is for amlogic based devices (not rockchip). Everything about your post is not appropriate. Please post arch questions in an arch forum. Don't hijack a post that is completely unrelated to your question.
  19. Upgrade to what newer version? A userspace version (i.e. ubuntu focal to ubuntu jammy) or a kernel upgrade (i.e. 23.02 based armbian kernel to 23.05 armbian kernel)? For userspace it is recommeded to do an install, as upgrades are not tested (but I just did a focal to jammy upgrade last night and they generally do work). For the kernel, you can just do apt update/upgrades to continue following the builds over time (assuming you don't have your kernel frozen in armbian-config).
  20. @helios thanks for posting that. One thing that has changed between the two versions is the name of the kernel image. It used to be uImage and is now Image. Can you look at the extlinux.conf files on the two versions to make sure they are changed appropriately for the kernel name change?
  21. The u-boot-s905x2-s922 file hasn't changed. So it shouldn't be necessary to copy that. Can you look at the file size of the two and also run diff on the two files. Again they should be the same as that file hasn't changed. If they are different, then something in the build process is causing a problem.
  22. Did you patch the Makefile so they build? For example a patch that adds dtbs: patch/kernel/archive/meson64-6.2/boards-g12-add-spi-nor-flash-enabled-dtbs.patch
  23. Can you add the version information for the builds you are trying that are not working. I'm otherwise just guessing.
  24. *minimal* is the key there, it really is minimal, you need to install armbianconfig if you want to use it: sudo apt install armbian-config (Note: since you have installed 23.05, the apt repositories don't yet have the 23.05 packages available (some issues still being addressed) so the apt install may not currently work until that is resolved)
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines