Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-4762

Can't reload a new driver from driver update disk

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • None
    • rhel-9.2.0
    • anaconda
    • None
    • None
    • rhel-sst-installer
    • ssg_front_door
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Deprecated Functionality
    • Hide
      .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.
      Show
      .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.
    • Done
    • None

      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

      1. 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

      1. 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
      2. 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
      3. 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

      1. 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

      1. 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

      1. 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
      2. 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
      3. 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

      1. 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.

              anaconda-maint-list anaconda-maint-list
              rhn-support-jikortus Jiri Kortus
              anaconda-maint-list anaconda-maint-list
              Release Test Team Release Test Team
              Sagar Dubewar Sagar Dubewar
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: