Since I'm part responsible for yaltar's mishap I will tread carefully.
G-010S-A / OLT HWTC10 users I did some googling and I found that some Orange installations use a FGS202
https://forum.openwrt.org/t/support-for-gpon-sfp-fgs202/42641 and with the knowledge in that thread you can easily extract the mibs from the bins uploaded.
What caught my eye was the u-boot environment variable
mib_file=HWTC. And it turns out the mibs are named
data_1g_8q and
alu_data_1g_8q just like the MA5671A mib. Since these mibs are designed for use on Orange infrastructure but contain
SCOM identifiers, I modified them to
SMBS using the image stevebrush posted, ie. Vendor ID = SMBS, Version = SMBSSGLBF115, and Equipment ID = SagemcomFast5656OFR. FYI ALU = Alcatel Lucent and I assume the FGS202 mib_file variable picks between the 2.
Use a G-010S-A firmware with omcid
wget -O /tmp/data_1g_8q.ini https://gist.githubusercontent.com/up-n-atom/4dd952ecde3754264e9d2e1bb98414a2/raw/9ba660cc34ed7217e52048e7903251479b88bdc7/data_1g_8q.ini
scp /tmp/data_1g_8q.ini ONTUSER@192.168.1.10:/tmp/
ssh ONTUSER@192.168.1.10
touch /tmp/deamon_sfp.cfg
killall -9 deamon
/sbin/deamon /tmp/deamon_sfp.cfg &
killall omciMgr
killall parser
/opt/lantiq/bin/omcid -d1 -p/tmp/data_1g_8q.ini -o160 -i0 -g1 -l/tmp/omci.log > /dev/console 2> /dev/console &
And yet again I will apologize for my English.
EDIT:
fw_setenv image0_version 'image 0 version here'
fw_setenv image1_version 'image 1 version here'