Skip to content
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

Can't netboot on Raspberry Pi 1 and 2 with the lastest firmware #935

Closed
Terminus-IMRC opened this issue Feb 1, 2018 · 2 comments
Closed

Can't netboot on Raspberry Pi 1 and 2 with the lastest firmware #935

Terminus-IMRC opened this issue Feb 1, 2018 · 2 comments

Comments

@Terminus-IMRC
Copy link

@Terminus-IMRC Terminus-IMRC commented Feb 1, 2018

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:

Feb  1 12:07:52 imrc dnsmasq-tftp[680]: file /netboot/boot/autoboot.txt not found
Feb  1 12:07:52 imrc dnsmasq-tftp[680]: sent /netboot/boot/config.txt to 192.168.20.103
Feb  1 12:07:52 imrc dnsmasq-tftp[680]: file /netboot/boot/recovery.elf not found
Feb  1 12:07:54 imrc dnsmasq-tftp[680]: sent /netboot/boot/start.elf to 192.168.20.103
Feb  1 12:07:54 imrc dnsmasq-tftp[680]: sent /netboot/boot/fixup.dat to 192.168.20.103
Feb  1 12:07:54 imrc dnsmasq-tftp[680]: file /netboot/boot/recovery.elf not found
Feb  1 12:07:54 imrc dnsmasq-tftp[680]: sent /netboot/boot/config.txt to 192.168.20.103
Feb  1 12:07:54 imrc dnsmasq-tftp[680]: file /netboot/boot/dt-blob.bin not found
Feb  1 12:07:54 imrc dnsmasq-tftp[680]: file /netboot/boot/recovery.elf not found
Feb  1 12:07:54 imrc dnsmasq-tftp[680]: sent /netboot/boot/config.txt to 192.168.20.103
Feb  1 12:07:55 imrc dnsmasq-tftp[680]: file /netboot/boot/bootcfg.txt not found
Feb  1 12:07:55 imrc dnsmasq-tftp[680]: sent /netboot/boot/cmdline.txt to 192.168.20.103
Feb  1 12:07:55 imrc dnsmasq-tftp[680]: file /netboot/boot/armstub.bin not found
Feb  1 12:07:55 imrc dnsmasq-tftp[680]: error 0 Early terminate received from 192.168.20.103
Feb  1 12:07:55 imrc dnsmasq-tftp[680]: failed sending /netboot/boot/kernel.img to 192.168.20.103
Feb  1 12:07:59 imrc dnsmasq-tftp[680]: sent /netboot/boot/kernel.img to 192.168.20.103
Feb  1 12:07:59 imrc dnsmasq-tftp[680]: sent /netboot/boot/bcm2708-rpi-b.dtb to 192.168.20.103
Feb  1 12:07:59 imrc dnsmasq-tftp[680]: sent /netboot/boot/config.txt to 192.168.20.103

tftpd log when netbooting fails:

Feb  1 12:35:38 imrc dnsmasq-tftp[680]: file /netboot/boot/autoboot.txt not found
Feb  1 12:35:38 imrc dnsmasq-tftp[680]: sent /netboot/boot/config.txt to 192.168.20.103
Feb  1 12:35:38 imrc dnsmasq-tftp[680]: file /netboot/boot/recovery.elf not found
Feb  1 12:35:41 imrc dnsmasq-tftp[680]: sent /netboot/boot/start.elf to 192.168.20.103
Feb  1 12:35:41 imrc dnsmasq-tftp[680]: sent /netboot/boot/fixup.dat to 192.168.20.103

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=1 or start_db=1 in config.txt doesn't solve the problem.

Could you solve this issue?

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
@pelwell
Copy link
Contributor

@pelwell pelwell commented Feb 2, 2018

Today's firmware release contains a patch that should fix this issue.

@Terminus-IMRC
Copy link
Author

@Terminus-IMRC Terminus-IMRC commented Feb 3, 2018

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
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.