search for: core_udp_sento

Displaying 4 results from an estimated 4 matches for "core_udp_sento".

Did you mean: core_udp_sendto
2015 Oct 07
4
UEFI: Failed to load ldlinux.e64/ldlinux.e32
...ese quirks. > > > On Wed, Oct 7, 2015 at 7:58 AM, Ashish, Shivendra > <shivendra.ashish at hpe.com> wrote: >> Still getting error >> >> Disable uderdefault address > > 1) I'm presuming this is actually "disable UseDefaultAddress" > >> Core_udp_sento: udp->configure unsuccessful >> >> This message lopping in console > > Not entirely surprising (for now) though I'd expect more output than > just that and the rest of those messages would likely tell me exactly > what the return codes are. > > More importantly,...
2015 Oct 07
4
UEFI: Failed to load ldlinux.e64/ldlinux.e32
On Wed, Oct 7, 2015 at 2:33 AM, Geert Stappers <stappers at stappers.nl> wrote: > On Tue, Oct 06, 2015 at 10:27:15PM -0400, Gene Cumm via Syslinux wrote: >> > On Fri, Oct 2, 2015 at 4:07 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> >> >> I have a patch that I think may help your situation of syslinux.efi >> >> being unable to load
2015 Oct 07
0
UEFI: Failed to load ldlinux.e64/ldlinux.e32
...ributors don't have machines affected by these quirks. On Wed, Oct 7, 2015 at 7:58 AM, Ashish, Shivendra <shivendra.ashish at hpe.com> wrote: > Still getting error > > Disable uderdefault address 1) I'm presuming this is actually "disable UseDefaultAddress" > Core_udp_sento: udp->configure unsuccessful > > This message lopping in console Not entirely surprising (for now) though I'd expect more output than just that and the rest of those messages would likely tell me exactly what the return codes are. More importantly, you didn't mention what else yo...
2015 Oct 09
0
UEFI: Failed to load ldlinux.e64/ldlinux.e32
Gene wrote: > On Wed, Oct 7, 2015 at 7:58 AM, Ashish, Shivendra <shivendra.ashish at hpe.com> wrote: >> Still getting error >> >> Disable uderdefault address > > 1) I'm presuming this is actually "disable UseDefaultAddress" > >> Core_udp_sento: udp->configure unsuccessful >> >> This message lopping in console > > Not entirely surprising (for now) though I'd expect more output than > just that and the rest of those messages would likely tell me exactly > what the return codes are. > > More importantl...