OpenWrt Forum Archive

Topic: TP-Link TL-MR3020 Support

The content of this topic has been archived between 16 Jun 2013 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

I have no idea! Yes, it will appear, but I have no idea how the process works, or how long it takes to complete.

If you have luci (actually even if you don't) I would recommend the factory, just so you don't get weirdness happening.
You can always do the sysupgrade after (but isn't necessary).

seems factory will overwrite my network settings..

d00m178 wrote:

robthebrew

so there is chance that package for luci and mjpg-streamer that also not available for now will be compiled after some time and will appear in http://downloads.openwrt.org/snapshots/ … /packages/ ?

when it will be done ? when I should check this folder ? Is there some info about time how buildbot works ?

Buildbot snapshots get created roughly once per day.

ar71xx builder: http://buildbot.openwrt.org:8010/builders/ar71xx

Overview: http://buildbot.openwrt.org:8010/grid

Regarding luci_trunk, it was missing there in build 183, but failed in 184 and was delete from the download directory.
Check step 30 / shell_13:
http://buildbot.openwrt.org:8010/builde … logs/stdio
http://buildbot.openwrt.org:8010/builde … logs/stdio


EDIT: corrected the package reference.

(Last edited by hnyman on 21 Mar 2013, 18:53)

hnyman
thank you.

but take a look:
build 184
http://buildbot.openwrt.org:8010/builde … logs/stdio

there is lots of "deleting luci*" like:

deleting packages/luci_trunk+svn9684-1_ar71xx.ipk
deleting packages/luci-theme-openwrt_trunk+svn9684-1_ar71xx.ipk
deleting packages/luci-theme-freifunk-generic_trunk+svn9684-1_ar71xx.ipk
deleting packages/luci-theme-freifunk-bno_trunk+svn9684-1_ar71xx.ipk
deleting packages/luci-theme-bootstrap_trunk+svn9684-1_ar71xx.ipk
deleting packages/luci-theme-base_trunk+svn9684-1_ar71xx.ipk
deleting packages/luci-ssl_trunk+svn9684-1_ar71xx.ipk
deleting packages/luci-sgi-uhttpd_trunk+svn9684-1_ar71xx.ipk
deleting packages/luci-sgi-cgi_trunk+svn9684-1_ar71xx.ipk
...........


what does it mean ?

also 185 build marked as failed. seems I should waid 1 day for 186 buid ?

Yep. Looks like I mixed the builds while writing my message. 184 failed with Luci and those old packages from the previous build were deleted.

185 failed totally, and so did 186 a few minutes ago. Next try tomorrow... "waiting, next in ~ 23 hrs 36 mins".
Apparently one of the buildbots (Nico) can't reach the svn server, and failed rapidly most platforms :-(
http://buildbot.openwrt.org:8010/grid

(Last edited by hnyman on 21 Mar 2013, 18:56)

looks like that 187 build also failed.. May be it require the attention of someone ?

d00m178 wrote:

looks like that 187 build also failed.. May be it require the attention of someone ?

I wrote a comment on the developer mailing list and one of the buildbot admins answered that he has now turned that buildslave off. So hopefully today's build will run normally.
https://lists.openwrt.org/pipermail/ope … 19437.html

thank you ! hope everything will be ok

no luci and no mjpg-streamer in new 188 biuld again (

in post 349 I reported a problem " Receive serial links is not 8-bit clean" with my 3G-Stick Huawei E160.
there was a similar problem posted by rico123 in topic 252

it is a communication problem with the two ports ttyUSB2 and ttyUSB3  the E160 uses on my router.
The old configurartion worked in 2012, but not with a new test in march 2013.
After a lot debugging I found that changing to the other port, ignoring much of the information I found about this issue,  made the stick run again.

I changed the port from ttyUSB3 to ttyUSB2  with LUCI and now it works.

But you can learn something  how to add some additional logging to the 3G communication, which helped me to identify the problem.

Solution:
1.Connect with a ssh to the router  (e.g with putty)
2. put the stick in the USB-Port
3. execute dmesg from the console prompt
4. you should see something like "converter now attached to ttyUSB0"
      and "converter now attached to ttyUSB1"

5. look in LUCI --> network -> wan --> edit , what port is choosen

In my old version it was set to the second port (here ttyUSB3) and it run very nice in 2012 with eplus.

As I testet it in march 2013 it failed.
Jul 15 16:13:02 OpenWrt daemon.info pppd[4155]: Using interface 3g-wan
Jul 15 16:13:02 OpenWrt daemon.notice pppd[4155]: Connect: 3g-wan <--> /dev/ttyUSB2
after some seconds
Jul 15 16:16:43 OpenWrt daemon.notice pppd[5103]: Connection terminated.
Jul 15 16:16:43 OpenWrt daemon.warn pppd[5103]: Receive serial link is not 8-bit clean:
Jul 15 16:16:43 OpenWrt daemon.warn pppd[5103]: Problem: all had bit 7 set to 0
Jul 15 16:16:44 OpenWrt daemon.notice pppd[5103]: Modem hangup

As there was no detailed information I changed the parameter "-V" to "-v" in /etc/ppp/3g.connect

6. edit the /etc/ppp/3g.connect and change the "-V" parameter to "-v"
then you will see more of the communication process.
7. connect to the wan in LUCI
8. look at the system protocoll , what is logged after
   "Jul 15 16:13:02 OpenWrt daemon.notice pppd[4155]: Connect: 3g-wan <--> /dev/ttyUSB2"
   "Jul 15 16:26:22 OpenWrt daemon.debug pppd[7539]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x6ebb52c5>]"
9. if you see  ...
  " Jul 15 16:26:43 OpenWrt daemon.debug pppd[7539]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x6ebb52c5>]
Jul 15 16:26:46 OpenWrt daemon.debug pppd[7539]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x6ebb52c5>]
Jul 15 16:26:49 OpenWrt daemon.debug pppd[7539]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x6ebb52c5>]
Jul 15 16:26:52 OpenWrt daemon.warn pppd[7539]: LCP: timeout sending Config-Requests
Jul 15 16:26:52 OpenWrt daemon.notice pppd[7539]: Connection terminated.
Jul 15 16:26:52 OpenWrt daemon.warn pppd[7539]: Receive serial link is not 8-bit clean:
Jul 15 16:26:52 OpenWrt daemon.warn pppd[7539]: Problem: all had bit 7 set to 0
Jul 15 16:26:54 OpenWrt daemon.notice pppd[7539]: Modem hangup

the server at the provider side did not answer

This is a strong hint that your stick tries to communicate over the wrong port

10. change the port in LUCI to the other port and try again,  does the blue led on the stick lights without flashing?
      then you are connected, maybe you have to unplug the stick and plug it in again.

11. look at the protocoll
   you should see something like

Mar 27 12:08:13 OpenWrt daemon.info pppd[11064]: Using interface 3g-wan
Mar 27 12:08:13 OpenWrt daemon.notice pppd[11064]: Connect: 3g-wan <--> /dev/ttyUSB2
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x276de296>]
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: rcvd [LCP ConfReq id=0x3 <asyncmap 0x0> <auth chap MD5> <magic 0xe72c66> <pcomp> <accomp>]
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: sent [LCP ConfRej id=0x3 <pcomp> <accomp>]
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x276de296>]
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: rcvd [LCP ConfReq id=0x4 <asyncmap 0x0> <auth chap MD5> <magic 0xe72c66>]
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: sent [LCP ConfAck id=0x4 <asyncmap 0x0> <auth chap MD5> <magic 0xe72c66>]
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: sent [LCP EchoReq id=0x0 magic=0x276de296]
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: rcvd [LCP DiscReq id=0x5 magic=0xe72c66]
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: rcvd [CHAP Challenge id=0x1 <8625c86c34b817c88cc43e8dc60bda13>, name = "UMTS_CHAP_SRVR"]
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: sent [CHAP Response id=0x1 <b0f78a561df5d63ba2af9e643fa451c2>, name = "eplus"]
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: rcvd [LCP EchoRep id=0x0 magic=0xe72c66 27 6d e2 96]
Mar 27 12:08:14 OpenWrt daemon.debug pppd[11064]: rcvd [CHAP Success id=0x1 ""]
Mar 27 12:08:14 OpenWrt daemon.info pppd[11064]: CHAP authentication succeeded
Mar 27 12:08:14 OpenWrt daemon.notice pppd[11064]: CHAP authentication succeeded

