Hide Forgot
Description of problem: I don't know that is a real problem or not, but possibly can be an wrong detection. Maybe unsupported hw? Version-Release number of selected component (if applicable): Kernel 4.4.4. How reproducible: Always Actual results: [ 1.680975] usb 2-1.8: New USB device found, idVendor=0a5c, idProduct=5800 [ 1.680984] usb 2-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1.680990] usb 2-1.8: Product: 5880 [ 1.680996] usb 2-1.8: Manufacturer: Broadcom Corp [ 1.681001] usb 2-1.8: SerialNumber: 0123456789ABCD [ 1.681232] usb 2-1.8: config 0 descriptor?? Expected results: Correct identification? Additional info: dmesg | lsusb provides the following: Bus 002 Device 005: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 002 Device 004: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module Bus 002 Device 003: ID 413c:8184 Dell Computer Corp. F3607gw v2 Mobile Broadband Module Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4db1 Primax Electronics, Ltd Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.