Jump to content

Igor

Administrators
  • Posts

    14593
  • Joined

  • Last visited

Posts posted by Igor

  1. 59 minutes ago, zador.blood.stained said:

    Please try testing after recompiling the u-boot now.

     

    M1 and PRO are O.K., will check R1 and M1+ too

     

    4 minutes ago, Aux said:

    same issue with update from Armbian 5.25 to 5.30 bootloop on Banana Pi.


    Using u-boot from previous version is a way to go - you have to update it on another computer if you already issued an update.

     

    1 minute ago, Echo said:

    OrangePi PC update was successfully. A reboot succeeded. Thanks for the update!

     

    You are welcome.

  2. 19 minutes ago, tkaiser said:

    Can we agree on a process like https://forum.armbian.com/index.php?/topic/4451-example-support-proposal-for-rock64/ and if not what are your ideas?


    I support the idea of protocol - if this is meant that way - but honestly I haven't been able to catch up - only quick scan. 

     

    44 minutes ago, tkaiser said:

    and we always just talk and talk and talk but nothing happens.


    My impression is different. A lot has been done, but also a lot can be done. The question is, what do we want and can we afford? Some things were made wrong, but in general we don't waste that much time either (if we rule out supporting Orange Pi zero wireless, similar pointless cases and perhaps support in general). We are already at a limit of what we can do with resources we have and that is one of the primary reasons, why all things weren't done yet. Even we cut off half of the board support ...


    There is more than just clear comm and few rules to achieve greatness.

    20 tools, each covering one aspect of a community or group by Pieter Hintjens:

     

    Quote

    Strong mission -- the stated reason for the group's existence
    Free entry -- how easy it is for people to join the group
    Transparency -- how openly and publicly decisions are made
    Free contributors -- how far people are paid to contribute
    Full remixability -- how far contributors can remix each others' work
    Strong protocols -- how well the rules are written
    Fair authority -- how well the rules are enforced
    Non-tribalism -- how far the group claims to own its participants
    Self-organization -- how far individuals can assign their own tasks
    Tolerance -- how the group embraces conflicts
    Measurable success -- how well the group can measure its progress
    High scoring -- how the group rewards its participants
    Decentralization -- how widely the group is spread out
    Free workspaces -- how easy it is to create new projects
    Smooth learning -- how easy it is to get started and keep learning
    Regular structure -- how regular and predictable the overall structure is
    Positivity -- how far the group is driven by positive goals
    Sense of humor -- how seriously the group takes itself
    Minimalism -- how much excess work the group does
    Sane funding -- how the group survives economically


     

    21 minutes ago, tkaiser said:

    We support way too much boards to deal with, we scare away potential contributors

     

    It could have impact or not. Perhaps our way of doing is too good, strict or perfect? It depend from which perspective do we look. I know that current scenario of engagement is not ideal and needs change if we don't want to get crazy and to level things up. This takes time and energy and we are going from one large project to another without stop. I see that more problematic than we failed to implement some protocol or feature.

     

    Quote

    Using Armbian and having to fear an 'apt upgrade' really sucks. There was a lot of babbling about what has to happen prior to releasing major releases ('team testers' and stuff) but... today we're on 5.30 for whatever reasons (maybe I just missed discussion, call for testers and announcement?)


    Actually we did testings, but this kind of issue could be found only if all boards were tested. We are not on that level, even 5 people (we have 8 people in total for testing from last call, but theirs board diversity is another problem) responded to assigned tasks. Testing protocol was not fixed yet, since we need few real world experiences, before we know what is important and to wrote all this down.

     

    We need to divide stable and latest builds, freeze non critical stuff (u-boot), ... yes. 

    I'll fix recent upgrade problems, when I'll fully understand them, but first I would need to get some sleep and recharge. I removed failed u-boot from repo but images for bananas are failed too.

  3. 5 minutes ago, wsian said:

    Bananapi armbian 5.27 mainline upgrade to 5.30. Cannot log in remotely from putty.. When connect to hdmi monitor, it boot up normally and can log in. Everything seems ok but no response when attempt to og in remotely (putty). Very strange.


    Most likely u-boot configuration which initialised network is broken for Bananapi. Still checking if this is it. U-boot upgrade has been removed until this is not resolved.

  4. 3 minutes ago, tahaea1 said:

    I don't really remember the kernel version. Armbian version was 5.25 or 5.24. Clean image as in what? I was using 5.25 for about 2 months I think? was apt updating regularly and it updated to 5.30 today. 


    OK. I'll try to reproduce.

     

    In the mean time, you can try to flash (downgrade) u-boot from http://apt.armbian.com/pool/main/l/linux-u-boot-bananapi-default/linux-u-boot-bananapi_5.25_armhf.deb to see if that helps. Extract  u-boot-sunxi-with-spl.bin and write to SD card:

    dd if=u-boot-sunxi-with-spl.bin of=/dev/yoursdcard bs=1024 seek=8 status=noxfer

     

  5. 4 minutes ago, tahaea1 said:

    Banana Pi Jessie mainline

    upgraded with apt-get

    using usb hdd as root


    Which kernel version and from which Armbian version you made update? Did you start from clean image? You have to tell me everything! btw. Super Pi is not supported even I am almost sure it's exactly the same as Banana Pi ... I never saw one of those ... some minor changes can lead to improper Ethernet initialisation. I also need to wait for others to report - on supported boards.

  6. 49 minutes ago, nihilista said:

    Updated my bananapi pro to from 5.30 minutes ago...but now it doesnt boot ;-(

    Any possibility to get my system back without setting up completely new? Never had this with all update before.....


    Everything is solvable ... but we need more information to help. It might be a problem with u-boot. From where you did upgrade?

  7. 1 hour ago, mihai.aldea said:

    No updates yet? Does that means that we can't use the generic DVB-T tuners (eg. Astrometa ID 15f4:0131) with 3.4.113?


    Most of developers are dealing with mainline kernel, which is slowly emerging / getting ready on H3 devices too. There you have more chances for such hardware to work. I am using Nanopi neo for my tvheadend with 4.10.x - no problems:

    Spoiler
    
     _   _                   ____  _   _   _            
    | \ | | __ _ _ __   ___ |  _ \(_) | \ | | ___  ___  
    |  \| |/ _` | '_ \ / _ \| |_) | | |  \| |/ _ \/ _ \ 
    | |\  | (_| | | | | (_) |  __/| | | |\  |  __/ (_) |
    |_| \_|\__,_|_| |_|\___/|_|   |_| |_| \_|\___|\___/ 
                                                        
    
    Welcome to ARMBIAN 5.26 stable Debian GNU/Linux 8 (jessie) 4.10.0-sun8i   
    System load:   0.19             Up time:       34 days
    Memory usage:  28 % of 243Mb    IP:            xxxxxxxxxxxxxx
    CPU temp:      32°C           
    Usage of /:    19% of 7.2G   

     


    It's still in development, so you are on your own.

  8. Quote

    To conserve resources we could rebuild packages daily but rebuild nightly images only once a week, and we could significantly cut down the number of nightlies.


    OK, once per week and interessant only. I'll clear them out during this week. Will also push 5.30 updated images out.

     

    Quote

    We can leave this part as is - third parties are fully responsible for providing support to their users, but we can accept requests like adding options to kernel configuration since this will be beneficial to Armbian users too.

     

    Fine with me.

     

    Quote

    And creating separate lists for each group IMO is the best way to go, adding switches like "show WIP" and "show obsolete" and mixing stable boards with everything else will create unneeded confusion and complication.

     

    I made a third and I hope last adjustements. Now each one has it's own page, accessible from menu, below "Download". In /download, we only have stable, nothing else. I was only thinking to add links from there to WIP and deprecated section? Also some more explanation needs to be added to WIP and deprecated.

     

    Quote

    I am against adding any info for the hardware that we don't plan to support anytime soon. Who will maintain those lists and how?

     

    Specific is to big waste of time for us ... no, perhaps some general infomation that users will understand get some ideas / hints, why we don't support just every board on the market and that shitty boards exits and there is nothing much we can do about.

  9. 13 minutes ago, op1tjaap said:

    Would like to solve this because it would give me the freedom to compile a development kernel of my choise.


    If you are using our build scrpit - you already can do that - just use the packaging adjustements we made. And those you did, they look o.k. to me. Well, the kernel branch you are using, might not be bootable? Try first with some stable branch, "known to work kernel". 4.12 and sun8i doesn't look close to fully stable branch.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines