Jump to content

SteeMan

Moderators
  • Posts

    1365
  • Joined

  • Last visited

Everything posted by SteeMan

  1. The script that displays that info is: /etc/update-motd.d/10-armbian-header
  2. This is certainly possible. The level of difficulty depends on exactly what you mean by 'using a different kernel'. Start with https://docs.armbian.com/Developer-Guide_Welcome The basic Armbian kernel build process is to start with a kernel git tree, apply a bunch of patches that are missing from said tree (usually patches that haven't yet made it to mainline), combine with a kernel specific config file and build the resulting kernel. So depending on what the differences are between your 'different kernel' and what Armbian builds, you could insert your different kernel into any/all of those areas (i.e. you could add the missing patches that other kernel has, you could fix/change the kernel config to add/removed features, or you could use an entirely different git kernel source tree, or a combination of these three). The key would be to figure out what is different between the Armbian and other kernel that is relevant for your board. Ideally this could be done as a PR to Armbian to add better support for that board into Armbian.
  3. Moved post to unsupported/community maintained. This is not a supported board. My mistake, misread the post. This is pine64 not pinebook a64. That board should be supported but the forum structure isn't up to date. I have added the correct tag for the post, but left it in the original locatation.
  4. You can try them all. But it may be the case that none of them work. I just did a search of the forum archives, no one has ever reported getting armbian working on your box. You seemed to have some success with the ophub fork, so you could try using their dtb with armbian or just trying their builds.
  5. Shouldn't you be using the odroidhc4 images?
  6. No that is not normal at that point. Most likely the dtb you are trying isn't compatible with your hardware. I would suggest trying other dtbs
  7. If you click the button on that page labeled: Community Maintained Builds? (it is just above the selectors for all of the builds), then on the github page that link takes you to, click on Download Latest Image? Or to save you the work you could use the link at the top of the FAQ instructions. Or just go here: https://github.com/armbian/community/releases (latest build is 211, note they are listed in alpha order so the newest is not at the top)
  8. Use the u-boot-s905x3 found in the current rolling releases. Why are you trying to use an old archived release?
  9. https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus
  10. Ophub is a fork of Armbian. They use the Armbian name without permission. They do not contribute to Armbian development nor do they participate in these forums. You need to contact them for support of their software. We can't help you here.
  11. Try a different SD card. I've seen this happening more recently, especially with high capacity SD cards.
  12. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. This doesn't look like an Armbian kernel. What image are you using?
  13. I'd recommend submitting PRs for what you think is necessary. You will get better feedback there than here in the forum as more developers follow the GitHub activity than the forums.
  14. I'd recommend starting by submitting PRs for the board. Build up some knowledge and experience with Armbian development and processes. Then when you feel comfortable with the requirements expected of a maintainer, make that final commitment (https://docs.armbian.com/Board_Maintainers_Procedures_and_Guidelines/)
  15. I'm assuming the image is using an ext4 filesystem, and macos isn't able to read a Linux ext4 filesystem. I'f you were to use the SD card on any Linux box it should be readable. Or install ext4 support on your Mac.
  16. The quick fix is to use armbian-config to go back to the older working kernel, and then freeze kernel updates.
  17. @alidaf what build are you trying to image? Why do you expect a Linux image to be readable on macros? Does the SD card work on the target sbc?
  18. Buster was recently moved to end of support status in Armbian (Debian ends support in a couple of months too). Buster was released nearly five years ago. It is time to upgrade.
  19. I should also add: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
  20. I personally would say no. No one has submitted anything to Armbian related to these TV boxes. So none of the progress you see discussed in the forums is Armbian based. It is all done on forks of Armbian or other outside work. Until you start seeing someone step up and begin submitting PRs to Armbian for any of this work, I wouldn't say it has a future for you to consider it a replacement for anything. However if you only need to get something working once and don't care about receiving future kernel updates, then taking a build you see here would be fine.
  21. Please provide all the information I asked for. What build are you using? What steps have you taken? Please provide exact steps? Why are you using recovery mode? That isn't a step in the instructions.
  22. @thantien what box? what build? What steps have you taken?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines