WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: gfxboot  (Read 712 times)

Offline TomyTurbos

  • Jr. Member
  • **
  • Posts: 95
gfxboot
« on: February 03, 2019, 01:27:34 PM »
Hi.  Hopefully this is the right forum for this question.

'Into the Core' makes reference to this on pg. 80, but I have not been able to find out much more about it and/or how it is done.

I have a working persistent coreplus 10.0 install on USB stick, using syslinux 6.03 , and have gfxboot.c32 in the boot/syslinux.

In syslinux.cfg I changed the UI directive to gfxboot.c32. (note that both menu.c32 and vesamenu.c32 do work).

Now I get the following immediately after Syslinux starts: 

'Usage: gfxboot.c32 boot logo_file [message file]'

followed by the boot prompt, and it does boot to 'default' after timeout.

So, obviously I'm doing it wrong!   The problem is the distinct lack of info.  I'm hoping someone here has familiarity with this and can steer me through it.  That picture of the gfx menu on pg.80 is awful pretty and I'd like to (I want to say 'I NEED to', but...) use an image of my own.

Thanks in advance.


Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6597
Re: gfxboot
« Reply #1 on: February 03, 2019, 06:51:24 PM »
Hi TomyTurbos
Posting you  syslinux.cfg  might be helpful.

Offline TomyTurbos

  • Jr. Member
  • **
  • Posts: 95
Re: gfxboot
« Reply #2 on: February 03, 2019, 07:05:18 PM »
The only difference between my working syslinux.cfg and non-working syslinux.cfg is this:

'UI=gfxboot.c32'

Config file works with 'UI=menu.c32' and 'UI=vesamenu.c32'.

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6597
Re: gfxboot
« Reply #3 on: February 03, 2019, 07:33:57 PM »
Hi TomyTurbos
... Now I get the following immediately after Syslinux starts: 

'Usage: gfxboot.c32 boot logo_file [message file]'
Based on that usage message, your example is missing the  boot logo_file  which I presume is an image file of some type. The
usage message also seems to imply an optional  message file.

Offline TomyTurbos

  • Jr. Member
  • **
  • Posts: 95
Re: gfxboot
« Reply #4 on: February 03, 2019, 08:56:29 PM »
Hi TomyTurbos
... Now I get the following immediately after Syslinux starts: 

'Usage: gfxboot.c32 boot logo_file [message file]'
Based on that usage message, your example is missing the  boot logo_file  which I presume is an image file of some type. The
usage message also seems to imply an optional  message file.

That's what I'm trying to find out.  The spartan documentation I have found has no specification of image type or size, only that it needs to be in a cpio format.

I was really hoping that someone here was actually using gfx with syslinux and could help.  Page 80 shows that it CAN be done, but there is no further insight into HOW it is done.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9997
Re: gfxboot
« Reply #5 on: February 04, 2019, 12:32:10 AM »
https://github.com/openSUSE/gfxboot (there's some xml docs under doc/)
gfxboot is quite complex, allowing menus, fonts, etc. Getting grub-0.97-splash running would be fairly easy, but it only allows 640x480 max 14 color images.
The only barriers that can stop you are the ones you create yourself.

Offline TomyTurbos

  • Jr. Member
  • **
  • Posts: 95
Re: gfxboot
« Reply #6 on: February 04, 2019, 04:52:39 PM »
Well, at this point I am abandoning the pursuit, though the power of gfxboot is still highly intriguing. 

All I know is that there MUST be a way, else why would it be in 'The Book'?