Re: [Linux-usb-users] No input interrupt endpoint

2007-05-10 Thread Alan Stern
On Thu, 10 May 2007, Michael St. Laurent wrote:

> > Okay, then I was wrong about the KVM being unintelligent.
> 
> No worries.  ;)
> 
> > > For giggles, I disconnected the keyboard and mouse then 
> > switched the KVM
> > > to the Linux system.  I got the same message once again.
> > 
> > Maybe that "phantom" device refers to the pusbutton on the KVM itself.
> > In any case, it clearly is the case of those error messages.  
> > Below is a 
> > patch for the USB HID driver in 2.6.18 which ought to help.
> 
> Thank you very much for the patch.  ;)  I was hoping there was a way to
> handle it with a config file change though.  I assue that there is not?

I can think of only one possibility, which is to prevent _all_ warning 
messages from showing up on the console.  You can do that as follows:

echo 4 >/proc/sys/kernel/printk

or even simply holding down the Alt and SysRq keys while pressing 4.  This 
won't prevent the warning messages from going into the system log, though.

Of course, you could always get a different brand KVM switch.  That would 
stop the errors.

Alan Stern



-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] No input interrupt endpoint

2007-05-10 Thread Michael St. Laurent
> Okay, then I was wrong about the KVM being unintelligent.

No worries.  ;)

> > For giggles, I disconnected the keyboard and mouse then 
> switched the KVM
> > to the Linux system.  I got the same message once again.
> 
> Maybe that "phantom" device refers to the pusbutton on the KVM itself.
> In any case, it clearly is the case of those error messages.  
> Below is a 
> patch for the USB HID driver in 2.6.18 which ought to help.

Thank you very much for the patch.  ;)  I was hoping there was a way to
handle it with a config file change though.  I assue that there is not?

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] No input interrupt endpoint

2007-05-10 Thread Alan Stern
On Wed, 9 May 2007, Michael St. Laurent wrote:

> It's a TRENDnet TK-407 KVM which connects four systems to a monitor,
> keyboard and mouse.  There are separate USB ports for the keyboard and
> the mouse so for the console connection it has one monitor connector,
> one USB connector with a keyboard symbol above it and one USB connector
> with a mouse symbol over it.  I have the devices connected to the
> indicated ports.  The keyboard does not have any outgoing USB ports on
> it nor does the mouse.
> 
> The only other keyboard involved is the one built into the laptop
> computer also connected to the KVM.  So I tried disconnecting everything
> from the KVM except for the one Linux system but I'm still seeing the
> problem.
> 
> If there is a hub involved then it has to be inside the KVM.

> > The KVM switch has no intelligence of its own, so it can't create
> > "phantoms".  Furthermore this thing shows up behind a hub; 
> > again something
> > the switch couldn't do.
> > 
> > What exactly have you got plugged in to the KVM switch?  Is 
> > it a keyboard 
> > with USB ports attached and the trackball plugged into one of 
> > the ports?  
> > How many ports are there?  Is anything plugged into any of the other 
> > ports?

Okay, then I was wrong about the KVM being unintelligent.

> For giggles, I disconnected the keyboard and mouse then switched the KVM
> to the Linux system.  I got the same message once again.

Maybe that "phantom" device refers to the pusbutton on the KVM itself.
In any case, it clearly is the case of those error messages.  Below is a 
patch for the USB HID driver in 2.6.18 which ought to help.

Alan Stern



Index: linux-2.6.18/drivers/usb/input/hid-core.c
===
--- linux-2.6.18.orig/drivers/usb/input/hid-core.c
+++ linux-2.6.18/drivers/usb/input/hid-core.c
@@ -1591,6 +1591,10 @@
 
 #define USB_VENDOR_ID_YEALINK  0x6993
 #define USB_DEVICE_ID_YEALINK_P1K_P4K_B2K  0xb001
+
+#define USB_VENDOR_ID_UNI  0x10d5
+#define USB_DEVICE_ID_UNI_SP04_A1  0x000d
+
 /*
  * Alphabetically sorted blacklist by quirk type.
  */
@@ -1705,6 +1709,7 @@
 
{ USB_VENDOR_ID_ACECAD, USB_DEVICE_ID_ACECAD_FLAIR, HID_QUIRK_IGNORE },
{ USB_VENDOR_ID_ACECAD, USB_DEVICE_ID_ACECAD_302, HID_QUIRK_IGNORE },
+   { USB_VENDOR_ID_UNI, USB_DEVICE_ID_UNI_SP04_A1, HID_QUIRK_IGNORE },
 
{ USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_UC100KM, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_CS124U, HID_QUIRK_NOGET },


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] No input interrupt endpoint

2007-05-09 Thread Michael St. Laurent
> > It's showing two keyboards?  There is only one connected.  
> It must be
> > some kind of 'phantom' keyboard presented by the KVM 
> switch.  The real
> > keyboard is the Logitech one. 
> 
> The KVM switch has no intelligence of its own, so it can't create
> "phantoms".  Furthermore this thing shows up behind a hub; 
> again something
> the switch couldn't do.
> 
> What exactly have you got plugged in to the KVM switch?  Is 
> it a keyboard 
> with USB ports attached and the trackball plugged into one of 
> the ports?  
> How many ports are there?  Is anything plugged into any of the other 
> ports?

For giggles, I disconnected the keyboard and mouse then switched the KVM
to the Linux system.  I got the same message once again.

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] No input interrupt endpoint

2007-05-09 Thread Michael St. Laurent
> > It's showing two keyboards?  There is only one connected.  
> It must be
> > some kind of 'phantom' keyboard presented by the KVM 
> switch.  The real
> > keyboard is the Logitech one. 
> 
> The KVM switch has no intelligence of its own, so it can't create
> "phantoms".  Furthermore this thing shows up behind a hub; 
> again something
> the switch couldn't do.
> 
> What exactly have you got plugged in to the KVM switch?  Is 
> it a keyboard 
> with USB ports attached and the trackball plugged into one of 
> the ports?  
> How many ports are there?  Is anything plugged into any of the other 
> ports?
> 
> Here's a cut-down version of your output, showing what's 
> connected to the
> switch.  First you've got a hub.  It might be built into the keyboard:
> 
> Bus 002 Device 006: ID 058f:9254 Alcor Micro Corp. Hub
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   1.10
>   bDeviceClass9 Hub
>   bDeviceSubClass 0 Unused
>   bDeviceProtocol 0 Full speed (or root) hub
>   bMaxPacketSize0 8
>   idVendor   0x058f Alcor Micro Corp.
>   idProduct  0x9254 Hub
>   bcdDevice3.12
>   iManufacturer   1 ALCOR
>   iProduct2 Generic USB Hub
>   iSerial 0 
> 
> Plugged into the hub are three low-speed devices.  First is a keyboard
> (with 2 interfaces -- I have no idea what the reason is for that!):
> 
> Bus 002 Device 007: ID 046d:c312 Logitech, Inc. 
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   1.10
>   bDeviceClass0 (Defined at Interface level)
>   bDeviceSubClass 0 
>   bDeviceProtocol 0 
>   bMaxPacketSize0 8
>   idVendor   0x046d Logitech, Inc.
>   idProduct  0xc312 
>   bcdDevice1.00
>   iManufacturer   1 BTC
>   iProduct2 USB Multimedia Keyboard
>   iSerial 0 
> 
> Then there's the Trackball:
> 
> Bus 002 Device 008: ID 046d:c404 Logitech, Inc. TrackMan Wheel
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   1.10
>   bDeviceClass0 (Defined at Interface level)
>   bDeviceSubClass 0 
>   bDeviceProtocol 0 
>   bMaxPacketSize0 8
>   idVendor   0x046d Logitech, Inc.
>   idProduct  0xc404 TrackMan Wheel
>   bcdDevice2.20
>   iManufacturer   1 Logitech
>   iProduct2 Trackball
>   iSerial 0 
> 
> Finally there's this funny thing.  It might be a keypad or something
> like that:
> 
> Bus 002 Device 009: ID 10d5:000d Uni Class Technology Co., Ltd 
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   1.10
>   bDeviceClass0 (Defined at Interface level)
>   bDeviceSubClass 0 
>   bDeviceProtocol 0 
>   bMaxPacketSize0 8
>   idVendor   0x10d5 Uni Class Technology Co., Ltd
>   idProduct  0x000d 
>   bcdDevice1.00
>   iManufacturer   1 No brand
>   iProduct2 SP04-A1
>   iSerial 3 2ôÒ
> 
> Anything there look familiar?  I'll include a portion of the other
> descriptors from this device:
> 
>   bNumConfigurations  1
>   Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength   59
> bNumInterfaces  2
> bConfigurationValue 1
> iConfiguration  4 HID Mouse
> bmAttributes 0x80
> MaxPower  100mA
> Interface Descriptor:
>   bLength 9
>   bDescriptorType 4
>   bInterfaceNumber0
>   bAlternateSetting   0
>   bNumEndpoints   1
>   bInterfaceClass 3 Human Interface Devices
>   bInterfaceSubClass  0 No Subclass
>   bInterfaceProtocol  0 None
>   iInterface  7 Keyboard
>   Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81  EP 1 IN
> bmAttributes3
>   Transfer TypeInterrupt
>   Synch Type   None
>   Usage Type   Data
> wMaxPacketSize 0x0008  1x 8 bytes
> bInterval  10
> 
> So interface 0 appears to be a more-or-less normal HID 
> object.  Hard to 
> say just what it is, though.
> 
> Interface Descriptor:
>   bLength 9
>   bDescriptorType 4
>   bInterfaceNumber1
>   bAlternateSetting   0
>   bNumEndpoints   1
>   bInterfaceClass 3 Human Interface Devices
>   bInterfaceSubClass  0 No Subclass
>   bInterfaceProtocol  0 None
>   iInterface  6 Mouse
>   Endpoint Descriptor:
> 

