RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1930568 - Update hwdb to support new HW
Summary: Update hwdb to support new HW
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.3
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: David Tardon
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks: 1898973 2005009
TreeView+ depends on / blocked
 
Reported: 2021-02-19 07:41 UTC by Rick
Modified: 2021-11-10 09:53 UTC (History)
11 users (show)

Fixed In Version: systemd-239-51.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2005009 (view as bug list)
Environment:
Last Closed: 2021-11-09 19:55:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhat-plumbers systemd-rhel8 pull 209 0 None open Update hwdb 2021-09-16 16:13:01 UTC
Red Hat Product Errata RHBA-2021:4469 0 None None None 2021-11-09 19:56:17 UTC

Description Rick 2021-02-19 07:41:59 UTC 
Description of problem:

USB Device Pilot IV idVendor (2a4b:0400) Description is blank when check by command lsusb.
#lsusb
Bus 001 Device 008: ID 04b3:4010 IBM Corp. 
Bus 001 Device 002: ID 2a4b:0400  

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.Search information device number 2a4b:0400 by command lsusb.

Actual results:

USB Device Description is blank.
#lsusb
Bus 001 Device 008: ID 04b3:4010 IBM Corp. 
Bus 001 Device 002: ID 2a4b:0400  

Expected results:

Expected result: USB Device have Description 

Additional info:
Lenovo had submitted request to register this device as Emulex device and it was accepted by the usb-ids repo. Need to upgrade usb.ids version above 2021.01.29 in hwdata package.


https://usb-ids.gowdy.us/read/UD?restrict=2

2a45 Meizu Corp.  
2a47 Mundo Reader, S.L.  
2a4b EMULEX Corporation
Comment 1 Vitezslav Crhonek 2021-02-19 11:30:51 UTC 
Thanks for the bug report!

This is going to be fixed in hwdata-0.314-8.8.el8 available on RHEL-8.4.0 GA:

$ cat usb.ids:
...
# Version: 2021.01.29
# Date:    2021-01-29 20:34:11
...
2a4b  EMULEX Corporation
        0400  Pilot4 Integrated Hub
...
Comment 2 dhsia 2021-02-22 03:55:53 UTC 
(In reply to Vitezslav Crhonek from comment #1)
> Thanks for the bug report!
> 
> This is going to be fixed in hwdata-0.314-8.8.el8 available on RHEL-8.4.0 GA:
> 
> $ cat usb.ids:
> ...
> # Version: 2021.01.29
> # Date:    2021-01-29 20:34:11
> ...
> 2a4b  EMULEX Corporation
>         0400  Pilot4 Integrated Hub
> ...


Hi Vitezslav
We have a feature request for usb-utils 013 build for RHEL8.4. 
https://bugzilla.redhat.com/show_bug.cgi?id=1855548

In the 013 build, udev hwdb is included, It is more friendly to get vendor and product names.
Comment 3 Rick 2021-02-22 08:37:14 UTC 
(In reply to Vitezslav Crhonek from comment #1)
> Thanks for the bug report!
> 
> This is going to be fixed in hwdata-0.314-8.8.el8 available on RHEL-8.4.0 GA:
> 
> $ cat usb.ids:
> ...
> # Version: 2021.01.29
> # Date:    2021-01-29 20:34:11
> ...
> 2a4b  EMULEX Corporation
>         0400  Pilot4 Integrated Hub
> ...

Thanks Vitezslav

   Will you have fix plan on RHEL 8.3? If no. Is there any workaround to update usb.ids ? 

Rick Hsu
Comment 4 Vitezslav Crhonek 2021-03-09 08:12:53 UTC 
Hi Rick,

Sorry, I don't know the answer to your question. We update hwdata every release. I guess
no special fix for RHEL8.3 is needed, but please contact your support to check that.
Comment 5 Rick 2021-08-17 07:22:47 UTC 
Hi Vitezslav,

   After I verify this issue on RHEL 8.5 (RHEL-8.5.0-20210730.n.0-x86_64-dvd1), this problem still exists although the latest usb.ids has been used.

    [root@localhost ~]# less /usr/share/hwdata/usb.ids
...
# Version: 2021.06.16
# Date:    2021-06-16 20:34:10
...
2a4b  EMULEX Corporation
        0400  Pilot4 Integrated Hub
...

    But this issue can be fixed by added below data to /usr/lib/udev/hwdb.d/20-usb-vendor-model.hwdb.

usb:v2A4B*
 ID_VENDOR_FROM_DATABASE=ENULEX Corporation Pilot4 Integrated Hub

    And then update the binary database.
[root@localhost ~]# systemd-hwdb update

    Finally I can see the device name for 2a4b:0400.
[root@localhost ~]# lsusb
Bus 002 Device 002: ID 8564:1000 Transcend Information, Inc. JetFlash
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0624:0296 Avocent Corp.
Bus 001 Device 004: ID 04b3:4010 IBM Corp.
Bus 001 Device 002: ID 2a4b:0400 ENULEX Corporation Pilot4 Integrated Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   
    It seems like we still need to add below record in 20-usb-vendor-model.hwdb file.

usb:v2A4B*
 ID_VENDOR_FROM_DATABASE=ENULEX Corporation Pilot4 Integrated Hub

   Can you please double confirm it ? Please let me know if you decided to implement this fix in RHEL 8.5.   


--Rick Hsu
Comment 6 Vitezslav Crhonek 2021-08-17 07:59:33 UTC 
(In reply to Rick from comment #5)
> Hi Vitezslav,
> 
>    After I verify this issue on RHEL 8.5
> (RHEL-8.5.0-20210730.n.0-x86_64-dvd1), this problem still exists although
> the latest usb.ids has been used.
> 
>     [root@localhost ~]# less /usr/share/hwdata/usb.ids
> ...
> # Version: 2021.06.16
> # Date:    2021-06-16 20:34:10
> ...
> 2a4b  EMULEX Corporation
>         0400  Pilot4 Integrated Hub
> ...
> 
>     But this issue can be fixed by added below data to
> /usr/lib/udev/hwdb.d/20-usb-vendor-model.hwdb.
> 
> usb:v2A4B*
>  ID_VENDOR_FROM_DATABASE=ENULEX Corporation Pilot4 Integrated Hub
> 
>     And then update the binary database.
> [root@localhost ~]# systemd-hwdb update
> 
>     Finally I can see the device name for 2a4b:0400.
> [root@localhost ~]# lsusb
> Bus 002 Device 002: ID 8564:1000 Transcend Information, Inc. JetFlash
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 0624:0296 Avocent Corp.
> Bus 001 Device 004: ID 04b3:4010 IBM Corp.
> Bus 001 Device 002: ID 2a4b:0400 ENULEX Corporation Pilot4 Integrated Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>    
>     It seems like we still need to add below record in
> 20-usb-vendor-model.hwdb file.
> 
> usb:v2A4B*
>  ID_VENDOR_FROM_DATABASE=ENULEX Corporation Pilot4 Integrated Hub
> 
>    Can you please double confirm it ? Please let me know if you decided to
> implement this fix in RHEL 8.5.   
> 
> 
> --Rick Hsu

Hi Rick,

/usr/lib/udev/hwdb.d/20-usb-vendor-model.hwdb file is part of systemd-udev.

# rpm -qf /usr/lib/udev/hwdb.d/20-usb-vendor-model.hwdb
systemd-udev-239-49.el8.x86_64

I can see that systemd upstream already contains data you need:
(https://raw.githubusercontent.com/systemd/systemd/main/hwdb.d/20-usb-vendor-model.hwdb)
...
usb:v2A4B*
 ID_VENDOR_FROM_DATABASE=EMULEX Corporation

usb:v2A4Bp0400*
 ID_MODEL_FROM_DATABASE=Pilot4 Integrated Hub
...

I guess it's only matter of systemd-udev update then, reassigning to systemd.
Comment 7 Rick 2021-08-17 08:05:46 UTC 
Hi Vitezslav,

   Thanks for your confirmation. Yes, we need to update systemd-udev. Do we have chance to implement the fix in RHEL 8.5? 

--Rick Hsu
Comment 8 David Tardon 2021-08-19 10:26:30 UTC 
We haven't been updating hwdb in the past, but I think we should do it regularly to support new HW. I don't see any drawbacks anyway.
Comment 14 Plumber Bot 2021-09-16 14:20:27 UTC 
fix merged to github master branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/207
Comment 15 Plumber Bot 2021-09-23 09:20:37 UTC 
fix merged to github rhel-8.5.0 branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/209
Comment 20 Rick 2021-10-05 00:05:48 UTC 
Hi Red Hat,

     Can you please provide the steps for verifying this issue? 

--Rick Hsu
Comment 21 Lukáš Nykrýn 2021-10-05 08:43:06 UTC 
Hi Rick,

We do not do any verification for specific devices, we just check the consistency of the hwdb with the upstream test you can find here:
https://github.com/systemd/systemd/blob/main/test/hwdb-test.sh

Also, please do not touch the status of the bugzilla, it is strongly tied to our internal processes and you could break our automation.

Lukas
Comment 22 Rick 2021-10-05 09:37:15 UTC 
Hi Lukas,

    Thanks. I got it. Since RHEL 8.5 is under developing. May I know which RHEL 8.5 release will merge this fix ?

--Rick Hsu
Comment 24 errata-xmlrpc 2021-11-09 19:55:38 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4469
Note You need to log in before you can comment on or make changes to this bug.