search for: aslinform

...in the same way. I'll attach a "script" log of the IPMI session. In the tftpd logs I can see it loaded everything up to bootlogo.png. Just like my own build of e466d24. The frustrating thing for me now, is that I still don't know how far into the boot process it got. The 'AslInformation' that keeps reappearing in the stack traces doesn't say me a lot. Is it doing something ACPI related? How come the previous build also crashed in the same way without loading even ldlinux.e64? Could it be a display initialization routine that causes the crashes? -------------- next...

...this is the case then the multi-nic issue is solved; the new code is able to find the NIC that booted syslinux.efi and then uses that NIC to retrieve the rest of files. >>> The frustrating thing for me now, is that I still don't know how far into the boot process it got. The 'AslInformation' that keeps reappearing in the stack traces doesn't say me a lot. Is it doing something ACPI related? How come the previous build also crashed in the same way without loading even ldlinux.e64? Could it be a display initialization routine that causes the crashes? <<< I...

>>> >> OK your HP has 4 NICs >> >> DevicePath(0x0,0x0)/MAC(ECB1D775E524,0x0) >> DevicePath(0x0,0x1)/MAC(ECB1D775E525,0x0)) >> DevicePath(0x0,0x2)/MAC(ECB1D775E526,0x0)) >> DevicePath(0x0,0x3)/MAC(ECB1D775E527,0x0)) According to HP it's actually one nic with four ports. I cannot disable them individually. <<< I see. From an EFI

On Fri, Jul 31, 2015 at 12:37 PM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: >>>> > > 5) upload handles.txt somewhere > > It's waiting at http://okkie.nu/tmp/handles.txt > <<< > > > OK your HP has 4 NICs > > DevicePath(0x0,0x0)/MAC(ECB1D775E524,0x0) > DevicePath(0x0,0x1)/MAC(ECB1D775E525,0x0)) >