Re: [Linux-usb-users] No input interrupt endpoint

2007-05-09 Thread Alan Stern
On Wed, 9 May 2007, Michael St. Laurent wrote:

> It's showing two keyboards?  There is only one connected.  It must be
> some kind of 'phantom' keyboard presented by the KVM switch.  The real
> keyboard is the Logitech one. 

The KVM switch has no intelligence of its own, so it can't create
"phantoms".  Furthermore this thing shows up behind a hub; again something
the switch couldn't do.

What exactly have you got plugged in to the KVM switch?  Is it a keyboard 
with USB ports attached and the trackball plugged into one of the ports?  
How many ports are there?  Is anything plugged into any of the other 
ports?

Here's a cut-down version of your output, showing what's connected to the
switch.  First you've got a hub.  It might be built into the keyboard:

Bus 002 Device 006: ID 058f:9254 Alcor Micro Corp. Hub
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize0 8
  idVendor   0x058f Alcor Micro Corp.
  idProduct  0x9254 Hub
  bcdDevice3.12
  iManufacturer   1 ALCOR
  iProduct2 Generic USB Hub
  iSerial 0 

Plugged into the hub are three low-speed devices.  First is a keyboard
(with 2 interfaces -- I have no idea what the reason is for that!):

Bus 002 Device 007: ID 046d:c312 Logitech, Inc. 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 8
  idVendor   0x046d Logitech, Inc.
  idProduct  0xc312 
  bcdDevice1.00
  iManufacturer   1 BTC
  iProduct2 USB Multimedia Keyboard
  iSerial 0 

Then there's the Trackball:

Bus 002 Device 008: ID 046d:c404 Logitech, Inc. TrackMan Wheel
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 8
  idVendor   0x046d Logitech, Inc.
  idProduct  0xc404 TrackMan Wheel
  bcdDevice2.20
  iManufacturer   1 Logitech
  iProduct2 Trackball
  iSerial 0 

Finally there's this funny thing.  It might be a keypad or something
like that:

Bus 002 Device 009: ID 10d5:000d Uni Class Technology Co., Ltd 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 8
  idVendor   0x10d5 Uni Class Technology Co., Ltd
  idProduct  0x000d 
  bcdDevice1.00
  iManufacturer   1 No brand
  iProduct2 SP04-A1
  iSerial 3 2ôÒ

Anything there look familiar?  I'll include a portion of the other
descriptors from this device:

  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   59
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  4 HID Mouse
bmAttributes 0x80
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Devices
  bInterfaceSubClass  0 No Subclass
  bInterfaceProtocol  0 None
  iInterface  7 Keyboard
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval  10

So interface 0 appears to be a more-or-less normal HID object.  Hard to 
say just what it is, though.

Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Devices
  bInterfaceSubClass  0 No Subclass
  bInterfaceProtocol  0 None
  iInterface  6 Mouse
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type

Re: [Linux-usb-users] No input interrupt endpoint

2007-05-09 Thread Michael St. Laurent
It's showing two keyboards?  There is only one connected.  It must be
some kind of 'phantom' keyboard presented by the KVM switch.  The real
keyboard is the Logitech one. 

> -Original Message-
> From: Alan Stern [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, May 09, 2007 11:11 AM
> To: Michael St. Laurent
> Cc: [email protected]
> Subject: Re: [Linux-usb-users] No input interrupt endpoint
> 
> On Wed, 9 May 2007, Michael St. Laurent wrote:
> 
> > > > I have a USB KVM switch connected to my system with a 
> > > logitech keyboard
> > > > and mouse.  Every time I switch back to my Linux system I'm 
> > > getting the
> > > > message "drivers/usb/input/hid-core.c: couldn't find an 
> > > input interrupt
> > > > endpoint" on the console and it's very irritating.
> > > > 
> > > > I'd prefer to fix the problem whatever it is, but since 
> everything
> > > > appears to be working despite the error I *will* settle for 
> > > just making
> > > > the error message stop.
> > > 
> > > Please provide more information, including the kernel 
> version, the 
> > > output from "lsusb -v", and the dmesg log showing initial 
> > > bootup and what 
> > > happens when you switch the KVM.
> > 
> > Thank you for responding Alan.  The info you requested is below:
> > 
> > [EMAIL PROTECTED] ~]#
> > [EMAIL PROTECTED] ~]# uname -a
> > Linux hcfw1.hartwellcorp.com 2.6.18-8.1.3.el5 #1 SMP Mon 
> Apr 30 19:55:44
> > EDT 200
> > 7 i686 i686 i386 GNU/Linux
> 
> A little old, but okay.
> 
> > [EMAIL PROTECTED] ~]# lsusb -v
> ...
> 
> This listing didn't contain any information on your keyboard 
> and mouse!
> That's what I need to see; so the KVM has to be set to connect them
> to the computer when you run lsusb.
> 
> > [EMAIL PROTECTED] ~]# dmesg
> ...
> > usb 2-2: new full speed USB device using uhci_hcd and address 2
> > usb 2-2: configuration #1 chosen from 1 choice
> > hub 2-2:1.0: USB hub found
> > hub 2-2:1.0: 4 ports detected
> > usb 2-2.1: new low speed USB device using uhci_hcd and address 3
> > usb 2-2.1: configuration #1 chosen from 1 choice
> > input: BTC USB Multimedia Keyboard as /class/input/input2
> > input: USB HID v1.10 Keyboard [BTC USB Multimedia Keyboard] on
> > usb-:00:1d.1-
> > 2.1
> > input: BTC USB Multimedia Keyboard as /class/input/input3
> > input,hiddev96: USB HID v1.10 Device [BTC USB Multimedia 
> Keyboard] on
> > usb-:0
> > 0:1d.1-2.1
> > usb 2-2.2: new low speed USB device using uhci_hcd and address 4
> > usb 2-2.2: configuration #1 chosen from 1 choice
> > input: Logitech Trackball as /class/input/input4
> > input: USB HID v1.10 Mouse [Logitech Trackball] on 
> usb-:00:1d.1-2.2
> > usb 2-2.3: new low speed USB device using uhci_hcd and address 5
> > usb 2-2.3: configuration #1 chosen from 1 choice
> > input: No brand SP04-A1 as /class/input/input5
> > input: USB HID v1.10 Keyboard [No brand SP04-A1] on 
> usb-:00:1d.1-2.3
> > drivers/usb/input/hid-core.c: couldn't find an input 
> interrupt endpoint
> 
> These are the devices going to the KVM switch, right?  A BTC 
> keyboard and
> Logitech trackball plus a no-name keyboard.  It's that 
> no-name keyboard
> which is causing the problem.
> 
> ...
> > usb 2-2: USB disconnect, address 2
> > usb 2-2.1: USB disconnect, address 3
> > usb 2-2.2: USB disconnect, address 4
> > usb 2-2.3: USB disconnect, address 5
> > 
> > The last few lines are probably from switching back to the 
> system from
> > which I'm sending this mail.
> 
> Yes; the devices get disconnected from the computer when you 
> change the
> KVM switch.
> 
> > When I switch to the system the following message is 
> displayed on the
> > console:
> > 
> > drivers/usb/input/hid-core.c: couldn't find an input 
> interrupt endpoint
> 
> The same error occurred during bootup.  Whatever that no-name 
> keyboard 
> thing is, something is wrong with it.
> 
> Alan Stern
> 
> 

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] No input interrupt endpoint

