@otca
I have a suggestion, you re-burn the jetson orin system and then don't do any configuration with jetson-io, follow the steps on our wiki exactly step by step.
If the i2c still doesn't work, I can only suspect that your board has a damaged hardware interface to the i2c.
@otca
"You did the right thing.
The Jetpack 4.6.5 version of the kernel does not yet support the MV series cameras.
Please switch to Jetpack 4.6.4 for your operations.
@otca 
All of this still suggests that i2c is not working.
When I look at your other postings, they seem to say that the camera itself is fine and not broken, right?
@Otca
I wonder if it would be convenient for you to send me your jetson board along with a set of camera boards and we'll test them?
@otca
In fact, when the following pin is high, i2cdetect should be able to show 0x3b that the device is online. This has nothing to do with either ko or dtb.
So I'm wondering why this is the case with your board.
Also, with your current configuration, can you use sudo dmesg and send me all the outputs to look at?
@otca It looks like your Image doesn't contain the patches needed by the mv camera, so it reports an error: unrecognised data type.
Can I ask you the hardware and software version of your board, and which Image you replaced in it is from github?
@otca It looks like the driver is reporting an error. Suggest you don't use the jetson-io mechanism and try strictly following the steps on our wiki.