Igor

Administrators
  • Content Count

    6727
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Igor got a reaction from guidol in Monitoring your system health with HTOP (big.LITTLE)   
    ... and I have build it and pushed to Armbian stable repository (Stretch, Xenial and Bionic; armhf+arm64). First boot scripts also creates CPUfreq config based on CPU count. More can be added if there is an interest ... Package can be installed via apt update and upgrade while auto config feature will work only on self made images.
  2. Like
    Igor got a reaction from guidol in Monitoring your system health with HTOP (big.LITTLE)   
    ... and I have build it and pushed to Armbian stable repository (Stretch, Xenial and Bionic; armhf+arm64). First boot scripts also creates CPUfreq config based on CPU count. More can be added if there is an interest ... Package can be installed via apt update and upgrade while auto config feature will work only on self made images.
  3. Like
    Igor got a reaction from Marc in Orange pi plus 2 / kernel 4.9+ with sata port ?   
    It works but a chip quality and speed is bad. Put GL830 into a search box above. It is noted hardware (quality) issue which has nothing to do with out work. All images and kernels share this problem. Perhaps we would need to use different wording to make this more clear.
  4. Like
    Igor reacted to BananaGonzo in Can't remote access BananaPi with SSH   
    Thank you Igor - it seems that the service is not running on startup even there is an entry at /etc/init.d :-(
    I even tried to set up a cronjob (@reboot).
     
    Doesn't work :-(
     
    This is what its look like after reboot (connected via serial):
     
    root@bpii:~# /etc/init.d/ssh status
    ● ssh.service - OpenBSD Secure Shell server
       Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
       Active: inactive (dead)
    root@bpii:~# 
     
     
    Ok, seems that when I'm connected via serial it is in emergency mode - I have to shut it down completely (shutdown -h now) disconnect power and FTDI, and connect power again.
     
    Now it works...
  5. Like
    Igor got a reaction from lanefu in board support - general discussion / project aims   
    There was never a formal team. More like a strong common passion and interest to do something valuable, to push things forward, to help, to show how things should look like. IMO it worked very well until the level of self-fulfillment and happines was high enough and a mountain of problems low enough. People perception on this is very colorful and even among inner circle, we have different views. No matter how good and super the project might be. We have more and more users, while most of them waste our time and energy, contribute nothing and ask for more. This is not sustainable.
     
    Armbian might not need major build script or infrastructure development, but both need regular maintenance. We are short already for that. Not hardware, not software but responsibility.
     
    If board support is extending and developing, then this will bring solving harder problems which are not possible to be solved by a few people in their free time. This calls for 20-30x size of the budget size. Where from?

    On the other hand, people expect that "we will solve all the problems they find out". Reality is that our main workforce is basically offline due to overload, mounted problems, life, ... 
     
    We can talk about how to reshape the project, but first, you need someone that will execute what we brained out. 
     
    Personally, I need to look on a project from a distance and leave super (hardware) details behind. It might give me an opportunity to better see the problems we have. 
  6. Like
    Igor got a reaction from usuario74 in VPN Server Questions   
    Hello!
     
    Bigger boards = better heat dispersion and (better) voltage control = less (over)heating, better (non microUSB) powering = better stability. H5 is noticable faster than H3 and has better software support than A64 => IMO Opi PC2 should fit your needs.
  7. Like
    Igor got a reaction from chwe in Access Point Ralink MT7601U (148f:7601) Wi-Fi on Ubuntu Bionic   
    https://github.com/armbian/documentation/commit/c6cfb75f75fa4f096eab5282dee06ad8ad518412
    apt update and upgrade and its done.
  8. Like
    Igor got a reaction from esbeeb in when linux 4.19 is released LTS, which ARM-related features are you most excited about?   
    Armbian is mostly ahead of the upstream kernel releases in board specific functions. Up to about one year. Regarding the biggest group (Allwinner), the only change will be that we will remove a few patches  and when 4.19.y is sorted out it will become our NEXT for A10/A20/H3/H5/H6/A64 and Armada 3700, Rockchip, Meson, ... almost all supported board as a first or second kernel.
     
  9. Like
    Igor got a reaction from lanefu in board support - general discussion / project aims   
    There was never a formal team. More like a strong common passion and interest to do something valuable, to push things forward, to help, to show how things should look like. IMO it worked very well until the level of self-fulfillment and happines was high enough and a mountain of problems low enough. People perception on this is very colorful and even among inner circle, we have different views. No matter how good and super the project might be. We have more and more users, while most of them waste our time and energy, contribute nothing and ask for more. This is not sustainable.
     
    Armbian might not need major build script or infrastructure development, but both need regular maintenance. We are short already for that. Not hardware, not software but responsibility.
     
    If board support is extending and developing, then this will bring solving harder problems which are not possible to be solved by a few people in their free time. This calls for 20-30x size of the budget size. Where from?

    On the other hand, people expect that "we will solve all the problems they find out". Reality is that our main workforce is basically offline due to overload, mounted problems, life, ... 
     
    We can talk about how to reshape the project, but first, you need someone that will execute what we brained out. 
     
    Personally, I need to look on a project from a distance and leave super (hardware) details behind. It might give me an opportunity to better see the problems we have. 
  10. Like
    Igor got a reaction from lanefu in board support - general discussion / project aims   
    There was never a formal team. More like a strong common passion and interest to do something valuable, to push things forward, to help, to show how things should look like. IMO it worked very well until the level of self-fulfillment and happines was high enough and a mountain of problems low enough. People perception on this is very colorful and even among inner circle, we have different views. No matter how good and super the project might be. We have more and more users, while most of them waste our time and energy, contribute nothing and ask for more. This is not sustainable.
     
    Armbian might not need major build script or infrastructure development, but both need regular maintenance. We are short already for that. Not hardware, not software but responsibility.
     
    If board support is extending and developing, then this will bring solving harder problems which are not possible to be solved by a few people in their free time. This calls for 20-30x size of the budget size. Where from?

    On the other hand, people expect that "we will solve all the problems they find out". Reality is that our main workforce is basically offline due to overload, mounted problems, life, ... 
     
    We can talk about how to reshape the project, but first, you need someone that will execute what we brained out. 
     
    Personally, I need to look on a project from a distance and leave super (hardware) details behind. It might give me an opportunity to better see the problems we have. 
  11. Like
    Igor got a reaction from lanefu in board support - general discussion / project aims   
    That is already written and it is used ad hoc or if a person bumps into:
    https://docs.armbian.com/Process_Contribute/

    Instead of telling people what to do. Let's ask people if they want to take responsibility as such:
     
    - source code maintainer - adjust kernel configurations, patches, ... help on what we do,
    - project manager: development and testings overview, samples redistribution
    - code cleaner - sweeping our build script code round the clock
    - documentation editor - as a title implies
    - marketing manager - to help communicate project specific services, new features, changes, ...
  12. Like
    Igor got a reaction from sfx2000 in zram vs swap   
    It was not properly fixed. Now is.
  13. Like
    Igor reacted to data in Orange Pi Lite2 wireless support   
    Keep in mind that 3 means enabled, 2 is disabled. Use  "[connection]\nwifi.powersave = 2"
  14. Like
    Igor got a reaction from Fred St-Pierre in Asus Tinkerboard   
    You can try to track here: https://github.com/rockchip-linux/kernel/commits/release-4.4 + https://github.com/armbian/build/commits/master/patch/kernel/rockchip-default
     
    Not very human-friendly 
  15. Like
    Igor got a reaction from esbeeb in when linux 4.19 is released LTS, which ARM-related features are you most excited about?   
    Armbian is mostly ahead of the upstream kernel releases in board specific functions. Up to about one year. Regarding the biggest group (Allwinner), the only change will be that we will remove a few patches  and when 4.19.y is sorted out it will become our NEXT for A10/A20/H3/H5/H6/A64 and Armada 3700, Rockchip, Meson, ... almost all supported board as a first or second kernel.
     
  16. Like
    Igor got a reaction from lanefu in board support - general discussion / project aims   
    Yes. Now we have many patches that are either our origin or changed from the 3rd party. We ("only") need to define a protocol ... like we need a better/more polished protocol for testing.
     

    We have resources for something but not for all. We also need to create or find resources for the current state of the project. Without doing anything extra! I don't know what will be possible to do and when from a current perspective. Let's keep things on the list even we might not solve them. This is nothing new.
     
     
    At least this is not exactly urgent. A default branch can be 1st pushed under EXPERT/unsupported but not removed. Yet.
     
     
    Current update logic is as follows. When its time for the update, when nightly builds run fine ... we test images and push out a 1st stable images (we could call them RC). The update follows after a while (few weeks) when second test force - users installing a system from new images, which should at least boot up to 99% - report those few remaining issues. This was the core idea in a last major update and there was actually an extremely low reported failures. I am actually very happy, but the price was higher than I am willing to accept. If this is once per year, ok, but if we start pushing out updates more often, this is not sustainable.
     
     
     
    If just a few people are aware of problems while the rest have no idea how hard is to make things happen, they will continue to push on us with full force (until we break down). We need to communicate properly that support is as is and there is nobody here waiting for users complains. Sometimes we solve things promptly, sometimes we file them for the future, some are ignored. More later ... life is calling.
  17. Like
    Igor got a reaction from Werner in board support - general discussion / project aims   
    There are still (many)some (short and) long-term questions which are scattered on the forum and in our heads which we would need to discuss.
     
    - release naming, 2018.10 or 18.04 + some RFC as shown on the pic,
    - collecting wishes on a special web page or forum topic. When someone approaches with "I want to help" that it is appointed to 1. Check issues on GH, 2. Fixing sound ... 3. Creating this ...
    - improving testing protocols, automating what is possible. I'm low on ideas what more is possible to do.
    - what to add to »end of support«?
    - secure project longterm survival, leverage maintenance costs to users or drastically limit down free support,
    - enforce browser of choice for desktop images, Firefox and/or some lighter alternatives?
    - fix Bluetooth on all Broadcom AP62xx devices. Its the same on most boards, but we have it working only on a Cubietruck IIRC
    - sum most frequent problems under »The Ten Commandments« / FAQ and promote it as much as possible
     
    - does forum need structure update?
    - add/remove moderators? Disable rights if not moderating content in past 6months?
    - enforce forum rules? Some very simple ones.
    - users are still seeking for help without providing logs. What to do about?

    Download UX:
    - make a bigger diff between nightly and stable, desktop and CLI (Gorazd)
    - add a warning when nightly is downloaded, (Gorazd)
    - tested devices lead to their test page where exists instead of Amazon affiliate, (Gorazd)
    - tested hardware have information to which kernel is attached to but not displayed, (Gorazd)
    - check other download option still no visible enough, (Gorazd)
    - add a support box with 1. Check common issues 2. Search for solution 3. Ask (with a link to the correct forum) (Gorazd)
    - add a button »alternative builds« with a link to dl.armbian.com/DEVICE (Gorazd)
     
    To keep things in place, I would like to ask @Tido and @chwe  to help keep this 2do list up2date according to with our decisions.
  18. Like
    Igor got a reaction from Werner in board support - general discussion / project aims   
    There are still (many)some (short and) long-term questions which are scattered on the forum and in our heads which we would need to discuss.
     
    - release naming, 2018.10 or 18.04 + some RFC as shown on the pic,
    - collecting wishes on a special web page or forum topic. When someone approaches with "I want to help" that it is appointed to 1. Check issues on GH, 2. Fixing sound ... 3. Creating this ...
    - improving testing protocols, automating what is possible. I'm low on ideas what more is possible to do.
    - what to add to »end of support«?
    - secure project longterm survival, leverage maintenance costs to users or drastically limit down free support,
    - enforce browser of choice for desktop images, Firefox and/or some lighter alternatives?
    - fix Bluetooth on all Broadcom AP62xx devices. Its the same on most boards, but we have it working only on a Cubietruck IIRC
    - sum most frequent problems under »The Ten Commandments« / FAQ and promote it as much as possible
     
    - does forum need structure update?
    - add/remove moderators? Disable rights if not moderating content in past 6months?
    - enforce forum rules? Some very simple ones.
    - users are still seeking for help without providing logs. What to do about?

    Download UX:
    - make a bigger diff between nightly and stable, desktop and CLI (Gorazd)
    - add a warning when nightly is downloaded, (Gorazd)
    - tested devices lead to their test page where exists instead of Amazon affiliate, (Gorazd)
    - tested hardware have information to which kernel is attached to but not displayed, (Gorazd)
    - check other download option still no visible enough, (Gorazd)
    - add a support box with 1. Check common issues 2. Search for solution 3. Ask (with a link to the correct forum) (Gorazd)
    - add a button »alternative builds« with a link to dl.armbian.com/DEVICE (Gorazd)
     
    To keep things in place, I would like to ask @Tido and @chwe  to help keep this 2do list up2date according to with our decisions.
  19. Like
    Igor reacted to itsy in Install / compile TVHeadend   
    Thanks a lot for this great service!
    I used the new image, added the ppa and now tvheadend runs :-)
     
    Have a nice sunday
    Thorsten
  20. Like
    Igor got a reaction from matrasa in Orange Pi PC old OS image   
    Now serial console logs on the problematic one. Alternative way: https://forum.armbian.com/topic/8293-apt-upgrade-bricked-tinkers-today/?do=findComment&comment=62642
     
  21. Like
    Igor got a reaction from matrasa in Orange Pi PC old OS image   
    Armbian with kernel 3.4.y and 4.14.y is identical. The only difference is kernel and below.
     

    Why didn't you tell this before? If you don't follow our recommendation you are only wasting (my) time.

    Here you need to start:
    https://docs.armbian.com/User-Guide_Getting-Started/#prerequisites-for-new-users
  22. Like
    Igor got a reaction from matrasa in Orange Pi PC old OS image   
    If an upgrade fails you need to provide us serial console logs that we understand what is going on, where booting stops. This will help you and others.
     
     
    You should scroll down to the bottom, where you can find the one and only image with an old kernel. 
     
    https://dl.armbian.com/orangepipc/Ubuntu_xenial_default_desktop.7z
     
    It's an image with a desktop (which you can disable in armbian-config). Older than this, we don't support anymore.

    We used to ship some external wireless drivers in the past, but since it was complicated to support, we don't do that anymore. You can try to compile them this way: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-build-a-wireless-driver
  23. Like
    Igor got a reaction from Werner in board support - general discussion / project aims   
    Yes, that is planned, but we still have weeks - we also don't need to jump on v4.19.0 ... It's DEV kernel and the idea is that DEV becomes NEXT when the time is right. Which is even more distant. Since 4.19.y is the next LTS it will be worth to prepare it and port support from more recent versions. 4.19.y is for 2019
  24. Like
    Igor reacted to martinayotte in Orange Pi Lite2 wireless support   
    Build started ... I will test it in the following hour ...
     
  25. Like
    Igor got a reaction from Werner in Orange Pi Lite2 wireless support   
    Because that branch is temporarily development branch with a purpose to develop a few things. We only have two choices here - switch to current 4.18.y, say goodbye to HDMI for a while and fix other things, wifi perhaps ... or wait until HDMI is not mainlined. Other options are too expensive.

    I have to remind you that this board is under development and regressions are possible. Some are intended, some not.