search for: efi_vesacon_set_mode

...hing, but it could also be the cause of some code overwriting a return address or whatever. > At this point the only choice I see is printing to console messages and > narrow down the problem location. Tough. Right now I found that the *last* message printed before crashing is coming from efi_vesacon_set_mode in efi/vesa.c, which returns successfully. At the moment I'm searching who's calling this function. It looks like efi/main.c triggers something by calling syslinux_register_efi() but something else is the one that executes the firmware->vesa->set_mode(). I'm adding debug state...

On 04-08-15 04:57, Gene Cumm wrote: >> I see. From an EFI point of view you have 4 NICs > I've still seen firmwares that allow me to disable those NIC ports > individually, though it was buried inside another menu. I did find a menu where I could adjust a lot of parameters per port, but I could not find a way to disable individual ports. By the way, I'm booting from the