This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
No display on monitor, but system is up
#1
Hi.

My TB has been resting for a month or so while I finished a Raspberry Pi project, and today I was going to reconnect the TB and do some experimenting. The last time the TB was connected, it was running TinkerOS 1.8, and everything was working smoothly. As the microSD card had been reused for something else, this time I was going to try TinkerOS 2.0.4 to see what had changed.

So I booted the TB with a fresh TinkerOS 2.0.4 today, but I got no display on my monitor (NEC MultiSync EA244WMi). From this thread I got the tip to check my HDMI cable, but to no avail. I even switched the cable to a brand new one. What happens is that when the TB boots, the monitor awakens from sleep, cycles through its inputs (DVI->HDMI->DP->VGA->DVI) and goes back to sleep. So there is some kind of communication between the TB and de monitor, but there is nothing on the screen.

The TB is running, and I can connect to it using SSH. The only peripherals connected to the TB is a generic mouse and a keyboard - both worked with the TB earlier.

OK, so where to look and what to try?
  • The TB was powered with a PoE splitter, so I removed it and replaced it with a regular 2.5A power supply in case the PoE wasn't delivering enough juice for hte HDMI to work properly. No luck.
  • I tried TinkerOS 2.0.3, 1.9 and 1.8 successively to see if there was a problem with 2.0.4 and my monitor. No luck.
So now I am stuck, and don't know where to look. Is there a config file I can play with? Boot options to try? Where do I sacrifice the goat?

Any help is much appreciated.
Reply
#2
Just checked in tinker-config, and got this error message when I tried the option to set a fixed resolution: "There is no HDMI connected". Why doesn't the TB detect my monitor...? It did previously...
Reply
#3
So I have been digging a little today, and now, when booting a fresh TinkerOS 1.8, I get this in my dmesg log when grep'ing for "hdmi":

[ 2.840013] rockchip-pinctrl pinctrl: pin gpio7-19 already requested by ff980000.hdmi; cannot claim for ff170000.i2c
[ 5.201288] i2c i2c-6: of_i2c: modalias failure on /hdmi@ff980000/ports
[ 5.201343] dwhdmi-rockchip ff980000.hdmi: registered DesignWare HDMI I2C bus driver
[ 5.201458] dwhdmi-rockchip ff980000.hdmi: Detected HDMI controller 0x20:0xa:0xa0:0xc1
[ 5.202229] rockchip-drm display-subsystem: bound ff980000.hdmi (ops dw_hdmi_rockchip_ops)

Funny thing is - There is nothing connected to any pins on my TB. The board is totally clean, except from heat fins. I can't remember seeing this message previously, but I could very well be mistanking. I may have overlooked it earlier on.

Any and all help is much appreciated.

Just to add the info: My monitor is a 24” NEC MultiSync EA244WMi with a native resolution of 1920x1200 @60.

Did a new test - booted TinkerOS 2.0.4, and grep'ed for "hdmi" i dmesg. Got this:

Quote:linaro@TinkerBoard:~$ dmesg | grep -i hdmi
[    3.544073] i2c i2c-6: of_i2c: modalias failure on /hdmi@ff980000/ports
[    3.544096] dwhdmi-rockchip ff980000.hdmi: registered DesignWare HDMI I2C bus driver
[    3.544146] dwhdmi-rockchip ff980000.hdmi: Detected HDMI TX controller v2.00a with HDCP (DWC MHL PHY)
[    3.545150] rockchip-drm display-subsystem: bound ff980000.hdmi (ops 0xc0c724ec)
[    3.650422] dwhdmi-rockchip ff980000.hdmi: event 2
[    3.650882] dwhdmi-rockchip ff980000.hdmi: event 3
[    3.984918] dwhdmi-rockchip ff980000.hdmi: event 1
[    3.984962] dwhdmi-rockchip ff980000.hdmi: event 1
[    4.545895] dwhdmi-rockchip ff980000.hdmi: event 2
[    4.548327] dwhdmi-rockchip ff980000.hdmi: event 3

Still no idea what is going on... Confused Huh
Reply
#4
OK, so now I have tried booting armbian v13.13.0.74 to see if this helps my HDMI problem, but to no avail. I can log into the system via SSH, but still nothing on my monitor. In dmesg I can see this info:

Quote:[    0.954794] rockchip-drm display-subsystem: failed to bind ff980000.hdmi (ops 0xc0e82a0c): -517
[    1.221959] dwhdmi-rockchip ff980000.hdmi: Detected HDMI TX controller v2.00a with HDCP (DWC MHL PHY)
[    1.222256] rockchip-drm display-subsystem: bound ff980000.hdmi (ops 0xc0e82a0c)
[    2.676680] OF: /sound/simple-audio-card,codec: could not get #sound-dai-cells for /hdmi@ff980000

But then... BREAKTHROUGH!

