cloud u please show us your wireless config file?

Hi I have E3000 with Tomato running but missing Dual Wan.  Everything running very stable with my setup but would like to try OpenWRT Dual Wan.  What's the difference between razvi build and openwrt trunk build?  How stable are they at the moment?

(Last edited by Almaz on 15 Oct 2013, 02:56)

Sorry, I moved back to the stock firmware as I needed more than the 2Mbyte/s. Try removing/renaming your wireless config and run 'wifi detect'. This should give you config that you can then paste into a wireless config.

Thanks, I get it works using same config that used before for b43.

Back to problem with failsafe. Failsafe on E3000 works for me only with reset button, not with WPS button. Failsafe on E2000 seems like doesn't work at all.

1. Anyone able to get into failsafe using WPS button on E3000 or WRT610Nv2?
2. Anyone able to get into failsafe on E2000 or WRT320N? Failsafe on E2000/WRT320N is implemented in OpenWRT?

https://forum.openwrt.org/viewtopic.php?pid=208815#p208815
perhaps, buttons are jumbled for the other routers.

(Last edited by sash-kan on 15 Oct 2013, 11:38)

Probably. Also E2000/WRT320N is special case:

Source

Can somebody test this ?
http://openwrt.razvi.ro/barrier_braker_asus_rt-n16_svn_r38488/

not work!!

Greetings.
My compilled (and working) r38639 (3 november) of OpenWRT for RT-N16:   http://rapidshare.com/share/DAFD134751328E027DD486ADD8D9BDE0

