- Mitglied seit
- 17 Feb 2010
- Beiträge
- 225
- Punkte für Reaktionen
- 0
- Punkte
- 0
Today I did a svn up to rebuild Freetz to revision 4965M. I selected an extra package (Polipo) using make menuconfig. I saw there were a lot of new files, so to be sure I did a make distclean after saving the dl folder and the .config file. After restoring the dl folder and the .config I did a make and when it was ready I upgraded the firmware using the Freetz UI. After the usual blinking phase of the info led and the big red flash (without smoke 
) the info led remained blinking twice with a few seconds interval. I had this before and had the device rebooting normally again after ./tools/push_firmware <previous>.image. This time I choose the do a make kernel-menuconfig and to disable Automatic kernel module loading. After rebuilding I did again a make kernel-menuconfig and enabled Automatic kernel module loading again. After the second rebuild I pushed the new, twice rebuilt firmware using ./tools/push_firmware and it worked! So this seem to have to do something with the automatic kernel module loading.
So here is a little recipe to fix this problem (maybe there other, better methods). But I am curious what went wrong exactly and how I can prevent this.
) the info led remained blinking twice with a few seconds interval. I had this before and had the device rebooting normally again after ./tools/push_firmware <previous>.image. This time I choose the do a make kernel-menuconfig and to disable Automatic kernel module loading. After rebuilding I did again a make kernel-menuconfig and enabled Automatic kernel module loading again. After the second rebuild I pushed the new, twice rebuilt firmware using ./tools/push_firmware and it worked! So this seem to have to do something with the automatic kernel module loading.So here is a little recipe to fix this problem (maybe there other, better methods). But I am curious what went wrong exactly and how I can prevent this.
Zuletzt bearbeitet:
