1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

ADSL2MUE modem part seems dead (not whole device bricked)

Discussion in 'Other Linksys Equipment' started by silicium, Oct 22, 2007.

  1. silicium

    silicium LI Guru Member

    It seems ADSL2MUE has a hardware issue with modem part :thumbdown:
    I bought one in 2005. It failed to keep stable connections after a few days online. Then connection success rate went lower and lower down to the point it was dead and I returned it to Linksys. It took several months to get a new one, in the meantime I bought and used a Netgear DG632 which never failed even on a very long landline with a low noise margin.
    When I got the new ADSL2MUE, I tested it during a few days and it was OK (with both original 4.1x firmware and 2.17-TI), even with original power supply. This was last year. DG632 says the DSL line is G.DMT, 1216/320 kb/s down/up. ATM settings are VCMUX, VPI/VCI=8/35.
    Yesterday I unpacked and tested it again... it failed like the previous one: OK during a few hours, then unable to keep the DSL connection, then unable to establish any connection: forever loop {DSL led blinks, then is on, internet led goes from down to red, then DSL led goes down}.
    All of this has been verified with 4.12-EU, 4.22-EU and 2.17-TI firmwares.
    Connection has been tested with both builtin PPPoA and bridge mode with dialup connection on computer.
    At first sign of failure, I remembered the power supply issue and plugged a 5V 12A SMPS with adjustable output voltage set at 5.10V. All testing has been done with it.
    Does anyone want it for free ? I don't need it any more and it may work on another line. At worst you will get a half-bricked device still useful for alternative firmware development & testing and other LAN appliance usage.
    Here is the syslog:

    Valid Configuration Tree
    NTP Polling Timer for DHCP Started succesfully.
    DSL Polling Timer Started succesfully.
    doing modulation_set.
    Firewall NAT service started
    Bridge Created: br0
    /dev/led file could not be opened
    Bridge Created: br1
    Bridge Interface Added: eth0
    Bridge Interface Added: usb0
    DSL Carrier is down2
    DSL Carrier is pass
    DSL Carrier is up
    ---}}} Start of connection delayed for 56 sec
    PPPoA launch delay.
    DSL Carrier is down2
    DSL Carrier is pass
    DSL Carrier is up
    DSL Carrier is down2
    DSL Carrier is pass
    DSL Carrier is up
    DSL Carrier is down2
    DSL Carrier is pass
    PPPoA Launch after conn delay timeout ...
    pppd 2.4.1 started by root, uid 0
    Connect: ppp0 {--}
    local IP address 90.*.*.*
    remote IP address 90.*.*.*
    primary DNS address 80.*.*.*
    secondary DNS address 81.*.*.*
    PPPoA Connect with IP Address 90.*.*.*
    PPPoA Connection Successfully Established
    PPPoA Connect with Gateway IP Address: 90.*.*.*
    DSL Carrier is up
    PPPD Successfully Started
    DSL Carrier is down2
    DSL Carrier is pass
    DSL Carrier is up
    PPPD Terminated Through Signal
    Connection terminated.
    pppd 2.4.1 started by root, uid 0
    connect(8.35): Device or resource busy
    System Call Error
    DSL Carrier is down2
    DSL Carrier is pass
    DSL Carrier is up
    pppd 2.4.1 started by root, uid 0
    connect(8.35): Device or resource busy
    System Call Error
    DSL Carrier is down2
    DSL Carrier is pass
    DSL Carrier is up
    pppd 2.4.1 started by root, uid 0
    connect(8.35): Device or resource busy
    System Call Error
    pppd 2.4.1 started by root, uid 0
    connect(8.35): Device or resource busy
    System Call Error
    pppd 2.4.1 started by root, uid 0
    connect(8.35): Device or resource busy
    System Call Error
    pppd 2.4.1 started by root, uid 0
    connect(8.35): Device or resource busy
    System Call Error
    pppd 2.4.1 started by root, uid 0
    connect(8.35): Device or resource busy
    System Call Error
     
  2. mstombs

    mstombs Network Guru Member

    Hi,

    I doubt you have a hardware failure, just a firmware incompatibility plus the poor design of this device!

    You could try Routertech firmware on the ADSL2MUE, you will see it is a development of the Ti example code in 2.17Ti. It has much newer DSP drivers - I recall the old 2.17Ti uses V3, the Linksys firmware V4. Default in Routertech is V6.2, or optionally V7.1.

    But, there have been mixed reports from France, one user can sync at 20Mbps in ADSL2+ with upgraded PSU. Another cannot get any version other than original Linksys 4.12 to lock on for more than a few seconds.

    The latest DSP drivers seen are DSP7.4, and if you are about to throw the device away I find my 'test' modem can run the very new beta Acorp firmwares for the LAN122 from here:

    http://mcmcc.bat.ru/acorp/LAN122/

    Note this uses a recent Ti core system, reverting to older versions may not be easy.
     
  3. silicium

    silicium LI Guru Member

    Hi, thanks for your alternative firmware proposition, but I am now hoping I won't even need it... The admin of french forum jelnet.free.fr questioned the quality of the line. I should have tested the cable too... the poor design you mention means that my problems came from using my Netgear router's DSL cable and filter (I swapped only routers and power supplies). I plugged the filter and cable from the Linksys box, then my ADSL2MUE has almost one hour uptime with good connection and downloaded more than 250MB from a Linux ISO image... To everybody, FILTER AND DSL CABLE QUALITY MATTERS !
    I can give one reason why there are mixed reports from France... I am afraid France Telecom could not hire enough qualified DSL technicians. I know at least one technical college whose networking classrooms still had outdated X25 and ISDN hardware in 2004, they had many big Cisco routers but no recent WAN hardware and only bought a mini DSLAM in 2005.
     
  4. mstombs

    mstombs Network Guru Member

  5. silicium

    silicium LI Guru Member

    Update - bad news, it did not hold up longer than one hour. Thank you for the report. I will flash alternative firmwares without placing any more hope in this poor design. AR7 chip may not be at fault because my Netgear DG632 is AR7-based too. Anyway my next purchase will avoid this chip.
     
  6. mstombs

    mstombs Network Guru Member

    Good luck - note that the AR7 is just the main chip, the router manufacturers have to add power supplies and DSL transformers etc. I've seen elsewhere where a D-Link AR7 may work where a Linksys one won't - I suspect a subtle mix of firmware version and default configuration that is hidden from the web interface.

    The Netgear GPL source DG632_V3.6.0C_38_src looks interesting because it appears to be complete and buildable, which is unusual for Ti AR7 releases!
     
  7. R0ut3r

    R0ut3r Network Guru Member

    same, identical problem. with mine 2!! adsl2mue
    all kinds of firmwares tryed, but no chance to have a "BIT" stable connection (10 minutes at the moment can be a success. in the past works well )
    np at all with other brands modem, and some other linksys router

    and is a normal provider, with a 8,35 pppoe/pppoa connection (my provider support both)
    i haven't tryed to change the adsl filter, but the power supplyer and the tel cable doesn't help
    and manymanymany firmwares
     
  8. silicium

    silicium LI Guru Member

    Better news before having a good night... Tried RouterTech firmware v2.3, it seems successful. Only two DSL disconnects after booting, then WAN has one hour uptime with p2p running. I will increase p2p load then add heavy ftp downloads to see if it crashes. Thanks for Routertech advice.
     
  9. R0ut3r

    R0ut3r Network Guru Member

    i hope that u solve the issue
    if all is ok, plz, can u explain exaclty what u do?
    regards
     
  10. mstombs

    mstombs Network Guru Member

    Are you happy with that? I still have a problem in that it can take a minute to sync, but now disconnects are very rare...

    Note if you have loaded the 4Mb flash version it has an alternative version 7.1 DSP driver than be forced to load at boot (see docs for env variable to set). Now you are on Routertech firmware there is also a new tool to look at what the modem reports about the DSL connection and gives you access to some tweaks. See http://www.routertech.org/viewtopic.php?p=23297 for more info, my current system (heavily tweaked/patched!) attached
     

    Attached Files:

  11. silicium

    silicium LI Guru Member

    >Are you happy with that?
    I *was* but the same defect came back this morning :thumbdown:. Then I flashed Acorp firmware, but the DSL led kept blinking either with MULTI_MODE or my ISP (DMT) settings. Then I bricked it after going back to an old firmware, ftp-adam2 disconnected in the middle of mtd0 transfer (with correct env), PCTool 2.3 freezed, PCTool 2.1 died after downloading, and eventually de-bricked it with reset button and RouterTech was back. I am going to try dsp71A...
     
  12. mstombs

    mstombs Network Guru Member

    Note the red power LED at least will be wrong with Acorp firmware - but I guess you also had no internet access... I also have had problems with PC-Tool (it works for some people and sometimes worked for me...) - I generally use the raw ftp commands.
     
  13. silicium

    silicium LI Guru Member

    DSP71A did not help :wall: despite my short line. It is stored back in the attic until I can test on someone else's line.
     
  14. R0ut3r

    R0ut3r Network Guru Member

    hi, in the past i have tryed pretty all the solutions wihtout success (on 2 different adsl2mue), but my adsl2mue disconnects with a very high rate (5/60 sec)
    happy to read, if u solve the problem
    plz let me know

    (obv like reported before no problem (for moths: is not the line!) with other modems/routers models: anly the adsl2mue have prob)

    regards
     
  15. silicium

    silicium LI Guru Member

    Are these two routers similar enough to flash the Linksys with the Netgear firmware ? Building seems impossible without their Linux distro called Montavista that must be expensive.
     
  16. mstombs

    mstombs Network Guru Member

    I will try sometime, I thought about trying firmware on my test box, but I think the bootloader is ADAM2, ADSL2MUE is pspboot, so incompatible.
    Montavista is not only expensive they won't even talk to you if you request their "Preview Kit" which is built from modified GPL source they have stolen - but there are plenty of copies of the pre- built toolchain available from Linksys or Acorp etc though.
     

Share This Page