Jump to content

Igor

Administrators
  • Posts

    14636
  • Joined

  • Last visited

Posts posted by Igor

  1. 31 minutes ago, blaster_56 said:

    I'm not the only one who face this kind of problem, i can garantee you that the Debian Jessie Image was not tested and Ethernet Driver is corrupted. (version 5.25 and 5.30)


    There are lots of problems with experimental kernel which is this topic about and which we don't support.

     

    If you have Opi PC+ and you want Debian Jessie: https://dl.armbian.com/orangepipcplus/Debian_jessie_default.7z (tested!)

  2. 4 hours ago, zador.blood.stained said:

    IMO every release. U-boot has ~2 months release cycle, kernel has ~2-2.5 months release cycle and current Armbian release cycle is much longer, so we may have to adjust it on the fly.


    OK, than next release should be planned for Sep 11, 2017, followed by Nov 13, 2017, ... the same dates as u-boot release date.
     

    26 minutes ago, zador.blood.stained said:

    Also should we hide "dev" kernel target in the build script unless EXPERT=yes is set and move all boards which only have a dev kernel target to WIP section?

     

    Yes, why not. 

  3. 8 minutes ago, debianxfce said:

    Armbian is based on Debian that has ARM support for many CPUs.


    Surely, aarch64 package base and our standard custom work on top of Debian is more or less o.k. / matured, but most problems on those boards are below userspace - on u-boot and kernel level. Standard arm64 Debian / Ubuntu kernel most likely won't even boot.

     

    Within Armbian we would also like to provide clean building process, starting with boot loader. Here some code cleaning / fixing is needed or workaround.

  4. 4 hours ago, Stanislav Sinyagin said:

    I'm fine with experimental status, but just wondering, how did 4.10.3-sun8i memorize the MAC address, and why 4.11.3-sun8i does not?


    Don't know. The main problem with development kernel(s) is that is difficult to stay on track to understand changes. Each question might lead into deep investigation which is not possible.

    I know one important detail - current network driver is deprecated / not good for mainline / half broken and somebody is working on a new one. Getting to know why the problem is present in current kernel is therefore pure waste of time. This issue is a school example, why support for WIP is pointless.

    You can try with workarounds to set MAC until things are solved.

     

    More or less updated status can be found here: http://linux-sunxi.org/Linux_mainlining_effort


    We have some general troubles and changes with nightly builds. Repository will be rebuilt daily, while images weekly.

     

    &Thanks!

  5. 3 hours ago, tkaiser said:

    But obviously I'm the only one and it seems a way better idea to roll out updates that can't be tested appropriately on every device so that at least there's some update drama involved all the time. By dropping support for Lamobo R1 everyone would be happy.

     

    I also support this idea with similar passion. The hardest part is done and we moved few boards to deprecated section and I also think its better to froze packages  (a new switch / feature has to be added to the build script that we don't need to use user patching method), rebuild, move working frozen kernel and bsp packages R1 images to deprecated and forget about this board. If you are bored, add switch to the build script and I'll do the rest when I got back to office.

  6. 2 hours ago, tkaiser said:

    Thank you for all the answers.

     

    Patience. My response time is currently close to one month and going faster, working more than possible, means risking burn out / mental breakdown, which leads to no response at all for longer period of time. This bug affect all humans and workarounds make things only worse.

  7. Conclusions:
     

    - nightly kernel and BSP building yes, nightly images once per week

    - focus more to provide simpler way for new developers to get in

    - nightly images should be carefully picked to provide best "price performance" ratio

     

    and another proposed actions:

     

    - moving another three boards (Lamobo R1 / Cubieboard 1 / Lime A10) into deprecated sessions. All those boards get one last update with last known working configuration and frozen kernel packages

     

    Quote

    - I still think Armbian needs a testing/beta branch so surprises like broken networking after just an usual 'apt upgrade' on a specific device

    - IMHO a release scheduled is always a good practice

    - Is there a(nother) private subforum where open issues and needed testing efforts were discussed before 'we' (or you?) decided to push the button and roll out just another update that bricked devices (servers without network connectivity any more can be considered bricked IMO)?

    - It should not happen but it can. I'm thinking of whenever a major update is planed an announcement thread should be pinned to each subforum that  testers are needed to check if everything works properly. 

     

    This a current project overview, which we try to follow. Is this time span perfectly o.k. ? Not sure. We will need to adjust it in the future, but it’s something to go with and stick to it, when and if we agree:

     

    UPCOMING MILESTONES

    Milestone               Responsible Person Due On
    Feature developement                   --- Due in 81 Days
    Feature freeze                         --- Due in 90 Days
    Beta testing and bug fixing            --- Due in 130 Days
    Writing release documentation          --- Due in 142 Days
    Launch                                 --- Due in 149 Days

    Withing project management we manage to establish fully operating testing system – a person get’s an email, when and what to test – his report is clicking few check boxes + adding a note when necessarily. Technology was tested twice and it works, methodology needs broad discussion. Project manager is the one, who has overview and drive (volunteer) developers to fix this and that. In reality this means I was driving myself and Michael was assisting in this and solving problems which are out of my league. Since we were also testers, most of bugs were saved already on the way ...
     

    Quote

    But I don't see us moving into this direction at all. Quite the opposite.

     

    Project management is yet another full time position, which waits to be filled developed and filled in. We deliberately use this hidden, because I was not sure if it’s the right way to go, because not everybody needs to  be involved in everything and because not finished products are better to hide. Check email.

     

    Until there is no somebody who will take a full lead on this, I am moving it forward with (my) highest possible speed. Well, in fact it's already we. Tido is helping in this beta trial process.

     

    Quote

    You may like to open ONLY COMMUNITY SUPPORT forums for not officially supported boards (old or new) and owners of these boards can help each other - instead of deleting, just move the topic there.

     

    We can add text to forum description, which board are officially supported – I know people will still fail to see.

     

    Quote

    IMHO. For me 3 boards are the minimum to be supported : desktop, NAS - LAMP and IoT server. 

     

    Yes. This is at least much simpler to support and is to consider.
     

    Quote

    But I saw a lot of projects failing cause of people loss the spirit spending their time to explain the same questions again and again and I don't want to see that armbian also fails. 


    Yeah. At least we are highly motivated to end / limit at best as possible.
     

    Quote

    Questions like: Why does "random function" does not work on my "random board" are annoying. Maybe some additional information to each board and some basic question rules can help to avoid this. 

     

    We would certainly need more moderators, which would take care of such questions appropriately. Technical knowledge about those boards is not a requirements. If @chwe wants to take care of general moderator duties, he is one click away :)
     

    Quote

    Having a wiki-page to each supported SBC that shows if the vendor claimed features are supported by armbian or not or if there is some known projects where someone works on this feature could help to avoid people from buying false boards. 


    This is fine, but very hard to maintain.

     

    The rest elsewhere. This one is already off topic.

  8. 10 minutes ago, Charizard said:

    4.11 kernel has a broken crypto functions. So we cannot use a lot of programs with this kernel like hostapd or openvpn. Can you move mainline kernel to experimental for the Banana pi, please ?

     

    Thank for notify - didn't know that. Is there a patch for this?

  9. 52 minutes ago, Stanislav Sinyagin said:

    Now 4.11 kernel update is missing for nanopineo2.

     

    This indicates that automated built process broke. Nothing unusual for development areas / work in progress ...

     

    15 minutes ago, Stanislav Sinyagin said:

    with 4.11, there's still an issue that an attached WiFi dongle is not visible after reboot

     

    Development process is based on volunteer contributions / time and it  takes months before issues gets fixed. 

  10. 1 hour ago, Aux said:

    Sorry guys but there is something completely wrong. Backup image recovered, update process from 5.25 to 5.30/31 started, reboot same errors.


    I just test the upgrade once again. Starting with this image: https://dl.armbian.com/bananapi/archive/Armbian_5.25_Bananapi_Debian_jessie_next_4.9.7.7z

     

    apt update

    apt upgrade

     

    Zero problems. 

    Spoiler
    
     ____                                  ____  _ 
    | __ )  __ _ _ __   __ _ _ __   __ _  |  _ \(_)
    |  _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | |
    | |_) | (_| | | | | (_| | | | | (_| | |  __/| |
    |____/ \__,_|_| |_|\__,_|_| |_|\__,_| |_|   |_|
                                                   
    
    Welcome to ARMBIAN 5.31 stable Debian GNU/Linux 8 (jessie) 4.11.5-sunxi   
    System load:   0.51 0.14 0.05   Up time:       0 min
    Memory usage:  5 % of 996MB     IP:            xxxxxxxx
    CPU temp:      41°C           
    Usage of /:    8% of 15G    
    
    [ General system configuration: armbian-config ]
    New to Armbian? Check the documentation first: https://docs.armbian.com

     

     

    Logs: http://sprunge.us/QjUT

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines