Posts made by BryceZ

Just a thought, are they primary partitions or extended partitions? I believe FOG only recognizes primary partitions, and I’m almost certain that it cannot handle logical volumes. Something worth double checking.

Go for it! I think I spent all of two minutes typing that up off the top of my head, so any clarifications or better wording would be greatly appreciated.

If you just want to modify fog.local so it looks like:
[CODE]LABEL fog.local
kernel chain.c32
append hd0
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive.
If you are unsure, select this option.
ENDTEXT[/CODE]
Pretty sure that’s what you’re wanting.

Sounds like there might be a typo on your default file. Would you mind posting your copy of /tftpboot/pxelinux.cfg/default?

The config.php file is mostly used for settings from the initial installation, during which they are written to the database that is created and then are no longer read from the file. Some entries, such as the database and database username with password, are still read, so use caution if you feel compelled to edit this file. Modifying the FOG_TFTP_HOST in WebUI->Information->FOG Settings is the correct location, so I’m not sure why it didn’t work for you. You can always try editing the database manually, it’s stored in fog.globalsettings.

Neil and t2i3m, you might want to look into [URL=‘http://www.fogproject.org/wiki/index.php?title=Boot_looping_and_Chainloading’]chainloading[/URL] to resolve your boot order issue.

I renamed the article in question to “Boot looping and Chainloading” as that seems like a more appropriate description of the article, and added it to the Troubleshooting section of the wiki.

Jtb, you’re right. I don’t know why I thought that was in the boot image.

The problem with making that configurable is that it’s set in the boot image, which would need to be built for it. There are methods that could be used to pass this setting along from the web server to the boot image, but I don’t think it’s been considered a priority, and that would be a non-trivial change.

As for the half-duplex networks… there are some older network printers are statically set to half-duplex, and unfortunately not all businesses provide sufficient IT budgets for replacing devices that aren’t “broken”.

I would suggest that you make a feature request for the change… unfortunately there is no dedicated feature request tool currently in use, so your best bet is to just make a thread in the Developer forum with Feature Request in the title. Or if you’re comfortable attempting to write the feature yourself, pull down the latest SVN and go for it, and pass it on to the developers once you’re done so they can work with you on getting it into the next version.

I could be wrong, but I think that was an attempt to make sure FOG would work with complex networks that might include half-duplex segments. If it was set to full-duplex and you tried to run across a half-duplex segment you’ll get duplex mismatch errors.

FOG expects the 100MB partition to be there for the Single Partition type, it’s built to handle it. I’m not sure how it reacts to the 100MB partition not being there.

Your issue is definitely a strange one that I have not encountered… much as I hate suggesting it, have you tried rebuilding the server from scratch?

A terribly not secure test would be to blast away all permissions on /tftpboot/ with something like chown -R fog.root /tftpboo/ && chmod -R 777 /tftpboot/

Another thing to consider would be to check the following configs:
tftpconfig=“/etc/xinetd.d/tftp”;
tftpconfigupstartconf=“/etc/init/tftpd-hpa.conf” (Ubuntu only)
tftpconfigupstartdefaults=“/etc/default/tftpd-hpa” (Ubuntu only)

With these intermittent issues I’m wondering if it’s a hardware problem. Have you tried with different Eee PC’s? Does the server have any issues with collecting or deploying with other hosts? Have you tried different kernels?

FOG does not have any traffic shaping features at this point, only queuing.

The balancing act between hardware support maintained in the kernel versus modules in the boot image can be tricky, and it could be that you’re experiencing some sort of buffer overflow due to bad hardware support, thus the suggestion of using the 0.29 boot image. While trying various kernel and boot image combinations is not ideal, it may be the simplest way.

Have you been able to image the Eee PC’s with 0.32?

All you need to do is replace /tftpboot/fog/images/init.gz with the init.gz from a 0.29 installation.

[CODE]mv /tftpboot/fog/images/init.gz /tftpboot/fog/images/init.gz.32
cd /opt
wget http://sourceforge.net/projects/freeghost/files/FOG/fog_0.29/fog_0.29.tar.gz
tar xzvf fog_0.29.tar.gz /opt/fog_0.29
cp fog_0.29/packages/tftp/fog/images/init.gz /tftpboot/fog/images/[/CODE]

Then try imaging on of the Eee PC’s

Because of the nature of the image files, there is no currently known way of any interaction with the image once it’s been uploaded. The [URL=‘http://www.partimage.org/Partimage-FAQ’]Partimage FAQ[/URL] goes into a little more detail, but the short answer is that you need a block device driver that has never been written, or at least has not been made public if it does exist.

FOG 0.29 used a very different boot image that some people have had better luck with. You might want to try reverting to the older boot image and see if that resolves your issue.

The inventory report is built from the inventory table, which is populated by running a full-inventory task on your hosts. This is done when selecting Full Inventory and Registration from the boot menu on new hosts, and can be queued from the FOG console for existing hosts.

Unfortunately there is no (known) way of modifying the image once it’s been uploaded. The easiest solution is to deploy the image to a machine and make whatever changes before re-uploading.

We (at least some of the developers and I) looked for ways to either export the old forums or make them read-only, but sourceforge forums don’t seem to allow for that. Turning off the old forums was an attempt to simplify community interaction by using a single forum platform instead of trying to maintain both. The loss of information from the old forums was unfortunate, and we migrated some of the threads that we knew were important and ongoing, but this seemed like the best option.

The boot images don’t really have version numbers

To get the boot image from 0.29 go to the sourceforge project page for FOG and download [URL=‘http://sourceforge.net/projects/freeghost/files/FOG/fog_0.29/’]FOG 0.29[/URL] to your FOG server. Go to /tftpboot/fog/images/ and rename init.gz to init.gz.BACKUP (or whatever). Open the downloaded package and go to fog_0.29/packages/tftp/fog/images/, and copy init.gz into /tftpboot/fog/images/. Make sure the ownership and permissions are the same for init.gz and init.gz.BACKUP, and then PXE boot one of your Z400 computers to give it a try.