Please use Reply-To-All so that your messages will be seen on the mailing list. On Mon, 21 Jun 2010 shane000@xxxxxxxxxxxxxx wrote: > Hi Alan, > Thank you very much for taking time to reply. > I don't have the link to the original posting and can't recall what > 'original solution' was; > > but, i remember when I read the original posting, it did not have > solution for my issue. > > You recommended upgrade kernel to 2.6.34; > > I verified current kernel is 2.6.18 > > if you say "Linux does not turn off power to USB ports," how would > a newer version kernel affect/fix the problem? I don't know. But there have been so many changes between 2.6.18 and 2.6.34 (4 years of development!) that anything is possible. Think of it like this: There are 16 Linux kernel releases from 2.6.18 to 2.6.34. That's more than the number of releases of Windows between Windows-95 and Windows 7. (The analogy isn't really fair, but it does make a point.) > > if the O/S does not turn power off, (but the power is definitely > 'off' as neither the keyboard or optical mouse has any lights after > returning context from windows side to linux), then that implies the > loss of power to the keyboard and mouse if caused by the TrendNet > switch? That's right. But are you certain the power is truly off? The fact that the LEDs are off doesn't prove anything, because the LEDs don't get turned on until the power is on _and_ the keyboard or mouse is configured. It's possible that the power is on but the devices aren't configured. > Please correct me if my logic trail is incorrect, or if you can provide > other insight. > thank you. > shane.// When you build a newer kernel, I suggest you enable CONFIG_USB_DEBUG and see what shows up in the dmesg log. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
