search for: efistub

> > efistub.jpg: > > >>Start PXE over IPv4. > Station IP address is 192.168.201.185 > > Server IP address is 10.210.32.100 > NBP filename is pxelinux.0 > NBP filesize is 6644000 Bytes > Downloading NBP file... > > Succeed to download NBP file. > > Downl...

...from that commit. > > -- > -Gene While we wait for a reply from Andrey... According to the report, syslinux.efi X64 is successfully booting the 32-bit kernel. In theory, this should / would mean that the kernel was built with CONFIG_EFI_MIXED, among others. As far as I know, the EFISTUB code doesn't know how to boot a kernel with a different architecture / bitness than the firmware. If this is (still) correct, then syslinux.efi X64 should be using the (latest) EFI handover protocol to be able to boot this 32-bit kernel (not the EFISTUB code). According to the report, both...

On 11/6/14, Ady <ady-sf at hotmail.com> wrote: > >> I have done another install to the usb stick. >> >> # syslinux --directory EFI/BOOT --install /dev/sdc1 >> >> ...this creates files ldlinux.c32 and ldlinux.sys in /EFI/BOOT >> >> I then mounted the 1st partition of the usb stick and copied >> syslinux.efi and ldlinux.e64 from

> I have done another install to the usb stick. > > # syslinux --directory EFI/BOOT --install /dev/sdc1 > > ...this creates files ldlinux.c32 and ldlinux.sys in /EFI/BOOT > > I then mounted the 1st partition of the usb stick and copied > syslinux.efi and ldlinux.e64 from /usr/share/syslinux/efi64 to > /EFI/BOOT in the usb stick. > > I renamed syslinux.efi to

...; > Sounds like you got the attachment intact. > > > Hi again > > > > We got a new server so figured we should try UEFI PXE on that so used your latest debug > > build and got similar results(efi.jpg). Using a EFI linux kernel directly does not > > work either(efistub.jpg) > > > > Jocke > > Your previous message was held due to a attachment limit on the list. > These were a lot smaller. > > efi.jpg: > > imd-Finding path; to str; > imd at Acpi(PNP0A03,0)/Pci(1C|0)/Pci(0|0)/Mac(40F2E92FCA02)/IPv4(not-done) > Getting c...

On Wed, Nov 29, 2017 at 6:30 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Nov 28, 2017 at 2:38 PM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: >> On Mon, 2017-11-27 at 18:18 -0500, Gene Cumm wrote: > >>> On Mon, Nov 27, 2017 at 6:07 PM, Joakim Tjernlund >>> <Joakim.Tjernlund at infinera.com> wrote: >>> > On

On Wed, 2017-12-13 at 17:15 +0000, Ady Ady via Syslinux wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > > > > efistub.jpg: > > > > > > Start PXE over IPv4. > > > > Station IP address is 192.168.201.185 > > > > Server IP address is 10.210.32.100 > > NBP filename is pxelinux.0 > > NBP filesize is 6644000 Bytes > > Downloading NBP file... > &g...

Hello, now that 5.00pre is out, is there any timeline or rough estimate when stable EFI support can be expected? I'm one of the authors of a live CD project which we'd really like to make usable on Macs which only have EFI support (without BootCamp). Most other EFI-capable machines I've seen so far also have a BIOS emulation, but I expect things to change with upcoming Windows 8

...environment (nasm, gnu-efi, gcc, binutils, mtools...)? No chance that someone could suggest that updating the gnu-efi submodule _might_ _perhaps_ affect the result? I cannot believe that there is not even one developer that could think (and post here) about the potential idea that some code in EFISTUB (or whatever is related to EFI in the Linux kernel) needs to be also incorporated in Syslinux. Really? There is not one person that could think that some development in the EFISTUB code (or similar) during the last year-and-a-half / two years might need to be ported to the Syslinux code too?...

...ne > > > While we wait for a reply from Andrey... > > > According to the report, syslinux.efi X64 is successfully booting the > 32-bit kernel. In theory, this should / would mean that the kernel was > built with CONFIG_EFI_MIXED, among others. > > As far as I know, the EFISTUB code doesn't know how to boot a kernel > with a different architecture / bitness than the firmware. If this is > (still) correct, then syslinux.efi X64 should be using the (latest) EFI > handover protocol to be able to boot this 32-bit kernel (not the > EFISTUB code). In case of mi...

Hello, I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. After boot linux sees only 2.5G of RAM while system has 32G installed. If I boot the same kernel with GRUB64 efi instead of syslinux then amount of RAM available to linux is 32G. Is this a bug or I'm missing something? syslinux.cfg: label live-686-pae menu label Linux (686-pae) menu

...re testers... > _ gPXE/iPXE... > _ Older kernels and/or kernels for older machines (e.g. PuppyLinux and > family and derivatives; I could mention several others) > _ Non-relocatable and relocatable kernels > _ Linux kernels prior to version 3.3 and/or with similar "older > (EFISTUB) standards", "supposedly" bootable in BIOS and/or (U)EFI > systems at the time (e.g. Slackware 14.0 / 14.1, Debian 7 Wheezy, RHEL > 6.x / 7 ) > _ BIOS and/or (U)EFI systems > > As a remainder and FWIW, from prior discussions (2014Q4) we have: > http://www.syslinu...

...x.e64 in the tar file and it printed: Sounds like you got the attachment intact. > Hi again > > We got a new server so figured we should try UEFI PXE on that so used your latest debug > build and got similar results(efi.jpg). Using a EFI linux kernel directly does not > work either(efistub.jpg) > > Jocke Your previous message was held due to a attachment limit on the list. These were a lot smaller. efi.jpg: imd-Finding path; to str; imd at Acpi(PNP0A03,0)/Pci(1C|0)/Pci(0|0)/Mac(40F2E92FCA02)/IPv4(not-done) Getting cached packet My IP is 192.168.201.185 netmask 255.255....

...natives), DBAN, several hardware testers... _ gPXE/iPXE... _ Older kernels and/or kernels for older machines (e.g. PuppyLinux and family and derivatives; I could mention several others) _ Non-relocatable and relocatable kernels _ Linux kernels prior to version 3.3 and/or with similar "older (EFISTUB) standards", "supposedly" bootable in BIOS and/or (U)EFI systems at the time (e.g. Slackware 14.0 / 14.1, Debian 7 Wheezy, RHEL 6.x / 7 ) _ BIOS and/or (U)EFI systems As a remainder and FWIW, from prior discussions (2014Q4) we have: http://www.syslinux.org/wiki/index.php/Common_Pr...

...ail.com> >Subject: Re: [syslinux] syslinux 6.03 does not boot some kernels > >On Fri, Dec 5, 2014 at 9:51 AM, Ady <ady-sf at hotmail.com> wrote: >> >> It sounds as if syslinux.efi 6.03 is only capable of booting a Linux >> kernel 3.3+ with an adequate config with EFISTUB. Considering that some >> relevant changes were introduced to the Linux kernel in its 3.3 branch, >> are these reported behaviors mean that prior kernels (such as the >> current stable Debian Wheezy with kernel 3.2) are not bootable in UEFI >> mode by Syslinux 6.03? >>...

...he binaries already included in the official upstream archives version 6.03, "as-is". Testing with public popular kernels that are known to work (so to compare the behavior) might be useful too, but I don't know of any particular kernels to suggest for such tests. I know that for EFISTUB, the kernel config should include: CONFIG_RELOCATABLE=y CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_FB_EFI=y CONFIG_FRAMEBUFFER_CONSOLE=y For UEFI ia32 firmware, it should be possible (in theory, and if I understand correctly) to use 32 bit Syslinux to load a 64 bit kernel, as long as the latter has...

...bian Wheezy stable kernel 3.2 is being reported as not bootable with Syslinux 6.03, but successfully bootable with Syslinux 6.01. IMHO, this should be considered a Syslinux regression. It sounds as if syslinux.efi 6.03 is only capable of booting a Linux kernel 3.3+ with an adequate config with EFISTUB. Considering that some relevant changes were introduced to the Linux kernel in its 3.3 branch, are these reported behaviors mean that prior kernels (such as the current stable Debian Wheezy with kernel 3.2) are not bootable in UEFI mode by Syslinux 6.03? Is Syslinux adding more conditions than...

On Mon, Nov 23, 2015 at 3:06 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > It saddens (me) > C'mon; really? As you asked. -- -Gene

On Sat, 7 Feb 2015, Ady via Syslinux wrote: > Thank you for this meaningful report. Ideally, I would suggest > performing a similar test (at least with the same kernel built with all > the above "config_*=y" settings) with official pre-built Syslinux > versions 4.07 and 3.86 (remembering that all Syslinux-related files, > including c32 modules, if being used, shall

Am 02.12.2014 schrieb Ady: > ( ... ) > > Since we are in the Syslinux Mailing List, please let me rephrase the > most relevant part of this case: syslinux.efi 6.03 is incapable of > booting some kernel, whereas syslinux.efi 6.01 can successfully boot it > under the same conditions. > I can now confirm that this can be replicated on hardware, a ThinkCentre M93 will reboot