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

Rock64 armbian image ethernet password
0

20 posts in this topic

Recommended Posts

Just got a rock64 board and tried the armbian testing image. Is ethernet working out-of-the-box with this image? My ethernet isn't working. Also the normal password didn't work (root / 1234). Would be nice to have some infos about that.

Share this post


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

Also the normal password didn't work (root / 1234).

To my knowledge, root 1234 should work on every board. That's often a sign that something on your system is corrupt. Did you follow the getting started recommendations? (e.g. etcher instead of dd/win32, reliable SD card & psu).

Share this post


Link to post
Share on other sites
5 minutes ago, zador.blood.stained said:

I heard about different issues (not related to tx/rx offloading) on the production boards.

 

Yes, ayufan said he had problems with Ethernet -- we talked today in #ROCK64 channel and I tested with 1GB production board (and offloading active): https://pastebin.com/aAzkEYEB (somewhat low performance in one direction but IMO not critical) and then next batch of boards got DRAM 'downgraded' which seems to cause problems for him.

 

Anyway: I tested with production board and without tx/rx offloading fix/workaround Ethernet stopped to work after ~30 seconds as it's the case with the pre-production boards too.

Share this post


Link to post
Share on other sites
1 minute ago, tkaiser said:

Anyway: I tested with production board and without tx/rx offloading fix/workaround Ethernet stopped to work after ~30 seconds as it's the case with the pre-production boards too.

Unfortunately udev rules don't work since they are executed too early, so we may need a simple systemd service to execute the ethtool command at the right time.

Share this post


Link to post
Share on other sites
1 minute ago, zador.blood.stained said:

Do these hooks work with NM too?

 

At least as long as the interface is not controlled by NM it works (tested 20 days ago when I benchmarked my first Armbian build on ROCK64). So we might add a NM hook too but since their way of doing things isn't that persistent a systemd service might be the better idea...

 

What about this in the meantime?

diff --git a/packages/bsp/common/etc/init.d/armhwinfo b/packages/bsp/common/etc/init.d/armhwinfo
index 96345fa..1900085 100755
--- a/packages/bsp/common/etc/init.d/armhwinfo
+++ b/packages/bsp/common/etc/init.d/armhwinfo
@@ -253,6 +253,8 @@ prepare_board() {
                                        echo 7 >/sys/class/net/eth0/queues/rx-0/rps_cpus
                                        echo 32768 >/proc/sys/net/core/rps_sock_flow_entries
                                        echo 32768 >/sys/class/net/eth0/queues/rx-0/rps_flow_cnt
+                                       # preliminary rx/tx offloading workaround
+                                       /sbin/ethtool -K eth0 rx off tx off
                                        ;;
                                nanopim3) # dw-mci on cpu1, USB host on cpu2, GbE on cpu3, USB OTG on cpu4, video-codec on cpu5
                                        for i in $(awk -F':' '/dw-mci/{print $1}' </proc/interrupts | sed 's/\ //g'); do

 

Share this post


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

root login with the default password 1234?

 

Initial root login on Armbian is always 1234 unless changed within build script.

Share this post


Link to post
Share on other sites

Please describe your situation in details, perhaps add screenshot or video.

 

Are you trying to log in via serial console? In case it's not added to /etc/securetty ... it's not possible to login in. In case of this board, this is quite possible since it's WIP.

Share this post


Link to post
Share on other sites

No, I didn't use a serial console. I use a hdmi screen and a usb keyboard. I boot the board, the login screen appears and I try to login. But the system doesn't accept "root" as user, the error message is "incorrect login", the "password" prompt doesn't appear. It's possible to tape "rock64", than the password prompt appears.

Share this post


Link to post
Share on other sites
On 7.9.2017 at 6:19 PM, tkaiser said:

Sorry, I'm a nob, but maybe it's not so complicated to use the script from ayufan. I put it in the directory like in his github repo (/etc/network/if-up.d/rock64-offload) and made it executable. But it's not working on my rock64 (Version 2.0, 2 GB). Can anyone help me? Or is there a possibility to solve the ethernet problem with one of the next nightly builds. That woud be great :-)

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

0

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