search for: _firmware_

...options for specific needs. ENDTEXT KERNEL /boot/vmlinuz64 INITRD /boot/corepure64.gz APPEND loglevel=3 cde vga=788 multivt <><><> Are there any obvious errors there? Where is the proper formal syntax listed? A previous mail sounds interesting/applicable: >..... > If the _firmware_ is UEFI x64, then use the adequate syslinux.efi file, > plus ldlinux.e64. With that bootloader, you should be able to load a > (CONFIG_EFI_MIXED-enabled) Linux kernel for x86 (IA32) or for x86_64 > (X64). > If the _firmware_ is UEFI x64, then the syslinux.efi file for x86 > (IA32) w...

...ble to find 'syslx64.cfg'. > - i looked for available information - what did i miss? There is something that many users seem to confuse: it is not the architecture of the microprocessor (x32 or x64) that defines which syslinux.efi is to be used, but rather the firmware. If the _firmware_ is UEFI x64, then use the adequate syslinux.efi file, plus ldlinux.e64. With that bootloader, you should be able to load a (CONFIG_EFI_MIXED-enabled) Linux kernel for x86 (IA32) or for x86_64 (X64). If the _firmware_ is UEFI x64, then the syslinux.efi file for x86 (IA32) won't boot in such...

hi i was creating a boot stick for BIOS years ago, which still is working - of course. need just update kernels. i now need to set up new linux laptops. as i do not want to run into troubles i do intend to create a new stick for UEFI. do not mix BIOS/UEFI on one device. once again nothing fancy. prompt and say will do. was reading all available text about best solution. i so prepared a