-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
What happened to the build code #293
Comments
I built this on a new machine. |
OK. And now, for the first time ever, after rpi-update my Pi refuses to boot. I have updated code using rpi-update every time it changes to verify wifi drivers I compile work or not work with the new code and this is the first time ever my Pi will not boot. Now trying to find out why. |
I have successfully ran rpi-update and rebooted. Let me know if reverting a file makes it boot. It's possible something is broken on new build machine, or you may have just got unlucky. |
I just ran rpi-update and rebooted remotely. All good. On Thu, Jun 26, 2014 at 1:37 PM, popcornmix [email protected]
|
See: #293 kernel: Set build number back to normal monotonic sequence See: #293 kernel: bcm2708: Avoid hang when timer_set_next_event is called with MAX_INT See: raspberrypi/linux#616 kernel: armctrl: Don't mask interrupts from ack See: raspberrypi/linux@39e4e12
See: raspberrypi/firmware#293 kernel: Set build number back to normal monotonic sequence See: raspberrypi/firmware#293 kernel: bcm2708: Avoid hang when timer_set_next_event is called with MAX_INT See: raspberrypi/linux#616 kernel: armctrl: Don't mask interrupts from ack See: raspberrypi/linux@39e4e12
gpu_mem=16 Before updating it was running 3.12.22+ #691. Copied the boot directory files from another Pi running 3.12.20+ #687 and my broken Pi is running again. So now I'm running rpi-update again. Let's see what happens in a few minutes. OK rpi-update has finished so rebooting. And it is now working. So I guess start_cd.elf was broken then as you've updated the commit. Phew, excellent, thanks for sorting it so quickly. Good to get back to normal. And the build looks good too, #692. well done. |
Okay to close? |
Certainly. Thanks for the quick update |
See: raspberrypi#293 kernel: Set build number back to normal monotonic sequence See: raspberrypi#293 kernel: bcm2708: Avoid hang when timer_set_next_event is called with MAX_INT See: raspberrypi/linux#616 kernel: armctrl: Don't mask interrupts from ack See: raspberrypi/linux@39e4e12
In the latest commit, 4f63c3b, firmware/extra/uname_string shows Linux version 3.12.23+ with build #1 PREEMPT Thu Jun 26 17:26:49 BST 2014.
Should it not be something like #692 or similar. Or has it reverted to #1 because Raspbian is now compiled with gcc 4.8 rather than gcc 4.7?
The text was updated successfully, but these errors were encountered: