Hi I have a computer with BIOS and Linux Arch installed. Starting from a recent syslinux update (6.02->6.03pre9) I am not able to use syslinux anymore. I try to boot my computer and the only thing I see is "EDD Load error - Boot error" message. When I install 6.02 back the system is completely fine. Other people use syslinux 6.03 fine. They use ext4 and I use btrfs as my root partition fs so it might be a problem for syslinux. I would like to debug and see this problem fixed. How to enable more verbose output at boot stage? I would like to get more information about why the EDD error happens. Any other debugging advises?
On 05/19/2014 11:20 AM, Anatol Pomozov wrote:> Hi > > I have a computer with BIOS and Linux Arch installed. > > Starting from a recent syslinux update (6.02->6.03pre9) I am not able > to use syslinux anymore. I try to boot my computer and the only thing > I see is "EDD Load error - Boot error" message. When I install 6.02 > back the system is completely fine. > > Other people use syslinux 6.03 fine. They use ext4 and I use btrfs as > my root partition fs so it might be a problem for syslinux. > > I would like to debug and see this problem fixed. How to enable more > verbose output at boot stage? I would like to get more information > about why the EDD error happens. Any other debugging advises?Size problem again? There are no actual btrfs-related changes in the 6.03 series... Are you using the precompiled binaries or did you build your own? -hpa
Op 2014-05-19 om 11:20 schreef Anatol Pomozov:> Hi > > I have a computer with BIOS and Linux Arch installed. > > Starting from a recent syslinux update (6.02->6.03pre9) I am not able > to use syslinux anymore. I try to boot my computer and the only thing > I see is "EDD Load error - Boot error" message. When I install 6.02 > back the system is completely fine. > > Other people use syslinux 6.03 fine. They use ext4 and I use btrfs as > my root partition fs so it might be a problem for syslinux. > > I would like to debug and see this problem fixed. How to enable more > verbose output at boot stage? I would like to get more information > about why the EDD error happens. Any other debugging advises?Kernel bootparameter 'earlyprintk=....', e.g. earlyprintk=vga Groeten Geert Stappers -- Leven en laten leven
Hi On Mon, May 19, 2014 at 2:03 PM, H. Peter Anvin <hpa at zytor.com> wrote:> On 05/19/2014 11:20 AM, Anatol Pomozov wrote: >> Hi >> >> I have a computer with BIOS and Linux Arch installed. >> >> Starting from a recent syslinux update (6.02->6.03pre9) I am not able >> to use syslinux anymore. I try to boot my computer and the only thing >> I see is "EDD Load error - Boot error" message. When I install 6.02 >> back the system is completely fine. >> >> Other people use syslinux 6.03 fine. They use ext4 and I use btrfs as >> my root partition fs so it might be a problem for syslinux. >> >> I would like to debug and see this problem fixed. How to enable more >> verbose output at boot stage? I would like to get more information >> about why the EDD error happens. Any other debugging advises? > > Size problem again? There are no actual btrfs-related changes in the > 6.03 series... > > Are you using the precompiled binaries or did you build your own?I use binary packages from Linux Arch. Here is one from [stable] repository that works fine for me webpage: https://www.archlinux.org/packages/core/x86_64/syslinux/ binaries: http://mirrors.kernel.org/archlinux/core/os/x86_64/syslinux-6.02-8-x86_64.pkg.tar.xz And this one fails webpage: https://www.archlinux.org/packages/testing/x86_64/syslinux/ binaries: http://mirrors.kernel.org/archlinux/testing/os/x86_64/syslinux-6.03pre11-2-x86_64.pkg.tar.xz The package build script is quite complicated. Here it is https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/syslinux and its history: https://projects.archlinux.org/svntogit/packages.git/log/trunk?h=packages/syslinux My problem appeared as far as I remember during migration from 6.02-8 to 6.03pre9-1 Here is exact package change https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/syslinux&id=0cf9199eb62d8c3af9f4df8c782a482ffd037da9 Besides syslinux itself other things has changed e.g. gcc (but I really hope my problem not because of compiler). Unless there is better way to debug the problem I can start building binaries by myself and bisecting changes. BTW if you see any improvements for the package build instructions we'll be glad to change it.
On 05/19/2014 02:07 PM, Geert Stappers wrote:> Op 2014-05-19 om 11:20 schreef Anatol Pomozov: >> Hi >> >> I have a computer with BIOS and Linux Arch installed. >> >> Starting from a recent syslinux update (6.02->6.03pre9) I am not able >> to use syslinux anymore. I try to boot my computer and the only thing >> I see is "EDD Load error - Boot error" message. When I install 6.02 >> back the system is completely fine. >> >> Other people use syslinux 6.03 fine. They use ext4 and I use btrfs as >> my root partition fs so it might be a problem for syslinux. >> >> I would like to debug and see this problem fixed. How to enable more >> verbose output at boot stage? I would like to get more information >> about why the EDD error happens. Any other debugging advises? > > Kernel bootparameter 'earlyprintk=....', e.g. earlyprintk=vga >He doesn't get far enough for that. -hpa
> Size problem again?This problem is not exactly about the (apparent but not factual) available size to install Syslinux on Btrfs. The bug reports (in bugzilla.syslinux.org, in this Syslinux Mailing List, in bbs.archlinux.org , in bugs.archlinux.org and in other places) are clearly showing different kinds of error messages and different Syslinux versions (including 4.xx). To be clear, the (apparent but not factual) 64KB size issue in Btrfs triggered by Syslinux 6.xx *might* be related to these cases, but the reports include cases where: _ users going back to (or simply trying) Syslinux 4.xx are still seeing the same error. _ users using some Syslinux 6.xx version are booting fine and the error is seen only after some (even minor) update. Since the same error message can be seen under all sorts of Syslinux versions and circumstances other than the 64KB problem (which is not even an issue in Syslinux 4.xx), the conclusion is that only part of the reports and only part of the symptoms might be related to the size limitation; while some reports and some symptoms are not related to the size issue nor to Btrfs. Moreover, similar error messages could be seen in situations where Btrfs is not even used for the Syslinux boot volume, which adds to the confusion about the source of the problem. It should be noted that some users are (at least seemingly) capable of successfully installing Syslinux 6.02 on Btrfs (even with the 64KB problem), whereas some users are failing to install Syslinux 4.xx in a Btrfs volume. Therefore, other than the 64KB issue in Syslinux 6.xx, there is probably something else interfering (in addition to the 64KB issue). Whether this "something else" is related to some Btrfs feature, or to some Btrfs limitation, or to some (Btrfs-tools) package version, or to how exactly the specific version of Syslinux was installed, or to... I (we) don't know (yet). In any case, hopefully Syslinux (in the future) should be capable of overcoming the 64KB issue. ETA: unknown/undefined. Regards, Ady.