-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firmware needs to be updated. #415
Comments
When the installation fails, it writes a log file to I'm not aware of RPI 2 B+ that won't boot though. It might be that newer batches use a different hardware config, but I'd be surprised if that were the case. |
I'm using the latest v1.0.8.1 installer.
|
This:
...seems to indicate that the RPi does not have access to the internet.
|
Yeah I know, but that's not the actual issue. My router configuration is perfectly fine. That the installer even boots on the new Pi is due to my efforts of replacing some files with newer ones from the firmware repository. But since I don't have a clue what I'm actually doing it's a wonder that my modified installer even booted. I'm 100% sure the not working ethernet is a result of my experiment. As @diederikdehaas said Is there some kind of serial number on my Pi I can provide to find out which batch it is from? Or the production date? |
I know it sounds silly, but it sounds like you have a Pi3, not a Pi2. |
@Mausy5043 give you the exact cause (IMO) of the failed installation. For verifying the gpg keys, it needs the proper time and that seemed to have failed with you. Hence the message: @kpfleming's remark makes a lot of sense too as you'd need newer firmware for the Pi3, but (likely) not the Pi2. And if you bought the Pi's not too long ago, it seems more likely you'd get a Pi3 than a Pi2. |
@kpfleming It is definitely not a Pi3. But I might have caused a bit of confusion when I merged two models together: I have a new I also checked it again: The installer boots on the Pi I ordered in 2015 (also a B+), but doesn't boot on the Pi I ordered this week. Same model, same engraving, same SD-Card, same installer. |
Can you post the full output of |
Ups, sorry. Missed that. There you go:
|
That does indeed look like a new revision of the board :-/ Damn 😞 |
The |
Yep, Pi 1 B+. Single Core board.
This is a fresh raspbian lite installation btw. |
This is rather shocking to me ... comparing your data with my 'old' RPi 1B+:
Notice the difference (apart from kernel/gcc version and Serial)? 😞 (and apparently it also has hardware java support) |
|
My wording was rather poor, but I tried to say that :-P |
@lukasma : Could you try building the installer from the |
The solution I had in mind was indeed applying the kernel-4.4-support PR to v1.0.x |
See debian-pi#415 (comment) for details.
* Enable DeviceTree for all Raspberry Pi models. While DT was (too) new in kernel 3.18 it is working properly in kernel 4.4+, so re-enable DT for all Pi's. * Added rpi3 section to the installer's config.txt. Kernel and initramfs are the same as for the rpi2, but to enable the serial console, we need to specify 'enable_uart=1'. * Changed detection of rpi hardware version to be based on Revision value. The Hardware field of /proc/cpuinfo doesn't allow us to differentiate enough, while the Revision field does, so switch to that. * Update various case statements to deal with value '3' for hardware_versions. While the new detection statements also detect other versions (cm, 0), let's deal with that when the need arises. * Added another revision number for RPi 1. See #415 (comment) for details. * Added RPi 3B to the README as supported device.
I've applied the kernel-4.4 update to the v1.0.x branch and I've uploaded the resulting images here: If you could test whether that works for you, that would be appreciated. |
Yes I will test it. |
Done. It wasn't a direct link, but a pattern, but the way I had posted it it rendered it as a (direct) link. |
Yup did that in the end. I thought * was a pattern to be replaced with 8.1 to get version 1.0.8.1 ^^ |
And it is booting and installing :) Passed the step where it faild last time (validating release). Will look for errors but can't imagine it will fail now... |
Great 👍 |
It worked :) Thanks!! |
Changes have been merged, thus closing the issue. |
Hi,
I think some files need to be updated in order to make the installer work properly again. Here is what I observed:
I got a fleet of RPI 2 B+ models. I use the ua-netinst with a costum script to set up a Raspbian installation that fits my needs on every new PI. Yesterday I got a new B+. But when powering it up, nothing happend. Instead the ACT LED flashed eight times. This means ´SDRAM not recognised. You need newer bootcode.bin/start.elf firmware.´. It seems that they ship new B+ models which are not able to work with older firmware.
To solve this issue I just overwrote bootcode.bin, start.elf, start_cd.elf and start_x.elf with the corresponding files from https://github.com/raspberrypi/firmware/tree/master/boot. At least it is booting know, but still not installing becasue it can't validate the release.
Can someone confirm this issue?
The text was updated successfully, but these errors were encountered: