Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
One solution to the problem of firmware (BIOS, etc) updater programs being only available for Windows or DOS is to use memdisk to boot a FreeDOS image containing the updater. Something like:
menuentry "BIOS updater" {
linux16 /memdisk iso
initrd16 /updater.iso
}
This works fine, but if the image is compressed (memdisk supports both zip and gzip), there is a decompression error and the image cannot be booted. This worked correctly in legacy grub.
Version-Release number of selected component (if applicable):
grub2-2.02-0.16.el7
Steps to Reproduce:
1. Try and boot a compressed memdisk image. It will fail if the the image size is not a multiple of 4.
I have worked with the grub2 people, and they acknowledge the bug. A fix was just committed:
commit a8c473288d3f0a5e17a903a5121dea1a695dda3b
Author: Andrei Borzenkov <arvidjaar>
Date: Thu May 7 20:24:24 2015 +0300
loader/linux: do not pad initrd with zeroes at the end
Syslinux memdisk is using initrd image and needs to know uncompressed
size in advance. For gzip uncompressed size is at the end of compressed
stream. Grub padded each input file to 4 bytes at the end, which means
syslinux got wrong size.
Linux initramfs loader apparently does not care about trailing alignment.
So change code to align beginning of each file instead which atomatically
gives us the correct size for single file.
Reported-By: David Shaw <dshaw>
Created attachment 1122174[details]
memdisk-freedos-gz.png
Hello David,
is this the error you're seeing (see attachment)?
I've tried to start freedos floppy disk image without compression (which worked) and with gz compression which failed with attached screenshot.
Thanks
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, 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://rhn.redhat.com/errata/RHBA-2016-2336.html
Description of problem: One solution to the problem of firmware (BIOS, etc) updater programs being only available for Windows or DOS is to use memdisk to boot a FreeDOS image containing the updater. Something like: menuentry "BIOS updater" { linux16 /memdisk iso initrd16 /updater.iso } This works fine, but if the image is compressed (memdisk supports both zip and gzip), there is a decompression error and the image cannot be booted. This worked correctly in legacy grub. Version-Release number of selected component (if applicable): grub2-2.02-0.16.el7 Steps to Reproduce: 1. Try and boot a compressed memdisk image. It will fail if the the image size is not a multiple of 4.