Thank you, Jonathan. I should note that r33202 boots fine for me on
ar71xx, if that helps narrow down a root cause.
On Fri, Aug 24, 2012 at 12:15 PM, Jonathan Bither wrote:
> When I rebuilt the other day my ar2315 would not boot due to jffs2 errors. I
> haven't checked to see if it was somethin
When I rebuilt the other day my ar2315 would not boot due to jffs2 errors. I
haven't checked to see if it was something in my tree, but just thought i'd let
you know. I can rebuilt with a clean true today and watch serial to see if the
issue persists.
On 08/24/2012 01:02 PM, Ben West wrote:
>
My problem is likely unrelated, but could you (Tobias) say precisely
what revision of trunk you are using?
Freshly compiled trunk r33202 w/ default config does not appear to
boot at all on my OM1P (ar2315 chipset), i.e. no response on eth0.
However, I don't think the bugs mentioned w/ compat-wirel
Tobias Diedrich wrote:
> This patch tries to fix this (but is probably wrong :))
> After applying this patch "iw phy phy0 info" looks good, but
> WiFi Analyzer on my phone still shows a very weak signal for the AP.
>
> Until I do this:
> root@OpenWrt:/# iw phy phy0 set txpower fixed 0
> root@OpenW
Compiling OpenWRT from trunk, I've found that there are issues with
setting txpower on AR2417:
- No txpower setting in LuCI gui
- iw phy phy0 info shows 0dBm for all channels regardless of regdomain
[9.332000] cfg80211: Calling CRDA to update world regulatory domain
[9.34] cfg80211: W
