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

preview Asus Tinkerboard
34 34

477 posts in this topic

Recommended Posts

14 hours ago, dragonlost said:

I use image : Armbian_5.33_Tinkerboard_Ubuntu_xenial_next_4.13.3_desktop . I use etcher for flash sdcard.

 

I have no problem with network manager just permission connection editing problem. What are permission for editing connection in network manger ?

Sounds like the user you are logged in as a user that hasn’t been added to the correct groups. Did you create a new user?

 

Can you post the output of:

ls -la /etc/NetworkManager/

cat /etc/group

Share this post


Link to post
Share on other sites

There was an issue with board support packages after the last stable release and most likely images that were rebuilt afterwards (including Tinkerboard images) have this bug - policykit files were placed in a wrong directory, which affected NetworkManager, stutdown/reboot from the desktop menu and other things that rely on policykit.

Share this post


Link to post
Share on other sites

Hello.

 

I see config file for kernel 4.14 support RTC ds1307 I2C.

 

I would like to know if this kernel supports this RTC ? Because I would like to be able to use one to have the time maintained on my tinkerboard.

 

Share this post


Link to post
Share on other sites
On 10/1/2017 at 8:30 AM, TonyMac32 said:

Basic status update here (31 followers of thread) 

 

  • All mainline kernels support wireless
  • All kernels reboot properly
  • Mainline kernel HDMI hotplug now supported

 


Are these kernels out of beta? I do a dist-upgrade and see nothing as of yet, still on 4.11.6

Share this post


Link to post
Share on other sites
18 minutes ago, Frostbyte said:

Are these kernels out of beta?

 


We plan to put them into stable repository after in deep testing. https://forum.armbian.com/index.php?/topic/5149-upcoming-release-date-feature-freeze/ Simply contact @Tido to put you on a list and he will note you when we are ready for a final round of testing. ... if you want to help us out and make this happen sooner.

 

Frostbyte likes this

Share this post


Link to post
Share on other sites

Just tried the latest nightly build. It's quite smooth and stable. Unfortunately it still doesn't have sound. Hope this can be resolved soon. This is probably the only show stopper to use this os as the daily driver.

Share this post


Link to post
Share on other sites

Sound isn't really that bad to enable, but last I checked it made some awful noises.  The short of it is that ASUS/Rockchip decided not to use the on-board audio of the SoC and instead used a USB codec that I can't find any drivers for other than "Generic USB"  Certain audio sources output horrific noises, so I never changed the settings to enable it by default.

 

To be fair debugging that completely slipped my mind as I never have a chance to use the thing as anything but a test box.  Let me look around for this, it is a giant hole in the side of the only real use case for this board...

Share this post


Link to post
Share on other sites
43 minutes ago, TonyMac32 said:

USB codec that I can't find any drivers for

Have already gathered some information about this 'device'?  If so, can you post it?

Share this post


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

Sound isn't really that bad to enable, but last I checked it made some awful noises.  The short of it is that ASUS/Rockchip decided not to use the on-board audio of the SoC and instead used a USB codec that I can't find any drivers for other than "Generic USB"  Certain audio sources output horrific noises, so I never changed the settings to enable it by default.

 

To be fair debugging that completely slipped my mind as I never have a chance to use the thing as anything but a test box.  Let me look around for this, it is a giant hole in the side of the only real use case for this board...

 

@TonyMac32 Thanks for looking into this. In the mean time, is there some instruction for me to enable sound over HDMI in the mainline nightly build? I really only need sound in Chromium.

 

I'm quite impressed by the Armbian. x2goclient runs so much smoother in Armbian than TinkerOS 2.01. I recorded a screencast to show this:

 

https://tinkerboarding.co.uk/forum/thread-663.html

 

Igor likes this

Share this post


Link to post
Share on other sites

Hi guys, just a quick question. What am I doing wrong if Firefox always crashes when I start it? The system is updated and I haven't changed much yet. Thanks for any help.

Share this post


Link to post
Share on other sites

@Minty I haven't run into that issue, I can test it later (power outage at the moment)

 

@badrobitsame basic message, I've not had any permission issues with Wifi, have you done anything specific with the image before trying to use wireless?  Did you have any issues creating the default user, use ether to burn the image, etc?

Share this post


Link to post
Share on other sites

@TonyMac32 I haven't done anything to the image. I flash it to my SD card using the etcher tool on Windows 10, boot the TinkerBoard, update the root password to ubuntu, create a new user (ubuntu) set its password to ubuntu and then hit enter for all the questions about the user. I then attempt to connect to my hidden wifi network. I provide the SSID, and select the WEP & WPA2 Personal option provide the password and hit enter. I then get a popup saying "Failed to add new connection (1) Insufficient privileges. 

