Bug 218773 - device not initialized
Summary: device not initialized
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: All Linux
: P3 high
Assignee: Default virtual assignee for Drivers/USB
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-25 04:11 UTC by Roman Gruber
Modified: 2024-04-26 09:51 UTC (History)
0 users

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Roman Gruber 2024-04-25 04:11:54 UTC 
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
Comment 1 Roman Gruber 2024-04-25 04:12:19 UTC 
I am busy working on a job, last build kernel was on the 14th of april 2024.
Comment 2 Artem S. Tashkinov 2024-04-26 09:50:14 UTC 
ASUS X670-P is a brand new motherboard, this issue can't be 10 years old.

1. Update your motherboard BIOS to the latest release.
2. If possible please confirm this bug affects Windows 10/11 running on your device.
3. Make sure you've tried a completely different USB cable.
Comment 3 Artem S. Tashkinov 2024-04-26 09:51:09 UTC 
Oh, and please upload `sudo dmesg > /tmp/dmesg.txt` (once this all happens, i.e. the mouse is not detected first and then gets detected).
Note You need to log in before you can comment on or make changes to this bug.