and some more ,  at last
Mar 27 12:08:17 OpenWrt daemon.notice pppd[11064]: secondary DNS address 212.23.115.132
Mar 27 12:08:17 OpenWrt daemon.debug pppd[11064]: Script /etc/ppp/ip-up started (pid 11116)
Mar 27 12:08:17 OpenWrt user.notice ifup: Enabling Router Solicitations on wan (3g-wan)
Mar 27 12:08:18 OpenWrt daemon.debug pppd[11064]: Script /etc/ppp/ip-up finished (pid 11116), status = 0x1
Mar 27 12:08:18 OpenWrt user.info firewall: adding wan (3g-wan) to zone wan

12. now 3G runs.

Hi,

my new build firmwarel with r36128 seems to corrupt the file system, it may be a flash layout problem.
I had to build the new firmwarel as the opkg update did not install new modules.

the new firmware has obviosly a  different layout  comparing to the old.

Any help appreciated.

|_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
-----------------------------------------------------
BARRIER BREAKER (Bleeding Edge, r36128)
-----------------------------------------------------
  * 1/2 oz Galliano         Pour all ingredients into
  * 4 oz cold Coffee        an irish coffee mug filled
  * 1 1/2 oz Dark Rum       with crushed ice. Stir.
  * 2 tsp. Creme de Cacao