2007-05-09 Thread Alan Stern
On Wed, 9 May 2007, Michael St. Laurent wrote:

> > > I have a USB KVM switch connected to my system with a 
> > logitech keyboard
> > > and mouse.  Every time I switch back to my Linux system I'm 
> > getting the
> > > message "drivers/usb/input/hid-core.c: couldn't find an 
> > input interrupt
> > > endpoint" on the console and it's very irritating.
> > > 
> > > I'd prefer to fix the problem whatever it is, but since everything
> > > appears to be working despite the error I *will* settle for 
> > just making
> > > the error message stop.
> > 
> > Please provide more information, including the kernel version, the 
> > output from "lsusb -v", and the dmesg log showing initial 
> > bootup and what 
> > happens when you switch the KVM.
> 
> Thank you for responding Alan.  The info you requested is below:
> 
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]# uname -a
> Linux hcfw1.hartwellcorp.com 2.6.18-8.1.3.el5 #1 SMP Mon Apr 30 19:55:44
> EDT 200
> 7 i686 i686 i386 GNU/Linux

A little old, but okay.

> [EMAIL PROTECTED] ~]# lsusb -v
...

This listing didn't contain any information on your keyboard and mouse!
That's what I need to see; so the KVM has to be set to connect them
to the computer when you run lsusb.

> [EMAIL PROTECTED] ~]# dmesg
...
> usb 2-2: new full speed USB device using uhci_hcd and address 2
> usb 2-2: configuration #1 chosen from 1 choice
> hub 2-2:1.0: USB hub found
> hub 2-2:1.0: 4 ports detected
> usb 2-2.1: new low speed USB device using uhci_hcd and address 3
> usb 2-2.1: configuration #1 chosen from 1 choice
> input: BTC USB Multimedia Keyboard as /class/input/input2
> input: USB HID v1.10 Keyboard [BTC USB Multimedia Keyboard] on
> usb-:00:1d.1-
> 2.1
> input: BTC USB Multimedia Keyboard as /class/input/input3
> input,hiddev96: USB HID v1.10 Device [BTC USB Multimedia Keyboard] on
> usb-:0
> 0:1d.1-2.1
> usb 2-2.2: new low speed USB device using uhci_hcd and address 4
> usb 2-2.2: configuration #1 chosen from 1 choice
> input: Logitech Trackball as /class/input/input4
> input: USB HID v1.10 Mouse [Logitech Trackball] on usb-:00:1d.1-2.2
> usb 2-2.3: new low speed USB device using uhci_hcd and address 5
> usb 2-2.3: configuration #1 chosen from 1 choice
> input: No brand SP04-A1 as /class/input/input5
> input: USB HID v1.10 Keyboard [No brand SP04-A1] on usb-:00:1d.1-2.3
> drivers/usb/input/hid-core.c: couldn't find an input interrupt endpoint

These are the devices going to the KVM switch, right?  A BTC keyboard and
Logitech trackball plus a no-name keyboard.  It's that no-name keyboard
which is causing the problem.

