35b and/or g.vector support?

[infabius]

Hi u can try to make a new update with 35b on vdsl settings?

[negan07]

The profiles available depend on adsl broadcom driver strictly (providers too). Broadcom must provide the support if any: nothing else to do.

Actually there is: ADSL PHY: AnnexA version - A2pvbH042n.d26b Binary file is: adsl_phy.bin Executable is: xdslctl Profiles are: 8a 8b 8c 8d 12a 12b 17a 30a

Drivers are usually low level monolithic code. Sometimes with a little bit of luck, it should be possible to try to find out an updated adsl_phy.bin broadcom driver and the related xdslctl (ARM compatible) from other source codes of other brands with v35b support.

Actually adsl_phy.bin version is A2pvbH042n.d26b In any case an updated one is appreciated.

[superpippo82xxx]

i've a zyxel router with this firmware: ADSL PHY: AnnexA version - A2pvfbH043e.d26n $ adsl profile --show

Modulations: G.Dmt Enabled G.lite Enabled T1.413 Enabled ADSL2 Enabled AnnexL Enabled ADSL2+ Enabled AnnexM Enabled VDSL2 Enabled VDSL2 profiles: 8a Enabled 8b Enabled 8c Enabled 8d Enabled 12a Enabled 12b Enabled 17a Enabled 30a Disabled 35b Enabled US0 Enabled Phone line pair: Inner pair Capability: bitswap On sra On trellis On sesdrop Off CoMinMgn Off 24k On phyReXmt(Us/Ds) Off/On Ginp(Us/Ds) On/On TpsTc AvPvAaPa monitorTone: On dynamicD: On dynamicF: Off SOS: On Training Margin(Q4 in dB): -1(DEFAULT)

adsl_v35b.zip

[negan07]

good job

which zyxel model exactly ?

[superpippo82xxx]

zyxel VMG8823-B50B

[infabius]

https://mega.nz/#F!Pd8TgAJA!t-Yj3SktM8dNqvoIwiWbmg New driver adsl and more

[negan07]

bad news and good news the xdslctl seems compatible with the arch but it needs some shared libs: libbcm_crc.so libbcm_flashutil.so so they are needed to try it

more i have looked the adsl drivers deeply and i've seen that adsl_sdram is versioned too so it should be better to have adsl_sdram of the same version ...043e.d26n too

[superpippo82xxx]

i can't find adsl_sdram... Here missing library lib.zip

[negan07]

bad news and good news

the bad one is that trying to install the adsl driver above with 35mhz vectoring not working here's the dmesg log output:

*** dslThread dslPid=2288
BcmAdsl_Initialize=0xBF152028, g_pFnNotifyCallback=0xBF187E4C
AdslCoreSetSDRAMBaseAddr: pAddr=0x0FE00000 sdramPageAddr=0xCFE00000
BcmAdslCoreCalibrate: (cnt1-cnt)=0x039388d7, adslCoreCyclesPerMs=1000007, BCMOS_MSEC_PER_TICK =1
AdslCoreSetSdramImageAddr: lmem2=0x10500000, sdramSize=0x19d460
pSdramPHY=0xCFFFFFF8, 0x1B7749 0xDEADBEEF
AdslCoreSetSdramImageAddr: sdramPageAddr=0xcfe00000, sdramImageAddr=0xcff00000, sdramPhyImageAddr=0x10500000
*** AdslCoreSetXfaceOffset: data[0]=0xFFFFFE6F data[1]=0x190 ***
Failed to read SDRAM image from '/etc/adsl/adsl_phy.bin'.
AdslCoreHwReset:  Failed to load ADSL PHY image (0)
AdslCoreSetSdramImageAddr: lmem2=0x10500000, sdramSize=0x19d460
pSdramPHY=0xCFFFFFF8, 0xB0AF 0xF8FFBD27
AdslCoreSetSdramImageAddr: sdramPageAddr=0xcfe00000, sdramImageAddr=0xcff00000, sdramPhyImageAddr=0x10500000
*** AdslCoreSetXfaceOffset: data[0]=0xFFFFFE6F data[1]=0x190 ***
Failed to read SDRAM image from '/etc/adsl/adsl_phy.bin'.
AdslCoreHwReset:  Failed to load ADSL PHY image (0)
AdslCoreSetSdramImageAddr: lmem2=0x10500000, sdramSize=0x19d460
pSdramPHY=0xCFFFFFF8, 0xB0AF 0xF8FFBD27
AdslCoreSetSdramImageAddr: sdramPageAddr=0xcfe00000, sdramImageAddr=0xcff00000, sdramPhyImageAddr=0x10500000
*** AdslCoreSetXfaceOffset: data[0]=0xFFFFFE6F data[1]=0x190 ***
Failed to read SDRAM image from '/etc/adsl/adsl_phy.bin'.
AdslCoreHwReset:  Failed to load ADSL PHY image (0)
dgasp: kerSysRegisterDyingGaspHandler: dsl0 registered 
ADSL led state change to <2>
bcmxtmcfg: DS xDSL G.inp Mode = DISABLED 
bcmxtmcfg: xDSL G.Fast Mode = DISABLED 
XTM Init: Ch:0 - 1553 rx BDs at 0xffdbc000
XTM Init: Ch:1 - 16 rx BDs at 0xffde6000
bcmxtmrt: PTM/ATM Non-Bonding Mode configured in system
bcmxtmcfg: Out of sequence call to XTM_ASM_HANDLER::Uninitialize().  Recovering.
bcmxtmcfg: ATM Bonding configured in system. Fallback mode = Enabled 
bcmxtmcfg: Bonding State is DATA_IDLE 
bcmxtmcfg: SID MODE SET to 12 BIT MODE 
bcmxtmcfg: ATM Bonding Mgmt Log Area = c715dd08 

the main reason is: Failed to read SDRAM image from '/etc/adsl/adsl_phy.bin'. so _adslsdram is mandatory and must be founded out to make further experiments

the good news is that searching in the link proposed above there are other adsl driver versions, of the A2pvbH series and of the A2pvfbH series (35b ?): A2pvbH - 042r 042u A2pvfbH - 043f 043g 043k the one proposed above is the A2pvfbH043f the original built in driver is the A2pvbH042n

Trying out the most recent built A2pvbH042u looking good.

# xdslctl profile --version
xdslctl version 1.2
ADSL PHY: AnnexA version - A2pvbH042u.d26b

Can't say what performance differences are there in brief, but working.

[negan07]

bumping this issue because while working on dsl tweaks & fixes some interesting came out

xdslctl not revealing all its stuffs on --help like --vectoring option

typing:

xdslctl info --vectoring You can see the vectoring state i have response:

Vectoring state: 5
VCE MAC Address: 0:0:0:0:0:0
Total error samples Ethernet pkts sent: 0
Total error samples Ethernet pkts discarded: 0
Total error samples statuses sent: 0
Total error samples statuses discarded: 0

according to this definitions:

#define VECT_WAIT_FOR_CONFIG  0
#define VECT_FULL             1
#define VECT_WAIT_FOR_TRIGGER 2
#define VECT_RUNNING          3
#define VECT_DISABLED         4
#define VECT_UNCONFIGURED     5

it looks unconfigured but there's nothing to do for configuring

xdslctl.bin configure --vectoring on (xdslctl.bin to skip the configure parser)

option unable

[0d1n0]

the main reason is: Failed to read SDRAM image from '/etc/adsl/adsl_phy.bin'. so adsl_sdram is mandatory and must be founded out to make further experiments

---

adsl_sdram.bin is generated when you build kernel image .... so the base of generation is the binary drivers probably. i'm investigating about it.

[0d1n0]

Some News, I just loaded without problem adsl driver A2pvbH042j2.d26b of a tplink VR2800 V1 and it seem to work without problem on my D7000 with original xdsctl. you don't need sdram.bin but only '/etc/adsl/adsl_phy.bin and to be binary version aligned adsldd.ko module of same firmware version.however i didn't change adsldd on my d7000. My d7000 firmware is D7000-V1.0.1.64_1.0.1-ancistrus_negan07-build-289.img.

root@D7000:$ xdslctl --version xdslctl version 1.2 ADSL PHY: AnnexA version - A2pvbH042j2.d26b root@D7000:$ www root@D7000:$ xdslctl info xdslctl: ADSL driver and PHY status Status: Showtime Last Retrain Reason: 8000 Last initialization procedure status: 0 Max: Upstream rate = 969 Kbps, Downstream rate = 18420 Kbps

I cannot test vdsl link because i have adsl+ only. Probably the error is due to incompatibility between adlsdd module of version 42 and version 43 of firmware broadcom.If this is true you need a adlsdd.ko version aligned to load 43 firmware phys binary.

[0d1n0]

Ok i just loaded firmware B2pvfbH043g.d26p and A2pvfbH043i1.d26p on my D7000 . The problem was adsldd.ko. The first version seem have some problem to connecto to dslam but second version give me adsl stream.

dgasp: kerSysRegisterDyingGaspHandler: dsl0 registered ADSL led state change to <2> dslThreadTerminate: Unlocking dslThread dslPid=31683 dslThread: Exiting dslThreadTerminate: Exiting kerSysDeregisterDyingGaspHandler: dsl0 is deregistering kerSysDeregisterDyingGaspHandler: dsl0 is deregistered dslThread dslPid=1682 BcmAdsl_Initialize=0xBFB11028, g_pFnNotifyCallback=0xBFB49150 AdslCoreSetSDRAMBaseAddr: pAddr=0x0FE00000 sdramPageAddr=0xCF800000 AdslCoreSetSdramImageAddr: lmem2=0x10500000, pgSize=0x800000 sdramSize=0x19E628 AdslCoreSetSdramImageAddr: lmem2(0x500000) vs ADSL_PHY_SDRAM_BIAS(0x500000); origAddr=0xCFD00000 newAddr=0xCFD00000 pSdramPHY=0xCFFFFFF8, 0x1B782B 0xDEADBEEF AdslCoreSetSdramImageAddr: sdramPageAddr=0xcf800000, sdramImageAddr=0xcfd00000, sdramPhyImageAddr=0x10500000 AdslCoreSetXfaceOffset: data[0]=0xFFFFFE6F data[1]=0x190 XfaceOffset: 0x190 => 0x190 AdslCoreSetSdramTrueSize: data[0]=0x9730DDFF data[1]=0x68CF2200 AdslCoreSetSdramTrueSize: data[0]=0xFFDD3097 data[1]=0x22CF68 PhySdramSize got adjusted: 0x19E628 => 0x22CF68 AdslCoreSharedMemInit: shareMemSize=864368(864368) AdslCoreHwReset: pAdslX=0xfc700190 AdslCoreHwReset: pAdslX->sdramBaseAddr=0x0000d0af, pAdslX->gfcTable[]=0x0000d0cf, adslCorePhyDesc.sdramImageAddr=0xcfd00000 AdslCoreHwReset: pLocSbSta=c1768000 bkupThreshold=3072 AdslCoreHwReset: AdslOemDataAddr = 0xCFE5FDD0, time=12 ms VersionInfo: B2pvfbH043g.d26p BcmDiagsMgrRegisterClient: 0 *** dgasp: kerSysRegisterDyingGaspHandler: dsl0 registered ADSL led state change to <2> BcmAdsl_Initialize=0xBFB11028, g_pFnNotifyCallback=0xBFB49150 dgasp: kerSysRegisterDyingGaspHandler: dsl0 registered ADSL led state change to <2> BcmAdsl_Initialize=0xBFB11028, g_pFnNotifyCallback=0xBFB49150 dgasp: kerSysRegisterDyingGaspHandler: dsl0 registered ADSL led state change to <2>

oot@D7000:$ cd /tmp/x root@D7000:$ ./xdslctl profile --show

Modulations: G.Dmt Enabled G.lite Enabled T1.413 Enabled ADSL2 Enabled AnnexL Enabled ADSL2+ Enabled AnnexM Disabled VDSL2 Enabled VDSL2 profiles: 8a Enabled 8b Enabled 8c Enabled 8d Enabled 12a Enabled 12b Enabled 17a Enabled 30a Enabled 35b Enabled US0 Enabled Phone line pair: Inner pair Capability: bitswap On sra Off trellis On sesdrop Off CoMinMgn Off 24k On phyReXmt(Us/Ds) Off/On Ginp(Us/Ds) On/On TpsTc AvPvAa monitorTone: On dynamicD: On dynamicF: Off SOS: On Training Margin(Q4 in dB): -1(DEFAULT)

root@D7000:$ ./xdslctl --version ./xdslctl version 1.2 ADSL PHY: AnnexA version - A2pvfbH043i1.d26p

[negan07]

good work post here the driver binary files you obtained to make some tries (adsldd.ko & phy.bin)

compiling kernel the driver is simply copied from a dir to another because it comes already as a binary standalone

but the driver version is not the real problem because also 042u can work with vectoring

the problem is maybe as you found out the adsldd.ko against a compatible kernel

http://forum.kitz.co.uk/index.php/topic,20343.255.html this router DGA4130 (and also many similar brands all around with different names) has 35b vect support and uses the same broadcom kernel 3.4 of D7000 and includes the already tested 042u

it should be useful to extract from DGA4130 firmware the driver binaries (better the entire dump filesystem)

these routers are branded but the can be unlocked: they should include ssh so it should be easy to dump the binary files on local machine using scp

If someone is able to find out / dump / receive the binary adsl driver files from DGA4130 or similar post them here they could result useful.

At least some of the files involved should be located at /lib/modules and they are:

bdmf.ko
rdpa_gpl.ko
rdpa.ko
rdpa_mw.ko
chipinfo.ko
bcmxtmrtdrv.ko
bcmxtmcfg.ko
pktflow.ko
pktrunner.ko
adsldd.ko
bcm_enet.ko
nciTMSkmod.ko
bcmvlan.ko
pwrmngtd.ko
rdpa_cmd_tm.ko
rdpa_cmd_spdsvc.ko
rdpa_cmd_ds_wan_udp_filter.ko
rdpa_cmd_dr.ko
/usr/sbin/xdslctl

with: bcmxtmrtdrv.ko bcmxtmcfg.ko adsldd.ko xdslctl

mostly involved

[0d1n0]

Above diagram illustrate dependencies and links involved in adsl vdsl drivers of broadcom sdk. So all modules present should be of the same sdk version to avoid issues.

[0d1n0]

Follow a partial list of some models that have 35b support at least in latest firmaware images: Asus DSL_AC87VG Asus DSL-AC88U Tplink Archer VR2800V1 Zyxel VMG8823-B50B TIM Technicolor DGA4130 D-Link DVA-5592

[0d1n0]

You are sure that 042u with dga4130 can support 35b? It is tested?

[0d1n0]

http://anonfile.com/L7QfVcdebf/zz.rar adslphy, adsldd.ko and xdsclt used in test

[0d1n0]

I think that 042u cannot support profile 35b but can support vectoring with profile 17a and 30a. (max 100 or 200 mbits).I think that support for 35mhz band 35b AnnexQ 300mbits is present only with 43 version of broadcom drivers. inside the firmware image you should check xdslctl about presence of 35b or BrcmPriv1 profile .

[0d1n0]

Ok should be solved 042u support 35b probably. The issue is that you should update xdslctl with the adsl_phy.bin to manage new settings. I have one that seem compatible but should be better to recover original xdslclt that came with adsl_phy.bin to be version aligned. Of course we need somebody with a 35b profile active to test that driver work properly.

here the link to binary xdslclt http://anonfile.com/Ded9Wad2b3/xdslctl xdsctl profile --show

OLD COMMAND: VDSL2 Enabled VDSL2 profiles: 8a Enabled 8b Enabled 8c Enabled 8d Enabled 12a Enabled 12b Enabled 17a Enabled 30a Enabled US0 Enabled Phone line pair: Inner pair

---

NEW COMMAND

    VDSL2   Enabled
    Gfast   Disabled

VDSL2 profiles: 8a Enabled 8b Enabled 8c Enabled 8d Enabled 12a Enabled 12b Enabled 17a Enabled 30a Enabled 35b Enabled US0 Enabled Phone line pair: Inner pair

[negan07]

tested the above driverset with newer 043i1 and different adsldd.ko xdslctl

the good news is that there is a valid carry but no valid connection both xdslctl give same result

reverting back to old original xdslctl with new adsldd.ko module gives segfault and the newer driver without adsldd.ko can't handle carry

there is (only) to find out the right driverset: at least adsldd.ko, adsl_phy.bin & xdslctl DGA4130 looks to be compiled with the same toolchain & share the same kernel

[0d1n0]

http://anonfile.com/K1K8aee2b9/AGTEF1.0.4.rar in the file binaries (kernel and userspace) of dga4130 version 1.0.4 that use A2pvbH042u. Last version of firmware is 1.10 but it use A2pvfbH043k and i think that you should substitute every kernel dependent modules to work properly . In the help of xdslctl there is no 35b profile but probably you can activate it with xdslctl configure --profile BrcmPriv1 command line. Adsl part of driver work properly on my d7000 tested with only substitution of adsl_phy.bin and xdslctl but i cannot test vdsl.

[negan07]

BrcmPriv1 should be the same of 35b: drivers may have different aliases

if the latest agev version hasn't updated kernel (very useful should be a full compiling source pack of it) it still should have 3.4.11 so the updated modules may match.

But in the actual situation it should be a good goal to have a 35mhz profile working anyway.

[0d1n0]

Yes BrcmPriv1 is 35b: old internal name probably (Broadcom Private 1???) .I can get 1.10 without problem but i suggest to test 1.0.4 set of module to see if they work as i expect. here 1.10 set http://anonfile.com/L9A8b0edbf/AGTEF1.1.rar Sources objects are more difficult to get.... but probably we can request it see link below https://www.technicolor.com/distribute/home-experience/regulatory-information

[negan07]

Very Good. Doing some tests of it then will see if packaging all the driverset or at least adsldd.ko & bins

[negan07]

Testing the 042u phy with d26o dd full driver package from agev 1.0.4 and the connection looking good with adsl/vdsl

pktflow/runner and xtms look to match

xdslctl looks similar to the original: vectoring info is hidden and no show also for BrcmPriv1

vectoring/BrcmPriv1 still to test

[0d1n0]

Yes BrcmPriv1 not show on help but should be valid profile with command xdslctl configure --profile BrcmPriv1. Probably an early version of xdslctl of broadcom sdk not fully updated with description.

[negan07]

full driverset 042u.d26o uploaded to repository: if vectoring & 35mhz is available there should be nothing more to do

[j27h]

Great work, let's wait for some test (unfortunately I am only got an ADSL line). If everything is going to work as expected, do you think it will be useful to test also the 043kdriver of the 1.10 AGEV firmware?

[negan07]

already tested 043k.d26r but no carry: and a msg error appears at every xdslctl invocation maybe adsldd.ko is the issue other modules and library seems to load successfull

did agev bumped kernel in the meanwhile ?

didn't try 043k.d26o but shouldn't make so practical difference

[Coliuto]

Hi negan, I've tried the latest firmare 322 with a VDSL 35b (using the package xdsl-driver-full-new) but unfortunately it does not work. As you can see from these screens: https://i.imgur.com/eH2b6o8.png - https://i.imgur.com/rabrREL.png There's something else I could try to make it work? Thank you.

[negan07]

no carry and no link or carry and no link ? from the image seems connected

tried to force profile manually with

xdslctl.bin configure --profile BrcmPriv1

?

post also dmesg output after cmd execution

[Coliuto]

