A statement from Asus would be good. The fact it's been going on for months suggests it's something that may not be able to be fixed with firmware. Embarrassing if this is the case.
Nov 29 15:56:55 rc_service: tp_init 1313:notify_rc stop_dsl_diag
Nov 29 15:56:57 email: No diagnostic file!
Nov 29 16:01:33 rc_service: hotplug 11750:notify_rc restart_nasapps
Nov 29 16:01:33 kernel: FAT: FAT read failed (blocknr 1247)
Nov 29 16:01:33 kernel: FAT: unable to read inode block for updating (i_pos 5460994)
Nov 29 16:01:34 kernel: FAT: Directory bread(block 341312) failed
Nov 29 16:01:34 kernel: FAT: Directory bread(block 341313) failed
Nov 29 16:01:34 kernel: FAT: Directory bread(block 341314) failed
Code:Nov 29 15:56:55 rc_service: tp_init 1313:notify_rc stop_dsl_diag Nov 29 15:56:57 email: No diagnostic file! Nov 29 16:01:33 rc_service: hotplug 11750:notify_rc restart_nasapps Nov 29 16:01:33 kernel: FAT: FAT read failed (blocknr 1247) Nov 29 16:01:33 kernel: FAT: unable to read inode block for updating (i_pos 5460994) Nov 29 16:01:34 kernel: FAT: Directory bread(block 341312) failed Nov 29 16:01:34 kernel: FAT: Directory bread(block 341313) failed Nov 29 16:01:34 kernel: FAT: Directory bread(block 341314) failed
Argh, looks like I wasted a 24 hour diagnostic run to find it failed. I've formatted my USB stick with NTFS and am trying again.
Might be worth formatting as a Ext3 rather than a native Windows FAT/NTFS
Good point. I'll do that before I start it again.
Ixel, you really need to contact Broadbandbuyer and discuss your options with this device, it's consuming too much of your time and effort trying to remedy what ASUS should have done months ago.
I fell into a 'love/hate' relationship with the device which was hard to break but I'm glad I did.
I've set a deadline of just before Christmas Eve - plenty of time for DLM to react if it's true that it doesn't observe FEC, but the ES figure (which is currently around a few seconds in both directions over a 24 hour timeframe). As I understand it the DLM is back in operation again.
In the meantime do you think I should contact them anyway and explain the situation and my plan? Or should I wait until a few weeks have passed as intended right now?
Something else that i noticed is that asus appear to have told the retailers to get rid and push/sell stock of the Asus DSL-AC68U for example ocuk is constantly selling it on the weekly offer but i am pretty sure it has been on sale for a month now... and other website's are slowly getting cheaper and cheaper the lowest being 160 pounds.
I've asked Paul Lee twice about the power adaptors and had no response, which now makes me wonder even more! I've submitted a diagnostics for him on one of their tools and they're analysing it. If I hear anything I will gladly post any findings.Has anyone had any further contact from Asus on the matter?
I've been in touch with Paul Lee. He told me the diagnostics I sent were clear of CRC errors basically (because I sent him that of my connection being capped at 49Mbps downstream with INP 3 and a delay of 8ms), however I'll be submitting further diagnostics at his request for a different sync rate with both fastpath and interleaving, for 5 hours.
Also as a final note, I've been asked not to share any knowledge of the modem's advanced functionality (which is obvious), hence why I've not shared it on a public forum. This also means requests via PM's or trusts will be ignored so please don't ask me how I'm doing such things. Anyone with such knowledge should also ensure they don't share such knowledge either. I will still continue to share statistics and news here however.
All that matters is that I can hopefully help ASUS get this problem solved by diagnosing various configurations on my line via the modem's firmware at their request.
Keep up the good work - I agree with you or there will be a few broken units (user error)
Yeah. I'm hoping they don't just come back to me and say something along the lines of that they can't help me because I've manually altered some advanced settings, even though those settings only override the sync rate, INP and delay of the modem.
I've told Paul Lee how I've done it, waiting to see what he says.
Yeah. I'm hoping they don't just come back to me and say something along the lines of that they can't help me because I've manually altered some advanced settings, even though those settings only override the sync rate, INP and delay of the modem.
I've told Paul Lee how I've done it, waiting to see what he says.
Tx_CRC[0] = 0
Tx_FEC[0] = 487
Tx_ERR_SEC = 0
Tx_FEC_SEC = 7
Rx_CRC[0] = 659
Rx_FEC[0] = 0
Rx_ERR_SEC = 74
Rx_FEC_SEC = 0
Near-end total: los=0, sef=0, lpr=0
Far-end total: los=1, sef=1, lpr=0
VDSL2 Sync-Up Time: 0 Day(s) 1:10:31