Re: [Linux-usb-users] usblp error handling broken
On Mon, May 07, 2007 at 01:35:27PM +0200, Jochen Karrer wrote: Hi, The error handling in usblp_write is broken. Try bringing this up on the linux-usb-devel mailing list. The developers there should be able to help you out. Also please note which kernel version you are looking at. thanks, greg k-h - 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/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
[Linux-usb-users] usb power management
Hi, How to enable usb power management like suspend/resume in linux from the kernel. Is it already built in? Regards, Mohan Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html - 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/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
2007/5/6, Antonino Ingargiola [EMAIL PROTECTED]: 2007/5/5, Oliver Neukum [EMAIL PROTECTED]: Am Samstag, 5. Mai 2007 20:08 schrieb Antonino Ingargiola: Now I don't want to abuse your kindness, but I (personally) would be *really* interested in a similar fix for the FTDI usb-serial driver, because many measurements I do use an FTDI device. Does this work? Thanks for the patch! Alas, I will have access to an FTDI device only on Tuesday, then I'll test it and report results. Sorry. I've not been able to try this ftdi patch yet. My work pc has ubuntu dapper with 2.6.15 kernel. I've compiled 2.6.21 there but the leap is too much and there are probably udev incompatibilities so the /dev entry is not created for any USB device. I need to install a newer distro to work with mainline. This mail is just to point out that the patch is not forgotten, just need more time to try it. Regards, ~ Antonio - 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/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
On Saturday 05 May 2007, Oliver Neukum wrote:
Am Samstag, 5. Mai 2007 20:08 schrieb Antonino Ingargiola:
Now I don't want to abuse your kindness, but I (personally) would be
*really* interested in a similar fix for the FTDI usb-serial driver,
because many measurements I do use an FTDI device.
Does this work?
Regards
Oliver
--- a/drivers/usb/serial/ftdi_sio.c2007-05-05 20:21:41.0 +0200
+++ b/drivers/usb/serial/ftdi_sio.c2007-05-05 20:27:09.0 +0200
@@ -1749,10 +1749,6 @@ static void ftdi_process_read (struct wo
length = 0;
}
- if (priv-rx_flags THROTTLED) {
- dbg(%s - throttled, __FUNCTION__);
- break;
- }
if (tty_buffer_request_room(tty, length) length) {
/* break out wait for throttling/unthrottling to
happen */
dbg(%s - receive room low, __FUNCTION__);
@@ -1825,16 +1821,6 @@ static void ftdi_process_read (struct wo
dbg(%s - incomplete, %d bytes processed, %d remain,
__FUNCTION__, packet_offset,
urb-actual_length - packet_offset);
- /* check if we were throttled while processing */
- spin_lock_irqsave(priv-rx_lock, flags);
- if (priv-rx_flags THROTTLED) {
- priv-rx_flags |= ACTUALLY_THROTTLED;
- spin_unlock_irqrestore(priv-rx_lock, flags);
- dbg(%s - deferring remainder until unthrottled,
- __FUNCTION__);
- return;
- }
- spin_unlock_irqrestore(priv-rx_lock, flags);
/* if the port is closed stop trying to read */
if (port-open_count 0){
/* delay processing of remainder */
@@ -1856,9 +1842,15 @@ static void ftdi_process_read (struct wo
port-read_urb-transfer_buffer,
port-read_urb-transfer_buffer_length, ftdi_read_bulk_callback, port);
- result = usb_submit_urb(port-read_urb, GFP_ATOMIC);
- if (result)
- err(%s - failed resubmitting read urb, error %d,
__FUNCTION__,
result); +spin_lock_irqsave(priv-rx_lock, flags);
+ if (priv-rx_flags THROTTLED) {
+ priv-rx_flags |= ACTUALLY_THROTTLED;
+ } else {
+ result = usb_submit_urb(port-read_urb, GFP_ATOMIC);
+ if (result)
+ err(%s - failed resubmitting read urb, error
%d, __FUNCTION__,
result); +}
+ spin_unlock_irqrestore(priv-rx_lock, flags);
}
return;
-
Oliver:
Sort of late, but,
I have a couple of kernels building with this patch applied, one with the
sd-0.48 patch where FTDI stuff is a 40+% cpu hog and can't be used, and one
with the cfs-v10 patch where it can be co-erced into working if I screw with
it enough.
I have also been using another serial patch that for unk reasons, also helps
the usb-serial case here, but vger won't let me repost that without stripping
off the headers. That patch has some resemblance to
this:8250-clear-on-read-bits-LSR-MSR where I usually replace spaces with
dashes so I don't have to use to surround the name in my scripts.
So these test kernels will have both patches.
I'll let you know how they work later this morning.
--
Cheers, Gene
There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Oh my GOD -- the SUN just fell into YANKEE STADIUM!!
-
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/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] problem with usb-storage
Am Dienstag, 8. Mai 2007 21:16 schrieb Alan Stern: May 8 10:46:07 benz505sx kernel: usb-storage: -- Result from auto-sense is 0 May 8 10:46:07 benz505sx kernel: usb-storage: -- code: 0x70, key: 0x3, ASC: 0x30, ASCQ: 0x1 This error message means Medium Error: Cannot read medium - unknown format. However I suspect that code is incorrect, because the command was ALLOW_MEDIUM_REMOVAL, which doesn't require the slot to read anything from the stick. More likely the slot just can't handle the command at all. Fortunately it's possible to prevent the command from being sent. If you post the output from lsusb -v for your device, I can send you a patch. What version of the kernel are you running? lsusb -v: Bus 003 Device 002: ID 054c:0069 Sony Corp. Memorystick MSC-U03 Reader Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize016 idVendor 0x054c Sony Corp. idProduct 0x0069 Memorystick MSC-U03 Reader bcdDevice1.07 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 8 Mass Storage bInterfaceSubClass 5 SFF-8070i bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 1 I'm using the kernel version 2.6.20.2 with the options I mentionend in my first posting. On the other hand if that message shows up only when the slot is empty, and if your only problem is that the log files keep growing, then there's nothing to worry about. Simply turn off CONFIG_USB_STORAGE_DEBUG; that will prevent these messages from being logged. Thats something for a start. But it would be great if I get the slot working... Does the slot not work? You haven't said what happens when you try to use the stick. Those errors messages above aren't fatal. The stick is not mountable. When I insert it (a Sony Memory Stick M2 micro in an M2 Adaptor) into the slot some program (I think the kernel modul sonypi or so, which gives also access to the fn-keys) tells me, that I inserted a memory stick. But there is no accessable device under /dev. The stick itself is working, as I can use it in my phone and access it through the phone if I connect the phone with a usb-cable with my laptop. Thanks, Ben - 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/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
On Saturday 05 May 2007, Oliver Neukum wrote:
Am Samstag, 5. Mai 2007 20:08 schrieb Antonino Ingargiola:
Now I don't want to abuse your kindness, but I (personally) would be
*really* interested in a similar fix for the FTDI usb-serial driver,
because many measurements I do use an FTDI device.
Does this work?
Regards
Oliver
--- a/drivers/usb/serial/ftdi_sio.c2007-05-05 20:21:41.0 +0200
+++ b/drivers/usb/serial/ftdi_sio.c2007-05-05 20:27:09.0 +0200
@@ -1749,10 +1749,6 @@ static void ftdi_process_read (struct wo
length = 0;
}
- if (priv-rx_flags THROTTLED) {
- dbg(%s - throttled, __FUNCTION__);
- break;
- }
if (tty_buffer_request_room(tty, length) length) {
/* break out wait for throttling/unthrottling to
happen */
dbg(%s - receive room low, __FUNCTION__);
@@ -1825,16 +1821,6 @@ static void ftdi_process_read (struct wo
dbg(%s - incomplete, %d bytes processed, %d remain,
__FUNCTION__, packet_offset,
urb-actual_length - packet_offset);
- /* check if we were throttled while processing */
- spin_lock_irqsave(priv-rx_lock, flags);
- if (priv-rx_flags THROTTLED) {
- priv-rx_flags |= ACTUALLY_THROTTLED;
- spin_unlock_irqrestore(priv-rx_lock, flags);
- dbg(%s - deferring remainder until unthrottled,
- __FUNCTION__);
- return;
- }
- spin_unlock_irqrestore(priv-rx_lock, flags);
/* if the port is closed stop trying to read */
if (port-open_count 0){
/* delay processing of remainder */
@@ -1856,9 +1842,15 @@ static void ftdi_process_read (struct wo
port-read_urb-transfer_buffer,
port-read_urb-transfer_buffer_length, ftdi_read_bulk_callback, port);
- result = usb_submit_urb(port-read_urb, GFP_ATOMIC);
- if (result)
- err(%s - failed resubmitting read urb, error %d,
__FUNCTION__,
result); +spin_lock_irqsave(priv-rx_lock, flags);
+ if (priv-rx_flags THROTTLED) {
+ priv-rx_flags |= ACTUALLY_THROTTLED;
+ } else {
+ result = usb_submit_urb(port-read_urb, GFP_ATOMIC);
+ if (result)
+ err(%s - failed resubmitting read urb, error
%d, __FUNCTION__,
result); +}
+ spin_unlock_irqrestore(priv-rx_lock, flags);
}
return;
-
Oliver:
While running kernel-2.6.21.1-sd-0.48 + this and the other patch I mentioned,
Unforch, this patch doesn't seem to have effected my usb-serial problems, for
upsd anyway, it's running at 47% of the cpu right now, while running sd-0.48.
Occasionally a stop and restart will fix it... Nope. On the restart, its
about 3% _until_ something starts reading its output data file, which could
be gkrellmBUPS, or its own gui, either one bounces it back up to 45+% of the
cpu. On a kernel where it works sorta right, as in a recent fedora kernel,
its about 1.5%, and on even older 2.6.18ish stuff, this utility ran at .1% of
the cpu regardless of who read its output data. But that was with a pl2303
adapter, which no longer works at all so I bought some ftdi based ones.
So the next boot will be to cfs-v10 + these.
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
Cheers, Gene
There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
For certain people, after fifty, litigation takes the place of sex.
-- Gore Vidal
-
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/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
On Saturday 05 May 2007, Oliver Neukum wrote:
You are included this time David because 3 messages I posted this morning,
whose text should resemble this one, the first of those 3, were
also /dev/nulled. this is BS when I can't even discuss a patch in the same
manner as others can.
So whats wrong with this message that its filtered?
Am Samstag, 5. Mai 2007 20:08 schrieb Antonino Ingargiola:
Now I don't want to abuse your kindness, but I (personally) would be
*really* interested in a similar fix for the FTDI usb-serial driver,
because many measurements I do use an FTDI device.
Does this work?
Regards
Oliver
--- a/drivers/usb/serial/ftdi_sio.c2007-05-05 20:21:41.0 +0200
+++ b/drivers/usb/serial/ftdi_sio.c2007-05-05 20:27:09.0 +0200
@@ -1749,10 +1749,6 @@ static void ftdi_process_read (struct wo
length = 0;
}
- if (priv-rx_flags THROTTLED) {
- dbg(%s - throttled, __FUNCTION__);
- break;
- }
if (tty_buffer_request_room(tty, length) length) {
/* break out wait for throttling/unthrottling to
happen */
dbg(%s - receive room low, __FUNCTION__);
@@ -1825,16 +1821,6 @@ static void ftdi_process_read (struct wo
dbg(%s - incomplete, %d bytes processed, %d remain,
__FUNCTION__, packet_offset,
urb-actual_length - packet_offset);
- /* check if we were throttled while processing */
- spin_lock_irqsave(priv-rx_lock, flags);
- if (priv-rx_flags THROTTLED) {
- priv-rx_flags |= ACTUALLY_THROTTLED;
- spin_unlock_irqrestore(priv-rx_lock, flags);
- dbg(%s - deferring remainder until unthrottled,
- __FUNCTION__);
- return;
- }
- spin_unlock_irqrestore(priv-rx_lock, flags);
/* if the port is closed stop trying to read */
if (port-open_count 0){
/* delay processing of remainder */
@@ -1856,9 +1842,15 @@ static void ftdi_process_read (struct wo
port-read_urb-transfer_buffer,
port-read_urb-transfer_buffer_length, ftdi_read_bulk_callback, port);
- result = usb_submit_urb(port-read_urb, GFP_ATOMIC);
- if (result)
- err(%s - failed resubmitting read urb, error %d,
__FUNCTION__,
result); +spin_lock_irqsave(priv-rx_lock, flags);
+ if (priv-rx_flags THROTTLED) {
+ priv-rx_flags |= ACTUALLY_THROTTLED;
+ } else {
+ result = usb_submit_urb(port-read_urb, GFP_ATOMIC);
+ if (result)
+ err(%s - failed resubmitting read urb, error
%d, __FUNCTION__,
result); +}
+ spin_unlock_irqrestore(priv-rx_lock, flags);
}
return;
-
Oliver:
Sort of late, but,
I have a couple of kernels building with this patch applied, one with the
sd-0.48 patch where FTDI stuff is a 40+% cpu hog and can't be used, and one
with the cfs-v10 patch where it can be co-erced into working if I screw with
it enough.
I have also been using another serial patch that for unk reasons, also helps
the usb-serial case here, but vger won't let me repost that without stripping
off the headers. That patch has some resemblance to
this:8250-clear-on-read-bits-LSR-MSR where I usually replace spaces with
dashes so I don't have to use to surround the name in my scripts.
So these test kernels will have both patches.
I'll let you know how they work later this morning.
--
Cheers, Gene
There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Oh my GOD -- the SUN just fell into YANKEE STADIUM!!
-
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/
___
Linux-usb-users@lists.sourceforge.net
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
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/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] usb power management
On Wed, 9 May 2007, Radha Mohan wrote: Hi, How to enable usb power management like suspend/resume in linux from the kernel. Is it already built in? It is already built into the 2.6.20 and 2.6.21 kernels, provided you set CONFIG_USB_SUSPEND when you build the kernel. 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/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] problem with usb-storage
On Wed, 9 May 2007, Benjamin von Engelhardt wrote: Am Dienstag, 8. Mai 2007 21:16 schrieb Alan Stern: May 8 10:46:07 benz505sx kernel: usb-storage: -- Result from auto-sense is 0 May 8 10:46:07 benz505sx kernel: usb-storage: -- code: 0x70, key: 0x3, ASC: 0x30, ASCQ: 0x1 This error message means Medium Error: Cannot read medium - unknown format. However I suspect that code is incorrect, because the command was ALLOW_MEDIUM_REMOVAL, which doesn't require the slot to read anything from the stick. More likely the slot just can't handle the command at all. Fortunately it's possible to prevent the command from being sent. If you post the output from lsusb -v for your device, I can send you a patch. What version of the kernel are you running? lsusb -v: Bus 003 Device 002: ID 054c:0069 Sony Corp. Memorystick MSC-U03 Reader Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize016 idVendor 0x054c Sony Corp. idProduct 0x0069 Memorystick MSC-U03 Reader bcdDevice1.07 I'm using the kernel version 2.6.20.2 with the options I mentionend in my first posting. On the other hand if that message shows up only when the slot is empty, and if your only problem is that the log files keep growing, then there's nothing to worry about. Simply turn off CONFIG_USB_STORAGE_DEBUG; that will prevent these messages from being logged. Thats something for a start. But it would be great if I get the slot working... Does the slot not work? You haven't said what happens when you try to use the stick. Those errors messages above aren't fatal. The stick is not mountable. When I insert it (a Sony Memory Stick M2 micro in an M2 Adaptor) into the slot some program (I think the kernel modul sonypi or so, which gives also access to the fn-keys) tells me, that I inserted a memory stick. But there is no accessable device under /dev. The stick itself is working, as I can use it in my phone and access it through the phone if I connect the phone with a usb-cable with my laptop. Okay, here's the patch for 2.6.20. Let me know what happens. If possible, include the entire dmesg output starting from the time you insert the stick. Alan Stern Index: usb-2.6/drivers/usb/storage/unusual_devs.h === --- usb-2.6.orig/drivers/usb/storage/unusual_devs.h +++ usb-2.6/drivers/usb/storage/unusual_devs.h @@ -616,7 +616,7 @@ UNUSUAL_DEV( 0x054c, 0x0069, 0x, 0x Sony, Memorystick MSC-U03, US_SC_UFI, US_PR_CB, NULL, - US_FL_SINGLE_LUN ), + US_FL_SINGLE_LUN | US_FL_NOT_LOCKABLE ), /* Submitted by Nathan Babb [EMAIL PROTECTED] */ UNUSUAL_DEV( 0x054c, 0x006d, 0x, 0x, - 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/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
[Linux-usb-users] Brother HL 1440
hey all, first of all, i'm not subscribed to the list, so can you please post answers to me too? thanks! i've got a problem with my printer. history: - i have a brother HL1440 connected to the usb port, and i used to print to /dev/usb/lp0. it allways worked... but it gave errors: message usb_control/bulk_msg: timeout usbdevfs: USBDEVFS_CONTROL failed dev 16 rqt 128 rq 6 len 256 ret -110 /message lsusb gives me: Language IDs: none (cannot get min. string descriptor; got len=-1, error=110:Connection timed out) (and off course more info) now... i think those are the same but... what's the problem now? i added another printer, a HP officejet pro K550. this one is recognized perfectly! (w ;)) and i can access it through usb://HP/Officejet%20Pro%20K550?serial=MY6BA612PS but... now i can't use the other printer anymore. plus, i don't want to use lp0 etc... because that can change after boot etc... so... is there a way to make the brother printer work decently? or is this a known bug, is there something i can test?/do? i'm kinda stuck. i tried unplugging the new k550, reset the HL1440, but i still can't print to the HL1440 anymore. it keeps saying: media tray empty... which it is not ;)) since this is a server, and i'm pretty far away from it, it's kinda hard to reboot etc... kernel version is still 2.4.33-pre2 any ideas? sollutions? (i put the newest usb.ids in hwdata... not that it matters afaik, but it certainly doesn't hurt) i've been looking on the net for about 8 hours now, and i didn't find a sollution, that's why i try here. thanks! -- harry aka Rik Bobbaers K.U.Leuven - LUDIT -=- Tel: +32 485 52 71 50 [EMAIL PROTECTED] -=- http://people.linux-vserver.org/~harry For all of you reporting a score more than 100 as you iq lol @ you.How can you possibly score more than 100%? I'm very happy with my score of 89. (c)bash.org #758032 Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm - 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/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
[Linux-usb-users] Brother HL 1440
hey all, second attempt, with some useful info (i hope) first of all, i'm not subscribed to the list, so can you please post answers to me too? thanks! i've got a problem with my printer. history: - i have a brother HL1440 connected to the usb port, and i used to print to /dev/usb/lp0. it allways worked... but it gave errors: message usb_control/bulk_msg: timeout usbdevfs: USBDEVFS_CONTROL failed dev 16 rqt 128 rq 6 len 256 ret -110 /message lsusb gives me: Language IDs: none (cannot get min. string descriptor; got len=-1, error=110:Connection timed out) (and off course more info) now... i think those are the same but... what's the problem now? i added another printer, a HP officejet pro K550. this one is recognized perfectly! (w ;)) and i can access it through usb://HP/Officejet%20Pro%20K550?serial=MY6BA612PS but... now i can't use the other printer anymore. plus, i don't want to use lp0 etc... because that can change after boot etc... so... is there a way to make the brother printer work decently? or is this a known bug, is there something i can test?/do? i'm kinda stuck. i tried unplugging the new k550, reset the HL1440, but i still can't print to the HL1440 anymore. it keeps saying: media tray empty... which it is not ;)) since this is a server, and i'm pretty far away from it, it's kinda hard to reboot etc... kernel version is still 2.4.33-pre2 any ideas? sollutions? (i put the newest usb.ids in hwdata... not that it matters afaik, but it certainly doesn't hurt) i've been looking on the net for about 8 hours now, and i didn't find a sollution, that's why i try here. thanks! output of lsusb -vv below sig... -- harry aka Rik Bobbaers K.U.Leuven - LUDIT -=- Tel: +32 485 52 71 50 [EMAIL PROTECTED] -=- http://people.linux-vserver.org/~harry For all of you reporting a score more than 100 as you iq lol @ you.How can you possibly score more than 100%? I'm very happy with my score of 89. (c)bash.org #758032 : 17:34 lucifer ~ ;lsusb -vv Unknown line at line 4533 Unknown line at line 4534 Unknown line at line 4535 Unknown line at line 4536 Unknown line at line 4537 Unknown line at line 4538 Unknown line at line 4539 Unknown line at line 4540 Unknown line at line 4541 Unknown line at line 4542 Unknown line at line 4543 Unknown line at line 4544 Unknown line at line 4545 Unknown line at line 4546 Unknown line at line 4547 Unknown line at line 4548 Unknown line at line 4549 Unknown line at line 4550 Unknown line at line 4551 Unknown line at line 4552 Unknown line at line 4553 Unknown line at line 4554 Unknown line at line 4555 Unknown line at line 4556 Unknown line at line 4557 Unknown line at line 4558 Unknown line at line 4559 Unknown line at line 4560 Unknown line at line 4561 Unknown line at line 4562 Unknown line at line 4563 Unknown line at line 4564 Unknown line at line 4565 Unknown line at line 4566 Unknown line at line 4567 Unknown line at line 4568 Unknown line at line 4569 Unknown line at line 4570 Unknown line at line 4571 Unknown line at line 4572 Unknown line at line 5917 Unknown line at line 5918 Unknown line at line 5919 Unknown line at line 5920 Unknown line at line 5921 Unknown line at line 5922 Unknown line at line 5923 Unknown line at line 5924 Unknown line at line 5925 Unknown line at line 5926 Unknown line at line 5927 Unknown line at line 5928 Unknown line at line 5929 Unknown line at line 5930 Unknown line at line 5931 Unknown line at line 5932 Unknown line at line 5933 Unknown line at line 5934 Unknown line at line 5935 Unknown line at line 5936 Unknown line at line 5937 Unknown line at line 5938 Unknown line at line 5939 Unknown line at line 5940 Unknown line at line 5941 Unknown line at line 5942 Unknown line at line 5943 Unknown line at line 5944 Unknown line at line 5945 Unknown line at line 5946 Unknown line at line 5947 Unknown line at line 5948 Unknown line at line 5949 Unknown line at line 5950 Unknown line at line 5951 Unknown line at line 5952 Unknown line at line 5959 Unknown line at line 5960 Unknown line at line 5961 Unknown line at line 5962 Unknown line at line 5963 Unknown line at line 5964 Unknown line at line 5965 Unknown line at line 5966 Unknown line at line 5967 Unknown line at line 5968 Unknown line at line 5969 Unknown line at line 5970 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 bMaxPacketSize0 8 idVendor 0x idProduct 0x bcdDevice0.00 iManufacturer 0 iProduct2 USB OHCI Root Hub iSerial 1 c480f000 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1
Re: [Linux-usb-users] No input interrupt endpoint
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 bcdUSB 1.10
Re: [Linux-usb-users] {Spam?} Re: No input interrupt endpoint
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. Dang it... I did something boneheaded. The lsusb -v I sent would not have included the KVM stuff in it as I did it via a remote connection. Here's a new one. 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 PortPwrCtrlMask0x76 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 PortPwrCtrlMask0x76 Hub Port Status: Port 1: .0100 power Port 2: .0100 power Bus 002 Device 009: ID 10d5:000d Uni Class Technology Co., Ltd Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at
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/ ___ Linux-usb-users@lists.sourceforge.net 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
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: linux-usb-users@lists.sourceforge.net 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/ ___ Linux-usb-users@lists.sourceforge.net 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
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
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
Re: [Linux-usb-users] No input interrupt endpoint
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/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
Re: [Linux-usb-users] usb power management
But CONFIG_USB_SUSPEND selected by on USB_OTG which inturn depends on ARCH_OMAP architecture. I want this for my PC. So I assume USB power management is not present. Or else can I somehow use CONFIG_USB_SUSPEND code for my architecture. - Original Message From: Alan Stern [EMAIL PROTECTED] To: Radha Mohan [EMAIL PROTECTED] Cc: linux-usb-users@lists.sourceforge.net Sent: Wednesday, May 9, 2007 9:09:25 PM Subject: Re: [Linux-usb-users] usb power management On Wed, 9 May 2007, Radha Mohan wrote: Hi, How to enable usb power management like suspend/resume in linux from the kernel. Is it already built in? It is already built into the 2.6.20 and 2.6.21 kernels, provided you set CONFIG_USB_SUSPEND when you build the kernel. Alan Stern __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - 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/ ___ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
