Take the 2-minute tour ×
Raspberry Pi Stack Exchange is a question and answer site for users and developers of hardware and software for Raspberry Pi. It's 100% free, no registration required.

I've just got my raspberry pi.

When I first tried, everything went on well, I got the image on me TV and I tried to set wireless connections.

But when I was trying, the screen suddenly displayed "no signal", I tried to reboot(just cut the power off)my pi but it didn't work. I tried several other times and checked the connections, but they seemed all good.

Later I searched on the Internet for the solution. I tried some but nothing worked.

Now as I give the pi the power supply. The PWR light goes steady red and the OK light flashes green for a while and then goes out. No other signals at all.

I really need some advice, how can I get image on my TV again? Do I need to change other settings or am I simply better to buy another pi or another HDMI cable? Any idea or solution is really welcomed and appreciated!

PS: I can see the dim ACT light flashing

share|improve this question
    
please, try to reverse the HDMI cable, connect the end that went into the TV to RasPI and vice versa, might solve this problem. –  lenik Jun 30 '13 at 9:00

3 Answers 3

I would suggest you to re-flash your SD Card(i.e your OS).There are chances that the one/more of your vital OS files got corrupted,resulting into your Pi unable to detect any valid OS(statup problem).

The no-signal is a consequence of the above problem.....Hope you get to use your Pi once,you re-flash it again.

N.B: In-case you purchased a pre-loaded SD Card....here are the steps to do it again yourself.

Assuming you have a linux box handy.............

  1. Download your favorite Raspberry Pi OS image from here.
  2. Insert the SD card into a linux box.
  3. Open terminal, and execute $df -l
  4. You get a list of all storage devices connected to the computer, try to deduce your SD card from its size/name.

    Eg: /dev/mmcblk0

  5. To re-flash the SD card,we need to unmount it,this way:

    $umount /dev/mmcblk0

  6. Assuming your pwd[present working directory] has the OS image,execute the following command.

    $dcfldd bs=4M if=.img of=/dev/mmcblk0

    Note: This process may take several minutes,any interruption may result in SD becoming corrupted.

7.Now, you have a re-flashed SD card,slide into your raspberry, and hope this gives you smile in your face,

share|improve this answer

My initial start-up 'problem' with my new Pi was No Screen Image - this simply turned out to be the HDMI cable connector not fully fitting into the Pi socket because I first fitted the Pi into an RS box bought to protect the Pi. Without the box everything worked: once I'd doctored the male connection (cut back the plastic encapsulation a tad) it all worked fine when back in the box. As a general rule - To succeed in life you need good connections.

share|improve this answer

Strangely enough I had this same problem last Wednesday. I at first thought it was the HDMI, as realistically no signal means not, "No connection" (check signal wire - bad cable) but means no data/no signal (bad send/no send).

Thinking I destroyed my pi while transporting it, I tried reposting the pi, checking the disk image, checked solderer connections, power usb in, even swapped the HDMI cable. I didn't have the luxury of testing with a volt meter or changing my display.

In the end, I found by wiggling the connection for the power input caused the screen to spark a rainbow colour and made the HDMI connection connect.

My untested theory is that: perhaps that when underpowered, the HDMI cannot fully enable, or otherwise provide enough power to operate a successful connection. Leading to a "No Data/No signal"

I tested this on another pi, and got the same results.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.