Grub 2.12 problem with vmnext3 network card and PXE

Some of our vSphere VMs are using vmnext3 networc cards. Grub2.12 is downloaded via TFTP onto the VMs. An embedded grub.cfg downloads a grub.cfg placed on a TFTP server. However since Grub 2.12 this doesn't work anymore. When executing the embeeded cfg the cursor stalls for a couple of seconds

[bug #65250] GRUB unable to PXE boot

URL: <https://savannah.gnu.org/bugs/?65250> Summary: GRUB unable to PXE boot Group: GNU GRUB Submitter: century6 Submitted: Sun 04 Feb 2024 07:01:23 AM UTC Category: Network Severity:

[bug #63245] PXE boot with GRUB 2.06 sometimes fail on generation 11 Intel NUCs

Follow-up Comment #2, bug #63245 (project grub): I came up with a pretty efficeient method to reproduce this issue. I edit the grub.cfg so it only contatins this lines: set timeout="0" menuentry "Reboot" { reboot } This will of course just reboot as soon as the grub.cfg is

[bug #63245] PXE boot with GRUB 2.06 sometimes fail on generation 11 Intel NUCs

Follow-up Comment #1, bug #63245 (project grub): Link to video showing behaviour after failure: https://1drv.ms/v/s!AggiUAzQLDWUooY9XvGgiR0vsa8n-w?e=AT7SNt One idea Intel had was to try to PXE boot with a USB dongle, I bought one that was able to PXE boot on DELL but did not show up as an boot

[bug #63245] PXE boot with GRUB 2.06 sometimes fail on generation 11 Intel NUCs

URL: <https://savannah.gnu.org/bugs/?63245> Summary: PXE boot with GRUB 2.06 sometimes fail on generation 11 Intel NUCs Project: GNU GRUB Submitter: jerrymattias Submitted: Thu 20 Oct 2022 06:30:08 AM UTC Ca

[bug #62072] If a multicast RA message is received during UEFI PXE boot, grub2 program will crash

Follow-up Comment #1, bug #62072 (project grub): I didn't verify the problem on version 2.06, but I think the same problem may exist in this version. ___ Reply to this item at:

[bug #62072] If a multicast RA message is received during UEFI PXE boot, grub2 program will crash

URL: <https://savannah.gnu.org/bugs/?62072> Summary: If a multicast RA message is received during UEFI PXE boot, grub2 program will crash Project: GNU GRUB Submitted by: century6 Submitted on: Thu 17 Feb 2022 11:54:56

[bug #61101] UEFI PXE boot over VLAN is failing with 'could not resolve hardware address' msg

Follow-up Comment #4, bug #61101 (project grub): I had some discussion with TJ_ on IRC/#grub. TJ was very helpful, here are some relevant links and findings we discussed: This thread is related: https://lists.gnu.org/archive/html/help-grub/2017-01/msg2.html "UEFI-PXE boot to grub2 with

[bug #61101] UEFI PXE boot over VLAN is failing with 'could not resolve hardware address' msg

Follow-up Comment #3, bug #61101 (project grub): Grub is not able to tftp/get its modules. Building modules into the image does not help "error: could not resolve hardware address." ___ Reply to this item at:

[bug #61101] UEFI PXE boot over VLAN is failing with 'could not resolve hardware address' msg

Follow-up Comment #2, bug #61101 (project grub): I have also run into this same problem. I'll add that I've tried patches to 2.06 from various vendors (Fedora, OpenSUSE, CentOS). I'm able to test on Dell (C6420/Intel) and SuperMicro (H12DSG-Q-CPU6/AMD). Same as Piotr, 2.06 works fine with

[bug #61101] UEFI PXE boot over VLAN is failing with 'could not resolve hardware address' msg

Follow-up Comment #1, bug #61101 (project grub): Windows is booting fine over UEFI PXE boot with VLAN enabled. ___ Reply to this item at: <https://savannah.gnu.org/bugs/?61101> ___ M

[bug #61101] UEFI PXE boot over VLAN is failing with 'could not resolve hardware address' msg

URL: <https://savannah.gnu.org/bugs/?61101> Summary: UEFI PXE boot over VLAN is failing with 'could not resolve hardware address' msg Project: GNU GRUB Submitted by: pb_pzaprawa Submitted on: Wed 01 Sep 2021 09:51:34

[bug #51226] Unable to chainload Windows PE EFI from PXE

Follow-up Comment #2, bug #51226 (project grub): For others also having this problem: I switched to the iPXE bootloader, which boots Windows and Linux correctly and without long loading times on physical devices as I faced with the old GRUB version. In addition to that, the iPXE developers offer

[bug #51226] Unable to chainload Windows PE EFI from PXE

Follow-up Comment #1, bug #51226 (project grub): I'm facing the same problem, but I get "BlInitializeLibrary failed 0xc017" instead of "BlInitializeLibrary failed 0xc001". Some more information from my side: I used 2.02~beta2-9 [1] from Ubuntu long time, which worked correctly. Then, I

Fwd: efi pxe qemu error repo

I am hitting this or something like it: http://savannah.gnu.org/bugs/?50518 - ipxe ... error: sector sizes of 1 bytes aren't supported yet. I can repo my problem with the file I grabbed from my debian pxe server: scp pc8:/srv/tftp/boot/grub/x86_64-efi/core.efi . qemu-system-x86_64 -m 1024

[bug #51226] Unable to chainload Windows PE EFI from PXE

URL: <http://savannah.gnu.org/bugs/?51226> Summary: Unable to chainload Windows PE EFI from PXE Project: GNU GRUB Submitted by: pmatous Submitted on: Mon 12 Jun 2017 01:05:32 PM UTC Category: B

[bug #50715] GRUB stack overwriting PXE stack (or the other way around)

Follow-up Comment #2, bug #50715 (project grub): Well, the stack location is highly error prone from every view point you look at it... Some hints and remarks you may want to consider: 1. PXE option rom allocates its own 2KB stack with which it call network bootstrap program (grub in this case

[bug #50715] GRUB stack overwriting PXE stack (or the other way around)

Follow-up Comment #1, bug #50715 (project grub): Well, this code is run as the very first thing, before any memory allocator is active. I guess we could use different, more "safe" stack location until memory size is detected. But that also means we must restrict max image size, so we still need

[bug #50715] GRUB stack overwriting PXE stack (or the other way around)

URL: <http://savannah.gnu.org/bugs/?50715> Summary: GRUB stack overwriting PXE stack (or the other way around) Project: GNU GRUB Submitted by: tomkep Submitted on: Tue 04 Apr 2017 11:39:59 AM UTC Category: N

[bug #41447] pxechainloader fails to load a pxe image

Update of bug #41447 (project grub): Planned Release:2.02 => 2.03+ ___ Follow-up Comment #1: Couldn't reproduce. Which images did you use? What did "pxe clie

[bug #41488] x86_64-efi PXE data not populated in some circumstances

Update of bug #41488 (project grub): Planned Release:2.02 => 2.03+ ___ Reply to this item at: ___

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #18, bug #50245 (project grub): Summary: I've put all my files ( for all different compilation/configuration ) here. ( all dumps, full configuration, and compilation scripts ) https://drive.google.com/file/d/0ByYkzo4DOiiscDhaYzdRVHdpRlU/view?usp=sharing Short summary: All

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #17, bug #50245 (project grub): Ok. I gave up. Last time I've used Debian-amd64 on which grub was compile and made. So like I said: 1) tftpd v4.60 + i386 -> working like a charm - no problems - everything working 2) tftpd v4.60 + efi -> can not even load grub 3) RouterOS tftp

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #16, bug #50245 (project grub): > I'm using v4.60 which is newer that yours 4.52 Oops, sorry, I somehow had 4.50 in mind. Yes, 4.60 is 64 bit only, so I cannot easily test it (I do not have 64 bit Windows). This could of course be tftp32 regression.

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #15, bug #50245 (project grub): Ok. I can not find another path :) About tftps. I'm confused after your comment. I'm using v4.60 which is newer that yours 4.52. But I will try downgrade. ___ Reply to this item at:

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #14, bug #50245 (project grub): BTW I cannot reproduce it with TFTPD32 v4.52 at all. There is "PXE compatibility" option which indeed makes TFTPD32 process only tsize option but even if I enable it, grub still boots just fine and tftpd32 log shows that it answered

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #13, bug #50245 (project grub): > tftpd v4.60 + i386 -> working like a charm OK, let's finish with this part. Could you please another version of the patch (please revert previous version first). It continues to send blksize but in different order. Please attach packet trace

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #11, bug #50245 (project grub): Thanks for Your time helping me. Definitely I messed up something with compilation last time. So. With Your path is much better, but :( 1) tftpd v4.60 + i386 -> working like a charm 2) tftpd v4.60 + efi -> can not even load grub. ( VMware is

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #10, bug #50245 (project grub): I cannot reproduce it - version with patch boots correctly here. Please try with clean build out of GIT + patch and make sure to recreate netboot directory using just built grub: pkgdatadir=$PWD ./grub-mknetdir --net-directory ... -d grub-core

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #9, bug #50245 (project grub): With patch applied I get "push out of the packet range.." error. Attached: grub_packet_range.pcapng.gz Grub-2017-02-12-17-21-51.png (file #39737, file #39738) ___ Additional Item

[bug #50245] Tftp error while booting via PXE

Update of bug #50245 (project grub): Release:2.00 => 2.02~rc1 ___ Follow-up Comment #8: OK. Your packet trace shows that server does not respond with OACK for GRUB request. Firmware

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #7, bug #50245 (project grub): Sorry for that. I've also reproduce it on i386-pc platform. Seems platform independent. ___ Reply to this item at:

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #6, bug #50245 (project grub): Sorry, I do not understand. You report problem with grub on x86_64-efi platform and attach packet capture for grub on i386-pc platform. How is it relevant for EFI problem? ___ Reply to this

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #5, bug #50245 (project grub): Files attached. I've used VMWare workstation 12.5.2 + tftpd v4.60 http://tftpd32.jounin.net No efi. I've used legacy bios. (file #39734, file #39735) ___ Additional Item Attachment:

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #4, bug #50245 (project grub): So it did configure some address. Is it the correct one? Please run tcpdump or wireshark on TFTP server and provide packet capture together with IP address grub was using. ___ Reply to this

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #3, bug #50245 (project grub): grub> net_ls_cards efinet0 00:0c:29:20:99:56 grub> net_ls_addr efinet0 00:0c:29:20:99:56 192.168.1.82 ___ Reply to this item at:

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #2, bug #50245 (project grub): what is output of net_ls_cards net_ls_addr ?? ___ Reply to this item at: ___ Message sent via/by

[bug #50245] Tftp error while booting via PXE

Follow-up Comment #1, bug #50245 (project grub): I've check grub for legacy bios: grub-mkimage -d /usr/lib/grub/i386-pc/ -O i386-pc-pxe -o ./booti386 -p '(tftp)/grub' pxe tftp and there is no problem with tftp. Ale images are loading without problems. So it's seems problem is related with efi

[bug #50245] Tftp error while booting via PXE

URL: <http://savannah.gnu.org/bugs/?50245> Summary: Tftp error while booting via PXE Project: GNU GRUB Submitted by: marianob85 Submitted on: Tue Feb 7 19:32:02 2017 Category: Network Severity:

[bug #41447] pxechainloader fails to load a pxe image

Update of bug #41447 (project grub): Planned Release:None => 2.02 ___ Reply to this item at: ___

[bug #41488] x86_64-efi PXE data not populated in some circumstances

Update of bug #41488 (project grub): Item Group: Software Error => Hardware-specific Planned Release:None => 2.02 ___ Reply to this item at:

[bug #33348] PXE support doesn't play well/at all with gPXE http support.

Update of bug #33348 (project grub): Planned Release:None => 2.03+ ___ Reply to this item at: ___

[bug #45794] another EFI PXE boot problem

Update of bug #45794 (project grub): Status:None = Invalid Open/Closed:Open = Closed ___ Follow-up Comment #3: Closing then.

[bug #45794] another EFI PXE boot problem

Follow-up Comment #2, bug #45794 (project grub): You're right. Sorry for the noise. I was debugging with a Fedora-patched version of upstream which erroneously adds the exclusive flag in grub_efi_net_config. I completely missed that and blamed the wrong party.

[bug #45794] another EFI PXE boot problem

Follow-up Comment #1, bug #45794 (project grub): grub_efi_net_config_real does not open protocol exclusively; where do you see it? The only place where exclusive open happens is open_card. bor@bor-Latitude-E5450:~/src/grub$ grep -rw GRUB_EFI_OPEN_PROTOCOL_BY_EXCLUSIVE grub-core/net/

[bug #45204] EFI PXE boot fails for some firmware

Follow-up Comment #7, bug #45204 (project grub): Works for me. Thanks! ___ Reply to this item at: http://savannah.gnu.org/bugs/?45204 ___ Message sent via/by Savannah

[bug #45204] EFI PXE boot fails for some firmware

Update of bug #45204 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Follow-up Comment #8: Pushed as

[bug #45204] EFI PXE boot fails for some firmware

Follow-up Comment #6, bug #45204 (project grub): Could you test attached patch? (file #34210) ___ Additional Item Attachment: File name: 45204.diff Size:4 KB

[bug #45204] EFI PXE boot fails for some firmware

] McastCount[0] The subsequent pxe boot worked fine both ways. ___ Reply to this item at: http://savannah.gnu.org/bugs/?45204 ___ Message sent via/by Savannah http://savannah.gnu.org

[bug #45204] EFI PXE boot fails for some firmware

Follow-up Comment #4, bug #45204 (project grub): Could you dump existing filters for problem platform? If we are forced to enter this territory I'd prefer to have explicit control over settings. I think we should do if (snp-mode-receive_filter_mask) receive_filters(snp,

[bug #45204] EFI PXE boot fails for some firmware

URL: http://savannah.gnu.org/bugs/?45204 Summary: EFI PXE boot fails for some firmware Project: GNU GRUB Submitted by: msalter Submitted on: Thu 28 May 2015 03:11:54 PM GMT Category: Network Severity

[bug #45204] EFI PXE boot fails for some firmware

Additional Item Attachment, bug #45204 (project grub): File name: efinet-save-and-restore-SNP-rx-filters.patch Size:2 KB ___ Reply to this item at: http://savannah.gnu.org/bugs/?45204 ___

[bug #45204] EFI PXE boot fails for some firmware

Follow-up Comment #3, bug #45204 (project grub): I originally did explicitly add UNICAST/BROADCAST rather than previous settings. But I wasn't sure if MULTICAST would be needed since ipv6 was supported on the platform. MULTICAST was allowed for both ipv4 and ipv6, so I ended up saving/restoring

[bug #45204] EFI PXE boot fails for some firmware

Follow-up Comment #2, bug #45204 (project grub): We do not really know what settings filters had. May be we should just set them as we need - which I assume is at least EFI_SIMPLE_NETWORK_RECEIVE_UNICAST|EFI_SIMPLE_NETWORK_RECEIVE_BROADCAST; probably specific multicast addresses for IPv6

[bug #45204] EFI PXE boot fails for some firmware

Follow-up Comment #1, bug #45204 (project grub): Your patch includes *.orig files; could you rediff without them? ___ Reply to this item at: http://savannah.gnu.org/bugs/?45204 ___ Message

[bug #41731] 64bit EFI PXE boot fails with 'error: timeout reading'

Update of bug #41731 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Follow-up Comment #6: Pushed now in

[bug #41731] 64bit EFI PXE boot fails with 'error: timeout reading'

Follow-up Comment #4, bug #41731 (project grub): Yup, the attached patch prevented the timeouts. ___ Reply to this item at: http://savannah.gnu.org/bugs/?41731 ___ Message sent via/by

[bug #41731] 64bit EFI PXE boot fails with 'error: timeout reading'

Follow-up Comment #3, bug #41731 (project grub): This sounds like a problem I recently ran into. Does the attached patch help? (file #31140) ___ Additional Item Attachment: File name:

[bug #41731] 64bit EFI PXE boot fails with 'error: timeout reading'

Follow-up Comment #2, bug #41731 (project grub): Placed the tcpdump (-vvv) here: http://ep09.pld-linux.org/~mmazur/misc/grub-pxe.log.bz2 ___ Reply to this item at: http://savannah.gnu.org/bugs/?41731

[bug #41731] 64bit EFI PXE boot fails with 'error: timeout reading'

URL: http://savannah.gnu.org/bugs/?41731 Summary: 64bit EFI PXE boot fails with 'error: timeout reading' Project: GNU GRUB Submitted by: mmazur Submitted on: Fri 28 Feb 2014 11:10:30 AM GMT Category: Network

[bug #41731] 64bit EFI PXE boot fails with 'error: timeout reading'

Follow-up Comment #1, bug #41731 (project grub): net-stall doesn't indicate problem at all, only that flow needs to be slowed down and is done so automaticaly. Could you look/supply at the packet dump? ___ Reply to this item at:

[bug #41488] x86_64-efi PXE data not populated in some circumstances

Follow-up Comment #2, bug #41488 (project grub): Packet trace seems to lack replies from DHCP server and the last DHCPACK looks more like it comes from boot server, not from DHCP Proxy. That makes it a bit confusing. Could you attach packet trace with both DHCP requests and replies?

[bug #41488] x86_64-efi PXE data not populated in some circumstances

Follow-up Comment #3, bug #41488 (project grub): I had filter for the mac of the client only. I have uploaded fresh captures. One has a better filter than the first and the unfiltered version. This was run with the latest grub (2.02~beta2) and a patch I have been working on for this issue. ~joe

[bug #41488] x86_64-efi PXE data not populated in some circumstances

Follow-up Comment #1, bug #41488 (project grub): More testing today: Replicated behavior on vanilla 2.02~beta2. test I made a small modification to efinet.c to look at ProxyOffer instead of DhcpAck. (See attached diff.pxe_reply) This time the self IP info was unpopulated but the server

[bug #41488] x86_64-efi PXE data not populated in some circumstances

URL: http://savannah.gnu.org/bugs/?41488 Summary: x86_64-efi PXE data not populated in some circumstances Project: GNU GRUB Submitted by: mr_joem Submitted on: Thu 06 Feb 2014 11:59:02 PM GMT Category: Network

[bug #41447] pxechainloader fails to load a pxe image

URL: http://savannah.gnu.org/bugs/?41447 Summary: pxechainloader fails to load a pxe image Project: GNU GRUB Submitted by: dchawla Submitted on: Mon 03 Feb 2014 07:51:55 PM GMT Category: Booting Severity

[bug #37563] Command line example to generate to pxe image is wrong.

Update of bug #37563 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Follow-up Comment #3: Update documentation to

[bug #37720] grub2 - pxe boot - multihomed nfs root system - IPAPPEND functionality missing

Follow-up Comment #3, bug #37720 (project grub): See $net_pxe_mac variable ___ Reply to this item at: http://savannah.gnu.org/bugs/?37720 ___ Message sent via/by Savannah

[bug #37720] grub2 - pxe boot - multihomed nfs root system - IPAPPEND functionality missing

URL: http://savannah.gnu.org/bugs/?37720 Summary: grub2 - pxe boot - multihomed nfs root system - IPAPPEND functionality missing Project: GNU GRUB Submitted by: stumbaumr Submitted on: Mo 12 Nov 2012 13:14:49 GMT Category

[bug #37720] grub2 - pxe boot - multihomed nfs root system - IPAPPEND functionality missing

Update of bug #37720 (project grub): Status:None = Invalid Open/Closed:Open = Closed ___ Follow-up Comment #1: Wrong. And it's not a

[bug #37563] Command line example to generate to pxe image is wrong.

URL: http://savannah.gnu.org/bugs/?37563 Summary: Command line example to generate to pxe image is wrong. Project: GNU GRUB Submitted by: tanakmura Submitted on: 2012年10月13日 14時07分33秒 Category: Documentation

[bug #37563] Command line example to generate to pxe image is wrong.

Follow-up Comment #1, bug #37563 (project grub): And tftp module will be required. ___ Reply to this item at: http://savannah.gnu.org/bugs/?37563 ___ Message sent via/by Savannah

[bug #37563] Command line example to generate to pxe image is wrong.

Follow-up Comment #2, bug #37563 (project grub): And tftp module will be required. ___ Reply to this item at: http://savannah.gnu.org/bugs/?37563 ___ Message sent via/by Savannah

[bug #36795] PXE tftp transfer dies after 50KiB

Update of bug #36795 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Reply to this item at:

[bug #36795] PXE tftp transfer dies after 50KiB

URL: http://savannah.gnu.org/bugs/?36795 Summary: PXE tftp transfer dies after 50KiB Project: GNU GRUB Submitted by: nightstrike Submitted on: Thu 05 Jul 2012 08:21:11 PM GMT Category: Network Severity

[bug #33348] PXE support doesn't play well/at all with gPXE http support.

Update of bug #33348 (project grub): Priority: 5 - Normal = 3 - Low Item Group: Software Error = Feature Request ___ Reply to this item at:

[bug #32785] PXE module is not compiled when --with-platform=efi is used

Follow-up Comment #3, bug #32785 (project grub): Hi there, I would like to implement this, however the bzr branch of grub seems to be rather buggy, is there an RC version that I can work from that has this implemented or can you point me to the revision where this was implemented so I can try

[bug #32785] PXE module is not compiled when --with-platform=efi is used

Follow-up Comment #4, bug #32785 (project grub): EFI net support is already implemented in net branch. And rather than saying rather buggy please point to exact bugs. ___ Reply to this item at: http://savannah.gnu.org/bugs/?32785

[bug #32785] PXE module is not compiled when --with-platform=efi is used

Follow-up Comment #5, bug #32785 (project grub): But not in this report but in a separate one ___ Reply to this item at: http://savannah.gnu.org/bugs/?32785 ___ Message sent via/by Savannah

[bug #32785] PXE module is not compiled when --with-platform=efi is used

Update of bug #32785 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Follow-up Comment #2: implemented in bzr.

[bug #33501] can t boot on lvm volumes with pxe boot

Follow-up Comment #2, bug #33501 (project grub): It works.thanks a lot. I did insert all theses moduless for my tests but never in that order. I thought that once the module is loaded,i didn t haved to care the order i loaded them. Thanks again Here the grub.cfg that works : menuentry 'Linux

[bug #33501] can t boot on lvm volumes with pxe boot

URL: http://savannah.gnu.org/bugs/?33501 Summary: can t boot on lvm volumes with pxe boot Project: GNU GRUB Submitted by: christian_dare Submitted on: jeu. 09 juin 2011 13:40:19 GMT Category: Network

[bug #33501] can t boot on lvm volumes with pxe boot

Update of bug #33501 (project grub): Status:None = Invalid Open/Closed:Open = Closed ___ Follow-up Comment #1: This grub.cfg is wrong.

[bug #33348] PXE support doesn't play well/at all with gPXE http support.

URL: http://savannah.gnu.org/bugs/?33348 Summary: PXE support doesn't play well/at all with gPXE http support. Project: GNU GRUB Submitted by: rvalles Submitted on: Thu 19 May 2011 07:22:48 AM GMT Category: Network

[bug #33348] PXE support doesn't play well/at all with gPXE http support.

Follow-up Comment #1, bug #33348 (project grub): Done some discussion on this on irc. phcoder | rvalles: gPXE detects multiboot header in GRUB and unloads PXE. phcoder | perhaps we need to destroy it in grub-mkimage -O i386-pc-pxe This covers

[bug #33348] PXE support doesn't play well/at all with gPXE http support.

Follow-up Comment #2, bug #33348 (project grub): It seems doc/pxe_extensions on gpxe truck documents the gPXE extensions. PXENV_FILE_OPEN seems to be used to open URLs and benefit from gPXE's support for file transfer protocols other than TFTP. Option 208-211 apparently hold the url that was

[bug #32785] PXE module is not compiled when --with-platform=efi is used

Update of bug #32785 (project grub): Priority: 5 - Normal = 3 - Low Item Group:None = Feature Request ___ Follow-up Comment #1: PXE support on EFI

[bug #32785] PXE module is not compiled when --with-platform=efi is used

URL: http://savannah.gnu.org/bugs/?32785 Summary: PXE module is not compiled when --with-platform=efi is used Project: GNU GRUB Submitted by: fredbaton Submitted on: Mon 14 Mar 2011 09:38:20 PM GMT Category: Compilation

[bug #28801] pxe boot problem

Update of bug #28801 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Reply to this item at:

[bug #28801] pxe boot problem

Follow-up Comment #2, bug #28801 (project grub): It works fine with the 1.98 ___ Reply to this item at: http://savannah.gnu.org/bugs/?28801 ___ Message posté via/par Savannah

[bug #28801] pxe boot problem

Follow-up Comment #1, bug #28801 (project grub): We've recently fixed a bug that affected PXE. Could you retest? ___ Reply to this item at: http://savannah.gnu.org/bugs/?28801 ___ Message

[bug #28801] pxe boot problem

URL: http://savannah.gnu.org/bugs/?28801 Summary: pxe boot problem Project: GNU GRUB Submitted by: nerux Submitted on: mer 03 fév 2010 14:51:29 GMT Category: None Severity: Major Priority

[bug #27814] [PATCH] PXE FS does not handle the TFTP open call's block size behaviour correctly

Update of bug #27814 (project grub): Status:None = Fixed Open/Closed:Open = Closed ___ Reply to this item at:

[bug #27814] [PATCH] PXE FS does not handle the TFTP open call's block size behaviour correctly

URL: http://savannah.gnu.org/bugs/?27814 Summary: [PATCH] PXE FS does not handle the TFTP open call's block size behaviour correctly Project: GNU GRUB Submitted by: alexextreme Submitted on: Mon 26 Oct 2009 04:25:16 PM GMT

[bug #27814] [PATCH] PXE FS does not handle the TFTP open call's block size behaviour correctly

Follow-up Comment #1, bug #27814 (project grub): Added a new patch that removes something I forgot to remove in the original. (file #18946) ___ Additional Item Attachment: File name: grub2-r2657-pxe-block-size.patch Size:1 KB

[bug #24661] [patch] PXE module does not work with TFTP correctly

Update of bug #24661 (project grub): Open/Closed:Open = Closed ___ Follow-up Comment #1: Fixed. ___ Reply to this item at:

[bug #14056] [PATCH] Adding ability to boot 3rd party's PXE bootcode from GRUB

Update of bug #14056 (project grub): Open/Closed:Open = Closed ___ Follow-up Comment #7: We've moved to GRUB 2 as a development platform. Would be nice to have this loader there. If

GRUB with PXE network driver

Hi, I've added PXE network driver support to my patch set recently. This version can now load files from the network using PXE capable NICs. I successfully tested recent e1000 NICs, as well as e100 cards, Broadcoms and 3coms. I did not find a PXE capable NIC that did not work. The code is based

[bug #14056] [PATCH] Adding ability to boot 3rd party's PXE bootcode from GRUB

Follow-up Comment #6, bug #14056 (project grub): With this patch i can sucessfully load pxelinux.0 from pxegrub! No i have a netboot system with parts using pxelinux (and menu.c32); other parts are using pxegrub. Thanks for the work! Greetings Christian Schweingruber CATATEC

[bug #14056] [PATCH] Adding ability to boot 3rd party's PXE bootcode from GRUB

Follow-up Comment #5, bug #14056 (project grub): Please try pxeloader (nd)/startrom.n12 boot (note slash changed) Please also describe what exactly you see while trying to boot startrom.n12. As for pxelinux, you may try to specify correct TFTP server and path by executing tftpserver and

  1   2   >