Jump to content

Igor

Administrators
 View Profile  See their activity

  • Posts

    14388

  • Joined

  • Last visited

 Content Type 

Everything posted by Igor

  1. Igor
    Probably someone knows but: - doesn't have time to answer, research and answer, do everything you are asking and provide you a simple plug and play solution, - didn't notice this at this very short period of time. Complexity in this world is extreme and not everyone knows everything. Basically you are seeking someone that will spent hours or days to study instead of you and make something you will deploy and use? That is extreme optimism, but its possible. Getting that kind of question answered just in a matter of days adds to more to this extreme. This does not work this way. And you are new to this community. What is here not supported is laziness. RK3399 boards share this functionality, so I would say there must be something on this topic already on this forum. Its a goldmine but also a black hole at the same time so sometimes is hard to find things. And when you contribute, chances that someone you are looking for will help you. I am sorry, I don't know what you are asking without spending hours. Which is something I can't afford. Remember to not bump topic if you don't add value. Welcome to Armbian community.
  2. Igor
    Worth trying switching to < 6.0 kernel in armbian-config, alternative kernel. I am running Odroid HC4 in production, which is pretty much the same device without any issues with kernel 6.0.12 ___ _ _ _ _ _ ____ _ _ / _ \ __| |_ __ ___ (_) __| | | | | |/ ___| || | | | | |/ _` | '__/ _ \| |/ _` | | |_| | | | || |_ | |_| | (_| | | | (_) | | (_| | | _ | |___|__ _| \___/ \__,_|_| \___/|_|\__,_| |_| |_|\____| |_| Welcome to Armbian 22.11.1 Jammy with Linux 6.0.12-meson64 System load: 2% Up time: 149 days 5:15 That is very different. Its kernel from chip vendor which we have dropped some time ago. It has other problems. First we need to reproduce and then understands why it happens. You can try to set fixed cpu frequency or governor in armbian-config -> CPU to rule out this possible source of issues.
  3. Igor
    https://docs.armbian.com/User-Guide_FAQ/ Automated test builds straight from development lab are designed for developers. They won't generate expenses by (repeatedly) asking questions but fix the problem if they could. Development builds are full of bugs and unfinished sections so it is extremely expensive to deal with this. tl;dr; Those builds might work or not. Use Armbian with the one and only stable kernel and wait 6-12 months that modern kernel is in good enough shape that won't randomly break. You are welcome to test new kernel it the mean time and use if it works good enough, but bug reports won't be taken by anyone (as we don't have people to waste time for such a nonsense) until support is stabilised and you or vendor will be interested enough to support us to support you.
  4. Igor
    Well, this should be determined by someone that is closer to OMV. More looks like a bug in their modules as they should cover such case / circumstances.
  5. Igor
    Purely blind speculation. The problem could be as we are providing Wireguard module and tools by default, while OMV could be trying to install dkms package which re-compiles it on demand ...
  6. Igor
    Yes, its a known (non-critical) issue - some SHA files are missing but since this happened, everything in this regard changed & updating mechanism was temporally teared apart we should do this manually or by making yet another temporally script. SHA files will be O.K. within upcoming major update due by the end of the month.
  7. Igor
    Did you check with OMV people to understand what this plugin does? Or perhaps try to see if there is something in the system or omv logs when you do that. That might help us to understand what is going on.
  8. Igor
    This was fixed https://github.com/armbian/build/pull/5088 built jammy image with patched 6.1.125 kernel verified /dev/snd/ nodes returned Sent patched image to the user who had the audio HAT for the RockPi-S He verified that audio (output at least) now works. Build from sources, try automated community builds or wait few weeks for release,
  9. Igor
    Video Summary: Just overview on the status of CI and discussion on known problems regarding upcoming release. We are pretty confident new build framework will be up to the job. On the board support level, still we need to do testing, try to bump boot loader on Allwinner devices, bump rockchip64 current to 6.1.y.
  10. Igor
    Yeah, true. Not worth the troubles. For build runners we don't need anything special. Just internet connection, not even any private networking. At least not until all other runners are just everywhere.
  11. Igor
    This week meeting topics: 1. Pre-release CI status check General goal of weekly meetings: To discuss the three (3) issues of the week Discussions will be documented to respective Jira tickets so they can be tracked Three (3) new issues will be selected from Jira for the next meeting The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. Since meetings are held in public, any registered community member can join and listen. If you want to suggest issues for the next week, you have to be recognized Armbian contributor. If you want to become one, resolve at least one intermediate level issue and tell us something about you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer
  12. Igor
    https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity I am sorry, but this "Armbian" have nothing to do with us. Contact people / vendor that made this assembly. Moving to unsupported.
  13. Igor
    This is worrying. Tried all possible methods with Khadas Rescue tools? https://www.khadas.com/post/krescue-take-control-of-your-vim https://hackmd.io/@Collega/HkKVfudc9
  14. Igor
    If you find a better working u-boot version, sent a PR with changes to this line and you will make all users of this hw happier: https://github.com/armbian/build/blob/main/config/boards/bananapim5.conf#L10
  15. Igor
    Video 1. Reviewing where we are with CI support 2. Challenges of upcoming release
  16. Igor
    This should fix it: https://github.com/armbian/build/pull/5132 Feel free to sent a PR in case you find something like that.
  17. Igor
    It looks like support is covered with this driver and there are not obvious reasons why it doesn't work. Try contacting people in the commit message. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/wireless/broadcom/brcm80211/brcmfmac?h=v6.3.1&id=0ec9eb90feec4933637fbde9d5bfbc3b62aea218 One is adding support and something else is keeping it in operational state once kernel changes. Sadly there is little we can assist here - wireless drivers are mess and we avoid them as one can eat us moths. And such luxury we don't have. P.S. Regarding your request. We have no idea why you don't have access to private forum - infrastructure bug Everything looks alright, but it doesn't work ... As we don't maintain this forum software on our own - its too complicated / not possible - we need to raise a ticket at 3rd party, which will take time and which is why I replied here.
  18. Igor
    You need to provide exact steps - what you did. Or better what you have ignored ... if you start with a destkop image, just follow 1st run wizzard and desktop will be loaded. If you skip one critical step (generating username) desktop won't run.
  19. Igor
    Possible quick fix is: sudo apt install armbian-firmware-full + reboot If that doesn't help, its more complicated.
  20. Igor
    This week meeting topics: 1. Upcoming release 2. Security in GitHub actions 3. CI support General goal of weekly meetings: To discuss the three (3) issues of the week Discussions will be documented to respective Jira tickets so they can be tracked Three (3) new issues will be selected from Jira for the next meeting The purpose of a weekly developers meeting is to coordinate development of the build engine, continuous integration, operating system features and low level support. Meetings are hosted located on Zoom (Video) and IRC and Discord (Text). While we would prefer you attend on Zoom when possibly, we will also monitor text chat during the call for those unable to join Zoom. Please RSVP either way. Do you want to participate or help in some way? Meetings are focused in developers top level topics and its expected that understand embedded software development, software testings or operating system management. In term of programming languages, knowledge of at least BASH & Python is expected. Since meetings are held in public, any registered community member can join and listen. If you want to suggest issues for the next week, you have to be recognized Armbian contributor. If you want to become one, resolve at least one intermediate level issue and tell us something about you. This is needed to efficiently communicate and to give you access to our organisation infrastructure Jira, Github, hardware lab and servers. @Contributor/Maintainer
  21. Igor
    If you will be digging in: - u-boot package contains information how to flash boot loader to eMMC/SD/SPI - this is install script that is called from armbian-config, also works as standalone armbian-install
  22. Igor
    https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one In some cases (Rock 5, Bananapi 5, ...) we are providing images with pretty well working but outdated kernel which is responsible for interacting with hardware. Difference between legacy and modern mainline is extreme. 1) devices that are plugged to the board were never officially supported. Porting drivers to the mainline for all Linux community (by a few people) is done in best effort manner. 2) it always works this way https://docs.armbian.com/User-Guide_Getting-Started/#how-to-install-to-emmc-nand-sata-nvme-usb unless it doesn't / its broken. If its broken it can be broken for all boards. SPI boot method is not always working / supported. My 2c
  23. Igor
    "Ubuntu" does not define interacting with the hardware, kernel does. As we don't use proprietary kernel from Hardkernel, this is done different, possibly its undeveloped feature. What you need to do is edit device tree and enable this UART (this is standard procedure on all boards). If overlays were made, then this is a lot easier: armbian-config -> hardware -> enable / disable, save, reboot.
  24. Igor
    Daily ATM and if it performs well, it stays that way.
  25. Igor
    It's know that is broken, it was fixed but since we are in the middle of big changes, we have deconstructed updating mechanism which is slowly going to be back in function. Try to use self build or daily auto build image and this problem is probably gone.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept