Public bug reported:

The USB hub identified as: "214b:7000  USB2.0 HUB" presents a problem on
Linux where often it is only detected after another device (for example
a mouse) is connected to it.

On the computer's firmware screen and configuration, and on Windows, the
hub works fine: once connected, it is detected and devices connected on
it are detected.

On Linux, most of the times nothing happens or only the hub is detected
(not the devices connected to it). After one of the devices is
disconnected and reconnected, or another USB device is connected in the
hub, then the hub and all devices connected to it are detected at once.

I believe this is a problem related to the Linux kernel because I never
observed this behaviour on the computer's firmware or on Windows.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-53-generic 5.4.0-53.59
ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Thu Nov 19 23:54:44 2020
HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc
InstallationDate: Installed on 2017-06-13 (1255 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80UG
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1 
kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 
i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc 
log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x100000 nbd.nbds_max=2 
nbd.max_part=127
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-53-generic N/A
 linux-backports-modules-5.4.0-53-generic  N/A
 linux-firmware                            1.187.4
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2019-12-22 (333 days ago)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UG
dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Confirmed


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904953

Title:
  USB2.0 HUB only works after an USB device is connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904953/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to