Jump to content

SteeMan

Moderators
  • Posts

    1387
  • Joined

  • Last visited

Everything posted by SteeMan

  1. I noticed today that there are no 23.02 images for the rockpi-4c. The images exist for the 4a, 4b and 4cplus variants but not the 4c. The 22.11 images are the latest for the 4c. The reason I noticed is that on the downloads page for the rockpi4 it is still showing 22.11 as the current images because that page is showing the 4c info, with links provided to the other variants. The fact that it still showed 22.11 caught my eye.
  2. So I had some more time today, I restored my test x96 mini box back to android, then downloaded the current jammy 23.02 build: Armbian_23.02.2_Aml-s9xx-box_jammy_current_6.1.11.img.xz, installed it onto sd card using balenea, copied u-boot-s905x-s912 -> u-boot.ext, edited the extlinux.conf to use: FDT /dtb/amlogic/meson-gxl-s905w-p281.dtb Inserted the sd card, pressed and held reset button, plugged in power, waited about 2 seconds, released the reset button and it booted into Armbian jammy. So it works for me. Things to check for: are you sure you are using a quality sd card? Are you sure you have properly copied the u-boot.ext? While I don't think it would be an issue with the android firmware you are using, especially as you have tried different ones, the one I am using (don't know where I got it, as I downloaded it years ago) is of size: 1,566,582,416
  3. With the current release (23.2) Armbian has moved to using the Plymouth package for the boot screen (for most if not all boards). I personally don't know much about it, but the resource files are in /usr/share/plymouth/themes/armbian
  4. Why do you mention android roms? The reset button has nothing to do with installing android roms.
  5. @Wilson The only suggestions I have, are when using the amlogic usb tools, that you try all of the usb ports on your box and that you try different versions of the tool. I've had cases where only older versions worked with some of my older boxes. But it does tend to be finicky. And sometimes pushing the reset button as part of the process has helped me.
  6. @maka armbian-install is the command in a standard Armbian build (as of 22.11 and later) that installs from sd card to emmc or other storage. Since that is what the author of this post was doing there is nothing to indicate that he is using a non-armbian build. Although your point that armbian-install is used for a different purpose in non-armbian builds is a good one, based on the content of this thread it didn't seem to me there was any indication that the author was not using an armbian build, but it is a possibility.
  7. recovery mode has nothing to do with using the amlogic usb burning tool. Have you tried different usb ports? Also, I've had some boards only work with specific versions of the amlogic usb burning tool.
  8. I don't have this box (nor any s912 based box), so I can only suggest you search the archives for similar issues. I know I have seen threads discuss similar issues (can't boot headless without an hdmi connected for other sbc's, and if I recall correctly the workaround was to buy some sort of null hdmi connector, which tricks the box into thinking an hdmi is connected). Also, it could be a dtb issue, I would suggest trying all of the s912 based dtbs.
  9. How long are you holding the reset button. Try different lengths of time between 2 and 10 seconds. It sounds like you are holding it too long and it is booting into android recovery). If you are seeing repeated booting, you are holding it too long.
  10. The aml-s9xx-box builds don't use a boot.ini file.
  11. This is expected behavior. Each distribution is modifying the boot environment in different incompatible ways. That is why the install instructions (https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus) say if you have tried to install other distributions, you will need to restore to a clean android firmware before installing armbian.
  12. Let me first say welcome to Armbian. Second I want to point you to this basic information: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Finally, I've never looked into trying to do this, and I don't recall any recent forum discussions on this. There might be something if you searched through the forum archives.
  13. I think this box runs on an rk3188 cpu. Moving post to the rockchip tv box forums.
  14. Running armbian-install will corrupt your emmc. You need to run install-aml.sh like the instructions say. I checked and that script exists in /root for the latest build. You will need to reinstall an original android firmware to get your box back to working.
  15. FYI a workaround reply to the bug report: "Confirm, when doing kernel config during image build -- it can be worked-around by running ./compile.sh with command kernel-config, for now. I will try to come up with a way to make this work during image build, but inconsistencies arise, so fix is more complex than originally thought"
  16. You can do the equivalent by having a patch to the kernel Makefile that does the same thing to it's version number
  17. @belegdol On your first point, yes that is a one time issue as a result of using the kernel version. While undesirable, I believe it is a necessary change. On your second point, while I understand your point and the functionality has changed, it also didn't work the way you wanted under the old master branch. In the master branch the .deb files end up with the same version number across builds, there is no incremental build number. The version is the armbian version and thats all. At least in the new main branch the version changes so each build (where there are changes) will at least get a different .deb file. So I would say the new functionality is better, but still not ideal.
  18. I'm pretty sure this is a bug and I have logged it as such: https://github.com/armbian/build/issues/4905
  19. @tuanna You didn't buy a 4/32 box. That CPU doesn't support that amount of memory. It is common that sellers lie about the specs of boxes they sell, to the point of faking specs reported in their android firmwares and even changing the markings on chips. According to your pictures, if you research the memory chips (D9PSC) they are 2Gb each x 4 = 8Gb = 1 GB Researching the Toshiba emmc chip, while I can't figure out exactly its size, that part ranges from 2GB - 16BGB, so not 32GB. My take is you have a 1/8 box, just as linux is reporting.
  20. @bacco70 Please provide some basic information about your setup. What box do you have? What build do you have installed (file name and where downloaded from)? This would indicate that you are trying to install on to a none clean emmc. The script assumes you are installing on top of the native android firmware. This message indicates you have other stuff previously installed. Please explain what you have done before this attempt.
  21. @belegdol To use the old code you want to checkout the 'master' branch of the build repository: git clone --depth=1 --branch=master https://github.com/armbian/build Note that that branch is no longer maintained, but you can use it to test the differences between old and new build functionality.
  22. The purpose of Community builds is to provide the "community" an opportunity to step up and care for these boards. If no one is interested, eventually they will stop working and be dropped. Armbian is first and foremost the build environment for building SBC firmwares. Second, some Armbian developers also maintain boards they personally care about. But there are far more boards than core developers can support. But the infrastructure is there for others to step in and support boards they care about. But in the end if no one cares enough to maintain a board, it will drop from community support to end of support eventually.
  23. First off, I'm trying to understand what happened. What do you mean by this statement? Nothing in the instructions you linked to mentions using this command.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines