> My final idea: have you used a wireless keyboard or mouse?
or wireless headphones.
Nope, I don't have any other USB devices. Everything is connected through a
hub, so I only have one cable plugged in. I didn't miss anything.
I think it's pretty likely at this point my mobo is FUBAR. I'm go
I get a completely different device:
Bus 001 Device 005: ID 046d:081b Logitech, Inc. Webcam C310
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2
bDeviceProtocol
On Wed, 25 Jan 2023 at 14:54, Matthew McAllister
wrote:
> BTW, this is what the logs contained when the device was last successfully
> started. (It is indeed the bluetooth chip; no idea why it's not a PCI device.)
>
> 2023-01-04T23:44:08.519572-08:00 cockpit kernel: [3.927596] usb 1-5: new
On Wed, 2023-01-25 at 08:06 +, Tixy wrote:
> My final idea: have you used a wireless keyboard or mouse?
or wireless headphones.
On Tue, 2023-01-24 at 19:36 -0800, Matthew McAllister wrote:
[...]
> BTW, this is what the logs contained when the device was last
> successfully started. (It is indeed the bluetooth chip; no idea why
> it's not a PCI device.)
My final idea: have you used a wireless keyboard or mouse? (I'm
clutchi
Also, just try booting using linux 6.0 to see if that fixes anything. That
still seems to available, so if you uninstalled it, it can be reinstalled.
That is great advice, but before starting the thread I had already tried
booting 5.10, 5.19, 6.0, and 6.1 to no avail.
I was running 6.0.0-4-am
On Mon, 2023-01-23 at 19:54 -0800, Matthew McAllister wrote:
> > Also, looking at old kernel logs from back when it was working
> > would be useful (/var/log/kernel.N.gz where N if the biggest number
> > there is). Hopefully that will show what device is on usb 1-5
> > (though I believe port number
On Mon, 2023-01-23 at 19:54 -0800, Matthew McAllister wrote:
> > Also, looking at old kernel logs from back when it was working
> > would be useful (/var/log/kernel.N.gz where N if the biggest number
> > there is). Hopefully that will show what device is on usb 1-5
> > (though I believe port number
On Mon, 2023-01-23 at 19:54 -0800, Matthew McAllister wrote:
> Coincidentally, this is also exactly when the bluetooth on my motherboard
> stopped working. (The WiFi is on the same MT7921K chipset and still works
> weirdly).
>
> Can you suggest any steps other than straight-up RMA'ing the mobo?
Wouldn't the bluetooth device result in a PCIE error and not a USB error
though? The WiFi device shows as PCIE and it's on the same chip.
Thanks for your replies by the way.
Matthew
On 1/23/23 8:24 PM, Jeffrey Walton wrote:
On Mon, Jan 23, 2023 at 11:12 PM Matthew McAllister
wrote:
Also, lo
On Mon, Jan 23, 2023 at 11:12 PM Matthew McAllister
wrote:
>
> > Also, looking at old kernel logs from back when it was working would be
> > useful (/var/log/kernel.N.gz where N if the biggest number there is).
> > Hopefully that will show what device is on usb 1-5 (though I believe port
> > nu
Also, looking at old kernel logs from back when it was working would be useful
(/var/log/kernel.N.gz where N if the biggest number there is). Hopefully that
will show what device is on usb 1-5 (though I believe port numbers may change
over time and depend on what's plugged in).
That was the p
On Mon, 2023-01-23 at 13:54 +0500, Alexander V. Makartsev wrote:
[...]
> > [ 66.959391] usb 1-5: device not accepting address 5, error -71
> > [ 66.960945] usb usb1-port5: unable to enumerate USB device
> >
> > This occurs when *no USB cables are plugged in*. The kernel is
> > stalling the e
On 23.01.2023 11:40, Matthew McAllister wrote:
Hi all,
Since I upgraded packages a couple weeks ago, whenever I start my PC,
I have to wait 60 seconds for the kernel to enumerate USB devices.
Here's the log:
[ 8.815277] usb 1-5: device descriptor read/64, error -110
[ 24.431295] usb 1-5
Hi all,
Since I upgraded packages a couple weeks ago, whenever I start my PC, I
have to wait 60 seconds for the kernel to enumerate USB devices. Here's
the log:
[ 8.815277] usb 1-5: device descriptor read/64, error -110
[ 24.431295] usb 1-5: device descriptor read/64, error -110
[ 24.9
15 matches
Mail list logo
