OpenWrt Forum Archive

Topic: TP-Link TL-WDR4310 v1.0 First Steps

The content of this topic has been archived between 1 Oct 2014 and 4 May 2018. Unfortunately there are posts – most likely complete pages – missing.

Post #76
mtlemmonrunner
12 Sep 2012, 15:22
Benjamin3001 wrote:

...

I've checked the recovery method with the reset button, but this don't work sad

...

Hi,

Did you set your local NIC to 192.168.1.2/255.255.255.0 w/Gateway of 192.168.1.1 first?

Then its quick or not long before the reset button needs pressed during power on and no need to hold the reset really just a tap at the correct moment during the blinking of the * or star/sun looking LED.

I found the 4300 is nearly bullet proof "failsafe" boots w/trunk images...

Oh forgot the more important thing...Once in failsafe mode need to run command "mount_root" in order to get your /etc/config back online.  Then checkout the edits you may have changed causing faulty issue(s) e.g. vi /etc/config/network /etc/config/wireless /etc/config/dhcp /etc/config/firewall...

If you really can't see issue then start over with command "firstboot"

All this is documented here: http://wiki.openwrt.org/doc/howto/generic.failsafe

depending on how or what config you need these configs will differ from user to user.

to get new fresh /etc/config/wireless file you can delete it and regenerate it via command "wifi detect > /etc/config/wireless"

Good luck,
tom

(Last edited by mtlemmonrunner on 12 Sep 2012, 15:34)

Post #77
To0
12 Sep 2012, 19:48

So I recently bought the WDR3600 as it appears to be the same as this but about half the price (one less antennae) .  Sadly noone seems to be talking about it, or the differences.

I'm tempted to try the trunk that claims it is supported but the specifics of the build do not indicate that the loss of the antennae has been taken into account.  Can anyone confirm either:

The build r33219 works

That the 3rd antennae can be added onto this router.

Thanks for the help.

Post #78
slh
12 Sep 2012, 20:09

This r33219 may answer the first part of your question, for the second part - you won't be able to add a third antenna. The TL-WDR3600 is a 2-stream device (for both 2.4 GHz and 5 GHz), while the TL-WDR4300 uses 2-streams for 2.4 GHz and 3-streams for 5 GHz - so its third antenna is only used for 5 GHz operations.

(Last edited by slh on 12 Sep 2012, 20:13)

Post #79
To0
12 Sep 2012, 20:23

My understanding is the hardware is the same, the only part that might be different is the board and the physical presence of the antennae, is there something I can do to check?  Photo of my board?

Updated the wiki with what I can for now.

(Last edited by To0 on 12 Sep 2012, 21:14)

Post #80
slh
13 Sep 2012, 00:01

The TL-WDR4300 has two wlan cards, one 2-stream 2.4 GHz radio (AR9344) embedded into the SoC and one separate 3-stream 5 GHz radio (AR9580) on the same PCB, but this is logically an independent card that just shares the same PCB with the router SoC.

For the TL-WDR3600, I assume that this separate 5 GHz wlan card, at least its PHY, has been switched with a 2-stream variant, so just soldering on an antenna won't make it work. Unfortunately both PCB pictures for TL-WDR4300 and TL-WDR3600 are not detailed enough to read the chip model numbers (in the lower left), however it is obvious that quite a few SMD components in the path to that vacant antenna connection are missing on the TL-WDR3600 picture - so even if there was the same MAC/ PHY used, it would get pretty hard to assemble all the missing SMD components to make that antenna work. Keep in mind that the in-SoC 2.4 GHz radio only uses 2 antennas either way.

Post #81
sdke
13 Sep 2012, 08:26

Has anyone already needed it to use the serial mode to unbrick it? Mine is proball bricked. leds keep blinking, no signal,..

if anyone done it, is it possible to take a picture from it? Thanks

Post #83
janos666
14 Sep 2012, 15:51
sdke wrote:

Has anyone already needed it to use the serial mode to unbrick it?

