Open Packetslave opened 3 years ago
fwiw, here's the output when connecting the loupedeck to USB: https://gist.github.com/Packetslave/3a4b64f942ccede0a7b3616da4a629af
Answering my own question (after a LOT of googling). The solution was to manually modprobe cdc_ether
before connecting the Loupedeck. That caused it to be detected properly and the interface created.
enx0222c7f51d92: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 100.127.1.2 netmask 255.255.255.248 broadcast 100.127.1.7
inet6 fe80::7bf:4d9d:d47c:af1 prefixlen 64 scopeid 0x20<link>
ether 02:22:c7:f5:1d:92 txqueuelen 1000 (Ethernet)
RX packets 2 bytes 656 (656.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6 bytes 1160 (1.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Just swung by to say thanks for providing the answer you found. If this project looked like it was still maintained I might have bought one of these thingamajigs and benefited from it.
Hey, there's more info about this elsewhere. I will try to find it:)
Howdy, some very cool stuff here. Wondering if there's a quick HOWTO on getting started with Linux and the Loupedeck-CT.
On Ubuntu 20.04 LTS, I can see that the Loupedeck is being detected and appears to be getting mapped to libinput as a mouse (?). I don't see that there a network interface being created for it (no 100.127.* interfaces in ifconfig). I assume there's a tweak or two I need to make to convince the kernel that it should treat the Loupedeck as a network device?
If I can get the LD interface to come up, I can take it from there.
Thanks!