Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upCan't netboot on Raspberry Pi 1 and 2 with the lastest firmware #935
Comments
popcornmix
added a commit
that referenced
this issue
Feb 2, 2018
See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=195178 firmware: arm_loader: Distinguish multiple turbo users power: Used cached values for reads See: Hexxeh/rpi-firmware#165 firmware: dtoverlay: Use SUDO_USER in -pre and -post scripts bootcode: Fix network booting on Pi1/Pi2 See: #935
popcornmix
added a commit
to Hexxeh/rpi-firmware
that referenced
this issue
Feb 2, 2018
See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=195178 firmware: arm_loader: Distinguish multiple turbo users power: Used cached values for reads See: #165 firmware: dtoverlay: Use SUDO_USER in -pre and -post scripts bootcode: Fix network booting on Pi1/Pi2 See: raspberrypi/firmware#935
|
Today's firmware release contains a patch that should fix this issue. |
|
Thank you for your so quick response! I really appreciate it! I confirmed it's now fixed, so closing. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the latest firmware 58395c1, Raspberry Pi 1 and 2 fail to netboot, but Raspberry Pi 3 does. With the previous firmware 80e1fbe, all the models netboot correctly.
tftpd log when netbooting succeeds:
tftpd log when netbooting fails:
When netboot fails, ACT LED flashes 7 times, which means "kernel.img not found". Actually, the pi doesn't load kernel.img after loading start.elf and fixup.dat. So start.elf and/or fixup.dat got something odd between these commits...?
Specifying
start_x=1orstart_db=1inconfig.txtdoesn't solve the problem.Could you solve this issue?