[quote=“chad-bisd, post: 10876, member: 18”]It also appears to have some extra lines near the top.[/quote]
Heh… Didn’t think to look there once I saw the bottom. 
Either way, figured I’d post the info here so the official core.config could be cleaned up for future downloaders.
Thanks!
I have recently tried to image a virtual machine what was created under VMWare Workstation v9.0 on a Linux host. None of the available kernels worked and all reported that they could not find a hard disk.
lspci -k in the VM shows that the SCSI controller is a:
LSI Logic / Symbios Logic 53c1030 PIC-X Fusion-MPT Dual Ultra320 SCSI (rev 01)
With a kernel module “mptspi” in use.
I build a new kernel on another machine using:
CONFIG_FUSION=y
CONFIG_FUSION_SPI=y
and this kernel works fine with the VMWare Workstation v9.0 VMs that use the LSI Logic SCSI disk controller option.
Wondering what determines which SCSI controllers are chosen to be included in the FOG distribution kernels, and if just including all SCSI controllers would really make the kernel that much larger.
As I look at the core.config, I see that almost all the SCSI controller low-level devices are included.
I suspect that the Fusion MPT was simply missed because it is outside of the “SCSI device support” menu structure.
Fusion MPT device support is actually at the same level in the menu as “SCSI device support” and is only 4 menu items down from it. Also, Fusion MPT device support does not mention SCSI in the help until you drill down to the SPI, FC and SAS options.
Hope this helps to get Fusion MPT SPI support into an official kernel. 
Thanks!
[quote=“chad-bisd, post: 10833, member: 18”]When I rebuilt my kernel, I chose to use the core.config from FOG, remove a few things I didn’t need and added a few things I did, including new source files for the ASIX usb networking drivers.
Compiling a custom kernel doesn’t take long once you’ve got the source files downloaded and the workstation configured. If the kernel for one of the newer ubuntu versions work, see if you can zcat /proc/config.gz to get the config out of it. You can also lsmod to see what modules are loaded so you know what you need to have selected when you compile your kernel.[/quote]
Not sure if anyone is aware of this but the current freeghost/kerne/core.config file has some extraneous HTML code appended to it - apparently inserted by Adblock all on one line - adding 73,883 bytes of crap to the core.config.
The end of the core.config file looks like this:
[code]# CONFIG_AVERAGE is not set
</pre></body><style type=“text/css” style="display: none !important; ">/This block of style rules is inserted by AdBlock/#FFN_Banner_Holder,#FFN_imBox_Container,#RadAd_Skyscraper,#ab_pointer,#adxLeaderboard
…snip…
],a[href^="http://www.adbrite.com/mb/commerce/purchase_form.php?"],a[href^="http://www.firstload.de/affiliate/"],a[href^=“http://www.friendlyduck.com/AF_”],a[href^=“http://www.google.com/aclk?”],a[href^=“http://www.liutilities.com/aff"],a[href^=“http://www.liutilities.com/products/campaigns/adv/”],a[href^=“http://www.my-dirty-hobby.com/?sub=”],a[href^="http://www.ringtonematcher.com/”],#cnt #center_col > #res > #topstuff > .ts:only-child,#mbEnd[cellspacing=“0”][cellpadding=“0”],#mclip_container:last-child,#mn #center_col > div > h2.spon:first-child,#mn #center_col > div > h2.spon:first-child + ol:last-child,#ssmiwdiv[jsdisplay],#tads.c,#tadsb.c,#tadsto.c,.ch[onclick=“ga(this,event)”],.ra[align=“left”][width=“30%”],.ra[align=“right”][width=“30%”],#center > .dose > .dosesingle.float { display:none !important; }</style></html>
[/code]
And of course when running a make using it,
[code]
scripts/kconfig/conf --silentoldconfig Kconfig
.config:2:warning: unexpected data
.config:3:warning: unexpected data
.config:3332:warning: unexpected data
.config:3333:warning: unexpected data
[/code]
editing the core.config file and stripping off that one line reduces the core.config file to 79,521 bytes and it works without causing make to complain.
We use in-house and deploy to our clients the following open-source products:
m0n0wall (firewall, VPN, etc)
pfSense (when m0n0wall is not enough)
Untangle (for everything that our firewalls do not do)
Xymon (server & device monitoring)
Cacti (graphing of network device traffic etc via SNMP)
FOG (imaging of course)
xTuple PostBooks (open source ERP)
Samba (file/print sharing)
Cerberus (awesome open-source web-based helpdesk system)
Asterisk (open-source VoIP PBX)
Webmin (mostly to give non-tech end-users ‘safe’ access to DHCP reservations etc)
djbdns (everywhere for DNS)
packetfence ([URL=‘https://en.wikipedia.org/wiki/Network_Access_Control’]network access control)[/URL]
Bacula (modular, enterprise backup solution)
Hylafax (network fax solution)
Apache or nginx (web servers for helpdesk, cacti, FOG, Xymon, etc)
MySQL and Postgresql databases (use by helpdesk, cacti, asterisk, packetfence, bacula, etc)
Gentoo (All of our Linux servers are Gentoo, unless a particular software product required Redhat, Centos, Ubuntu or other… I’m looking at you FOG, and packetfence
There’s more, but I just can’t remember it all right now.
Cheers![URL=‘https://en.wikipedia.org/wiki/Network_Access_Control’][/URL]
After posting the above report, It seems that each Image definition had its Operating System reset to “Please select an option”
But upon checking the new db:
select * from hosts;
it shows that on the hosts with errors their hostImage is set to an ID that does not exist. e.g not in the drop-down list of images to choose from and not in the images table.
As I set each to a correct choice, the errors at the top of the Images page went away. As I then visited each host’s page, the error there was also gone.
It appears that the OS for each image definition did not get properly upgraded.
Hi everyone. THANK YOU FOR FOG! Seriously.
Now that I realized there is a 0.33beta avail for testing, I am jumping in head-first.
Hope this is the correct place to report bugs or bug-like issues. If not, please direct me to the correct place.
I just grabbed 0.33beta today like so:
svn co [url]https://freeghost.svn.sourceforge.net/svnroot/freeghost/trunk[/url] freeghost
And ran the install script.
When the web UI updater ran on first logon I got the following errors:
[ATTACH]248[/ATTACH]
As I went through the menus, I cam across the following related errors:
[ATTACH]249[/ATTACH]
And on a host’s page:
[ATTACH]250[/ATTACH]
Google was of no help, and I also found nothing similar when searching the forums here.
Any help fixing this? Would love to get to putting 0.33beta through
Thanks! And thanks again for FOG!
edit: I have nightly dumps of the db, so I can easily restore a 0.32 fog db and run any tests requested if necessary.
[url=“/_imported_xf_attachments/0/248_FOG-0.33beta-SchemaUpdateErrors-20130222.png?:”]FOG-0.33beta-SchemaUpdateErrors-20130222.png[/url][url=“/_imported_xf_attachments/0/249_FOG-0.33beta-ImageDBErrors-20130222.png?:”]FOG-0.33beta-ImageDBErrors-20130222.png[/url][url=“/_imported_xf_attachments/0/250_FOG-0.33beta-HostDBErrors-20130222.png?:”]FOG-0.33beta-HostDBErrors-20130222.png[/url]