Muse wrote: ↑Tue Jul 02, 2019 3:41 pmHi.
I recently purchased the 4gb model of the new Pi 4, I first realised I needed a micro hdmi to hdmi, so I bought that. Then I thought I'd try to just use my 8gb memory card that I was previously using with my Pi2 with no problems. However when I inserted a mouse, keyboard, micro hdmi, and then finally the Power cable but to no avail, nothing happened. I get a green light flash for one second with the red, and then only red.
So I thought maybe its the sd card, so I bought a new 64gb one, I've loaded Noobs 3.0.1 onto it, plugged everything else in, and its still black! still says no input.
I haven't touched my Pi in a few days, and now I'm back to square one. No splash screen. No inputs. The red and green LED do some flashing initially, and then the red stays on, the green goes out, and nothing on screen... WTF is up with this board?jeffcodes wrote: ↑Wed Jul 17, 2019 2:12 amI'm having the same problems. Black screen, I don't even get the initial splash screen. I've tried flashing the bootloader and that does not help.
I have even had mixed success getting the red and green led's to light up.
I did verify that my SD card and the install was successful by running it on my Pi 3 B.
I have tried to SSH into the machine but I can't even get it to register an IP address on my wired network. I thought perhaps the micro HDMI adapter I bought was DOA. That doesn't appear to be the issue either.
I used etcher to flash OS to the disk.
Pretty out of tools in my toolbox at this point. I had to order this thing from the UK, so I hope it doesn't have to go back...
Any ideas are greatly appreciated.
UPDATE: I downloaded and flashed the Buster with desktop only ( I was trying Buster full with recommended software), and got it to boot finally. I got the immediate Rasbian splash screen, and then it took several minutes for it to fully boot up and into the set-up screen. Walking through set-up also took another several minutes. After this, the system rebooted and it was running fairly smooth. I tried an NES emulator and the sound is pretty broken up, and frame rate was terrible. This is par for the course from what I've read. Still some work needed to get the most out of this little board.
This post is helpful of you find yourself here: https://www.raspberrypi.org/forums/view ... 8#p1485558
the green light indicates that the sd card is being read if its not on it can mean a couple of thingsCorbod89 wrote: ↑Thu Jul 11, 2019 8:14 pmHey,
Complete noob here having the same problem. Tried a number of steps (see below)
1 - Reinstalling NOOBs/Raspbian onto a new SD card (tried this a couple of times).
2- Reprogrammed the EEPROM.
Still just get a blank screen when U put the power cable in. I just get a solid red light in the RPI4, so I'm guessing its reading the SD card correctly now and its just the connection to the screen (correct me if I am wrong)?
Im using an LG TV screen which i also use for my Nintendo Swtich, could this be the problem?
Any help is greatly appreciated,
Looking forward to getting it all sorted and trying new things with the Raspberry Pi
Thanks a mill
I have also noticed that for different Raspberry Pi and monitor combinations a different set of resolutions are shown. I have also noticed that not all of the shown resolutions will work when selected. If the new selected resolution does not work correctly not selecting OK will cause the resolution to revert back to the previous one. One time I mistakenly selected OK when the new resolution was not compatible. Shutting down and rebooting returned the PI to a working resolution.mors3 wrote: ↑Wed Oct 02, 2019 6:02 pmQuick update to this that might help someone.
I'm lucky enough that in my house I have a few different screens/monitors, so after verifying that the Raspbian Buster image I was writing was ok (sha256 hash check) and the green flashing light was doing what it should (with no card solid on for a couple of seconds, then off/on/off/on/off/on/off/on then off, with sdcard in lots of quick green flashes for a couple of minutes, then just the red light, indicating the computer had booted normally and was now just waiting for the user to do something interesting) I was confident that the Pi was working ok, but the screen simply couldn't display what the Pi was telling it to.
So I took the Pi off to a monitor that was reasonably high definition (better than 1080p, so will display higher than 1920 X 1080) and it then worked perfectly.
So to properly solve it I then enabled VNC (using the Raspberry Pi Configuration application in the main menu -> preferences, then go into the Interfaces tab).
I shut down the Pi, moved it to the screen I wanted to use it with, plugged it in and booted it up.
Still a black screen, as expected.
I then used another computer with VNC Viewer, connected it to the Pi and I can see the desktop, (little bit eerie, if a pixel is being displayed on the wire but not on the screen, does it truly exist?).
I then went into Screen Configuration in the main menu -> Preferences and selected the HDMI-1 display (as my HDMI cable is plugged into the port closest to the USB C power port, which is HDMI port 1).
Then go into the Configure menu, down to Screens, pick your screen (I only have HDMI-1 as that's the only screen connected), then into Resolution and set it to something low (I set mine to 800 X 600) and press the green tick icon on the toolbar to apply the change.
(If the screen suddenly wakes up for you, then this will be the way to solve it)
Keep going up in resolution and applying the change until the screen goes black again, and when it does just select cancel to revert to the last size you were on (the one that worked before you selected a resolution that was too high for the monitors capability).
This was the quickest, easiest way to test and get this running for me, you may find a neater way
As a final thought, as I said I've a few screens I could test this with in my home, and the one that was fine from the get-go was a simple monitor, the others were ones with multiple inputs so I have a suspicion that it may be something to do with the way that the Pi asks the screen what it's capable resolutions are and if its a normal screen it's quite explicit, but a screen that's designed to be connected to a wide variety of different types of inputs is a lot more flexible, so the Pi throws it's hands up and shouts 'FINE! I'm going to display at 1366 X 768 then cos that's my favourite resolution!' and the screen is just sad.
Code: Select all