From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218773] New: device not initialized
Date: Thu, 25 Apr 2024 04:11:54 +0000 [thread overview]
Message-ID: <bug-218773-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218773
Bug ID: 218773
Summary: device not initialized
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: roman.gruber@gmx.at
Regression: No
This is kina a longterm old bug which is 10 years old
Cold Boot
Where is my mouse?
connected via ASUS X670-P Prime Mainboard -> usb cable -> Monitor ASUS PA278QV
-> USB Mouse
Sienna_Cichlid /home/roman # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05dc:a410 Lexar Media, Inc. JumpDrive 128MB/256MB
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 2516:014f Cooler Master Co., Ltd. CK351 Gaming Optical
Switch Keyboard
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 007 Device 007: ID 0763:410c M-Audio AIR 192 6
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
replug cable / oh mouse is here ...
i3wm / Xorg-Server Running / openrc ...
could open already vivaldi browser, terminal and other stuff. The X Server was
fully functional and also the shell was working and also the keyboard was
already working.
Sienna_Cichlid /home/roman # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05dc:a410 Lexar Media, Inc. JumpDrive 128MB/256MB
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 003 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 2516:014f Cooler Master Co., Ltd. CK351 Gaming Optical
Switch Keyboard
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 007 Device 007: ID 0763:410c M-Audio AIR 192 6
Bus 007 Device 008: ID 093a:2533 Pixart Imaging, Inc. Gaming Mouse
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Sienna_Cichlid /home/roman # uname -a
Linux Sienna_Cichlid 6.8.6-gentoo_15_04_2024 #1 SMP PREEMPT Mon Apr 15 05:28:26
CEST 2024 x86_64 AMD Ryzen 5 7600X 6-Core Processor AuthenticAMD GNU/Linux
Happens regularly with different kernel version, since I own that hardware
April 2023.
USB Devices not properly found / working / especially mice is a very old bug
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-04-25 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 4:11 bugzilla-daemon [this message]
2024-04-25 4:12 ` [Bug 218773] device not initialized bugzilla-daemon
2024-04-26 9:50 ` bugzilla-daemon
2024-04-26 9:51 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-218773-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.