if anyone done it, is it possible to take a picture from it? Thanks

I did.
I didn't solder the cables, just attached them temporarily. And I already re-assembled the box. Plus I don't really see the use of it to show three colored cables hanging from the PCB.

You can find a post in this topic which explains the pin layout and the Uboot TFPT method is nicely documented on the wiki page of the WDR4300. I followed that almost point-by-point.

(Last edited by janos666 on 14 Sep 2012, 15:54)

Post #84
Benjamin3001
16 Sep 2012, 06:51

Hi Tom,

thank you for your answer and little guide.

I will try this in detail...hopefully it will work!

As Timo experienced, is there a possibility that the VLAN features not working with this model?

cheers
Ben


mtlemmonrunner wrote:
Benjamin3001 wrote:

...

I've checked the recovery method with the reset button, but this don't work sad

...

Hi,

Did you set your local NIC to 192.168.1.2/255.255.255.0 w/Gateway of 192.168.1.1 first?

Then its quick or not long before the reset button needs pressed during power on and no need to hold the reset really just a tap at the correct moment during the blinking of the * or star/sun looking LED.

I found the 4300 is nearly bullet proof "failsafe" boots w/trunk images...

Oh forgot the more important thing...Once in failsafe mode need to run command "mount_root" in order to get your /etc/config back online.  Then checkout the edits you may have changed causing faulty issue(s) e.g. vi /etc/config/network /etc/config/wireless /etc/config/dhcp /etc/config/firewall...

If you really can't see issue then start over with command "firstboot"

All this is documented here: http://wiki.openwrt.org/doc/howto/generic.failsafe

depending on how or what config you need these configs will differ from user to user.

to get new fresh /etc/config/wireless file you can delete it and regenerate it via command "wifi detect > /etc/config/wireless"

Good luck,
tom

Post #85
buccinator
15 Oct 2012, 06:29

hello, i have been trying to find some answers before i get a few of these routers; hoping someone here can clear things up or correct me smile

1. are these dual band antennas unique? ie. can any other dBi antennas be a drop in replacement?
2. if they are unique, is a unique antenna extension cable required aswell? or will a generic one work?

i cant find any images on the sma connectors for these routers. ive emailed tp-link back n forth. they said that;

cut n paste of their replies below

<snip>
1. The max wireless transmit power is 22dBm.
2. For your problem, there is three antennas in the TL-WDR4300, they are the same, for the 2.4GHz and 5 GHz at the same time.
3. Sorry that you can not to use 20bi omi antenna for one, 20bi uni antenna for one and leave the existing antenna for one to cover local area.
4. If you want to change the antenna to extend the range, you have to change all of them at the same time with the same frequency range.
5. For products to be recommended, please refer to this link.
http://www.tp-link.com/en/products/?categoryid=217

1. Sorry that at this moment, we have not got 22bBm antenna.
2. We do not recommend you to change the antenna, because the TL-WR4300 is a
dual band router, the antenna we sell are all signal band.
3. To change the antenna to single band may affect it's stability.
5. To get the tx power, would you please be kind enough to get it changed
from dBm by googling how to convert them, it will be appreciated very much.

1. Sorry that the TL-WDR4300 cannot be used at Access Point mode.
2. You want to get several TL-WDR4300 , and set WDS between these routers to
cover more range, right?
3. Please refer to this link to set up the WDS
http://www.tp-link.com/en/article/?faqid=440
4. For the dual antenna, sorry at this moment, we have not got dual band
antenna to sell.we still do not suggest you to replace the antenna , If you
insist you can buy the dual antenna of other band, and it may affect the
stability.
5. As for the max wireless transmit power in mw, 22 dBm converting to mw is
about 102mw.
6. Yes the dual band antenna need the dual band cable.

