amtm Segmentation Fault in AMTM

[Diamond67]

Managed to get amtm working somehow. But had to reinstall Entware, which caused some problems. First of all, which one to choose?

The Entware repository for your router no
 longer receives updates from the Entware team.

 However, there's an Entware backports repository available
 by @garycnew with updates for some packages.
 For more info see here:
 snbforums.com/threads/entware-armv7sf-k2-6-eos.89032/

 Be aware that some of these backported packages
 may not be compatible or functional on your router.

 The use of the Entware backports repository can be
 enabled at any time after installation.

 1. Use original Entware repository only.
 2. Use Entware backports repository in parallel.

Anyway, I did choose the 1.

Then:

Found compatible previous Entware
    installation on this device.

Next question was this:

 1. Reuse previous Entware installation
 2. Return to device/server selection

I took advantage of the previous Entware Installation (which obviously was the wrong choice, because the original problem eventually came back after installing Diversion).

I could see the r option and did reset (option 1, only amtm). And I could update the scripts. But as said, eventually no luck, because the "illegal instruction" was there again.

I have no time to struggle with this today. Maybe tomorrow I could start again and reset using the 2. option (if I can get that far):

1. Reset amtm.
    This resets amtm and its own settings.
    Third-party scripts are NOT affected.

 2. Reset amtm, remove scripts and Entware.
    This resets amtm and its own settings
    and removes all third-party scripts,
    including Entware (if installed).
    Third-party scripts WILL be removed.

 3. Remove Entware.
    This removes the Entware repository.
    Third-party scripts depending on Entware
    may no longer work after removing.

 

[Diamond67]

Btw, managed to run the dcl command (to check the Disk Check Log) after a cold start. Seems that both USB flash drives are OK?

Mon Sep  1 13:55:03 DST 2025 Probing 'vfat' on device /dev/sda1
 Running disk check with command 'fatfsck -a' on /dev/sda1
 fatfsck 3014.9.11
 Checking boot region...
 Checking fsinfo region...
 Checking FAT tables...
 Checking root directory...
 Checking directory structure and allocations...
 Checking FAT table allocation...
 Using 1751295/1945600 clusters.
 Clearing dirty flag...
 Repair finished with no repaired inconsistencies.
 File system is clean.
 Mon Sep  1 13:55:15 DST 2025 Disk check done on /dev/sda1

 Mon Sep  1 13:55:29 DST 2025 Probing 'ext4' on device /dev/sdb1
 Running disk check with command 'e2fsck -p' on /dev/sdb1
 ASUSENTWARE: recovering journal
 ASUSENTWARE: clean, 793/1892352 files, 6253282/7567356 blocks
 Mon Sep  1 13:55:33 DST 2025 Disk check done on /dev/sdb1
_____________________________________________

 END FILE

 

[Diamond67]

Maybe tomorrow I could start again and reset using the 2. option (if I can get that far)

Problem solved. I hope.

Did the amtm reset, using the 2nd option

2. Reset amtm, remove scripts and Entware.
    This resets amtm and its own settings
    and removes all third-party scripts,
    including Entware (if installed).
    Third-party scripts WILL be removed.

Then, installed Diversion (and Entware automatically), restored fresh Diversion settings from my backup (from email inbox) using WinSCP. Installed Skynet and other scripts. Took some time but everything went alright.

There was no need to format the Entware USB Flash Drive. Just created the Swap File. Although I did a backup of all documents etc. which were located in the drive, all seemed to be intact and fully functional.

edit: Disk Check log showed no trouble with Flash Drives. So, it seems that just the amtm/Entware or whatever got corrupted and needed a reinstall.
edit2: Afterwards I had a tiny situation with IP addresses because I had forgotten to import my .csv file to YazDHCP. Easy to fix though.