Raspbian: dies after config

[Myra]

I've been using a Raspberry Pi since March, first with Debian squeeze, then Debian wheezy, and now I've downloaded the Wheezy raspbian to try out. The problem, briefly, is that after I go through the configuration menu and try to restart it, it doesn't restart.

In detail: I downloaded the Raspbian image via BitTorrent. I got the SD card written, and then inserted it into the Pi. Pi booted up and gave me the configuration screen (which is very nice by the way!). I went through the configuration items, then indicated that I'm finished. It asked me if I want to restart now, I said yes. Then it shut down the computer, then said it will restart, and then the screen went black, and the monitor power light started blinking to show that it has no signal.

Any ideas as to how I can fix this? I've done this process twice now, so it's not just a one-off fluke.

[Jim JKla]

Have you tried reloading your previous image?

[RaTTuS]

what do the lights do ?
does the config.txt file look ok on another machine?

[Myra]

Hmmm, I have finally got a working Raspbian SD image. Third time lucky. This time I just did a couple of things in the configuration setup, and then exited, and didn't reboot straight away. But it would be interesting to track down what went wrong in case someone else has this problem.

Jim: yes, I can use one of my older SD cards and it still works.

RaTTuS: the red PWR light stays on, and the green OK light blinks. I think it is blinking 5 times, then is off for a bit, then blinks 5 times again.

Looking at the config.txt on another machine... Oh, that's interesting... In my working Raspbian, the config.txt has some lines saying:

# uncomment for ccomposite PAL
#sdtv_mode=2

the config.txt on the bad SD card says (when viewed with less)

# uncomment for c^@^@^@^@

with lots and lots of ^@, which are in reverse mode (black text on white background). Obviously some funny characters have crept in there somehow... Something in the configuration setup is doing that, I think. I don't know what, though.

I have edited my configure.txt to get rid of the last few lines (in the working version, the last few lines are all commented out anyway) and tried it again in the RPi. Still the same bahaviour...

I then copied the config.txt from my working version to the bad SD card and tried again. Still the same results. Obviously more than just the config.txt got messed up...

I think at this point I will give up, since I do have a working Raspbian image. It's frustrating, though, that i don't know what caused the problem nor how to fix it...

[PaulCheffus]

I think at this point I will give up, since I do have a working Raspbian image. It's frustrating, though, that i don't know what caused the problem nor how to fix it...

Hi

Try copying the boot partition from the working version to the non working version. I had this same problem when I ran rpi-update which seemed to corrupt some of the boot file but only on my Transcend 8Gb class 10 card.

Cheers

Paul

[Myra]

Paul: Hmmm, interesting observation. My SD cards are Transcend as well, but they are a more modest 4GB class 6. Which file is the "boot partition" that I should copy over? Sorry, despite being a RasPi user for a few months, I'm still no systems expert.

[PaulCheffus]

Paul: Hmmm, interesting observation. My SD cards are Transcend as well, but they are a more modest 4GB class 6. Which file is the "boot partition" that I should copy over? Sorry, despite being a RasPi user for a few months, I'm still no systems expert.

Hi

If you put the card into a reader on a windows pc the only files you can see are the ones in the boot partition. There will be files called arm192_start.elf, arm240_startelf, etc. I replaced them all from a different card that I had already updated successfully (Kingston 8GB Class 4).

You should be able to get the files from here
http://elinux.org/R-Pi_Troubleshooting# ... re_version

Cheers

Paul

[Myra]

Paul: nope, even that didn't do it. Shame... Well, I can always just rewrite those SD cards that didn't work.