Jump to content

Werner

Administrators
  • Posts

    5518
  • Joined

  • Last visited

Everything posted by Werner

  1. Ah, I misunderstood. I thought does not appear at all anymore but the question was about manual call. Has been answered properly already.
  2. If there is no overlay available you may need to write one by yourself. I'd start by modifying the device tree itself and set the port in question to host and see if this actually works. I think armbian-config comes with a device tree editor. Make sure to make a backup beforehand.
  3. moved to off-topic we dont support 3rd party os.
  4. To 1.) it is only displayed if the first boot assistant is not cancelled before user creation. To 2.) You should find some clues here: https://github.com/armbian/build/tree/main/packages/bsp/common/etc/update-motd.d
  5. Cannot reproduce: root@pihole-v2:~# apt update Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://deb.debian.org/debian bookworm-backports InRelease Hit:5 https://github.armbian.com/configng stable InRelease Get:6 https://armbian.atomonetworks.com/apt bookworm InRelease [54.1 kB] Get:7 https://armbian.atomonetworks.com/apt bookworm/bookworm-utils all Packages [10.4 kB] Get:8 https://armbian.atomonetworks.com/apt bookworm/bookworm-utils arm64 Packages [205 kB] Get:9 https://armbian.atomonetworks.com/apt bookworm/bookworm-utils arm64 Contents (deb) [55.9 kB] Get:10 https://armbian.atomonetworks.com/apt bookworm/bookworm-utils all Contents (deb) [36.1 kB] Fetched 362 kB in 3s (143 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. root@pihole-v2:~# cat /etc/apt/sources.list.d/armbian.list deb [signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com bookworm main bookworm-utils bookworm-desktop
  6. Hi, there are some pending changes to uefi config, not sure if they would affect you: https://github.com/armbian/build/pull/8377
  7. I assume it is some debugging left-over. Dealing with sbc families and sunxi in particular it is a ongoing fight against regressions and having a debug kernel can help to identify such. It is not ideal having this on end-user sbcs enabled but to limit resources we cannot afford having two current branches with and without debugging. If this is an issue for you, you can always use the build framework to build your own kernel package with adjusted kernel config disabling traces.
  8. I don't think there are pre-built images with both ha and de by default. You can try to build your own by adding this extensions to your own userpatches and enable it: https://github.com/armbian/os/blob/main/userpatches/extensions/ha.sh
  9. Alright, was described a bit weird so I assumed you were talking about some 3rd party image. I cannot tell what's the difference or if they work better than ours since I don't use or deal with those. Best you just give all of them a try. Bullseye is Debian old-stable and will soon become old-old-stable. So if you don't want to deal with multiple major upgrades, if possible at all, I'd recommend to start with Bookworm or even Trixie (which I assume will not introduce major breakage until finally released in August since most packages are frozen already).
  10. I suggest - if you want to continue with this approach - to add this as an extensions since having the necessary patches built-in for a board that needs hw modifications makes no sense. Examples: https://github.com/armbian/build/tree/main/extensions
  11. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  12. Well other option is the upstream broke somehow. KDE neon is based on their testing branch so if there is a faulty package uploaded desktop breaks. Though we won't dive into this since KDE is no officially supported desktop environment by us. We mostly do GNOME and XFCE only. We don't have resources to deal with more while we wish we would/could.
  13. Well yes and no. This depends in board family and how well support is matured. In case of rk3588 support is very basic. This is also an LTS kernel which means no new features will be available and only security fixes will be applied. Enhanced hdmi support is available in edge kernel and also in rockchip bsp which we call vendor. If the system is accessible via terminal or ssh, use armbian-config to switch kernels. Otherwise - if available - download an image matching DE and kernel or use the build framework to build your own.
  14. moved to off-topic since not about Armbian but 3rd party img.
  15. expected. HDMI or hw support in general in 6.12.y is very basic and I am often impressed that hdmi actually works on some boards with this kernel. tl;dr: use vendor or edge kernels If need stuff running. current won't receive any further feature updates but security fixed only.
  16. Hi, I have a few sbcs live while most are laying on the shelf waiting for tests. I have a PiHole on an Orangepi One Plus. On a ROC RK3399 PC PLUS I have paperless-ngx running in Docker. On an OPi5 Plus I have Invidious, yourspotify and something else I frequently forget about. Most likely something from similar importance
  17. There is no need to install the "wireguard" package from upstream which, as you noticed, has a dependency to Debian kernel which obviously fails to boot. Since Wireguard is shipped by default with every Armbian image, all you need are the userspace tools which are in the "wireguard-tools" package which you can install with "--no-install-recommends" to avoid useless packages installed via soft dependency.
  18. Does regular image with same version/kernel work?
  19. you burned to microsd, then burned to microsd. What?
  20. How long did you wait for this? if you for example use a quite large microsd card that however has a slow pace this may take a few minutes.
  21. I would. Happened in the past but no clue which hw. Probably also something aw related.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines