search for: bootlogo

...g files: ["gfxboot.cfg"] ; main menu items where user can't add boot options nobootoptions=harddisk,memtest ; main menu items that are not passed an 'install' parameter noinstallopt=harddisk,firmware,memtest [/"gfxboot.cfg"] ["isolinux.cfg"] ui gfxboot.c32 bootlogo label harddisk com32 chain.c32 hd0 exit [/"isolinux.cfg"] As usual, using 3 or more menu entries is recommended so to avoid the minor "quirks" when using less than that amount. Please don't forget to use unique LABELs without special characters (such as spaces). Altern...

Matt Fleming wrote: > On Wed, 03 Jul, at 09:53:32PM, Sebastian Herbszt wrote: >> gfxboot.c32 is supposed to work as expected if you put all required files >> inside the bootlogo archive. > > From reading com32/gfxboot/gfxboot.c, the code in the bootlog archive > calls *out* into a realmode section compiled into gfxboot.c32 > (realmode_callback.asm) to do things like open files, read sectors, etc. > > It's these utility functions that no longer work....

...39;t add boot options > > nobootoptions=harddisk,memtest > > ; main menu items that are not passed an 'install' parameter > > noinstallopt=harddisk,firmware,memtest > > [/"gfxboot.cfg"] > > > > ["isolinux.cfg"] > > ui gfxboot.c32 bootlogo > > label harddisk > > com32 chain.c32 hd0 exit > > [/"isolinux.cfg"] > > > > As usual, using 3 or more menu entries is recommended so to avoid the > > minor "quirks" when using less than that amount. Please don't forget to > > use...

Display an error message if the user specified bootlogo file is not found. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> Index: syslinux-3.82-440-g6483c80/modules/gfxboot.asm =================================================================== --- syslinux-3.82-440-g6483c80.orig/modules/gfxboot.asm +++ syslinux-3.82-440-g6483c80/modules/gf...

I am unable to get bootlogo with the syslinux.cfg. CAn anybody just list me the syslinux.cfg file for my reference. I tried the syslogo.lss file but it shows junk characters on the screen. PLease help me out Regards K.dinesh *********************************************************************** In a World Without Fences Wh...

...el /casper/vmlinuz >> append file=/cdrom/preseed/ubuntu.seed boot=casper >> initrd=/casper/initrd.lz quiet splash -- >> menu background splash.png >> ui vesamenu.c32 >> >> This works. Now just substitute 'ui vesamenu.c32' with 'ui gfxboot >> bootlogo', and I get the described behaviour. I used >> isolinux-debug.bin this time, but the last line I get is >> "Initializing gfx code...", and then the screen goes black. > > Right, unfortunately gfxboot.c32 is making use of the COMBOOT API which > was deleted in 5.0...

...; main menu items where user can't add boot options > nobootoptions=harddisk,memtest > ; main menu items that are not passed an 'install' parameter > noinstallopt=harddisk,firmware,memtest > [/"gfxboot.cfg"] > > ["isolinux.cfg"] > ui gfxboot.c32 bootlogo > label harddisk > com32 chain.c32 hd0 exit > [/"isolinux.cfg"] > > As usual, using 3 or more menu entries is recommended so to avoid the > minor "quirks" when using less than that amount. Please don't forget to > use unique LABELs without special char...

Updating myself again: On 07-08-15 16:03, Oscar Roozen wrote: > e466d24 still has an issue with png's in vesalinux causing crashes I can confirm this remaining crash is caused by the line "MENU BACKGROUND bootlogo.png". The original bootlogo.png is 640x480. Forcing the videomode with "MENU RESOLUTION 640 480" did not resolve the crashes, nor did resizing the png to 1024x768 and forcing the mode to that size. If anyone wants to test or just admire this exact bootlogo.png, it is available fo...

...>>> nobootoptions=harddisk,memtest >>> ; main menu items that are not passed an 'install' parameter >>> noinstallopt=harddisk,firmware,memtest >>> [/"gfxboot.cfg"] >>> >>> ["isolinux.cfg"] >>> ui gfxboot.c32 bootlogo >>> label harddisk >>> com32 chain.c32 hd0 exit >>> [/"isolinux.cfg"] >>> >>> As usual, using 3 or more menu entries is recommended so to avoid the >>> minor "quirks" when using less than that amount. Please don't forge...

Gene Cumm wrote: > On Tue, Dec 1, 2015 at 3:02 PM, Erwan Velu via Syslinux > <syslinux at zytor.com> wrote: > > Hi folks, > > > > As per Ady request (thanks for the reminder), I forgot to send the patches > > I run in Mageia. > > > > There is two of them : > > > > One is making errors in parsing modules.alias not fatal. > > >

