Jump to content

Werner

Administrators
  • Posts

    5954
  • Joined

  • Last visited

Everything posted by Werner

  1. yet still giving enough to write a answer. flaming over LPEs (or any vulnerability) does not solve any issues. I suggest to read the license again to get a clue who's responsible about fixing things in general: https://github.com/armbian/build/blob/5e60c0183d035bfd5179373e1eac284790e08904/LICENSE#L265-L268 Both parties also shall read the terms of use again, the very first bullet point in particular. I will not give this hint a second time. fixes will land upstream, stable builds will adapt four times a year. For everyone wants things faster, options were provided.
  2. Try with this commit:https://github.com/armbian/build/commit/b880d98b07090b0b59bb3096c508e5123b224037 Seems like Micha had to cleanup my mess
  3. Quite a while ago I added GPIO names to the rock-3a. Perhaps you can get an idea how to do this. Source: https://docs.radxa.com/en/rock3/rock3a/hardware-design/hardware-interface#gpio-interface Implementation: https://github.com/armbian/build/pull/7403/changes
  4. perhaps the patch is no longer necessary once this lands upstream. We will see once we get there
  5. If you want to do the work you can open a pr including these changes into Armbian. However I believe all opi5* boards are in decent state I'd simply wait for upstream . the patchew link is dead btw.
  6. duplicate https://forum.armbian.com/topic/59601-sd-card-boot-cant-find-my-sda1hdd-after-warning-and-fsck/?do=findComment&comment=237240
  7. That's default Debian behavior. Ubuntu includes sbin in PATH afaik. In any case Armbian does not alter this.
  8. There is no such device. The only device with E and W suffix I know exist are the Radxa Zero 3W and 3E. Double-check what hardware you actually have.
  9. Werner

    Orange Pi RV2

    No, probably not. CI takes days to catch up. Best is to use the build framework to create an up-to-date image/kernel This happens automatically after a few days.
  10. It should be available on any armbian installation oob. You can also get it here: https://github.com/armbian/build/blob/main/packages/bsp/common/usr/sbin/armbian-add-overlay
  11. Werner

    Orange Pi RV2

    Support for 7.1 has been merged yesterday https://github.com/armbian/build/pull/9784
  12. I verified the overlay above working with diy kernel 7.1.0-rc1 and kernel 6.18.10 from apt repo.
  13. Hm does not contain 7.1.0 dmesg boot log
  14. Seems like the same "issue" like here. tl;dr: upstream uses "otg" to allow user to change the usb port behaviour as they like. https://forum.armbian.com/topic/59094-usb-2-port-not-available/#comment-237191
  15. The upstream default seems to be "otg" to allow users in userspace to change the usb port behavior. Try this and use armbian-add-overlay /dts-v1/; /plugin/; / { fragment@0 { target = <&usb_host0_xhci>; __overlay__ { dr_mode = "host"; }; }; };
  16. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  17. must be specific to this board. rock-3a which also uses RK3568 is not affected. btw. bleedingedge is intended to be used by developers only since breakage just like you noticed, is very much expected.
  18. For those who want to follow the linux-sunxi mailing list but not as plain emails but in patchwork format, feel free to use https://patchwork.armbian.eu/project/patchwork/list/
  19. Multiple options: - wait for upcoming 26.05 release which will most likely have an updated kernel package including a fix for this - as suggested use nightly - use the build framework to build an most up-to-date kernel package set by yourself (its very easy) which then can be installed via dpkg -i However since "dirty frag" just showed up, there is more to fix anyway... Edit: looks like fix for dirty frag hit upstream earlier today
  20. you chould check the device tree which mode is there by default. I assume it is not "host" but something else. I believe the device tree follows upstream and is not altered by Armbian. Not sure though, needs research
  21. You posted in the wrong sub-forum. Your topic is about the orangepizero2w which for once has nothing to do with orangepizero2 and for the other is unsupported by Armbian. Therefore the topic was moved (and the tag adjusted) to the unsupported/community supported section of the forums, also known as staging. Latter do not offer dedicated sub-forums for each individual board.
  22. I don't know the names either. I suggest to look at the original device tree by decompiling it: dtc -I dtb -O dts /boot/dtb/allwinner/whateverthenameofthezero3devicetreewas.dtb
  23. Check uboot logs if the overlay has been loaded correctly. You may need an usb uart adapter for this.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines