search for: f180d7c8

...; load a file via http results in an immediate error message with no > resulting traffic as far as I can see. OK. Found it. core/fs/pxe/pxe.h disabled all of the gPXE/iPXE callbacks in the core, disabling HTTP and other functionality. It appears someone disabled it intentionally in commit ID f180d7c8 but forgot to go back and conditionally re-enable it. This would affect 4.10-pre*, 5.1* and 6.0*. -- -Gene

...ate error message with no >>> resulting traffic as far as I can see. >> >> OK. Found it. core/fs/pxe/pxe.h disabled all of the gPXE/iPXE >> callbacks in the core, disabling HTTP and other functionality. It >> appears someone disabled it intentionally in commit ID f180d7c8 but >> forgot to go back and conditionally re-enable it. This would affect >> 4.10-pre*, 5.1* and 6.0*. > > Got it functional. Now to clean and commit. Commit ID 804efa7. I thought that was going to take a lot less time but it's working -- -Gene

...ror message with no > >> resulting traffic as far as I can see. > > > > OK. Found it. core/fs/pxe/pxe.h disabled all of the gPXE/iPXE > > callbacks in the core, disabling HTTP and other functionality. It > > appears someone disabled it intentionally in commit ID f180d7c8 but > > forgot to go back and conditionally re-enable it. This would affect > > 4.10-pre*, 5.1* and 6.0*. > > > > Maybe I'm not crazy after all.. :-) ;-) > Wonder if it works if re-enabled. You can check now. The Syslinux git repo has iPXE callbacks re-enab...

...results in an immediate error message with no >> resulting traffic as far as I can see. > > OK. Found it. core/fs/pxe/pxe.h disabled all of the gPXE/iPXE > callbacks in the core, disabling HTTP and other functionality. It > appears someone disabled it intentionally in commit ID f180d7c8 but > forgot to go back and conditionally re-enable it. This would affect > 4.10-pre*, 5.1* and 6.0*. Got it functional. Now to clean and commit. -- -Gene

...esults in an immediate error message with no >> resulting traffic as far as I can see. > > OK. Found it. core/fs/pxe/pxe.h disabled all of the gPXE/iPXE > callbacks in the core, disabling HTTP and other functionality. It > appears someone disabled it intentionally in commit ID f180d7c8 but > forgot to go back and conditionally re-enable it. This would affect > 4.10-pre*, 5.1* and 6.0*. > Maybe I'm not crazy after all.. :-) Wonder if it works if re-enabled. Appreciate you taking the time to look deep into this. -Alan

...Sparks via Syslinux wrote: >> On 9/24/2015 4:59 AM, Gene Cumm wrote: >>> OK. Found it. core/fs/pxe/pxe.h disabled all of the gPXE/iPXE >>> callbacks in the core, disabling HTTP and other functionality. It >>> appears someone disabled it intentionally in commit ID f180d7c8 but >>> forgot to go back and conditionally re-enable it. This would affect >>> 4.10-pre*, 5.1* and 6.0*. > You can check now. > The Syslinux git repo has iPXE callbacks re-enabled. > http://repo.or.cz/syslinux.git/commit/804efa7bb278a032d384c97e8530195b294e71bc > T...

On 9/23/2015 3:32 PM, Ady via Syslinux wrote: > >> On 9/23/2015 2:08 PM, Ady via Syslinux wrote: >> >>> Even if it still hangs with this test, does it hang exactly as before >>> (i.e. shows only one character and hangs immediately)? >> >> It happens with one entry, or two entries, or three. >> The configuration works otherwise perfectly on any