.Driver disk menu fails to display user inputs on the console
When you start RHEL installation using the `inst.dd` option on the Kernel command line with a driver disk, the console fails to display the user input. Consequently, it appears that the application does not respond to the user input and freezes, but displays the output which is confusing for users. However, this behavior does not affect the functionality, and user input gets registered after pressing `Enter`.
As a workaround, to see the expected results, ignore the absence of user inputs in the console and press `Enter` when you finish adding inputs.
Description of problem:
Driver disk menu in RHEL-9.1 doesn't print what the user enters. This can be quite confusing as the user may think that the menu is entirely broken or has frozen (because no user input is echoed back), until enter is pressed:
(Page 1 of 1) Driver disk device selection
/DEVICE TYPE LABEL UUID
1) sr0 iso9660 RHEL-9-1-0-BaseOS-x8 2022-07-17-00-48-01-00
2) sda2 LVM2_mem lx126c-ooBl-cdlP-vrkR-cLOh-im0s-UFE6
3) sda5 LVM2_mem eHHdfq-ncam-4ZlS-gBXg-wMjb-fuBn-ql1f
4) sda3 xfs 9c83e053-1d78-459a-98b0-fce83a2b1de1
5) sda1 xfs 0ab92ae1-d0b0-4934-9e6f-1ffedae4bbeb
6) sr1 iso9660 2022-07-18-03-31-37-00
# to select, 'r'-refresh, or 'c'-continue: Invalid selection '66666'
(Page 1 of 1) Driver disk device selection
/DEVICE TYPE LABEL UUID
1) sr0 iso9660 RHEL-9-1-0-BaseOS-x8 2022-07-17-00-48-01-00
2) sda2 LVM2_mem lx126c-ooBl-cdlP-vrkR-cLOh-im0s-UFE6
3) sda5 LVM2_mem eHHdfq-ncam-4ZlS-gBXg-wMjb-fuBn-ql1f
4) sda3 xfs 9c83e053-1d78-459a-98b0-fce83a2b1de1
5) sda1 xfs 0ab92ae1-d0b0-4934-9e6f-1ffedae4bbeb
6) sr1 iso9660 2022-07-18-03-31-37-00
# to select, 'r'-refresh, or 'c'-continue: DD: Examining /dev/sr1
mount: /media/DD-2: WARNING: source write-protected, mounted read-only.
(Page 1 of 1) Select drivers to install
1) [ ] /media/DD-2/rpms/x86_64/kmod-redhat-e1000e-1.0.1_dup7.4a-1.el9.x86_64.rpm
2) [ ] /media/DD-2/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-2/rpms/x86_64/kmod-redhat-e1000e-1.0.1_dup7.4a-1.el9.x86_64.rpm
2) [ ] /media/DD-2/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
(Page 1 of 1) Driver disk device selection
/DEVICE TYPE LABEL UUID
1) sr0 iso9660 RHEL-9-1-0-BaseOS-x8 2022-07-17-00-48-01-00
2) sda2 LVM2_mem lx126c-ooBl-cdlP-vrkR-cLOh-im0s-UFE6
3) sda5 LVM2_mem eHHdfq-ncam-4ZlS-gBXg-wMjb-fuBn-ql1f
4) sda3 xfs 9c83e053-1d78-459a-98b0-fce83a2b1de1
5) sda1 xfs 0ab92ae1-d0b0-4934-9e6f-1ffedae4bbeb
6) sr1 iso9660 2022-07-18-03-31-37-00
# to select, 'r'-refresh, or 'c'-continue:
Version-Release number of selected component (if applicable):
anaconda-34.25.1.9-1.el9 / RHEL-9.1-20220718.0
How reproducible:
Always.
Steps to Reproduce:
1. Start RHEL-9.1 installation with 'inst.dd' on kernel command line and a driver disk present.
2. When the driver disk menu shows up, try to enter something.
3. Hit enter.
Actual results:
Nothing the user enters shows up on the console. When enter is pressed, the actual input is confirmed (which most likely will result in an error as the user may try to enter the same input several times).
Expected results:
Anything the user enters is printed on the console, so that the interaction between the user and the TUI works with a proper feedback.
Hi Song,
the UI is responsive even though the UX is not good, so the priority is not high. I'm not happy about this state because it's pretty annoying, but this issue has a high probability to be a time sink for debugging to discover the root cause and we don't have time to spare right now.
Description of problem: Driver disk menu in RHEL-9.1 doesn't print what the user enters. This can be quite confusing as the user may think that the menu is entirely broken or has frozen (because no user input is echoed back), until enter is pressed: (Page 1 of 1) Driver disk device selection /DEVICE TYPE LABEL UUID 1) sr0 iso9660 RHEL-9-1-0-BaseOS-x8 2022-07-17-00-48-01-00 2) sda2 LVM2_mem lx126c-ooBl-cdlP-vrkR-cLOh-im0s-UFE6 3) sda5 LVM2_mem eHHdfq-ncam-4ZlS-gBXg-wMjb-fuBn-ql1f 4) sda3 xfs 9c83e053-1d78-459a-98b0-fce83a2b1de1 5) sda1 xfs 0ab92ae1-d0b0-4934-9e6f-1ffedae4bbeb 6) sr1 iso9660 2022-07-18-03-31-37-00 # to select, 'r'-refresh, or 'c'-continue: Invalid selection '66666' (Page 1 of 1) Driver disk device selection /DEVICE TYPE LABEL UUID 1) sr0 iso9660 RHEL-9-1-0-BaseOS-x8 2022-07-17-00-48-01-00 2) sda2 LVM2_mem lx126c-ooBl-cdlP-vrkR-cLOh-im0s-UFE6 3) sda5 LVM2_mem eHHdfq-ncam-4ZlS-gBXg-wMjb-fuBn-ql1f 4) sda3 xfs 9c83e053-1d78-459a-98b0-fce83a2b1de1 5) sda1 xfs 0ab92ae1-d0b0-4934-9e6f-1ffedae4bbeb 6) sr1 iso9660 2022-07-18-03-31-37-00 # to select, 'r'-refresh, or 'c'-continue: DD: Examining /dev/sr1 mount: /media/DD-2: WARNING: source write-protected, mounted read-only. (Page 1 of 1) Select drivers to install 1) [ ] /media/DD-2/rpms/x86_64/kmod-redhat-e1000e-1.0.1_dup7.4a-1.el9.x86_64.rpm 2) [ ] /media/DD-2/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-2/rpms/x86_64/kmod-redhat-e1000e-1.0.1_dup7.4a-1.el9.x86_64.rpm 2) [ ] /media/DD-2/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 (Page 1 of 1) Driver disk device selection /DEVICE TYPE LABEL UUID 1) sr0 iso9660 RHEL-9-1-0-BaseOS-x8 2022-07-17-00-48-01-00 2) sda2 LVM2_mem lx126c-ooBl-cdlP-vrkR-cLOh-im0s-UFE6 3) sda5 LVM2_mem eHHdfq-ncam-4ZlS-gBXg-wMjb-fuBn-ql1f 4) sda3 xfs 9c83e053-1d78-459a-98b0-fce83a2b1de1 5) sda1 xfs 0ab92ae1-d0b0-4934-9e6f-1ffedae4bbeb 6) sr1 iso9660 2022-07-18-03-31-37-00 # to select, 'r'-refresh, or 'c'-continue: Version-Release number of selected component (if applicable): anaconda-34.25.1.9-1.el9 / RHEL-9.1-20220718.0 How reproducible: Always. Steps to Reproduce: 1. Start RHEL-9.1 installation with 'inst.dd' on kernel command line and a driver disk present. 2. When the driver disk menu shows up, try to enter something. 3. Hit enter. Actual results: Nothing the user enters shows up on the console. When enter is pressed, the actual input is confirmed (which most likely will result in an error as the user may try to enter the same input several times). Expected results: Anything the user enters is printed on the console, so that the interaction between the user and the TUI works with a proper feedback.