• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      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

      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.

Le Potato general topics
2 2

23 posts in this topic

Recommended Posts

Topic covering feature updates/bugfixes.

 

Sep. 29 2017 - HDMI hotplug script/udev added for Mainline.  Switching monitors no longer results in a necessary reboot.

Nov. 22 2017 - Dev updated to 4.14 with Libretech patches

Nov. 23 2017 - Next updated to 4.14.y with Libretech patches  <- wait for nightly, not on download page Active download

Dec. 18 2017 - Patch uploaded to fix Ethernet instability: commit

 

[bug] Dec. 14 2017 - Testing to be certain I had stereo audio via HDMI, I noticed that the left and right audio channels are swapped.  I would like some feedback from others if possible. 

[bug] Dec. 14 2017 - Random MAC address  <- tested using internal efuse, from factory appears not to be burnt.  (hex dump of efuse device is giving me identical values on 2 devices)

[bug] Dec. 20 2017 - Init 0 results in reboot

[bug] Dec. 20 2017 - Ethernet LED's do not blink. (Thanks for reminder @Tido)

Da Xue likes this

Share this post


Link to post
Share on other sites

@Igor I think we can push 4.14 to NEXT, I have it ready to push, but there is the disabled RT patch that I haven't looked at.  (I'd forgotten all about it honestly)  Leave it for review later?  And can I push the changes?

 

Changes:

 

 -NEXT to 4.14.y (LTS?)

 -Patchset as discussed above.

 

 _                       _        _
| |    ___   _ __   ___ | |_ __ _| |_ ___
| |   / _ \ | '_ \ / _ \| __/ _` | __/ _ \
| |__|  __/ | |_) | (_) | || (_| | || (_) |
|_____\___| | .__/ \___/ \__\__,_|\__\___/
            |_|

Welcome to ARMBIAN 5.35 user-built Debian GNU/Linux 9 (stretch) 4.14.1-meson64
System load:   1.48 0.38 0.13   Up time:       0 min
Memory usage:  3 % of 1850MB    IP:            10.0.0.101
Usage of /:    9% of 29G

New to Armbian? Check the documentation first: https://docs.armbian.com

This kernel/patchset likewise results in a workable NanoPi K2 (minus wifi at the moment), can be tested.

Share this post


Link to post
Share on other sites

@Neil Armstrong I'm looking for others to verify this, but on my setup the left and right audio channels are swapped over HDMI.  I verified it wasn't my monitor/headphone configuration by simply changing the monitors selected input to my main computer, where the channels were correct.

 

I am also seeing a random MAC address, is there an official fix for that, or is it a workaround situation?

Share this post


Link to post
Share on other sites

The C2 is a gxbb board, it would be better discussed in the K2 topic.  :lol:

 

Me being a smartass aside, I will take a look.  For Le Potato I'm going to be testing out the Ethernet patches to hopefully cure the network dropping out.

 

*AT YOUR OWN RISK* You may be able to test the nanopi K2 image on the C2, they are both GXBB, I'd recommend comparing the device trees to look for any issues.

 

Share this post


Link to post
Share on other sites

The network issue appears resolved as of the gxl patches submitted a day or two ago.  I have enabled usb sound (modules), camera and cifs and ecryptfs.  I have one issue the hdmi sound works sometimes and not others,  The only messages that show up that might be related in syslog are:

Dec 21 08:08:39 localhost pulseaudio[12024]: [alsa-sink-meson-i2s-dai.0.auto-i2s-hifi i2s-hifi-0] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Dec 21 08:08:39 localhost pulseaudio[12024]: [alsa-sink-meson-i2s-dai.0.auto-i2s-hifi i2s-hifi-0] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA developers.
Dec 21 08:08:39 localhost pulseaudio[12024]: [alsa-sink-meson-i2s-dai.0.auto-i2s-hifi i2s-hifi-0] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Dec 21 09:40:38 localhost pulseaudio[12024]: [alsa-source-USB Audio] alsa-source.c: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Dec 21 09:40:38 localhost pulseaudio[12024]: [alsa-source-USB Audio] alsa-source.c: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
Dec 21 09:40:38 localhost pulseaudio[12024]: [alsa-source-USB Audio] alsa-source.c: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.

 

Is this unique to me or have others seen hdmi stop working?

Edited by Tido
addded code box

Share this post


Link to post
Share on other sites
22 minutes ago, reblair said:

Is this unique to me or have others seen hdmi stop working?

 

I have not seen it, however it's not impossible, the patches themselves refer to the sound driver as WIP, like I noted in the first post (which I update periodically), I am getting a left/right channel swap over HDMI.  Those errors do look like that is something to do with ALSA itself or the USB line in (I'm assuming since it's a source), since the error is mirrored across both devices.

 

I'm glad to see the networking appears to be resolved, so far I have not had any issues either.

Share this post


Link to post
Share on other sites
On 12/14/2017 at 6:14 AM, TonyMac32 said:

@Neil Armstrong I'm looking for others to verify this, but on my setup the left and right audio channels are swapped over HDMI.  I verified it wasn't my monitor/headphone configuration by simply changing the monitors selected input to my main computer, where the channels were correct.

 

Hum, I'd have check this out but I would not be surprised if the channels were swapped. Audio is still a "work in progress" at the moment. I'll try to have look at this later on. Thanks for reporting the problem

Share this post


Link to post
Share on other sites

With respect to the audio missing, it is true there is a mic equipped camera plugged in and oddly the issue must be intermittent because a reboot fixed it and it hasn't recurred after a day of running and occasional audio use (the camera still connected). 

Share this post


Link to post
Share on other sites

Ethernet Patch definitely made my potato solid.  I'm running fresh image now, with consul, nomad, docker and Jira running in a container..  def much faster than on my Opi2e.

 

Thanks for the patches!

 

Linux lepotato 4.14.8-meson64 #2 SMP PREEMPT Sun Dec 24 21:03:07 EST 2017 aarch64 aarch64 aarch64 GNU/Linux

 

Da Xue and TonyMac32 like this

Share this post


Link to post
Share on other sites

@Da Xue,  Just lately (in December) I downloaded the 2,2GB image from loverpi (aml-s905x-cc-ubuntu-xenial-linux-libretech-4.14.5-gd9ecccb8d-dirty-desktop-2017-12-17.img.zip) .

I read about the Keyboard bug and boom, it caught me as well. So I was looking here for an update: http://share.loverpi.com/board/libre-computer-project/libre-computer-board-aml-s905x-cc/image/ubuntu/   and yes there is a newer version than I have. So I did: apt-get update && apt-get upgrade  - no updates available.

 

How do you deliver updates to your images ?

 

Share this post


Link to post
Share on other sites

@Tido, Armbian is way better at this than we are. Right now apt-get update only updates the debian packages and not the kernel, u-boot, and any other image fixes. If you are using standard Ubuntu, Armbian is the way to go.

 

We have purchased a domain which we will package some u-boots and kernels but that won't happen until a non-preview release. Hence, why our images are "preview" releases rather formal releases. We anticipate the formal releases to happen around the time 18.04 comes out. Our images will have a different target than Armbian since we will be including some specific support for ecosystem components like FPGAs and HATs and our target markets. Armbian will be the more generic distro for these boards.

chwe likes this

Share this post


Link to post
Share on other sites
15 hours ago, Da Xue said:

that won't happen until a non-preview release

So you will start testing when you have a release available, but you might face problems then, because of no testing.
Why not start doing testing already and  name it like:  "Alpha or Beta  upgrade path - it might break your system" and the user has to activate it by themselv like in armbian ?

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

2 2

  • 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.