Buggy v34 firmware. Losing VDSL Modem Sync

[mawheele]

Just want to let Billion know that v34 of the new firmware seems to include an extremely flaky update to the VDSL modem. V32 has been rock solid for me for months. I updated the firmware as I do have both an Apple TV and and XBOX for which the firmware says there are undefined improvements. Following the update, the VDSL modem would drop the connection 1-2 times per day and as a consequence I've lost some synch speed now I'm now back on V32 and no issues.

Infinity on Zen Internet. Synch was 18.5, now down to 16.4 - 1.17 up.

Any thoughts?

[billion_fan]

Just want to let Billion know that v34 of the new firmware seems to include an extremely flaky update to the VDSL modem. V32 has been rock solid for me for months. I updated the firmware as I do have both an Apple TV and and XBOX for which the firmware says there are undefined improvements. Following the update, the VDSL modem would drop the connection 1-2 times per day and as a consequence I've lost some synch speed now I'm now back on V32 and no issues.

Infinity on Zen Internet. Synch was 18.5, now down to 16.4 - 1.17 up.

Any thoughts?

Firmware has been pulled, (it was using a different DMT code) we should have a newer firmware that will have the xbox and apple tv improvements, and the same DMT code as d32 (v32) soon

I'll post a link here once I get it

[billion_fan]

Latest firmware with correct DMT code can be found on the link below (firmware 2.50a.d36)

http://www.billion.uk.com/esupport/inde ... on-250ad36

[mawheele]

Awesome - thank you. Looks steady for the past 4 or so hours. Just need the sync rate to step back up to prior levels now. I guess that may require a few days more stability.

[Radiocrazy]

Just want to let Billion know that v34 of the new firmware seems to include an extremely flaky update to the VDSL modem. V32 has been rock solid for me for months. I updated the firmware as I do have both an Apple TV and and XBOX for which the firmware says there are undefined improvements. Following the update, the VDSL modem would drop the connection 1-2 times per day and as a consequence I've lost some synch speed now I'm now back on V32 and no issues.

Infinity on Zen Internet. Synch was 18.5, now down to 16.4 - 1.17 up.

Any thoughts?

Well I never!! I have had the same problem since I updated the firmware on Wednesday to 34 and I have just seen the post just flashed etec8900ax2400_2.50a.d36.afw so I will report back

[Radiocrazy]

I have had only one disconnection so far around 5:00am and since then not lost a connection up time is now 16 hours, so a vast improvement so I'm back to the stability of the stock firmware I can describe exactly what happened with V.34.
1. I would have a connection that the stats report a download speed of 34 Mbps but running any speed test would spike up to near 30 Mbps but would
fall very quickly to a very erratic speed varying around 18 to 22 Mbps.
2. After this eventually within 2 hours no throughput just a connection both the DSL LED and the Internet LED would be still showing a connection.
3. Eventually the internet LED would go out followed very quickly by the DSL LED after the modem re-synced the internet LED came on and the whole
process would start again.
4. The only spanner in the works is using an openreach modem using the WAN port this would work better in respect that the speed would not be
erratic but eventually still the internet LED would go out on the Billion but the openreach modem would not lose sink and only rebooting the Billion
would bring the internet LED back on and restore internet access.

I will not do any more experiments this end I will just see how long I can continue on the V.36 firmware without losing sync.

[Radiocrazy]

Dropped the line at 04:30:57, I managed nearly 2 days. So far the best firmware for stability is the stock firmware (etec8900ax2400_2.50a.d32.afw) which I have reached 6 days with, I'm going to give it another go then I'm running my 7800 with the openreach modem for a test, which in the past has gone months without a single disconnection. Unless I do the same with the 9800 what do you think?

Service Support = PTM(2)
Sep 6 04:30:57 kern warn kernel: HOST XTM tx ch 0 disabled.
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: ReprogramRxPaf traffictype 2
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: ReconfigureSAR port 0 traffictype 0
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: Normal(XTM/PTM) Mode enabled
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: DS xDSL G.inp Mode = DISABLED
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: ATM Bonding configured in system. Fallback mode = Enabled
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: Bonding State is DATA_IDLE
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: SID MODE SET to 12 BIT MODE
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: ATM Bonding Mgmt Log Area = 8fa31d00
Sep 6 04:30:59 kern info kernel: device ptm0 left promiscuous mode
Sep 6 04:30:59 kern info kernel: device ptm0 entered promiscuous mode
Sep 6 04:30:59 kern info kernel: device ptm0 left promiscuous mode
Sep 6 04:31:21 kern crit kernel: Line 0: VDSL G.993 channel analysis
Sep 6 04:31:22 kern crit kernel: Line 0: VDSL2 link up, Bearer 0, us=6755, ds=36193
Sep 6 04:31:22 kern warn kernel: bcmxtmcfg: DS xDSL G.inp Mode = DISABLED
Sep 6 04:31:22 kern warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP(1), Service Support = PTM(2)

[billion_fan]

Dropped the line at 04:30:57, I managed nearly 2 days. So far the best firmware for stability is the stock firmware (etec8900ax2400_2.50a.d32.afw) which I have reached 6 days with, I'm going to give it another go then I'm running my 7800 with the openreach modem for a test, which in the past has gone months without a single disconnection. Unless I do the same with the 9800 what do you think?

Service Support = PTM(2)
Sep 6 04:30:57 kern warn kernel: HOST XTM tx ch 0 disabled.
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: ReprogramRxPaf traffictype 2
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: ReconfigureSAR port 0 traffictype 0
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: Normal(XTM/PTM) Mode enabled
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: DS xDSL G.inp Mode = DISABLED
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: ATM Bonding configured in system. Fallback mode = Enabled
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: Bonding State is DATA_IDLE
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: SID MODE SET to 12 BIT MODE
Sep 6 04:30:57 kern warn kernel: bcmxtmcfg: ATM Bonding Mgmt Log Area = 8fa31d00
Sep 6 04:30:59 kern info kernel: device ptm0 left promiscuous mode
Sep 6 04:30:59 kern info kernel: device ptm0 entered promiscuous mode
Sep 6 04:30:59 kern info kernel: device ptm0 left promiscuous mode
Sep 6 04:31:21 kern crit kernel: Line 0: VDSL G.993 channel analysis
Sep 6 04:31:22 kern crit kernel: Line 0: VDSL2 link up, Bearer 0, us=6755, ds=36193
Sep 6 04:31:22 kern warn kernel: bcmxtmcfg: DS xDSL G.inp Mode = DISABLED
Sep 6 04:31:22 kern warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP(1), Service Support = PTM(2)

v32 and v36 have the same DMT code, so we expect the same performance.

We will have a major update coming soon, so it might be worth waiting for this release, before testing again.

[Radiocrazy]

Thanks for that i was thinking about flashing back to V32 but i will wait if it's the same DMT code it would be a pointless exercise, I understand that it's a major rewrite of the firmware has everything been rewritten e.g. the modem side as well.

[billion_fan]

Thanks for that i was thinking about flashing back to V32 but i will wait if it's the same DMT code it would be a pointless exercise, I understand that it's a major rewrite of the firmware has everything been rewritten e.g. the modem side as well.

That's correct, I will be testing the firmware over the weekend, and if all goes well, I will release the firmware next week