On Tue, Feb 06, 2018 at 07:54:53PM +0100, Herbert Poetzl wrote:
> On Tue, Feb 06, 2018 at 07:38:42PM +0200, Mathias Nyman wrote:
>> On 01.02.2018 02:43, Herbert Poetzl wrote:
>>> On Wed, Jan 31, 2018 at 04:58:58PM +0200, Mathias Nyman wrote:
>>>> On 30.01.2018 08:06,
On Tue, Feb 06, 2018 at 07:38:42PM +0200, Mathias Nyman wrote:
> On 01.02.2018 02:43, Herbert Poetzl wrote:
>> On Wed, Jan 31, 2018 at 04:58:58PM +0200, Mathias Nyman wrote:
>>> On 30.01.2018 08:06, Herbert Poetzl wrote:
>>>> On Mon, Jan 29, 2018 at 02:26:52PM +0200,
On Wed, Jan 31, 2018 at 04:58:58PM +0200, Mathias Nyman wrote:
> On 30.01.2018 08:06, Herbert Poetzl wrote:
>> On Mon, Jan 29, 2018 at 02:26:52PM +0200, Mathias Nyman wrote:
>>> On 20.01.2018 06:20, Herbert Poetzl wrote:
>>>> I've recently acquired a Gig
On Mon, Jan 29, 2018 at 02:26:52PM +0200, Mathias Nyman wrote:
> On 20.01.2018 06:20, Herbert Poetzl wrote:
>> I've recently acquired a Gigabyte Z170X Gaming 7-EK motherboard
>> with the Intel Z170 chipset and Sunrise Point-H USB 3.0 xHCI
>> Controller for running Linux
I've recently acquired a Gigabyte Z170X Gaming 7-EK motherboard
with the Intel Z170 chipset and Sunrise Point-H USB 3.0 xHCI
Controller for running Linux.
Now most things seem to work fine (some problems with UEFI but
that was kind of expected), but the xhci_hcd module is filling
up my log files
