2014-01-07-wheezy-raspbian.zip does not boot

Bug #1267973 reported by Daniel Bergqvist
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Raspbian
Invalid
Undecided
Unassigned

Bug Description

I have successfully installed "2013-09-25-wheezy-raspbian.img" on my memory card and Raspberry Pi boots fine with it. But when I install "2014-01-07-wheezy-raspbian.img" instead it doesn't boot. I see the red light and the lights for the Ethernet card, but the light for the memory card doesn't lit.

I use Win32DiskImager under Windows 7 to install the image on the memory card. Since I don't have any keyboard or monitor connected to the Raspberry Pi I cannot see any error messages. But I have tried several times to install the 2014-01-07 version and it fails every time, but if I install the 2013-09-25 version it works fine.

I don't know much about the version of the Raspberry Pi, but I know I have a model B.

Kind regards,
Daniel

Revision history for this message
Michael Still (mikal) wrote :

I am seeing problems with 2014-01-07 as well. With a monitor and a keyboard plugged in, I get dumped at a root prompt for a very minimal linux setup straight after the keyboard is detected. This linux setup is a 56mb boot partition. The root partition is not mounted.

Revision history for this message
Attila Rakosi (rakosi2) wrote :

I am getting same. I was running fine on "2013-09-25-wheezy-raspbian.img" but I did a "sudo apt-get upgrade" and never turned on again.

Revision history for this message
peter green (plugwash) wrote :

"I am seeing problems with 2014-01-07 as well. With a monitor and a keyboard plugged in, I get dumped at a root prompt for a very minimal linux setup straight after the keyboard is detected. This linux setup is a 56mb boot partition. The root partition is not mounted."
It sounds like you are getting dumped into the "safe mode", this is supposed to be triggered by placing a jumper but some people seem to end up in it unintentionally.

Try adding avoid_safe_mode=1 to config.txt

In general if things fail this early it's probablly not a raspbian problem and you are likely to have better luck on the forums or on the raspberry pi foundation's github issue trackers.

Revision history for this message
Diederik (didi-debian) wrote :

If this is still an issue, it should be reported at https://github.com/RPi-Distro/repo/issues

Thus I'm closing it as invalid.

Changed in raspbian:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.