Joined: 06 Jun 2006 Posts: 7463 Location: Dresden, Germany
Posted: Thu Apr 03, 2014 9:14 Post subject:
ah and one another important note. not all broadcom devices can be supported by brcm3x builds. it simply depends on the cpu features. some mips cpu's are a little bit to old, some are not. mips16e and mips32 R2 support is required _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 02 Jan 2011 Posts: 56 Location: Ostrava, Czech Republic
Posted: Thu Apr 03, 2014 10:02 Post subject: RE
Updated on E3000, K3x version. No issues, both wifi works properly, WDS bridge with another E3000 works as well. _________________ 1 x Asus RT-N18U
1 x Linksys E3000 DD-WRT build 23838 NEWD-2 K3.x mega
1 x Linksys E3000 DD-WRT build 23919 NEWD-2 K3.x mega
1 x Linksys E3000 DD-WRT build 25628 NEWD-2 K3.x mega
ah and one another important note. not all broadcom devices can be supported by brcm3x builds. it simply depends on the cpu features. some mips cpu's are a little bit to old, some are not. mips16e and mips32 R2 support is required
Is there a command to identify the CPU's features?
if the gui does not show linksys e3000 but wrt54g or something like that it simply means that the nvram is screwed up. because the wrt54g string is the default name if the device cannot be detected. an the detection is done by nvram. so the nvram is in inconsistent state and contains wrong values. this may finally also lead to non working wifi
I have the same issue with Asus N12B1 and k3.x builds. Is there anyway to fix it?
if the gui does not show linksys e3000 but wrt54g or something like that it simply means that the nvram is screwed up. because the wrt54g string is the default name if the device cannot be detected. an the detection is done by nvram. so the nvram is in inconsistent state and contains wrong values. this may finally also lead to non working wifi
i think there is something wrong with the detection of E3000 in this build. i upgraded from 21676 K3.X without a reset, it was detected fine. i did a 30-30-30 reset, now it is detected as a wrt54g with wrong / 00 MAC addresses, i flashed several times just to make sure the flash went fine, back to 21676 for now.
* The wifi don't work.
* Olivetti olicard 145 don't work. In /tmp/ppp/options.pppoe the connection are configured on /dev/usb/tts/4 but in the mobile broadband web page the connection should be done with tts5
br0: port 1(vlan1) entering forwarding state
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
drivers/usb/serial/option.c: USB Driver for GSM modems:
usb 1-1: USB disconnect, address 2
usb 1-1: new high speed USB device using ehci_hcd and address 3
usb 1-1: configuration #1 chosen from 1 choice
option 1-1:1.0: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
option 1-1:1.1: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
option 1-1:1.2: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
option 1-1:1.3: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
option 1-1:1.4: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
option 1-1:1.5: GSM modem (1-port) converter detected
usb 1-1: GSM modem (1-port) converter now attached to ttyUSB5
SCSI subsystem initialized
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
device vlan1 left promiscuous mode
br0: port 1(vlan1) entering disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entering disabled state
device eth2 left promiscuous mode
br0: port 3(eth2) entering disabled state
device br0 entered promiscuous mode
device vlan1 entered promiscuous mode
br0: port 1(vlan1) entering learning state
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
device eth2 entered promiscuous mode
br0: port 3(eth2) entering learning state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 3(eth2) entering forwarding state
I just wanted to report that I was able to flash my E3000 with dd-wrt.v24-23838_NEWD-2_K3.x_mega-e3000.bin. I did the standard 30/30/30 before and after the upgrade. I use my E3000 primarily as a wired NAT router so I haven't tested the radios. So far, so good.
The only thing I have to report is that on the status page it is reporting that I have 256kB of NVRAM. My previous K3.x build (dd-wrt.v24-21676_NEWD-2_K3.x_mega-e3000.bin) only reported 64kB.
Due to the nvram 32,000b limit(cfe bug), had to disable traf info & can't enable ssh. If I do configure then 2GHz is switched off after any reboot because various nvram configuration vars disappear.
Configured both wifi with aes security and other settings for max performance.
Tested performance with iperf to NAS.
5GHz N performance(2 stream): max - 150Mbits, min - 70Mbits, avg - 98 Mbits. Transfer speed diagram is saw/wave shaped, with around 12sec between peaks.
EDIT:
Did another test when all other devices disconected.
bin/iperf.exe -c 192.168.1.XX -P 1 -i 1 -m -p 5001 -w 4096.0K -N -l 4.0M -f m -t 30
Result: a very fast transfer
[224] 0.0-30.2 sec 656 MBytes 182 Mbits/sec
I managed to post my feedback in the Atheros forum.
Build Flashed: dd-wrt.v24_vpn_generic (Not k2.6 or k3.x)
Router Model: WRT-310n V.1
Status: Online and alive (sshd tested and working)
Reset: None (30/30/30 pre and post install)
Errors: "Deadlock Detected, try to fix it"
Router itself is working and seems stable; below are only commments of weird things happening.
I get the above error in my ssh terminal any time I run nvram commit (or if I'm logged into my terminal while applying changes through my web interface). Earlier searches suggested that this is a bug in the firmware on certain routers.
I noted in the Atheros forum that each tab change on the web gui results in a white screen (almost a timeout) that when I press Stop on my browser shows that much of the page has been loaded. It's almost like the last few elements of the page don't load at all. I'm using the current version of Chrome on Windows 7.
Flashed successfully with
dd-wrt.v24-23838_NEWD-2_K2.6_big-nv64k.bin
with reset, but Wi-Fi is not working.
Reverted to
dd-wrt.v24-21676_NEWD-2_K2.6_mega-nv64k.bin
Same here, the wifi would work on my 3700v3 only after you manually disable in wireless setting, then enable again, but after reboot wifi will stop working again, this should be a driver problem.