Are they hardware or software related?
Software.scotty101 wrote: ↑Fri Jun 28, 2019 9:45 amAre they hardware or software related?
Do I need to return this Pi while it is still within the returns policy?
tvservice -o "turns off" the screen
tvservice -p "turns on" the screen but the screen is still blank.
Does the output work when plugged in to a normal HDMI equipped monitor or TV? (I'm presuming the lapdock this is some sort of HDMI->LCD system?)Mortimer wrote: ↑Thu Jun 27, 2019 8:34 pmI am having trouble getting HDMI output from my new RPi4. I am able to get to it via SSH, so would appear to be working. The display (Motorola Atrix Lapdock) is not complaining that there is no signal, which it does if I switch the connection to the HDMI-1 port. So I presume there is a signal there, but the lap dock is not displaying it.
I tried the following:
hdmi_force_hotplug:0 = 1
hdmi_group:0 = 2
hdmi_mode:0 = 39
The lap dock now displays the four raspberries, then it blanks with a flashing cursor. I will get a brief flash of the splash screen (less than a second) a few more seconds of flashing cursor then the screen goes completely black and nothing further is displayed.
Will give this a try later too. I may be going crazy but I thought I had read that hdmi_boost didn't work with the Pi4.goodburner wrote: ↑Fri Jun 28, 2019 10:47 amI was having similar issues where it wouldn't boot if I enabled some options like VNC, Serial Port, Serial Console, overclock GPU memory, etc.. I was able to fix this by setting
confIg_hdmi_boost to 7.
At least I think so, I'm upgrading packages right now and will report if it is successful.
Because some bugs only show up after launch? Impossible to test every single TV/Monitor/HDMI convertor, and even with the larger beta test program we used this time, you cannot catch everything.goodburner wrote: ↑Fri Jun 28, 2019 11:19 amafter upgrading the packages it went blank again after showing the cursor at the top left like before.
I had to disable vnc and serial port/console again and noticed the screen was set to 4k while I had it at 1080p previously.
it seems to be working now.
I'm not sure why these weren't caught before releasing the device.
Not a solution to the HDMI problem. Whilst my TV has a composite input, i don't have the correct cable and the normal screen I use with Pi's is the Nexdock (more portable)
I have been able to SSH in to the Pi. I setup WiFi/SSH on a Pi3. This gave me the ability to run the tvservice command to try a few things as well as change the config.txt file and safely shutdown the Pi
+1 I've had the same issue and logged it. AIUI it's more to do with Buster/current kernel etc. than a "P4B thing" (ie. it happened with Buster on a Pi B2 too) and is worse with TV's / CEA modes. (IIRC EDID info. not being passed fully in some cases). Ironically, IIRC, I got a "better" result via an HDMI-to-VGA converter and a VGA input which used a (reduced) set of DMT (cf. CEA) modes.
Code: Select all
[pi4] # Enable DRM VC4 V3D driver on top of the dispmanx display stack #dtoverlay=vc4-fkms-v3d max_framebuffers=2 hdmi_force_hotplug:0=1 #hdmi_safe=1 hdmi_group:0=1 hdmi_mode:0=4