Tiny Core Base > Raspberry Pi

USB gadget kernel module with RPi zero

<< < (16/18) > >>

creitzel:
Alright, I guess I'm done with this experiment.  I can't figure out how to change the device descriptor on the pi (in fact I haven't seen anything that looks like its even doable). 

Win10 is now recognizing the device as a generic usb hub, still reporting the device descriptor error, and Ubuntu reports it as a usb hub as well. 

Based on the fact that there are several write-ups where people have claimed to get this working, my guess is that the current versions of Ubuntu, and Win10 have changed how they query devices, and that the g_ether code isn't up to date with those changes.

I guess I'll go back to trying to get ssh working via bluetooth.

Rich:
Hi creitzel
Did you load the  g_ether.ko  driver:

--- Code: ---modprobe g_ether
--- End code ---

Have you looked at this:
https://www.olimex.com/forum/index.php?topic=8239.0

creitzel:
Hi Rich,

yes I loaded the g_ether module.  I included a line in bootlocal.sh which did that modprobe statement.  Everything looks great on the pi-zero side, no errors, and I can verify that the dwc2 and g_ether modules are loaded using lsmod. 

The problem is when I connect the usb to a host computer, both Win10, and Ubuntu Mate 22.04 are identifying the pi as a "generic usb hub", rather than an RNDIS Ethernet device.  This appears to be a common problem from what I've read on the internet, and the solution posted in all of those threads is to just force windows to load the proper driver for the device. 

That said, Win10 no longer allows you to do this.  I have been trying all night to get Win10 to allow me to install the RNDIS driver, and it just won't allow it.  It looks like maybe they've beefed up security or something, to disallow it. 

I don't know that there is much more I can do with it.  It appears to me that the g_ether module, and the gadget framework might be out of date with what the newer versions of the OS's are doing to query device descriptors or something.

Juanito:
Is it worth trying usb modeswitch?

Rich:
Hi creitzel
This link looks kind of interesting:
https://wiki.t-firefly.com/en/Firefly-Linux-Guide/demo_usb_ethernet.html

This section mentions load order of the modules is important:
https://wiki.t-firefly.com/en/Firefly-Linux-Guide/demo_usb_ethernet.html#kernel-settings

This section also appears to be relevant:
https://wiki.t-firefly.com/en/Firefly-Linux-Guide/demo_usb_ethernet.html#network-sharing-to-realize-pc-internet-access
To check  net.ipv4.ip_forward  execute this:

--- Code: ---tc@E310:~$ sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 0
tc@E310:~$
--- End code ---
To enable it, execute this:

--- Code: ---tc@E310:~$ sudo sysctl net.ipv4.ip_forward=1
net.ipv4.ip_forward = 1
tc@E310:~$
--- End code ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page