Re: [OpenWrt-Devel] ramips eth tx timeout
Hi! On 17/07/12 11:22, Florian Fainelli wrote: > Transmit timeouts are really a bad situation, I'd rather check where they do > come from, maybe your transmit path is locked for too long, or you are > loosing > transmit completion interrupts? Ethernet generally works stable and well on all Rt3xxx boards I got here for testing. But all of them show the same behavior which I now managed to reproduce reliably: Step 1: change the ip interface of bridge interface which includes eth0.1 Step 2: /etc/init.d/network restart Step 3: upon the first few packages trying to cross the interface, I get the transmit timeout. This applies to all Rt3050, Rt3052F, Rt3350, ... systems. Any idea? I don't remember this was a problem half a year ago when I last built a firmware for an Rt3350 based device... Any idea what could have introduced this? Cheers Daniel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT54g / b43 / mac802.11 BREAKTHROUGH
> What chip is in your WRT54G? We tested both: 4318 (Buffalo HP54G) and 4306 (Linksys WRT54GL) bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT54g / b43 / mac802.11 BREAKTHROUGH
> > 1) why does a band change (can be seen through minstrel) is a
> problem?
>
> Because IIRC b43 doesn't support anything other than 2.4GHz at
> all.
8-) sorry, i used the wrong term "band":
(fast) changing between b and g rates are the problem.
you can easily reproduce, when you force this by:
iw dev $WIFIDEV set bitrates legacy-2.4 11 12
("use only b-rate 11 and g-rate 12")
So minstrel will happily change/try both, wifi will stop.
The same with:
iw dev $WIFIDEV set bitrates legacy-2.4 5.5 6
bye, Bastian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
