hippy wrote: ↑
Tue Sep 24, 2019 7:26 pm
You could also try setting up your Pi as some other gadget to see if the PC recognises that, which could help narrow down the issue. Setting it up as an MSD g_mass_storage device is easy enough and all modern PC's should recognise that.
That should give some indication on whether there is a hardware problem.
For what it's worth, I've had success runing a 4B as a USB ethernet gadget via the USB C port with a linux USB host (actually a Pi 1B running raspbian). That was with g_ether rather than the manual setup via libcomposite.
Now, and this is going to get somewhat technical...
I suspect that @dibner is using windows on his desktop PC as BSOD is, in my experience, not a linux thing. Natively, windows only has drivers for RNDIS USB ethernet dongles, linux has drivers for both RNDIS and CDC. g_ether may be presenting to the host as the wrong type. I've no idea how it decides which to use.
While I don't have the link to hand, I believe that by using libcomposite instead of g_ether it's possible to force which of RNDIS or CDC is presented to the USB host.
To establish whether it's an OS related issue, get hold of a live linux CD/USB stick, boot the desktop from that and connect the Pi. If that works it's a fair indication that the problem is in the installed OS on the desktop and not in the hardware. If so, try uninstalling any and all USB ethernet drivers present in that OS.
@dibner: It would likely help us help you if you told us what OS is running on your laptop and on your desktop as well as whether the host ports are USB2 or USB3.
Attempts to contact me outside of thes forums will be ignored unless signed in triplicate, sent in, sent back, queried, lost, found, subjected to public enquiry, lost again, and finally buried in soft peat for three months and recycled as firelighters