Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 ... 19 20 [21] 22 23 ... 26

Author Topic: OpenWrt (Chaos Calmer r46559) for ECI/r v1 & v2 - Update: G.INP/ReTX Support  (Read 269499 times)

petervrangel

  • Just arrived
  • *
  • Posts: 5
Re: OpenWrt (Chaos Calmer r46559) for ECI/r v1 & v2 - Update: G.INP/ReTX Support
« Reply #300 on: September 22, 2017, 06:51:31 AM »

Unfortunately on this page only Firmware Version: 5.4.7.9.1.6

fresh for my modem there I did not find.
Logged

ejs

  • Kitizen
  • ****
  • Posts: 2078
Re: OpenWrt (Chaos Calmer r46559) for ECI/r v1 & v2 - Update: G.INP/ReTX Support
« Reply #301 on: September 22, 2017, 04:32:03 PM »

You can take the vdsl.bin file from the firmware for a different device and use it with the ECI modem. Try a .bin file extracted from the Netgear DM200 firmware.
Logged

petervrangel

  • Just arrived
  • *
  • Posts: 5
Re: OpenWrt (Chaos Calmer r46559) for ECI/r v1 & v2 - Update: G.INP/ReTX Support
« Reply #302 on: September 23, 2017, 03:58:55 PM »

Thank you very much, everything turned out with the firmware
dsl_vr9_firmware_xdsl-05.07.09.05.01.07_05.07.03.0F.00.01

connect stat with Home Hub 5a

root@LEDE:~# /etc/init.d/dsl_control status
ATU-C Vendor ID:                          Broadcom 177.174
ATU-C System Vendor ID:                   Broadcom
Chipset:                                  Lantiq-VRX200 Unknown
Firmware Version:                         5.7.9.5.1.7
API Version:                              4.17.18.6
XTSE Capabilities:                        0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex:                                    B
Line Mode:                                G.993.5 (VDSL2 with down- and upstream vectoring)
Profile:                                  17a
Line State:                               UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS):  Near: 0 / Far: 35801
Errored seconds (ES):                     Near: 0 / Far: 24
Severely Errored Seconds (SES):           Near: 0 / Far: 5
Loss of Signal Seconds (LOSS):            Near: 0 / Far: 4
Unavailable Seconds (UAS):                Near: 122 / Far: 122
Header Error Code Errors (HEC):           Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P):        Near: 0 / Far: 0
Pre-emtive CRC errors (CRCP_P):           Near: 0 / Far: 0
Power Management Mode:                    L0 - Synchronized
Latency / Interleave Delay:               Down: Fast (0.18 ms) / Up: Fast (0.0 ms)
Data Rate:                                Down: 50.064 Mb/s / Up: 15.064 Mb/s
Line Attenuation (LATN):                  Down: 18.3dB / Up: 21.7dB
Signal Attenuation (SATN):                Down: 18.3dB / Up: 21.5dB
Noise Margin (SNR):                       Down: 12.6dB / Up: 6.5dB
Aggregate Transmit Power (ACTATP):        Down: 1.4dB / Up: 13.6dB
Max. Attainable Data Rate (ATTNDR):       Down: 92.778 Mb/s / Up: 22.052 Mb/s
Line Uptime Seconds:                      18
Line Uptime:                              18s
« Last Edit: September 23, 2017, 05:49:16 PM by petervrangel »
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 4093
Re: OpenWrt (Chaos Calmer r46559) for ECI/r v1 & v2 - Update: G.INP/ReTX Support
« Reply #303 on: September 23, 2017, 04:04:47 PM »

Thank you very much, everything turned out with the firmware
dsl_vr9_firmware_xdsl-05.07.09.05.01.07_05.07.03.0F.00.01
Can you share the new connecting stats?
Logged
Talktalk FTTP 550/75 - Speedtest - BQM

petervrangel

  • Just arrived
  • *
  • Posts: 5
Re: OpenWrt (Chaos Calmer r46559) for ECI/r v1 & v2 - Update: G.INP/ReTX Support
« Reply #304 on: September 23, 2017, 05:45:18 PM »

B-FOCus V-2FUb/r Rev B

root@LEDE:~# /etc/init.d/dsl_control status
ATU-C Vendor ID:                         
ATU-C System Vendor ID:                   
Chipset:                                  Lantiq-VRX200 Unknown
Firmware Version:                         5.7.9.5.1.7
API Version:                              4.17.18.6
XTSE Capabilities:                        0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex:                                    B
Line Mode:                                G.993.5 (VDSL2 with down- and upstream vectoring)
Profile:                                  17a
Line State:                               UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS):  Near: 0 / Far: 35804
Errored seconds (ES):                     Near: 0 / Far: 24
Severely Errored Seconds (SES):           Near: 0 / Far: 5
Loss of Signal Seconds (LOSS):            Near: 0 / Far: 4
Unavailable Seconds (UAS):                Near: 127 / Far: 127
Header Error Code Errors (HEC):           Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P):        Near: 0 / Far: 0
Pre-emtive CRC errors (CRCP_P):           Near: 0 / Far: 0
Power Management Mode:                    L0 - Synchronized
Latency / Interleave Delay:               Down: Fast (0.18 ms) / Up: Fast (0.0 ms)
Data Rate:                                Down: 50.064 Mb/s / Up: 15.064 Mb/s
Line Attenuation (LATN):                  Down: 18.3dB / Up: 21.5dB
Signal Attenuation (SATN):                Down: 18.3dB / Up: 21.5dB
Noise Margin (SNR):                       Down: 13.0dB / Up: 6.5dB
Aggregate Transmit Power (ACTATP):        Down: 1.1dB / Up: 13.6dB
Max. Attainable Data Rate (ATTNDR):       Down: 94.251 Mb/s / Up: 22.063 Mb/s
Line Uptime Seconds:                      9
Line Uptime:     
« Last Edit: September 23, 2017, 05:48:58 PM by petervrangel »
Logged

reynard80

  • Just arrived
  • *
  • Posts: 1

Although I don't have a ECI/r modem, I do have a Zyxel with the same chipset. I hope you guys are willing to help me with the following problem with seems to be similar to the discussion in this thread.

I have installed LEDE/OpenWRT on my Zyxel with a Lantiq VRX chipset and I am able to connect to my ISP via VDSL2. However, I can't get the same speed as with the stock modem from my ISP. It's the same Zyxel, and I also rooted that modem to get to the Lantiq firmware that my ISP is using. However, I'm still only getting 22/2Mbps on my LEDE modem, where I should be getting 30/3Mbps.

I noted one difference in the line features, namely that bitswap is enabled on both up- and downstream on the stock modem, but on the LEDE modem, it is not enabled on the downstream. How can I enable bitswap on the downstream?

I saw this command on page 1 of the thread, but where do I run it? Should I build a new LEDE image or can I configure these options while the modem is running?

Quote
DSL_CPE#>lfcg 1
nReturn=0 nDirection=1 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=1 bVirtualNoiseSupport=1 b20BitSupport=0

DSL_CPE#>lfcg 0
nReturn=0 nDirection=0 bTrellisEnable=1 bBitswapEnable=1 bReTxEnable=0 bVirtualNoiseSupport=1 b20BitSupport=0

Below is my dsl_control status for reference:

Code: [Select]
Chipset:                Lantiq▒ XWAY▒ VRX268
Firmware Version:       5.7.5.6.1.7
API Version:            4.17.18.6
MEI Version:            1.5.17.6
Power Management Mode:                    L0 - Synchronized
Line State:                               UP [0x801: showtime_tc_sync]
Line Uptime Seconds:                      2275
Line Uptime:                              37m 55s
Resyncs:                1
ATU-C Vendor ID:                          Broadcom 177.28
ATU-C System Vendor ID:                   Broadcom
XTSE Capabilities:                        0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex:                                    B
Line Mode:                                G.993.5 (VDSL2 with down- and upstream vectoring)
Profile:                                  17a
Trellis:                D: ON / U: ON
Bitswap:                D: OFF / U: ON
G.INP:                  D: Enabled / U: Enabled
Virtual Noise Support:  D: Supported / U: Not Supported
Attain Data Rate:       82.487 Mb/s / 52.455 Mb/s
Data Rate:                                Down: 22.400 Mb/s / Up: 2.152 Mb/s
NFEC:                   32 / 32
RFEC:                   16 / 16
LSYMB:                  16 / 16
Interleave Depth:       1 / 1
Interleave Block:       32 / 32
LPATH:                  0 / 0
Line Attenuation (LATN):                  Down: 10.1dB / Up: 9.3dB
Signal Attenuation (SATN):                Down: 10.1dB / Up: 10.5dB
Noise Margin (SNR):                       Down: 20.0dB / Up: 29.2dB
Aggregate Transmit Power (ACTATP):        Down: -12.2dB / Up: 12.7dB
Max. Attainable Data Rate (ATTNDR):       Down: 82.487 Mb/s / Up: 52.455 Mb/s
Forward Error Correction Seconds (FECS):  Near: 0 / Far: 57
Errored seconds (ES):                     Near: 0 / Far: 27
Severely Errored Seconds (SES):           Near: 0 / Far: 18
Loss of Signal Seconds (LOSS):            Near: 0 / Far: 18
Unavailable Seconds (UAS):                Near: 75 / Far: 75
Header Error Code Errors (HEC):           Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P):        Near: 0 / Far: 0
Pre-emtive CRC errors (CRCP_P):           Near: 0 / Far: 0
15m Code Violations:    0 / 0
15m FEC Errors:         0 / 0
1d Code Violations:     0 / 80
1d FEC Errors:          0 / 57
Logged