Am 03.07.2013 23:05, schrieb Sebastian Herbszt: > Matt Fleming wrote: >> On Wed, 03 Jul, at 09:53:32PM, Sebastian Herbszt wrote: >>> gfxboot.c32 is supposed to work as expected if you put all required >>> files >>> inside the bootlogo archive. >> >> From reading com32/gfxboot/gfxboot.c, the code in the bootlog archive >> calls *out* into a realmode section compiled into gfxboot.c32 >> (realmode_callback.asm) to do things like open files, read sectors, etc. >> >> It's these utility function...

Hello all, i announce you the gfxboot COMBOOT module which is written in assembler. Since i didn't find as much spare time as i have hoped last weekend it is far from complete. Nevertheless the module is able to interact with the bincode ([1] and [2]) in the bootlogo cpio archive from the openSUSE 10.2 mini cd. So far it is able to call the bincode gfxboot code and setup some menu entries. Some callbacks (status, open and read) have already been implemented but it is missing a config file parser, so the menu entries are hard coded. This also applies to other pa...

On Wed, Aug 5, 2015 at 3:03 PM, Oscar Roozen via Syslinux <syslinux at zytor.com> wrote: > Unfortunately I can't test anymore until Friday. Maybe gnu-efi got > updated? I seem to remember seeing a shell script pulling in the > newest version during compilation... It's version locked to a certain commit ID. -- -Gene

...el live menu label ^Try Ubuntu without installing kernel /casper/vmlinuz append file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- menu background splash.png ui vesamenu.c32 This works. Now just substitute 'ui vesamenu.c32' with 'ui gfxboot bootlogo', and I get the described behaviour. I used isolinux-debug.bin this time, but the last line I get is "Initializing gfx code...", and then the screen goes black. Thanks, Andreas

...> unnecessary files, I can get it to an ISO under 1 MiB (trim hdt.c32, > memtest, modules.*, *.ids, *.hlp ). I downloaded all files, created an iso and noticed it's crap. gfxboot starts but instead of back.jpg I just get a black background. I didn't check the pre-created isos but the bootlogo from the above mentioned isolinux directory is incomplete and does not contain all required files. So I grabbed mageia-gfxboot-theme-4.5.6.9-1.mga6.src.rpm, corrected IN_CPIO_INSTALL in the Makefile and created a proper bootlogo file with size of ~953k instead of ~337k. With that file I get a prope...

The following changes since commit aae5483d9ebd6f091aa740108ad7f2958303931f: Steffen Winterfeldt (1): gfxboot.c32 are available in the git repository at: git://repo.or.cz/syslinux/sherbszt.git gfxboot32 Sebastian Herbszt (4): gfxboot: use $(NASM) and $(OBJCOPY) gfxboot: fix typo in cb_getcwd - wrong function number gfxboot: accept plain boot logo files

...with gfxboot, and I think it is completely unrelated to the 'packed archive' issue. Again I tried using gfxboot with the Ubuntu gfxboot archive, this time with EFI64, using a real EFI-capable machine. I first verified that everything else actually works by commenting out 'ui gfxboot bootlogo' and got a working menu. Uncommented the line again, and the screen goes black immediately, no output at all. This time it's also really not working, no 'blind' typing possible, default entry will not boot after timeout. The same with a minimal config. I must say that I used a...

...32456 vesamenu.c32 -a---- 29/09/2019 16:33 201680 libcom32.c32 -a---- 29/09/2019 16:33 199952 bootx64.efi ``` (bootx64.efi is efi64/efi/syslinux.efi renamed syslinux.cfg ``` UI vesamenu.c32 TIMEOUT 140 MENU ROWS 4 MENU CLEAR MENU BACKGROUND /slax/boot/bootlogo.png MENU RESOLUTION 1024 768 LABEL default MENU LABEL Run Linux KERNEL /slax/boot/vmlinuz APPEND vga=769 initrd=/slax/boot/initrfs.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 apparmor=0 LABEL default MENU LABEL Run Linux debug KERNEL /slax/boot/vmlinuz APPEND vga=769 initrd=/slax/boot/i...

...loader and kernel have to fit into a certanin size? 2) Is there a size limit on initrd.gz? Everything is going to run from ram, and I would like to make sure that I can set up a larger initrd than floppy emulation would allow. Does the initrd have to be gzipped? 3) With Syslinux can I replace the bootlogo with my own? Thanks in advance, David dnelson444 at tiscali.co.uk

...83c80/modules/gfxboot.asm =================================================================== --- syslinux-3.82-440-g6483c80.orig/modules/gfxboot.asm +++ syslinux-3.82-440-g6483c80/modules/gfxboot.asm @@ -968,7 +968,6 @@ msg_missing db 'missing',0 msg_usage db 'Usage: gfxboot.com <bootlogo>',0dh,0ah,0 msg_memory db 'Could not detect available memory size',0dh,0ah,0 msg_bootlogo_toobig db 'bootlogo file too big',0dh,0ah,0 -msg_pxelinux db 'pxelinux is not supported',0dh,0ah,0 msg_unknown_file_size db 'unknown file size',0dh,0ah,0 msg_not_fo...