1. Sorry for the late reply and the fact that the TL-WDR4300 can not used at
AP mode.
2. And for using the DDWRT or some firmware like that, we have to get you
informed.
3. Some official firmware of TP-LINK products can be replaced by the third
party firmware such as DD-WRT. TP-LINK does not provide technical support
and does not guarantee the performance and stability of third party
firmware. Damage to the product as a result of using third party firmware
will void the product's warranty.
</snip>

Post #86
wilsonhlacerda
17 Oct 2012, 15:07
rebum wrote:

I have recently purchased WDR4300 and the hardware revision is V1.2, is it supported or is it going to be supported?

Any news on that?
Thinking on buying an WDR4300, but it'll be also hardware v1.2......

Any positive or negative tests with hardware v1.2 running OpenWrt for hardware v1.0? (openwrt-ar71xx-generic-tl-wdr4300-v1-......)

Remembering, TP-LINK WDR4300 is a nice and cheap router!
128MB RAM
8MB FLASH
2 USB
2.4Ghz + 5Ghz Simultaneous
CPU 560MHz AR9344
US$70 to US$100 almost worldwide

(Last edited by wilsonhlacerda on 17 Oct 2012, 15:14)

Post #87
h0ly0ne
25 Oct 2012, 15:04

Purchased a WDR4300 with Rev 1.2 today and the Flash process (upgrade from Vendor Web UI) worked flawlessly (openwrt-ar71xx-generic-tl-wdr4300-v1-... - attitude adjustment beta v2).

Some configuration is missing on my side, but i'll post my results when the device is going into productive Environment
the next few days.

Greetings,
h0ly0ne

Post #89
sat_be
31 Oct 2012, 09:57

Hi, I'm also interested in this router, what is your experience with sw openwrt-ar71xx-generic-tl-wdr4300-v1-... - attitude adjustment beta v2 on TP-Link 4300? Does it run stable? Perforamance of the 2.4 and 5GHz bands?

regards

Post #90
rololo88
10 Nov 2012, 13:04

Please help guys,


     I just install openwrt on my new router wdr4310 , i was configuring my router then suddenly i lost communication with my router, im now unable to know my router ip address, cannot telnet either

How can i connect my router now? what's going wrong? pls help.

Thank you

Post #91
yx_wh
22 Nov 2012, 11:03

I have bought a TP-Link TL-WDR4320. Is it an upgraded version of TL-WDR4310? Will TL-WDR4310 firmware work on it?
I found a link
http://blog.ich8.com/post/2695
regards.

Post #92
slh
22 Nov 2012, 14:35

Without being able to read that link, OpenWrt most likely won't install on a TL-WDR4320 without -at least- minimal changes to the firmware headers (similar to the previous adaptions needed for the TL-WDR4310). However at this moment no one knows if there have been any hardware changes which might require additional modifcations to the hardware.

Post #94
nebbia88
22 Nov 2012, 22:10

Why no use AAb2?
You get Luci and most of all a stable package folder... Trunk build will change soon and you'd got to update firmware if you want to install some kmod or other...

(Last edited by nebbia88 on 22 Nov 2012, 22:11)

Post #95
yx_wh
23 Nov 2012, 08:54

oh... I don't know that...
I just followed instructions in
http://wiki.openwrt.org/toh/tp-link/tl-wdr4300
before and I don't know trunk is just like "unstable" in debian...
Thank you for your advice.

using sysupgrade, i have OpenWrt Attitude Adjustment 12.09-beta2 installed on it.

(Last edited by yx_wh on 23 Nov 2012, 09:25)

Post #97
yx_wh
23 Nov 2012, 09:27

I tried and WDR4320 can work with 12.09 Beta2 too

Post #98
ylxu
2 Dec 2012, 09:04
yx_wh wrote:

I tried and WDR4320 can work with 12.09 Beta2 too

Thank you for conforming this.
Here is dmesg of trunk r34381 on WDR4320. Both 2.4G and 5G work well, but the "Failed to stop TX DMA" issue is still here after running 3 days :