Share this post


Link to post
Share on other sites
2 hours ago, gururise said:

Anyone able to get sound over HDMI or through the audio out to work?

I have not tried over HDMI.  The audio out can be enabled by setting up the proper output, there are some posts about that earlier in the thread.  The caveat is some random noise output that is pretty bad, which I haven't had opportunity to figure out so I haven't enabled it.  

Share this post


Link to post
Share on other sites

Hello.

 

Like badrobit. On the RC5 and RC4 version of the nightIy no longer have the right to edit or add to the conection on network-manager with the account created at startup. Yet it seems to me that this problem had been solved in the RC3 nightly by correcting the location of the policies. (the stable and next version have the same problem).

Share this post


Link to post
Share on other sites

I've added RPi 7" DSI touchscreen support to the 4.4 kernel, I will work on patching it into mainline as well, but no guarantee, it is not the cleanest of drivers (requires modifying the dw-mipi-dsi.c file), and this patch is MiQi safe.

 

This would have been done earlier, but I had to make sure it would work by declaring the hardware in the device tree instead of explicitly in the kernel source. (and make sure it didn't break the MiQi)  As it turns out, I was incredibly overthinking the problem, cheers to the Linux kernel devs. :beer:

 

Tested OK with this configuration: 

  • Tinker with DSI Display
  • Tinker with DSI Display and HDMI display
    • (displays are "on top of each other" on first boot, drag the smaller display around in the desktop settings and you have an extended desktop)
    • Touchscreen driver is not robust against this configuration.  It tries to cover the full extended desktop.
  • Tinker with only HDMI (no ghost devices/errors/crashes. Tested to be sure the drivers could cope with not finding the hardware, as the device tree entries are still there)
  • MiQi (as it does not have the DT entries, merely a test to make sure no source/driver interactions)

 

chwe likes this

Share this post


Link to post
Share on other sites

a couple days ago, but:  https://www.asus.com/uk/Single-Board-Computer/Tinker-Board/HelpDesk_Download/

Version 2.0.3 Beta  Version 2017/10/30   some points from the changelog:

  • Let USB audio card would not break the PulseAudio's some setting.
  • Add more hardware interface config (SPI0/UART2/UART3/UART4/PCM) setting at hw_intf.conf.
  • Update QT5, GStreamer, xserver packages  ... (maybe related to this post on github)
  • Modify DTS overlay folder name & add prefix/postfix for overlay file(s)

and so on

Share this post


Link to post
Share on other sites
6 minutes ago, Tido said:

Version 2.0.3 Beta

 

Unfortunately, being beta, I don't believe any of the changes are reflected in the github.  I do need to go through and see what's been added to the Tinker-specific kernel in the past few months, and again see what I can do to make it work with MiQi (This is not MiQi's fault, this is pure Tinker Board nonsense).

Share this post


Link to post
Share on other sites

If you want to do audio testing, the capability has always been there, but when I first tried it there was a lot of ugly (and potentially dangerous) noise on certain files/bitrates.  See

Sound was never disabled, you just had to do your homework to get it.  Since I was trying to get a lot of other things working at the time I did not patch the suspect settings into the system for the fear of breaking things.  You enable this at your own risk, once enough people with enough time show me enough evidence that all is well we can see about setting it up to work out of the box.

 

My recommendation is to use a cheap speaker and keep the volume low, cycle through various bitrates and sources/programs before trusting it until we can be reasonably sure the Rockchip/PA demons have gone away.

 

I have not yet tried this with Mainline or Armbian Legacy.  At the moment I am experimenting with the Rockchip main 4.4 repo, this is extra super WIP for people who know it isn't going to work perfectly and can build their own:  https://github.com/Tonymac32/build

 

Share this post


Link to post
Share on other sites

This board seems to work well for me with Armbian once I'd resolved the power supply issue. I'm running the ethernet link at 1G, sound is provided by an external CM108 device.  I'm mainly using it for light desktop work, browsing using Chromium and also running the Arduino IDE. Compared to a Pi3 it does all these tasks faster. :)

 

Welcome to ARMBIAN 5.36 user-built Ubuntu 16.04.3 LTS 4.13.16-rockchip
System load:   0.00 0.00 0.00   Up time:       4 days
Memory usage:  7 % of 2005MB    IP:            10.xxx.yyy.zzz
CPU temp:      58°C
Usage of /:    23% of 15G

[ General system configuration (beta): armbian-config ]

Last login: Sun Jan 14 20:18:47 2018 from 10.xxx.yyy.zzz

 

 

 

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

34 34

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