This problem has been resolved?
Thanks
Are you sure it's firm ware and bit the install. I had the same issue when using the xbian installer for windows. I switched to using win32 disc imager and the base image. It worked straight away
I have the same problem.
Bought the Pi at RS. Build date: 1320. Label on the back says E2713RS2V13B1.0
did any of you with this new RPi actually tried what was mentioned ??? as without this info it would be impossible to help, unless someone wants to donate the newest RPi to our devs team
(21st Aug, 2013 07:18 PM)rikardo1979 Wrote: [ -> ]did any of you with this new RPi actually tried what was mentioned ??? as without this info it would be impossible to help, unless someone wants to donate the newest RPi to our devs team
I tried to do the firmware update mentioned here, but don't know how...
When I use the Xbian windows installer (or the image), there is no /boot folder on the SD card.
If I just copy all the Hexxeh files to the SD, the SD card is too small.
I'm open to suggestions on how to get it working, without you having to make changes to Xbian itself.
(21st Aug, 2013 10:23 PM)brantje Wrote: [ -> ]Can it be this?
Not the same RAM chip but same issue. I cannot find any information on the Marvell chip in these new rev Pi's.
I'm going to mail Dom from the Pi Foundation and see if I can get to the bottom of this.
Is there a way to tell if the "Samsung/Hynix" chip is installed by a software command? If not, it's going to be difficult
One assumes the firmware will be downwardly compatible and eventually will make it into ... say Beta 2.
I also think the main Xbian download page needs to be modified to mention this and possibly add a route to a fix.
(21st Aug, 2013 11:47 PM)f1vefour Wrote: [ -> ] (21st Aug, 2013 10:23 PM)brantje Wrote: [ -> ]Can it be this?
Not the same RAM chip but same issue. I cannot find any information on the Marvell chip in these new rev Pi's.
I'm going to mail Dom from the Pi Foundation and see if I can get to the bottom of this.
I don't think this is a marvell chip - the logo is different
Marvell chip and they specialise in processors, not ram.
It's a Crucial chip - or better known as Micron
Micron Chip logo
Here she is
Micron D9HQN
Have the Chinese tried to pull a fast one :-)
From Dom:
Dom Wrote:by dom ยป Sat Jul 27, 2013 10:35 am
We need to use the data sheet for a specific sdram device and detect that device (from a manufacturer and device code) to detect size, and configure rows, columns and various timings.
Behind the scenes there are continuous negotiations going on for all the components that make the Pi. If a new sdram vendor comes in and offers to undercut the existing vendors,
or if lead times are too high, or volumes available are insufficient then using a new sdram device will be considered.
When a new sdram part is used, we need to update bootcode.bin and start.elf, as older firmware won't work on it.
We were under the belief that NOOBs and the other distributions supported the Micron sdram, but it seems a mistake was made on raspbian, which needs an update.
Newest firmware should fix the issue.
Good work IriDium on finding out it was a Micron chip and not Marvell.
I knew firmware would need an update but wasn't sure about the kernel.
Mystery solved.
@
mk01
I would pull Doms' git and hot fix the latest available Xbian image with the latest Pi firmware.
I gave it another shot with copying the Hexxeh files to the SD card.
The first time I used the windows installer and chose Xbian Beta 1.1. The copied the files to the SD card.
When powering on the RPi, ACT blinks 1 long time. Screen stays black with a non blinking cursor in the top left corner.
I then gave it another shot with Xbian Beta 1.0 (and copying the files). Same thing happens.
Now, when I use Xbian Alpha 4 (and copying the files), it does some completely different things!
Text starts to roll down like it is doing its job like it's supposed to. It Expands, Reboots, goes black, boots, blinking cursor in top left, and then gives a black screen (no non-blinking cursor either). LNK keeps blinking.
While doing all it's stuff, it does give an error:
could not insert 'snd_bmc2835': exec format error
I have here one of the first Rpi's bought in February 2012 and one I bought yesterday. The same SD with Xbian does run on the original rPi but won't boot on the newest.
OK, thanks.
That did the trick!
Btw, these files where at the root, not in /boot.
(24th Aug, 2013 04:59 AM)Lampje Wrote: [ -> ]OK, thanks.
That did the trick!
Btw, these files where at the root, not in /boot.
They go in /boot, when you open the SD in Windows you only can see what is /boot.
Thanks for letting me know it worked.