-----------------------------------------------------
root@OpenWrt:/#

root@OpenWrt:/#
root@OpenWrt:/# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                   14656        44     14612   0% /
/dev/root                 3072      3072         0 100% /rom
tmpfs                    14656        60     14596   0% /tmp
tmpfs                      512         0       512   0% /dev
root                     14656        44     14612   0% /tmp/root

overlayfs:/tmp/root      14656        44     14612   0% /
root@OpenWrt:/#

there is an error on the boot console at the end

....
[   32.730000] eth0: link up (100Mbps/Full duplex)
[   32.730000] br-lan: port 1(eth0) entered forwarding state
[   32.740000] br-lan: port 1(eth0) entered forwarding state
[   33.830000] jffs2: Too few erase blocks (2)
[   34.740000] br-lan: port 1(eth0) entered forwarding state


I set the password  with telnet , and after a reboot the changes are lost.
all other schanges are lost too.

the old good running version reports:

BusyBox v1.19.4 (2012-04-24 21:04:04 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
|       |.-----.-----.-----.|  |  |  |.----.|  |_
|   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
|_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
-----------------------------------------------------
ATTITUDE ADJUSTMENT (Bleeding Edge, r31672)
-----------------------------------------------------

root@OpenWrt:/# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                     640       224       416  35% /
/dev/root                 2560      2560         0 100% /rom
tmpfs                    14756       140     14616   1% /tmp
tmpfs                      512         0       512   0% /dev
/dev/mtdblock3             640       224       416  35% /overlay
overlayfs:/overlay         640       224       416  35% /
root@OpenWrt:/#

That looks completely screwed up. Are you sure you compiled for the correct target?
What is the output of

cat /proc/mtd

Preferably before and after, as you did for df

1. I am shure that I compiled for the MR-3020

me .config file says

CONFIG_TARGET_ar71xx_generic=y
...

CONFIG_TARGET_ar71xx_generic_TLMR3020=y

2. output of cat /proc/mtd
old Version :

root@OpenWrt:/# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00020000 00010000 "u-boot"
mtd1: 000dc3ac 00010000 "kernel"
mtd2: 002f3c54 00010000 "rootfs"
mtd3: 000b0000 00010000 "rootfs_data"
mtd4: 00010000 00010000 "art"
mtd5: 003d0000 00010000 "firmware"

As I returned to the old firmware I have no actual dat for that.

3. There was a discussion concerníng the needed space for the installation
Are there any problems to install http://downloads.openwrt.org/attitude_a … actory.bin on a V1.6 with 4/16MB?

Do you think its a better idea to install the rc1 and throw out some unneeded stuff later and add the needed thing later?

I need support for usbSerial for ftdi and pl2303, gpsd and gpsd client, 3G for Huawei E160, and if possible LUCI

I would go with AArc1.
It should fit. Depends how much other stuff you want to add after.
Or you could compile AArc1 with what you need but maybe not luci (it is quite big, and included in the built version of AArc1)
Report how much space you have after flashing it. also cat /proc/mtd

Flashing the rc1 was done without any problems. LUCI came up immediatly.
This is from the rc1
root@OpenWrt:~#
root@OpenWrt:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                    1088       212       876  19% /
/dev/root                 2048      2048         0 100% /rom
tmpfs                    14612       128     14484   1% /tmp
tmpfs                      512         0       512   0% /dev
root                     14608        40     14568   0% /tmp/root
overlayfs:/tmp/root      14608        40     14568   0% /tmp/root
/dev/mtdblock3            1088       212       876  19% /overlay
overlayfs:/overlay        1088       212       876  19% /


root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00020000 00010000 "u-boot"
mtd1: 000e9894 00010000 "kernel"
mtd2: 002e676c 00010000 "rootfs"
mtd3: 00110000 00010000 "rootfs_data"
mtd4: 00010000 00010000 "art"
mtd5: 003d0000 00010000 "firmware"
root@OpenWrt:~#

Thanks for the help

AArc1 works like charm but it has luci and other packages inside so size of firmware too big for move it to usb flash disk.
There is  no free space to install the necessary packages.
Because of it I try to compile my own fw.
Also there is no mjpg-streamer, but finally I compiled it and succesfully installed.
But now I stuck on other problem - I can't install libftdi which needed for kmod-usb-serial-ftdi for my arduino..
I tried to compile it but I've got an error:

checking for libusb-config... no
configure: error: *** libusb-config not found. You need a working libusb installation.
make[2]: *** [/home/banka/openwrt/trunk/build_dir/target-mips_r2_uClibc-0.9.33.2/libftdi-0.19/.configured_] Error 1
make[2]: Leaving directory `/home/banka/openwrt/trunk/feeds/packages/libs/libftdi'
make[1]: *** [package/feeds/packages/libftdi/compile] Error 2
make[1]: Leaving directory `/home/banka/openwrt/trunk'
make: *** [package/feeds/packages/libftdi/compile] Error 2

d00m178 wrote:

configure: error: *** libusb-config not found. You need a working libusb installation.

You are probably into effects of the libusb changes in late January

https://dev.openwrt.org/search?q=libusb
https://dev.openwrt.org/changeset/35388

Old libusb was renamed to libusb-compat, while newer libusb was palced as libusb. You might have to test with both libusb versions to see what your package really needs.
And be careful with menuconfig: you have to actively remove old dependencies, so if you test those, make really sure that you do not have 2 different libusbs included and built. If you switch it, you have to "make clean" to destroy the wrong one from build_dir.

I added some features to the rc1 on my device to see how much space it uses.

With the help of LUCI I installed:

kmod-usb-serial, kmod-usb-serial-pl2303, kmod-usb-serial-ftdi

Result: both USB-Serial converters are regognized when plugged in and attached to ttyUSB0 and tttyUSB1

kmod-fs-ext4 and kmod-usb-storage

Result: A USB Stick with ext4 is recognized and can be accesed with /dev/sda1

I installed the gpsd and the gpsd-clients module

Remaining space is 9% !!!

root@OpenWrt:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                    1088       988       100  91% /
/dev/root                 2048      2048         0 100% /rom
tmpfs                    14612      1844     12768  13% /tmp
tmpfs                      512         0       512   0% /dev
/dev/mtdblock3            1088       988       100  91% /overlay
overlayfs:/overlay        1088       988       100  91% /
/dev/sda1              2753976    121660   2494284   5% /mnt/sd1

but I have a lot of space on the /dev/sda1

Is it possible to move LUCI to the /dev/sda1 ?

I got the gpsd working at start, it sends a message
{"class":"VERSION","release":"3.7","rev":"3.7","proto_major":3,"proto_minor":7}

but it  doesnot read from the USB-Serial Converter

it throws a message :
Mar 27 18:52:39 OpenWrt user.err gpsd[1355]: gpsd:SHOUT: vendor/product match with 091e:0003 not found

but dmesg says :
11.460000] ftdi_sio 1-1.1:1.0: FTDI USB Serial Device converter detected
[   11.470000] usb 1-1.1: Detected FT232BM
[   11.470000] usb 1-1.1: Number of endpoints 2
[   11.470000] usb 1-1.1: Endpoint 1 MaxPacketSize 16384
[   11.480000] usb 1-1.1: Endpoint 2 MaxPacketSize 16384
[   11.480000] usb 1-1.1: Setting MaxPacketSize 64
[   11.490000] usb 1-1.1: FTDI USB Serial Device converter now attached to ttyUSB0

and the log in LUCI

Mar 27 18:52:38 OpenWrt user.notice gpsd: Starting...
Mar 27 18:52:38 OpenWrt user.notice try to start gpsd with : /dev/ttyUSB0

seems to be a problem with USBLib??? which is discussed in the other post

I never had this message with my old firmware.

hnyman wrote:
d00m178 wrote:

configure: error: *** libusb-config not found. You need a working libusb installation.

You are probably into effects of the libusb changes in late January

https://dev.openwrt.org/search?q=libusb
https://dev.openwrt.org/changeset/35388

Old libusb was renamed to libusb-compat, while newer libusb was palced as libusb. You might have to test with both libusb versions to see what your package really needs.
And be careful with menuconfig: you have to actively remove old dependencies, so if you test those, make really sure that you do not have 2 different libusbs included and built. If you switch it, you have to "make clean" to destroy the wrong one from build_dir.



I can't choose only libusb-compat in menuconfig. when I choose to build libftdi then automaticaly checked libusb-1.0 and libusb-compat. and not possible to choose only one of them

@dddesign
tnx for the script, but I haven't had a time to make anything more, and to be honest I don't know how to add those script you posted into mentioned dirs. If someone would be so kind to advise, I would appreciate it...and probably few people  more...

I have one problem with my wireless radio...I was forced to change my wireless network password, and after that I can't see my wireless network radio...wireless led at the tp-link is on, but no network visible...and yes, I adjusted passwords where it was necessary...I even tried to revert my old pass but no radio...

(Last edited by novikorisnik on 27 Mar 2013, 23:25)