Or you could have just read the R-Pi Troubleshooting Guide like I did when fixing the same HDMI problem in just a couple of minutes:sshipway wrote:I've investigated a problem similar to this one for a couple of weeks now.
The Pi outputs a relatively weak HDMI signal. Some devices may not immediately notice the Pi's HDMI or may not do the negotiation.
Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.
You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.
If the display is a computer monitor, use hdmi_group=1 and if it is an older TV, try hdmi_group=2.
Do not set hdmi_safe=1 as that overrides many of the previous options.
Using a shorter or better quality HDMI cable might help.
Make sure your Pi's power supply delivers 1A and not 500mA.
If you see a problem with the red colour - either absent, or interference - then try a boost. However it might simply be that the display requires a stronger signal than the Pi can give.
That wiki page is a load of old junk, because NOOBS hides those things in a different partition.rahult wrote:i refered:
http://elinux.org/R-Pi_Troubleshooting# ... on_display
there is a point:
Check that you have correctly written a Raspberry Pi image to the card by using a MAC or PC and browse for the following files:
start.elf amongst others
i could not find fixup.dat and start.elf files in my image.
plus there isnt any config.txt file too..
Exactly what model of Pi does the "kncminer" (whatever that is?) use - a P2B is not the same as the, albeit similar, B+ and needs an O.S. with upgraded firmware!Robertsthlm wrote:Hi,
So after my initial purchase of the Raspberry Pi Model B (The biggest model, quad core and 1gb ram)
I just cannot make it output anything on HDMI, the microsd card has been swapped and tested on a kncminer that runs a similar raspberry pi, if not in fact identical...
The green ACTivity led behaviour is similar to that for a NOOBS image when connected to a display that isn't compatible with NOOBS' default HDMI setting. If you were/are using NOOBS did you try "hdmi safe mode" by holding/toggling key '2' during boot. (NB. an older NOOBS setup that was originally created for a B+ again will not work on a P2B - you need a current version)The Raspberry pi, Powers up, The green ACT led flashes for 20-30 seconds Before it "quiets down", No signal from my monitor, No signal if connected to the TV (The KNCMiner does output to that TV so there should be no incompatibility issues) The powerbrick has been changed between different ones, Modified D-Link powerbricks 5V 2A, the latest one i found was a huge thing, 5V 3A, but the result is the same.... the board seems to boot normally, but no video. i even purchased a 3.5" touchscreen from Ebay just to make sure there were no issues with the HDMI itself, the screen is just all White and nothing else.
Have you actually tried one of the images from the RPi downloads page? (They all should work with a P2B, images from elsewhere may not have been updated by their maintainers)So tried 2 different Monitors (PC-Monitor and TV)
Tried atleast 5 different Power supplies
Hooked up a custom mini-display that is made just for the Raspberry pi.
No Rainbow-screen. nothing zip nada.
Board seems to boot just nice. No Video..
Tried The Elec-xbmc, the Another xbmc, Some Linux versions........ just about Everything...
Do i need more than one powersource to make this thing output video ?
Or is this really about me trying to boot from an incompatible distribution.. I have really tried most things now except to try to boot from older images and such..
Suggestions people... Anything would be much appriciated.
Users browsing this forum: Google [Bot] and 47 guests