35 35
Peba

Asus Tinkerboard

Recommended Posts

@TonyMac32 Probably I didn't explain my problem well.

 

When I run tinkerboard with armbian, I can NOT access the server through SSH or directly because HDMI doesn't work as well.

 

So I can't run the  armbianmonitor -u.

 

 

Share this post


Link to post
Share on other sites

It's impossible to debug without information beyond "it doesn't work". As far as the no SSH issue, that is very irregular. What kernel/image/etc? I'm guessing you don't have the ability to watch the debug UART?

Sent from my Pixel using Tapatalk

Share this post


Link to post
Share on other sites
3 hours ago, JMCC said:

What do you put in config.txt in your rpì?

 

on my raspberry :

hdmi_pixel_freq_limit=400000000
hdmi_drive=2
hdmi_mode=87
disable_overscan=1

# 10.1 inch
hdmi_timings=1200 0 100 24 52 1920 0 65 4 25 0 0 0 60 0 169000000 0
max_framebuffer_width=1920
max_framebuffer_height=1920
display_rotate=3
framebuffer_width=1920
framebuffer_height=1200

 

finally I was able to test my home on my linux is it worked. But still not on the tinkerboard.

On my linux computer :

"1200x1920_59.87"  159.00  1200 1215 1216 1320  1920 1983 1985 2012  +HSync +VSync

I have to test this xrandr parameter in my tinkerboard.

 

 

Share this post


Link to post
Share on other sites

@martinayotte It's two different problems, of course.
1- I can't connect to port 22 (although ping works, so I have routing to the board).
2- I can't get any image on a monitor over HDMI. 
 

@TonyMac32 You are completely right. I know for you it's very difficult to help me with me just complaining "it doesn't work".
I hoped that someone here had a similar problem in the past and point me that I'm doing some kind of "rookie" mistake.

 

The armbian version I'm using was Armbian_5.35.171201_Tinkerboard_Ubuntu_xenial_next_4.14.2 and similar desktop version. I tried more 1 or 2 older versions  from https://dl.armbian.com/tinkerboard/archive/ without success. 

I would say the problem was on my board but I got it working with tinkerOS (both ssh and HDMI)
So the problem is somewhere else... 

Share this post


Link to post
Share on other sites
22 minutes ago, João Cravo said:

1- I can't connect to port 22 (although ping works, so I have routing to the board).

I've seen a case where file system was corrupted, SSL certificate/keys file corrupted preventing the SSHD to start.

That could explain your issue ... To be sure, you need to log using USB-TTL Serial dongle and verify the log, especially "systemctl status ssh.service".

 

Share this post


Link to post
Share on other sites

If the 4.14 image is from the right period of time, the u-boot can lock up while trying to init the HDMI monitor. That's what I mentioned to dragonlost earlier.

Sent from my Pixel using Tapatalk

Share this post


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

can lock up while trying to init the HDMI monitor

Was this where you had to unplug and plug again?

Share this post


Link to post
Share on other sites

This was where you boot without the monitor attached and plug it in later. But that was only a few reports, best to just use an up to date image

Sent from my Pixel using Tapatalk

Share this post


Link to post
Share on other sites

I just tested the following ones
- Armbian_5.75_Tinkerboard_Debian_stretch_next_4.19.20
- Armbian_5.75_Tinkerboard_Ubuntu_bionic_next_4.19.20
- Armbian_5.75_Tinkerboard_Ubuntu_bionic_next_4.19.20_desktop

