no RNDIS on milkv duo 64MB Ram about duo-buildroot-sdk

[yevhenboichuk]

Did you try SSH?

[protektwar]

I have tried and it is not working, as there is no rndis device in dmesg on my machine... I can see the default ip address over the serial interface.

[drankinatty]

Linux To Try Again To Disable All RNDIS Protocol Drivers will be a continuing problem that the milkV developers will need to address. The likely cause for your problem is Ubuntu has blacklisted the rndis drivers to prevent them from loading. Then once manually loaded, you then need to enable dhcp on the interface on the Ubuntu box so it receives an IP from the milkv-duo. Then you should be able to ssh [email protected] (or however you have yours configured)

You can check for blacklisted entries in your /lib/modprob.d directory (at least on openSUSE it is /lib/modprobe.d/50-blacklist-rndis.conf)

I suspect you are being hit by this issue. I was on openSUSE. Check to make sure you drivers are loaded, e.g.

$ lsmod | grep rndis
rndis_wlan             69632  0
usb_f_rndis            49152  0
u_ether                32768  1 usb_f_rndis
libcomposite           81920  1 usb_f_rndis
rndis_host             20480  1 rndis_wlan
cdc_ether              24576  1 rndis_host
usbnet                 57344  3 rndis_wlan,rndis_host,cdc_ether
cfg80211             1040384  4 iwldvm,rndis_wlan,iwlwifi,mac80211
configfs               57344  3 usb_f_rndis,libcomposite
usbcore               327680  12 rndis_wlan,xhci_hcd,ehci_pci,usbnet,usbhid,cdc_acm,rndis_host,uvcvideo,ehci_hcd,btusb,xhci_pci,cdc_ether

(side-note, the buildroot-sdk builds fine on Archlinux as well as Ubuntu. The only stray package needed on Archlinux is genext2fs which is available in AUR)

[protektwar]

I have checked for blacklist on /etc/modprob.d and /lib/modprob.d/. There is no indication of a blacklist on my machine. I'm able to load the rndis_host manually, still nothing...

[black-ghost-off]

Try another image version

[protektwar]

Up to now I have tried all the below images, the result is the same:

[drankinatty]

What is your device named? On Ubuntu, do ip addr show and look for the interface that was created. It may be tty.USB0 or a normal interface name like enp2384. The key is that you need to tell Ubuntu that that device gets an IP via dhcp. On both openSUSE and Archlinux, the interface is created, but not enable (e.g. you will see the interface listed as DOWN in the ip link show output)

I don't know what config tool Ubuntu uses to configure network interfaces, but if it has one (wicked, network-manager, etc..), you should be able to configure that interface to get an IP via dhcp and then you will see your host gets an IP like 192.168.42.133. Once you have an IP, then you can connect to the duo on 192.168.42.1.

Post the output of ip addr show and ip link show. (note: don't post images, just copy/paste the text and put 3-backticks above the first line (backtick key is under Esc key) and put the same 3-backticks after the last line and it will format in a fixed font -- or indent it all by 4-spaces)

---

Side note: the Ethernet interface make things much easier. Your router (or whatever server you use on your LAN that hand out address) will just hand the duo and address on your local subnet. (if you solder the pin-header to connect the duo to the USB/Ethernet IOB -- use double-length pin-headers so your GPIO pins will still be available after you snap the duo into the IOB... learned the hard way)

Using the IOB or Ethernet adapter, it helps to modify the /etc/dhcpd.conf on the duo so it provides "milkv-duo" as the hostname -- so your router will update its name resolution table and allow the duo to be reached via ssh root@milkv-duo. The changes needed are to uncomment hostname and comment option host_name, e.g.

...
# Inform the DHCP server of our hostname for DDNS.
hostname
...
# Request a hostname from the network
# option host_name
...

side note -- end

[protektwar]

As already specified, I can see the usb0 and the default ip address on the duo. Here is an printscreen taken from duo, over the UART connection:

I can't see anything on my Ubuntu machine related to RNDIS or related to any usb connection once I connect the duo to USB-C port on my machine. I have checked several cables nothing is happening.

[drankinatty]

Your output on the duo (which is running Arch?) is fine. Ubuntu (your host) is the problem. If you see no interface on the Ubuntu box, and watching the journal when you plug the USB cable in doesn't do show anything other than a USB connection and no network interface setup -- then that is a problem. On the duo (Arch), the interface is set up, but is dnsmasq and dhcp running? (I've never used anything but the default duo image, so I don't know what the Arch image does)

Also remember, on the duo in /mnt/system there is a symlink for usb.sh that either is a link to usb-rndis.sh (meaning the duo USB will function as an RNDIS host with ethernet over USB) or it is a link to usb-host.sh (meaning RNDIS is disabled). If your link is to usb-host.sh, then that is why you computer isn't seeing the duo and not setting anything up when you plug it in. Look at:

# ls -al /mnt/system/usb.sh
lrwxrwxrwx    1 root     root            12 Dec 23 03:37 /mnt/system/usb.sh -> usb-rndis.sh

That shows the proper link for RNDIS. if you see /mnt/system/usb.sh -> usb-host.sh, then you need to fix the link with ls -sf /mnt/system/usb-rndis.sh /mnt/system/usb.sh,

Double check what you have.