petervrangel

  • Just arrived
  • *
  • Posts: 5

I'm trying to get a DSL driver out of the Fritz-Box7490 firmware:

7z e FRITZ.Box_7490.en-de-es-it-fr-pl.113.06.53.image -r filesystem.image
     7z e filesystem.image filesystem_core.squashfs
     unsquashfs4-lzma-avm-be filesystem_core.squashfs -e lib / modules / dsp_vr9 /

Please tell me how to unpack filesystem_core.squashfs?

When executing the command:

unsquashfs4-lzma-avm-be filesystem_core.squashfs -e lib / modules / dsp_vr9 /

I get a message:

bash: unsquashfs4-lzma-avm-be: command not found


System:

Linux HPLINUX 4.9.0-4-amd64 # 1 SMP Debian 4.9.65-3 (2017-12-03) x86_64 GNU / Linux

p7zip version 16.02

Thank you.

« Last Edit: March 17, 2018, 11:22:27 AM by petervrangel »
Logged

beetlepart

  • Just arrived
  • *
  • Posts: 1

Please tell me how to unpack filesystem_core.squashfs?

When executing the command:

unsquashfs4-lzma-avm-be filesystem_core.squashfs -e lib / modules / dsp_vr9 /

I get a message:

bash: unsquashfs4-lzma-avm-be: command not found


System:

Linux HPLINUX 4.9.0-4-amd64 # 1 SMP Debian 4.9.65-3 (2017-12-03) x86_64 GNU / Linux

p7zip version 16.02

Thank you.

Download and compile freetz tools, clone from https://github.com/Freetz/freetz.git.  You only need to 'make tools', unsquashfs4-lzma-avm-be will be in the tools folder. NOTE, you may need to change umask to 0022 in order to compile.

[Moderator edited to remove an invalid link.]
« Last Edit: April 11, 2018, 06:12:23 PM by burakkucat »
Logged

ben1066

  • Member
  • **
  • Posts: 74

It has been a very long time since I've posted on this forum, so hi again.

I have just installed the OpenWRT 18.06 RC1 on an ECI/r v2 modem, it boots fine and I can connect over the ethernet connection, all good so far. What I can't seem to do is get the DSL connection working, rendering the device somewhat useless. My line syncs okay with the ECI /i I have been running for years, but under the ECI /r it just cycles between handshake, full_sync, exception, idle request and silent. I'm not really sure what is going on. It did sync once, just after installing OpenWRT, having configured the VDSL settings but without a reboot, since, nothing. Is there a sifferent firmware I should be trying? I'm a little confused.

EDIT: Just flashed back it's stock firmware, starting to think I've been sold a brick unfortunately. Even on stock, after a reset, I'm getting the same 0x1 exception line state  :(

EDIT2: Hm no, my bad. On stock it didn't work initially but after doing a reset with the button on the back it appears to sync up. Then switching back to OpenWRT broke it. Does 18.06 actually work on this device?
« Last Edit: June 30, 2018, 07:32:56 PM by ben1066 »
Logged

bob8

  • Member
  • **
  • Posts: 14

fwiw, I had OpenWRT 18.06 Snapshot working fine on an ECI/r v2 modem when I briefly tested it last month.  I haven't tried RC1 or RC2 though which shouldn't be any different imho.

Are you sure you configured OpenWRT correctly?

