similar to: syslinux starting a efi application

Displaying 20 results from an estimated 700 matches similar to: "syslinux starting a efi application"

2015 Sep 15
2
[OT] linux on a PPC (mac mini)
Am 15.09.2015 um 17:12 schrieb Keith Keller <kkeller at wombat.san-francisco.ca.us>: > On 2015-09-15, wwp <subscript at free.fr> wrote: >> >> Searching the web, I see very few possibilities to install a recent (I >> need gnome2) GNU/Linux distro on such hardware. I gave Linux MintPPC 11 >> (http://www.mintppc.org/content/list-macs) a try, but the netinstall
2015 Sep 15
1
[OT] linux on a PPC (mac mini)
Am 15.09.2015 um 19:09 schrieb Keith Keller <kkeller at wombat.san-francisco.ca.us>: > On 2015-09-15, Leon Fauster <leonfauster at googlemail.com> wrote: >>> On 2015-09-15, wwp <subscript at free.fr> wrote: >> >> this also helps to boot >> >> http://www.rodsbooks.com/refind/ > > rEFInd will work on EFI-based Macs, but not on old PPC
2014 Jan 15
1
extlinux device trouble
On Wed, Jan 15, 2014 at 3:26 AM, Johann Obermayr <johann.obermayr at sigmatek.at> wrote: > Am 15.01.2014 04:57, schrieb Gene Cumm: > >> On Tue, Jan 14, 2014 at 10:50 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> >>> On Tue, Jan 14, 2014 at 9:28 AM, Johann Obermayr >>> <johann.obermayr at sigmatek.at> wrote: >>>>
2015 Apr 06
1
Is efiboot.img required?
Hi, > 6. Renamed back /EFI/boot/bootx64.efi to /EFI/boot/syslinux.efi, just > to be sure. The "Default fallback loader on 32 MiB device" entry has > changed to "Syslinux on 32 MiB device". How the hell does it know that it is "Syslinux" ? The same file content does not cause that name if it is presented under the default name. Does EFI just guess
2014 Jan 15
3
extlinux device trouble
On Tue, Jan 14, 2014 at 10:50 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Jan 14, 2014 at 9:28 AM, Johann Obermayr > <johann.obermayr at sigmatek.at> wrote: >> Hello, >> >> i'm using version 4.07. >> On my computer extlinux does not work. >> after debugging, i found the trouble. >> >> in the function parse_mountinfo there
2014 Jan 14
2
extlinux device trouble
Hello, i'm using version 4.07. On my computer extlinux does not work. after debugging, i found the trouble. in the function parse_mountinfo there was using a function get_string. in the function get_string there was a line (42) } else if (ch == '\\') { but in my mountinfo list, there was \ , but not with octal digit. so the function get_string will fail. here are some information
2014 Nov 19
2
pxelinux 6.03 in UEFI qemu/tianocore/ovmf: does not work
Hello. I played with UEFI PXE booting the other day, and as usual, used qemu/kvm virtual machine for initial testing/debugging, because it is way easier and faster for this task than using a real hardware. However, it looks like either qemu or {pxe,sys}linux 6.03 is buggy, -- the two does not play well together. When booting, the system successfully loads syslinux.efi, at least the tftp server
2020 Aug 02
4
8.2.2004 Quick recovery and fix for unbootable machines
This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that is, the one from the latest installation media. I am running on an x86_64 architecture (see uname -i). Please use the correct shim file for your architecture
2015 Jun 26
2
/boot on a separate partition?
On Fri, Jun 26, 2015 at 9:58 AM, Jonathan Billings <billings at negate.org> wrote: > On Thu, Jun 25, 2015 at 01:27:47PM -0600, Chris Murphy wrote: >> It's bad design. First, it's a nested mount: file system A on /, and >> file system B on /boot, and file system C on /boot/efi. Therefore the >> mount process must make sure they're mounted in that order, or
2023 Mar 20
2
Is chain loading EFI apps not supported?
On 20 Mar 2023 at 0:00, marteg via Syslinux wrote: > > Greetings! > > If I understand everything correctly, the last release of syslinux > supports UEFI, but it can't load another EFI application in this mode, so > practically only linux kernel can be bootloaded. Unfortunately, I have a > need to dualboot windows and linux with UEFI, and this holds me back from >
2009 Nov 24
13
[Bug 25258] New: [9400M] KMS and X do not use monitor's native resolution
http://bugs.freedesktop.org/show_bug.cgi?id=25258 Summary: [9400M] KMS and X do not use monitor's native resolution Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at
2020 Aug 02
1
Fwd: 8.2.2004 Quick recovery and fix for unbootable machines with rescue disk
Hello all-- These instructions are somewhat OK but my messed up box is the only one I've got basically to help with this problem. Where can we find "correction" instructions using a "rescue" CD or flash drive? I understand RedHat provided detailed instructions to supported customers. Thanks. _______________________ Sent from MzK's phone. ---------- Forwarded message
2023 Mar 19
1
Is chain loading EFI apps not supported?
Greetings! If I understand everything correctly, the last release of syslinux supports UEFI, but it can't load another EFI application in this mode, so practically only linux kernel can be bootloaded. Unfortunately, I have a need to dualboot windows and linux with UEFI, and this holds me back from using this amazing piece of software. Have there since been any progress regarding this
2018 Nov 20
7
kernel 3.10.0-957.el7.x86_64 + EFI on Dell server - problem
hi guys I've one box where I just yesterday upgraded Centos. I wonder if that kernel upgrade process might somewhat troublesome. After that upgrade UEFI boot fails with: Failed to set MokListRT: Invalid Parameter Something has gone seriously wrong: import_mok_state() failed : Invalid Parameter Has anybody seen that? And maybe know to fix it? many thanks, L.
2009 Oct 30
28
[Bug 24820] New: [nv15] Vertical screen corruption in X when KMS is enabled
http://bugs.freedesktop.org/show_bug.cgi?id=24820 Summary: [nv15] Vertical screen corruption in X when KMS is enabled Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:
2012 Feb 07
4
[Bug 45746] New: ION (NVAC) does not work with latest git kernel module
https://bugs.freedesktop.org/show_bug.cgi?id=45746 Bug #: 45746 Summary: ION (NVAC) does not work with latest git kernel module Classification: Unclassified Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau
2010 Feb 15
10
[Bug 26577] New: [regression] Black screen with X on NV11 and NV31
http://bugs.freedesktop.org/show_bug.cgi?id=26577 Summary: [regression] Black screen with X on NV11 and NV31 Product: xorg Version: git Platform: All OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2015 Apr 06
1
Is efiboot.img required?
> The most annoying thing (to me) is that it doesn't boot at all on > Legacy OS mode (MBR), while it should... :-/ No, it shouldn't. If you are initially booting in (U)EFI mode (into rEFInd, or some EFI shell or any other EFI boot loader or EFI boot manager), then generally speaking you are expected to boot in EFI mode. But some (U)EFI firmware _might_ be able to
2004 Apr 06
1
Your mail to feedback@suse.de
------------------------------------------------------------------------- (deutsche Version unten) Dear SuSE Linux User, thank you for your message regarding "Unknown Exception (feedback@suse.de)". Please note that the email address you sent your message to (feedback@suse.de) is no longer in use. Of course you still can send us your ideas, comments and bug reports related to our
2019 Jan 18
1
stuck in pxe loop from uefi + tianocore/ovmf
Hello all, hope all is well Was wondering if I'm doing something wrong/missing something. I have pxe+tftp+uefi working between 2 vms. However after the build is done and I reboot, I still come up to pxe b/c tianocore always starts, from what I've seen, with trying PXE first. Great for initial builds :) but I would like to it stop after. In the xml I am pointing to the disk to boot first.