• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. GBison
    3. Topics
    G
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 12
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by GBison

    • G

      Editing the 1.0.1 PXE Menu

      General
      • • • GBison
      6
      0
      Votes
      6
      Posts
      2.1k
      Views

      Tom ElliottT

      [quote=“GBison, post: 28720, member: 18212”]Hello all!

      In my last FOG setup in .32, I had the menu background changed, removed the descriptions of the functions, and changed the wording for some of the functions themselves through an easily edited text file. If I recall, the file was called default.something and was located somewhere inside the pxelinux folder.

      Now, with the new FOG 1.0.1 moving things around, I’m a bit lost. I found where the background goes after a bit of digging, but I’m wondering where I go to change the font color, highlight color, edit the text, etc. I know about the webUI PXE menu edit field, but this just adds extra text to the bottom… not what I’m looking to do right now.

      Any help is appreciated![/quote]

      If you really want to edit the menu, there’s no major issue, and it is (more or less) still editing one simple text file.

      The file is now located in:
      /var/www/{FOGWEBDIR}/lib/fog/BootMenu.class.php

      Just be cognizant of what you’re editing. iPXE is a bit finicky about syntax. If you’re dealing with gap’s and have dashes in them, you need to have two prepending dashes: (example below)
      [code]item --gap – ---------------------------[/code]

      You’ll break ipxe if you have:
      [code]item --gap ---------------------------[/code]

      Here’s ipxe’s scripting documentation:
      [url]http://ipxe.org/scripting[/url]

      Here’s ipxe’s command information:
      [url]http://ipxe.org/cmd[/url]

      [COLOR=#000000]It’s pretty simple once you look at it, but it may take a little bit to understand how it’s being build. The old /tftpboot/pxelinux.cfg/default file was useful, but it wasn’t dynamic. That’s where moving to ipxe made things so much easier. While confusing at first, it’s much simpler and, from a programmatic standpoint, nice to work with as you can add anything you need dynamically.[/COLOR]

    • G

      Upgrade to FOG 1.0.1- Unable to Connect to Database

      FOG Problems
      • • • GBison
      20
      0
      Votes
      20
      Posts
      7.4k
      Views

      A

      [quote=“Reuben Bannister, post: 27439, member: 24266”]Im also having the same problem’s. I’ve reinstalled my Ubuntu about 20 times on site on Friday pulling my hair out!

      Hopefully they will get this sorted asap as this was my first time using the software and Im clueless about Linux as well so having to install Ubuntu Workstation then think it was something i was doing wrong to then install Server and find the same issues. Watched the install videos over and over.

      This seems to help If I run ‘sudo service mysql stop’, then ‘sudo service MySQL start’, everything works perfectly until next reboot.[/quote]

      I too am having this problem and this solution works (at least temporarily).

    • G

      FOG Necessary Hardware?

      Hardware Compatibility
      • • • GBison
      3
      0
      Votes
      3
      Posts
      1.9k
      Views

      G

      I set up one of the desktops alone with monitor, keyboard, and mouse all hooked up. Updated the kernel, which I think is why the “[I]checking in”[/I] error occurred. Fog worked fine.

      However, as a test I pulled out the VGA cable and plugged it back in during an image deployment, and [I]“irq#16: will be disabled” [/I](or something along those lines) message popped up in the FOG screen. So, even though I don’t understand how or why, it appears that this error is, in my case at least, related to monitor connections or the video cards. It’s possible that if the output changes in some way, FOG isn’t sure how to handle it.

      For assurance’s sake, we will just have our desktops fully hooked up from now on. Strange FOG would barf over something so trivial, but who knows.

      Thanks for your help Tom!

    • 1 / 1