Previous Thread
Tatha,
I believe I have some answers to your questions...
1) Wireless Interface
This is not a bug its a feature. By default OpenWRT will not bring up the wireless interface (sensible IMHO) until the user has correctly configured it. This is a "good idea" it stops a sea of open wireless networks.
Users should edit (on the router):
/etc/config/wireless
2) Wierdness!
The 0xdeadc0de is a magic marker that indicates that the jffs2 partition should be formatted (by the kernel). The boot scripts will not mount the jffs2 partition if it finds the magic (because its not formatted!). Your fix essentially forces the jffs2 partition to be considered unformatted. Result a the ramdisk will be used (note this means that all changes will be lost across a reboot!).
Your problem was that you are attempting to mount a jff2 partition which was not formatted, nor marked (with the magic code) as unformatted. As you found out this has "interesting" effects. I suspect your non-working ethernet was just a side effect of this!
Now I suspect the real cause is that you have built a CHK image without the magic jffs2 marker. The following is the layout of my CHK images:
CHK Kernel:
TRX Part 0: lzma-loader (patched)
TRX Part 1: Linux Kernel
TRX Part 2: squashfs root
CHK Rootfs:
jffs2 format marker (0xdeadc0de)
My suggestion download the OpenWRT WGR614L "Bleeding Edge" Environment. That creates images, at least for me, that work correctly!
RSS
