On Wed, Jul 31, 2019 at 07:32:29PM +0200, Markus Breunig wrote: > > > Am 16.07.2019 um 11:23 schrieb Johan Hovold: > > [ Pleas avoid top posting. ] > > > > On Sun, Jul 07, 2019 at 09:38:00PM +0200, Markus Breunig wrote: > >> Hi Greg, > >> > >> also the company GNS has a fragmented homepage, the handbook ist > >> available here: > >> http://www.servicedocs.com/ARTIKELEN/7200284490001.pdf > >> habe a look to page 10 "Remarks to Linux" > >> > >> This is the log of "lsusb -v" (full scan result attached): > >> > >> Bus 001 Device 004: ID 04d8:f8e8 Microchip Technology, Inc. Harmony > >> 300/350 Remote > > > > Are you sure this is the right device? This looks like a remote control, > > and one that should be using the cdc-acm driver. > > > > The output of lsusb before plugging the GNS5890 device into the USB-port: > > Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse > Bus 001 Device 004: ID 046a:0001 Cherry GmbH Keyboard > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. > SMSC9512/9514 Fast Ethernet Adapter > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > and the result of the lsusb after plugging the GNS5890 device into the > USB-port: > > Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse > Bus 001 Device 004: ID 046a:0001 Cherry GmbH Keyboard > Bus 001 Device 006: ID 04d8:f8e8 Microchip Technology, Inc. Harmony > 300/350 Remote > Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. > SMSC9512/9514 Fast Ethernet Adapter > Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Ok, thanks for confirming. Based on the below descriptors, this device should be handled by the cdc-acm driver and show up as a /dev/ttyACMn. Do you have that driver enabled? Can you enable debugging in that driver and post the syslog from when plugging the device in if it still doesn't work? You can enable debugging using modprobe cdc-acm dyndbg==p or through sysfs, see Documentation/admin-guide/dynamic-debug-howto.rst > >> Device Descriptor: > >> bLength 18 > >> bDescriptorType 1 > >> bcdUSB 2.00 > >> bDeviceClass 255 Vendor Specific Class > >> bDeviceSubClass 0 > >> bDeviceProtocol 0 > >> bMaxPacketSize0 8 > >> idVendor 0x04d8 Microchip Technology, Inc. > >> idProduct 0xf8e8 Harmony 300/350 Remote > >> bcdDevice 48.12 > >> iManufacturer 1 > >> iProduct 2 > >> iSerial 3 > >> bNumConfigurations 1 > >> Configuration Descriptor: > >> bLength 9 > >> bDescriptorType 2 > >> wTotalLength 67 > >> bNumInterfaces 2 > >> bConfigurationValue 1 > >> iConfiguration 0 > >> bmAttributes 0xc0 > >> Self Powered > >> MaxPower 100mA > >> Interface Descriptor: > >> bLength 9 > >> bDescriptorType 4 > >> bInterfaceNumber 0 > >> bAlternateSetting 0 > >> bNumEndpoints 1 > >> bInterfaceClass 2 Communications > >> bInterfaceSubClass 2 Abstract (modem) > >> bInterfaceProtocol 1 AT-commands (v.25ter) > >> iInterface 0 > >> CDC Header: > >> bcdCDC 1.10 > >> CDC ACM: > >> bmCapabilities 0x02 > >> line coding and serial state > >> CDC Union: > >> bMasterInterface 0 > >> bSlaveInterface 1 > >> CDC Call Management: > >> bmCapabilities 0x00 > >> bDataInterface 1 > >> Endpoint Descriptor: > >> bLength 7 > >> bDescriptorType 5 > >> bEndpointAddress 0x82 EP 2 IN > >> bmAttributes 3 > >> Transfer Type Interrupt > >> Synch Type None > >> Usage Type Data > >> wMaxPacketSize 0x0008 1x 8 bytes > >> bInterval 2 > >> Interface Descriptor: Johan
