On Mon, 23 Nov 2015, Patrick Shirkey wrote:
> Thanks Alan,
>
> FYI, running these commands exhibits some interesting behavior on my machine.
>
> Unbinding disables all external ports.
>
> [7946053.417529] xhci_hcd :00:14.0: remove, state 4
> [7946053.417537] usb usb4: USB disconnect, device
On 23.11.2015 04:31, Alan Stern wrote:
On Sun, 22 Nov 2015, Peter Stuge wrote:
Patrick Shirkey wrote:
if the kernel does have support for xHCI, we assume that
the user will prefer xHCI over EHCI if the motherboard has xHCI.
Obviously the solution above should suffice for my purposes but out
On Sun, 2015-11-22 at 21:31 -0500, Alan Stern wrote:
> In general it's best not to make things too complicated. Perhaps the
> switch could be changed at runtime, say whenever xhci-hcd binds to or
> unbinds from the motherboard's controller. But this could have
> undesirable consequences.
I am af
On Mon, November 23, 2015 1:24 pm, Alan Stern wrote:
> On Mon, 23 Nov 2015, Patrick Shirkey wrote:
>
>> >> Is there a method to determine if the system has multiple or single
>> >> controllers available?
>> >
>> > lspci will tell you.
>> >
>> >> Do you or anyone else here have a link to the sysfs
On Sun, 22 Nov 2015, Peter Stuge wrote:
> Patrick Shirkey wrote:
> > > if the kernel does have support for xHCI, we assume that
> > > the user will prefer xHCI over EHCI if the motherboard has xHCI.
> >
> > Obviously the solution above should suffice for my purposes but out
> > of interest is it
On Mon, 23 Nov 2015, Patrick Shirkey wrote:
> >> Is there a method to determine if the system has multiple or single
> >> controllers available?
> >
> > lspci will tell you.
> >
> >> Do you or anyone else here have a link to the sysfs command to unbind
> >> the
> >> controller?
> >
> > If you prov
Patrick Shirkey wrote:
> > if the kernel does have support for xHCI, we assume that
> > the user will prefer xHCI over EHCI if the motherboard has xHCI.
>
> Obviously the solution above should suffice for my purposes but out
> of interest is it viable to make the switch accessible to run time
> co
On Mon, November 23, 2015 2:43 am, Alan Stern wrote:
> On Sun, 22 Nov 2015, Patrick Shirkey wrote:
>
>> > It _is_ possible to disable xHCI at the system level. By sending the
>> > proper command to the appropriate sysfs file, you can unbind the
>> > xhci-hcd driver from the xHCI controller. This
On Sun, 22 Nov 2015, Patrick Shirkey wrote:
> > It _is_ possible to disable xHCI at the system level. By sending the
> > proper command to the appropriate sysfs file, you can unbind the
> > xhci-hcd driver from the xHCI controller. This will disable the
> > controller, and so all further USB com
On Sun, November 22, 2015 5:41 am, Alan Stern wrote:
> On Sat, 21 Nov 2015, Patrick Shirkey wrote:
>
>> On Sat, November 21, 2015 9:35 am, Peter Stuge wrote:
>> > Patrick Shirkey wrote:
>> >> > You essentially have to educate yourself on silicon level (ie. what
>> >> > hardware IP is being used in
On Sat, 21 Nov 2015, Patrick Shirkey wrote:
> On Sat, November 21, 2015 9:35 am, Peter Stuge wrote:
> > Patrick Shirkey wrote:
> >> > You essentially have to educate yourself on silicon level (ie. what
> >> > hardware IP is being used in which consumer products) to sustain a
> >> > dependency on 1
On Sat, November 21, 2015 9:35 am, Peter Stuge wrote:
> Patrick Shirkey wrote:
>> > You essentially have to educate yourself on silicon level (ie. what
>> > hardware IP is being used in which consumer products) to sustain a
>> > dependency on 127 possible devices per bus.
>> >
>> > I guess you'll
Patrick Shirkey wrote:
> > You essentially have to educate yourself on silicon level (ie. what
> > hardware IP is being used in which consumer products) to sustain a
> > dependency on 127 possible devices per bus.
> >
> > I guess you'll find that there are only very few xHCI IPs out there,
> > prob
On Sat, November 21, 2015 3:46 am, Peter Stuge wrote:
> Patrick Shirkey wrote:
>> I have read various forum posts and some of the archive from this list
>> about the following error message:
>>
>> Not enough host controller resources for new device state
>>
>> Some people have had success with dis
Patrick Shirkey wrote:
> I have read various forum posts and some of the archive from this list
> about the following error message:
>
> Not enough host controller resources for new device state
>
> Some people have had success with disabling XHCI at the BIOS level.
>
> That seems to be an unnec
On Fri, 20 Nov 2015, Patrick Shirkey wrote:
> Hi,
>
> I have read various forum posts and some of the archive from this list
> about the following error message:
>
> Not enough host controller resources for new device state
>
> Some people have had success with disabling XHCI at the BIOS level.
Hi, (ever so awesome and we are all super unworthy) - Kernel peoples!
I have found this dmesg error message which appears to be written in
the xHCI host controller. (or maybe it originated in EHCI, i don't
know.)
None the less the issue is: "Not enough host controller resources for
new device sta
17 matches
Mail list logo
