This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2164216 - Can't reload a new driver from driver update disk
Summary: Can't reload a new driver from driver update disk
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: anaconda
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
Sagar Dubewar
URL:
Whiteboard:
Depends On:
Blocks: 2129768 2144442
TreeView+ depends on / blocked
 
Reported: 2023-01-24 19:15 UTC by Jiri Kortus
Modified: 2023-09-18 16:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
.Unable to load an updated driver from the driver update disc in the installation environment A new version of a driver from the driver update disc might not load if the same driver from the installation initial ramdisk has already been loaded. As a consequence, an updated version of the driver cannot be applied to the installation environment. As a workaround, use the `modprobe.blacklist=` kernel command line option together with the `inst.dd` option. For example, to ensure that an updated version of the `virtio_blk` driver from a driver update disc is loaded, use `modprobe.blacklist=virtio_blk` and then continue with the usual procedure to apply drivers from the driver update disk. As a result, the system can load an updated version of the driver and use it in the installation environment.
Clone Of:
Environment:
Last Closed: 2023-09-18 16:05:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4762 0 None Migrated None 2023-09-18 16:05:51 UTC
Red Hat Issue Tracker RHELPLAN-146344 0 None None None 2023-09-18 16:03:54 UTC

Description Jiri Kortus 2023-01-24 19:15:27 UTC 
Created attachment 1940275 [details]
syslog

Created attachment 1940275 [details]
syslog

Description of problem:
It's not possible to load a new driver from driver update disk instead of an original one which is being used (in my case it was virtio_blk, used for storage access):
...
DD: starting interactive mode

(Page 1 of 1) Driver disk device selection
    /DEVICE  TYPE     LABEL                UUID
 1) dm-1     xfs                           217055ce-6ad4-4a69-a0a7-cf9dfc97f91d
 2) sr0      iso9660  RHEL-9-2-0-BaseOS-x8 2023-01-14-09-33-15-00
 3) dm-0     swap                          16b348b1-ce4f-4fa8-8b16-0f0e9618b2f5
 4) vda2     LVM2_mem                      G5h2p0-OTbn-SXVd-9T7E-F0s6-xI32-YA7z
 5) vda1     xfs                           fc3957f4-0679-45e2-adde-c5e399bdea27
 6) sr1      iso9660                       2023-01-17-16-03-10-00
# to select, 'r'-refresh, or 'c'-continue: DD: Examining /dev/sr1
mount: /media/DD-1: WARNING: source write-protected, mounted read-only.

(Page 1 of 1) Select drivers to install
 1) [ ] /media/DD-1/rpms/x86_64/kmod-redhat-e1000e-1.0.1_dup7.4a-1.el9.x86_64.rpm
 2) [ ] /media/DD-1/rpms/x86_64/kmod-redhat-virtio_blk-1.0.1_dup7.4a-1.el9.x86_64.rpm
# to toggle selection, or 'c'-continue: 
(Page 1 of 1) Select drivers to install
 1) [x] /media/DD-1/rpms/x86_64/kmod-redhat-e1000e-1.0.1_dup7.4a-1.el9.x86_64.rpm
 2) [ ] /media/DD-1/rpms/x86_64/kmod-redhat-virtio_blk-1.0.1_dup7.4a-1.el9.x86_64.rpm
# to toggle selection, or 'c'-continue: 
(Page 1 of 1) Select drivers to install
 1) [x] /media/DD-1/rpms/x86_64/kmod-redhat-e1000e-1.0.1_dup7.4a-1.el9.x86_64.rpm
 2) [x] /media/DD-1/rpms/x86_64/kmod-redhat-virtio_blk-1.0.1_dup7.4a-1.el9.x86_64.rpm
# to toggle selection, or 'c'-continue: DD: Extracting: kmod-redhat-e1000e
DD: Extracting: kmod-redhat-virtio_blk

(Page 1 of 1) Driver disk device selection
    /DEVICE  TYPE     LABEL                UUID
 1) dm-1     xfs                           217055ce-6ad4-4a69-a0a7-cf9dfc97f91d
 2) sr0      iso9660  RHEL-9-2-0-BaseOS-x8 2023-01-14-09-33-15-00
 3) dm-0     swap                          16b348b1-ce4f-4fa8-8b16-0f0e9618b2f5
 4) vda2     LVM2_mem                      G5h2p0-OTbn-SXVd-9T7E-F0s6-xI32-YA7z
 5) vda1     xfs                           fc3957f4-0679-45e2-adde-c5e399bdea27
 6) sr1      iso9660                       2023-01-17-16-03-10-00
