|| On Wed, 18 Oct 2006 21:06:04 +0200 || Waldemar Brodkorb <[EMAIL PROTECTED]> wrote:
wb> One idea is, that you have choosen a configuration in menuconfig, wb> saved it and then switched to another filesystem or target device wb> afterwards. I am not sure I understand this entirely yet. When doing SVN checkout and then configuring it for the first time, I left the file system on default (writeable root) and only changed the device to the ASUS WL-500gP. It is possible that in later attempts I was playing with those settings, too, but it seems odd that selecting a menu option and recompiling should break things in such a fundamental way. But it seems that problem is solved now, so it should no longer be a problem. wb> After that your compiled image will be broken. This ugly behavior wb> is fixed in the latest svn version. I think I committed the wb> changes on Tuesday in the late evening. Hm. So they should be in there now. I'll try again today, then. wb> I use FreeWRT stable branch on at least 5 Asus WL500gP devices wb> without problems. Last time I had major problems was exactly wb> after I changed the filesystem without removing ".config" before. Ah. wb> If you change from OpenWrt to FreeWRT you always should use mtd wb> to update the system in flash. Otherwise FreeWRT might try to wb> mount an existing JFFS2 partition with startup scripts which do wb> not work. Ah. Now that is a thing that hadn't occured to me before. wb> Use following command: wb> # mtd -r write freewrt-xx.bin linux I followed the instructions from the Wiki carefully (having bricked one router before I did not feel like repeating the experience) and I am quite sure that it said I should convert to trx before trying mtd. Now it does not say that anymore, and it seems the change was made by you about 3 minutes ago. Funny. Okay, I'll try that. wb> There is one other possibility to get access to the FreeWRT [...] wb> FreeWRT will send one UDP package to your connected client to wb> signal that you can push the reset button. If you push the button wb> at the correct time, FreeWRT will go into failsafe. Ah, this is familiar, although I remember that OpenWRT had an issue to recognise the reset button on the ASUS WL-500gP. Has FreeWRT resolved that issue? wb> But there is still one situation, where it does not help. In case wb> there is an old partition the kernel use to execute the "nvram" wb> binary (in preinit.arch), failsafe can not be reached. wb> So in short: wb> - remove .config wb> - svn up wb> - build a new image wb> - install original firmware via tftp wb> - use the webinterface to install the new FreeWRT image Okay. I will try this. Thanks a lot for your help. Regards, Georg -- Georg C. F. Greve <[EMAIL PROTECTED]> Free Software Foundation Europe (http://fsfeurope.org) Join the Fellowship and protect your freedom! (http://www.fsfe.org) What everyone should know about DRM (http://DRM.info)
pgpcZr4Bm9hsh.pgp
Description: PGP signature
_______________________________________________ freewrt-users mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-users
