search for: efi_not_ready

...no keyboard is present on a machine (or when UEFI has chosen to not init USB due to fast boot). Reproducible at least with "EFI v2.31 by American Megatrends" on an Asrock H81M-ITX board. Reason is the input draining loop near the end in efi/main.c; it calls ReadKeyStroke() as long as EFI_NOT_READY is not returned. On machines without keyboard, EFI_DEVICE_ERROR may be returned instead, causing infinite looping. Positively checking for EFI_SUCCESS keeps the intent while avoiding this behavior. Patch is against 6.03; the issue is still present in 6.04 as per e466d2498604c8eea055a8e98284d65...

...point out there the code is freezing at in main.c. > >> > It's > >> > right at load_env32(NULL); at that point status has a numerical value of > >> > 6. > >> > >> That's excellent to know. Thanks. > > And numerical value of 6 is EFI_NOT_READY, indicating the keyboard > buffer is empty, as expected. > Gene, Yeah I guess that could be good or bad news. Also I have determined where it is getting hung at -- core/elflink/load_env32.c in start_ldlinux at rv = spawn_load(LDLINUX, argc, argv); Do you have any other ideas for troublesh...

...rt but I've more typically seen newer lines below the old lines and as a part of the same comment. > @@ -348,7 +352,11 @@ char efi_getchar(char *hi) > > do { > status = uefi_call_wrapper(in->ReadKeyStroke, 2, in, &key); > - } while (status == EFI_NOT_READY); > + } while (status != EFI_NOT_READY); > + > + status = WaitForSingleEvent(in->WaitForKey, 0); > + status = uefi_call_wrapper(in->ReadKeyStroke, 2, in, &key); > + > > if (!key.ScanCode) > return (char)key.UnicodeChar; &...

...gt; machine (or when UEFI has chosen to not init USB due to fast boot). > Reproducible at least with "EFI v2.31 by American Megatrends" on an > Asrock H81M-ITX board. > > Reason is the input draining loop near the end in efi/main.c; it calls > ReadKeyStroke() as long as EFI_NOT_READY is not returned. On machines > without keyboard, EFI_DEVICE_ERROR may be returned instead, causing > infinite looping. Positively checking for EFI_SUCCESS keeps the intent > while avoiding this behavior. > > Patch is against 6.03; the issue is still present in 6.04 as per > e...

On Mon, Aug 31, 2015 at 06:08:19AM -0400, Gene Cumm via Syslinux wrote: > On Aug 30, 2015 8:42 PM, "Derrick" <derrick22 at gmail.com> wrote: > > > > Gene thanks, here is the output > > > > My IP is 10.2.49.10 > > Img @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 =

.../* + * EFI image boot capabilities by Patrick Masotta (Serva) (c)2015 + */ + +/* * Copyright 2011-2014 Intel Corporation - All Rights Reserved */ @@ -348,7 +352,11 @@ char efi_getchar(char *hi) do { status = uefi_call_wrapper(in->ReadKeyStroke, 2, in, &key); - } while (status == EFI_NOT_READY); + } while (status != EFI_NOT_READY); + + status = WaitForSingleEvent(in->WaitForKey, 0); + status = uefi_call_wrapper(in->ReadKeyStroke, 2, in, &key); + if (!key.ScanCode) return (char)key.UnicodeChar; @@ -356,10 +364,21 @@ char efi_getchar(char *hi) /* * We cu...

...gt; >> > Also, I wanted to point out there the code is freezing at in main.c. >> > It's >> > right at load_env32(NULL); at that point status has a numerical value of >> > 6. >> >> That's excellent to know. Thanks. And numerical value of 6 is EFI_NOT_READY, indicating the keyboard buffer is empty, as expected. -- -Gene >> > On Mon, Aug 31, 2015 at 3:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> >> >> On Aug 30, 2015 8:42 PM, "Derrick" <derrick22 at gmail.com> wrote: >> >>...

...that point status has a numerical >> >> >> > value >> >> >> > of >> >> >> > 6. >> >> >> >> >> >> That's excellent to know. Thanks. >> >> >> >> And numerical value of 6 is EFI_NOT_READY, indicating the keyboard >> >> buffer is empty, as expected. >> >> >> >> -- >> >> -Gene >> >> >> >> >> > On Mon, Aug 31, 2015 at 3:08 AM, Gene Cumm <gene.cumm at gmail.com> >> >> >> > wrote:...