> 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
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
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
wr
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
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
> First question: do you have the firmware-realtek package installed?
That... is a great question. And the answer is no, I do not.
And I have now installed firmware-realtek, and it has solved my problem.
That's what I get for buying a mobo without researching the network chip.
Thanks so much!
Greetings,
I'm running bookworm and I have an odd issue with a new desktop
computer. Every time I boot, the Ethernet controller will repeatedly
turn off and on again for several minutes. Here is a snippet of what
this looks like in dmesg:
[ 273.008517] r8169 :05:00.0 eno1: Link is Down
Hi Piotr,
Thank you for your reply. I almost missed it, sorry to say.
> You are using non-bullseye kernel, bullseye is on 5.10.0-9-amd64.
Where is that from?
I'm pretty sure you hit the mark! I had completely forgotten that I
built my own kernel to try out a new driver. I'll either upgrade t
Hi folks,
I've discovered that PCSX2 causes an Intel GPU hang on bullseye. The
whole display manager has to be restarted after the crash.
I'm not sure if this occurs in bookworm. I would report the bug
directly, but I don't know which maintainer would be the best to take a
look at it. My gue
10 matches
Mail list logo
