Displaying 20 results from an estimated 1000 matches similar to: "uEFI support for PXELinux 6.0 alpha?"
2014 Mar 27
1
Any hints about compiling syslinux 6.03-pre9 on AMD64?
Dear all,
I packaged syslinux 6.03-pre9 on AMD64 Debian Sid, however, the problem
is, I have problem to use it for PXE booting (BIOS mode).
It always gives me "Failed to load COM32 file vesamenu.c32".
I am sure all the settings are correct because if I switch to the
prebuilt syslinux downloaded from
2013 May 07
1
Syslinux 5.01 fails to boot iPXE
I have an issue to boot iPXE with Syslinux 5.01. However, the same
method works for Syslinux 4.06.
The error messages I got is (see attached png file):
===================================
iPXE 1.0.0+git-20120202.f8840ba-3 -- Open Source Network Boot Firmware
-- http://ipxe.org
Features: VLAN HTTP iSCSI DNS TFTP AoE SRP BzImage COMBOOT ELF MBOOT PXE
PXEXT
/syslinux/ipxe.lkn: command not found
2013 Sep 26
3
One DHCP/PXE config for BIOS, EFI32, and EFI64 clients?
On 09/26/2013 01:44 AM, Jeffrey Hutzelman wrote:
> Yes; you can configure your DHCP server to hand out different values for
> the pxelinux.configfile option to specific clients, matching on MAC
> address or a variety of other conditions. Of course, this means that
> the config file for that machine will need to know what firmware to
> expect and thus what path to set.
Hi Jeffrey,
2013 Sep 12
2
Problem with pxelinux 5.10 and memtest86+ 4.20
Deal developers,
I'd like to follow the thread
http://www.zytor.com/pipermail/syslinux/2013-April/019761.html
but change the subject to 'pxelinux 5.10 and memtest86+ 4.20' and
provide more test cases.
The pxelinux before version 5, e.g. version 4.06, worked very well with
memtest86+ 4.20, all my PXE client machines, including VMWare
workstation 9, VirtualBox 4.2, and all the real
2014 Mar 08
2
Syslinux EFI + TFTPBOOT Support
On 2014?03?08? 20:57, Gene Cumm wrote:
> Please try 6.03-pre6. I see a regression on 6.03-pre7 with EFI64 netboot
>
>> > Another thing you I'd like to mentioned is, after bootx64.efi was
>> > downloaded, the next download for ldlinux.e64 was about 15 secs later.
>> > Is that normal?
> When it's successful for me, it takes 0.2s from the beginning of
>
2013 Oct 29
2
syslinux/isolinux 6.2 "Error: Couldn't read the first disk sector"
After switching to version 6.2, I am having a problem to use chain.c32
to boot a local disk.
My settings:
======================
label local
MENU LABEL Local operating system in hard drive
kernel chain.c32
append hd0
======================
It gave me "Error: Couldn't read the first disk sector"
If I change the settings as
======================
label local
MENU LABEL
2014 Apr 23
1
*.c32 for efi64 and efi32?
/sudo/pseudo code/
On Wednesday, April 23, 2014 9:32 AM, Don Cupp <doncuppjr at yahoo.com> wrote:
I actually propose another strategy that may kills many birds with one stone. I think it should be able to be handled internally. Right now, we take a kernel argument as a literal file name hdt.c32 really mean load file hdt.c32. That great, it works, that is how most config files are written.
2014 Apr 23
2
*.c32 for efi64 and efi32?
On 04/23/2014 09:06 PM, Ady wrote:
> Suggestions and patches are surely welcome.
Ady,
Mine is only suggestion, and for sure I will just follow what Syslinux
developers decide.
Thanks.
Steven.
--
Steven Shiau <steven _at_ stevenshiau org>
Public Key Server PGP Key ID: 4096R/47CF935C
Fingerprint: 0240 1FEB 695D 7112 62F0 8796 11C1 12DA 47CF 935C
2014 Mar 08
2
Syslinux EFI + TFTPBOOT Support
On 03/08/2014 10:06 PM, Gene Cumm wrote:
>> Hi Gene,
>> > Thanks. As you suggested, I did a test about 6.03-pre6, and I still got
>> > the same issue. My client machine
>> > still only shows:
>> > ====================
>> > Getting cached packets
>> > My IP is 192.168.120.1
>> > ====================
>> > The syslog log
2013 Sep 13
0
Problem with pxelinux 5.10 and memtest86+ 4.20
On 09/13/2013 06:36 AM, Gene Cumm wrote:
> On Thu, Sep 12, 2013 at 12:24 AM, Steven Shiau <steven at nchc.org.tw> wrote:
>> On 2013/9/12 11:55, Steven Shiau wrote:
>>>
>>> Deal developers,
>>> I'd like to follow the thread
>>> http://www.zytor.com/pipermail/syslinux/2013-April/019761.html
>>> but change the subject to 'pxelinux
2013 Sep 12
0
Problem with pxelinux 5.10 and memtest86+ 4.20
On 2013/9/12 ?? 11:55, Steven Shiau wrote:
> Deal developers,
> I'd like to follow the thread
> http://www.zytor.com/pipermail/syslinux/2013-April/019761.html
> but change the subject to 'pxelinux 5.10 and memtest86+ 4.20' and
> provide more test cases.
>
> The pxelinux before version 5, e.g. version 4.06, worked very well with
> memtest86+ 4.20, all my PXE
2013 Oct 29
0
syslinux/isolinux 6.2 "Error: Couldn't read the first disk sector"
My bad, I meant version 6.02, not 6.2
Steven.
On 10/29/2013 11:28 AM, Steven Shiau wrote:
> After switching to version 6.2, I am having a problem to use chain.c32
> to boot a local disk.
> My settings:
> ======================
> label local
> MENU LABEL Local operating system in hard drive
> kernel chain.c32
> append hd0
> ======================
> It gave me
2013 Sep 20
0
One DHCP/PXE config for BIOS, EFI32, and EFI64 clients?
On 09/20/2013 02:34 AM, Ady wrote:
>> There might be an alternative (and possibly others too): let the user
>> select the appropriate firmware from within pxelinux.cfg/default.
>>
>> So, keep using the same method you used in previous versions, instead
>> of selecting the Syslinux cfg / firmware from the DHCP snippet that
>> Daniel posted.
>>
>>
2013 Sep 20
0
Problem with pxelinux 5.10 and memtest86+ 4.20
On 09/13/2013 06:36 AM, Gene Cumm wrote:
> I believe this is a result of how/where memtest wants to be loaded. I
> can confirm it's present in 5.11-pre9 but appears resolved for me in
> 6.02-pre16. I should be able to test in Workstation-9.0.2 tomorrow.
Hi Gene,
Were you able to reproduce the issue on VMWare WS 9?
If so, when we will expect the fixed version (5.x) to be released?
2013 Sep 26
0
Problem with pxelinux 5.10 and memtest86+ 4.20
On 09/24/2013 04:58 AM, Gene Cumm wrote:
> I'm not sure if there will be another 5.xx release or pre-release,
> except possibly more testing with some changes I've made recently for
> lwIP-enabled PXELINUX (lpxelinux.0)
Gene,
Got it. If possible, please have another 5.xx release since 6.x is a big
jump from 5.x.
Thank you very much.
Steven.
--
Steven Shiau <steven _at_ nchc
2013 Sep 26
0
Problem with pxelinux 5.10 and memtest86+ 4.20
On 09/27/2013 02:37 AM, H. Peter Anvin wrote:
> "Big jump" in what way?
Oh, I should not use that strong words... Actually what I meant is the
implementation of EFI support so the file directories in the release
tarball are different.
Steven.
--
Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org>
National Center for High-performance Computing, Taiwan.
2013 Oct 17
0
One DHCP/PXE config for BIOS, EFI32, and EFI64 clients?
On 2013/9/27 ?? 07:28, H. Peter Anvin wrote:
> It wouldn't be too hard to implement, just a matter of someone finding
> the time.
>
> -hpa
Great! I believe this feature is very useful for a PXE server.
Since syslinux 6.02 is released, may we expect this feature to be added
in 6.03? Am I too greedy? :)
Thanks for all the great job about syslinux. Appreciate.
Steven.
--
Steven
2013 Sep 16
4
One DHCP/PXE config for BIOS, EFI32, and EFI64 clients?
Dear all,
I'd like to have a DHCP/PXE server for different arch of clients, i.e.
BIOS, EFI32, and EFI64 clients.
As described here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589
What Daniel has proposed
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589#10) should
work, i.e. Using a file called pxelinux.cfg/bios containing the
following 2 lines:
2014 Apr 23
0
*.c32 for efi64 and efi32?
I actually propose another strategy that may kills many birds with one stone. I think it should be able to be handled internally. Right now, we take a kernel argument as a literal file name hdt.c32 really mean load file hdt.c32. That great, it works, that is how most config files are written. All we need to do is change the expectation a little from a literal to a directive with a literal
2014 Mar 07
2
Syslinux EFI + TFTPBOOT Support
On 2014?03?07? 23:05, Ady wrote:
> I understand that these remarks might seem not the main issue, but I
> tend to think that once you are successful while using only "default"
>
> values and in a minimalistic case, you could add complexity
> (different paths, multiple firmwares, additional kernels, multiple
> cfg files...).
Ady,
Thanks. I will follow your advice to