Jump to content

Igor

Administrators
  • Posts

    13589
  • Joined

  • Last visited

Everything posted by Igor

  1. @Gunjan Gupta is doing that and sadly its a lot of work: "here are 77 broken patches that need manual fixing" We are looking at weeks.
  2. You can try default Armbian way, but beware this case was not tested, so its recommended for making a full HA backup so you can restore in no time. Mine too: igorp@odroidn2:~$ df -h Dat. sist. Vel. Upor. Prost Upo% Priklop na udev 1,7G 0 1,7G 0% /dev tmpfs 372M 5,9M 366M 2% /run /dev/mmcblk0p1 29G 5,4G 24G 19% / tmpfs 1,9G 0 1,9G 0% /dev/shm tmpfs 5,0M 0 5,0M 0% /run/lock tmpfs 4,0M 0 4,0M 0% /sys/fs/cgroup tmpfs 1,9G 0 1,9G 0% /tmp /dev/zram1 47M 38M 5,7M 87% /var/log tmpfs 372M 0 372M 0% /run/user/1000 I see no reasons to upgrade anywhere. Especially not to buggy USB3 storage.
  3. Open a PR here https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip-6.1/overlay If he doesn't want to be contacted, there is nothing we can do. This is volunteering position at best effort principle. Some have time, interests and love, some don't. When we notice maintainer becomes unresponsive, board is (at release cycle) moved from "Standard" to "Community support" unless someone else take it over ... https://github.com/ich777/pikvm-rockpi-e This would be much better to be done as extension to the build framework. Examples: https://github.com/armbian/os/blob/main/userpatches/extensions/ha.sh https://github.com/armbian/os/blob/main/userpatches/extensions/openhab.sh Docs: https://docs.armbian.com/Developer-Guide_Extensions/ There is another person, that is around, doing similar https://github.com/srepac/kvmd-armbian perhaps teaming up and do it properly & maintainable? And with IMO less efforts.
  4. Try those things that didn't work for @pgd just to make sure ... Also welcome to make a PR https://github.com/armbian/os/blob/main/userpatches/targets-release-apps.template#L35-L57
  5. Yes. I have also updated instructions in the 1st post.
  6. 32bit, expect troubles ... make image and try? How-to is in the first post.
  7. Yes, its kernel / low level hardware issue with this particular device. We will look into this, but this won't happen "over the night". I tried with mainline based kernel on Odorid M1 and it works there. It also says warning about "docker and privileges" but reboot fixes that warning. Backup / restore works ...
  8. I managed to recreate this problem on VIM4 ... This HW has some old factory kernel, which could be the reason. Trying on some other device first.
  9. I am having one almost identical device (Khadas VIM1S, same kernel) for testing. Installed add-on: Logs https://pastebin.com/raw/JVpwyx1C shows no problems. Are you using our images with preinstalled HA supervisor? If you DIY-ed, you need to fix this problem on your own. Here are some clues. Also did you try to reboot at least once?
  10. IMO, probably just some simple on/off commanding from known (Python) environment is the key? "WiringPi" association / brand name / keyword just don't want to die off Yes, its on the level "OS is not working" without telling anything, not even where, what image, what hw. Additional details: "Logs? Why do you need that???" I could not agree more. IMO commercialization-consumerism of Linux, where RPi (and clones) played critical role, is the reason why we are seeing this. Often its discouraging when you help someone with a usable instructions or tip, but then you realize he is a decade away from understanding what you are telling him ...
  11. what is new? download (temporally) final versions https://www.armbian.com/khadas-edge-2/
  12. Probably this will work ? https://www.acmesystems.it/libgpiod Should we install this by default?
  13. Images for testing are coming up: https://k-space.ee.armbian.com/incoming/orangepi5/archive/ https://k-space.ee.armbian.com/incoming/orangepi5-plus/archive/ or https://fi.mirror.armbian.de/incoming/ or https://stpete-mirror.armbian.com/incoming/
  14. If you switch to automation (apt.armbian.com), then routing should be fine as we only keep a small selection of mirrors, that are verified, ATM. This is a workaround, that significantly affects performance - for some people/locations, updating is painfully slow. In a day, two, we will re-enable all mirrors.
  15. Can you provide what you get from: sudo apt update sudo apt upgrade Dot it 3x.
  16. We (I think) hopefully fixed the problem. Is this still happening?
  17. Such board does not exists. It exists with H2+. Which is H3 - 4k video. Which is anyway irrelevant for this use case. Armbian support it as any other Linux distribution. https://docs.armbian.com/User-Guide_Board-Support-Rules/ This means. We don't know if images https://www.armbian.com/orange-pi-r1/ works and if you will have problems, you are on your own to fix them. As this is old and simple board, it will probably just work.
  18. Yeah, mirrors syncing / checking which are in sync is not working perfectly well. Yet. In a day, those random errors should be gone.
  19. This is by design. Community maintained targets are hosted at one location only, GitHub. We can't host everything at our primary fast download network. And all torrents have HTTPS sources, this file just one (1). This file changes every week, so there are slim chances file will have more then one seeder (GitHub 1x). Torrents from standard supported hardware should maxed out your download line. I needed 2 minutes to download this file successfully.
  20. Keeping this in overlay is probably best way ...
  21. It is. Wait. We are working on it. https://github.com/armbian/mirror/issues/16
  22. until

    Recording: https://us06web.zoom.us/rec/share/L_0e84KNP6qITW11jFDUVuBIQs-YrdqE3Hw2cgJf5eOYmdHx_pFN42pcD-Adg4S4.gyLUuhvP58Ch2qUk
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines