FS#48253 - [archiso] archiso broken by latest syslinux-6.03-4 release
Attached to Project:
Arch Linux
Opened by Jeff Hodd (jghodd) - Friday, 19 February 2016, 18:53 GMT
Last edited by Anatol Pomozov (anatolik) - Sunday, 28 February 2016, 17:14 GMT
Opened by Jeff Hodd (jghodd) - Friday, 19 February 2016, 18:53 GMT
Last edited by Anatol Pomozov (anatolik) - Sunday, 28 February 2016, 17:14 GMT
|
Details
Description:
The latest release of syslinux - v6.03-4 - breaks archiso builds, making them unbootable. On boot, the system displays "ISOLINUX 6.03 6.03* EHDD" and hangs. I noticed the breakage a couple of days ago after an archiso build that downloaded the most recent syslinux package version. I had been repeatedly building for the 3 days prior to that without any issues. None of the configuration changed between builds since I'm working on detailing the kde installation. Yesterday, I repackaged syslinux-6.03-3 as syslinux-6.03-5 and loaded it into my own testing repo - the issue went away after an archiso build using the repackaged syslinux-6.03-3. The problem is definitely caused by the '-4' version. Additional info: * package version(s) - archiso-23-1 - syslinux-6.03-4 * config and/or log files etc. Steps to reproduce: Create an arch iso build using archiso and write it to a flash drive - try to boot it up. It errors out with the message "ISOLINUX 6.03 6.03* EHDD" and hangs. |
This task depends upon
Closed by Anatol Pomozov (anatolik)
Sunday, 28 February 2016, 17:14 GMT
Reason for closing: Fixed
Additional comments about closing: 6.04-5
Sunday, 28 February 2016, 17:14 GMT
Reason for closing: Fixed
Additional comments about closing: 6.04-5
Disk /dev/sdd: 58.5 GiB, 62774706176 bytes, 122606848 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x427b7ac4
Device Boot Start End Sectors Size Id Type
/dev/sdd1 * 0 7864319 7864320 3.8G 0 Empty
/dev/sdd2 164 63651 63488 31M ef EFI (FAT-12/16/32)
Otherwise, I don't use a separate /boot partition - /boot is included in the root partition.
I did note that no changes were made to any of the configuration where syslinux is concerned. I use what;s basically provided in the archiso package's 'releng' directory with some archiso config file customisations for my build (kernel params). What has been working for 3 years - and I do rolling releases, so I build out sometimes 5-6 times a month - suddenly stopped working with the arrival of syslinux-6.03-4.
Indeed the syslinux package contains 2 changes in the last release
1) in syslinux-install_update https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/syslinux&id=7bfa5296e2db18f4cddd77dac7c8aa4fa53d200c and as far as I see archiso does not use the script
2) An upstream bugfix for btrfs as a /boot partition http://repo.or.cz/syslinux.git/patch/548386049cd41e887079cdb904d3954365eb28f3?hp=721a0af2f0ba111c31685c5f6c5481eb25346971 (related to the recent format change). It does not sounds like your case neither.
So it sounds weird that it fails. I can't test archiso right now so let's try to check if there are errors in your archiso build log?
Do you try to boot in EFI mode? I wonder if gnu-efi-libs pulled during syslinux build has changed since last syslinux build. To test it could you *build* previous syslinux (6.03-3) and use instead what we have in the repo. Does it still fail?
Could you try to boot in BIOS mode?
Check out this task thread - https://bugs.archlinux.org/task/48247
When I originally created this bug report, I created it as a core:syslinux issue which was found by the Manjaro folks, who also discovered the syslinux bug. They've been able to determine that the issue is the btrfs boot patch. I'm building their version now (no btrfs boot patch + latest git commit) and will also build the current version (6.03-4) without the btrfs boot patch, and will test both during the course of the day. I'll update you once I've tested both versions.
https://bugs.archlinux.org/task/48247 claims that the problem is btrfs patch but I don't understand how it can be. The patch touches only codepath for booting from btrfs /boot partition... Weird. I am going to build syslinux without the btrfs patch and create an archiso image.
I noticed that you closed the other task. Should this one now be considered a syslinux vs an archiso bug?
I'm about to start a new archiso build using the 6.03-4 commit without the btrfs patch. It'll take a while, but I'll keep an eye on new information from you in the meantime.
I see upstream discusses binutils-2.26 issue
http://www.syslinux.org/archives/2016-February/024794.html
https://sourceware.org/bugzilla/show_bug.cgi?id=19538
but we do not have binutils in [stable] yet....
Since syslinux-6.03-4 does not appear to be ready for prime-time, can 6.03-4 be backed out of the core repository and replaced with the older 6.03-3?
Please do test your version of syslinux like you mentioned in #comment144182. It is very important to make sure that the problem is not btrfs patch but the build environment. 2 people have the same result will confirm that the problem is somewhere else.
> can 6.03-4 be backed out of the core repository and replaced with the older 6.03-3?
Assuming that syslinux is broken because of build environment (binutils or gcc) then rebuild 6.03-3 will not help. We need the binaries built with the old environment (exactly like 6.03-3). To go this route I need confirmation from other people that the problem is not because of syslinux changes.
http://www.syslinux.org/archives/2015-September/024317.html
http://www.syslinux.org/archives/2015-September/024318.html
http://www.syslinux.org/archives/2015-September/024319.html
These changes look suspicious. I am going to test them as well.
In fact... our binutils-2.26 package in [testing] has that fix.
Our binutils 2.25.1 pulls additional commits from upstream. I do not know the original commit that introduces the binutils problem but I wonder if it can be in our 2.25.1 already?
I did a 'git log' on the arch 6.04-4 commit and compared it to the the latest from repo.or.cz/syslinux.git - quite a difference. The arch version is missing quite a few updates between Oct. 2014 and Feb. 2016, including a gcc patch. At some point are the two versions going to converge? A 1.5 year difference in the code base is quite a large one.
So followed tarball seems to be fine (6.04-dev): http://repo.or.cz/syslinux.git/snapshot/c1cc1bcef1e23ecb9f650c75f9dafc7e61101218.tar.gz
You either try to find out which extra patches are needed our you use a newer git-snapshot which works.
I'm currently building another ISO image. As soon as I've feedback I'll post it here.