Raspi will not boot - HELP NEEDED (solved )

[drupopuppis]

Help anyone....I am lost....can't get my raspi to boot anymore.
All right, here is what happened!
Yesterday I have downloaded the new 2012-08-08-wheezy-armel.img and burned into my 2gb SD card where previously I was running 2012-06-18-wheezy-beta.img. After burning my raspi booted fine and I spent the all night on coding, (or trying to). Turned off the machine and went to bed. Today, same time same place I try to boot the raspi and I get a red led steady on and a random green flashing led, no booting!

I have tried unsuccessfully,

1- a different power supplier, (from 5v 0.7 a to 5v 1.2 a)
2- Unplug all peripherals
3- Set the monitor to accept video from HDMI source
4- Reinstall previous OS

Still nothing.......I have now only have the red led steady on ....... still no booting.

My SD card and power supplier have both worked fine since August when I first got the raspi so I doubt this is the case for the fault.
The sd card was burned using ImageWriter on Linux Ubuntu as it was previously with the old OS.
If anyone has a clue on what could have gone wrong and what can be done that would be great, I have already spent hours of my time and didn't get the raspi to work.....frustrations level are higher than the usual....

Thank you all for your time

[Burngate]

Red led on => power reaching the Pi, though not verified to be adequate
random green flashing => Pi at least trying to read SD card

Since you explicitly say you set the monitor to accept HDMI, I assume you don't get the splash screen, so it would seem your Pi isn't loading the firmware - bootcode.bin, then loader.bin then start.elf is the order I believe, and start.elf is the actual works.

Can you read the SD card on your Linux machine? Has it got the usual files - bootcode.bin, loader.bin, start.elf at least to get to the splash screen, and kernel.img for Linux with optional config.txt and cmdline.txt - and are they at least vaguely readable? If so, it would tend to mean the card isn't at fault.

[obcd]

If you have the Pi connected to a network, you could check if it receives a dhcp addres or if it's pingable.
This would prove that the Pi is still working, but just isn't showing a picture anymore.
If your pi ssh server is turned on, you should be able to connect to it with a program like putty as well.
Most video related issues can be tweaked in the /boot/config.txt file. You can check the eLinux website about video troubleshooting and possible settings in that file. I believe the latest firmwares have CEC support, and maybe that's where things go wrong. You can override those settings in the config.txt file.

[pluggy]

If you put the SD card back in the Linux PC, can you read both partitions and does it have a convincing files structure on it ?

Already been mentioned by someone else but its a good place to go......

[drupopuppis]

Hi all,

Thank you for all your reply, really appreciate that.

I have attached screenshots of my sd card partitions as read from my linux machine, all files seem to be there. What really puzzles me is that I revert back to the old OS so the update issues, (as reported from many more users), should not count any more, indeed I am not able to boot even with the old OS. Still I am using the same power supplier that I was using before and I have not added any peripherals such as usb hubs or anything else that might require more power to run.

[drupopuppis]

If you have the Pi connected to a network, you could check if it receives a dhcp addres or if it's pingable.
This would prove that the Pi is still working, but just isn't showing a picture anymore.
If your pi ssh server is turned on, you should be able to connect to it with a program like putty as well.
Most video related issues can be tweaked in the /boot/config.txt file. You can check the eLinux website about video troubleshooting and possible settings in that file. I believe the latest firmwares have CEC support, and maybe that's where things go wrong. You can override those settings in the config.txt file.

I am afraid it was not set-up to Be Network attached, so I can't get hold of it in anyway. The SD card is the same as before when it was running fine, I have just formatted and rewritten the OS as I have done few more times in the past using my linux machine. Still wondering what went wrong. Obviously I don't have another power supplier with higher amp output to try, I will try a different sd card just now and see what happens.

[drupopuppis]

BREAKING NEWS..!

The raspi has come out from the "coma". After puchasing a different card, (SDHC 4gb), burning with the usual tool from ubuntu, (ImageWriter),....Bingo....I am back on the game.....although I have lost hours of work........

As for the suggestion of attaching the raspi to the network...mmhhhh interesting indeed......anyone has a link to a good tutorial?

By the way, I thank you all for the kind support..!

[W. H. Heydt]

BREAKING NEWS..!

The raspi has come out from the "coma". After puchasing a different card, (SDHC 4gb), burning with the usual tool from ubuntu, (ImageWriter),....Bingo....I am back on the game.....although I have lost hours of work........

As for the suggestion of attaching the raspi to the network...mmhhhh interesting indeed......anyone has a link to a good tutorial?

By the way, I thank you all for the kind support..!

Pi systems are set up to use DHCP. Just run a CAT-5 cable from your router, switch, or hub to the Pi and it should be on your LAN. Some distros, such as Raspbian have ssh daemon running by default. Looking at your DHCP host (usually a router) should show you the Pi and you can get into it from any machine with an ssh client on it.

[drupopuppis]

BREAKING NEWS..!

The raspi has come out from the "coma". After puchasing a different card, (SDHC 4gb), burning with the usual tool from ubuntu, (ImageWriter),....Bingo....I am back on the game.....although I have lost hours of work........

As for the suggestion of attaching the raspi to the network...mmhhhh interesting indeed......anyone has a link to a good tutorial?

By the way, I thank you all for the kind support..!

Pi systems are set up to use DHCP. Just run a CAT-5 cable from your router, switch, or hub to the Pi and it should be on your LAN. Some distros, such as Raspbian have ssh daemon running by default. Looking at your DHCP host (usually a router) should show you the Pi and you can get into it from any machine with an ssh client on it.

Amazing......I did not know this......I am not sure I will be able to do all that...but I am definitely interested.....so let me get it right, if I'am hooked to the router via cat5 cable and the PI is on, even without connecting my monitor to it I can still type the ip address of the PI from my linux machine and get access? Or maybe I went to far?

[ghans]

Yes. This is called running a "headless" server. (If you wanted to know )

ghans