...
> usb 2-2: USB disconnect, address 2
> usb 2-2.1: USB disconnect, address 3
> usb 2-2.2: USB disconnect, address 4
> usb 2-2.3: USB disconnect, address 5
> 
> The last few lines are probably from switching back to the system from
> which I'm sending this mail.

Yes; the devices get disconnected from the computer when you change the
KVM switch.

> When I switch to the system the following message is displayed on the
> console:
> 
> drivers/usb/input/hid-core.c: couldn't find an input interrupt endpoint

The same error occurred during bootup.  Whatever that no-name keyboard 
thing is, something is wrong with it.

Alan Stern


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] No input interrupt endpoint

2007-05-09 Thread Michael St. Laurent
> > I have a USB KVM switch connected to my system with a 
> logitech keyboard
> > and mouse.  Every time I switch back to my Linux system I'm 
> getting the
> > message "drivers/usb/input/hid-core.c: couldn't find an 
> input interrupt
> > endpoint" on the console and it's very irritating.
> > 
> > I'd prefer to fix the problem whatever it is, but since everything
> > appears to be working despite the error I *will* settle for 
> just making
> > the error message stop.
> 
> Please provide more information, including the kernel version, the 
> output from "lsusb -v", and the dmesg log showing initial 
> bootup and what 
> happens when you switch the KVM.

Thank you for responding Alan.  The info you requested is below:

[EMAIL PROTECTED] ~]#
[EMAIL PROTECTED] ~]# uname -a
Linux hcfw1.hartwellcorp.com 2.6.18-8.1.3.el5 #1 SMP Mon Apr 30 19:55:44
EDT 200
7 i686 i686 i386 GNU/Linux
[EMAIL PROTECTED] ~]# lsusb -v

Bus 003 Device 001: ID :
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize064
  idVendor   0x
  idProduct  0x
  bcdDevice2.06
  iManufacturer   3 Linux 2.6.18-8.1.3.el5 uhci_hcd
  iProduct2 UHCI Host Controller
  iSerial 1 :00:1d.2
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   25
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 9 Hub
  bInterfaceSubClass  0 Unused
  bInterfaceProtocol  0 Full speed (or root) hub
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0002  1x 2 bytes
bInterval 255
Hub Descriptor:
  bLength   9
  bDescriptorType  41
  nNbrPorts 2
  wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
  bPwrOn2PwrGood1 * 2 milli seconds
  bHubContrCurrent  0 milli Ampere
  DeviceRemovable0xc0
  PortPwrCtrlMask0x86
 Hub Port Status:
   Port 1: .0100 power
   Port 2: .0100 power

Bus 001 Device 001: ID :
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize064
  idVendor   0x
  idProduct  0x
  bcdDevice2.06
  iManufacturer   3 Linux 2.6.18-8.1.3.el5 uhci_hcd
  iProduct2 UHCI Host Controller
  iSerial 1 :00:1d.0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   25
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 9 Hub
  bInterfaceSubClass  0 Unused
  bInterfaceProtocol  0 Full speed (or root) hub
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0002  1x 2 bytes
bInterval 255
Hub Descriptor:
  bLength   9
  bDescriptorType  41
  nNbrPorts 2
  wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
  bPwrOn2PwrGood1 * 2 milli seconds
  bHubContrCurrent  0 milli Ampere
  DeviceRemovable0xc0
  PortPwrCtrlMask0x86
 Hub Port Status:
   Port 1: .0100 power
   Port 2: .0100 power

Bus 002 Device 001: ID :
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdU

Re: [Linux-usb-users] No input interrupt endpoint

2007-05-09 Thread Alan Stern
On Tue, 8 May 2007, Michael St. Laurent wrote:

> I have a USB KVM switch connected to my system with a logitech keyboard
> and mouse.  Every time I switch back to my Linux system I'm getting the
> message "drivers/usb/input/hid-core.c: couldn't find an input interrupt
> endpoint" on the console and it's very irritating.
> 
> I'd prefer to fix the problem whatever it is, but since everything
> appears to be working despite the error I *will* settle for just making
> the error message stop.

Please provide more information, including the kernel version, the 
output from "lsusb -v", and the dmesg log showing initial bootup and what 
happens when you switch the KVM.

Alan Stern


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users