Displaying 20 results from an estimated 1000 matches similar to: "{syslinux} Hyper-V Gen 2 waiting for ldlinux.e64"
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote:
> James Clement
> > Geert Stappers
> > > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James wrote:
> > > > The screen displays the following:
> > > >
> > > > PXE Network Boot using IPv4
> > > > ....
> > > > Station IP address is 192.168.205.50
2015 Oct 07
3
Hyper-V Gen 2 waiting for ldlinux.e64
> On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux
> wrote:
> > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux
> wrote:
> > > is for BIOS, not for EFI. So that suggestion can be scraped.
> > >
> > > Which makes
> > > * text which is on the screen of the netbooting (virtual) machine
> > >
2015 Oct 09
0
load_env32 WAS: Hyper-V Gen 2 waiting for ldlinux.e64
On Thu, Oct 08, 2015 at 01:24:26AM +0200, Geert Stappers via Syslinux wrote:
> On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote:
>
> > Correct me if I am wrong but if I understand correctly, syslinux.efi is
> > what drives the request for ldlinux.e64. Is there a way we can enable
> > some debug somehow to see why the request for ldlinux.e64 includes
>
2015 Oct 07
0
Hyper-V Gen 2 waiting for ldlinux.e64
>
> > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux
> > wrote:
> > > > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux
> > wrote:
> > > > is for BIOS, not for EFI. So that suggestion can be scraped.
> > > >
> > > > Which makes
> > > > * text which is on the screen of
2015 Oct 12
0
{syslinux} Hyper-V Gen 2 waiting for ldlinux.e64
> On Fri, Oct 09, 2015 at 10:55:11AM -0500, Clements, James wrote:
> > > On Fri, Oct 09, 2015 at 09:45:23AM -0500, Clements, James wrote:
> > > > From: Geert Stappers [mailto:stappers at stappers.nl]
> > > > Sent: 09 October 2015 15:39
> > > > > On Fri, Oct 09, 2015 at 09:14:55AM -0500, Clements, James wrote:
> > > > > > From:
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
> On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux
> wrote:
> > On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux
> wrote:
> > > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote:
> > > > On Wed, Oct 07, 2015 Geert Stappers wrote
> > > > > 13:36:47.974245 IP 192.168.205.50.1939 >
2015 Oct 07
0
Hyper-V Gen 2 waiting for ldlinux.e64
On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James via Syslinux wrote:
> > On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux wrote:
> > is for BIOS, not for EFI. So that suggestion can be scraped.
> >
> > Which makes
> > * text which is on the screen of the netbooting (virtual) machine
> > * when/why was the network capture stopped
2015 Oct 07
0
Hyper-V Gen 2 waiting for ldlinux.e64
On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux wrote:
> On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote:
> > On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux wrote:
> > > Hi,
> > >
> > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a
> > > PXE client (no physical machines
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
> On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux
> wrote:
> > On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote:
> > > On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux wrote:
> > > > Hi,
> > > >
> > > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a
> > > >
2015 Oct 07
0
Hyper-V Gen 2 waiting for ldlinux.e64
On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote:
> On Wed, Oct 07, 2015 Geert Stappers wrote
> > On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux
> > > On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote:
> > > >
> > > > http://www.syslinux.org/archives/2015-October/024375.html
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux wrote:
> On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote:
> > On Wed, Oct 07, 2015 Geert Stappers wrote
> > > 13:36:47.964636 IP 192.168.205.1.47973 > 192.168.205.50.1938: UDP, length 30
> > > 13:36:47.964685 IP 192.168.205.50.1938 > 192.168.205.1.47973: UDP, length 4
> >
2015 Oct 07
0
Hyper-V Gen 2 waiting for ldlinux.e64
On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux wrote:
> On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux wrote:
> > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote:
> > > On Wed, Oct 07, 2015 Geert Stappers wrote
> > > > 13:36:47.974245 IP 192.168.205.50.1939 > 192.168.205.1.tftp: 47 RRQ
2013 May 10
1
[syslinux:firmware] efi: Lookup which file system we were loaded from
On 05/10/2013 06:27 AM, syslinux-bot for Matt Fleming wrote:
>
> diff --git a/efi/main.c b/efi/main.c
> index 31f0bff..27e7f8f 100644
> --- a/efi/main.c
> +++ b/efi/main.c
> @@ -1177,13 +1177,10 @@ static void efi_setcwd(CHAR16 *dp)
>
> EFI_STATUS efi_main(EFI_HANDLE image, EFI_SYSTEM_TABLE *table)
> {
> + EFI_PXE_BASE_CODE *pxe;
> EFI_LOADED_IMAGE *info;
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote:
> On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux
> <syslinux at zytor.com> wrote:
> > Hi,
> >
> > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a
> > PXE client (no physical machines available). This is a UEFI VM, and
> > as per instructions I've read
2015 Jul 13
2
boot... round 2
On 13.07.2015 12:08, Gene Cumm wrote:
> systemd Mailing List <systemd-devel at lists.freedesktop.org> would be
> the wrong address.
>
> On Mon, Jul 13, 2015 at 5:33 AM, poma <pomidorabelisima at gmail.com> wrote:
>> On 03.07.2015 21:35, Gene Cumm wrote:
>>> On Jul 3, 2015 1:34 PM, "poma" <pomidorabelisima at gmail.com> wrote:
>>>
2025 Apr 21
0
[PATCH] Improve EFI console logging
Hello,
While debugging #1103692 on Debian [0], I came across an issue where
error messages generated early in the syslinux boot process through
writestr() didn't end up appearing on-screen. Instead, it appeared
that only the cursor moved.
I discovered that it's because the early code passes a video attribute
of 0 to the efi_write_char() function, which is black-on-black, and
produces
2025 Apr 22
0
[PATCH] Improve EFI console logging
Hi Dave,
You're welcome, glad you find the patches useful :)
Have a nice day,
Marek
On 4/22/25 15:57, Dave Henderson wrote:
> Thanks for your contributions Marek!? I still use this bootloader and
> appreciate all patches that continue to keep it working!
>
>
> Dave
>
>
>
> On 4/21/25 15:45, Marek Benc via Syslinux wrote:
>> Hello,
>>
>> While
2025 Apr 19
0
[PATCH] efi/main.c: include <efisetjmp.h>
On Tue Mar 24 03:57:51 PDT 2020, Thomas Petazzoni wrote:
> Building syslinux against gnu-efi 3.0.10 currently fails with:
>
> syslinux/efi/main.c:33:8: error: unknown type name ?jmp_buf?
>??? 33 | static jmp_buf load_error_buf;
>?????? |??????? ^~~~~~~
> syslinux/efi/main.c: In function ?local_boot?:
> syslinux/efi/main.c:189:5: warning: implicit declaration of
2015 Mar 14
0
[PATCH 0/1] EFI access from Com32 modules
This patch adds to Com32 modules the capabilities of accessing the EFI environment
The idea is simple, the EFI parameters "image" and "table" received by syslinux.efi's
efi_main() are stored in the "firmware" structure, next they are retrieved from the Com32
module which is linked against the gnu-efi static library. The Com32 module can use the EFI
2015 Jul 08
0
EFI: PXE: "My IP is 0.0.0.0"
On Mon, Jul 6, 2015 at 6:04 AM, Patrick Masotta <masottaus at yahoo.com> wrote:
>
> What I've found:
> (from older to newer hardware)
>
> 1) There's not "any" SB protocol present (Elitebook 8460p/2560p)
The only solution for these is to use our own stack (likely full
TCP/IP like lwIP) and connect to the Net GUID
(EFI_SIMPLE_NETWORK_PROTOCOL). Does the