# to select, 'r'-refresh, or 'c'-continue: modprobe: FATAL: Module virtio_blk is in use.


This, however, works fine on RHEL-8.8 (using modified drivers that print 'DRIVERDISK:...' when loaded):
...
(Page 1 of 1) Driver disk device selection
    /DEVICE  TYPE     LABEL                UUID
 1) vda1     xfs                           fc3957f4-0679-45e2-adde-c5e399bdea27
 2) vda2     LVM2_mem                      G5h2p0-OTbn-SXVd-9T7E-F0s6-xI32-YA7z
 3) sr0      iso9660  RHEL-8-8-0-BaseOS-x8 2023-01-22-20-30-07-00
 4) sr1      iso9660                       2023-01-23-08-05-38-00
# to select, 'r'-refresh, or 'c'-continue: DD: Examining /dev/sr1
mount: /media/DD-1: WARNING: device write-protected, mounted read-only.

(Page 1 of 1) Select drivers to install
 1) [ ] /media/DD-1/rpms/x86_64/kmod-redhat-e1000e-1.0.1_dup7.4a-1.el8.x86_64.rpm
 2) [ ] /media/DD-1/rpms/x86_64/kmod-redhat-virtio_blk-1.0.1_dup7.4a-1.el8.x86_64.rpm
 3) [ ] /media/DD-1/rpms/x86_64/kmod-redhat-e1000-1.0.1_dup7.4a-1.el8.x86_64.rpm
# to toggle selection, or 'c'-continue: 
(Page 1 of 1) Select drivers to install
 1) [x] /media/DD-1/rpms/x86_64/kmod-redhat-e1000e-1.0.1_dup7.4a-1.el8.x86_64.rpm
 2) [ ] /media/DD-1/rpms/x86_64/kmod-redhat-virtio_blk-1.0.1_dup7.4a-1.el8.x86_64.rpm
 3) [ ] /media/DD-1/rpms/x86_64/kmod-redhat-e1000-1.0.1_dup7.4a-1.el8.x86_64.rpm
# to toggle selection, or 'c'-continue: 
(Page 1 of 1) Select drivers to install
 1) [x] /media/DD-1/rpms/x86_64/kmod-redhat-e1000e-1.0.1_dup7.4a-1.el8.x86_64.rpm
 2) [x] /media/DD-1/rpms/x86_64/kmod-redhat-virtio_blk-1.0.1_dup7.4a-1.el8.x86_64.rpm
 3) [ ] /media/DD-1/rpms/x86_64/kmod-redhat-e1000-1.0.1_dup7.4a-1.el8.x86_64.rpm
# to toggle selection, or 'c'-continue: DD: Extracting: kmod-redhat-e1000e
DD: Extracting: kmod-redhat-virtio_blk

(Page 1 of 1) Driver disk device selection
    /DEVICE  TYPE     LABEL                UUID
 1) vda1     xfs                           fc3957f4-0679-45e2-adde-c5e399bdea27
 2) vda2     LVM2_mem                      G5h2p0-OTbn-SXVd-9T7E-F0s6-xI32-YA7z
 3) sr0      iso9660  RHEL-8-8-0-BaseOS-x8 2023-01-22-20-30-07-00
 4) sr1      iso9660                       2023-01-23-08-05-38-00
# to select, 'r'-refresh, or 'c'-continue: 
...
[anaconda root@localhost ~]# dmesg | grep DRIVER
[  207.240946] DRIVERDISK: virtio_blk loaded
[  207.249243] e1000e: DRIVERDISK: e1000e loaded


Version-Release number of selected component (if applicable):
anaconda-34.25.2.6-1.el9, dracut-057-20.git20221213.el9, kernel-5.14.0-234.el9 (RHEL-9.2.0-20230115.7)

How reproducible:
100%

Steps to Reproduce:
1. Prepare a driver update disk (I just used an ISO connected to a second CD-ROM drive in a VM) containing a driver that will be in use later on (i. e. driver for a block device present in the system). Also create proper conditions so that the driver can't get reloaded -- in case of virtio_blk, it's necessary to create partitioning on a virtio block device first.
2. Start installation with 'inst.dd'.
3. Select a driver that's already in use and continue.

Actual results:
The driver is not loaded in the installation environment.

Expected results:
The driver is loaded in the installation environment and is present in the installed system.
Comment 4 Jiri Kortus 2023-01-30 12:15:14 UTC 
Additional note, as it may not be obvious from bug description: The driver is not loaded during installation, but is loaded in the installed system.
Comment 7 RHEL Program Management 2023-09-18 16:04:10 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8 RHEL Program Management 2023-09-18 16:05:55 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.