Jump to content

Igor

Administrators
  • Posts

    13936
  • Joined

  • Last visited

Everything posted by Igor

  1. You don't need to install anything. This is a script I use on a very similar device: #!/bin/bash task(){ gp=$1 [[ ! -d /sys/class/gpio/gpio${gp} ]] && echo ${gp} > /sys/class/gpio/export echo "out" > /sys/class/gpio/gpio${gp}/direction echo "0" > /sys/class/gpio/gpio${gp}/value sleep 10 echo "1" > /sys/class/gpio/gpio${gp}/value } task "$1" doing this. More info: https://www.google.com/search?q=sunxi+gpio
  2. @going Is there a simple way to package all those tools within a kernel compilation: https://armbian.atlassian.net/browse/AR-1283
  3. Since you are new around, perhaps tell us who you are and what you do https://forum.armbian.com/forum/10-off-topic/ Welcome! Also make sure you read documentation: https://docs.armbian.com/User-Guide_FAQ/ Bug reporting requirements: https://www.armbian.com/bugs/ Workaround for this problem cost me around 2h https://armbian.atlassian.net/browse/AR-1282 Each commit has to be reviewed. Please spent some time to figure out how to do that: https://docs.armbian.com/Development-Code_Review_Procedures_and_Guidelines/ as this is a very first step from here. Then things has to be compiled and once released, then you will be able to update and have this fixed on your device. You can ofc skip all this and do it on your own https://docs.armbian.com/Developer-Guide_Build-Preparation/ Proper fixing of code that is not maintained by Armbian https://github.com/aircrack-ng/rtl8812au/issues/987 would cost us week, perhaps more. Which we don't have so this "quick" solution should do. Welcome to Armbian 22.05.3 Jammy with Linux 5.19.0-odroidxu4 System load: 1% Up time: 6 min Memory usage: 5% of 1.95G IP: XXXXXX CPU temp: 47°C Usage of /: 5% of 29G [ 13 security updates available, 29 updates total: apt upgrade ] Last check: 2022-08-13 13:52 Last login: Sat Aug 13 13:49:49 CEST 2022 on ttySAC2 odroidxu4:~:# iwconfig lo no wireless extensions. wlx40a5eff39254 IEEE 802.11bgn ESSID:"XXXXXX" Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency:2.437 GHz Access Point: XXXXXX Bit Rate:150 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:****-****-****-****-****-****-****-**** Security mode:open Power Management:off Link Quality=61/100 Signal level=40/100 Noise level=0/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
  4. I am sorry, but this is something that has to be consulted with an legal expert. We never had such case. We have no option but to wait for a legal adviser with a appropriate licence / background that will donate their time and research the case. Anyway nobody, except administrators, have access to sensitive data. Answering random topic in community forums is probably not following instructions -> "contacting administrator"? What about: https://forum.armbian.com/contact/ (for next time and others that might hit into this topic) Software breaks all the time. I don't see a reason why you should be deleting "technical support" account as you will probably soon need to ask another question. People that fooled you they support a board don't have a clue about real problems and we don't provide support for their clients. This is the truth and they are aware of it, just don't care or respect open source software agreements. The conflict originates from that. Initially theirs. They should not drag you into this in first place ... Switching to Armbian is a 1st step of showing minimum respect, second one is to become a community member and 3rd to understand what we do, what are our limits, what is our price to we are paying so you don't need to. Who you are, what you do, do you like our work? Do you drink beer with strangers? I don't.
  5. Because software support is difficult, complex and expensive I am glad you noticed the critical difference and get it sorted out. What if what we as users of free software got is already beyond reasonable? https://docs.armbian.com/User-Guide_FAQ/#why-is-armbian-constantly-asking-for-money-free-software-should-be-free
  6. Researching background? If you want to run closed source proprietary Linux, use Xunlong / vendor stuff. If you want to use quality and open source, well, there is a looooong way. https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one but can't do many other things. Its always a trade. Providing "Armbian wallpaper" on top of Xunlong proprietary software would be dirt cheap. This particular feature is not supported yet for many reasons. You can read articles on the topic https://linux-sunxi.org/AR100 and there are many forum topics on this https://forum.armbian.com/search/?q=AR100&quick=1 Working features have nothing to do with a support status. https://docs.armbian.com/#what-is-supported We annually invest thousands of hours just into stabilising release builds vs. nothing that rolling distros do (arch - manjaro). If you need that certain feature works, pay for development to anyone you prefer. Once done, send a patch to us, we will integrate it at our cost and will maintain it if not too expensive. But you can also send it directly to kernel.org.
  7. Upstream Linux release document is just a formality. All features are already present. Non RC builds will be out when people return from well deserved holidays.
  8. Great! A few 1000 x more and R&D investment is covered
  9. Armbian developers are more or less the only one that are progressing somewhere and this https://github.com/armbian/build/pull/3984 is the result of that work + information you can find at http://discord.armbian.com/. They are hardware vendor and they still have enough work to come out with good hardware. Certain problems on hw level has been identified and support is not near complete, modern kernel ... nothing ATM. You can use this form: https://forum.armbian.com/clients/donations/
  10. Igor

    Video Playback

    If this would be just a matter of installing something, we would pre-install it. We might get some luck in kernel 5.19.y -> https://forum.armbian.com/search/?q=hantro&quick=1
  11. For Odroid N2+ this works exactly the same, but you need to use EDGE kernel. https://www.armbian.com/odroid-n2/ ... as the bug is elsewhere.
  12. Good catch. I had in my mind we fixed this lds related bug ... well, 5.10.y is going out soon, so this is not getting fixes unless someone has a desire to do that. This is needed as it is very difficult to secure good stability and functionality across all hardware by using one kernel. If we would go simple way, it would be a lot worse. So we kept meson64 on 5.10.y and bump others to next LTS. ATM not sure what will happen with current branch but EDGE is being prepared for 5.19.y. If things will work well, its possible to bump current directly to 5.19.y
  13. Yes it is - use Jammy user land. It works there perfectly. Debian user land usually needs more debugging and fixing. If you insist going Debian route - when you find where the problem is https://docs.armbian.com/Process_Contribute/
  14. Pick something you understand well enough or start learning by reading this forum, documentation, ... https://forum.armbian.com/staffapplications/
  15. Topics were moved there just temporally as we decide to tag them and mass move to respective forums. It took several weeks and we had to hire people to help us doing that, otherwise that job would take months to complete. This should help everyone to get some control over forums information complexity. It should make it easier and faster to find and group content. It helps you. It won't be recorded or treated as we are already way over the budget. Public don't support or invest into this project enough while our private financing for random R&D has limits. Public support we receive - users donations - is only good enough to cover petty expenses project has, while it can't even cover basic staff expenses, any even smallest R&D task, needed to maintain this project without providing any end user support. I am sure you understand that.
  16. Wrong place. That is a build system bug tracker. https://github.com/armbian/build/issues/new/choose
  17. It was only tested with Jammy: https://forum.armbian.com/ytopic/19336-armbian-ubuntu-2204-jammy-with-zfs-211-for-odroid-hc4/ Debian package base might need some additional fixing.
  18. AFAIK we don't have support for x86 inside default installer yet, but it should work if you DD fresh image directly to the device, whatever that device is. eMMC, NVME, SATA or USB.
  19. FYI. They don't do any development, bug fixing or supporting boards they suppose to "support". Their pages are full of BS, but nobody cares as "their" product is usually legitimately working at least as good as others - if they manage to copy Armbian / RaspberryPi OS well. Its easy and fully automatized. HW stability, which few Armbian people lost several thousands of hours for, can't be worse as they only add some bash script and change brand name. Code is binary the same, they even abuse Armbian repository infrastructure without a shame. This is nothing as they also try to abuse our human support infrastructure without a shame. "Armbian must ... support ... fix ... yesterday" is in their heads when problems starts. And this is the world where you never can close all bugs. Not even close and not with resources project have. Why this board doesn't work? Armbian does not support it officially as we are drowning in hardware - when you don't steal all critical value from others then this represent serious problem and expense. If you didn't know this, if they forget informing their users that everything that is important is not their job, but others ... then this really stinks. And makes many peoples work, those that invest their days into open source, worthless.
  20. Human resources primarily for project management, business development and similar non technical tasks which would improve conditions for development ... We have several hundred dedicated CPU cores and around 1 TB memory for CI. We also have several dedicated storage machines / mirrors. If if double all numbers, I could say we are good, otherwise its survivable not even critical. If we keep project support expansion under control, images count low. This is some general list of roles that are needed: https://forum.armbian.com/staffapplications/ I assume you are familiar with this FAQ? For expanding / changing TV boxes section we currently only have means / task for small forum rearrangements. Planning and leading changes is time consuming ... If you got an idea, join here https://docs.armbian.com/Community_IRC/
  21. Changed redirrect from https://www.armbian.com/rk322x-tv-box/ -> to this thread. what about? https://www.armbian.com/xt-q8l-v10/ Support for this hardware comes from Armbian so this Debian / Ubuntu analogy has little point here as in high level software packages LTS and relatinship aren't that important - if you can't boot the board or if its unstable, when some feature doesn't work - this is what we try to fix here. But I do agree there are reasons for both, Debian and Ubuntu package relations. This diff is important to some people, so Armbian tends to support them both since the day one. I would anyway enabled full package for all hw, but resources we have are already way to small to play this big.
  22. This looks like as ready to put it here https://github.com/armbian/build/pulls
  23. I have refunded your donation as I can't accept it as a payment for resolving a bug. You are only allowed to donate if you don't generate us any additional expenses. Outside that its not called a Donation anymore. When you open us a bug, you easily generate several thousands dollars of expenses directly to our private finances and in most cases bug has nothing to do with us. Users keep wasting our time in insane quantity ... Trading our scarce family budget and scarce time we need to run this project without even dealing with its users for a beer? And allowing project that steals from open source and from us telling us what is the value of our time?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines