Topic: Tp-Link td-w8970

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

Page 4 of 16

Post #76

rezad1393

25 Nov 2014, 15:55

rezad1393 wrote:

dziny wrote:
Do you know if it is possible to switch between the rylos version and and official 14.07 using the sysupgrade method? Don't want to go back to serial given how bad it was for me.
a point here. i had to mess with serial.i used the serial method described by rylos and in it it has erase instructions that i think it uses its size of ROM (8MB) so i think after using the official ROM (that is 3~4MB) it doesn't boot and it gives errors so maybe it doesn't work with rylos exact instruction. but after using serial with rylos i used the web interface and uploaded the official ROM.
and it works (just the LAN bridge right now,i haven't tested adsl ). so i think you can do it my way if the serial doesn't work.

it seems that the serial way donsnt work with the official openwrt ROM image.
i thought it was because i used Rylos instruction and erased something needed (which i still think i did erase some stuff not neeeded to be erased) but i saw somewhere else somebody else also said that serial flashing didnt work with the provided ROM but his way of solving it was creating a new image himself and flashing that.

Post #77

nighty2k

6 Dec 2014, 15:30

Hey Guys, i try to get my 8970 to work on a vdsl line but i dont get a sync.
I m a few moments before cracking up with this, so i hope you could help me

Okay, here are the facts:

First of all, to check the Hardware, i crossflashed the 8970 to a 9980 image.
VDSL Sync works, even when it was bad.(20/1 MB/s)
On the Line actual a EasyBox 904xDSL is running with a sync of 50.1/9.8 sync

Facts about the Line:
German VDSL2 from Vodafone(Germany), technical its a Bitstream Line from Telekom(Germany) so it must be
Profile 17a, PTM, VLAN 7.
As far as i know, since VDSL is a PTM Line, there is no need for VPI,VCI and encapsulation!?

Software:
I flashed the 8970 to the last offical Build: 14.07, October 2nd, 2014. @r42625
The VDSL.bin i got from a Speedport w921v v1.36 with the firmware cutter ( http://patchwork.openwrt.org/patch/6446/ )

Today i found these two patches, and applied them to my *.sh
(Should solve VDSL Problems)
https://dev.openwrt.org/changeset/43101
https://dev.openwrt.org/changeset/43114

Config:

...
...
config interface 'wan'
option ifname 'ptm0.7'
option proto 'pppoe'
option username 'username'
option password 'password'
option ipv6 '1'
option macaddr 'xx:xx:xx:xx:xx:xx'

config vdsl 'dsl'
option annex 'b' #Also tried 'j' and nothing (see Patches)
option firmware '/lib/firmware/vdsl.bin' # seems to be okay
option tone 'b' # should be b, but also tried bv
option xfer_mode 'ptm'

Result:
Everything i get is:
root@OpenWrt:~# /etc/init.d/dsl_control status
Chipset: Lantiq-VRx n
Line State: DOWN [0xff: idle request]
Data Rate: 0 b/s / 0 b/s
Line Attenuation: 0.0dB / 0.0dB
Noise Margin: 0.0dB / 0.0dB
Line Uptime: down

Ideas:
As i saw in the /etc/init.d/dsl_control , nFilter (-1 = N/A) and Tone (1=Manual) are Hardcoded here.
Should it be necessary to do changes here?
I hope you can help me with this.

Post #78

zhadoom

6 Dec 2014, 16:50

As far as i know, since VDSL is a PTM Line, there is no need for VPI,VCI and encapsulation!?

Correct. PTM maybe use a VLAN but none like vpi/vci ( ATM params ).

Try this:

config vdsl 'dsl'
    option annex 'a' 
    option firmware '/lib/firmware/vdsl.bin'
    option tone 'av'
    option xfer_mode 'ptm'

Since the 17a profile is the same between the band plans.

(Last edited by zhadoom on 6 Dec 2014, 16:51)

Post #79

abraXxl

6 Dec 2014, 17:50

@nighty2k:
Try to fetch an old Firmware Version of the Speedport W921. I heard that there might be issues with the Firmware Blob for the "xDSL Chip" from 1.36, as it does not fit to the driver from openwrt BB.
AFAIK the DSL Blob from version 1.21 of the Speedport FW works with BB.

(Last edited by abraXxl on 6 Dec 2014, 17:54)

Post #80

dziny

6 Dec 2014, 19:17

Let us know about the result! You can still find version 1.21 firmware on Telekom web site. I'm interested in hearing if it works since I'm going to setup VDSL on this router for my parents in about a week.

Post #81

nighty2k

7 Dec 2014, 14:16

Hey guys

i am still back at home and was able to test your hints with a little success.

So lets start with the result:

After a lot of this:
DOWN [0xff: idle request]
DOWN [0x1: exception]
DOWN [0x200: silent]
DOWN [0x300: handshake]
DOWN [0x380: full_init]

I got this:
Line State: UP [0x801: showtime_tc_sync]
Data Rate: 20.548 Mb/s / 1.512 Mb/s
Line Attenuation: 3.0dB / 0.0dB
Noise Margin: 6.0dB / 6.3dB
Line Uptime: 22s

The Solution:
The Problem was the Firmware like told from abraXxl
I modified the vdsl_fw_install.sh to fetch the v1.21 because of the v1.20 is not longer accessible from D-Telekom

My working 'network' config:
....
(No ATM Settings)
...
config interface 'wan'
option ifname 'ptm0.7'
option proto 'pppoe'
option username 'username'
option password 'password'
option ipv6 '1'
option macaddr 'aa:bb:cc:dd:ee:ff'

config interface 'wan6'
option ifname '@wan'
option proto 'dhcpv6'

config vdsl 'dsl'
option firmware '/lib/firmware/vdsl.bin'
option tone 'b'
option xfer_mode 'ptm'

Further recommendations:
As i told yesterday, i applied these patches:
https://dev.openwrt.org/changeset/43101
https://dev.openwrt.org/changeset/43114
so there is no need for set an annex and the driver is initializes as VDSL only.
You can see it if you check the running processes
vdsl_cpe_control schould be initialized with -i 00_00_00_00_00_00_00_07 (= VDSL)

More Problems:
As i told yesterday, my line is running fine with a Vodafone EasyBox 904xDSL with a full sync of 50.1 / 9.8 MBs
With the crossflashed 9980 Firmware and also with the BB14.07 i only get 20.548 Mb/s / 1.512 Mb/s.
Does Anybody have an idea? As far as i know, the 904xDSL has exactly the same Chipset, so a fully sync should be possible.
One idea i have, it could be a problem with VDSL vectoring.
My line is in a Telekom test-area for VDSL Vectoring, as far as i know, if a area is vectoring enabled, all lines of a DSLAM must be vectoring enabled. Non vectoring devices should be compatible but i dont know if this could affect the sync!?

D-Telekom added the vectoring capability to the w921v with firmware 1.34
@abraXxl, is there a way to geht the 1.36 running with OpenWrt to test this?

Post #82

abraXxl

7 Dec 2014, 19:57

These both patches do only fix bugs in scripts in OpenWrt, and are not related to
the sync rate of your device.
https://dev.openwrt.org/changeset/43101
https://dev.openwrt.org/changeset/43114

If you have a Vodafone VDSL line, I expect you have an so called "Next Genenation DSL Anschluss", with no POTS (only VOIP).
So you have high probably better results with annex J and/or tone BV.

I have here an "1und1/Telekom VDSL Anschluss", but Vodaphone VDSL is similar.

My /etc/config/network dsl section look like this, maybe it helps.

[...]
config vdsl 'dsl'
        option firmware '/lib/firmware/vdsl.bin'
        option xfer_mode 'ptm'
        #option annex 'j'
        option annex 'b'
        option tone 'bv'
[...]

AFAIK there are currently no ways to enable sync with 1.36 in BB and CC.

(Last edited by abraXxl on 7 Dec 2014, 20:00)

Post #83

nighty2k

8 Dec 2014, 20:35

After changing to tone = 'bv' dosent changed anything, i googled and tested a little bit arround.
My 20/1.5 MB/s problem seems to be a VDSL2 Vectoring Fallback mode.
If a DSLAM detects a non VDSL2 Vectoring capable reouter, it falls back to ADSL2+ (Annex B/J in case of Germany).

For the moment, i runnung a self compiled CC from latest git with changed drv_dsl_cpe_api_vrx
4.11.11 (latest git = 4.11.4)
For informations look @ https://forum.openwrt.org/viewtopic.php?id=50860

If i am right, the usabale firmware blob depands on this version !?
So the bad news is, 4.11.11 arent able to control the Speedport v1.36 fw blob.

Does anybody see a chance to get the information which api is used in Telekom Speedport W921V >= v1.34 or Vodafone EasyBox 904 xDSL >= 03.16 because stating with this versions, these VRC200 Devices starts with vectoring support.

The GPL published sources from 904xdsl i already checked with any success to find the used version.

Post #84

dziny

14 Dec 2014, 16:30

I'm having issues with pppoe ADSL2. I wonder if anyone has any insight on it. My /etc/config/network looks like

config atm-bridge 'atm'
        option vpi '1'
        option vci '32'
        option encaps 'llc'
        option payload 'bridged'

config interface 'wan'
        option ifname 'nas0'
        option proto 'pppoe'
        option username 'username'
        option password 'pswrd'
        option ipv6 '0'
        option peerdns '0'
        option dns '208.67.222.222 208.67.220.220'

config vdsl 'dsl'
        option annex 'b'
        option firmware '/lib/firmware/vdsl.bin'
        option tone 'bv'
        option xfer_mode 'atm'

I have tried different firmware blobs but to no avail. This is in country using annex B (Slovakia) I have previously had the router running fine on annex A in the UK but it was pppoa.

I can see dsl_control process running:
/sbin/vdsl_cpe_control -i 10_00_10_00_00_04_00_00 -n /sbin/dsl_notify.sh -f /lib/firmware/vdsl.bin -a /tmp/adsl.scr -A /tmp/vdsl.scr

But dsl_control status shows no connection/IDDLE

Finally, my log shows:

Sun Dec 14 15:12:50 2014 daemon.notice netifd: Interface 'wan' is now down
Sun Dec 14 15:12:50 2014 kern.info kernel: [  203.008000] IPv6: ADDRCONF(NETDEV_UP): nas0: link is not ready
Sun Dec 14 15:12:50 2014 daemon.notice netifd: Interface 'wan' is disabled
Sun Dec 14 15:12:50 2014 daemon.notice netifd: Interface 'wan' is enabled
Sun Dec 14 15:12:50 2014 daemon.notice netifd: Interface 'wan' is setting up now
Sun Dec 14 15:12:50 2014 daemon.notice netifd: Network device 'nas0' link is down
Sun Dec 14 15:12:50 2014 daemon.notice netifd: Interface 'wan' has link connectivity loss
Sun Dec 14 15:12:50 2014 daemon.notice netifd: Network device 'nas0' link is up
Sun Dec 14 15:12:50 2014 daemon.notice netifd: Interface 'wan' has link connectivity 
Sun Dec 14 15:12:50 2014 daemon.info pppd[2719]: Plugin rp-pppoe.so loaded.
Sun Dec 14 15:12:50 2014 daemon.info pppd[2719]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Dec 14 15:12:50 2014 daemon.notice pppd[2719]: pppd 2.4.7 started by root, uid 0
Sun Dec 14 15:13:05 2014 daemon.warn pppd[2719]: Timeout waiting for PADO packets
Sun Dec 14 15:13:05 2014 daemon.err pppd[2719]: Unable to complete PPPoE Discovery
Sun Dec 14 15:13:05 2014 daemon.info pppd[2719]: Exit

Anyone has ideas? Curiously, an older device (BT homehub 2b) with openwrt with almost identical settings runs great The only different is config is the bit:

config adsl 'dsl'
        option annex 'b'
        option firmware '/lib/firmware/adsl.bin'

since that device does not support vdsl.

Post #85

s7a7ic

13 Jan 2015, 13:37

@dziny
I have the same problem like you and I'm using nearly the same config.
Did you have success with your ADSL Annex B connection?

Could someone please tell me how to debug the pppoe connection or where to start looking?
I have the same log-output like dziny.

I'm using the Easybox 803 with original FW and also tested my connection on TD-W8970b with original FW.
After flashing OpenWRT I can't get ADSL to work and also tried some different vr9-firmwares. After three days I only found reports about working Annex A/VDSL configs for this router and I must say it was easyer to flash OpenWRT on this device than get ADSL to work...

My ISP is easybell (O2/Telefonica in Berlin).

Edit: I'm using the image from Rylos.

(Last edited by s7a7ic on 13 Jan 2015, 16:29)

Post #86

wickusb

16 Jan 2015, 11:39

Unfortunately im using annex a

Here is my config for dsl portion in /etc/config/network

config vdsl 'dsl'
option annex 'a'
option firmware '/lib/firmware/vdsl.bin'
option tone 'av'
option xfer_mode 'atm'

root@OpenWrt:~# ls -l /lib/firmware/
-rw-r--r-- 1 root root 885524 Oct 1 16:46 dsl_vr9_firmware_xdsl-05.06.00.08.01.06_05.05.02.00.01.01.bin
drwxrwxrwt 2 root root 40 Jan 15 06:52 lantiq
lrwxrwxrwx 1 root root 61 Oct 1 16:47 vdsl.bin -> dsl_vr9_firmware_xdsl-05.06.00.08.01.06_05.05.02.00.01.01.bin

Post #87

wickusb

16 Jan 2015, 12:02

Have you tried the following

config vdsl 'dsl'
option annex 'b'
option firmware '/lib/firmware/vdsl.bin'
option tone 'b'
option xfer_mode 'atm'

Post #88

dziny

17 Jan 2015, 14:19

wickusb wrote:

Have you tried the following
config vdsl 'dsl'
option annex 'b'
option firmware '/lib/firmware/vdsl.bin'
option tone 'b'
option xfer_mode 'atm'

I have tried option tone will all possible options, but none was working for me.

Post #89

s7a7ic

17 Jan 2015, 19:01

Thank you for reply

The problem was the DSL firmware.
Like abraXxl said, it has to be the binary blob from W921 Speedport FW and V1.21! (the latest V1.36 doesn't work)
Now I'm online with my new All-In-One OpenWrt Router

I had problems to extract the firmware with vdsl_fw_install.sh on the device, because there wasn't much space left for all the copying.
So optionally you can place the Firmware_Speedport_W921V_1.20.000.bin in /tmp (and name it like that, the name is hardcoded in w912_fw_cutter), now execute w921_fw_cutter and move the vr9_xdsl*.bin to /lib/firmware/vdsl.bin or just download w921_fw_cutter and compile/run it on your linux machine (don't forget to modify the paths inside the code).

@dizny: try to include a mac-addess inside the wan cfg-part

Here is my running config:

config atm-bridge 'atm'
        option vpi '1'
        option vci '32'
        option encaps 'llc'
        option payload 'bridged'

config interface 'wan'
        option ifname 'nas0'
        option proto 'pppoe'
        option macaddr 'e8:94:f6:aa:XX:XX'
        option delegate '0'
        option username 'user@isp.to'
        option password 'PaSSw0rd'

config interface 'wan6'
        option ifname '@wan'
        option proto 'dhcpv6'

config vdsl 'dsl'
        option annex 'b'
        option firmware '/lib/firmware/vdsl.bin'
        option tone 'bv'
        option xfer_mode 'atm'

(Last edited by s7a7ic on 17 Jan 2015, 19:34)

Post #90

dziny

18 Jan 2015, 19:50

Thank for the tip. I'll try it. Just to make sure I am using the same firmware blob as you, mine has size 885524 and md5sum 6feba8f8f939fed82d049ae13bc2cf96.

Post #91

s7a7ic

19 Jan 2015, 10:34

My vdsl.bin extracted from Firmware_Speedport_W921V_1.21.000.bin

Size: 761108 (743.3 K)
MD5: 59dd9dc81195c6854433c691b163f757

Looks like you have still the Firmware-Blob from Rylos Image. I think after a "restore defaults" it get's restored, so you have to copy the working binary into /lib/firmware after every restore again.

(Last edited by s7a7ic on 19 Jan 2015, 10:37)

Post #92

wickusb

30 Jan 2015, 12:59

I've been using my 8970 for a few weeks now on openwrt and the only problem im getting is the kernel crashes due to the wireless driver.

I found other posts with a similar problem.

https://forum.openwrt.org/viewtopic.php?id=35295
https://forum.openwrt.org/viewtopic.php?id=34313

After the crash the wifi is dead but wired and adsl is still working fine

the crash msg from the kernel.log is below.

[ 3059.656000] ------------[ cut here ]------------
[ 3059.656000] WARNING: at kernel/sched/core.c:1590 wake_up_process+0x2c/0x48()
[ 3059.656000] Modules linked in: ltq_atm_vr9 ath9k ath9k_common iptable_nat ath9k_hw ath pppoe nf_nat_ipv4 nf_conntrack_ipv4 mac80211 ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT pppox ppp_async nf_nat_irc nf_nat_ftp nf_nat nf_defrag_ipv4 nf_conntrack_irc nf_conntrack_ftp ltq_deu_vr9 iptable_raw iptable_mangle iptable_filter ipt_REJECT ip_tables crc_ccitt compat drv_dsl_cpe_api drv_mei_cpe ledtrig_usbdev ip6t_REJECT ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables nf_conntrack_ipv6 nf_conntrack nf_defrag_ipv6 pppoatm ppp_generic slhc br2684 atm ipv6 drv_ifxos arc4 crypto_blkcipher ltq_hcd_vr9 gpio_button_hotplug
[ 3059.656000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.10.49 #3
[ 3059.656000] Stack : 00000000 00000000 00000000 00000000 8049c4ce 00000032 80420ed8 273d1a57
[ 3059.656000]    803c1a64 80421303 00000000 80493960 80420ed8 273d1a57 7fffffff 00000004
[ 3059.656000]    80410000 802de8cc 00000003 801f7464 00000000 00000000 803c3124 80413c14
[ 3059.656000]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 3059.656000]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 80413ba0
[ 3059.656000]    ...
[ 3059.656000] Call Trace:
[ 3059.656000] [<80246554>] show_stack+0x48/0x70
[ 3059.656000] [<80301c14>] warn_slowpath_common+0x78/0xa8
[ 3059.656000] [<80301ccc>] warn_slowpath_null+0x18/0x24
[ 3059.656000] [<803014cc>] wake_up_process+0x2c/0x48
[ 3059.656000] [<8012d744>] hrtimer_wakeup+0x1c/0x34
[ 3059.656000] [<8005477c>] __run_hrtimer.isra.32+0x58/0x104
[ 3059.656000] [<8012cff8>] hrtimer_interrupt+0x1c8/0x408
[ 3059.656000] [<80097e48>] c0_compare_interrupt+0x70/0x9c
[ 3059.656000] [<8012aa18>] handle_irq_event_percpu+0x58/0x260
[ 3059.656000] [<8012af38>] handle_percpu_irq+0x54/0x84
[ 3059.656000] [<8011c7b4>] generic_handle_irq+0x40/0x54
[ 3059.656000] [<800d6700>] do_IRQ+0x1c/0x2c
[ 3059.656000] [<80006430>] ret_from_irq+0x0/0x4
[ 3059.656000] [<8020d670>] r4k_wait_irqoff+0x18/0x1c
[ 3059.656000] [<800b36c0>] cpu_startup_entry+0xb8/0x110
[ 3059.656000] [<8043793c>] start_kernel+0x398/0x3b0
[ 3059.656000]
[ 3059.656000] ---[ end trace 9229c1ddddc69ea0 ]---
[ 5360.920000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[11803.228000] huh, entered softirq 9 RCU 80212398 preempt_count 00000100, exited with 00000300?
[38951.228000] eth0: port 4 lost link
[38951.228000] br-lan: port 1(eth0.1) entered disabled state
[38953.148000] br-lan: port 1(eth0.1) entered forwarding state
[38953.152000] br-lan: port 1(eth0.1) entered forwarding state
[38955.156000] br-lan: port 1(eth0.1) entered forwarding state
[57731.056000] ------------[ cut here ]------------
[57731.060000] WARNING: at /BB/build/lantiq/xrx200/build_dir/target-mips_34kc+dsp_uClibc-0.9.33.2/linux-lantiq_xrx200/compat-wireless-2014-05-22/net/mac80211/driver-ops.h:12 ieee80211_set_key_rx_seq+0x43c/0x508 [mac80211]()
[57731.080000] : Failed check-sdata-in-driver check, flags: 0x0
[57731.084000] Modules linked in: ltq_atm_vr9 ath9k ath9k_common iptable_nat ath9k_hw ath pppoe nf_nat_ipv4 nf_conntrack_ipv4 mac80211 ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT pppox ppp_async nf_nat_irc nf_nat_ftp nf_nat nf_defrag_ipv4 nf_conntrack_irc nf_conntrack_ftp ltq_deu_vr9 iptable_raw iptable_mangle iptable_filter ipt_REJECT ip_tables crc_ccitt compat drv_dsl_cpe_api drv_mei_cpe ledtrig_usbdev ip6t_REJECT ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables nf_conntrack_ipv6 nf_conntrack nf_defrag_ipv6 pppoatm ppp_generic slhc br2684 atm ipv6 drv_ifxos arc4 crypto_blkcipher ltq_hcd_vr9 gpio_button_hotplug
[57731.148000] CPU: 0 PID: 969 Comm: hostapd Tainted: G W 3.10.49 #3
[57731.156000] Stack : 00000000 00000000 00000000 00000000 8049c4ce 0000003f 82d34f50 00000001
[57731.156000]    803c1a64 80421303 000003c9 80493960 82d34f50 00000001 00000000 830e3000
[57731.156000]    00000008 802de8cc 00000003 801f73f0 00000000 00000000 803c3124 82d77a74
[57731.156000]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[57731.156000]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 82d77a00
[57731.156000]    ...
[57731.192000] Call Trace:
[57731.196000] [<80246554>] show_stack+0x48/0x70
[57731.200000] [<80301c14>] warn_slowpath_common+0x78/0xa8
[57731.204000] [<80301c70>] warn_slowpath_fmt+0x2c/0x38
[57731.208000] [<832a7f94>] ieee80211_set_key_rx_seq+0x43c/0x508 [mac80211]
[57731.216000]
[57731.216000] ---[ end trace 9229c1ddddc69ea1 ]---
[57731.220000] : failed to remove key (0, e8:94:f6:3f:80:bf) from hardware (-5)
[57731.228000] Unhandled kernel unaligned access[#1]:
[57731.228000] CPU: 0 PID: 969 Comm: hostapd Tainted: G W 3.10.49 #3
[57731.228000] task: 82d34da8 ti: 82d76000 task.ti: 82d76000
[57731.228000] $ 0 : 00000000 00000001 00000001 00000001
[57731.228000] $ 4 : 00000001 8381ba80 833b055f 0000007d
[57731.228000] $ 8 : 00010000 54cb5432 01b854a4 00000117
[57731.228000] $12 : 00000000 0d1cef00 00000117 00000000
[57731.228000] $16 : 833b055f 00000001 0000007d 8381ba80
[57731.228000] $20 : 00000001 00000001 00000000 830e3000
[57731.228000] $24 : 00000003 00000000
[57731.228000] $28 : 82d76000 82d77af0 00000008 832a8004
[57731.228000] Hi : 00000898
[57731.228000] Lo : 00002260
[57731.228000] epc : 8020a064 queue_delayed_work_on+0x4c/0xc8
[57731.228000] Tainted: G W
[57731.228000] ra : 832a8004 ieee80211_set_key_rx_seq+0x4ac/0x508 [mac80211]
[57731.228000] Status: 1100fc02 KERNEL EXL
[57731.228000] Cause : 00800010
[57731.228000] BadVA : 833b055f
[57731.228000] PrId : 00019556 (MIPS 34Kc)
[57731.228000] Modules linked in: ltq_atm_vr9 ath9k ath9k_common iptable_nat ath9k_hw ath pppoe nf_nat_ipv4 nf_conntrack_ipv4 mac80211 ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT pppox ppp_async nf_nat_irc nf_nat_ftp nf_nat nf_defrag_ipv4 nf_conntrack_irc nf_conntrack_ftp ltq_deu_vr9 iptable_raw iptable_mangle iptable_filter ipt_REJECT ip_tables crc_ccitt compat drv_dsl_cpe_api drv_mei_cpe ledtrig_usbdev ip6t_REJECT ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables nf_conntrack_ipv6 nf_conntrack nf_defrag_ipv6 pppoatm ppp_generic slhc br2684 atm ipv6 drv_ifxos arc4 crypto_blkcipher ltq_hcd_vr9 gpio_button_hotplug
[57731.228000] Process hostapd (pid: 969, threadinfo=82d76000, task=82d34da8, tls=778b9440)
[57731.228000] Stack : 82d76000 82d77b18 00000008 832a7eec 8324d400 833b033b 00000001 831a0000
[57731.228000]    00000038 832a8004 00000000 833b05a7 00000000 831a03b4 fffffffb 801f28e0
[57731.228000]    00000000 830f0c18 830f1194 fffffffe 83361398 8329a440 82d77ac0 801f28e0
[57731.228000]    00100100 00200200 82cf6500 833b03c8 833b0000 830f0000 00000000 83361398
[57731.228000]    00000000 831d54e0 82cfc600 00000008 833613a8 fffffffc 83361398 82d77be0
[57731.228000]    ...
[57731.228000] Call Trace:
[57731.228000] [<8020a064>] queue_delayed_work_on+0x4c/0xc8
[57731.228000] [<832a8004>] ieee80211_set_key_rx_seq+0x4ac/0x508 [mac80211]
[57731.228000]
[57731.228000]
[57731.228000] Code: 7c420400 10400008 24030001 <c2020000> 00432025 e2040000 1080fffc 00000000 08082824
[57731.460000] ---[ end trace 9229c1ddddc69ea2 ]---

Post #93

dziny

14 Feb 2015, 19:13

s7a7ic wrote:

My vdsl.bin extracted from Firmware_Speedport_W921V_1.21.000.bin
Size: 761108 (743.3 K)
MD5: 59dd9dc81195c6854433c691b163f757
Looks like you have still the Firmware-Blob from Rylos Image. I think after a "restore defaults" it get's restored, so you have to copy the working binary into /lib/firmware after every restore again.

When using this firmware I'm getting
DSL_CPE: Wrong combination of DSL PHY Firmware and hybrid type used! Please change one of it.
after I do vdsl_cpe_control --c.

My config is as you recommend:

config atm-bridge 'atm'
        option vpi '1'
        option vci '32'
        option encaps 'llc'
        option payload 'bridged'

config interface 'wan'
        option ifname 'nas0'
        option proto 'pppoe'
        option username 'foo'
        option password 'bar'
        option ipv6 '0'
        option macaddr 'e8:de:27:d1:xx:xx'

config interface 'wan6'
        option ifname '@wan'
        option proto 'dhcpv6'

config vdsl 'dsl'
        option annex 'b'
        option firmware '/lib/firmware/vdsl.bin'
        option tone 'bv'
        option xfer_mode 'atm'

Any thoughts?

Post #94

hecatae

14 Feb 2015, 22:59

I'm still using:

BusyBox v1.22.1 (2014-09-17 15:50:14 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
 -----------------------------------------------------
 BARRIER BREAKER (Barrier Breaker, r42943)
 -----------------------------------------------------
  * 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:~#

as I have had dlna issue with newer versions, and still debugging the issue

Post #95

int0x13

20 Feb 2015, 17:03

Hello i have recently got this modem router for 50€ on amazon. I want to install Openwrt, but i find the wiki is not clear at some point.
Some questions:

1)Why not make a direct link to the file instead of the directory???
The file to flash is this one right?
http://downloads.openwrt.org/barrier_br … rade.image

Is it the one you all use here?
2)It is not clear if we can install openwrt thought tplink web interface? Or serial console only?
3)If serial console only, in the wiki it's mentioned:
"Download the openwrt-lantiq-xrx200-TDW8970-uImage-initramfs image from wherever you can find it (the official release does not supply a uImage with an initramfs, so booting that just gives you an error about a missing root filesystem.)"
Why the hell dont you provide a link or upload the file you're referring to in the openwrt foler? this one:
http://downloads.openwrt.org/barrier_br … iq/xrx200/
So why is there anyway this file if you say it's not working:
http://downloads.openwrt.org/barrier_br … 970-uImage
Thank you to clarify the procedure!

Post #96

int0x13

23 Feb 2015, 17:22

Ok after 2 days of work i've finally manged to install OpenWrt, i used the method proposed by RyLos here (and his firmware):
https://forum.openwrt.org/viewtopic.php … 74#p223474

Now i have (of course) some issues:
1)I cant mount a usb key (formated into fat32) I dont know why this command dont work
root@OpenWrt:/tmp# mount /dev/sda1 /mnt/usbkey/
mount: mounting /dev/sda1 on /mnt/usbkey/ failed: Invalid argument

I guess there is some missing module, but i was not able to fix it even i have tried many thing.
I even had a kernel panic when i plugged the usb

2)The boot is very slow, there gaps between the boot process sometimes 30s between the next step in the bootlog. The ping responds only after somthing like 100s

Post #97

HerrBert

23 Feb 2015, 17:31

Hi there,

i want to flash the original tp-link firmware, but i dont have an image..
Is anyone here who can send me the origial TP-Link-Image for the TP-Link 8970B?

That would be realy nice!!!!
Thanks a lot!

Post #98

int0x13

23 Feb 2015, 17:54

HerrBert wrote:

Hi there,
i want to flash the original tp-link firmware, but i dont have an image..
Is anyone here who can send me the origial TP-Link-Image for the TP-Link 8970B?
That would be realy nice!!!!
Thanks a lot!

You flashed openwrt and you're not happy with it (i can understand i have also some problems) and want flash back the stock firmware?

Post #99

HerrBert

24 Feb 2015, 09:47

int0x13 wrote:

HerrBert wrote:
Hi there,
i want to flash the original tp-link firmware, but i dont have an image..
Is anyone here who can send me the origial TP-Link-Image for the TP-Link 8970B?
That would be realy nice!!!!
Thanks a lot!
You flashed openwrt and you're not happy with it (i can understand i have also some problems) and want flash back the stock firmware?

Hi int0x13,

yes thats right! I mean openWRT is good, but i need the switch to seperate vlans etc.. and im not able to install the switch drivers... I think the stock Firmware is for it good enough..
So do you know where i get this image to flash it with uboot?

Thanks a lot!!

Post #100

dziny

24 Feb 2015, 12:08

I don't have any issues with the switch vlans on openwrt, all works just fine. If you are running Rylos firmware just sysupgrade to the official w8970 image
http://downloads.openwrt.org/barrier_br … rade.image
This image has all kernel modules available for the switch to work. I was also running Rylos before and has run into the issue that some modules were unavailable for that image.

Can't help you with going back to the official image though, I would image it would entail stripping some bytes from the official image file and then upload it via the serial port.

Sorry, posts 101 to 100 are missing from our archive.

Page 4 of 16