[    0.000000] Linux version 3.3.8 (ylxu@t61.local) (gcc version 4.6.4 20121106 (prerelease) (Linaro GCC 4.6-2012.11) ) #1 Mon Nov 26 23:29:58 CST 2012
[    0.000000] MyLoader: sysp=f6be3244, boardp=d2934ba2, parts=ace82dc4
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU revision is: 0001974c (MIPS 74Kc)
[    0.000000] SoC: Atheros AR9344 rev 2
[    0.000000] Clocks: CPU:560.000MHz, DDR:450.000MHz, AHB:225.000MHz, Ref:40.000MHz
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone PFN ranges:
[    0.000000]   Normal   0x00000000 -> 0x00008000
[    0.000000] Movable zone start PFN for each node
[    0.000000] Early memory PFN ranges
[    0.000000]     0: 0x00000000 -> 0x00008000
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat 8030ca40, node_mem_map 81000000
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32512 pages, LIFO batch:7
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line:  board=TL-WDR4300 console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 126356k/131072k available (2168k kernel code, 4716k reserved, 571k data, 212k init, 0k highmem)
[    0.000000] SLUB: Genslabs=9, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:51
[    0.000000] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688)
[    0.070000] pid_max: default: 32768 minimum: 301
[    0.070000] Mount-cache hash table entries: 512
[    0.080000] NET: Registered protocol family 16
[    0.080000] gpiochip_add: registered GPIOs 0 to 22 on device: ath79
[    0.090000] MIPS: machine is TP-LINK TL-WDR3600/4300/4310
[    0.090000] registering PCI controller with io_map_base unset
[    0.310000] bio: create slab <bio-0> at 0
[    0.310000] PCI host bridge to bus 0000:00
[    0.320000] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff]
[    0.320000] pci_bus 0000:00: root bus resource [io  0x0000]
[    0.330000] pci 0000:00:00.0: [168c:0033] type 0 class 0x000280
[    0.330000] pci 0000:00:00.0: invalid calibration data
[    0.330000] pci 0000:00:00.0: reg 10: [mem 0x00000000-0x0001ffff 64bit]
[    0.330000] pci 0000:00:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
[    0.330000] pci 0000:00:00.0: supports D1
[    0.330000] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    0.330000] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1001ffff 64bit]
[    0.340000] pci 0000:00:00.0: BAR 6: assigned [mem 0x10020000-0x1002ffff pref]
[    0.340000] pci 0000:00:00.0: using irq 40 for pin 1
[    0.350000] Switching to clocksource MIPS
[    0.350000] NET: Registered protocol family 2
[    0.360000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.360000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.370000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.370000] TCP: Hash tables configured (established 4096 bind 4096)
[    0.380000] TCP reno registered
[    0.380000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.390000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.390000] NET: Registered protocol family 1
[    0.400000] PCI: CLS 0 bytes, default 32
[    0.410000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.420000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.430000] msgmni has been set to 246
[    0.430000] io scheduler noop registered
[    0.440000] io scheduler deadline registered (default)
[    0.440000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[    0.470000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
[    0.470000] console [ttyS0] enabled, bootconsole disabled
[    0.490000] m25p80 spi0.0: found en25q64, expected m25p80
[    0.490000] m25p80 spi0.0: en25q64 (8192 Kbytes)
[    0.500000] 5 tp-link partitions found on MTD device spi0.0
[    0.500000] Creating 5 MTD partitions on "spi0.0":
[    0.510000] 0x000000000000-0x000000020000 : "u-boot"
[    0.520000] 0x000000020000-0x000000118970 : "kernel"
[    0.520000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[    0.540000] 0x000000118970-0x0000007f0000 : "rootfs"
[    0.540000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[    0.550000] mtd: partition "rootfs" set to be root filesystem
[    0.560000] mtd: partition "rootfs_data" created automatically, ofs=410000, len=3E0000 
[    0.570000] 0x000000410000-0x0000007f0000 : "rootfs_data"
[    0.580000] 0x0000007f0000-0x000000800000 : "art"
[    0.580000] 0x000000020000-0x0000007f0000 : "firmware"
[    0.720000] ag71xx_mdio: probed
[    0.720000] eth0: Atheros AG71xx at 0xb9000000, irq 4
[    1.300000] eth0: Atheros AR8327 switch driver attached.
[    2.460000] ag71xx ag71xx.0: eth0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd033, driver=Atheros AR8216/AR8236/AR8316]
[    2.480000] TCP cubic registered
[    2.480000] NET: Registered protocol family 17
[    2.480000] 8021q: 802.1Q VLAN Support v1.8
[    2.490000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[    2.500000] Freeing unused kernel memory: 212k freed
[    4.260000] Registered led device: tp-link:blue:qss
[    4.260000] Registered led device: tp-link:blue:system
[    4.260000] Registered led device: tp-link:green:usb1
[    4.260000] Registered led device: tp-link:green:usb2
[    4.260000] Registered led device: tp-link:blue:wlan2g
[    5.460000] eth0: link up (1000Mbps/Full duplex)
[    7.670000] eth0: link down
[    9.250000] Compat-drivers backport release: compat-drivers-2012-09-04-2-gddac993
[    9.260000] Backport based on wireless-testing.git master-2012-09-07
[    9.260000] compat.git: wireless-testing.git
[    9.390000] cfg80211: Calling CRDA to update world regulatory domain
[    9.400000] cfg80211: World regulatory domain updated:
[    9.400000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    9.410000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    9.420000] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[    9.430000] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[    9.430000] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    9.440000] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    9.770000] SCSI subsystem initialized
[    9.900000] usbcore: registered new interface driver usbfs
[    9.910000] usbcore: registered new interface driver hub
[    9.910000] usbcore: registered new device driver usb
[   10.370000] ath: EEPROM regdomain: 0x0
[   10.370000] ath: EEPROM indicates default country code should be used
[   10.370000] ath: doing EEPROM country->regdmn map search
[   10.370000] ath: country maps to regdmn code: 0x3a
[   10.370000] ath: Country alpha2 being used: US
[   10.370000] ath: Regpair used: 0x3a
[   10.370000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   10.370000] Registered led device: ath9k-phy0
[   10.370000] ieee80211 phy0: Atheros AR9340 Rev:0 mem=0xb8100000, irq=47
[   10.380000] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
[   10.390000] ath: EEPROM regdomain: 0x0
[   10.390000] ath: EEPROM indicates default country code should be used
[   10.390000] ath: doing EEPROM country->regdmn map search
[   10.390000] ath: country maps to regdmn code: 0x3a
[   10.390000] ath: Country alpha2 being used: US
[   10.390000] ath: Regpair used: 0x3a
[   10.390000] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[   10.390000] Registered led device: ath9k-phy1
[   10.390000] ieee80211 phy1: Atheros AR9300 Rev:4 mem=0xb0000000, irq=40
[   10.400000] cfg80211: Calling CRDA for country: US
[   10.410000] cfg80211: Regulatory domain changed to country: US
[   10.410000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   10.420000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[   10.430000] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[   10.440000] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   10.450000] cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   10.450000] cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   10.460000] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[   10.480000] Button Hotplug driver version 0.4.1
[   11.190000] PPP generic driver version 2.4.2
[   11.470000] ip_tables: (C) 2000-2006 Netfilter Core Team
[   11.760000] NET: Registered protocol family 24
[   11.860000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   11.870000] ehci-platform ehci-platform: Generic Platform EHCI Controller
[   11.880000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
[   11.910000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
[   11.930000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
[   11.930000] hub 1-0:1.0: USB hub found
[   11.940000] hub 1-0:1.0: 1 port detected
[   11.960000] nf_conntrack version 0.5.0 (1977 buckets, 7908 max)
[   12.360000] usb 1-1: new high-speed USB device number 2 using ehci-platform
[   12.550000] compat_xtables: Unknown symbol ipv6_find_hdr (err 0)
[   12.570000] hub 1-1:1.0: USB hub found
[   12.570000] hub 1-1:1.0: 4 ports detected
[   12.670000] xt_time: kernel timezone is -0000
[   13.190000] i2c /dev entries driver
[   13.290000] Initializing USB Mass Storage driver...
[   13.290000] usbcore: registered new interface driver usb-storage
[   13.300000] USB Mass Storage support registered.
[   13.400000] Linux video capture interface: v2.00
[   13.430000] Error: Driver 'gpio-keys-polled' is already registered, aborting...
[   13.790000] u32 classifier
[   13.800000]     Performance counters on
[   13.800000]     input device check on
[   13.800000]     Actions configured
[   13.990000] Mirror/redirect action on
[   14.630000] uvcvideo: Unable to create debugfs directory
[   14.640000] usbcore: registered new interface driver uvcvideo
[   14.640000] USB Video Class driver (1.1.1)
[   18.130000] eth0: link up (1000Mbps/Full duplex)
[   18.170000] eth0: link down
[   18.170000] device eth0.1 entered promiscuous mode
[   18.180000] device eth0 entered promiscuous mode
[   19.140000] eth0: link up (1000Mbps/Full duplex)
[   19.160000] br-lan: port 1(eth0.1) entered forwarding state
[   19.160000] br-lan: port 1(eth0.1) entered forwarding state
[   21.160000] br-lan: port 1(eth0.1) entered forwarding state
[   41.880000] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
[   41.890000] jffs2_build_filesystem(): unlocking the mtd device... done.
[   41.890000] jffs2_build_filesystem(): erasing all blocks after the end marker... done.
[   55.810000] JFFS2 notice: (1924) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[  811.300000] br-lan: port 1(eth0.1) entered disabled state
[  811.330000] device eth0.1 left promiscuous mode
[  811.330000] device eth0 left promiscuous mode
[  811.330000] br-lan: port 1(eth0.1) entered disabled state
[  811.390000] device eth0.1 entered promiscuous mode
[  811.390000] device eth0 entered promiscuous mode
[  811.400000] br-lan: port 1(eth0.1) entered forwarding state
[  811.410000] br-lan: port 1(eth0.1) entered forwarding state
[  813.410000] br-lan: port 1(eth0.1) entered forwarding state
[ 1082.040000] device wlan0 entered promiscuous mode
[ 1082.100000] br-lan: port 2(wlan0) entered forwarding state
[ 1082.110000] br-lan: port 2(wlan0) entered forwarding state
[ 1084.110000] br-lan: port 2(wlan0) entered forwarding state
[ 1236.570000] device wlan0 left promiscuous mode
[ 1236.580000] br-lan: port 2(wlan0) entered disabled state
[ 1237.910000] cfg80211: Calling CRDA for country: CN
[ 1237.910000] cfg80211: Regulatory domain changed to country: CN
[ 1237.920000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1237.920000] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 1237.930000] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (N/A, 3000 mBm)
[ 1248.550000] device wlan0 entered promiscuous mode
[ 1248.950000] br-lan: port 2(wlan0) entered forwarding state
[ 1248.960000] br-lan: port 2(wlan0) entered forwarding state
[ 1250.960000] br-lan: port 2(wlan0) entered forwarding state
[ 1481.360000] device wlan0 left promiscuous mode
[ 1481.360000] br-lan: port 2(wlan0) entered disabled state
[ 1482.630000] device wlan0 entered promiscuous mode
[ 1483.060000] br-lan: port 2(wlan0) entered forwarding state
[ 1483.070000] br-lan: port 2(wlan0) entered forwarding state
[ 1485.070000] br-lan: port 2(wlan0) entered forwarding state
[ 1485.870000] device wlan1 entered promiscuous mode
[ 1485.920000] device wlan1 left promiscuous mode
[ 1485.920000] br-lan: port 3(wlan1) entered disabled state
[ 1517.710000] device wlan0 left promiscuous mode
[ 1517.710000] br-lan: port 2(wlan0) entered disabled state
[ 1519.530000] device wlan0 entered promiscuous mode
[ 1519.780000] br-lan: port 2(wlan0) entered forwarding state
[ 1519.790000] br-lan: port 2(wlan0) entered forwarding state
[ 1521.790000] br-lan: port 2(wlan0) entered forwarding state
[ 1522.600000] device wlan1 entered promiscuous mode
[ 1522.850000] br-lan: port 3(wlan1) entered forwarding state
[ 1522.850000] br-lan: port 3(wlan1) entered forwarding state
[ 1524.850000] br-lan: port 3(wlan1) entered forwarding state
[ 2721.440000] device wlan0 left promiscuous mode
[ 2721.440000] br-lan: port 2(wlan0) entered disabled state
[ 2721.730000] device wlan1 left promiscuous mode
[ 2721.730000] br-lan: port 3(wlan1) entered disabled state
[ 2722.990000] device wlan0 entered promiscuous mode
[ 2723.250000] br-lan: port 2(wlan0) entered forwarding state
[ 2723.260000] br-lan: port 2(wlan0) entered forwarding state
[ 2725.260000] br-lan: port 2(wlan0) entered forwarding state
[ 2726.040000] device wlan1 entered promiscuous mode
[ 2726.090000] device wlan1 left promiscuous mode
[ 2726.090000] br-lan: port 3(wlan1) entered disabled state
[ 2761.410000] device wlan0 left promiscuous mode
[ 2761.410000] br-lan: port 2(wlan0) entered disabled state
[ 2763.020000] device wlan0 entered promiscuous mode
[ 2763.270000] br-lan: port 2(wlan0) entered forwarding state
[ 2763.280000] br-lan: port 2(wlan0) entered forwarding state
[ 2765.280000] br-lan: port 2(wlan0) entered forwarding state
[ 2766.080000] device wlan1 entered promiscuous mode
[ 2766.730000] device wlan1 left promiscuous mode
[ 2766.740000] br-lan: port 3(wlan1) entered disabled state
[ 2886.360000] device wlan0 left promiscuous mode
[ 2886.360000] br-lan: port 2(wlan0) entered disabled state
[ 2887.930000] device wlan0 entered promiscuous mode
[ 2888.180000] br-lan: port 2(wlan0) entered forwarding state
[ 2888.180000] br-lan: port 2(wlan0) entered forwarding state
[ 2890.180000] br-lan: port 2(wlan0) entered forwarding state
[ 2891.010000] device wlan1 entered promiscuous mode
[ 2891.660000] device wlan1 left promiscuous mode
[ 2891.670000] br-lan: port 3(wlan1) entered disabled state
[ 2924.970000] device wlan0 left promiscuous mode
[ 2924.970000] br-lan: port 2(wlan0) entered disabled state
[ 2926.010000] device wlan0 entered promiscuous mode
[ 2926.330000] br-lan: port 2(wlan0) entered forwarding state
[ 2926.330000] br-lan: port 2(wlan0) entered forwarding state
[ 2928.330000] br-lan: port 2(wlan0) entered forwarding state
[ 2929.160000] device wlan1 entered promiscuous mode
[ 2929.810000] device wlan1 left promiscuous mode
[ 2929.820000] br-lan: port 3(wlan1) entered disabled state
[ 2986.400000] device wlan0 left promiscuous mode
[ 2986.400000] br-lan: port 2(wlan0) entered disabled state
[ 2988.020000] device wlan0 entered promiscuous mode
[ 2988.270000] br-lan: port 2(wlan0) entered forwarding state
[ 2988.280000] br-lan: port 2(wlan0) entered forwarding state
[ 2990.280000] br-lan: port 2(wlan0) entered forwarding state
[ 2991.100000] device wlan1 entered promiscuous mode
[ 2991.950000] br-lan: port 3(wlan1) entered forwarding state
[ 2991.950000] br-lan: port 3(wlan1) entered forwarding state
[ 2993.950000] br-lan: port 3(wlan1) entered forwarding state
[ 3025.730000] device wlan0 left promiscuous mode
[ 3025.730000] br-lan: port 2(wlan0) entered disabled state
[ 3026.040000] device wlan1 left promiscuous mode
[ 3026.040000] br-lan: port 3(wlan1) entered disabled state
[ 3027.320000] device wlan0 entered promiscuous mode
[ 3027.570000] br-lan: port 2(wlan0) entered forwarding state
[ 3027.580000] br-lan: port 2(wlan0) entered forwarding state
[ 3029.580000] br-lan: port 2(wlan0) entered forwarding state
[ 3030.370000] device wlan1 entered promiscuous mode
[ 3031.230000] br-lan: port 3(wlan1) entered forwarding state
[ 3031.230000] br-lan: port 3(wlan1) entered forwarding state
[ 3033.230000] br-lan: port 3(wlan1) entered forwarding state
[ 3148.470000] device wlan0 left promiscuous mode
[ 3148.470000] br-lan: port 2(wlan0) entered disabled state
[ 3148.820000] device wlan1 left promiscuous mode
[ 3148.820000] br-lan: port 3(wlan1) entered disabled state
[ 3150.370000] device wlan0 entered promiscuous mode
[ 3150.620000] br-lan: port 2(wlan0) entered forwarding state
[ 3150.630000] br-lan: port 2(wlan0) entered forwarding state
[ 3152.630000] br-lan: port 2(wlan0) entered forwarding state
[ 3153.420000] device wlan1 entered promiscuous mode
[ 3154.270000] br-lan: port 3(wlan1) entered forwarding state
[ 3154.280000] br-lan: port 3(wlan1) entered forwarding state
[ 3156.280000] br-lan: port 3(wlan1) entered forwarding state
[ 3763.580000] usb 1-1.1: new high-speed USB device number 3 using ehci-platform
[ 3763.690000] scsi0 : usb-storage 1-1.1:1.0
[ 3764.690000] scsi 0:0:0:0: Direct-Access     WD       10EAVS External  1.75 PQ: 0 ANSI: 4
[ 3764.700000] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 3764.710000] sd 0:0:0:0: [sda] Write Protect is off
[ 3764.710000] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[ 3764.710000] sd 0:0:0:0: [sda] No Caching mode page present
[ 3764.720000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 3764.730000] sd 0:0:0:0: [sda] No Caching mode page present
[ 3764.740000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 3764.770000]  sda: sda1
[ 3764.770000] sd 0:0:0:0: [sda] No Caching mode page present
[ 3764.780000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 3764.790000] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3842.610000] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
[ 3842.620000] EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
[ 3842.730000] EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
[ 3842.990000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 4308.130000] device wlan0 left promiscuous mode
[ 4308.130000] br-lan: port 2(wlan0) entered disabled state
[ 4308.430000] device wlan1 left promiscuous mode
[ 4308.430000] br-lan: port 3(wlan1) entered disabled state
[ 4309.840000] device wlan0 entered promiscuous mode
[183889.700000] EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
[183889.960000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[187219.580000] tun: Universal TUN/TAP device driver, 1.6
[187219.580000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[187348.580000] fuse init (API version 7.18)
[362902.420000] ath: phy0: Failed to stop TX DMA, queues=0x004!

(Last edited by ylxu on 2 Dec 2012, 09:08)

Post #99
sdke
6 Dec 2012, 18:17

So I have my rs232 model, but I can't let putty connect to it

It's on COM11, putty set on no flow control.

GND is connected with GND
TXD is connected with RXD
RXD is connected with TXD

I tried with the 3,5 voltage cabe, nothing. I tried with the normal adapter, nothing.

Helped wanted guys wink

Post #100
nebbia88
6 Dec 2012, 21:17

What "cable"?? What adapter? Chip? Also, NEVER connect a standard rs232 port, could have 12V and FRY circuits on router!