Screen wont detect?

[Lugnuts]

Hey guys,

First time firing up the N2 and my TV displays "mode not supported". I have the Linux and Android eMMC from ameridroid, the Android will display the hardkernel boot logo and then the TV displays "mode not supported". the Linux image however does not shot the boot logo.

Anything I could check before reflashing to a new image?

sorry in advance, I'm new to Linux.

my RPi3b runs fine on the same TV and HDMI cable.

[andy5macht]

I had the same issue with meveric´s debian stretch.
The only solution was to change boot.ini to disable display_autodetect:

Code: Select all

setenv display_autodetect "false"

[tobetter]

Hi, would you please share the two files edid.bin and display.bin in your memory card? These files will be created when display_autodetect is true and they contain the hardware information of your display which we can research why display does not come. I suspect that your display would have some special mode or DVI monitor, or something else. It would be also nice if you can share the exact product model of your display.

[Lugnuts]

I will jump on that when I get home later, thanks for the fast replies!

[Lugnuts]

Here is the edid.bin & display.bin

This is the TV I am using the N2 on. https://www.samsung.com/us/support/owne ... 610-series

[andy5macht]

I also got an older Samsung TV. If needed i can supply the two files this evening.

[joy]

I also got an older Samsung TV. If needed i can supply the two files this evening.

Hi andy5macht,
Could you make a new thread in [Issues] category of [ODROID-N2]?
It's a bit complicated to track history of this thread's owner.

Make a new thread and share the two files there.
I will find you in the new thread.

[joy]

Here is the edid.bin & display.bin

This is the TV I am using the N2 on. https://www.samsung.com/us/support/owne ... 610-series

Hi Lugnuts,
Thank you for sharing the files.
I've looked through them.
According to the information, the primary resolution of your samsung monitor is 1080p60hz (and other resolutions are also supported)
and your N2 did parse the timing well.
Hmm..... It should work with display auto detection......weird...

Could you try display manual mode of "1080p60hz" and "1360x768p60hz"?
Please modify boot.ini of your card as following.
You can find boot.ini file in /media/boot/ folder (vfat file system).

1. Change display_autodetect to "false"
https://github.com/mdrjr/n2_bootini/blo ... oot.ini#L7

Code: Select all

# Auto Detection of Monitor settings based on your Screen information
setenv display_autodetect "false"

2. Adjust hdmimode
https://github.com/mdrjr/n2_bootini/blo ... ot.ini#L49
(1) 1080p60hz

Code: Select all

setenv hdmimode "1080p60hz"

(2) 1360x768p60hz

Code: Select all

setenv hdmimode "1360x768p60hz"

Could you check it and share the test result?

-----------------------------------------------------------------------------------------------------------------

And here is the timing information of your monitor.

Code: Select all

Manufacturer: SAM Model 50d Serial Number 1
Made week 48 of 2008
EDID version: 1.3
Digital display
Maximum image size: 16 cm x 9 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
  720x400@70Hz
  640x480@60Hz
  640x480@67Hz
  640x480@72Hz
  640x480@75Hz
  800x600@60Hz
  800x600@72Hz
  800x600@75Hz
  832x624@75Hz
  1024x768@60Hz
  1024x768@70Hz
  1024x768@75Hz
  1280x1024@75Hz
  1152x870@75Hz
Standard timings supported:
  1152x864@75Hz
  1280x800@60Hz
  1280x960@60Hz
  1280x1024@60Hz
  1440x900@60Hz
  1440x900@75Hz
  1680x1050@60Hz
Detailed mode: Clock 148.500 MHz, 160 mm x 90 mm
               1920 2008 2052 2200 hborder 0
               1080 1084 1089 1125 vborder 0
               +hsync +vsync 
Detailed mode: Clock 85.500 MHz, 160 mm x 90 mm
               1360 1424 1536 1792 hborder 0
                768  771  777  795 vborder 0
               +hsync +vsync 
Monitor ranges (GTF): 24-75Hz V, 26-81kHz H, max dotclock 230MHz
Monitor name: SAMSUNG
Has 1 extension blocks
Checksum: 0x6b (valid)

CEA extension block
Extension version: 3
30 bytes of CEA data
  Video data block
    VIC 16 1920x1080@60Hz (native)
    VIC 04 1280x720@60Hz 
    VIC 05 1920x1080i@60Hz 
    VIC 03 720x480@60Hz 
    VIC 32 1920x1080@24Hz 
    VIC 34 1920x1080@30Hz 
  Audio data block
    Linear PCM, max channels 1
    Supported sample rates (kHz): 48 44.1 32
    Supported sample sizes (bits): 24 20 16
  Speaker allocation data block
  Extended tag: video capability data block
    YCbCr quantization: No Data (0)
    RGB quantization: No Data (0)
    PT scan behaviour: No Data (0)
    IT scan behaviour: Support both over- and underscan (3)
    CE scan behaviour: Support both over- and underscan (3)
  Extended tag: Colorimetry data block
  Vendor-specific data block, OUI 000c03 (HDMI)
    Source physical address 4.0.0.0
    Supports_AI
    DC_36bit
    DC_30bit
    DC_Y444
    Maximum TMDS clock: 225MHz
Underscans PC formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
Detailed mode: Clock 74.250 MHz, 160 mm x 90 mm
               1280 1390 1430 1650 hborder 0
                720  725  730  750 vborder 0
               +hsync +vsync 
Detailed mode: Clock 74.250 MHz, 160 mm x 90 mm
               1920 2008 2052 2200 hborder 0
                540  542  547  562 vborder 0
               +hsync +vsync interlaced 
Detailed mode: Clock 27.000 MHz, 160 mm x 90 mm
                720  736  798  858 hborder 0
                480  489  495  525 vborder 0
               -hsync -vsync 
Checksum: 0xbf (valid)

[Lugnuts]

Looks like turning auto detect off worked perfectly, thanks for all the help!