You should definitely try with the systemd-gadgets I linked earlier. It makes all the configuration really easy, you just need to enable the relevant services, so in your case usbgadget-func-uvc.service and gadget-start.service. You also need to copy them beforehand to /etc/systemd/system, including gadget-init.service, and you need to copy gadget to /etc/default/gadget, and the scripts gadget-start.sh and gadget-init.sh to /etc/systemd/scripts. Edit /etc/default/gadget to edit the configs and names of the gadget, and then start gadget-start.service. No need to enable gadget-init.service, it’s called as a dependency from other services.

There’s an install script in the repo that you can use as well, setup.sh, and a PKGBUILD so you can create an Arch package. After installing with either method, just change /etc/default/gadget, enable the uvc and gadget start services, and then just start the gadget start service,

Hey, if you ever create that, give me a shoutout, I’d love to see it.

No, unfortunately not :/

That’s just the “name” of the configuration, for instance in my USB ethernet gadget I use both c.1 and c.2 as config names, and not a.1.

Yeah, it’s a bit weird that it works like that. I’ll be honest, in the last three or four years that I’ve been tinkering with USB gadgets, I’ve never noticed that those symlinks you create should be broken until you mentioned it. I just kinda took it for granted that it works (probably because I never had issues with this part of the process).

I’ve got some experience with Linux USB gadgets, and can confirm that the docs definitely aren’t wrong, as I’ve used them myself to write gadgets using the same symlink commands that the docs mention and that OP used here.

I’ve got a working USB ethernet gadget and MTP gadget for the Steam Deck that make the same link that should be broken, and here’s a repo that implements every USB gadget with almost every gadget making the same symlink, one directory up from where OP does it. I’ve tested all the gadgets from that repo and they all work, and because they work, I’ve forked the repo here for future use in the above mentioned Steam Deck plugin.

I can pretty confidently say that it’s not a broken symlink. I’m not 100% sure why this doesn’t work for OP, but I think it’s most likely an issue with not loading the correct driver for the UVC function.

No, this is ConfigFS, the linux kernel’s special filesystem for configuring kernel stuff, and for some reason that I don’t really know, it doesn’t matter if the symlink is relative or not. The kernel documentation even creates a relative symlink from the same directory as OP did here.

Hmm, not sure then. It seems correct to me. Check out this repo, it has systemd services for all the USB gadgets, you can run uvc very easily with this: https://github.com/BigfootACA/systemd-gadget

I can write specific instructions how to get this working later today, if you’ll need them.

Normally, you’d be right, but this special filesystem doesn’t care about that. I’ve done similar with different gadgets so many times, always with relativr symlinks, sometimes directly from the root of the special filesystem, sometimes from the gadgets own subdirectory, and it just works.

Hey, you need to also modprobe usb_f_uvc at the beggining, right after modprobe libcomposite

SUSE Linux Enterprise exists since 2000.

I mean, SUSE Linux Enterprise, the distro on which OpenSUSE Leap is based, has been developed by SUSE since 2000. It’s newest version, 15, is used in IBM’s Watson and HP’s Frontier supercomputers. I’d say it’s enterprise ready.