I agree with you, you are right in everything you wrote! It is annoying to see
theoretic numbers and not the actual numbers the hardware implementing the
specification can support but something else is in my mind
too...N�r��yb�X��ǧv�^�){.n�+{��^n�r���z���h�&��
Why didn't you say so (given that you were replying to a message that I
sent)?
Because I thought it would go to the correct existing subject on the
first place.
I don't know. What new subject are you referring to?
Some days ago, the first two messages I have sent were not linked there:
Good question. I don't know the answer; it may be hidden in a part
of the system log that you didn't post.
Nothing unusual was found on the log. If you need more information, just
tell me what you need.
This is a known bug in the 4.8 kernel, caused by changes to the timer
code. A
My C-Media USB speakers do not work on Ubuntu 16.10 with 4.8.0 on my AMD
KABINI USB 2.0 port. Using Ubuntu 16.04 with 4.4.0 on the same machine
at the same port with the same cable fixes the issue.
If I put the speakers on any USB 3.0 connector then it works both in
16.10 and 16.04!!
Why do
I never had them in the first place.
Yes I know, the question was asked to the thread creator!
Why did the messages move to a new subject and were not added to the
original subject?
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to
Second try...
Hello guys! Did you have any progress on this? Do you still have the
affected machine and devices?
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Hello guys! Did you have any progress on this? Do you still have the
affected machine and devices?
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
"-517" is -EPROBE_DEFER, it means some resources for this device
are not ready.
Thanks for the info, I fell on it too on a completely different box but
had no time to find what it is. Now it is clear what is going on.
Here is how the bug reporter fell on it:
dmesg shows that he performed
