On Thu, 3 Jan 2013, Octavio Alvarez wrote: > I just wanted to mention the following link to this FAQ on the Asus > website. They blame the OS (Vista) for this, but they don't provide any > workaround information, except what we already know: either switch to > +5VSB or disable wakeups. > > http://support.asus.com/FAQ/Detail.aspx?no=7E9E847A-6F0F-DE5A-BF73-6733215FD3BD&p=1&m=P5N-E%20SLI > > Looking for "7E9E847A-6F0F-DE5A-BF73-6733215FD3BD" site:asus.com > shows that this FAQ is not exclusive of nVidia-based systems. That FAQ agrees pretty closely with what we have already concluded. > So the title of this bug may be wrong. I wonder if there is any > non-Asus system with MCP51 that behaves correctly. > > And yes, I second Frank's question: > > > Is there way to determine if the port is powered permanently? Not that I know of. > Does the output of any utility (dmidecode, or whatever other > utility) change if power is on +5V or +5VSB? Any BIOS setting? I don't think so. But I'm no expert on ASUS's hardware. > If not, then what would the sanest default be? Where to document > this cas in a clean, user friendly way? The sanest default is what my patch does: disable wakeup for OHCI controllers on computers with ASUS boards. I'm open to suggestions on the best way to document it for users. 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