Always the same result as showed below :( 
I guess I will buy the USB-TTL Serial dongle and give it a try as @martinayotte suggested.

$ sudo nmap -sn 192.168.0.0/24
Starting Nmap 7.70 ( https://nmap.org ) at 2019-03-03 13:21 CET
Nmap scan report for tinkerboard.home (192.168.0.10)
Host is up (0.015s latency).
MAC Address: 88:D7:F6:C2:E3:ED (Asustek Computer)
(...)

$ ping 192.168.0.10
PING 192.168.0.10 (192.168.0.10): 56 data bytes
64 bytes from 192.168.0.10: icmp_seq=0 ttl=64 time=3.717 ms
64 bytes from 192.168.0.10: icmp_seq=1 ttl=64 time=4.386 ms
64 bytes from 192.168.0.10: icmp_seq=2 ttl=64 time=5.429 ms

$ nc -v 192.168.0.10 22
nc: connectx to 192.168.0.10 port 22 (tcp) failed: Operation timed out

 

Share this post


Link to post
Share on other sites

What I sometimes do before I resort to the serial port:

 

If you are starting from sd-card, take it and insert it with a USB adapter on a linux pc. Mount it and look at /var/log to get some hints.

 

Perhaps put some diagnostic commands into /etc/rc.local, like "systemctl status ssh.service (with output into a file)" or whatever (like netstat -tlpen, is port even open?). Especially perhaps try to run "armbianmonitor -u" in there.

 

Reboot, and then take it to a pc again and look at the output.

 

It's a pain but sometimes you can see something while you are waiting for the USB-TTL serial dongle.

 

Share this post


Link to post
Share on other sites
3 hours ago, João Cravo said:

I just tested the following ones
- Armbian_5.75_Tinkerboard_Debian_stretch_next_4.19.20
- Armbian_5.75_Tinkerboard_Ubuntu_bionic_next_4.19.20
- Armbian_5.75_Tinkerboard_Ubuntu_bionic_next_4.19.20_desktop

Why don't you test some "Default" images (kernel 4.4.y)? If those work, then at least we can narrow down the problem to mainline.

Share this post


Link to post
Share on other sites

Hello.

After a lot of trying with xrandr. I can not have an image on the tinkerboard with this screen.

Here is the edid of the screen.
 

connected 1920x1200+0+0 (0xd4) right (normal left inverted right x axis y axis) 720mm x 720mm
    Identifier: 0x6a
    Timestamp:  245757
    Subpixel:   unknown
    Gamma:      1.0:1.0:1.0
    Brightness: 1.0
    Clones:    
    CRTC:       2
    CRTCs:      0 1 2
    Transform:  1.000000 0.000000 0.000000
                0.000000 1.000000 0.000000
                0.000000 0.000000 1.000000
               filter:
    EDID:
        00ffffffffffff00328d5e04aac83301
        241b0103951f1178eaebf59559549027
        1e505400000001010101010101010101
        0101010101011c3eb07840805c700f01
        f20cd0d02200001e0000000000000000
        00000000000000000000000000fe004c
        6f6e7469756d0a2020202020000000fe
        00776972656c6573732d7461670a01be
        02031902000000000000002308070783
        00000065030c00100000000000000000
        000000000000000000001e0000000000
        00000000000000000000000018000000
        00000000000000000000000000001800
        00000000000000000000000000000000
        18000000000000000000000000000000
        0000000000000000000000000000003a
    non-desktop: 0
        range: (0, 1)
    link-status: Good
        supported: Good, Bad
  1200x1920 (0xd4) 159.000MHz +HSync +VSync *current +preferred
        h: width  1200 start 1215 end 1216 total 1320 skew    0 clock 120.45KHz
        v: height 1920 start 1983 end 1985 total 2012           clock  59.87Hz


I tried to start with to see. Then to see with ssh or vnc or nomachine. Can not see the screen.

 

Share this post


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

I can not have an image on the tinkerboard with this screen.

Did you try the Default (4.4.y) kernel?

Share this post


Link to post
Share on other sites

TINKERBOARD FREEZES UNDER NFS LOAD

 

Hi, I'm not sure where to post my issue but the Rockwell Eth issue which freezes my Tinkerboard under NFS load is back with the new images.

 

So far I've been using the 'Armbian_5.59_Tinkerboard_Ubuntu_bionic_next_4.14.67_desktop' image upgraded via apt to the most recent version

( ARMBIAN 5.73 stable Ubuntu 18.04.2 LTS 4.19.20-rockchip). Based on prior advice I've added 

 

sudo ethtool -K eth0 tx off rx off

 

to /etc/rc.local as the rk3328 is buggy on tx offloading

 

Given the new images I've tried 'Armbian_5.75_Tinkerboard_Ubuntu_bionic_next_4.19.20_desktop' with the same entry in /etc/rc.local but
as soon as I start multiple compiles via NFS the Tinkerboard freezes - just like the old image did prior to the ethtool modifications.

 

Any idea how what might be wrong as I otherwise like some of the new features from the updated image?

 

 

Share this post


Link to post
Share on other sites
On 3/11/2019 at 3:31 PM, stefan.steffens said:

TINKERBOARD FREEZES UNDER NFS LOAD

 

Hi, I'm not sure where to post my issue but the Rockwell Eth issue which freezes my Tinkerboard under NFS load is back with the new images.

 

So far I've been using the 'Armbian_5.59_Tinkerboard_Ubuntu_bionic_next_4.14.67_desktop' image upgraded via apt to the most recent version

( ARMBIAN 5.73 stable Ubuntu 18.04.2 LTS 4.19.20-rockchip). Based on prior advice I've added 

 

sudo ethtool -K eth0 tx off rx off

 

to /etc/rc.local as the rk3328 is buggy on tx offloading

 

Given the new images I've tried 'Armbian_5.75_Tinkerboard_Ubuntu_bionic_next_4.19.20_desktop' with the same entry in /etc/rc.local but
as soon as I start multiple compiles via NFS the Tinkerboard freezes - just like the old image did prior to the ethtool modifications.

 

Any idea how what might be wrong as I otherwise like some of the new features from the updated image?

 

Check if your 'kernel.hung_task_panic' is set to 1.  My fresh install had it set and it was causing me issues with network based storage.

 

sysctl kernel.hung_task_panic

 

If it is, set it to zero

 

sysctl -w kernel.hung_task_panic=0

sysctl -p

 

John

Edited by jad3675

Share this post


Link to post
Share on other sites

Thanks for the hint but funnily when I started from scratch with a new SD card I couldn't reproduce the crashes even under heave NFS load on GigEth :-)

 

And this while 'kernel.hung_task_panic' was set to 1

 

Though I'm sure of not having changed anything (I'm using a step-by-step cook book to make sure I don't forget anything) compared to the first setup I'm now a happy
user again as it's working.

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
35 35