Raspberry Pi Model B HDMI issue

Hello,

I have a Pavilion 25xi monitor, it is fairly new and has a resolution of 1920 x 1080.

Here are some things i tried again:

- I removed the lines from the config.txt file, but then i get a "Check cable" dialog when booting the RPi.
- I added "hdmi_safe=1" to the config.txt file, i was able to see very low resolution output on the screen for a few seconds. But then the screen turns black and stays that way.

Some other commands which didn't work (tested them one by one):

framebuffer_width=1920
framebuffer_height=1080

hdmi_force_hotplug=1

config_hdmi_boost=4

Hope to hear from you soon!
Too bad i don't have another monitor to test it out.

Hello,

I have a Pavilion 25xi monitor, it is fairly new and has a resolution of 1920 x 1080.

Here are some things i tried again:

- I removed the lines from the config.txt file, but then i get a "Check cable" dialog when booting the RPi.
- I added "hdmi_safe=1" to the config.txt file, i was able to see very low resolution output on the screen for a few seconds. But then the screen turns black and stays that way.

Some other commands which didn't work (tested them one by one):

framebuffer_width=1920
framebuffer_height=1080

hdmi_force_hotplug=1

config_hdmi_boost=4

Hope to hear from you soon!
Too bad i don't have another monitor to test it out.

If it is a modern HDMI monitor then you should not have to modify any of the config files after imaging the SD card, it just works

this is a video I produced setting up Raspbian

Raspberry PI Model B+ Quick Set-up (1/2 Hour Guide from unpack to GUI and WIFI)

btw, how are you modifying the config files ?, remote SSH, XWINDOW ?

n HP Pavilion 25xi is indeed modern and should cope perfectly if 'just plugged in' to an RPi via HDMI.
Here are lines to include in config.txt to force a couple of resolutions. I suspect these will not work any better than what you have tried already though. In which case, try the alternate possibilities of insufficient voltage suggested by others. (unplug everything from the Pi except the monitor and a keyboard ...), and measure the voltage between TP1 and TP2 after trying to boot. Or, if it boots with nothing else plugged in, then you've found the problem!

I have left in the comments to explain what the lines do and what you can try. This is straight from my own config.txt and modes 4 and 16 both work fine.
# uncomment if hdmi display is not detected and composite is being output
# eg if using 3 to 1. Defaults to low resolution unless uncomment rows below too
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode
# note these override choosing 'best' mode even if a monitor is detected
# (mode 16 will force 1080p 1920x1080, 60Hz, progressive)
# (mode 4 will force 1280x720, 60Hz, progressive)
hdmi_group=1
hdmi_mode=4

And the following is a longer list of possible resolutions - these are just the ones that my 1920x180 monitor can cope with..
HDMI_group=1 (CEA) has 15 modes:
           mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
           mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
           mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
           mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
           mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
           mode 6: 720x480 @ 60Hz 4:3, clock:27MHz x2 interlaced
           mode 7: 720x480 @ 60Hz 16:9, clock:27MHz x2 interlaced
  (prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
           mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
           mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
           mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive
           mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced
           mode 21: 720x576 @ 50Hz 4:3, clock:27MHz x2 interlaced
           mode 22: 720x576 @ 50Hz 16:9, clock:27MHz x2 interlaced
  (native) mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive
HDMI_group=2 ( DMT) has 20 modes:
           mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
           mode 5: 640x480 @ 72Hz 4:3, clock:31MHz progressive
           mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive
           mode 8: 800x600 @ 56Hz 4:3, clock:36MHz progressive
           mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive
           mode 10: 800x600 @ 72Hz 4:3, clock:50MHz progressive
           mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive
           mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive
           mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive
           mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive
           mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive
           mode 32: 1280x960 @ 60Hz 4:3, clock:108MHz progressive
           mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive
           mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive
           mode 39: 1360x768 @ 60Hz 16:9, clock:85MHz progressive
           mode 42: 1400x1050 @ 60Hz 4:3, clock:121MHz progressive
           mode 47: 1440x900 @ 60Hz 16:10, clock:106MHz progressive
           mode 48: 1440x900 @ 75Hz 16:10, clock:136MHz progressive
           mode 51: 1600x1200 @ 60Hz 4:3, clock:162MHz progressive
   mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive

I still do not understand why you need to set any forced values to get it to work

I tried mine on a few different HDMI screens at home and everyone worked without adjustment

It will be interesting to see if it is something other than power related

if you have not read the blog articles Myself and others have provided, I suggest you do before spending too much time on other avenues of investigation