84

Hi,

New forum member here with a Fritzbox 7530.

I've been using the version from this thread for about a week and it has been rock solid, so thanks for making it available.

I have a few observations and queries:

  1. The stock AVM software allows you to increase the downstream SNR by 1dB per click of the slider, and it works fine. On this build if I select +1dB (or even -1dB) I still always connect with the same SNR of 5.2dB and the same downstream sync speed of 48.8Mbps.

  2. My upstream sync is always 9.3Mbps with stock software and always 8.4Mbps with this build. Not enough to cry over but I'm not sure why this is. SNR is reported as 6dB on both. I am in the UK and use annex B with tone A.

  3. I can't seem to install luci-app-sqm.

  4. I noticed with the very latest stock AVM software (7.29), the flashing instructions on this site no longer work. I have an old AVM recovery tool that flashes back an older version (7.21), and with that version the flashing instructions DO work. After some experimentation I discovered that with the latest AVM software you need to set your PC to 192.168.1.x instead of 192.168.178.x. Obviously the python script parameter must also be changed to 192.168.1.1. Then it will load the u-boot. I tried again with both AVM versions to make sure I wasn't imagining things. The result is that now you may set your PC to 192.168.1.70/24 (as suggested in step 4) at the very start and use it all the way through the process, which is what I did. I only really mention this in case somebody tries to flash from the latest software and gets stuck.

Apologies for the long first post!

DSL Status
Line State:Showtime with TC-Layer sync
Line Mode:G.993.2 (VDSL2, Profile 17a)
Line Uptime:22h 17m 45s
Annex:B
Data Rate:48.847 Mb/s / 8.407 Mb/s
Max. Attainable Data Rate (ATTNDR):49.727 Mb/s / 8.414 Mb/s
Latency:0.15 ms / 0.00 ms
Line Attenuation (LATN):17.8 dB / 28.4 dB
Signal Attenuation (SATN):17.1 dB / 28.0 dB
Noise Margin (SNR):5.1 dB / 6.1 dB
Aggregate Transmit Power (ACTATP):13.4 dB / 7.0 dB
Forward Error Correction Seconds (FECS):321 / 240801
Errored seconds (ES):0 / 244510
Severely Errored Seconds (SES):0 / 38068
Loss of Signal Seconds (LOSS):0 / 0
Unavailable Seconds (UAS):28 / 28
Header Error Code Errors (HEC):0 / 0
Non Pre-emptive CRC errors (CRC_P):0 / 0
Pre-emptive CRC errors (CRCP_P):0 / 0
ATU-C System Vendor ID:Broadcom 164.161
Power Management Mode:L0 - Synchronized
85

Wait I tought this didn't work with 35b what router is this?

86

It is possible that the AVM firmware uses a different mechanism than OpenWrt for SNR adjustments. Someone would have to look how AVM does this to see if it can be implemented for OpenWrt. However, it is possible that this only works with the DSL firmware from AVM and would also require support for a vendor-specific firmware interface.

Which DSL firmware are you using? I would expect the version extracted from the AVM firmware to perform the same as on stock firmware.

The package depends on a few kernel modules, and the versions of those need to match the kernel in your OpenWrt image exactly. If the OpenWrt image and the modules were not built together, this won't match.

VRX518 does support profile 35b. The supported devices are Fritzbox 7530 and 7520 at the moment.

2 Likes
87

Thanks for you reply. I am using the version of OpenWRT supplied by mm933 earlier in this thread, so whatever driver is in that. I don't know how to use another one.

 OpenWrt SNAPSHOT, r17855-040b8ac240
 -----------------------------------------------------
