Jump to content

Werner

Administrators
  • Posts

    5784
  • Joined

  • Last visited

Everything posted by Werner

  1. The interface name is code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } end0 code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } Use udev rules to rename to eth0 if you want.
  2. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  3. Armbian does not provide images for this board nor does it support it (yet). The OS you are using comes from a 3rd party. So I suggest to ask for support where you got the image from.
  4. You must be either poor or selfish (or both) to abuse open source projects that are living from donations themselves to beg for money. I have never seen such a behaviour before...
  5. Because they aren't. Only way to get hw acceleration at this time is using an Ubuntu Jammy based image and install 3rd party ppa + packages like stated on the download page.
  6. Flagship I'd say anything that is based on RK3588(S). However mainline support is still in development, legacy got most of the stuff working. If you want something older that is well matured and should handle 4k with ease I'd say something with RK3399. For latter LibreELEC provides images for various boards. It sounds like you are mostly interested in streaming so go for LibreELEC. If you want generic Linux desktop with Debian/Ubuntu userspace functionality go for Armbian. As a generic hint I recommend avoiding so called "TV Boxes" altogether. These devices are like cancer on the market. Undocumented, no source codes, no BSP, removed/inaccessible debug console, mutating uncontrolled (vendors tend to change hw components without notice and simply keeping the product name while breaking software support). Better get a proper board. Here is some inspiration:https://www.armbian.com/download/
  7. Try importing updated keys from Debian, similar to this: https://talk.plesk.com/threads/no_pubkey-bd11a6aa914bdf7e.368962/post-924677
  8. I don't know what you were booting but certainly not Armbian...
  9. There are no pre-made Armbian images yet. However you can make your own using the build framework: https://github.com/armbian/build
  10. Mainline support for RK3588(S) is in early stage so issues are kind of expected. Did you try legacy (5.10.y) in comparison?
  11. Fairly new users to the forums are only allowed to edit their posts for a short period of time. With time and created postings this time span will increase. Until then it is perfectly fine to create a fresh posting for adding information.
  12. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  13. If I click and then click on archive I get all images. Like here: https://mirror-eu-de1.armbian.airframes.io/dl/rockpi-4a/archive/
  14. Check kernel config in /boot if the mentioned module is marked as M there. From my guts feel I'd say I hasn't even compiled in.
  15. I think halfway proper hw acceleration is only possible with Jammy gnome legacy and the ppa's mentioned at the download page installed. The reason is the gnome version comes with wayland which the additional drivers work with.
  16. Hm I always knew the open parameter code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } luksOpen instead of code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } open
  17. https://askubuntu.com/questions/601/the-following-packages-have-been-kept-back-why-and-how-do-i-solve-it
  18. Necessary files for building have been merged. If it will be supported however depends on if a person steps up as maintainer. https://github.com/armbian/build/pull/5680 https://github.com/armbian/build/pull/5671
  19. https://fi.mirror.armbian.de/.meeting/devmeeting_2023-09-06T17_46_27.885Z-subbed.mp4
  20. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  21. There are and they are stored here unless it is forgotten to record: https://fi.mirror.armbian.de/.meeting Once you RSVP the link will direct to the meeting. No further instructions needed.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines