AVM FritzBox Lantiq-VRX200 and ADSL2+

My TD-8980 died, so I chose the AVM 7360 V2. But now I can't get DSL sync (ADSL2+ Annex A) . I rule out hardware problems because it works with Freetz NG. I have tried many configurations but nothing works. Same situation with AVM 3370, DSL won't synchronize!
Any tips, does it work for anyone?

I am having similar issue on my AVM 3370 converted from German to International.

stock firmware works and connects fine:

ADSL 2+ (ITU G.992.5) Annex A

this is on:

OpenWrt 22.03.6, r20265-f85a79bcb4

/lib/firmware:

lrwxrwxrwx    1 root     root            43 Jan  1  1970 lantiq-vrx200-a-to-b.bspatch -> xcpe_581816_580B11_to_579906_574402.bspatch
lrwxrwxrwx    1 root     root            22 Jan  1  1970 lantiq-vrx200-a.bin -> xcpe_581816_580B11.bin
-rw-r--r--    1 root     root          1920 Nov 25 18:18 xcpe_581816_580B11.LICENSE
-rw-r--r--    1 root     root        898952 Nov 25 18:18 xcpe_581816_580B11.bin
-rw-r--r--    1 root     root        253635 Nov 25 18:18 xcpe_581816_580B11_to_579906_574402.bspatch

ubus call dsl metrics

{
	"api_version": "4.17.18.6",
	"firmware_version": "5.7.9.9.0.6",
	"chipset": "Lantiq-VRX200",
	"driver_version": "1.5.17.6",
	"state": "Silent",
	"state_num": 3,
	"up": false,
	"uptime": 0,
	"atu_c": {
		
	},
	"power_state": "L3 - No power",
	"power_state_num": 3,
	"upstream": {
		
	},
	"downstream": {
		
	},
	"errors": {
		"near": {
			"es": 0,
			"ses": 0,
			"loss": 0,
			"uas": 1456,
			"lofs": 0,
			"fecs": 0,
			"hec": 0,
			"ibe": 0,
			"crc_p": 0,
			"crcp_p": 0,
			"cv_p": 0,
			"cvp_p": 0
		},
		"far": {
			"es": 0,
			"ses": 0,
			"loss": 0,
			"uas": 1456,
			"lofs": 0,
			"fecs": 0,
			"hec": 0,
			"ibe": 0,
			"crc_p": 0,
			"crcp_p": 0,
			"cv_p": 0,
			"cvp_p": 0
		}
	}
}

Maybe this ? Since after 22.03.0-rc4 OpenWrt introduced support to:

Vectoring on Lantiq VRX200 / VR9 - missing callback for sending error samples - For Developers - OpenWrt Forum

So few ADSL/ADSL2+users here are able to test recent changes.
But I assume old fw like 22.03.0-rc1 would work .
Please also test 22.03.0-rc4 if possible.
If we can point any version from where it stopped to work that would be great improvement to bug hunters.

OpenWrt does not support switching the DSL Annex on VR9/VRX200 modems. So you are stuck on whatever the hardware is configured for. On Fritzboxes that is generally Annex B (I don't know if it is different for the "International" variants, or if these also rely on whatever AVM does in the original firmware for Annex switching).

The command dsl_cpe_pipe.sh vig allows to check the hardware configuration. The numerical value nHybrid shows the result:

  1. Annex A (DSL_HYBRID_TYPE_POTS)
  2. Annex B (DSL_HYBRID_TYPE_ISDN_B)
  3. Annex B/J (DSL_HYBRID_TYPE_ISDN_BJ)
  4. universal (DSL_HYBRID_TYPE_UNIVERSAL_VRX500)

My own Fritzbox 7520/7530 devices return the last value, so one of those might also be an option in addition to an actual Annex A device.

1 Like

I assume this is not true since it's confirmed to be working on freetz fw /hacked OEM fw
There might be devices with some HW filters that's forbid other annex but not the one VDSL2 enabled. VDSL is annex-less and do not leave spare bandwidth for ISDN/pots but that you know.

Slightly differently. VDSL does have Annexes as well (A north america, B europe, C japan, that define different band plans, that in turn define the frequencies for the the different up- and download bands). But Annex B for Europe contains different bandplans some sparing POTS and some ISDN bands. The upshot is however that a device compatible with VDSL2 AnnexB likely can not have fixed frequency filters...

See ITU-T G.993.2 for more details and boring standards prose than you might desire :wink:

I am aware that AVM's firmware does allow switching the annexes for ADSL connections (and so it is clear the hardware supports it).

But it does not work in OpenWrt. If you try to use a DSL firmware with non-matching Annex in ADSL mode, the modem won't work. The sub error code reported by dsl_cpe_pipe.sh lecg in this case is 0xf (ALM_ModemFSM_FailReasonGet_S_FW_HYBRID). And dsl_cpe_pipe.sh g997lisg reports a sub status of 5 (LINIT_SUB_FW_HYBRID).

Of course it should be possible to reverse engineer what AVM does in their version of the drivers to make it work, but it looks like so far nobody has done that.

1 Like

I've bought two 3370 Fritz!boxes from ebay. one of them accepts only the International freetz-ng image and the other one only the German one.

both of them connect just fine under Freetz-ng OS on adsl Annex A

both of them can not connect to Annex A under openwrt 24.10

FWIW, my BT Home Hub 5A with openwrt 24.10 & my Netgear DM200 with 23.05 connect fine on Annex A

Edit: some technical info about the boxes I am "playing"

Fritz!box (non-International), openwrt 24.10 (initramfs):

AVM FRITZ!Box 3370 Rev. 2 (Micron NAND)
xRX200 rev 1.1
MIPS 34Kc V5.5
BogoMIPS 331.77

nReturn=0 DSL_DriverVersionApi=4.17.18.6 DSL_ChipSetFWVersion=5.7.9.9.0.6 DSL_ChipSetHWVersion=Unknown DSL_ChipSetType=Lantiq-VRX200 DSL_DriverVersionMeiBsp=1.5.17.6 nHybrid=3

Fritz!box (International), openwrt 24.10 installed in flash:

AVM FRITZ!Box 3370 Rev. 2 (Micron NAND)
xRX200 rev 1.1
MIPS 34Kc V5.5
BogoMIPS 331.77

nReturn=0 DSL_DriverVersionApi=4.17.18.6 DSL_ChipSetFWVersion=5.9.0.13.0.1 DSL_ChipSetHWVersion=Unknown DSL_ChipSetType=Lantiq-VRX200 DSL_DriverVersionMeiBsp=1.5.17.6 nHybrid=3

BT Home Hub 5A, openwrt 24.10 installed in flash:

BT Home Hub 5A
xRX200 rev 1.2
MIPS 34Kc V5.6
BogoMIPS 331.77

nReturn=0 DSL_DriverVersionApi=4.17.18.6 DSL_ChipSetFWVersion=5.9.0.13.0.1 DSL_ChipSetHWVersion=Unknown DSL_ChipSetType=Lantiq-VRX200 DSL_DriverVersionMeiBsp=1.5.17.6 nHybrid=1

Netgear DM200, openwrt 24.10 installed in flash:

Netgear DM200
xRX200 rev 1.2
MIPS 34Kc V5.6
BogoMIPS 334.23

nReturn=0 DSL_DriverVersionApi=4.17.18.6 DSL_ChipSetFWVersion=5.9.0.13.0.1 DSL_ChipSetHWVersion=Unknown DSL_ChipSetType=Lantiq-VRX200 DSL_DriverVersionMeiBsp=1.5.17.6 nHybrid=1

Edit II: I have opened a git ticket about this issue, behavior

1 Like