Raspberry Pi Model B+ 512MB Support.

[pilotgary]

I've just received a new Model B+. I tried the new 1.0.3 release, but only got a blank screen. When I put the card in a original model B everything is working fine.

[diederikdehaas]

You mean that it doesn't start the installer at all? If not, could you be more specific as to when it fails?
The more details you can provide, the better I can try to troubleshoot it.
But since I don't have a B+, I can't test for it myself.

[pilotgary]

The screen stays black and only the power light is on. The network activity lights stay off. After a while the screen's power saver kicks in.
I installed the Wheezy 20-6-2014 image on the card and that has booted fine on the B+.
Adafruit (https://learn.adafruit.com/introducing-the-raspberry-pi-model-b-plus-plus-differences-vs-model-b?view=all) reports that a new kernel image is needed to support the USB/Ethernet chip, so I suspect that may be the issue.
I'll be happy to test anything if needed.

[diederikdehaas]

Some ppl have reported that a newer firmware/kernel fixed their problem with the B+ and since nothing powers/lights up, my first guess is the firmware.
So what happens if you get the following files from https://github.com/Hexxeh/rpi-firmware and replace the ones on the sd card with the downloaded ones?

bootcode.bin
fixup.dat
fixup_cd.dat
fixup_x.dat
start.elf
start_cd.elf
start_x.elf

[pilotgary]

It appears to be working. It has started an install of "jessie" with no problems so far. I'll give you an update on how things went later. Thanks for your help.

[diederikdehaas]

Awesome 👍

[pilotgary]

The installation has finished. There where a load of warnings of packages that had been unpacked, but never configured and a "failed to create hard link '/boot/initrd.img-3.12-1-rpi.dpkg-bak' => '/boot/initrd.img-3.12-1-rpi' : Operation denied, but I've seen those before installing "jessie" on an old model B.
After the reboot the screen was all black again, but I took the card out, copied the newer firmware files back into /boot and when I powered it back up it was working perfectly.

Thanks for your help. You've got to love those quick fixes.

[diederikdehaas]

Those warning are caused by a newer version of one of the installation components and are expected and harmless. Dunno why it's outputting these now and I should probably update the README to mention it.
Good to know that it's indeed the firmware files which are causing the issue, thanks for reporting back 👍
I will try to get the bootloader package updated in the raspbian archives so that it works for B+ model without this 'hack'.

[diederikdehaas]

Reopening the issue, since it doesn't work 'OOTB' and an open issue is far more likely to be found by ppl running into the same issue.

[diederikdehaas]

Raspbian bug filed: https://bugs.launchpad.net/raspbian/+bug/1344822

[diederikdehaas]

Fixed with the release of version 1.0.4