• Before reporting problems with your board running Armbian, check the following:

    • 1. Check power supply, check SD card and check other people experiences   06/23/17

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information   06/24/17

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

armbian-config
5 5

81 posts in this topic

Recommended Posts

On 4. 4. 2017 at 10:28 PM, zador.blood.stained said:

(i.e. with mainline u-boot environment can be edited from the OS using fw_setenv)


I am puzzled with calculating offset. I found some parameters, which looks properly calculated, but it looks like it doesn't write to the right place, since u-boot stuck at prompt.


/etc/fw_env.config

# Device to access      offset          env size
/dev/mmcblk0            0x88000         0x20000


This is a bit old but numbers looks alright ? https://blog.night-shade.org.uk/2014/01/fw_printenv-config-for-allwinner-devices/

http://linux-sunxi.org/Bootable_SD_card#SD_Card_Layout 

Share this post


Link to post
Share on other sites

Offset is correct. There is a bug in recent U-boot when saving environment files. Will try to catch the bastard ...

Share this post


Link to post
Share on other sites
        ls /tmp/armbianmonitor_checks_* >/dev/null 2>&1 || return
        for file in /tmp/armbianmonitor_checks_* ; do
                echo -e "\n### \c"
                ls "${file}" | cut -f1 -d.
                echo
                cat "${file}"
        done

Just a thought. At the end of CollectSupportInfo function in armbianmonitor there is the code above (no idea why it's there, I hate this interactive forum crap more and more). So maybe throwing debug info of the various armbian-config modules in append mode there so users can be asked to submit output from 'armbianmonitor -u' in case things don't work as expected (eg. me trying out AP mode with RTL8812 but failing)?

Share this post


Link to post
Share on other sites

I didn't went further with diagnostic part, since the core of this tool, basics what I wanted to achieve, is getting ready and now I am running it over and over again to find troubles. The main problem regarding enabling AP is that hostapd at regular repository is missing config file, while this is fixed in beta. That means if you don't switch to beta, this detection is broken for all standard wireless chips. Next it would be good to print out some debug info when detection fails in both cases ... but on the other hand if hostapd with most primitive settings doesn't work, than there is nothing we can do. If wireless is not detected, you should not get here anyway. 

 

37 minutes ago, tkaiser said:

I hate this interactive forum


I am on IRC always, when I am in the office :)

Share this post


Link to post
Share on other sites
13 minutes ago, Igor said:

I am on IRC always, when I am in the office

 

I know but was referring to formatting issues when writing here. Eg. try to post somthing with code inside spoiler tags. Since the forum upgrade the 'code tag' and linefeeds get ignored and I always end up re-editing my posts due to this 'improvement' (you're not responsible for -- i know. But the forum upgrade made it harder to share stuff here)

Share this post


Link to post
Share on other sites
21 minutes ago, tkaiser said:

try to post somthing with code inside spoiler tags


If I do that to clean post, eg. SPOILER -> INSERT code, than it works. If there is anything else, than I can't add code. Well, I'll check their forums or file an support ticket.

Share this post


Link to post
Share on other sites
On 6. 5. 2017 at 2:20 PM, zador.blood.stained said:

It would be good to add 2 new features in the future:

  • enable or disable MOTD scripts (individually)
  • freeze or unfreeze kernel and board support packages (`apt-mark hold`)


This is also done. I think we have enough features for upcoming update. I did few tests - works fine, while time will tell if there are still bugs. I'll try to do some code cleanup & optimisations ...

Share this post


Link to post
Share on other sites

Did anyone try overlayfs feature recently?

 

In the latest nightlies, when I enable overlayfs on my Orange Pi Zero it works as expected, when I try to disable overlayfs again, the Zero does not boot up anymore.

 

Share this post


Link to post
Share on other sites
7 hours ago, d1dd1 said:

 

Did anyone try overlayfs feature recently?

 

In the latest nightlies, when I enable overlayfs on my Orange Pi Zero it works as expected, when I try to disable overlayfs again, the Zero does not boot up anymore.

 


It used to work, so this looks like a bug and need to be inspected.

Share this post


Link to post
Share on other sites

I thought armbian-config was going to be useable with the last update that went out?
I'm running Ubuntu 16.04.2 kernel but is not available after installation. Do I still need to manually install using above git commands?
Any idea when this will be included in the mainline?

I'm running off NanoPiNeoAir, btw.

Share this post


Link to post
Share on other sites
12 hours ago, StuxNet said:

 

I thought armbian-config was going to be useable with the last update that went out?

 

 

Update hasn't been pushed out yet - too much problems and too little time. 

Share this post


Link to post
Share on other sites
On 5/27/2017 at 3:48 AM, Igor said:

 

Update hasn't been pushed out yet - too much problems and too little time. 

How I know that feeling. Totally understand, my bad. Keep up the good work man.

pfeerick likes this

Share this post


Link to post
Share on other sites

I see that the armbian-config update rolled out. Awesome work. Thanks.

I immediately tested the hotspot feature on an NanoPi NeoAir and it half way works. The 'Armbian' SSID is visible however I tried connecting with half a dozen devices using the default password and nothing ever connects. 
This is actually a mild relief since after hours of trying to get it to work manually using modprobe dhd and the like (before the armbian-config update) I experienced the same exact issue. Perhaps a DHCP leasing thing?

Anyways, not looking for a fix, I appreciate a CLI GUI at all. Just thought yall might like to know I couldn't get it to work. One more insiginificant thing you can put on the gigantic TODO list. ;)

Share this post


Link to post
Share on other sites

I fixed many troubles in the meantime (ofc not all), but what started to bother me is UX. The menu is getting larger and we will for sure find new things worth adding. I seek ideas how to create a future proof menu structure now. If you are not running latest beta, check this short video: https://www.youtube.com/watch?v=9zw9KlB56tA

 

Ideas, how to organise items/functions the most meaningful way, are welcome!

 

Share this post


Link to post
Share on other sites

First things that come to mind:

- "networking" submenu with options like WiFI, Hotspot, NetworkManager (just to call nmtui), etc.

- "software" submenu for Softy, USB redirector, installing a desktop environment, installing headers, etc.

- "tweaks" submenu for things like editing armbianEnv.txt, changing timezone, changing locale, etc. Alternatively 2 submenus instead - "system settings" for locale, timezone and other generic Debian/Ubuntu stuff and "tweaks" for Armbian-specific stuff (overlays, MOTD, loglevel)

 

Also current "debian-config" is 70 lines short from being a 1000 lines long. At this point it could use a refactoring, at least splitting stuff into functions and splitting functions into different files.

 

Share this post


Link to post
Share on other sites

Also a feature request, IMO it is worth adding a feature to tweak the "AllowRootLogin" option in /etc/ssh/sshd_config with 3 possible options - Allow password and public key, allow public key only and disallow everything. This may need release-specific logic, sshd_config man page has to be checked on each release.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

5 5

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.