On Sat, 2020-04-11 at 20:27 -0400, Tom Horsley wrote:
> On Sat, 11 Apr 2020 17:12:55 -0700
> Samuel Sieb wrote:
>
> > "lsusb -t" will show you what ports things are plugged into. The
> > backups might have been working but was it running at USB3 speeds or
> > just USB2? The cable might be
On Sat, 2020-04-11 at 18:57 -0400, Tom Horsley wrote:
> OK, I pulled every USB device one at a time till dmesg stopped
> printing this error. The device that finally made it stop
> was a USB 3 backup drive. I plugged it back in to the exact
> same usb port, and the messages did not start back up.
On Sat, 11 Apr 2020 17:12:55 -0700
Samuel Sieb wrote:
> "lsusb -t" will show you what ports things are plugged into. The
> backups might have been working but was it running at USB3 speeds or
> just USB2? The cable might be perfectly fine for USB2, but it sounds
> like the system thought it
On 4/11/20 5:08 PM, Tom Horsley wrote:
On Sat, 11 Apr 2020 19:58:33 -0400
Fred Smith wrote:
computers and their hardware being fickle, it may well start up
again once you actually try using it for backup. :(
Weirdly, the backups seem to have been working fine, so I'm
very confused by what it
On Sat, 11 Apr 2020 19:58:33 -0400
Fred Smith wrote:
> computers and their hardware being fickle, it may well start up
> again once you actually try using it for backup. :(
Weirdly, the backups seem to have been working fine, so I'm
very confused by what it might have been complaining about.
On Sat, Apr 11, 2020 at 06:57:10PM -0400, Tom Horsley wrote:
> On Sat, 11 Apr 2020 18:37:28 -0400
> Tom Horsley wrote:
>
> > DMESG shows this cable bad message once every 5 seconds, which
> > is a bit annoying.
>
> OK, I pulled every USB device one at a time till dmesg stopped
> printing this
On 4/11/20 3:57 PM, Tom Horsley wrote:
On Sat, 11 Apr 2020 18:37:28 -0400
Tom Horsley wrote:
DMESG shows this cable bad message once every 5 seconds, which
is a bit annoying.
OK, I pulled every USB device one at a time till dmesg stopped
printing this error. The device that finally made it
On Sat, 11 Apr 2020 18:37:28 -0400
Tom Horsley wrote:
> DMESG shows this cable bad message once every 5 seconds, which
> is a bit annoying.
OK, I pulled every USB device one at a time till dmesg stopped
printing this error. The device that finally made it stop
was a USB 3 backup drive. I plugged
What on earth is this message about?
usb usb2-port8: Cannot enable. Maybe the USB cable is bad?
earlier in dmesg it says:
usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.05
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: xHCI