In pure desperation, I tried a third monitor - a Dell U2711 (native 2560x1440 resolution), and voila! - I get an image. Both armbian v13.13.0.74 and TinkerOS 2.0.4 recognizes this monitor and outputs their image to the monitor.

So now I am puzzled...

Why don't I get video output on the NEC MultiSync EA244WMi (native 1920x1200 resolution), when previously I did? Even with a fresh SD Card made from the same IMG file that used to work (Tinker OS 1.8), I now get no video output. The Tinker Board does not detect a monitor.

And why do I get video output to my Dell U2711 but not the NEC MultiSync EA244WMi? The Tinker Board selects 1920x1080@60 resolution on the native Dell U2711 2560x1440 display, but at least I get an image output.

This is one of the reasons why I fear that the Tinker Board will not succeed as a "Raspberry Pi killer" (or even as a "low/no ambition" system). If the user can't reliable use his/her industry standard equipment, and trust that it will A) work at all, or B) work unchanged over time, then there are too many hurdles for the TB to make it.
Reply
#5
Hi Popeye70,

Can you try to modify the following file and remove the red part, and to check the result?

/etc/X11/xorg.conf.d/20-modesetting.conf 

Section "Device"
    Identifier  "Rockchip Graphics"
    Driver      "modesetting"
    Option      "AccelMethod"    "glamor"
    Option      "DRI"            "2"
EndSection
Section "Screen"
    Identifier "Default Screen"
    SubSection "Display"
        Depth 24
-        Modes "1920x1080" "1280x1024" "1024x768" "800x600"
    EndSubSection
EndSection
Reply
#6
(03-14-2018, 02:54 AM)ashinlin Wrote: Hi Popeye70,

Can you try to modify the following file and remove the red part, and to check the result?

/etc/X11/xorg.conf.d/20-modesetting.conf 

Section "Device"
    Identifier  "Rockchip Graphics"
    Driver      "modesetting"
    Option      "AccelMethod"    "glamor"
    Option      "DRI"            "2"
EndSection
Section "Screen"
    Identifier "Default Screen"
    SubSection "Display"
        Depth 24
-        Modes "1920x1080" "1280x1024" "1024x768" "800x600"
    EndSubSection
EndSection

Thanks for the tip! I tried to remove the line, but to no avail. Putting it back and adding "1920x1200" made no difference either. If I'm not mistaken, this setting would only affect the graphical user interface, not the initial boot sequence until the windows manager is started?

So... I get no screen output on my NEC MultiSync what so ever. No initial boot sequence, nothing. The monitor wakes up for 2 seconds, probably because it detects "something", but it only briefly displays "HDMI No signal" and goes back to sleep again as it is unable to make any sense of the signal.

Using tinker-config (on 2.0.4), I have tried to boot with overscan first enabled and then disabled, but no success.

And then, as a final test before I was going to let  the TB rest in a drawer, I decided to try the Tinker Board on some of my colleagues different monitors, with the following results:
  • My NEC MultiSync EA244WMi (1920x1200): No success (but it used to work!)
  • Colleague #1: Dell U2711 (2560x1440): Success
  • Colleague #2: Dell U2515H (2560x1440): Success
  • Colleague #3: NEC MultiSync EA223WM (1680x1050): Success
  • Colleague #3: NEC MultiSync EA244WMi (1920x1200): No success
  • Colleague #4: NEC MultiSync EA244WMi (1920x1200): Success!
All other monitors I have tested except the NEC MultiSync 244WMi appear to work, but I can't say that I have a lot of empirical data to support the conclusion. Even the NEC MultiSync 223WM (1680x1050) worked flawlessly. Two of the three NEC MultiSync 244WMi does NOT work, while the third did work. The first MultiSync NEC 244WMi did work when I last tried it with the TB (just before Xmas 2017), but it didn't work when I tried it again this February. All monitors work flawlessly with regular PCs (mainly ThinkPad X and T series).

So what's my conclusion? I don't know, to be honest. I don't feel really comfortable with the TB, as I was going to use it as a navigational aid on my boat, running OpenCPN. If I risk loosing the display sometime in the future,  this is not a viable option. As the new Raspberry Pi 3 B+ was announced today, I may end my Tinker Board adventure and stick to the RPi's as they have never failed me and have a much bigger user base, more active community and much broader support for devices and utilities/libraries to make the devices work without compiling my own code.
Reply
#7
(03-14-2018, 11:36 AM)Popeye70 Wrote:
(03-14-2018, 02:54 AM)ashinlin Wrote: Hi Popeye70,

Can you try to modify the following file and remove the red part, and to check the result?

/etc/X11/xorg.conf.d/20-modesetting.conf 

Section "Device"
    Identifier  "Rockchip Graphics"
    Driver      "modesetting"
    Option      "AccelMethod"    "glamor"
    Option      "DRI"            "2"