root@OpenWrt:~# /etc/init.d/dsl_control dslstat
{
        "api_version": "4.21.3",
        "firmware_version": "8.12.1.7.1.7",
        "chipset": "Lantiq-VRX500",
        "driver_version": "1.9.3",
88

Ok I worked it out, I extracted vr11-B-dsl.bin from inside the AVM recovery tool, copied it to the router and put the path to the file into the DSL 'firmware file' field, and rebooted.
My upstream speed has now returned to stock software levels (8.4Mbps -> 9.4Mbps).

Note that the AVM recovery tool I used was the one I already had laying around, so the firmware is about 6 months old.

 OpenWrt SNAPSHOT, r17855-040b8ac240
 -----------------------------------------------------
root@OpenWrt:~# /etc/init.d/dsl_control dslstat
{
        "api_version": "4.21.3",
        "firmware_version": "8.13.1.9.1.7",
        "chipset": "Lantiq-VRX500",
        "driver_version": "1.9.3",
89

I have the same problem as @tremowsen.
The Modem syncs good, but the Connection failed.
.... Timeout waiting for PADO packets ...
.... Unable to complete PPPoE Discovery ... in the system log.
I use the last version from janh.
Perhaps something to do with the switch?
Please can you show the complete network and dsl config.
Thank you

90

I had a similiar problem... Check if you get packets from the dslam (with tcpdump) and post the whole log.

91

Here are my logs and configs ...

root@OpenWrt:~# tcpdump -vv -i  ptm0.7
tcpdump: listening on ptm0.7, link-type EN10MB (Ethernet), capture size 262144 bytes
16:08:36.701915 IP6 (hlim 1, next-header Options (0) payload length: 56) :: > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener report v2, 2 group record(s) [gaddr ff02::1:ff11:2233 to_ex { }] [gaddr ip6-allrouters to_ex { }]
16:08:37.104082 IP6 (hlim 1, next-header Options (0) payload length: 76) fe80::ae9a:96ff:fe11:2233 > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener report v2, 3 group record(s) [gaddr ff02::1:ff00:0 to_ex { }] [gaddr ff02::1:ff11:2233 to_ex { }] [gaddr ip6-allrouters to_ex { }]
16:08:37.132001 IP6 (hlim 1, next-header Options (0) payload length: 36) fe80::ae9a:96ff:fe11:2233 > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener report v2, 1 group record(s) [gaddr ff02::1:ff00:0 to_ex { }]
16:08:37.902546 IP6 (hlim 1, next-header Options (0) payload length: 76) fe80::ae9a:96ff:fe11:2233 > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener report v2, 3 group record(s) [gaddr ff02::1:ff00:0 to_ex { }] [gaddr ff02::1:ff11:2233 to_ex { }] [gaddr ip6-allrouters to_ex { }]
16:08:37.982439 IP6 (hlim 1, next-header Options (0) payload length: 36) fe80::ae9a:96ff:fe11:2233 > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener report v2, 1 group record(s) [gaddr ff02::1:ff00:0 to_ex { }]
16:08:40.398674 PPPoE PADI [Service-Name] [Host-Uniq 0x78180000]
16:08:45.404763 PPPoE PADI [Service-Name] [Host-Uniq 0x78180000]
tcpdump: pcap_loop: The interface disappeared
7 packets captured
7 packets received by filter
0 packets dropped by kernel

-> logread ..

Sun Oct 24 16:06:44 2021 kern.info kernel: [  509.423529] vrx518_tc:ptm_stop: ptm stop
Sun Oct 24 16:06:44 2021 daemon.notice netifd: Interface 'wan' is disabled
Sun Oct 24 16:06:44 2021 daemon.notice netifd: Interface 'wan' is enabled
Sun Oct 24 16:06:44 2021 daemon.notice netifd: Interface 'wan' is setting up now
Sun Oct 24 16:06:44 2021 kern.info kernel: [  509.472921] vrx518_tc:ptm_open: ptm open
Sun Oct 24 16:06:44 2021 daemon.err insmod: module is already loaded - slhc
Sun Oct 24 16:06:44 2021 daemon.err insmod: module is already loaded - ppp_generic
Sun Oct 24 16:06:44 2021 daemon.err insmod: module is already loaded - pppox
Sun Oct 24 16:06:44 2021 daemon.err insmod: module is already loaded - pppoe
Sun Oct 24 16:06:44 2021 daemon.info pppd[5538]: Plugin pppoe.so loaded.
Sun Oct 24 16:06:44 2021 daemon.info pppd[5538]: PPPoE plugin from pppd 2.4.9
Sun Oct 24 16:06:44 2021 daemon.notice pppd[5538]: pppd 2.4.9 started by root, uid 0
Sun Oct 24 16:06:59 2021 daemon.warn pppd[5538]: Timeout waiting for PADO packets
Sun Oct 24 16:06:59 2021 daemon.err pppd[5538]: Unable to complete PPPoE Discovery
Sun Oct 24 16:06:59 2021 daemon.info pppd[5538]: Exit.
Sun Oct 24 16:06:59 2021 daemon.notice netifd: Interface 'wan' is now down
Sun Oct 24 16:07:00 2021 kern.info kernel: [  525.273957] vrx518_tc:ptm_stop: ptm stop
Sun Oct 24 16:07:00 2021 daemon.notice netifd: Interface 'wan' is disabled
Sun Oct 24 16:07:00 2021 daemon.notice netifd: Interface 'wan' is enabled
Sun Oct 24 16:07:00 2021 daemon.notice netifd: Interface 'wan' is setting up now


-> /etc/config/network ..

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd37:627c:6da4::/48'

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

config dsl 'dsl'
	option annex 'j'
	option tone 'b'
	option line_mode 'vdsl'
	option firmware '/lib/firmware/vr11-B-dsl.bin'


config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth0'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '192.168.1.1'
	option netmask '255.255.255.0'
	option ip6assign '60'

config interface 'wan'
	option device 'ptm0.7'
	option proto 'pppoe'
	option username 'XXXXXXXXXXXX'
	option password 'XXXXXXXX'
	option ipv6 'auto'

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


config switch
	option name 'switch0'
	option reset '1'
	option enable_vlan '1'

config switch_vlan
	option device 'switch0'
	option vlan '1'
	option ports '1 2 3 4 0'


dslstat
root@OpenWrt:~# /etc/init.d/dsl_control dslstat
{
        "api_version": "4.21.3",
        "firmware_version": "8.13.1.10.1.7",
        "chipset": "Lantiq-VRX500",
        "driver_version": "1.9.3",
        "state": "Showtime with TC-Layer sync",
        "state_num": 7,
        "up": true,
        "uptime": 175,
        "atu_c": {
                "vendor_id": [
                        181,
                        0,
                        66,
                        68,
                        67,
                        77,
                        192,
                        26
                ],
                "vendor": "Broadcom 192.26",
                "system_vendor_id": [
                        181,
                        0,
                        66,
                        68,
                        67,
                        77,
                        0,
                        0
                ],
                "system_vendor": "Broadcom",
                "version": [
                        118,
                        49,
                        49,
                        46,
                        48,
                        48,
                        46,
                        48,
                        57,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0
                ],
                "serial": [
                        80,
                        49,
                        48,
                        74,
                        55,
                        48,
                        48,
                        48,
                        54,
                        57,
                        54,
                        95,
                        50,
                        50,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0,
                        0
                ]
        },
        "power_state": "L0 - Synchronized",
        "power_state_num": 0,
        "xtse": [
                0,
                0,
                0,
                0,
                0,
                0,
                0,
                2
        ],
        "annex": "B",
        "standard": "G.993.2",
        "profile": "17a",
        "mode": "G.993.2 (VDSL2, Profile 17a, with down- and upstream vectoring)",
        "upstream": {
                "vector": true,
                "trellis": true,
                "bitswap": true,
                "retx": true,
                "virtual_noise": false,
                "interleave_delay": 0,
                "data_rate": 36999000,
                "latn": 8.100000,
                "satn": 8.000000,
                "snr": 10.400000,
                "actps": -90.100000,
                "actatp": -2.600000,
                "attndr": 45460000
        },
        "downstream": {
                "vector": true,
                "trellis": true,
                "bitswap": false,
                "retx": true,
                "virtual_noise": true,
                "interleave_delay": 160,
                "data_rate": 89990000,
                "latn": 10.900000,
                "satn": 10.900000,
                "snr": 15.200000,
                "actps": -90.100000,
                "actatp": 14.400000,
                "attndr": 123879424
92

It looks like you don't receive packets from the dslam as you don't have any PADO packets in the trace. The network config should be ok.

Take a look in the logfile... Do you have some message like "vrx518 0000:01:00.0: dc_ep_clk_on failed"?

93

I have looked at the log file.
You're right ..

Sun Oct 24 15:57:04 2021 kern.info kernel: [   11.651926] vrx518: Intel(R) SmartPHY DSL(VRX518) PCIe EP/ACA Driver - version 2.1.0-k
Sun Oct 24 15:57:04 2021 kern.info kernel: [   11.656431] vrx518: Copyright (c) 2016 Intel Corporation.
Sun Oct 24 15:57:04 2021 kern.info kernel: [   11.664363] vrx518 0000:01:00.0: enabling device (0140 -> 0142)
Sun Oct 24 15:57:04 2021 kern.info kernel: [   11.672546] NET: Registered protocol family 8
Sun Oct 24 15:57:04 2021 kern.info kernel: [   11.675350] NET: Registered protocol family 20
Sun Oct 24 15:57:04 2021 kern.info kernel: [   11.683824] vrx518_tc:pcie_ep_probe: Total 1 VRX518 EP detected
Sun Oct 24 15:57:04 2021 kern.err kernel: [   11.696422] vrx518 0000:01:00.0: dc_ep_clk_on failed
Sun Oct 24 15:57:04 2021 user.info kernel: [   11.702216] urngd: v1.0.2 started.
Sun Oct 24 15:57:04 2021 kern.info kernel: [   11.746960] MD5 checksum pass!!!

Do you have the same problems ?

94

I had the same issue, yes. We couldnt figure it out so far, I tried a lot and told Jan about, but only switching the router hardware fixed the problem…

95

What Fritzbox do you have?

AVM 7530 or 7520 ?

I have a 7520

96

7530, but dsl modem should be the same

97

Thanks for the tip with the other Fritzbox.

Oh yes ...
Now I've done a test with an "old" (2 years) Fritzbox 7530. Yes, the pppoe connection works with this box.

It doesn't work with the brand new 7520. Maybe the hardware is slightly different on new boxes

98

I think so, yes...

99

To add some more information about this issue: The message dc_ep_clk_on failed directly after pcie_ep_probe seems to be caused by the EMA hardware unit failing to turn on (see the call tc_clkon(&priv->ep_dev[i], PMU_EMA); in tc_main.c of the TC driver). And It seems that as a result the TX data path does not work. The driver will write the first packet to the hardware ring buffer, but there is never a response from the hardware. The kernel log shows the message transmit queue 0 timed out shortly after.

Does your device work with the vendor firmware?

100

Thank you for your answer @janh

The device has no problems with the original firmware.

101

Can you download the support data from the vendor firmware and check if the same message also shows up there in the dmesg section (you need to do this shortly after boot, but the device does not need to be connected to the DSL line)?

102

@janh

Yes i can do this. Tomorrow I will have access to the device again. I'll do it in the morning.

103

I just noticed that the kernel log in the vendor firmware regularly shows messages like these, which I assume is basically the same thing:

[1245616.372090] desc not available yet
[1245619.459083] rx_desc_process: 14 callbacks suppressed