Is the script set to executable (+x) in the image?
This is typical for scripts that are presebt but not running, and often
overlooked.

Maddes


On 20.03.2010 04:02, Otto Solares wrote:
> It works on squashfs but didn't on pure jffs2 which I pressume was our
> only environment difference.
> 
> The logcat diff between jffs2 and squashfs seems to be:
> 
> +user.info sysinit: Trying to fix trx header in firmware at 0x20...
> +user.info sysinit: New crc32: 0x407d9371, rewriting block
> +user.info sysinit: Done.
> +user.warn kernel: jffs2_scan_eraseblock(): End of filesystem marker found at 
> 0x0
> +user.warn kernel: jffs2_build_filesystem(): unlocking the mtd device... done.
> +user.warn kernel: jffs2_build_filesystem(): erasing all blocks after the end 
> marker... done.
> +user.info sysinit: copying files ... done
> +user.info kernel: mini_fo: using base directory: /
> +user.info kernel: mini_fo: using storage directory: /jffs
> 
> Obviously it's not running on pure jffs2 images but it seems to me a
> bug in the firstboot scripts unrelated to your patch...
> -
>  Otto
> 
> On Fri, Mar 19, 2010 at 08:12:24PM -0600, Otto Solares wrote:
>> Rechecked and yes, I'm using your latest patch and at boot the file
>> /lib/firstboot/25_fixtrx is there but next boot "lose" the firmware.
>>
>> BTW I'm just using pure jffs2 image, will test squashfs and let you
>> know.
>> -
>>  Otto
>>
>> On Sat, Mar 20, 2010 at 02:27:29AM +0100, Bernhard Loos wrote:
>>> Are you really sure, you used the second patch I posted and the
>>> firstboot script is included in the image?
>>>
>>> 2010/3/20 Otto Solares <[email protected]>:
>>>> On Fri, Mar 19, 2010 at 06:34:03PM -0600, Otto Solares wrote:
>>>>> On Fri, Mar 19, 2010 at 11:25:40AM -0600, Otto Solares wrote:
>>>>>> On Fri, Mar 19, 2010 at 04:53:34PM +0100, Bernhard Loos wrote:
>>>>>>> Does this happen directly after flashing or only after a reboot?
>>>>>> After the first reboot.
>>>>>>
>>>>>>> If openwrt does come up at least once, could you run "mtd -o 32 fixtrx
>>>>>>> firmware" and give me the output?
>>>>>> Yes, it comes up once and for the next reboot/power-cycle it "lose" the
>>>>>> firmware and waits for a TFTP firmware.
>>>>>>
>>>>>> I'm not near this new WRT160NL so I'll send you the output later.
>>>>> r...@openwrt:~# mtd -o 32 fixtrx firmware
>>>>> Trying to fix trx header in firmware at 0x20...
>>>>> New crc32: 0x73ea777a, rewriting block
>>>>> Done.
>>>> FYI after this command it always boots fine now.
>>>> -
>>>>  Otto

_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to