On 01/04/18 09:29, Pablo wrote:
> Hi again,
>
> I forgot to comment that this issue also appear in Debian 9 (my other
> PC)...
>
As I posted earlier, this seems to be related to the version of Linux.
I do not have this problem with
Meerkat> uname -a
Linux Meerkat 4.13.9-041309-generic #201710
On 08/07/2017 11:39 PM, Kai-Heng Feng wrote:
> Probably. Although a quick look at the USB stack difference from
> 4.4.0-78.99 to 4.4.0-89.112, I can't find commits related to this issue.
>
> But feel free to reopen the bug if this happens again.
>
> ** Changed in: linux (Ubuntu)
> Status:
On 08/03/2017 10:54 PM, Kai-Heng Feng wrote:
> Okay, I just found a hub with the same VIA chip inside.
> Remote wakeup works when autosuspend is enabled.
>
> Hub like this generally can connect to auxiliary power cord. Does power
> cord connection make any difference?
>
I upgraded the system by
On 08/03/2017 10:54 PM, Kai-Heng Feng wrote:
> Okay, I just found a hub with the same VIA chip inside.
> Remote wakeup works when autosuspend is enabled.
>
> Hub like this generally can connect to auxiliary power cord. Does power
> cord connection make any difference?
>
I normally run the hub wi
On 06/05/2017 08:57 PM, Kai-Heng Feng wrote:
> If you plugged a USB mouse or keyboard to the same port, will it be
> recognized?
>
I plugged a Microsoft USB 2.0 mouse into the externa Plugable USB 3.0
hub and it was recognized.
--
You received this bug notification because you are a member of
On 06/02/2017 12:27 AM, Kai-Heng Feng wrote:
> Sounds like there are two problems here,
> 1. The external drive does not work well in UAS mode (see previous comment)
> 2. The VIA hub has a remote wakeup bug.
>
> uname -a
Linux P9X79 4.12.0-041200rc2-generic #201705212331 SMP Mon May 22
03:32:26
As suggested by kai.heng.feng, I installed the 4.12.0-041200rc2 kernel.
If I connect my WD My Passport drive into an Plugable 7-port, external
USB 3.0 hub, it is not recognized. 'sudo lsusb -v' causes the drive to
be recognized and I can mount it. If I disconnect the drive, wait a few
seconds
On 05/30/2017 08:14 AM, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
This did not start happening after an upgrade.
I do not know of a previous version where this did work.
