Finally solved the problem...
Nothing related to the firmware. It was the vmware driver issue that changed setting from v4 to v5
Finally solved the problem...
Nothing related to the firmware. It was the vmware driver issue that changed setting from v4 to v5