Yes, the VDSL is connected. Leaving the "auto-sync mode" it syncs only in 17a. Forcing the 35b profile from the webgui ( https://i.imgur.com/rabrREL.png ) can't sync at all. Concerning the command you told be above: https://i.imgur.com/C8uW5QJ.png If I try "xdslctl --profile BrcmPriv1" (without the .bin), the command work but the line sync up in 17a.

I've made all those tests using the following firmware: https://files.fm/u/azdn4jtu Does it contain everything necessary to make the 35b work? Thanks.

[negan07]

this package must be installed: opkg update && opkg install xdsl-driver-full-new

the --profile option with or without .bin should be the same

any dmesg output after

xdslctl.bin --profile BrcmPriv1 ?

[Coliuto]

The package is already installed but using the command "xdslctl.bin" same result: https://i.imgur.com/ZeG8wE8.png

[negan07]

type dmesg after cmd execution and post here display content

[0d1n0]

i think that xdslctl.bin --profile BrcmPriv1 is not the right command right syntax should be xdslctl.bin configure --profile BrcmPriv1

[negan07]

yes profile not including configure if running xdslctl configure after setting the gui should be the same: the profile is not actived the dmesg output should be useful to see if it reports an error message maybe moreover, the vendor ID version I see in the screen is the Broadcom 177.28, not one of the last: this is another evaluation parameter

[0d1n0]

Yes could be that dslam have some problem if it 177.28 with 35b. 177.152 seem to be without problem with 35b.

[Coliuto]

type dmesg after cmd execution and post here display content

Now the command seems to be working but no synchronization at all. This is the output with dmesg:

D7000 login: admin Password: admin@D7000:$ xdslctl.bin configure --profile BrcmPriv1 admin@D7000:$ dmesg t: MAC address: -- -- -- -- -- --

[DoCreateDeviceReq.780]: register_netdev done bcmxtmcfg: Reserve TxQueueIdx=0 for vcid 0 bcmxtmrt: Traffic Type is 2. TxPAF control-0. Disable RDP-US-Bonding. bcmxtmrt: Egress TM Q 0 Setup. Buffering/Q - 128 bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=21600000, DS=106622000 ptm0.1 MAC address set to --:--:--:--:--:-- netdev path : ptm0.1 -> ptm0 BCMVLAN : ptm0 mode was set to RG wan interface=[ptm0.1], index=21 wan interface=[ppp1], index=22 lan interface=[group1], index=15 netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN. group1: port 3(eth3) entered disabled state eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 10 mbps full duplex group1: port 3(eth3) entered forwarding state group1: port 3(eth3) entered forwarding state group1: port 3(eth3) entered forwarding state group1: port 5(wl0) entered disabled state device wl0 left promiscuous mode group1: port 5(wl0) entered disabled state device wl0.1 left promiscuous mode group1: port 7(wl0.1) entered disabled state group1: port 6(wl1) entered disabled state device wl1 left promiscuous mode group1: port 6(wl1) entered disabled state eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN. group1: port 3(eth3) entered disabled state eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 1000 mbps full duplex group1: port 3(eth3) entered forwarding state group1: port 3(eth3) entered forwarding state group1: port 3(eth3) entered forwarding state device wl0 entered promiscuous mode group1: port 5(wl0) entered forwarding state group1: port 5(wl0) entered forwarding state device wl0.1 entered promiscuous mode group1: port 6(wl0.1) entered forwarding state group1: port 6(wl0.1) entered forwarding state device wl1 entered promiscuous mode group1: port 7(wl1) entered forwarding state group1: port 7(wl1) entered forwarding state device wl1.1 entered promiscuous mode group1: port 8(wl1.1) entered forwarding state group1: port 8(wl1.1) entered forwarding state group1: port 5(wl0) entered forwarding state group1: port 6(wl0.1) entered forwarding state group1: port 7(wl1) entered forwarding state group1: port 8(wl1.1) entered forwarding state group1: port 6(wl0.1) entered disabled state eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN. group1: port 3(eth3) entered disabled state eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 10 mbps full duplex group1: port 3(eth3) entered forwarding state group1: port 3(eth3) entered forwarding state group1: port 3(eth3) entered forwarding state eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN. group1: port 3(eth3) entered disabled state eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 1000 mbps full duplex group1: port 3(eth3) entered forwarding state group1: port 3(eth3) entered forwarding state group1: port 3(eth3) entered forwarding state Line 0: xDSL link down ADSL led state change to <0> bcmxtmcfg: XTM Link Information, port = 0, State = DOWN(2), Service Support = PTM(2) bcmxtmrt: Egress TM Q 0 Shutdown bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0 bcmxtmcfg: ReconfigureSAR port 0 traffictype 0 bcmxtmcfg: Normal(XTM/PTM) Mode enabled bcmxtmcfg: ChipId Rev-b0 bcmxtmcfg: DS xDSL G.inp Mode = DISABLED bcmxtmcfg: xDSL G.Fast Mode = DISABLED bcmxtmcfg: ATM Bonding configured in system. Fallback mode = Enabled bcmxtmcfg: Bonding State is DATA_IDLE bcmxtmcfg: SID MODE SET to 12 BIT MODE bcmxtmcfg: ATM Bonding Mgmt Log Area = c6b84518 bcmxtmcfg: gulXtmMonitorValid(0xbf119e44) = 1 message received before monitor task is initialized kerSysSendtoMonitorTask [sched_delayed] sched: RT throttling activated Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask block items: input:clear

clamp total entry used:0 total count:1148 input str:clear

psd clear oldest entry proc_write_echo_chargen receive: len: 6, input: clear proc_write_echo_chargen receive: clear list Leaving proc_write_echo_chargen : size: 6 netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. netlink: 20 bytes leftover after parsing attributes. message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL link down ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask Line 0: xDSL G.994 training ADSL led state change to <2> message received before monitor task is initialized kerSysSendtoMonitorTask message received before monitor task is initialized kerSysSendtoMonitorTask admin@D7000:$

[Coliuto]

Yes could be that dslam have some problem if it 177.28 with 35b. 177.152 seem to be without problem with 35b.

No, The issue concerning the DSLAM version is relating only at Lantiq chipset. Using broadcom chipset every DSLAM version is ok for 35b. This is my line on the Asus DSL-AC88U (broadcom): https://i.imgur.com/CDlxyle.png https://i.imgur.com/90gTX3l.png

[0d1n0]

which firmware version in these screenshot?

[negan07]

it seems to enter into a training loop...

vectoring is unconfigured on both devices

try activating the 30a profile and see what happen

[0d1n0]

bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=21600000, DS=106622000 in initial handshake is at 100... not 200... could be before command?

[0d1n0]

i found this interesting screenshot in a forum about dga4130 http://forum.kitz.co.uk/index.php?topic=20343.195 original post 347. version A2pvbH042u.d26o

[Coliuto]

which firmware version in these screenshot?

This is the Asus DSL-AC88U with the latest firmware as I wrote above

[Coliuto]

it seems to enter into a training loop... vectoring is unconfigured on both devices try activating the 30a profile and see what happen

The line cant sync in 30a, the only possibilities are 35b and 17a. The 30a is disabled and not used here in Italy. The Vectoring is already active modem-side (as always), but not active DSLAM-side. This is why the indication is 5 with every modem. If they turn on G.Vector on DSLAM (or even the Vectoring friendly mode), it will turn on 1 automatically.

[Coliuto]

bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=21600000, DS=106622000 in initial handshake is at 100... not 200... could be before command?

Yes, those are the values of the previous synchronization, before the "xdslctl.bin configure --profile BrcmPriv1" command

[0d1n0]

@Coliuto did you used in past Version 1.10.03_build398 2017/07/21 of asus DSL-AC88U firmware? if answer is positive this version support 35b profile?

[Coliuto]

On july 2017 you mean? I think yes. This is a screenshot by an italian user on June 2017 and the 35b was already supported by the DSL-AC88U: https://www.hwupgrade.it/forum/showpost.php?p=44848276&postcount=135

[0d1n0]

No this user have upgraded firmware it use 043g not 042j of 1.10.03_build398