[syslinux] Problems with gfxboot.c32

Matt Fleming matt at console-pimps.org
Wed Jul 3 06:47:20 PDT 2013

On Wed, 03 Jul, at 03:02:19PM, Andreas Heinlein wrote:
> I had to add at least one boot entry to get a working config, so I
> ended up with this isolinux.cfg:
> label 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.

Right, unfortunately gfxboot.c32 is making use of the COMBOOT API which
was deleted in 5.00 (it's done directly from 16-bit assembly so I didn't
catch it when doing the removal). Which means that it's missing large
parts of functionality, like being able to open and read/write files. 

I'll take a look at fixing this.

Matt Fleming, Intel Open Source Technology Center

More information about the Syslinux mailing list