I tested under RT-N16. Not working. Power LED stays lit always (doesn't go off after switching the router on)

(Last edited by dvb15 on 11 Nov 2013, 14:00)

I have been using openwrt on a wgt634 for quite a while, yesterday I switched to a RT-N16 running openwrt.
I am running r38677 successfully with lan+wlan working.
Still doing some testing and have to recompile with brcmsmac instead of b43.

(Last edited by sam0815 on 8 Nov 2013, 14:36)

I really tested not r38488, but r38554, as it was the last version on 08.11.2013, when I wrote the message.

Another bug: I see, that exfat module v0.9.8-1 has some issue on mounting:

OpenWrt /root # mount.exfat /dev/sdb1 /mnt
FUSE exfat 0.9.8
ERROR: exFAT file system is not found.

Then I installed exfat module v0.9.5-1. It mounted my partition okay. Could you check the issue or revert to 0.9.5 on the next building?

(Last edited by dvb15 on 11 Nov 2013, 14:01)

I've been playing around with trunk on my E2000. Snapshots work fine, but only able to get 11g on b43. Built with propietary wl driver and speeds are good, seems stable but only on very light testing. I've been working on getting brcmsmac working. I've used the following profile to create working images that give me 11n with brcmsmac. YMMV.

#
# Copyright (C) 2007-2013 OpenWrt.org
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#

define Profile/Broadcom-bgmac-brcmsmac
  NAME:=Broadcom SoC, bgmac Ethernet, BCM43xx WiFi (brcmsmac)
  PACKAGES:=kmod-bgmac kmod-brcmsmac
endef

define Profile/Broadcom-bgmac-brcmsmac/Description
    Package set compatible with hardware newer Broadcom BCM47xx or BCM535x 
    SoC with Broadcom BCM43xx Wifi cards using the mac80211 and brcmsmac
    drivers and bgmac Ethernet driver.
endef

$(eval $(call Profile,Broadcom-bgmac-brcmsmac))

cheers

New build
http://openwrt.razvi.ro/barrier_braker_asus_rt-n16_svn_r38780/

I have the same problem,could u please tell me which profile should be replaced?

Heya, I've tried to install from http://openwrt.razvi.ro version r38554 it wouldn't come out boot only in recovery modus I could login to my RT-N16. Tried several methods; tftp, Asus Utility and straight from Tomato none of them worked. So I roled back to version r36828 bammm..... immediately booted fine.

Okay Now i'm running OpenWrt r36828 but the sucker reboots once in a day/ few days. That was the whole reason I moved from Tomato to OpenWrt. In Tomato the reboots on the RT-N16 only happens when enabling QOS. I'm running OpenWrt with QOS too.
I thought well openWrt kernel 3.x with reversed engineered Broadcom-driver would solve the problem.. Hell no symptoms are the same.

I've read about down-clocking the sucker or disabling QOS. Disabling QOS is no option for me. Does this sound familiar to you guys?

neroanelli,

I didn't replace any. I added one using the code snippet you quoted, into a file named 223-Broadcom-bgmac-brsmac.mk.
I added that file at the target/linux/brcm47xx/profiles directory of the build source. Currently, I am having issues getting
kmod-brcmutil to build unless all packages are built, and then I run into issues with rrdtool1 failing to build. But I'm working on it.
Slowly. I'll post when I get things ironed out.

(Last edited by stygian on 16 Nov 2013, 15:01)

I've sorted out the problem I was having with rrdtool1 building and there have been fixups for brcmsmac, so hopefully my build with brcmsmac will be working soon. I've submitting a patch to get rrdtoo1 to build, but it hasn't been accepted yet. If anyone needs it, it's an attachment on ticket #14479.

(Last edited by stygian on 20 Nov 2013, 01:27)

Hi, I noticed that the switch driver has been switch to b53, can I know how to config the vlan id which is greater than 16?

I have a post previously but didn't get any answer.

https://forum.openwrt.org/viewtopic.php?pid=207616#p207616

The old driver file

package/switch/src/switch-robo.c has been removed in below commit:

https://github.com/razvanstanga/openwrt … f6c68df858

(Last edited by jianyu on 7 Dec 2013, 08:28)

Yesterday I hab some time and tried to to get wifi up&running with 300mbit/s on my RT-N16.
I used the brcm-wl but was not able to associate any clients with it (same as with gregd72002).
Under Luci a bitrate of 300mbit/s was shown?!
In post 317 third_eye46 said that he was able to run wifi with 300mbi/s - maybe just 300 being displayed but no connection?
Then I switched back to brcmsmac, which at least is running stable at lower bitrates.
Unfortunately had no time to dig deeper into the wl utility-maybe one can succeed in getting higher bitrates/stable connections with it.

Something else that maybe someone can help me with.
Had reflashed the Asus with the mtd command, but afterwards was not able to reflash with mtd-> mtd -r write openwrt.trx linux ->
always got the message
"could not open mtd device: linux"
Finally I relashed with sysupgrade, but still not able to use the above command...
Any help is welcome.

maybe partition is named firmware instead of linux?

anyway i do not see the point of not using sysupgrade...

cat /proc/mtd gives me:

dev:    size   erasesize  name
mtd0: 00040000 00020000 "boot"
mtd1: 01fa0000 00020000 "firmware"
mtd2: 00000944 00000944 "loader"
mtd3: 001036a0 00020000 "linux"
mtd4: 01e9c000 00020000 "rootfs"
mtd5: 01080000 00020000 "rootfs_data"
mtd6: 00020000 00020000 "nvram"

I was just confused because I used to flash with "mtd -r write openwrt.trx linux" which suddenly didn't work.
Maybe I should have a deeper look at the flash layout, etc.
By the way, is there any difference between flashing with mtd or sysupgrade?

show also the dmesg part where mtd partitions are listed

sysupgrade basically do some tasks in addition to the flashing.. for example it backups and restore settings (unless specified), it checks that the image is for the right model (unless specified), it stops services that could cause problems during flash write.. and so on

anyway.. from the size i guess firmware is linux(kernel only) + rootfs.

(Last edited by nebbia88 on 9 Jan 2014, 14:52)

dmesg output:

[    0.890000] 6 bcm47xxpart partitions found on MTD device physmap-flash.0
[    0.900000] Creating 6 MTD partitions on "physmap-flash.0":
[    0.910000] 0x000000000000-0x000000040000 : "boot"
[    0.910000] 0x000000040000-0x000001fe0000 : "firmware"
[    0.920000] 0x00000004001c-0x000000040960 : "loader"
[    0.930000] 0x000000040960-0x000000144000 : "linux"
[    0.940000] mtd: partition "linux" must either start or end on erase block boundary or be smaller than an erase block -- forcing
read-only
[    0.950000] 0x000000144000-0x000001fe0000 : "rootfs"
[    0.960000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcin
g read-only
[    0.970000] mtd: device 4 (rootfs) set to be root filesystem
[    0.980000] mtd: partition "rootfs_data" created automatically, ofs=0xf60000, len=0x1080000
[    0.990000] 0x000000f60000-0x000001fe0000 : "rootfs_data"
[    0.990000] 0x000001fe0000-0x000002000000 : "nvram"

I guess it has to do with "mtd: partition "linux" must either start or end on erase block boundary or be smaller than an erase block -- forcing
read-only", right?
By the way my image size is approx. 16MB.

as you see from offsets, firmware is (loader+linux+rootfs).

you must flash whole firmware because linux and rootfs are read only (BTW i do not see why one wants to flash only kernel!)

i understand that the naming could have been different.. afaik dd-wrt calls linux the firmware partition