EndSection
Section "Screen"
    Identifier "Default Screen"
    SubSection "Display"
        Depth 24
-        Modes "1920x1080" "1280x1024" "1024x768" "800x600"
    EndSubSection
EndSection

Thanks for the tip! I tried to remove the line, but to no avail. Putting it back and adding "1920x1200" made no difference either. If I'm not mistaken, this setting would only affect the graphical user interface, not the initial boot sequence until the windows manager is started?

So... I get no screen output on my NEC MultiSync what so ever. No initial boot sequence, nothing. The monitor wakes up for 2 seconds, probably because it detects "something", but it only briefly displays "HDMI No signal" and goes back to sleep again as it is unable to make any sense of the signal.

Using tinker-config (on 2.0.4), I have tried to boot with overscan first enabled and then disabled, but no success.

And then, as a final test before I was going to let  the TB rest in a drawer, I decided to try the Tinker Board on some of my colleagues different monitors, with the following results:
  • My NEC MultiSync EA244WMi (1920x1200): No success (but it used to work!)
  • Colleague #1: Dell U2711 (2560x1440): Success
  • Colleague #2: Dell U2515H (2560x1440): Success
  • Colleague #3: NEC MultiSync EA223WM (1680x1050): Success
  • Colleague #3: NEC MultiSync EA244WMi (1920x1200): No success
  • Colleague #4: NEC MultiSync EA244WMi (1920x1200): Success!
All other monitors I have tested except the NEC MultiSync 244WMi appear to work, but I can't say that I have a lot of empirical data to support the conclusion. Even the NEC MultiSync 223WM (1680x1050) worked flawlessly. Two of the three NEC MultiSync 244WMi does NOT work, while the third did work. The first MultiSync NEC 244WMi did work when I last tried it with the TB (just before Xmas 2017), but it didn't work when I tried it again this February. All monitors work flawlessly with regular PCs (mainly ThinkPad X and T series).

So what's my conclusion? I don't know, to be honest. I don't feel really comfortable with the TB, as I was going to use it as a navigational aid on my boat, running OpenCPN. If I risk loosing the display sometime in the future,  this is not a viable option. As the new Raspberry Pi 3 B+ was announced today, I may end my Tinker Board adventure and stick to the RPi's as they have never failed me and have a much bigger user base, more active community and much broader support for devices and utilities/libraries to make the devices work without compiling my own code.

Hello,
If you have not give up your TB, you could give a try as following settings to check the result.

If you want to set a special resolution, you need to add the related parameter. The linux system provide the easy way to get. "cvt" command

EX:
ubuntu:~$ cvt 1920 1200 60
# 1920x1200 59.88 Hz (CVT 2.30MA) hsync: 74.56 kHz; pclk: 193.25 MHz
Modeline "1920x1200_60.00"  193.25  1920 2056 2256 2592  1200 1203 1209 1245 -hsync +vsync

Then you can modify the file(/etc/X11/xorg.conf.d/20-modesetting.conf ) as below and reboot the system.

Section "Device"
    Identifier  "Rockchip Graphics"
    Driver      "modesetting"
    Option      "AccelMethod"    "glamor"
    Option      "DRI"            "2"
EndSection
Section "Monitor"
    Identifier "Monitor 0"
    Modeline "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
EndSection
Section "Screen"
    Identifier "Default Screen"
    Monitor "Monitor 0"
    SubSection "Display"
        Depth 24
        Modes "1920x1200_60.00"
    EndSubSection
EndSection
Reply
#8
The standard foot in mouth logic dictates, since you can connect with other monitors like the el cheapo  "DELL" unit 

P.S. I am not a fan of "DELL", as a good brand name, due to a defective PC computer motherboard, suffering from the "Bad Cap's Syndrome" and the non standard motherboard main power connector.I apologize for digressing off topic here.

This standard 'foot in mouth logic' dictates there is a probable problem in this monitors basic set up parameters.

Now, the 28 page pdf owner user set up manual, shows this particular monitor has a variety of features( link https://www.necdisplay.com/documents/UserManuals/EA244WMi_EA273WMi_UserManual.pdf) one of the features involves a sync cable for up to five  separate sub monitors. The onscreen menu has a wide variety of options for the user to select.  Page 18 show the wide variety of features, this particular monitor has.

Stupid question number one: Is there the same no picture using a "HDMI" to "Display Port" cable?

Stupid question number two: Is there no picture using the "HDMI" to "DVI-D?

Stupid question number three: Is there no picture using the "HDMI" to "VGA" cable?

Stupid question number four: What are the basic set up parameters?

Stupid question number five: Has the units basic parameters been custom configured for another computers colour( one word with two different spellings. the English say "Colour", Americans say "Color") monitor card?


Sorry, for all these stupid questions.


Such is life.   Smile
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)