Hi Da Flex,
Thanks for responding.
Yes, I have tried hdmi_safe=1 and both HDMI sockets. I also have hdmi_force_hotplug=1. Even when the monitor shows no signal, I disconnect the cable from the monitor and connect it to a different monitor, it works fine. I'm guessing the monitor is not sending the right data to tell the Pi what mode to use.
Here is what tvservice -m CEA shows:
# tvservice -m CEA
Group CEA has 9 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
(native) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive
Display More
Here is the status:
tvservice -s
state 0xa [HDMI CUSTOM RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive
I just did a tvservice -n and it shows the model number of the monitor that it's connected to. So there is communication.
tvservice -n
device_name=VIZ-E241i-B1
I saw a page somewhere that I can't find anymore where I hardcoded modes and resolutions into config.txt and it didn't help. I don't know the tvservice command at all so I don't know if the output above is what's reported from the monitor or if it's what the Pi supports.
I am using a case that routes the ports to the back of the case, and I have tried direct connecting. Since it works on another monitor, then it must be something in how monitors are communicating with the Pi.
Other suggestions?
Thanks,
Mike