Powering Vim3 on POE with the extender board - works as expected though thats all thats working.
I have an issue where no matter what mode I’m in (USB3 or PCIe) I can’t see the POE NIC or the NVMe, (yes i’m rebooting after changing).
Have cleaned all contacts - just to make sure but not helped.
Tried with latest Ubuntu and Debian from the Khadas repo’s using krescue.
The NVMe is the same recommended.
Networking, ip addr only shows eth0 & wlan0, lspci shows nothing, lshw just shows the wlan and eth0.
If anyone has this working or if support can let me know if I have a broken M2X - do let me know, purchased this as a dev board for an upcoming project in-which we plan to use these boards, there must be something missing - ie. kernel module or other, or there is no support or the board is broken.
Nope the drives raw, seems like the board is not functional. Neither of the components work or can be seen and have seen this asked a lot in the forum with no real outcome.
I have my M2X board mounted to the Edge-V, so I cannot check LAN right now. I will attempt to check SSD connected directly to the VIM3 tonight. I will use latest Krescue Ubuntu for the test.
To confirm, your SSD does not show up in Gparted’s devices?
Thanks - exactly what I have done - used the khadas builds, non work thus far.
Checked the NVMe on my laptop and desktop - no issues, just in the slot (its warm to the touch too).
Networks my biggest concern
I’m not seeing it in the system, so i wont show in gparted!
Yeah, I understood but could not post until now @Gouwa
Here you go, will downgrade to 4.* as someone mentioned a bug with 5 gen kernels.
My main need is both NICs operating the NVMe is a bonus if that also can start to work.
Hello Is the problem with the POE Ethernet Port already fixed?
On my VIM3Pro with extension board, i cant bring up the POE Ethernet port.
Only the adapter on the main board is working.
The ssd on the extensionboard is working.
No Sir, still not working even though I have near on asked for this 1000 times.
If you have found a solution or if @Frank or anyone else knows - add below please.
Its very frustrating and some misunderstanding be that on purpose or by accident, the port does not work.
Or add this to the boot.int file after section echo “Booting mainline kernel…”;.
fdt get value eth0_phy /soc/bus@ff600000/mdio-multiplexer@4c000/mdio@0/ethernet-phy@0 phandle;
fdt set /soc/bus@ff600000/mdio-multiplexer@4c000/mdio@1/ethernet_phy@8 phandle <${eth0_phy}>;
fdt rm /soc/bus@ff600000/mdio-multiplexer@4c000/mdio@0/ethernet-phy@0 phandle
fdt get value eth0_pins /soc/bus@ff600000/bus@34400/pinctrl@40/eth phandle;
fdt set /soc/bus@ff600000/bus@34400/pinctrl@40/eth-leds phandle <${eth0_pins}>;
fdt rm /soc/bus@ff600000/bus@34400/pinctrl@40/eth phandle
fdt rm /soc/bus@ff600000/bus@34400/pinctrl@40/eth-rgmii phandle
fdt set /soc/ethernet@ff3f0000 phy-mode “rmii”;
fdt set /soc/ethernet@ff3f0000 pinctrl-0 <${eth0_pins}>;
fdt set /soc/ethernet@ff3f0000 phy-handle <${eth0_phy}>;