OTG USB not work after connect M2 wifi

I have followed instruction to connect wifi by installing M2 wifi connector from this link
https://devtalk.nvidia.com/default/topic/1045195/jetson-agx-xavier/how-to-connect-nvidia-xavier-to-wifi-network-/
but just using 8260 model.

I also installed intel wireless driver
Intel® Dual Band Wireless-AC 8260 4.1+ iwlwifi-8000-ucode-25.30.13.0.tgz
and cp ucode to /lib/firmware

It seemed to work well, however, I cannot use OTG USB any more, and I lose control.
Only I can do is to ssh from another computer and do some investigation.
I could do iwconfig and it showed wlan0 info. That sound like wifi module works well.
But when I try dmesg, it showed some errors like

[ 38.573726] tegra194-vi5 15c10000.vi: ep of_device is not enabled /host1x/vi@15c10000/ports/port@0/endpoint.
[ 38.575000] tegra194-vi5 15c10000.vi: ep of_device is not enabled /host1x/vi@15c10000/ports/port@1/endpoint.
[ 38.578629] tegra-xusb 3610000.xhci: USB2 port 0 has OTG_CAP
[ 38.579816] tegra-xusb 3610000.xhci: USB3 port 2 has OTG_CAP
[ 38.585055] Could not get extcon-dev /xhci@3610000:id(0)
[ 38.591660] Could not get extcon-dev /host1x/nvdisplay@15210000:typec0(0)
[ 38.592328] Could not get extcon-dev /xudc@3550000:vbus(0)

I tried to remove M2 connector out and restart Xavier, later boot I can use mouse and keyboard via OTG USB.
I could do lsusb also
when no M2 Wifi connector, lsusb showed like below
Bus 002 Device 002: ID 05e3:0617 Genesys Logic, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 046d:c535 Logitech, Inc.
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

However, when I connect M2 Wifi, it showed nothing.

So could you please help to make both works?

Hi lertluck.l,

There are some customers who also suffering this issue. After our investigation, we notice Intel 8260 card would somehow turn off the i2c bus.

This seems an issue from Intel so I can only suggest you to try different cards.