I used the Bridge modem LuCI setup instructions found in the 'Install guide for HH5A'.
https://openwrt.ebilan.co.uk/viewtopic.php?f=7&t=266

Have you tried LEDE 17.01.4 which also works just fine?

(I notice 18.06 allows you to adjust the downstream noise margin in LuCI, but I've not test it as I get full line sync speed)
Logged

Adeel567

  • Just arrived
  • *
  • Posts: 6

Hello, I am quite confused right now.
I've got the UART connected, i am pretty certain I have a V1.2. I've got my PC configured using a usb ethernet adapter as 192.168.1.1.
I am not too sure how to set up TFTP on windows but I think it's fine as it has the correct IP.
The main issue is it says this:

Using vr9 Switch device
TFTP from server 192.168.1.1; our IP address is 192.168.1.100
Filename 'openwrt-lantiq-xrx200-VG3503J_V2-squashfs.image'.
Load address: 0x81000000
Loading: T T T T T

and when I ping 192.168.1.1 (my PC) it times out from the modem:

VR9 # ping 192.168.1.1
Using vr9 Switch device
ping failed; host 192.168.1.1 is not alive


The Lan1 light is on but the ethernet lights are not but windows recognises it being there.
any help?

Is it somehow bricked? If so, how can I reverse this.
« Last Edit: July 23, 2018, 04:47:31 PM by burakkucat »
Logged

bob8

  • Member
  • **
  • Posts: 14

Some suggestions.

Edit: use 'server' mode in TFTPD, not 'client' mode.

Whenever I have used TFTPD32/64 in Windows, try placing the VG3503J file in the same program folder as TFTPD*.exe.    Also check the Windows Firewall settings are not blocking the server.

Try a different PC/laptop with a built in ethernet LAN port.

If you are not sure if you have a v1 or v2 modem, there are some internal pics of the Lantiq SoC here
https://openwrt.org/toh/bt/vg3503j
« Last Edit: July 25, 2018, 05:24:50 PM by bob8 »
Logged

Adeel567

  • Just arrived
  • *
  • Posts: 6

Hi,
The large chip is a Lanti(a/q) V1.2
I've even tried the internal ethernet port and tried following the steps on OpenWRT.org. When doing so I was able to ping the modem from the PC but not the other way around. It still will not grab the TFTP file.
Not sure if it matters, but when it boots it says "ping failed; host 1.1.1.1 is not alive" and could it be an issue that mine seems like it is already erased or something where in the guides they are starting with the existing firmware fully running?
« Last Edit: July 25, 2018, 12:49:53 AM by Adeel567 »
Logged

bob8

  • Member
  • **
  • Posts: 14

TBH, I don't know if the ping command actually works from VR9 prompt, or whether your Windows firewall is blocking replies to pings.  Unfortunately, I can't check ping on an ECI modem.

Unless you got as far as executing the 'Erase' command, I think the original ECI firmware is still intact.

Referring to the upgrading from OpenWRT CC15 to LEDE steps in the OpenWRT wiki, I wonder if these commands would be sufficient to reinstate booting the original ECI firmware?

run reset_uboot_config
reset

setenv ethaddr AA:BB:CC:DD:EE:FF  (use MAC address printed on back of modem)
saveenv




« Last Edit: July 25, 2018, 03:13:52 PM by bob8 »
Logged

Adeel567

  • Just arrived
  • *
  • Posts: 6

If I let it boot it says:
Abort
ping failed; host 1.1.1.1 is not alive

Hit any key to stop autoboot:  0

## Checking CFG Image at b07c0000 ...

## Check Primary System Image ...

## Primary System Image Checksum Error !!

## Check Secondary System Image ...

## Secondary System Image Checksum Error !!

## Both Images Corrupted: Please contact with your vendor ##


I will try another PC now. But just to make sure is this how I am meant to setup TFTP (i'm using the OpenWRT link in this test) do I press put?  https://imgur.com/sRFOaos
Hang on, I used TFTP server with windows firewall and any possible conflicting program uninstalled. Renamed the newest lede file to match what i had pasted and it seems to be working so far me thinks. Maybe it actually was the damn firewall? It's taking its time at 1350bytes/sec so I'll feedback if it works.
« Last Edit: July 25, 2018, 02:20:34 PM by Adeel567 »
Logged
Pages: 1 ... 19 20 [21] 22 23 ... 26