search for: pxebsd

Displaying 11 results from an estimated 11 matches for "pxebsd".

Did you mean: pebs
2014 Dec 04
2
vesamenu back to text before booting
On Thu, 4 Dec 2014, Gene Cumm wrote: > Ady has an excellent point. Try the following instead: > > LABEL test > MENU LABEL test > COM32 pxechn.c32 > APPEND pxebsd.0 Thanks, that works! How do I use that in the generic case? The ?pxebsd.0? file can be called as? ? PXE loader ? COMBOOT (16-bit) ? DOS .COM ? Multiboot (although it switches back to 16-bit mode immediately) ? from its own bootsector, if installed on disc (blocklist) Normally I?d chain into it...
2014 Dec 04
0
vesamenu back to text before booting
...configuration of >> the menu entry started is, IMHO, the only way to go. >> > > If you want a per-label behavior, you could try adding a new menu > entry: Ady has an excellent point. Try the following instead: LABEL test MENU LABEL test COM32 pxechn.c32 APPEND pxebsd.0 Additionally, I'd suggest using the type-specific KERNEL-like directives (LINUX, COM32, PXE, etc) instead of the "guess and pray" directive KERNEL. -- -Gene
2014 Dec 05
0
vesamenu back to text before booting
...Dec 4, 2014 at 11:27 AM, Thorsten Glaser <t.glaser at tarent.de> wrote: > On Thu, 4 Dec 2014, Gene Cumm wrote: > >> Ady has an excellent point. Try the following instead: >> >> LABEL test >> MENU LABEL test >> COM32 pxechn.c32 >> APPEND pxebsd.0 > > Thanks, that works! How do I use that in the generic case? > The ?pxebsd.0? file can be called as? > > ? PXE loader > ? COMBOOT (16-bit) > ? DOS .COM > ? Multiboot (although it switches back to 16-bit mode immediately) > ? from its own bootsector, if installed on di...
2014 Dec 03
4
vesamenu back to text before booting
...matches Binary file ./debian-installer/jessie/i386/linux matches Binary file ./debian-installer/wheezy/amd64/linux matches Binary file ./debian-installer/wheezy/i386/linux matches It does not switch back to text mode when chaining to https://www.mirbsd.org/MirOS/current/i386/boot renamed to "pxebsd.0" (used to be "ldbsd.com" before you dropped COMBOOT support). bye, //mirabilos -- tarent solutions GmbH Rochusstra?e 2-4, D-53123 Bonn ? http://www.tarent.de/ Tel: +49 228 54881-393 ? Fax: +49 228 54881-235 HRB 5168 (AG Bonn) ? USt-ID (VAT): DE122264941 Gesch?ftsf?hrer: Dr. Stefa...
2014 Dec 04
3
vesamenu back to text before booting
> On Thu, 4 Dec 2014, Ady wrote: > > > Perhaps there should be a new MENU-type directive, so to force the > > screen to text mode (as opposed to leaving it in graphics mode for as > > long as it can be)? Perhaps this could also be useful when exiting a > > vesamenu to Syslinux CLI? > > Yes, please. To make this dependent *only* on the configuration of >
2014 Dec 03
0
vesamenu back to text before booting
...arent.de> wrote: > > On Tue, 2 Dec 2014, H. Peter Anvin wrote: > > > This is the default unless the "quiet" option is set. > > Hmm. > It does not switch back to text mode when chaining to > https://www.mirbsd.org/MirOS/current/i386/boot renamed > to "pxebsd.0" (used to be "ldbsd.com" before you dropped > COMBOOT support). Please inline your entire configuration file. --Gene
2014 Dec 05
2
vesamenu back to text before booting
On Thu, 2014-12-04 at 21:26 -0500, Gene Cumm wrote: > > Thanks, that works! How do I use that in the generic case? > > The ?pxebsd.0? file can be called as? > > > > ? PXE loader > > ? COMBOOT (16-bit) > > ? DOS .COM > > ? Multiboot (although it switches back to 16-bit mode immediately) > > ? from its own bootsector, if installed on disc (blocklist) > > > > Normally I?d chain into...
2014 Dec 02
2
vesamenu back to text before booting
Hi, I still have the question: when I have an environment that uses vesamenu, for example on PXE, how do I configure it so that, for some of the menu entries, it switches back to the text mode (03h) before handing off to the next bootloader / kernel? Thanks, //mirabilos -- tarent solutions GmbH Rochusstra?e 2-4, D-53123 Bonn ? http://www.tarent.de/ Tel: +49 228 54881-393 ? Fax: +49 228
2014 Dec 02
0
vesamenu back to text before booting
On 12/02/2014 06:48 AM, Thorsten Glaser wrote: > Hi, > > I still have the question: when I have an environment that uses > vesamenu, for example on PXE, how do I configure it so that, for > some of the menu entries, it switches back to the text mode (03h) > before handing off to the next bootloader / kernel? > This is the default unless the "quiet" option is set.
2014 Dec 03
0
vesamenu back to text before booting
...ebian-installer/jessie/i386/linux matches >Binary file ./debian-installer/wheezy/amd64/linux matches >Binary file ./debian-installer/wheezy/i386/linux matches > >It does not switch back to text mode when chaining to >https://www.mirbsd.org/MirOS/current/i386/boot renamed >to "pxebsd.0" (used to be "ldbsd.com" before you dropped >COMBOOT support). > >bye, >//mirabilos -- Sent from my mobile phone. Please pardon brevity and lack of formatting.
2014 Dec 05
0
vesamenu back to text before booting
On Thu, Dec 4, 2014 at 11:40 PM, Jeffrey Hutzelman <jhutz at cmu.edu> wrote: > On Thu, 2014-12-04 at 21:26 -0500, Gene Cumm wrote: > >> > Thanks, that works! How do I use that in the generic case? >> > The ?pxebsd.0? file can be called as? >> > >> > ? PXE loader >> > ? COMBOOT (16-bit) >> > ? DOS .COM >> > ? Multiboot (although it switches back to 16-bit mode immediately) >> > ? from its own bootsector, if installed on disc (blocklist) >> > >&...