FOG Project - User contributions [en]

Ubuntu 12.04 static ip configuration

2012-05-09T19:05:57Z

Jzhang88: Created page with "<pre> http://www.progtutor.com/blog/7-tips-tuts/751-static-ip-configuration-in-ubuntu-1204-lts Static IP configuration in Ubuntu 12.04 LTS Friday, 27 April 2012 11:05 David ..."

<pre>
http://www.progtutor.com/blog/7-tips-tuts/751-static-ip-configuration-in-ubuntu-1204-lts

Static IP configuration in Ubuntu 12.04 LTS
Friday, 27 April 2012 11:05 David Tran

There are tons of changes in Ubuntu 12.04 LTS and The most notable difference for the user is that any change manually done to /etc/resolv.conf will be lost as it gets overwritten each time something triggers resolvconf. Instead,Networking38resolvconf uses DHCP client hooks, and /etc/network/interfaces to generate a list of nameservers and domains to put in /etc/resolv.conf, which is now a symlink: /etc/resolv.conf -> ../run/resolvconf/resolv.conf

To configure the resolver, add the IP addresses of the nameservers that are appropriate for your
network in the file /etc/network/interfaces. You can also add an optional DNS suffix search-lists
to match your network domain names. For each other valid resolv.conf configuration option, you can
include, in the stanza, one line beginning with that option name with a dns- prefix. The resulting file
might look like the following:

# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.9.100
netmask 255.255.255.0
network 192.168.9.0
broadcast 192.168.9.255
gateway 192.168.9.254
dns-search example.com
dns-nameservers 8.8.8.8

</pre>

Articles Featuring FOG

2012-04-24T22:42:12Z

Jzhang88: Reverted edits by Netword (talk) to last revision by Admin

Tecchannel.de (German) - http://www.tecchannel.de/server/linux/1743185/index.html

Network World - http://www.networkworld.com/community/20-open-source-windows-tools?page=0%2C1

Michael Votaw @ University of Missouri - http://coeexchange.com/?p=3

kallasoft.com - http://www.kallasoft.com/fog-as-a-web-based-ghost-replacement/

JupiterBroadcasting.com - http://www.jupiterbroadcasting.com/?p=581

Degen.Net: FOG you, Ghost - http://www.degen.net/?p=114

Ask BJ - http://www.askbj.net/cms/node/282

astraltraveller - http://astraltraveller.wordpress.com/2009/06/03/fog-cloning-software/

dailycupoftech.com - http://www.dailycupoftech.com/2009/04/14/freebie-7-of-24-in-24-fog/

Spiceworks.com - http://community.spiceworks.com/how_to/show/373 http://community.spiceworks.com/how_to/show/975

Tech & Learning - http://www.techlearning.com/article/37828

How to get Macintosh's Netboot working with your FOG server

2012-03-31T15:24:00Z

Jzhang88: Reverted edits by TheLeaders (talk) to last revision by Jzhang88

==What this tutorial teaches==
*How to turn your FOG server into a Macintosh Netboot server as well

==What this tutorial does not teach==
*How to create images with NetRestore or Deploy Studio
*How to use NetRestore or Deploy Studio to image Macintosh's

==Getting Started==
Netboot is Apple's way of booting into a network. This how-to will teach how to change your FOG server to add support for Macintosh's through Netboot.

When FOG is installed on your machine, all of the services required for Netboot are installed. Other than creating the image, all the user has to do is create some directories and edit a couple files.

*First, run these commands:
mkdir -p /disk/0/NetBoot/NetBootSP0
mkdir /nbi
mkdir -p /tftpboot/macnbi-ppc
mkdir -p /tftpboot/macnbi-i386
printf "\n/disk/0/NetBoot *(async,ro,no_root_squash,insecure)" >> /etc/exports
printf "\n/nbi *(async,rw,no_root_squash,insecure)\n" >> /etc/exports

*Now, you need to move the images you're going to use over to your FOG server. Creating a Macintosh image is out of this article's scope, so it is assumed you already have the boot image and Macintosh image created.
*DeployStudio settings assumes you have a working DeployStudio server, and have used it to create a master image and runtime netboot set

*Make sure you have the following files:
booter
mach.macosx
mach.macosx.mkext
If you happen to have deleted these files, probably by accident, on your Mac, you may turn to Mac-how.net to find out [http://www.mac-how.net/ how to recover deleted files mac]

Note - files below depend on environment.

NetInstall-Restore.dmg
OR
DeployStudioRuntime.sparseimage

*NetInstall-Restore.dmg is the program that grabs the image from the FOG server and images the Macintosh.

*DeployStudioRuntime.sparseimage loads a boot environment for DeployStudio. This file, and the 3 files above can be found in the NetBootSP0/<runtime>.nbi folder on the DeployStudio server. The 3 boot files needed from above are located in the i386 folder.

*If you are using PowerPC Macintosh's, copy booter, mach.macosx, and mach.macosx.mkext to /tftpboot/macnbi-ppc.
cp booter mach.macosx mach.macosx.mkext /tftpboot/macnbi-ppc
*If you are using Intel Macintosh's, copy booter, mach.macosx, and mach.macosx.mkext to /tftpboot/macnbi-i386.
cp booter mach.macosx mach.macosx.mkext /tftpboot/macnbi-i386
*Copy mach.macosx and mach.macosx.mkext to /disk/0/NetBoot/NetBootSP0
cp mach.macosx mach.macosx.mkext /disk/0/NetBoot/NetBootSP0
*Copy NetInstall-Restore.dmg and the OSX image to /nbi
cp NetInstall-Restore.dmg MacOSX-3-9.dmg /nbi
OR
*Copy DeployStudioRuntime.sparseimage to /nbi or see dhcpd.conf for nfs mounting on DeployStudio Server
cp DeployStudioRuntime.sparseimage /nbi

*Now add the following lines to your dhcpd.conf (located in /etc/dhcp3 on Ubuntu):

<pre>
#Be sure to add authoritative or some G5's will not work. All G4's will work without authoritative.
authoritative;

#For PowerPC Mac's
class "AppleNBI-ppc" {
match if substring (option vendor-class-identifier, 0, 13) = "AAPLBSDPC/ppc";
option dhcp-parameter-request-list 1,3,6,12,15,17,43,53,54,60;

filename "macnbi-ppc/booter";
option vendor-class-identifier "AAPLBSDPC";

if (option dhcp-message-type = 1) {
option vendor-encapsulated-options 08:04:81:00:00:09;
}
elsif (option dhcp-message-type = 8) {
option vendor-encapsulated-options 01:01:02:08:04:81:00:00:09;
}
else {
option vendor-encapsulated-options 00:01:02:03:04:05:06:07;
}

#Replace 192.168.1.1 with the server's actual IP address.
option root-path "nfs:192.168.1.1:/nbi:NetInstall-Restore.dmg";
}

#For Intel Mac's
class "AppleNBI-i386" {
match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386";
option dhcp-parameter-request-list 1,3,17,43,60;

if (option dhcp-message-type = 1) { option vendor-class-identifier "AAPLBSDPC/i386"; }
if (option dhcp-message-type = 1) { option vendor-encapsulated-options 08:04:81:00:00:67; }

filename "macnbi-i386/booter";

#Replace 192.168.1.1 with the server's actual IP address.
#Need clarification if NetRestore works for both Intel and PowerPC
#For DeployStudio, either copy DeployStudioRuntime.sparseimage to /nbi, or use nfs share to connect to deploy studio server
#option root-path "nfs:<deploystudio_ip>:/Volumes/<volume_label>/Library/NetBoot/NetBootSP0:<runtime_folder>/DeployStudioRuntime.sparseimage";

#option root-path "nfs:192.168.1.1:/nbi:DeployStudioRuntime.sparseimage";
option root-path "nfs:192.168.1.1:/nbi:NetInstall-Restore.dmg";
}

</pre>

Restart the DHCP and NFS daemons. Hold down the N key to have your Macintosh netboot.

==Known issues==
*Please add any issues found with NetRestore or Deploy Studio.

==Software known to work==
*NetRestore 2.0.1
*Deploy Studio V1.0rc20

==Additional information and links==
*A more generic article on getting Linux to support Netboot[https://www.math.ohio-state.edu/oldwiki/administration/macosx/netboot/bsdp_with_isc_dhcp]
*Information about Netboot[http://www.bombich.com/mactips/bootpd.html]
*Deploy Studio[http://www.deploystudio.com/Home.html]

Create a windows XP image for many different hardware

2012-03-06T01:11:19Z

Jzhang88: Reverted edits by User330 (talk) to last revision by Necros

[[Category:Windows]]

= At the very beginning =

Because I realized my process many times and because I didn't wrote it before this howto, I may omit something. Please contact me if you got any problem while trying to create your master XP image. I gave so many hours to set up this receipe that I certainly encounteered a problem you may encounteer too. Use the discussion page for this howto to get an answer.

I hope this receipe will help you to reduce your everyday work.

I tested with Windows XP Home, Professionnal and Corporate yet and all hardware I found for now worked like a charm (about 20 or 30 different motherboards, including some laptops, from Pentium 4 / Athlon (socket 462) to Dual Core from AMD and Intel)

This may also work for Windows 2003, and windows 2000 (except for HAL detection and change because I don't know if sysprep for windows 2000 supports this feature)

You can find a quickly translated into french version of this tutorial here: [http://howto-windows.tbugier.fr.eu.org/wiki/index.php/Cr%C3%A9ation_d%27une_image_g%C3%A9n%C3%A9rique_Windows_XP]

= Before we begin =

I managed to create a windows XP FOG image virtually able to run on any hardware configuration. My goal is to have one and only one FOG image for this operating system. I'm currently working with 2 FOG images:
* a disk image for hard drives greater than 128 GB
* a disk image for hard drives less than 128 GB

<strike>After days trying to boot with a single image, I found that there is an issue with disks related to the 128 GB limit and the BIOS setting LARGE/LBA. I didn't found the exact thing which causes the blinking cursor of death while working on my receipe. That's why I decided to use 2 FOG images, as described above. I only know there is someting wrong related to the partition boot code in a NTFS partition ([http://mirror.href.com/thestarman/asm/mbr/NTFSBR.htm see this interesting page about NTFS partition boot code]).</strike>

I successfully tested both images I did on an 10 GB disk and a 160 GB disk on some systems. It seems my first tries were on a computer with a compatibility issue, I couldn't find for now. There is a chance only one XP image will work on any disk size. You may create only one XP installation and use it on all drives size you can find.

When running VMWare player, the guest OS runs on a CPU similar to the physical CPU running the virtual machine. If you install windows XP on an non-intel CPU, the Intelppm service will not install. Therefore, '''you must use an physical Intel CPU to run your virtual machines'''.

All target computer I tried support LBA addressing mode in the BIOS. If you got a system disk smaller than 128 GB, you may need to force the BIOS on this computer to LBA. If you don't do this you may have a blinking cursor of death on boot. If you don't have a LARGE/LBA setting in BIOS try updating it with the latest version. I found some modern computers without this option: the BIOS has been designed to an "auto" setting. If so, I advice you use a system disk bigger than 128 GB.

= Warning about Virtual machines =

I found some issues related to virtual machines:
* '''Virtual Box''' seems to run well, but when deploying your XP image on a computer, '''you will get the blinking cursor of death'''.
* '''VMWare Player''' makes a working image but '''you will get USB issues on deployed XP'''.

Therefore, I advice you to '''use VMWare Player only for testing purposes'''. When you feel ready for production, '''consider using a physical Intel based computer to create your master image'''. You will have to follow this how-to on your physical computer, exactly as you would do (or already done) on your virtual machine.

= Tools required =
* A computer with an Intel CPU (do not use an AMD CPU)
* [http://downloads.vmware.com/fr/d/info/desktop_downloads/vmware_player/3_0 VMWare Player] (do not use Virtual Box because I tried it and i didn't manage to get a working disk image with this software)
* A Windows XP home/professionnal/corporate CD
* [http://www.microsoft.com/downloads/details.aspx?familyid=3E90DC91-AC56-4665-949B-BEDA3080E0F6&displaylang=fr sysprep]
* [http://www.vernalex.com/tools/spdrvscn/ Sysprep Driver Scanner]
* [http://www.msfn.org/board/topic/43413-request-script-for-massstorage-section-sysprep/page__p__301583&#entry301583 hwid.cmd]
* [http://www.autoitscript.com/ Autoit]

= Create Master computers =

== configure the master VM ==
Install VMWare player if not already done.

Configure 2 VMs
* both with 2 microprocessors to install windows XP with ACPI multiprocessor HAL.
* one with an 40 GB hard drive and one with a 160 GB hard drive
* configure the VM BIOS to boot on the ethernet device first

'''Edit both .vmx files''' describing your VM and edit the following line:

<pre>
SCSI0.Present="TRUE"
</pre>

Change this line to this:

<pre>
SCSI0.Present="FALSE"
</pre>

If you omit this, and you try to deploy windows XP on a VM, you will have an exclamation mark on the ethernet device in your VM. Of course we want a fully working guest OS !

== Install windows XP on the master virtual computers (easy, isn't it ?) ==

'''Install windows XP in a regular way''', and use if possible a SP3 CD or ISO image. Do not install windows XP with the zero touch method provided by VMWare player. '''Install all hotfixes, .NET Frameworks, last version of IE'''. Do not install VMWare tools, or any driver. Do not install any software (adobe reader, java, office or any frequently used software) You can install them using FOG's Snapin feature. '''Do not activate your windows installation''' (if you used Home, Professionnal or Media Center)

Use the '''disk cleanup tool''' to remove all obsolete restore points, and useless files created while windows was updating. Restore points created by all hotfixes need several GigaBytes !

Now you got your windows XP up to date, use FOG web interface to '''capture an image'''. This image may be used as a roll back if something goes wrong later.

== Prepare sysprep ==

Note: I'm used to store my sysprep folder in an USB stick. Doing so makes easier the (re)creation of the master computer from scratch.

Create the sysprep folder in '''c:\'''. Extract sysprep previously downloaded from Microsoft in this newly created folder.

=== Files for the reseal process ===
Create '''sysprep.inf''' using this example. Customize your Timezone, your name, your company, AutoLogonCount and so on

<pre>
;SetupMgrTag
[GuiUnattended]
AutoLogon=Yes
AutoLogonCount=1
AdminPassword=*
EncryptedAdminPassword=NO
OEMSkipRegional=1
OEMDuplicatorstring="Windows XP"
TimeZone=105
OemSkipWelcome=1

[GuiRunOnce]
Command0="C:\WINDOWS\temp\checkforintel.cmd"

[UserData]
ProductID=xxxxx-xxxxx-xxxxx-xxxxx
FullName="Your Name"
OrgName="Your Company"
ComputerName=*

[Networking]
InstallDefaultComponents=Yes

[Identification]
JoinWorkgroup=WORKGROUP

[Unattended]
UpdateHAL=ACPIAPIC_MP,%WINDIR%\Inf\Hal.inf
OEMSkipEula=Yes
TargetPath=\WINDOWS

[Sysprep]
BuildMassStorageSection=No

[Branding]
BrandIEUsingUnattended=Yes

[Proxy]
Proxy_Enable=0
Use_Same_Proxy=0

;This must be the last line !
[SysprepMassStorage]
</pre>

Download and copy Sysprep Driver Scanner in '''c:\sysprep'''

Create '''hwid.cmd''' [http://www.msfn.org/board/topic/43413-request-script-for-massstorage-section-sysprep/page__p__301583&#entry301583 source here]

<pre>
rem %1 is path to MassDriverPacks Folder
IF "%1"=="" GOTO EOF
IF NOT EXIST %1 GOTO EOF

SETLOCAL ENABLEDELAYEDEXPANSION
SET STDOUT=%cd%\HWIDS.TXT
TYPE>%STDOUT% 2>NUL

::traverse drivers path
CALL :TRAVERSAL %1

GOTO EOF

:TRAVERSAL
PUSHD %1
for /f %%f in ('Dir /b *.inf') do (
for /f "eol=- tokens=2 delims=," %%i in ('find /i "pci\ven" %%f') do (
for /f "tokens=*" %%j in ("%%i") do (
for /f "tokens=1* delims=_" %%k in ("%%j") do (
if /i "%%k" EQU "PCI\VEN" (
for /f "usebackq tokens=1* delims=; " %%a in ('%%j') do (
echo %%a=%cd%\%%f>>%STDOUT%
)
)
)
)
)
)

FOR /F %%I IN ('DIR /AD /OGN /B') DO (
CALL :TRAVERSAL %CD%\%%I
)
POPD
GOTO EOF

:EOF
</pre>

Create the file '''kbdmouse.txt''' on '''c:\sysprep'''

<pre>
*pnp0303=C:\windows\inf\keyboard.inf
*pnp0f03=C:\windows\inf\msmouse.inf
*pnp0f0b=C:\windows\inf\msmouse.inf
*pnp0f0e=C:\windows\inf\msmouse.inf
*pnp0f12=C:\windows\inf\msmouse.inf
*pnp0f13=C:\windows\inf\msmouse.inf
</pre>

Use Autoit to compile this script into an exe. '''This is for french windows XP''' ! Edit the file with the three lines below to make it for english windows XP. The new exe file must be in '''c:\sysprep'''.

<pre>
; <AUT2EXE VERSION: 3.1.1.0>

; ----------------------------------------------------------------------------
;
; AutoIt Version: 3.1.0
; Author: Isaac Holmes
;
; Script Function:
; Click Continue Anyway for hardware installation during sysprep
;
; Edited to be easily localized
;
; ----------------------------------------------------------------------------

; Script Start - Add your code below here

$hardwareInstall = "Installation matérielle"
$confirmFileReplace = "Confirmer le remplacement du fichier"
$addHardwareWizard = "Assistant Ajout de matériel"

do

while not (winexists ($hardwareInstall) or winexists ($confirmFileReplace) or winexists ($addHardwareWizard))
wend

Sleep (100)

if winexists($hardwareInstall) then
WinActivate($hardwareInstall)
send("!c")
EndIf

if winexists($confirmFileReplace) then
WinActivate($confirmFileReplace)
send("{TAB}{ENTER}")
EndIf

if winexists($addHardwareWizard) then
WinActivate($confirmFileReplace)
send("{ENTER}")
EndIf
until 1=2
</pre>

For english, replace the three variables definitions by these lines (thanks to google for providing images an find the exact translation !)
<pre>
; ----------------------------------------------------------------------------
; English/US strings
; ----------------------------------------------------------------------------
$hardwareInstall = "Hardware Installation"
$confirmFileReplace = "Confirm File Replace"
$addHardwareWizard = "Add Hardware Wizard"
</pre>

Create '''reseal.cmd''' in '''c:\sysprep'''
<pre>
@echo off

echo ==============================================
echo.
echo Replace the IDE driver by the
echo generic IDE driver.
echo You may do this now
echo and then, press a key to continue
echo.
echo ==============================================
pause

echo ==============================================
echo.
echo Customize your local admin password in
echo %systemdrive%\sysprep\sysprep.inf
echo.
echo You may do this now
echo and then, press a key to continue
echo.
echo ==============================================
notepad %systemdrive%\sysprep\sysprep.inf
pause

echo ==============================================
echo.
echo Install FOG client, and configure it for your
echo network.
echo.
echo You may do this now
echo and then, press a key to continue
echo.
echo ==============================================
pause

pushd %systemdrive%\sysprep

::sysprep driver scanner (voir spdrvscn.exe /?)
echo Sysprep Driver Scanner...
%systemdrive%\sysprep\spdrvscn.exe /p %systemdrive%\sysprep\drivers\net /e inf /f /o "XP Image: ~year/~month/~day" /s /a /q

::désactiver le service/driver de processeur intel
echo Désactivation de intelppm
sc config intelppm start= disabled

::reactivation auto par script (pour, un jour, se passer du .vbs)
:: wmic cpu get Manufacturer | findstr /i intel
:: if "%errorlevel%" == "0" (sc config intelppm start= system)

::construire la liste des drivers de stockage de masse
echo Création de la liste des pilotes de stockage de masse
%systemdrive%\sysprep\sysprep.exe -bmsd

::créer la liste des drivers de stockage de masse personnalisés
echo Création de la liste additionnelle des pilotes de stockage de masse
call %systemdrive%\sysprep\hwid.cmd %systemdrive%\sysprep\drivers\stor

::ajouter les drivers clavier et souris de base au drivers de stockage de masse
::voir http://support.microsoft.com/?scid=kb%3Ben-us%3B283079&x=15&y=14
::permet de résoudre les problèmes de clavier et souris qui ne répondent pas
::pendant le mini-setup (ou windows welcome)
echo Bug de non-réponse du clavier et de la souris
type %systemdrive%\sysprep\kbdmouse.txt >> %systemdrive%\sysprep\sysprep.inf

::ajouter la liste des drivers de stockage de masse au sysprep
echo Fusion des 2 listes de pilotes de stockage de masse dans sysprep.inf
type %systemdrive%\sysprep\hwids.txt >> %systemdrive%\sysprep\sysprep.inf

::Nettoyage du disque
echo Nettoyage du disque dur
::désactivé pour l'instant
::call clean-hdd.cmd

::copier la vérification de CPU intel dans %windir%\temp
echo Copie des fichiers pour réactiver intelppm
copy checkforintel.cmd %windir%\temp\checkforintel.cmd /Y
echo Copie des fichiers pour redétecter les interfaces IDE
::désactivé pour recherche d'un petit bug
::copy update-ide.cmd %windir%\temp\update-ide.cmd /Y

echo Sysprep
start %systemdrive%\sysprep\continue-xp-fr.exe
if %1!==debug! %systemdrive%\sysprep\sysprep.exe
if NOT %1!==debug! %systemdrive%\sysprep\sysprep.exe -reseal -mini -noreboot -quiet

popd
</pre>

=== Device drivers repository ===

Create folders '''c:\sysprep\drivers\net''' and '''c:\sysprep\drivers\stor'''. These folders are respectively for ethernet drivers (including wireless) and mass storage controllers.

Create subdirectories with no space, and with a explicit name to easily identify the contained driver. Here is my repository tree with drivers working in the reseal process:
* drivers
** net
*** atheros
**** ar8121
**** ar8131
**** ar81xx
*** broadcom
**** 43xx
**** [http://www.broadcom.com/support/ethernet_nic/4401.php 440x]
**** [http://www.broadcom.com/support/ethernet_nic/netxtreme_desktop.php 57xx]
*** intel
**** pro100
**** pro1000
**** progb
*** marvell
**** yukon
*** nvidia
**** [http://www.nvidia.com/object/nforce_winxp_15.23.html 15.23]
**** [http://www.nvidia.com/object/nforce_winxp_15.25.html 15.25]
**** [http://www.nvidia.com/object/nforce_winxp_15.26.html 15.26]
**** [http://www.nvidia.com/object/nforce_winxp_15.45.html 15.45]
**** [http://www.nvidia.com/object/nforce_winxp_15.46.html 15.46]
**** [http://www.nvidia.com/object/nforce_winxp_20.09.html 20.09]
*** realtek
**** 8102,8102,8138,8168
**** 8139,8169
*** sis
**** 19x
**** 6xx,7xx,9xx
*** via
**** [http://www.via.com.tw/en/support/drivers.jsp rhine]
** stor
*** [http://www.nvidia.com/page/uli_drivers.html ali]
**** ide
**** M5281
**** M528x
*** [http://game.amd.com/gb-uk/drivers_catalyst.aspx?driver=Integrated/xp32-chipset ati]
*** intel
*** ite
**** raid
*** marvell
**** m614x
*** nvidia
**** [http://www.nvidia.com/object/nforce_winxp_15.23.html 15.23]
**** [http://www.nvidia.com/object/nforce_winxp_15.25.html 15.25]
**** [http://www.nvidia.com/object/nforce_winxp_15.26.html 15.26]
**** [http://www.nvidia.com/object/nforce_winxp_20.09.html 20.09]
*** promise
**** 378r
*** [http://www.siliconimage.com/support/index.aspx sil-img]
**** 3112r
**** 3114r
**** 3124
**** 3124r
**** 3132
**** 3132r5
**** 3x14
*** [http://www.sis.com/download/ sis]
**** 180OB
**** 964
**** 965
**** 966-968-1182
**** 966-968-1184
**** ide
*** via
**** vt64xx
**** vt87xx

=== Files for the deployment process ===
Create a file named '''checkforintel.cmd''' in '''c:\sysprep''' with this content:

<pre>
@echo off
wmic cpu get Manufacturer | findstr /i GenuineIntel
if "%errorlevel%" == "0" (sc config intelppm start= system)
</pre>

== Run sysprep ==

If you didn't captured a FOG image of your master (virtual) computer before launching the reseal process do it now. If something goes wrong while sysprep is running, you may be happy to have an easy roolback.

Run the reseal process by launching '''reseal.cmd''' and follow the instructions given at the beginning. They are here as a remainder.

The reseal process is very long depending of the number of mass storage drivers in the repository. I'm used to wait between 2 and 5 hours.

reseal.cmd doesn't shuts down the system after the work ended. Doing so ensures you can see any error before you shut down the guest yourself. You may add shutdown command at the end of the script or use the appropriate switch when invoking sysprep.exe

Note: I read somewhere that sysprep is alternatively long and fast. I saw that is true. If you want to add a single driver for a new hardware, you may deploy a master computer with your sealed XP image and re-seal it a second time with your new driver. (use the sysprep folder you ever keep near you in an USB stick).

= Capture the final master image =

Use FOG's web interface to capture your final image. Don't overwrite the rollback image you created before the reseal process. This image may be useful later.

= Deploy the master image on target computers =

Use FOG's web interface as usual to deploy your target computers.

With a 100 Mb/s network my images are about 1.5 GB and are downloaded in less than 2 minutes. After some reboots your windows XP is ready. From the image push to a working desktop on the target computer, the elapsed time is less than 10 minutes.

= Create snapins for device drivers =

== Howto create an autoextractible 7Zip archive ==

Download the 7Zip sfx for installer [http://7-zip.org/download.html here].

Extract '''7zS.sfx'''.

Create '''7zip.txt''' with the following (more about the file format [http://www.bugaco.com/7zip/MANUAL/switches/sfx.htm here]):

<pre>
;!@Install@!UTF-8!
Title="7-Zip 4.01 Update"
ExecuteFile="setup.cmd"
;!@InstallEnd@!
</pre>

Edit the file as you wish

Create a file '''setup.cmd''' with all commands needed by your software or driver to setup silently.

Create or re-use a folder containing the software to pack into an autoextractible file. Create a folder '''__7zip__''' containing a copy of '''7zip.txt''' (this is useful when you want to update the autoextractible file)

Create an 7Zip archive with all needed files. then concatenate it to the SFX with the copy command:

<pre>
copy /b 7zS.sfx + __7zip__\7zip.txt + archive.7z archive.exe
</pre>

You will get a new .exe file able to unpack and setup your software. Upload this .exe file to your snapins repository

== Close all "new hardware detected" wizard" ==

Please edit '''$WizardTitle''' to match the title of the windows depending your language. This example is for french Windows XP.

Compile this script into an exe with the tool provided with autoit.

<pre>
#region ---Au3Recorder generated code Start ---
Opt("WinWaitDelay",100)
Opt("WinDetectHiddenText",1)
Opt("MouseCoordMode",0)

Dim $CheckAgain
Dim $WizardTitle = "Assistant Matériel détecté"

$CheckAgain = 1
While ($CheckAgain > 0)
sleep(5000)
If (WinExists($WizardTitle ,"")) then
_WinWaitActivate($WizardTitle ,"")
Send("{ESC}")
Else
$CheckAgain = 0
EndIf
WEnd

#region --- Internal functions Au3Recorder Start ---
Func _WinWaitActivate($title,$text,$timeout=0)
WinWait($title,$text,$timeout)
If Not WinActive($title,$text) Then WinActivate($title,$text)
WinWaitActive($title,$text,$timeout)
EndFunc
#endregion --- Internal functions Au3Recorder End ---

#endregion --- Au3Recorder generated code End ---
</pre>

== Find how to install a driver with silent switchs ==

Some drivers may be unpacked by 7Zip and some others need to be unpacked and cancelled (nvidia chipset/video drivers, ATI video drivers). Some drivers may run like a charm by adding switches to their commandline. Some drivers may need an autoit script.

When you found a way to install your device driver silently, create an archive with 7Zip as described earlier.

Here is a (very incomplete) list of device drivers I managed to install silently. I will grow this list soon.

[[Working device drivers snapins]]

= Disabling autologon =

If you set AutologonCount, you may want tu set it to a high number and disable it manually once it becomes useless.

You may create a snapin which executes this commandline

<pre>
rundll32 netplwiz.dll,ClearAutoLogon
</pre>

It will disable autologon, and erase from the registry the administrator password given in sysprep.inf.

This is a security issue because the password remains in plaintext in the registry when you set '''EncryptedAdminPassword=NO''' in sysprep.inf.

= Troubleshooting =

== Sysprep fails writing registry ==

I had this error and after lots of research, I found a forum where someone said that a mass storage driver may be responsible of this error. Because my driver repository is quite big, I had to try and retry by eliminating drivers by brand and model until I found the bad driver. Because the system is not automatically shut down after sysprep.exe runs you may run sysprep.exe manually without rebooting and reset files changed by reseal.cmd

All my drivers are from the chip manufacturer. I remember that my faulty driver is from Silicon Image, but cannot remember today which one I had to remove. All drivers in the above list are working in the reseal process. However I cannot test all of them in deployment process because I don't have a motherboard with each model of mass storage controller.

== I have to plug my USB Flash Disk our my USB stick twice before windows lets me read his content ==

I noticed this issue after I released my second version of disk image for my own purpose. I checked my first disk image and it works well. I did some tries on my virtual machine: install the universal USB driver instead of the intel one, create my XP instalation withou plugging any USB device, and installing windows on a VM without any USB port. None of these tries was successful. I'm nearly sure that the only workaround is to create your master XP image from a physical computer. The major difference between my first final image and my second one is virtualization. I'm nearly sure building the master XP installation on a pure physical computer will work better with USB. I'll give a try soon.

== Chipset Intel P45 ==

I found a computer which doesn't work with my driver repository. It is build with an Asus P5Q motherboard. You may have to add to the drivers the mass storage driver from the CD provided with the motherboard. Not yet tested. I found in the txtsetup.oem file some small differences compared to the f6floppy drivers provided on Intel's website.

== I'm sure I got the mass storage driver for my chipset but it keeps to reboot or show STOP 0x7B error ==

A found a computer with ATI chipset which doesn't work with SATA when it is set to AHCI mode or native mode (deployed with XP). I had to set the SATA to IDE mode. Googling showed a similar problem on a gigabyte mainboard with the same ATI chipset, whereas windows has been installed a classic way. A change on the driver's .inf file found in a forum didn't help. If performance is not critical, try to use IDE (or legacy) mode in the BIOS setup.

== The key entered during Mini Setup is invalid when I'm activating my windows installation ==

This issue doesn't appear when the licence key is in sysprep.inf.

I noticed this small issue, and if you re-enter the same licence key and try to activate it a second time, it just works fine. I noticed also this occurred when I installed Windows XP Home without providing the licence key during setup (you can do that only with a XP SP3 CD, slipstreamed or not) '''AND''' without providing a licence key in sysprep.inf . I will try to provide a licence key during the installation on my master computer and compare if this issue keeps to occur after deployment on a target conputer. I think this will also affect XP Professionnal when installed the same way.

== I changed some settings in VMWare Player and now my XP fails to boot with a BSOD 0x0000007B ==

Have a look in your .vmx file defining the hardware of your virtual machine. The parameter '''scsi0.present''' may be reverted to '''TRUE'''.

= TO DO =

* Begin a howto to create device drivers snapins
I got working snapins for Intel (chipset, graphic), ATI (graphic), Realtek (AC97, HDAudio), NVidia (chipset, graphic), and some other hardware

* give download links to each driver in the driver repository tree

* Increase Autologoncount to 5, give snapin to deactivate autologon, and delete the password in the registry (after autologoncount reaches 0, the password remains (if unencrypted in sysprep.inf) unencrypted in the registry !)

= Links =
[http://www.windowsreference.com/windows-xp-sp3/stop-0x0000007e-error-after-installing-sp3-on-amd-based-systems/ command line to disable/enable intelppm service]

[http://www.msfn.org/board/topic/115873-sysprep-ghost-and-drivers/ Autoit script to install unsigned drivers ]

[http://www.runpcrun.com/0x0000007E About STOP 0x0000007E, Intelppm.sys related]

[http://windowsxp.mvps.org/noautologon.htm How to disable Autologon]

User:Jzhang88

2012-02-27T22:52:19Z

Jzhang88: Blanked the page

Acer Iconia Tab w500

2012-02-23T23:45:31Z

Jzhang88: Reverted edits by JamiTodd (talk) to last revision by Jzhang88

== Build a Custom Kernel with Asix USB NIC Drivers ==

Start by following the instructions for [[Build FOG Core Kernel]].

This entry was written based on creating a 3.1.5 kernel using Ubuntu 11.10 as the compiling system. The kernel generated from these instructions is being used on FOG 0.29 and has successfully imaged 40 Iconia w500 Tablets.

=== Download Asix 88772B USB NIC Drivers Source Code ===

Before completing the "make xconfig" step, download the Asix drivers, extract them, and copy them into the kernel source tree.

wget http://www.asix.com.tw/FrootAttach/driver/AX88772B_772A_760_772_178_LINUX_Driver_v4.1.0_Source.tar.bz2

tar -xzvf AX88772B_772A_760_772_178_LINUX_Driver_v4.1.0_Source.tar.bz2

cp AX88772B_772A_760_772_178_LINUX_Driver_v4.1.0_Source/a* (kernel-source-tree-root)/drivers/net/usb/

(NOTE1: you only need to copy the files starting with the letter "a" from the driver source folder... the Makefile and Readme are not needed. Thus the a*...)

(NOTE2: Based on the [[Build FOG Core Kernel]] page, (kernel-source-tree-root) is located in ~/Desktop/linux-3.1.5)

=== make xconfig and modify it for w500 ===

make xconfig

Select the Device Drivers - Network Device Support - USB Network Adapters - Multipurpose USB Networking Framework - Asix AX88xxx USB 2.0 Ethernet Adapters

Deselected the Device Drivers - Graphics Support - AGPGART (AGP Support)

Selected Device Drivers - Graphics Support - Direct Rendering Manage (XFree86 4.1.0 and Higher DRI Support) - ATI Radeon.

Deselected the option under ATI Radeon for: Enable modesetting on radeon by default - NEW DRIVER.

Save and exit

Continue instructions on [[Build FOG Core Kernel]] by issuing the make command and copying your kernel to FOG's tftpboot location listed on that page.

=== Create tftpd-map and alter configuration if using a separate DHCP server ===

Create file named /etc/default/tftpd-hpa.map using your favorite text editor such as nano.
(i.e. sudo nano /etc/default/tftpd-hpa.map)

Here is a copy of the map I am using... You'll need to put this into the map file you just created above:

# if the requested file starts with a-f A-F or 0-9 send it
# otherwise send pxelinux.0 for PXE stacks that are corrupt
# This was added for the Acer Iconia W500 Tablet

e ^[a-zA-Z0-9].*$
r .* pxelinux.0

Next edit the configuration file (/etc/default/tftpd-hpa) to tell it to use the map file you just created...

sudo nano /etc/default/tftpd-hpa

Here is a copy of my configuration... the important thing is the addition of the option -m and the map file location.

# /etc/default/tftpd-hpa
# FOG Modified version
TFTP_USERNAME="root"
TFTP_DIRECTORY="/tftpboot"
TFTP_ADDRESS="0.0.0.0:69"
TFTP_OPTIONS="-s -v -m /etc/default/tftpd-hpa.map"

Finally issue the restart command for the tftpd service or restart your FOG server.

sudo service tftpd-hpa restart

=== Keyboard / PXE issue ===

To inventory the Iconia w500 and navigate the FOG Menu after PXE booting there is an Acer Support document that you'll need to follow... This will allow you to upload your initial image to FOG as a keyboard is required.
[http://acer.custhelp.com/app/answers/detail/a_id/8157/~/how-do-i-perform-a-network-pxe-boot-on-the-iconia-tab-w500%3F Here] is the link: http://acer.custhelp.com/app/answers/detail/a_id/8157/~/how-do-i-perform-a-network-pxe-boot-on-the-iconia-tab-w500%3F

This work around involves hooking a USB extension cable to the keyboard dock and the center USB port on the tablet... and the other USB port on the tablet to a keyboard or USB Hub > keyboard.

New Home Page

2012-02-07T13:33:16Z

Jzhang88:

A guide to deployment, management,
And concept overview
For FOG.

Based on a document by:
Thomas J. Munn
CISSP

== Introduction ==

=== Preface to this Document ===

This document is intended to be modified by FOG users, in fact it is based on a document created by a FOG user. If you feel something could be said better or put more clearly, it is encouraged that you make changes to this document. We just ask that you keep it constructive and in good taste. In order to edit the wiki you are now required to create an account, as spamming of the forum has gotten pretty bad recently.

===What is FOG?===

FOG is a Linux-based, free and open source computer imaging solution for Windows XP, Vista, 7, and Linux (limited) that ties together a few open-source tools with a php-based web interface. FOG doesn't use any boot disks, or CDs; everything is done via TFTP and PXE. Also with FOG many network drivers are built into the kernel, so you don't really need to worry about nic drivers (unless there isn't kernel support for it yet). FOG also supports putting an image that came from a computer with a 80GB partition onto a machine with a 40GB hard drive as long as the data is less than 40GB. FOG supports multi-casting, meaning that you can image many PCs from the same stream. So it is about as fast whether you are imaging 1 PC or 20. 

=== Why FOG? ===

Working in an educational environment, our organization's techs very often re-imaged computers in their day to day activities. For a long time we used a commercial product that in many ways didn't meet our needs. It wasn't web based, and you needed to create driver disks, floppys or USB drives. Other things were very difficult, such as searching for a host by MAC address and the product was expensive, even with an educational discount. So we started to investigate ways in which we could do things better, and as our organization struggled to make a commercial product work better by trying to pxe boot dos, and testing it in Windows PE, we, the FOG Team, started to build a linux based solution on our own time. We finally got a working version and decided to release it as open source, since we use many other open source products, and figured we should give back to the community.

===What features are included with FOG?===

FOG is more than just an imaging solution. FOG has grown into a imaging/cloning and network management solution. FOG now performs tasks like installing and managing printers, tracking user access to computers, installing applications remotely via snapins, and automatic user log offs. If a computer is badly infected with a virus or malware, you can boot FOG in AV mode and have it remove the viruses. You can wipe your disks, destroying all information that was on them, you can restore deleted files, or scan the disk for bad blocks. 

=== Fundamental Concepts ===
This section provides some basic concepts that the FOG Project uses.
<UL><LI>'''Unicasting''' 
Unicasting in FOG means sending a single image to a single host. This can mean an upload or a deploy, and is independent of the image type. 
See this section for more on [[Unicasting]]</li>
<LI>'''Multicasting''' 
Multicasting in FOG uses UDPcast to send a single image to multiple computers using only slightly more bandwidth then sending the image to a single computer or unicast. 
See this section for more on [[Multicasting]]</li></UL>

=== FOG Benchmarks ===

'''[[Internal Benchmarks]]'''

===Requirements===
====Hardware====

FOG is best implemented on a dedicated server, any spare machine you have. We recommend that you have '''sufficient''' hard drive space as each image you make is usually between 5 and 10 GB and it's best to have a '''gigabit NIC''' with as much processor and RAM you can throw at it. 

====Software====

The FOG server runs on various flavors of Linux, which can be downloaded for free. The FOG installer script will verify or download and automatically install many open-source packages such as: MySQL, PHP, Apache, and more software from the open source community.

FOG is primarily geared toward helping school administrators manage mostly Windows environments, but more support for Linux clients is included in the latest version.
 

====Network====

FOG can be installed in a small lab on isolated network with just a single inexpensive switch and a handful of Ethernet cables; it can be added to your home network; or can be integrated with your existing enterprise network infrastructure with multiple subnets or VLANS (advanced configuration necessary.) The more robust your network, the better FOG can perform. Some adjustments are required on existing DHCP server(s) to integrate FOG into a network, as discussed later in the documentation. 

====How much does FOG cost?====

FOG is an Open Source project and licensed under the GPL which means that you are free to use FOG on as many computers as you like for free. This also means that if you want to make any changes to the source code you are free to do so.

The creators of FOG make no profits from this project with the exception of donations. FOG comes with absolutely '''NO WARRANTY''' and the creators of FOG are in '''NO WAY RESPONSIBLE FOR ANY DAMAGE OR LOSS CAUSED BY FOG!''' Please see the license file included with the FOG release for more information. With that being said, we attempt to do a very good job of supporting our users; in fact it is one of the goals of FOG to have better support than most commercial products. All support requests should be placed through the FOG's sourceforge forum which is located at:

https://sourceforge.net/projects/freeghost/forums

Thanks for supporting open source software and enjoy! 
*[http://www.office-coupons.net/office-depot-store-locator/ Office Depot Store Locator]

== Installing FOG ==

FOG is a typical ''[http://en.wikipedia.org/wiki/LAMP_%28software_bundle%29 LAMP]'' software bundle, so the main server is a '''L'''inux box. The rest of the components: '''A'''pache, '''M'''ySQL, '''P'''HP, and several other services, are automatically downloaded and installed by the FOG installation script. 
FOG can be installed by an experienced administrator in about 30 minutes. A new user with some familiarity with Linux can expect results in a few hours by following the guides below. 
 
==='''Full Step-By-Step [[Installation]] Guides'''===

====[[Installation#Ubuntu_.28Recommended.29|Ubuntu]] (Recommended)====
====[[Installation#Fedora_.28Recommended.29|Fedora]] (Recommended)====
====[[Installation#Debian|Debian]]====
====[[Installation#CentOS|CentOS]]====
====[[Installation#VMWare|VMware]]====

=== Network Integration ===
==== Basic Network Setup ====
The FOG setup script asks several questions which might not be obvious. These sections describe only the most generic settings.
<ul><li>'''Isolated Network''' 
The easiest method to image machines and get started using FOG is on a small, isolated network. The FOG setup program will configure all the necessary services for you completely automatically. This section covers only those basic steps.
 '''See [[FOG on an Isolated Network]]'''</li> 
<li>'''Integrating FOG Server with Existing Network Systems''' 
Slightly more complicated is the task of integrating FOG into your existing network infrastructure. This section attempts to describe the steps to link FOG with a fairly generic enterprise system. 
'''See [[Integrating FOG into an Existing Network]]'''</li></ul>
----
====Advanced Network Setup====
===== Modifications on your DHCP Server(s) =====
If you are installing FOG on an existing network, adjustments are necessary to forward DHCP clients to the FOG server after they receive their IP addresses: [[Modifying existing DHCP server to work with FOG]]
===== Wake On Lan (WOL) =====
<ul><li> [[Cisco_Wake_on_lan|Cisco WOL - Layer 3]] </li>
<li> [[ProCurve_Wake_on_lan|ProCurve WOL]] </li></ul>
===== Multicast/UDPCast =====
<ul><li> [[Cisco_Multi_Cast|Cisco Multicast - Layer 3]] </li></ul>

=== FOG Server Maintenance ===
====[[Backing up FOG]]====
====[[Restoring FOG from Backup]]====
====[[Upgrading the FOG Server]]====

== Using FOG ==

=== Quick Start - Basic Tasks ===

So you have a FOG server installed and setup, now what do you do? Below are a few common "Getting Started" items.

#[[Uploading your first Image]]
#[[Deploying your Image a single client]]
#[[Deploying your Image a group of clients]]

==== Tips ====

#FOG requires that all hosts be entered in the FOG Database for imaging. The most important part is getting the MAC address of the host right. FOG uses the MAC for targeting image installs and acquires. Using the wrong MAC could result in unpredictable results, including the complete erasure of the wrong pc! The IP address isn’t that important, and the ‘name’ field is more for the user. Mac address format is 00:12:3F:C4:57:0C . Using dashes, spaces, or no items at all will result in the GUI not accepting the host.
#At least one image must be defined using the FOG web interface under the Images section. After the image is defined, it must be associated with the hosts. This can be done through the web interface or on the client.
#After hosts are entered, it is wise to group them together by function, hardware, or common image. The image will be shared among all members of a particular group. This occurs within the ‘hosts’ screen, and NOT on the groups screen. This is a little confusing, so it helps to think of the ‘groups’ screen as a task generator, rather than controlling group memberships.
#For importing hosts in a .csv file follow the format below: 1 line per host:<pre>"00:c0:4f:18:62:63","Hostname","1.1.1.1","Your description","XP/Vista","Image filename to use"</pre>
#Hosts are then configured to boot via PXE boot by going into the BIOS. Make sure PXE boot is the FIRST option, NOT the hard disk, or things won’t work.
#Configure your ‘master’ pc for the first image. Probably a good idea to run ‘[http://support.microsoft.com/kb/302577 sysprep]’ prior to imaging, but not necessary. Sysprep will make your imaging life easier, if hardware is different, etc. See Microsoft.com for more details on using sysprep.

=== Mastering the FOG Web Interface ===

====The Main [[Managing FOG]] Page====
The FOG web interface is your primary management console. It is very well-documented in the pages linked below: 
The Main [[Managing FOG]] document and has a Table of Contents of its own. 
Subcategories within the Managing Fog section include the following sections:
<UL><LI>'''Understanding the FOG [[Managing_FOG#Dashboard|Dashboard]]''' 
Provides an overview of the GUI and explains the symbols used on the [[Managing_FOG#Menu Bar|Menu Bar]].</LI>
<LI>'''Managing [[Managing_FOG#Hosts|Hosts]]''' 
This section covers management tasks such as: [[Managing_FOG#Adding a new host|Adding a new host]], [[Managing_FOG#Managing Hosts|Managing Hosts]], [[Managing_FOG#Host Status|Host Status]], and [[Managing_FOG#Creating Host Groups|Creating Host Groups]].</LI>
<LI>'''Managing [[Managing_FOG#Groups|Groups of Hosts]]''' 
This section provides an [[Managing_FOG#Overview_4|Overview]] of sorting hosts into useful Groups, and provides instruction on [[Managing_FOG#Managing Groups|Managing Groups]].</LI>
<LI>'''Defining and Managing [[Managing_FOG#Images|Images]]''' 
Defines types of images: Single Partition | Multiple Partition - Single Disk | Multiple Partition - All Disks | Raw Image 
Also describes [[Managing_FOG#Creating_Images_Objects|Creating]], [[Managing_FOG#Modifying_Image_Objects|Modifying Image Objects]], and [[Managing_FOG#Adding_Existing_Image_Objects|Adding Images to Existing Objects]].</LI>
<LI>'''[[Managing_FOG#Storage_Management|Storage Management]] - adding additional Storage Nodes''' 
This section introduces the [[Managing_FOG#Overview_6|concept of Storage Nodes]], which provide scalability to FOG with the ability to "share the load of computers being imaged." 
Also covered are [[Managing_FOG#Adding_a_Storage_Node|Adding Storage Nodes]], Monitoring [[Managing_FOG#Monitoring_The_Master_Node|Image Replication]] between nodes, and Understanding the [[Managing_FOG#Master_Node_Status|role of the "Master Node"]] in a group. 
In addition, this section details the necessary steps to [[Managing_FOG#Including_multiple_PXE_.2F_TFTP_servers|include PXE and TFTP Services]] for a node located on a remote network segment.</LI>
<LI>'''Defining types of [[Managing_FOG#Users|Administrative FOG Users]]''' 
The difference between a regular FOG user and a [[Managing_FOG#Overview_7|Mobile user]] 
Also covered are [[Managing_FOG#Creating_Accounts|Creating]] and [[Managing_FOG#Modifying_Users|Modifying]] FOG user accounts</LI></UL>

====FOG [[Managing_FOG#Tasks|Tasks]]====
This is a major section of FOG Management because all day-to-day client management is initiated within the FOG Tasks section. 
The [[Managing_FOG#Overview_8|Overview Section]] provides a quick list of tasks available within FOG. 
[[Managing_FOG#General_Tasks|General Tasks]] - Basic Imaging Tasks:
::Uploading an image (includes video tutorial) Deploying an image Multicasting 
[[Managing_FOG#Advanced_Tasks|Advanced Tasks]] - Describes tasks other than imaging:
::Debug Upload - Unicast (Debug) Send - Unicast (Debug) Send - Unicast (Without Snapins) Deploy All Snapins Deploy Single Snapin Memory Test Wake Up Fast Wipe Normal Wipe Full Wipe Disk Surface Test File Recovery Virus Scan Hardware Inventory

====Delayed Tasks, or [[Managing_FOG#Scheduling|Scheduling Tasks]] in the future====
Describes advanced settings available for scheduling tasks including Shutdown after Execution, [[Managing_FOG#Single_Execution_Scheduling|Single Task]] scheduling, and [[Managing_FOG#Cron_Style_Task_Scheduling|setting a CRON-Style Task]].

====[[Managing_FOG#Printers|Adding Printers]] to FOG====
How to add printers to FOG. This allows the [[Managing_FOG#Printer_Manager|FOG Service to manage printers]] on FOG Clients

=== FOG Plugins ===
Plugins enhance FOG's functionality.
<UL><LI>The Capone plugin allows FOG to recognize similar hardware platforms and push your specified image to them with minimal (or no) interaction.</LI>
</UL>
See [[Plugins]] to activate and manage plugins.

===The [[Managing_FOG#The_FOG_Client_Service|FOG Client Service]]===
A service that runs on client computers allowing FOG to better manage them. Provides AD Integration, the ability to change a Hostname, Green Power management, Snap-in installation, User tracking, Printer Management, and more. See the [[Managing_FOG#Overview_10|Overview]] for a more complete list. 
The FOG client can be partially or fully-enabled by [[Managing_FOG#Module_specific_configuration_settings|modifying the ini file.]] 

===[[Managing_FOG#Installation|Installing]] the FOG Client===
A typical client installation, Silent installation, and a video tutorial.

===Advanced Description of [[Managing_FOG#Functions_and_Operation|FOG Services]]===
More detail on: 
::Auto Log Out Hostname Changer Host Register Task Reboot Directory Cleaner Display Manager Green FOG Snapin Client User Tracker User Cleanup Printer Manager Client Updater

===[[Managing_FOG#Keeping_Clients_up_to_date|Updating]] the FOG Client===
How to update the FOG client.

===The [[Managing_FOG#FOG_Tray|FOG Tray]]===
Describes the Windows application that runs in the taskbar

===[[Managing_FOG#Troubleshooting|Troubleshooting]] the FOG Client===
Log file location

===Snap-ins===
A FOG [[Managing_FOG#Snap-ins|Snap-in]] is anything that can be run on a Windows client. This can be ''just about anything'', including: installing applications like Firefox or Microsoft Office, adding an icon or shortcut to the desktop, or tweaking a registry key. This section covers [[Managing_FOG#Creating_a_Snapin_.2F_Overview|Creating a Snap-in]], adjusting the FOG server to handle snap-ins [[Managing_FOG#Preparing_the_FOG_Server|larger than 2MB]], [[Managing_FOG#Uploading_the_Snapin|Uploading the Snap-in]] into the FOG system, and [[Managing_FOG#Linking_the_Snapin_to_Hosts|Linking]] the Snap-in to hosts.

== Troubleshooting / Advanced Installations ==

=== Troubleshooting ===
This section is intended to bring together the most common issues from the [https://sourceforge.net/projects/freeghost/forums/forum/730843 Installation Problems] forums. The wiki format allows formatting and revision that isn't currently available in the SourceForge forums.
==== [[Knowledge Base]]====
Many pages and tips on diagnosing network, installation, and general troubleshooting steps.
====[[Password Central]]====
A single resource to explain all passwords necessary for FOG in all its various configurations
====[[Troubleshooting an image push to a client]]====
====[[Troubleshooting an image upload]]====
====[[Troubleshooting Driver Issues]]====
====[[Speeding up the Graphical User Interface]]====
====[[Bottleneck]] / Imaging Speed Issues====

===Advanced Installations===
==== Separate TFTP and DHCP Server ====

In this setup, the TFTP server and the DHCP server are hosted on a separate server. The TFTP server holds the PXE boot files including the Linux Kernel, boot file system image, and pxe config files. The DHCP server is the server that assigns the clients with IP addresses and network connection information.

Click here for detailed steps: 
[[Separate TFTP and DHCP Server]]

==== Additional TFTP / DHCP Server on separate subnet ====
This setup allows FOG to manage systems at a remote network location by installing the necessary services to allow clients to PXE boot to a Storage Node: 
[[Multiple_TFTP_servers|Including multiple PXE / TFTP servers]]

==== Separate NFS Server ====
No Content yet.

==== Change NFS location ====

This is '''not about a seperate NFS server''' in general, but about how to '''change the local storage directory''' and export it correctly.

See [[Change NFS location]] for more.

==== Other Advanced Topics ====

*[[Building a Custom Kernel]]
*[[Creating Custom FOG Service Modules]]
*[[Editing the ramdisk/init file]]

== Appendix ==
=== Preparing a Client for Cloning ===
FOG's strength can be better harnessed if some time and work is put into preparing a master image that fits the needs of your environment. 
This section covers client preparation steps that will save you time and headaches like:
::Setting a [[Client_Setup#Set_up_Default_Profile|Default User Profile]] Installing Windows Updates Pre-Installing the [[Client_Setup#Final_Steps_Before_Imaging_.2F_Before_Sysprep|FOG service]], etc. 
It also covers more advanced ideas that are guaranteed to ''cause'' headaches, like:
::Sysprep, [[Client_Setup#Hardware-Independent_Images_-_Understand_HAL|Hardware-Independent Images (HAL)]], and Driver integration. 
Read more about ''[[Client Setup]]''

For Microsoft sysprep information, see this page:
http://vernalex.com/guides/sysprep/video.shtml

===Other Resources===
FOG install HOWTO:
http://www.howtoforge.com/installing-fog-computer-imaging-solution-on-fedora8

FOG sourceforge page:
http://freeghost.sf.net/

Deployment Forum at Edugeek contains many Fog related threads
http://www.edugeek.net/forums/o-s-deployment/

== About the Developers ==

=== Chuck Syperski ===

Chuck Syperski is the lead software developer for FOG computer imaging solution. He is a software developer and network integration specialist for a public school district outside of Chicago, IL. Chuck Syperski has a Bachelor of Science in Computer Science from the University of Illinois. He specializes in Java, jsp, jsf, objective C, C, C++, C#, perl and php. You can contact Chuck Syperski directly via sourceforge as the following link:

http://sourceforge.net/users/microleaks/

=== Jian Zhang ===

No content

Imaging Windows 2008

2011-12-27T21:26:05Z

Jzhang88: Reverted edits by User 7587e06d357028b (talk) to last revision by Emcclure

Yes, you just need to set the Operating System to "Windows XP" in the OS dropdown and Image Type is "Multi Partition Image-All Disks (Not-Resizable)" selection must required while creating a new image from taking a image of a server. I have been tested on Dell PowerEdge 1950 with 3 drives (SAS, SCSI, with RAID-0, RAID-1 and RAID-5, OS- Windows 2008 R2 of Standard and Enterprise versions. (Tested by Suresh. K, Toronto, ON)

I ran some tests with Windows 2008 R2 SP1 created on an Optiplex 755. After patching the image and installing the FOG client I sysprepped the machine and uploaded the image 3 different times to the FOG server with 3 different configurations, 2 of which I have verified work. The 3 configurations are as follows:

2k8R2 setup with no system partition, Windows 7 Host OS setup with multiple partition in FOG - verified working

2k8R2 setup with a 100MB system partition on install setup in FOG as Windows 7 host OS with a single partition (resizeable) - verified working

2k8R2 setup with a 100MB system partition on install, setup in FOG as Windows XP host OS with multiple partition - error cannot have partition outside disk (will test again w/o system partition)

2k8R2 setup w/no 100MB system partition on install, setup in FOG as Windows XP host OS w/multiple partition - verified working

These were all tested on a ESXi 5.0 server. To make these work I had to setup each VM to use an IDE drive, not SCSI. I noticed that when using SCSI, FOG could not find the hard drive.
(Tested by Eric M., Beaverton, OR)

Build FOG file system with BuildRoot

2011-10-20T18:56:56Z

Jzhang88: /* build FOG file system */

== Ubuntu Desktop 11.10 ==

=== Ubuntu update ===

sudo apt-get update
sudo apt-get upgrade

=== install all essential package ===

sudo apt-get install build-essential subversion libqt4-dev bison flex gettext texinfo zlib1g-dev uuid-dev

=== Download the FOG source ===

cd ~/Desktop
mkdir svn
cd svn
svn checkout https://freeghost.svn.sourceforge.net/svnroot/freeghost/trunk

=== Download Buildroot ===

cd ..
wget http://buildroot.uclibc.org/downloads/buildroot-2011.08.tar.gz
tar xvfz buildroot-2011.08.tar.gz

=== Copy source to Buildroot ===

cp -rf svn/trunk/src/buildroot/* buildroot-2011.08/
cd buildroot-2011.08
mv fog.buildroot.config .config

=== build FOG file system ===
make xconfig
make source
make
gzip -9 < output/images/rootfs.ext2 > init.gz

copy init.gz to your FOG server /tftpboot/fog/images/init.gz

Installation on Fedora 8

2011-04-07T23:07:28Z

Jzhang88:

== Fedora 8 ==

=== Overview ===

* Note * Please understand that this tutorial will have you destroy all data on your hard disk.

'''Fedora''' is a Free Linux based operating system. This installation guide assumes that you have a basic understanding of the Linux command line environment, with using commands like ls, cp, mkdir.

If you wish to use a large storage device to store your images, like a raid array or separate hard disk, it should be mounted during installation as /images.

=== Known Issues ===

The FOG installer will only work cleanly on English versions of Fedora. (Fixed with version 0.13 of FOG!)

After you are done installing FOG you are going to need to update / edit a few settings in Fedora before the server is fully working and usable. Please see the links below for configuration changes that will need to take place.

*TFTP password issues [http://www.fogproject.org/wiki/images/c/cc/TFTP_password_issues.png]
*Storage group password issues [http://www.fogproject.org/wiki/images/8/83/Storage_node_password_issues.png]
*PXE boot menu password issues [http://www.fogproject.org/wiki/images/2/2c/PXE_boot_menu_password_issues.png]

=== Installing Fedora ===

The first thing to do is download and burn an ISO image of Fedora 8 or later from http://fedoraproject.org/. You may use either the 32 or 64 bit versions, both have been reported to work without issue.

Next boot off the CD / DVD you just created to start the Fedora installation process.
(We do not recommend that you attempt to install the OS that will be running FOG in a VM environment, as many users have reported performance related issues!)

You should see a screen similar to the pictured below, select: '''Install or Upgrade an existing System''' and press '''enter.'''

[[Image:Installf1.jpg]]

You will then be prompted if you would like to test the installation media, choose: '''Skip''' and press enter.

If you run into problems with your installation you can start the installation process over and run the media test to check for a bad burn.

[[Image:Installf2.jpg]]

Now the graphical portion of the installation will begin. At the welcome screen, press: '''Next.'''

Next you will be prompted for the installation language, choose you appropriate language and press: '''Next.'''

You will now be asked about disk partitioning. Select Remove all partition on the selected drives and create default layout, then click: '''Next.''' If you have a large disk or storage array this is the point where you would manually partition the drive and mount that disk/array as /images.

[[Image:Installf3.jpg]]

You will now be asked about network addressing, select the network device you would like to use by putting an check in the box next to the device name then, click on the edit button.

Assign the network device a IPv4 address with subnet mask and disable IPv6 support, then click '''OK.'''

Enter a DNS server and gateway address along with a hostname, then click: '''Next.'''

[[Image:Installf4.jpg]]

Next you will be prompted about you timezone information, select your timezone and click: '''Next.'''

The next screen will prompt you to create a root password, enter a password in the textbox and confirm, then press: '''Next.''' Remember this password you will need it later.

The next screen will prompt you to select the software groups you would like to install, uncheck '''Office and Productivity''' and then click: '''Next.'''

[[Image:Installf5.jpg]]

Then on the next screen click Next to start the installation. This step will take some time, so please be patient. When installation is complete, remove all disks from the CD/DVD drive and click reboot to restart the computer.

=== Selecting First Boot Settings ===

The first time Fedora boots it will load a setup wizard, which allows you select how you would like Fedora to operate. These options have changed in later versions of Fedora, so it options for SELinux and Firewall are not present that will have to be configured after login.

At the first boot welcome screen, click: '''Forward.'''

[[Image:Installf6.jpg]]

The next screen will ask you to accept the license agreement, do so and click: '''Forward.'''

The next screen is about the firewall, change the firewall to: '''Disabled''' and click: '''Forward.'''

[[Image:Installf7.jpg]]

The next screen will ask you about SELinux, set SELinux Setting to: '''Disabled''' and click: '''Forward.'''

[[Image:Installf8.jpg]]

The next screen will prompt you for the date and time settings, click: '''Forward.'''

The next screen will ask if you would like to send your hardware profile to Fedora select an option and click: '''Forward.'''

You will now be prompted to create a user, create a regular user that can be used after the FOG installation process. For the installation of FOG we will use the root user we created earlier in the installation process. You can proceed by clicking: '''Forward.'''

The first boot wizard is now complete and you will be prompted to restart your computer.

=== Setting up FOG ===

[http://freeghost.sourceforge.net/videotutorials/InstallFog.swf.html Video Tutorial]

(health warning: this flash video consumed all 1.5GB of my physical (ram) and virtual (swap) memory while it played, when it was all used up, the video crashed)

If you are running Fedora 9 +, you will need to disable SELinux and IPTables '''before''' installing FOG.

Your system is now ready to login to and install the FOG application suite.

Log into Fedora using the '''root''' username and password you created during installation.

Now we must download the FOG package from sourceforge. To do this click on
Applications -> Internet -> Firefox Web Browser
and enter the URL http://www.sf.net/projects/freeghost.

Then click on the '''Download''' link.

Then click on the latest release to start the download and save the package to the '''/opt''' directory. It should be named something like '''fog_x.xx.tar.gz'''

Open a terminal
Applications -> System Tools -> Terminal
and type:

cd /opt
tar -xvzf fog*
cd fog*
cd bin
./installfog.sh

You will be prompted for the Linux distro you are installing, enter '''1''' and press '''enter'''.

You will be prompted for the installation mode, either N (Normal Server) or S(Storage Server). If you are not sure which option to select, use N for Normal Installation. (Version 0.24 and up)

The installer will ask you for the IP address of the server, then press '''enter'''.

The installer will ask if you would like to enter a router address for DHCP, if you would like to press '''y''' and press '''enter''', then enter the address, then press '''enter'''.

The installer will ask if you would like to enter a DNS address for DHCP and the boot image, if you would like to press '''y''' and press '''enter''', then enter the address, then press '''enter'''.

You would then be prompted if you would like to change the default interface from eth0, if you would like press '''y''', press '''enter''' and add the interface (if you are unsure, select '''n''').

[[Image:Installf9.jpg]]

After the installation has completed open Firefox again and enter the URL: http://[youripaddress]/fog/management. You will then be prompted to install the database schema. Click on the '''Install/Update Now''' button.

[[Image:Installf10.jpg]]

When the schema is up to date, attempt to go to the URL: http://[youripaddress]/fog/management again. This time you should be prompted to login

username: '''fog'''
password: '''password'''.

[[Image:Installf11.jpg]]

=== Setting up Wake On Lan ===

If you would like to use wake on lan with FOG, you will have to run the following commands as root:

visudo

Scroll to the line that says

Defaults requiretty

Press '''i''' to enter insert mode. Change the line to:

# Defaults requiretty

Hit ESC to exit insert mode. Now type:

''':wq'''

and press the enter key.

=== Testing your installation ===

After login, click on the '''Hosts''' button (single computer monitor).

Then click on the '''Add New Host''' button. Enter at least a MAC address (seperated by :) and a hostname and click the '''Add''' button.

Now click on the '''Tasks''' button (the star).

Then click on '''List All Hosts''' and find the host you just created and click on the '''Advanced''' button.

Now under Advanced Actions click on '''Memtest86+''' and confirm that you would like to start the task.

Now click on '''Active Tasks''' and you should see the task that you just created listed.

Lastly, start the client computer that you created a task for and ensure that in BIOS, PXE boot has the highest boot priority. If everything worked correctly, you should see memtest86+ load.

=== Notes ===

<ul>
<li>Be sure to assign a STATIC ip address to your PC or FOG won’t work correctly.</li>
<li>Be sure to uncheck ‘firewall, selinux’ when creating the initial system. This will prevent problems later in the install.</li>
<li>Also your computer needs to be working and ‘internet’ functional prior to running the FOG install. FOG goes out to the internet to get the packages necessary for installation. It is a good idea to update your system PRIOR to installing FOG, via the ‘yum update’ command.</li>
<li>Please be aware of the following prior to reboot following the installation: FOG installs a DHCP server, so if you have another DHCP server, it will conflict with it. Probably a good idea to put the FOG server on a dedicated ‘lab’ network w/o a dhcp server, or that you disable FOG's DHCP server. Also it is CRITICAL that you type in the ‘correct’ ip address for the FOG server, probably the IP that you chose for the initial install.</li>
</ul>

PXE error code

2009-06-29T17:50:08Z

Jzhang88:

<pre>
What Are The PXE Error Codes?

Article: 138

Applies to: All releases

Init/Boot/Loader Codes
• PXE-E00 Could not find enough free base memory. PXE BaseCode and UNDI runtime modules are copied from FLASH or upper memory into the top of free base memory between 480K (78000h) and 640K (A0000h). This memory must be zero filled by the system BIOS. If this memory is not zero filled, the relocation code in the PXE ROMs will assume that this memory is being used by the system BIOS or other boot ROMs.
• PXE-E01: PCI Vendor and Device IDs do not match! This message should never be seen in a production BIOS. When the system BIOS initializes a PCI option ROM, it is supposed to pass the PCI bus/device/function numbers in the AX register. If the PCI device defined in the AX register does not match the UNDI device, this error is displayed.
• PXE-E04: Error reading PCI configuration space. This message is displayed if any of the PCI BIOS calls made to read the PCI configuration space return an error code. This should not happen with a production BIOS and properly operating hardware.
• PXE-E05: EEPROM checksum error. This message is displayed if the NIC EEPROM contents have been corrupted. This can happen if the system is reset or powered down when the NIC EEPROM is being reprogrammed. If this message is displayed the PXE ROM will not boot.
• PXE-E06: Option ROM requires DDIM support. This message should not be seen in a production BIOS. PCI option ROMs must always be installed as DDIM option ROMs (they must be installed into read/write upper memory).
• PXE-E07: PCI BIOS calls not supported. This message should not be seen in a production BIOS. PCI BIOS must have PCI BIOS services.
• PXE-E08: Unexpected API error. API: xxxxh Status: xxxxh. This message is displayed if a PXE API returns a status code that is not expected by the runtime loader.
• PXE-E09: Unexpected UNDI loader error. Status: xxxxh. This message is displayed if the UNDI runtime loader returns an unexpected status code.

ARP Codes
• PXE-E11: ARP timeout. The PXE ROM will retry the ARP request four times, if it does not get any valid ARP replies, this message is displayed. There are several possible causes:
• Setting the DHCP Class Identifier (option 60) on the DHCP server and installing the proxyDHCP on a separate machine.
• Using routers that do not respond to ARP requests.
• A situation that may lead to this error is with ProLiant BL p-Class blade servers connected to a ProLiant BL p-Class GbE Interconnect Switch with Port Trunking (802.3ad) enabled uplinked to another switch where port trunking is not enabled, and perhaps instead, the customer inadvertently enabled VLAN trunking.

The GbE switch options are based on IEEE terminology which is sometimes different than Cisco terminology. The Port Trunking option on the GbE switch is meant for the bonding together of multiple ports (802.3ad) for faster throughput and reliability. The Cisco term for this is etherchannel. The term "trunking" on a Cisco switch means vlan tagging and is often confused with IEEE port trunking. The two are not the same and cannot be used on one switch without the same option being enabled on both switches.

To resolve this issue, correct the port trunk configuration on both switches.
• After certain deployment operations, the server's MAC address might be set to 0.

To resolve this issue, apply the SoftPaq for Network Adapter Boot Code and PXE Firmware refered to in the Knowledge Base article Minimum Firmware Requirements For Target Servers (Article 200).

BIOS and BIS Codes
• PXE-E20: BIOS extended memory copy error. AH == nn This message is displayed if the BIOS extended memory copy service returns an error. This should not happen on a production BIOS. nn is the BIOS error code returned by the BIOS extended memory copy service (Int 15h, AH = 87h).
• PXE-E21: BIS integrity check failed. This message is displayed if the BIS image in extended memory has been corrupted.
• PXE-E22: BIS image/credential validation failed. The downloaded image and credential do not match the client key.
• PXE-E23: BIS initialization failed. BIS could not be initialized. No more data is available.
• PXE-E24: BIS shutdown failed. BIS could not be shutdown. No more data is available.
• PXE-E25: BIS get boot object authorization check flag failed. Could not determine if BIS is enabled/disabled.
• PXE-E26: BIS free memory failed. Could not release BIS allocated memory.
• PXE-E27: BIS get signature information failed. Required BIS credential type information could not be determined.
• PXE-E28: BIS bad entry structure checksum. BIS entry structure in the SM BIOS table is invalid.

TFTP/MTFTP Codes
• PXE-E32: TFTP open timeout. The PXE client was able to get a DHCP address and a boot file name, but timed out when attempting to download the boot file using TFTP or MTFTP. To resolve this issue, check each of the following network configuration items:
• This message is sometimes displayed, and the operation is retried, allowing for a successful download of the boot image. The message Transferring control to DOS boot diskette image... indicates that the boot file was successfully downloaded and the PXE boot has succeeded. In this case, no action is needed to correct the problem.
• By default, the Altiris PXE server is configured to use multicast TFTP. If multicast is disabled by the switches in the environment, either enable multicast (ports 1758 and 1759) or change the configuration of the PXE server to use regular TFTP (port 69).
• Verify that the Altiris MTFTP Service is running on the Deployment Server.
• PXE-E35: TFTP read timeout. Next TFTP data packet was not received.
• PXE-E36: Error received from TFTP server. A TFTP error packet was received from the TFTP server.
• PXE-E38: TFTP cannot open connection. A hardware error occurred when trying to send the TFTP open packet out.
• PXE-E39: TFTP cannot read from connection. A hardware error occurred when trying to send a TFTP acknowledge packet out.
• PXE-E3A: TFTP too many packages. This message can mean one of two things:
• You are trying to download a file using TFTP that is larger than the allocated buffer.
• You started downloading a file as a slave client using MTFTP and the file increased in size when you became the master client.
• PXE-E3B: TFTP error - File not found. The requested file was not found on the TFTP server.
• PXE-E3C: TFTP error - Access violation. The request file was found on the TFTP server. The TFTP service does not have enough access rights to open/read the file.
• PXE-E3F: TFTP packet size is invalid. The TFTP packet received is larger than 1456 bytes.

BOOTP/DHCP Codes
• PXE-E51: No DHCP or proxyDHCP offers were received. The client did not receive any valid DHCP, BOOTP or proxyDHCP offers. To resolve this issue, check each of the following network configuration items:
• DHCP services are not available on the network to which the PXE-enabled NIC is connected.
• A DHCP proxy or IP helper address is not configured for the subnet on which the PXE client is connected.
• The switch port connected to the PXE NIC is running Spanning Tree Protocol, EtherChannel Protocol, or Port Aggregation Protocol and is thus not activated immediately when a link is detected. This forces the DHCP request from the PXE client to timeout.
• DHCP is available on the network, but PXE is not.
• The network cable is not attached to the PXE-enabled NIC on the target server.
• PXE-E52: proxyDHCP offers were received. No DHCP offers were received. The client did not receive any valid DHCP or BOOTP offers. The client did receive at least one valid proxyDHCP offer.
• PXE-E53: No boot filename received. The client received at least one valid DHCP/BOOTP offer, but does not have a boot filename to download. There are several possible causes:
• The DHCP Server and the PXE Server were located on the same server, but one of them was moved to a different server. This would result in an incorrect PXE Server configuration.

To resolve this issue, reinstall the PXE Server component of the Altiris Deployment Solution.
• The DHCP relay agent, either a Proxy DHCP Server or a switch configured with helper addresses, is not configured correctly. For example, if DHCP and PXE are on separate servers, the DHCP relay agent needs to have both addresses in its configuration.

To resolve this issue, correct the DHCP relay agent configuration.
• If the Microsoft DHCP service is installed on the PXE server, but is disabled or unconfigured, Altiris PXE Setup configures PXE to work with the local DHCP service (even if the DHCP service is disabled). This causes the PXE server to not respond to PXE clients that get a DHCP address from DHCP services running elsewhere on the network.

To resolve this issue, remove Microsoft DHCP services from the PXE server and reinstall the PXE Server component of the Altiris Deployment Solution.
• PXE-E55: proxyDHCP service did not reply to request on port 4011. The client issued a proxyDHCP request to the DHCP server on port 4011 and did not receive a reply.

UNDI Codes
• PXE-E60: Invalid UNDI API function number. An API being used by the BaseCode is not implemented in the UNDI ROM.
• PXE-E61: Media test failed, check cable. Most likely the cable is not plugged in or connected. Could be a bad cable, NIC or connection.
• PXE-E63: Error while initializing the NIC. An error occurred while trying to initialize the NIC hardware. Try another NIC.
• PXE-E64: Error while initializing the PHY. An error occurred while trying to initialize the PHY hardware. Try another NIC.
• PXE-E65: Error while reading the configuration data. An error occurred while reading the NIC configuration data. Try another NIC.
• PXE-E66: Error while reading the initialization data. An error occurred while reading the NIC initialization data. Try another NIC.
• PXE-E67: Invalid MAC address. The MAC address stored in this NIC is invalid. Try another NIC.
• PXE-E68: Invalid EEPROM checksum. The EEPROM checksum is invalid. The contents of the EEPROM have been corrupted. Try another NIC.
• PXE-E69: Error while setting interrupt. The interrupt hardware could not be configured. Try another NIC.

Bootstrap and Discovery Codes
• PXE-E74: Bad or missing PXE menu and/or prompt information. PXE tags were detected but the boot menu and/or boot prompt tags were not found/valid.
• PXE-E76: Bad or missing multicast discovery address. Multicast discovery is enabled but the multicast discovery address tag is missing.
• PXE-E77: Bad or missing discovery server list. Multicast and broadcast discovery are both disabled, or use server list is enabled, and the server list tag was not found/valid.
• PXE-E78: Could not locate boot server. A valid boot server reply was not received by the client. Several possible causes are
• The PXE image is not correct for the target because a job that contains a task that is to run in a specific automation environment cannot be run on the target.
• The Virtualization Technology BIOS option may not be set on an Intel-based server running VMware ESX and a Windows 64-bit guest is being deploying to one of its virtual machines.
• PXE-E79: NBP is too big to fit in free base memory. The NBP is larger than the amount of free base memory.
• PXE-E7A: Client could not locate a secure server. This message is displayed when the client did not receive any security information from the boot server and BIS is enabled on the client.
• PXE-E7B: Missing MTFTP server IP address. This message is displayed when the ROM did not receive any PXE discovery tags or proxyDHCP offers and the DHCP SIADDR field is set to 0.0.0.0.

Miscellaneous Codes
• PXE-EA0: Network boot canceled by keystroke. User pressed Esc or Ctrl-C during DHCP/Discovery/TFTP.

BaseCode/UNDI Loader Codes
• PXE-EC1: BaseCode ROM ID structure was not found. UNDI boot module could not find the BaseCode ROM ID structure. If there is a BaseCode ROM image in the system, it has probably been corrupted.
• PXE-EC3: BaseCode ROM ID structure is invalid. The BaseCode ROM ID structure is invalid. The BaseCode ROM image has probably been corrupted.
• PXE-EC4: UNDI ROM ID structure was not found. The BaseCode loader module could not locate the UNDI ROM ID structure.
• PXE-EC5: UNDI ROM ID structure is invalid. The UNDI ROM image has probably been corrupted.
• PXE-EC6: UNDI driver image is invalid. The UNDI ROM image has probably been corrupted.
• PXE-EC8: !PXE structure was not found in UNDI driver code segment. The UNDI ROM image has probably been corrupted, or has not been initialized by the BIOS. This error is most often caused by one of three things:
• A .NIC image was programmed into a BIOS when a .LOM image should have been used.
• The memory allocated by the POST Memory Manager ($PMM) during PXE option ROM initialization has been corrupted or erased before PXE option ROM boot.
• The UNDI_Loader structure was not properly initialized during option ROM initialization.
• PXE-EC9: PXENV+ structure was not found in UNDI driver code segment. The UNDI ROM image has probably been corrupted, or has not been initialized by the BIOS. This error is most often caused by one of three things:
• A .NIC image was programmed into a BIOS when a .LOM image should have been used.
• The memory allocated by the POST Memory Manager ($PMM) during PXE option ROM initialization has been corrupted or erased before PXE option ROM boot.
• The UNDI_Loader structure was not properly initialized during option ROM initialization.

page source: http://h18013.www1.hp.com/products/servers/management/rdp/knowledgebase/00000138.html
</pre>

Multicasting over a router

2009-06-29T12:56:36Z

Jzhang88:

In order to multicast over a router/VLAN some configuration to your routers may be required. Below are a few vendor specific examples:

Cisco 2800 Series:

!
interface FastEthernet0/0
ip address 1.1.x.x 255.255.255.0
ip helper-address 10.10.10.2
ip pim sparse-dense-mode
duplex auto
speed auto
!
interface FastEthernet0/1
ip address 10.10.10.11 255.255.255.0
ip pim sparse-dense-mode
duplex auto
speed auto
!

more information
http://www.cisco.com/en/US/tech/tk828/technologies_tech_note09186a0080094821.shtml

Is PC compatible with FOG kernel

2009-04-10T03:09:02Z

Jzhang88:

<pre>
Boot up PC in debug mode

to view hard drive partition
#fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 20349 156280288+ 7 HPFS/NTFS

Partition table entries are not disk order

to view NIC settings
#ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:22:33:44:55
inet addr:192.168.1.252 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
....

lo Link encap:Local Loopback
int addr:127.0.0.1 Mask:255.0.0.0
....

If you do not see any /dev/??? or eth0 then you can try FOG Kernel Updates(require internet access).
WebUI > Other Information > Kernel Updates >Published Kernels
or
Building your own Custom Kernel
http://www.fogproject.org/wiki/index.php?title=FOGUserGuide&Itemid=51#Building_a_Custom_Kernel
</pre>

Kernel Parameters

2009-04-03T01:57:24Z

Jzhang88:

'''/usr/src/linux/Documentation/kernel-parameters.txt'''

<pre>
Kernel Parameters
~~~~~~~~~~~~~~~~~

The following is a consolidated list of the kernel parameters as implemented
(mostly) by the __setup() macro and sorted into English Dictionary order
(defined as ignoring all punctuation and sorting digits before letters in a
case insensitive manner), and with descriptions where known.

Module parameters for loadable modules are specified only as the
parameter name with optional '=' and value as appropriate, such as:

modprobe usbcore blinkenlights=1

Module parameters for modules that are built into the kernel image
are specified on the kernel command line with the module name plus
'.' plus parameter name, with '=' and value if appropriate, such as:

usbcore.blinkenlights=1

This document may not be entirely up to date and comprehensive. The command
"modinfo -p ${modulename}" shows a current list of all parameters of a loadable
module. Loadable modules, after being loaded into the running kernel, also
reveal their parameters in /sys/module/${modulename}/parameters/. Some of these
parameters may be changed at runtime by the command
"echo -n ${value} > /sys/module/${modulename}/parameters/${parm}".

The parameters listed below are only valid if certain kernel build options were
enabled and if respective hardware is present. The text in square brackets at
the beginning of each description states the restrictions within which a
parameter is applicable:

ACPI ACPI support is enabled.
AGP AGP (Accelerated Graphics Port) is enabled.
ALSA ALSA sound support is enabled.
APIC APIC support is enabled.
APM Advanced Power Management support is enabled.
AVR32 AVR32 architecture is enabled.
AX25 Appropriate AX.25 support is enabled.
BLACKFIN Blackfin architecture is enabled.
DRM Direct Rendering Management support is enabled.
EDD BIOS Enhanced Disk Drive Services (EDD) is enabled
EFI EFI Partitioning (GPT) is enabled
EIDE EIDE/ATAPI support is enabled.
FB The frame buffer device is enabled.
HW Appropriate hardware is enabled.
IA-64 IA-64 architecture is enabled.
IOSCHED More than one I/O scheduler is enabled.
IP_PNP IP DHCP, BOOTP, or RARP is enabled.
ISAPNP ISA PnP code is enabled.
ISDN Appropriate ISDN support is enabled.
JOY Appropriate joystick support is enabled.
LIBATA Libata driver is enabled
LP Printer support is enabled.
LOOP Loopback device support is enabled.
M68k M68k architecture is enabled.
These options have more detailed description inside of
Documentation/m68k/kernel-options.txt.
MCA MCA bus support is enabled.
MDA MDA console support is enabled.
MOUSE Appropriate mouse support is enabled.
MSI Message Signaled Interrupts (PCI).
MTD MTD (Memory Technology Device) support is enabled.
NET Appropriate network support is enabled.
NUMA NUMA support is enabled.
GENERIC_TIME The generic timeofday code is enabled.
NFS Appropriate NFS support is enabled.
OSS OSS sound support is enabled.
PV_OPS A paravirtualized kernel is enabled.
PARIDE The ParIDE (parallel port IDE) subsystem is enabled.
PARISC The PA-RISC architecture is enabled.
PCI PCI bus support is enabled.
PCIE PCI Express support is enabled.
PCMCIA The PCMCIA subsystem is enabled.
PNP Plug & Play support is enabled.
PPC PowerPC architecture is enabled.
PPT Parallel port support is enabled.
PS2 Appropriate PS/2 support is enabled.
RAM RAM disk support is enabled.
ROOTPLUG The example Root Plug LSM is enabled.
S390 S390 architecture is enabled.
SCSI Appropriate SCSI support is enabled.
A lot of drivers has their options described inside of
Documentation/scsi/.
SECURITY Different security models are enabled.
SELINUX SELinux support is enabled.
SERIAL Serial support is enabled.
SH SuperH architecture is enabled.
SMP The kernel is an SMP kernel.
SPARC Sparc architecture is enabled.
SWSUSP Software suspend (hibernation) is enabled.
SUSPEND System suspend states are enabled.
FTRACE Function tracing enabled.
TS Appropriate touchscreen support is enabled.
UMS USB Mass Storage support is enabled.
USB USB support is enabled.
USBHID USB Human Interface Device support is enabled.
V4L Video For Linux support is enabled.
VGA The VGA console has been enabled.
VT Virtual terminal support is enabled.
WDT Watchdog support is enabled.
XT IBM PC/XT MFM hard disk support is enabled.
X86-32 X86-32, aka i386 architecture is enabled.
X86-64 X86-64 architecture is enabled.
More X86-64 boot options can be found in
Documentation/x86/x86_64/boot-options.txt .
X86 Either 32bit or 64bit x86 (same as X86-32+X86-64)

In addition, the following text indicates that the option:

BUGS= Relates to possible processor bugs on the said processor.
KNL Is a kernel start-up parameter.
BOOT Is a boot loader parameter.

Parameters denoted with BOOT are actually interpreted by the boot
loader, and have no meaning to the kernel directly.
Do not modify the syntax of boot loader parameters without extreme
need or coordination with <Documentation/x86/boot.txt>.

There are also arch-specific kernel-parameters not documented here.
See for example <Documentation/x86/x86_64/boot-options.txt>.

Note that ALL kernel parameters listed below are CASE SENSITIVE, and that
a trailing = on the name of any parameter states that that parameter will
be entered as an environment variable, whereas its absence indicates that
it will appear as a kernel argument readable via /proc/cmdline by programs
running once the system is up.

The number of kernel parameters is not limited, but the length of the
complete command line (parameters including spaces etc.) is limited to
a fixed number of characters. This limit depends on the architecture
and is between 256 and 4096 characters. It is defined in the file
./include/asm/setup.h as COMMAND_LINE_SIZE.

acpi= [HW,ACPI,X86-64,i386]
Advanced Configuration and Power Interface
Format: { force | off | ht | strict | noirq | rsdt }
force -- enable ACPI if default was off
off -- disable ACPI if default was on
noirq -- do not use ACPI for IRQ routing
ht -- run only enough ACPI to enable Hyper Threading
strict -- Be less tolerant of platforms that are not
strictly ACPI specification compliant.
rsdt -- prefer RSDT over (default) XSDT

See also Documentation/power/pm.txt, pci=noacpi

acpi_apic_instance= [ACPI, IOAPIC]
Format: <int>
2: use 2nd APIC table, if available
1,0: use 1st APIC table
default: 0

acpi_sleep= [HW,ACPI] Sleep options
Format: { s3_bios, s3_mode, s3_beep, s4_nohwsig,
old_ordering, s4_nonvs }
See Documentation/power/video.txt for information on
s3_bios and s3_mode.
s3_beep is for debugging; it makes the PC's speaker beep
as soon as the kernel's real-mode entry point is called.
s4_nohwsig prevents ACPI hardware signature from being
used during resume from hibernation.
old_ordering causes the ACPI 1.0 ordering of the _PTS
control method, with respect to putting devices into
low power states, to be enforced (the ACPI 2.0 ordering
of _PTS is used by default).
s4_nonvs prevents the kernel from saving/restoring the
ACPI NVS memory during hibernation.

acpi_sci= [HW,ACPI] ACPI System Control Interrupt trigger mode
Format: { level | edge | high | low }

acpi_irq_balance [HW,ACPI]
ACPI will balance active IRQs
default in APIC mode

acpi_irq_nobalance [HW,ACPI]
ACPI will not move active IRQs (default)
default in PIC mode

acpi_irq_pci= [HW,ACPI] If irq_balance, clear listed IRQs for
use by PCI
Format: <irq>,<irq>...

acpi_irq_isa= [HW,ACPI] If irq_balance, mark listed IRQs used by ISA
Format: <irq>,<irq>...

acpi_no_auto_ssdt [HW,ACPI] Disable automatic loading of SSDT

acpi_os_name= [HW,ACPI] Tell ACPI BIOS the name of the OS
Format: To spoof as Windows 98: ="Microsoft Windows"

acpi_osi= [HW,ACPI] Modify list of supported OS interface strings
acpi_osi="string1" # add string1 -- only one string
acpi_osi="!string2" # remove built-in string2
acpi_osi= # disable all strings

acpi_serialize [HW,ACPI] force serialization of AML methods

acpi_skip_timer_override [HW,ACPI]
Recognize and ignore IRQ0/pin2 Interrupt Override.
For broken nForce2 BIOS resulting in XT-PIC timer.
acpi_use_timer_override [HW,ACPI]
Use timer override. For some broken Nvidia NF5 boards
that require a timer override, but don't have
HPET

acpi_backlight= [HW,ACPI]
acpi_backlight=vendor
acpi_backlight=video
If set to vendor, prefer vendor specific driver
(e.g. thinkpad_acpi, sony_acpi, etc.) instead
of the ACPI video.ko driver.

acpi_display_output= [HW,ACPI]
acpi_display_output=vendor
acpi_display_output=video
See above.

acpi.debug_layer= [HW,ACPI,ACPI_DEBUG]
acpi.debug_level= [HW,ACPI,ACPI_DEBUG]
Format: <int>
CONFIG_ACPI_DEBUG must be enabled to produce any ACPI
debug output. Bits in debug_layer correspond to a
_COMPONENT in an ACPI source file, e.g.,
#define _COMPONENT ACPI_PCI_COMPONENT
Bits in debug_level correspond to a level in
ACPI_DEBUG_PRINT statements, e.g.,
ACPI_DEBUG_PRINT((ACPI_DB_INFO, ...
The debug_level mask defaults to "info". See
Documentation/acpi/debug.txt for more information about
debug layers and levels.

Enable processor driver info messages:
acpi.debug_layer=0x20000000
Enable PCI/PCI interrupt routing info messages:
acpi.debug_layer=0x400000
Enable AML "Debug" output, i.e., stores to the Debug
object while interpreting AML:
acpi.debug_layer=0xffffffff acpi.debug_level=0x2
Enable all messages related to ACPI hardware:
acpi.debug_layer=0x2 acpi.debug_level=0xffffffff

Some values produce so much output that the system is
unusable. The "log_buf_len" parameter may be useful
if you need to capture more output.

acpi.power_nocheck= [HW,ACPI]
Format: 1/0 enable/disable the check of power state.
On some bogus BIOS the _PSC object/_STA object of
power resource can't return the correct device power
state. In such case it is unneccessary to check its
power state again in power transition.
1 : disable the power state check

acpi_pm_good [X86-32,X86-64]
Override the pmtimer bug detection: force the kernel
to assume that this machine's pmtimer latches its value
and always returns good values.

agp= [AGP]
{ off | try_unsupported }
off: disable AGP support
try_unsupported: try to drive unsupported chipsets
(may crash computer or cause data corruption)

enable_timer_pin_1 [i386,x86-64]
Enable PIN 1 of APIC timer
Can be useful to work around chipset bugs
(in particular on some ATI chipsets).
The kernel tries to set a reasonable default.

disable_timer_pin_1 [i386,x86-64]
Disable PIN 1 of APIC timer
Can be useful to work around chipset bugs.

ad1848= [HW,OSS]
Format: <io>,<irq>,<dma>,<dma2>,<type>

advansys= [HW,SCSI]
See header of drivers/scsi/advansys.c.

advwdt= [HW,WDT] Advantech WDT
Format: <iostart>,<iostop>

aedsp16= [HW,OSS] Audio Excel DSP 16
Format: <io>,<irq>,<dma>,<mss_io>,<mpu_io>,<mpu_irq>
See also header of sound/oss/aedsp16.c.

aha152x= [HW,SCSI]
See Documentation/scsi/aha152x.txt.

aha1542= [HW,SCSI]
Format: <portbase>[,<buson>,<busoff>[,<dmaspeed>]]

aic7xxx= [HW,SCSI]
See Documentation/scsi/aic7xxx.txt.

aic79xx= [HW,SCSI]
See Documentation/scsi/aic79xx.txt.

amd_iommu= [HW,X86-84]
Pass parameters to the AMD IOMMU driver in the system.
Possible values are:
isolate - enable device isolation (each device, as far
as possible, will get its own protection
domain) [default]
share - put every device behind one IOMMU into the
same protection domain
fullflush - enable flushing of IO/TLB entries when
they are unmapped. Otherwise they are
flushed before they will be reused, which
is a lot of faster

amd_iommu_size= [HW,X86-64]
Define the size of the aperture for the AMD IOMMU
driver. Possible values are:
'32M', '64M' (default), '128M', '256M', '512M', '1G'

amijoy.map= [HW,JOY] Amiga joystick support
Map of devices attached to JOY0DAT and JOY1DAT
Format: <a>,
See also Documentation/kernel/input/joystick.txt

analog.map= [HW,JOY] Analog joystick and gamepad support
Specifies type or capabilities of an analog joystick
connected to one of 16 gameports
Format: <type1>,<type2>,..<type16>

apc= [HW,SPARC]
Power management functions (SPARCstation-4/5 + deriv.)
Format: noidle
Disable APC CPU standby support. SPARCstation-Fox does
not play well with APC CPU idle - disable it if you have
APC and your system crashes randomly.

apic= [APIC,i386] Advanced Programmable Interrupt Controller
Change the output verbosity whilst booting
Format: { quiet (default) | verbose | debug }
Change the amount of debugging information output
when initialising the APIC and IO-APIC components.

apm= [APM] Advanced Power Management
See header of arch/x86/kernel/apm_32.c.

arcrimi= [HW,NET] ARCnet - "RIM I" (entirely mem-mapped) cards
Format: <io>,<irq>,<nodeID>

ataflop= [HW,M68k]

atarimouse= [HW,MOUSE] Atari Mouse

atascsi= [HW,SCSI] Atari SCSI

atkbd.extra= [HW] Enable extra LEDs and keys on IBM RapidAccess,
EzKey and similar keyboards

atkbd.reset= [HW] Reset keyboard during initialization

atkbd.set= [HW] Select keyboard code set
Format: <int> (2 = AT (default), 3 = PS/2)

atkbd.scroll= [HW] Enable scroll wheel on MS Office and similar
keyboards

atkbd.softraw= [HW] Choose between synthetic and real raw mode
Format: <bool> (0 = real, 1 = synthetic (default))

atkbd.softrepeat= [HW]
Use software keyboard repeat

autotest [IA64]

baycom_epp= [HW,AX25]
Format: <io>,<mode>

baycom_par= [HW,AX25] BayCom Parallel Port AX.25 Modem
Format: <io>,<mode>
See header of drivers/net/hamradio/baycom_par.c.

baycom_ser_fdx= [HW,AX25]
BayCom Serial Port AX.25 Modem (Full Duplex Mode)
Format: <io>,<irq>,<mode>[,<baud>]
See header of drivers/net/hamradio/baycom_ser_fdx.c.

baycom_ser_hdx= [HW,AX25]
BayCom Serial Port AX.25 Modem (Half Duplex Mode)
Format: <io>,<irq>,<mode>
See header of drivers/net/hamradio/baycom_ser_hdx.c.

boot_delay= Milliseconds to delay each printk during boot.
Values larger than 10 seconds (10000) are changed to
no delay (0).
Format: integer

bootmem_debug [KNL] Enable bootmem allocator debug messages.

bttv.card= [HW,V4L] bttv (bt848 + bt878 based grabber cards)
bttv.radio= Most important insmod options are available as
kernel args too.
bttv.pll= See Documentation/video4linux/bttv/Insmod-options
bttv.tuner= and Documentation/video4linux/bttv/CARDLIST

BusLogic= [HW,SCSI]
See drivers/scsi/BusLogic.c, comment before function
BusLogic_ParseDriverOptions().

c101= [NET] Moxa C101 synchronous serial card

cachesize= [BUGS=X86-32] Override level 2 CPU cache size detection.
Sometimes CPU hardware bugs make them report the cache
size incorrectly. The kernel will attempt work arounds
to fix known problems, but for some CPUs it is not
possible to determine what the correct size should be.
This option provides an override for these situations.

security= [SECURITY] Choose a security module to enable at boot.
If this boot parameter is not specified, only the first
security module asking for security registration will be
loaded. An invalid security module name will be treated
as if no module has been chosen.

capability.disable=
[SECURITY] Disable capabilities. This would normally
be used only if an alternative security model is to be
configured. Potentially dangerous and should only be
used if you are entirely sure of the consequences.

ccw_timeout_log [S390]
See Documentation/s390/CommonIO for details.

cgroup_disable= [KNL] Disable a particular controller
Format: {name of the controller(s) to disable}
{Currently supported controllers - "memory"}

checkreqprot [SELINUX] Set initial checkreqprot flag value.
Format: { "0" | "1" }
See security/selinux/Kconfig help text.
0 -- check protection applied by kernel (includes
any implied execute protection).
1 -- check protection requested by application.
Default value is set via a kernel config option.
Value can be changed at runtime via
/selinux/checkreqprot.

cio_ignore= [S390]
See Documentation/s390/CommonIO for details.

clock= [BUGS=X86-32, HW] gettimeofday clocksource override.
[Deprecated]
Forces specified clocksource (if available) to be used
when calculating gettimeofday(). If specified
clocksource is not available, it defaults to PIT.
Format: { pit | tsc | cyclone | pmtmr }

clocksource= [GENERIC_TIME] Override the default clocksource
Format: <string>
Override the default clocksource and use the clocksource
with the name specified.
Some clocksource names to choose from, depending on
the platform:
[all] jiffies (this is the base, fallback clocksource)
[ACPI] acpi_pm
[ARM] imx_timer1,OSTS,netx_timer,mpu_timer2,
pxa_timer,timer3,32k_counter,timer0_1
[AVR32] avr32
[X86-32] pit,hpet,tsc,vmi-timer;
scx200_hrt on Geode; cyclone on IBM x440
[MIPS] MIPS
[PARISC] cr16
[S390] tod
[SH] SuperH
[SPARC64] tick
[X86-64] hpet,tsc

clearcpuid=BITNUM [X86]
Disable CPUID feature X for the kernel. See
arch/x86/include/asm/cpufeature.h for the valid bit
numbers. Note the Linux specific bits are not necessarily
stable over kernel options, but the vendor specific
ones should be.
Also note that user programs calling CPUID directly
or using the feature without checking anything
will still see it. This just prevents it from
being used by the kernel or shown in /proc/cpuinfo.
Also note the kernel might malfunction if you disable
some critical bits.

code_bytes [IA32/X86_64] How many bytes of object code to print
in an oops report.
Range: 0 - 8192
Default: 64

hpet= [X86-32,HPET] option to control HPET usage
Format: { enable (default) | disable | force }
disable: disable HPET and use PIT instead
force: allow force enabled of undocumented chips (ICH4,
VIA, nVidia)

com20020= [HW,NET] ARCnet - COM20020 chipset
Format:
<io>[,<irq>[,<nodeID>[,<backplane>[,<ckp>[,<timeout>]]]]]

com90io= [HW,NET] ARCnet - COM90xx chipset (IO-mapped buffers)
Format: <io>[,<irq>]

com90xx= [HW,NET]
ARCnet - COM90xx chipset (memory-mapped buffers)
Format: <io>[,<irq>[,<memstart>]]

condev= [HW,S390] console device
conmode=

console= [KNL] Output console device and options.

tty<n> Use the virtual console device <n>.

ttyS<n>[,options]
ttyUSB0[,options]
Use the specified serial port. The options are of
the form "bbbbpnf", where "bbbb" is the baud rate,
"p" is parity ("n", "o", or "e"), "n" is number of
bits, and "f" is flow control ("r" for RTS or
omit it). Default is "9600n8".

See Documentation/serial-console.txt for more
information. See
Documentation/networking/netconsole.txt for an
alternative.

uart[8250],io,<addr>[,options]
uart[8250],mmio,<addr>[,options]
Start an early, polled-mode console on the 8250/16550
UART at the specified I/O port or MMIO address,
switching to the matching ttyS device later. The
options are the same as for ttyS, above.

If the device connected to the port is not a TTY but a braille
device, prepend "brl," before the device type, for instance
console=brl,ttyS0
For now, only VisioBraille is supported.

earlycon= [KNL] Output early console device and options.
uart[8250],io,<addr>[,options]
uart[8250],mmio,<addr>[,options]
Start an early, polled-mode console on the 8250/16550
UART at the specified I/O port or MMIO address.
The options are the same as for ttyS, above.

no_console_suspend
[HW] Never suspend the console
Disable suspending of consoles during suspend and
hibernate operations. Once disabled, debugging
messages can reach various consoles while the rest
of the system is being put to sleep (ie, while
debugging driver suspend/resume hooks). This may
not work reliably with all consoles, but is known
to work with serial and VGA consoles.

coredump_filter=
[KNL] Change the default value for
/proc/<pid>/coredump_filter.
See also Documentation/filesystems/proc.txt.

cpcihp_generic= [HW,PCI] Generic port I/O CompactPCI driver
Format:
<first_slot>,<last_slot>,<port>,<enum_bit>[,<debug>]

crashkernel=nn[KMG]@ss[KMG]
[KNL] Reserve a chunk of physical memory to
hold a kernel to switch to with kexec on panic.

crashkernel=range1:size1[,range2:size2,...][@offset]
[KNL] Same as above, but depends on the memory
in the running system. The syntax of range is
start-[end] where start and end are both
a memory unit (amount[KMG]). See also
Documentation/kdump/kdump.txt for a example.

cs89x0_dma= [HW,NET]
Format: <dma>

cs89x0_media= [HW,NET]
Format: { rj45 | aui | bnc }

dasd= [HW,NET]
See header of drivers/s390/block/dasd_devmap.c.

db9.dev[2|3]= [HW,JOY] Multisystem joystick support via parallel port
(one device per port)
Format: <port#>,<type>
See also Documentation/input/joystick-parport.txt

debug [KNL] Enable kernel debugging (events log level).

debug_locks_verbose=
[KNL] verbose self-tests
Format=<0|1>
Print debugging info while doing the locking API
self-tests.
We default to 0 (no extra messages), setting it to
1 will print _a lot_ more information - normally
only useful to kernel developers.

debug_objects [KNL] Enable object debugging

debugpat [X86] Enable PAT debugging

decnet.addr= [HW,NET]
Format: <area>[,<node>]
See also Documentation/networking/decnet.txt.

vt.default_blu= [VT]
Format: <blue0>,<blue1>,<blue2>,...,<blue15>
Change the default blue palette of the console.
This is a 16-member array composed of values
ranging from 0-255.

vt.default_grn= [VT]
Format: <green0>,<green1>,<green2>,...,<green15>
Change the default green palette of the console.
This is a 16-member array composed of values
ranging from 0-255.

vt.default_red= [VT]
Format: <red0>,<red1>,<red2>,...,<red15>
Change the default red palette of the console.
This is a 16-member array composed of values
ranging from 0-255.

vt.default_utf8=
[VT]
Format=<0|1>
Set system-wide default UTF-8 mode for all tty's.
Default is 1, i.e. UTF-8 mode is enabled for all
newly opened terminals.

dhash_entries= [KNL]
Set number of hash buckets for dentry cache.

digi= [HW,SERIAL]
IO parameters + enable/disable command.

digiepca= [HW,SERIAL]
See drivers/char/README.epca and
Documentation/serial/digiepca.txt.

disable_mtrr_cleanup [X86]
enable_mtrr_cleanup [X86]
The kernel tries to adjust MTRR layout from continuous
to discrete, to make X server driver able to add WB
entry later. This parameter enables/disables that.

mtrr_chunk_size=nn[KMG] [X86]
used for mtrr cleanup. It is largest continous chunk
that could hold holes aka. UC entries.

mtrr_gran_size=nn[KMG] [X86]
Used for mtrr cleanup. It is granularity of mtrr block.
Default is 1.
Large value could prevent small alignment from
using up MTRRs.

mtrr_spare_reg_nr=n [X86]
Format: <integer>
Range: 0,7 : spare reg number
Default : 1
Used for mtrr cleanup. It is spare mtrr entries number.
Set to 2 or more if your graphical card needs more.

disable_mtrr_trim [X86, Intel and AMD only]
By default the kernel will trim any uncacheable
memory out of your available memory pool based on
MTRR settings. This parameter disables that behavior,
possibly causing your machine to run very slowly.

dmasound= [HW,OSS] Sound subsystem buffers

dscc4.setup= [NET]

dtc3181e= [HW,SCSI]

earlyprintk= [X86-32,X86-64,SH,BLACKFIN]
earlyprintk=vga
earlyprintk=serial[,ttySn[,baudrate]]
earlyprintk=dbgp

Append ",keep" to not disable it when the real console
takes over.

Only vga or serial or usb debug port at a time.

Currently only ttyS0 and ttyS1 are supported.

Interaction with the standard serial driver is not
very good.

The VGA output is eventually overwritten by the real
console.

eata= [HW,SCSI]

edd= [EDD]
Format: {"off" | "on" | "skip[mbr]"}

eisa_irq_edge= [PARISC,HW]
See header of drivers/parisc/eisa.c.

elanfreq= [X86-32]
See comment before function elanfreq_setup() in
arch/x86/kernel/cpu/cpufreq/elanfreq.c.

elevator= [IOSCHED]
Format: {"anticipatory" | "cfq" | "deadline" | "noop"}
See Documentation/block/as-iosched.txt and
Documentation/block/deadline-iosched.txt for details.

elfcorehdr= [IA64,PPC,SH,X86-32,X86_64]
Specifies physical address of start of kernel core
image elf header. Generally kexec loader will
pass this option to capture kernel.
See Documentation/kdump/kdump.txt for details.

enforcing [SELINUX] Set initial enforcing status.
Format: {"0" | "1"}
See security/selinux/Kconfig help text.
0 -- permissive (log only, no denials).
1 -- enforcing (deny and log).
Default value is 0.
Value can be changed at runtime via /selinux/enforce.

ether= [HW,NET] Ethernet cards parameters
This option is obsoleted by the "netdev=" option, which
has equivalent usage. See its documentation for details.

eurwdt= [HW,WDT] Eurotech CPU-1220/1410 onboard watchdog.
Format: <io>[,<irq>]

failslab=
fail_page_alloc=
fail_make_request=[KNL]
General fault injection mechanism.
Format: <interval>,<probability>,<space>,<times>
See also /Documentation/fault-injection/.

fd_mcs= [HW,SCSI]
See header of drivers/scsi/fd_mcs.c.

fdomain= [HW,SCSI]
See header of drivers/scsi/fdomain.c.

floppy= [HW]
See Documentation/blockdev/floppy.txt.

force_pal_cache_flush
[IA-64] Avoid check_sal_cache_flush which may hang on
buggy SAL_CACHE_FLUSH implementations. Using this
parameter will force ia64_sal_cache_flush to call
ia64_pal_cache_flush instead of SAL_CACHE_FLUSH.

ftrace=[tracer]
[ftrace] will set and start the specified tracer
as early as possible in order to facilitate early
boot debugging.

ftrace_dump_on_oops
[ftrace] will dump the trace buffers on oops.

gamecon.map[2|3]=
[HW,JOY] Multisystem joystick and NES/SNES/PSX pad
support via parallel port (up to 5 devices per port)
Format: <port#>,<pad1>,<pad2>,<pad3>,<pad4>,<pad5>
See also Documentation/input/joystick-parport.txt

gamma= [HW,DRM]

gart_fix_e820= [X86_64] disable the fix e820 for K8 GART
Format: off | on
default: on

gdth= [HW,SCSI]
See header of drivers/scsi/gdth.c.

gpt [EFI] Forces disk with valid GPT signature but
invalid Protective MBR to be treated as GPT.

gvp11= [HW,SCSI]

hashdist= [KNL,NUMA] Large hashes allocated during boot
are distributed across NUMA nodes. Defaults on
for IA-64, off otherwise.
Format: 0 | 1 (for off | on)

hcl= [IA-64] SGI's Hardware Graph compatibility layer

hd= [EIDE] (E)IDE hard drive subsystem geometry
Format: <cyl>,<head>,<sect>

highmem=nn[KMG] [KNL,BOOT] forces the highmem zone to have an exact
size of <nn>. This works even on boxes that have no
highmem otherwise. This also works to reduce highmem
size on bigger boxes.

highres= [KNL] Enable/disable high resolution timer mode.
Valid parameters: "on", "off"
Default: "on"

hisax= [HW,ISDN]
See Documentation/isdn/README.HiSax.

hugepages= [HW,X86-32,IA-64] HugeTLB pages to allocate at boot.
hugepagesz= [HW,IA-64,PPC,X86-64] The size of the HugeTLB pages.
On x86-64 and powerpc, this option can be specified
multiple times interleaved with hugepages= to reserve
huge pages of different sizes. Valid pages sizes on
x86-64 are 2M (when the CPU supports "pse") and 1G
(when the CPU supports the "pdpe1gb" cpuinfo flag)
Note that 1GB pages can only be allocated at boot time
using hugepages= and not freed afterwards.
default_hugepagesz=
[same as hugepagesz=] The size of the default
HugeTLB page size. This is the size represented by
the legacy /proc/ hugepages APIs, used for SHM, and
default size when mounting hugetlbfs filesystems.
Defaults to the default architecture's huge page size
if not specified.

hlt [BUGS=ARM,SH]

hvc_iucv= [S390] Number of z/VM IUCV hypervisor console (HVC)
terminal devices. Valid values: 0..8

i8042.debug [HW] Toggle i8042 debug mode
i8042.direct [HW] Put keyboard port into non-translated mode
i8042.dumbkbd [HW] Pretend that controller can only read data from
keyboard and cannot control its state
(Don't attempt to blink the leds)
i8042.noaux [HW] Don't check for auxiliary (== mouse) port
i8042.nokbd [HW] Don't check/create keyboard port
i8042.noloop [HW] Disable the AUX Loopback command while probing
for the AUX port
i8042.nomux [HW] Don't check presence of an active multiplexing
controller
i8042.nopnp [HW] Don't use ACPIPnP / PnPBIOS to discover KBD/AUX
controllers
i8042.panicblink=
[HW] Frequency with which keyboard LEDs should blink
when kernel panics (default is 0.5 sec)
i8042.reset [HW] Reset the controller during init and cleanup
i8042.unlock [HW] Unlock (ignore) the keylock

i810= [HW,DRM]

i8k.ignore_dmi [HW] Continue probing hardware even if DMI data
indicates that the driver is running on unsupported
hardware.
i8k.force [HW] Activate i8k driver even if SMM BIOS signature
does not match list of supported models.
i8k.power_status
[HW] Report power status in /proc/i8k
(disabled by default)
i8k.restricted [HW] Allow controlling fans only if SYS_ADMIN
capability is set.

ibmmcascsi= [HW,MCA,SCSI] IBM MicroChannel SCSI adapter
See Documentation/mca.txt.

icn= [HW,ISDN]
Format: <io>[,<membase>[,<icn_id>[,<icn_id2>]]]

ide-core.nodma= [HW] (E)IDE subsystem
Format: =0.0 to prevent dma on hda, =0.1 hdb =1.0 hdc
.vlb_clock .pci_clock .noflush .noprobe .nowerr .cdrom
.chs .ignore_cable are additional options
See Documentation/ide/ide.txt.

idebus= [HW] (E)IDE subsystem - VLB/PCI bus speed
See Documentation/ide/ide.txt.

idle= [X86]
Format: idle=poll, idle=mwait, idle=halt, idle=nomwait
Poll forces a polling idle loop that can slightly
improve the performance of waking up a idle CPU, but
will use a lot of power and make the system run hot.
Not recommended.
idle=mwait: On systems which support MONITOR/MWAIT but
the kernel chose to not use it because it doesn't save
as much power as a normal idle loop, use the
MONITOR/MWAIT idle loop anyways. Performance should be
the same as idle=poll.
idle=halt: Halt is forced to be used for CPU idle.
In such case C2/C3 won't be used again.
idle=nomwait: Disable mwait for CPU C-states

ide-pci-generic.all-generic-ide [HW] (E)IDE subsystem
Claim all unknown PCI IDE storage controllers.

ignore_loglevel [KNL]
Ignore loglevel setting - this will print /all/
kernel messages to the console. Useful for debugging.

ihash_entries= [KNL]
Set number of hash buckets for inode cache.

in2000= [HW,SCSI]
See header of drivers/scsi/in2000.c.

init= [KNL]
Format: <full_path>
Run specified binary instead of /sbin/init as init
process.

initcall_debug [KNL] Trace initcalls as they are executed. Useful
for working out where the kernel is dying during
startup.

initrd= [BOOT] Specify the location of the initial ramdisk

inport.irq= [HW] Inport (ATI XL and Microsoft) busmouse driver
Format: <irq>

inttest= [IA64]

iomem= Disable strict checking of access to MMIO memory
strict regions from userspace.
relaxed

iommu= [x86]
off
force
noforce
biomerge
panic
nopanic
merge
nomerge
forcesac
soft

intel_iommu= [DMAR] Intel IOMMU driver (DMAR) option
on
Enable intel iommu driver.
off
Disable intel iommu driver.
igfx_off [Default Off]
By default, gfx is mapped as normal device. If a gfx
device has a dedicated DMAR unit, the DMAR unit is
bypassed by not enabling DMAR with this option. In
this case, gfx device will use physical address for
DMA.
forcedac [x86_64]
With this option iommu will not optimize to look
for io virtual address below 32 bit forcing dual
address cycle on pci bus for cards supporting greater
than 32 bit addressing. The default is to look
for translation below 32 bit and if not available
then look in the higher range.
strict [Default Off]
With this option on every unmap_single operation will
result in a hardware IOTLB flush operation as opposed
to batching them for performance.

io_delay= [X86-32,X86-64] I/O delay method
0x80
Standard port 0x80 based delay
0xed
Alternate port 0xed based delay (needed on some systems)
udelay
Simple two microseconds delay
none
No delay

io7= [HW] IO7 for Marvel based alpha systems
See comment before marvel_specify_io7 in
arch/alpha/kernel/core_marvel.c.

ip= [IP_PNP]
See Documentation/filesystems/nfsroot.txt.

ip2= [HW] Set IO/IRQ pairs for up to 4 IntelliPort boards
See comment before ip2_setup() in
drivers/char/ip2/ip2base.c.

ips= [HW,SCSI] Adaptec / IBM ServeRAID controller
See header of drivers/scsi/ips.c.

ports= [IP_VS_FTP] IPVS ftp helper module
Default is 21.
Up to 8 (IP_VS_APP_MAX_PORTS) ports
may be specified.
Format: <port>,<port>....

irqfixup [HW]
When an interrupt is not handled search all handlers
for it. Intended to get systems with badly broken
firmware running.

irqpoll [HW]
When an interrupt is not handled search all handlers
for it. Also check all handlers each timer
interrupt. Intended to get systems with badly broken
firmware running.

isapnp= [ISAPNP]
Format: <RDP>,<reset>,<pci_scan>,<verbosity>

isolcpus= [KNL,SMP] Isolate CPUs from the general scheduler.
Format:
<cpu number>,...,<cpu number>
or
<cpu number>-<cpu number>
(must be a positive range in ascending order)
or a mixture
<cpu number>,...,<cpu number>-<cpu number>

This option can be used to specify one or more CPUs
to isolate from the general SMP balancing and scheduling
algorithms. You can move a process onto or off an
"isolated" CPU via the CPU affinity syscalls or cpuset.
<cpu number> begins at 0 and the maximum value is
"number of CPUs in system - 1".

This option is the preferred way to isolate CPUs. The
alternative -- manually setting the CPU mask of all
tasks in the system -- can cause problems and
suboptimal load balancer performance.

iucv= [HW,NET]

js= [HW,JOY] Analog joystick
See Documentation/input/joystick.txt.

kernelcore=nn[KMG] [KNL,X86-32,IA-64,PPC,X86-64] This parameter
specifies the amount of memory usable by the kernel
for non-movable allocations. The requested amount is
spread evenly throughout all nodes in the system. The
remaining memory in each node is used for Movable
pages. In the event, a node is too small to have both
kernelcore and Movable pages, kernelcore pages will
take priority and other nodes will have a larger number
of kernelcore pages. The Movable zone is used for the
allocation of pages that may be reclaimed or moved
by the page migration subsystem. This means that
HugeTLB pages may not be allocated from this zone.
Note that allocations like PTEs-from-HighMem still
use the HighMem zone if it exists, and the Normal
zone if it does not.

movablecore=nn[KMG] [KNL,X86-32,IA-64,PPC,X86-64] This parameter
is similar to kernelcore except it specifies the
amount of memory used for migratable allocations.
If both kernelcore and movablecore is specified,
then kernelcore will be at *least* the specified
value but may be more. If movablecore on its own
is specified, the administrator must be careful
that the amount of memory usable for all allocations
is not too small.

keepinitrd [HW,ARM]

kstack=N [X86-32,X86-64] Print N words from the kernel stack
in oops dumps.

kgdboc= [HW] kgdb over consoles.
Requires a tty driver that supports console polling.
(only serial suported for now)
Format: <serial_device>[,baud]

kmac= [MIPS] korina ethernet MAC address.
Configure the RouterBoard 532 series on-chip
Ethernet adapter MAC address.

l2cr= [PPC]

l3cr= [PPC]

lapic [X86-32,APIC] Enable the local APIC even if BIOS
disabled it.

lapic_timer_c2_ok [X86-32,x86-64,APIC] trust the local apic timer
in C2 power state.

libata.dma= [LIBATA] DMA control
libata.dma=0 Disable all PATA and SATA DMA
libata.dma=1 PATA and SATA Disk DMA only
libata.dma=2 ATAPI (CDROM) DMA only
libata.dma=4 Compact Flash DMA only
Combinations also work, so libata.dma=3 enables DMA
for disks and CDROMs, but not CFs.

libata.noacpi [LIBATA] Disables use of ACPI in libata suspend/resume
when set.
Format: <int>

libata.force= [LIBATA] Force configurations. The format is comma
separated list of "[ID:]VAL" where ID is
PORT[:DEVICE]. PORT and DEVICE are decimal numbers
matching port, link or device. Basically, it matches
the ATA ID string printed on console by libata. If
the whole ID part is omitted, the last PORT and DEVICE
values are used. If ID hasn't been specified yet, the
configuration applies to all ports, links and devices.

If only DEVICE is omitted, the parameter applies to
the port and all links and devices behind it. DEVICE
number of 0 either selects the first device or the
first fan-out link behind PMP device. It does not
select the host link. DEVICE number of 15 selects the
host link and device attached to it.

The VAL specifies the configuration to force. As long
as there's no ambiguity shortcut notation is allowed.
For example, both 1.5 and 1.5G would work for 1.5Gbps.
The following configurations can be forced.

* Cable type: 40c, 80c, short40c, unk, ign or sata.
Any ID with matching PORT is used.

* SATA link speed limit: 1.5Gbps or 3.0Gbps.

* Transfer mode: pio[0-7], mwdma[0-4] and udma[0-7].
udma[/][16,25,33,44,66,100,133] notation is also
allowed.

* [no]ncq: Turn on or off NCQ.

* nohrst, nosrst, norst: suppress hard, soft
and both resets.

If there are multiple matching configurations changing
the same attribute, the last one is used.

lmb=debug [KNL] Enable lmb debug messages.

load_ramdisk= [RAM] List of ramdisks to load from floppy
See Documentation/blockdev/ramdisk.txt.

lockd.nlm_grace_period=P [NFS] Assign grace period.
Format: <integer>

lockd.nlm_tcpport=N [NFS] Assign TCP port.
Format: <integer>

lockd.nlm_timeout=T [NFS] Assign timeout value.
Format: <integer>

lockd.nlm_udpport=M [NFS] Assign UDP port.
Format: <integer>

logibm.irq= [HW,MOUSE] Logitech Bus Mouse Driver
Format: <irq>

loglevel= All Kernel Messages with a loglevel smaller than the
console loglevel will be printed to the console. It can
also be changed with klogd or other programs. The
loglevels are defined as follows:

0 (KERN_EMERG) system is unusable
1 (KERN_ALERT) action must be taken immediately
2 (KERN_CRIT) critical conditions
3 (KERN_ERR) error conditions
4 (KERN_WARNING) warning conditions
5 (KERN_NOTICE) normal but significant condition
6 (KERN_INFO) informational
7 (KERN_DEBUG) debug-level messages

log_buf_len=n Sets the size of the printk ring buffer, in bytes.
Format: { n | nk | nM }
n must be a power of two. The default size
is set in the kernel config file.

logo.nologo [FB] Disables display of the built-in Linux logo.
This may be used to provide more screen space for
kernel log messages and is useful when debugging
kernel boot problems.

lp=0 [LP] Specify parallel ports to use, e.g,
lp=port[,port...] lp=none,parport0 (lp0 not configured, lp1 uses
lp=reset first parallel port). 'lp=0' disables the
lp=auto printer driver. 'lp=reset' (which can be
specified in addition to the ports) causes
attached printers to be reset. Using
lp=port1,port2,... specifies the parallel ports
to associate lp devices with, starting with
lp0. A port specification may be 'none' to skip
that lp device, or a parport name such as
'parport0'. Specifying 'lp=auto' instead of a
port specification list means that device IDs
from each port should be examined, to see if
an IEEE 1284-compliant printer is attached; if
so, the driver will manage that printer.
See also header of drivers/char/lp.c.

lpj=n [KNL]
Sets loops_per_jiffy to given constant, thus avoiding
time-consuming boot-time autodetection (up to 250 ms per
CPU). 0 enables autodetection (default). To determine
the correct value for your kernel, boot with normal
autodetection and see what value is printed. Note that
on SMP systems the preset will be applied to all CPUs,
which is likely to cause problems if your CPUs need
significantly divergent settings. An incorrect value
will cause delays in the kernel to be wrong, leading to
unpredictable I/O errors and other breakage. Although
unlikely, in the extreme case this might damage your
hardware.

ltpc= [NET]
Format: <io>,<irq>,<dma>

mac5380= [HW,SCSI] Format:
<can_queue>,<cmd_per_lun>,<sg_tablesize>,<hostid>,<use_tags>

machvec= [IA64] Force the use of a particular machine-vector
(machvec) in a generic kernel.
Example: machvec=hpzx1_swiotlb

max_loop= [LOOP] Maximum number of loopback devices that can
be mounted
Format: <1-256>

maxcpus= [SMP] Maximum number of processors that an SMP kernel
should make use of. maxcpus=n : n >= 0 limits the
kernel to using 'n' processors. n=0 is a special case,
it is equivalent to "nosmp", which also disables
the IO APIC.

max_addr=nn[KMG] [KNL,BOOT,ia64] All physical memory greater than
or equal to this physical address is ignored.

max_luns= [SCSI] Maximum number of LUNs to probe.
Should be between 1 and 2^32-1.

max_report_luns=
[SCSI] Maximum number of LUNs received.
Should be between 1 and 16384.

mcatest= [IA-64]

mce [X86-32] Machine Check Exception

mce=option [X86-64] See Documentation/x86/x86_64/boot-options.txt

md= [HW] RAID subsystems devices and level
See Documentation/md.txt.

mdacon= [MDA]
Format: <first>,<last>
Specifies range of consoles to be captured by the MDA.

mem=nn[KMG] [KNL,BOOT] Force usage of a specific amount of memory
Amount of memory to be used when the kernel is not able
to see the whole system memory or for test.
[X86-32] Use together with memmap= to avoid physical
address space collisions. Without memmap= PCI devices
could be placed at addresses belonging to unused RAM.

mem=nopentium [BUGS=X86-32] Disable usage of 4MB pages for kernel
memory.

memchunk=nn[KMG]
[KNL,SH] Allow user to override the default size for
per-device physically contiguous DMA buffers.

memmap=exactmap [KNL,X86-32,X86_64] Enable setting of an exact
E820 memory map, as specified by the user.
Such memmap=exactmap lines can be constructed based on
BIOS output or other requirements. See the memmap=nn@ss
option description.

memmap=nn[KMG]@ss[KMG]
[KNL] Force usage of a specific region of memory
Region of memory to be used, from ss to ss+nn.

memmap=nn[KMG]#ss[KMG]
[KNL,ACPI] Mark specific memory as ACPI data.
Region of memory to be used, from ss to ss+nn.

memmap=nn[KMG]$ss[KMG]
[KNL,ACPI] Mark specific memory as reserved.
Region of memory to be used, from ss to ss+nn.
Example: Exclude memory from 0x18690000-0x1869ffff
memmap=64K$0x18690000
or
memmap=0x10000$0x18690000

memory_corruption_check=0/1 [X86]
Some BIOSes seem to corrupt the first 64k of
memory when doing things like suspend/resume.
Setting this option will scan the memory
looking for corruption. Enabling this will
both detect corruption and prevent the kernel
from using the memory being corrupted.
However, its intended as a diagnostic tool; if
repeatable BIOS-originated corruption always
affects the same memory, you can use memmap=
to prevent the kernel from using that memory.

memory_corruption_check_size=size [X86]
By default it checks for corruption in the low
64k, making this memory unavailable for normal
use. Use this parameter to scan for
corruption in more or less memory.

memory_corruption_check_period=seconds [X86]
By default it checks for corruption every 60
seconds. Use this parameter to check at some
other rate. 0 disables periodic checking.

memtest= [KNL,X86] Enable memtest
Format: <integer>
range: 0,4 : pattern number
default : 0 <disable>

meye.*= [HW] Set MotionEye Camera parameters
See Documentation/video4linux/meye.txt.

mfgpt_irq= [IA-32] Specify the IRQ to use for the
Multi-Function General Purpose Timers on AMD Geode
platforms.

mfgptfix [X86-32] Fix MFGPT timers on AMD Geode platforms when
the BIOS has incorrectly applied a workaround. TinyBIOS
version 0.98 is known to be affected, 0.99 fixes the
problem by letting the user disable the workaround.

mga= [HW,DRM]

min_addr=nn[KMG] [KNL,BOOT,ia64] All physical memory below this
physical address is ignored.

mminit_loglevel=
[KNL] When CONFIG_DEBUG_MEMORY_INIT is set, this
parameter allows control of the logging verbosity for
the additional memory initialisation checks. A value
of 0 disables mminit logging and a level of 4 will
log everything. Information is printed at KERN_DEBUG
so loglevel=8 may also need to be specified.

mousedev.tap_time=
[MOUSE] Maximum time between finger touching and
leaving touchpad surface for touch to be considered
a tap and be reported as a left button click (for
touchpads working in absolute mode only).
Format: <msecs>
mousedev.xres= [MOUSE] Horizontal screen resolution, used for devices
reporting absolute coordinates, such as tablets
mousedev.yres= [MOUSE] Vertical screen resolution, used for devices
reporting absolute coordinates, such as tablets

mpu401= [HW,OSS]
Format: <io>,<irq>

MTD_Partition= [MTD]
Format: <name>,<region-number>,<size>,<offset>

MTD_Region= [MTD] Format:
<name>,<region-number>[,<base>,<size>,<buswidth>,<altbuswidth>]

mtdparts= [MTD]
See drivers/mtd/cmdlinepart.c.

mtdset= [ARM]
ARM/S3C2412 JIVE boot control

See arch/arm/mach-s3c2412/mach-jive.c

mtouchusb.raw_coordinates=
[HW] Make the MicroTouch USB driver use raw coordinates
('y', default) or cooked coordinates ('n')

n2= [NET] SDL Inc. RISCom/N2 synchronous serial card

NCR_D700= [HW,SCSI]
See header of drivers/scsi/NCR_D700.c.

ncr5380= [HW,SCSI]

ncr53c400= [HW,SCSI]

ncr53c400a= [HW,SCSI]

ncr53c406a= [HW,SCSI]

ncr53c8xx= [HW,SCSI]

netdev= [NET] Network devices parameters
Format: <irq>,<io>,<mem_start>,<mem_end>,<name>
Note that mem_start is often overloaded to mean
something different and driver-specific.
This usage is only documented in each driver source
file if at all.

nf_conntrack.acct=
[NETFILTER] Enable connection tracking flow accounting
0 to disable accounting
1 to enable accounting
Default value depends on CONFIG_NF_CT_ACCT that is
going to be removed in 2.6.29.

nfsaddrs= [NFS]
See Documentation/filesystems/nfsroot.txt.

nfsroot= [NFS] nfs root filesystem for disk-less boxes.
See Documentation/filesystems/nfsroot.txt.

nfs.callback_tcpport=
[NFS] set the TCP port on which the NFSv4 callback
channel should listen.

nfs.idmap_cache_timeout=
[NFS] set the maximum lifetime for idmapper cache
entries.

nfs.enable_ino64=
[NFS] enable 64-bit inode numbers.
If zero, the NFS client will fake up a 32-bit inode
number for the readdir() and stat() syscalls instead
of returning the full 64-bit number.
The default is to return 64-bit inode numbers.

nmi_debug= [KNL,AVR32] Specify one or more actions to take
when a NMI is triggered.
Format: [state][,regs][,debounce][,die]

nmi_watchdog= [KNL,BUGS=X86-32,X86-64] Debugging features for SMP kernels
Format: [panic,][num]
Valid num: 0,1,2
0 - turn nmi_watchdog off
1 - use the IO-APIC timer for the NMI watchdog
2 - use the local APIC for the NMI watchdog using
a performance counter. Note: This will use one performance
counter and the local APIC's performance vector.
When panic is specified panic when an NMI watchdog timeout occurs.
This is useful when you use a panic=... timeout and need the box
quickly up again.
Instead of 1 and 2 it is possible to use the following
symbolic names: lapic and ioapic
Example: nmi_watchdog=2 or nmi_watchdog=panic,lapic

no387 [BUGS=X86-32] Tells the kernel to use the 387 maths
emulation library even if a 387 maths coprocessor
is present.

noaliencache [MM, NUMA, SLAB] Disables the allocation of alien
caches in the slab allocator. Saves per-node memory,
but will impact performance.

noalign [KNL,ARM]

noapic [SMP,APIC] Tells the kernel to not make use of any
IOAPICs that may be present in the system.

nobats [PPC] Do not use BATs for mapping kernel lowmem
on "Classic" PPC cores.

nocache [ARM]

nodelayacct [KNL] Disable per-task delay accounting

nodisconnect [HW,SCSI,M68K] Disables SCSI disconnects.

nodsp [SH] Disable hardware DSP at boot time.

noefi [X86-32,X86-64] Disable EFI runtime services support.

noexec [IA-64]

noexec [X86-32,X86-64]
On X86-32 available only on PAE configured kernels.
noexec=on: enable non-executable mappings (default)
noexec=off: disable non-executable mappings

noexec32 [X86-64]
This affects only 32-bit executables.
noexec32=on: enable non-executable mappings (default)
read doesn't imply executable mappings
noexec32=off: disable non-executable mappings
read implies executable mappings

nofpu [SH] Disable hardware FPU at boot time.

nofxsr [BUGS=X86-32] Disables x86 floating point extended
register save and restore. The kernel will only save
legacy floating-point registers on task switch.

noclflush [BUGS=X86] Don't use the CLFLUSH instruction

nohlt [BUGS=ARM,SH]

no-hlt [BUGS=X86-32] Tells the kernel that the hlt
instruction doesn't work correctly and not to
use it.

no_file_caps Tells the kernel not to honor file capabilities. The
only way then for a file to be executed with privilege
is to be setuid root or executed by root.

nohalt [IA-64] Tells the kernel not to use the power saving
function PAL_HALT_LIGHT when idle. This increases
power-consumption. On the positive side, it reduces
interrupt wake-up latency, which may improve performance
in certain environments such as networked servers or
real-time systems.

nohz= [KNL] Boottime enable/disable dynamic ticks
Valid arguments: on, off
Default: on

noirqdebug [X86-32] Disables the code which attempts to detect and
disable unhandled interrupt sources.

no_timer_check [X86-32,X86_64,APIC] Disables the code which tests for
broken timer IRQ sources.

noisapnp [ISAPNP] Disables ISA PnP code.

noinitrd [RAM] Tells the kernel not to load any configured
initial RAM disk.

nointroute [IA-64]

nojitter [IA64] Disables jitter checking for ITC timers.

nolapic [X86-32,APIC] Do not enable or use the local APIC.

nolapic_timer [X86-32,APIC] Do not use the local APIC timer.

nox2apic [X86-64,APIC] Do not enable x2APIC mode.

x2apic_phys [X86-64,APIC] Use x2apic physical mode instead of
default x2apic cluster mode on platforms
supporting x2apic.

noltlbs [PPC] Do not use large page/tlb entries for kernel
lowmem mapping on PPC40x.

nomca [IA-64] Disable machine check abort handling

nomce [X86-32] Machine Check Exception

nomfgpt [X86-32] Disable Multi-Function General Purpose
Timer usage (for AMD Geode machines).

noreplace-paravirt [X86-32,PV_OPS] Don't patch paravirt_ops

noreplace-smp [X86-32,SMP] Don't replace SMP instructions
with UP alternatives

noresidual [PPC] Don't use residual data on PReP machines.

noresume [SWSUSP] Disables resume and restores original swap
space.

no-scroll [VGA] Disables scrollback.
This is required for the Braillex ib80-piezo Braille
reader made by F.H. Papenmeier (Germany).

nosbagart [IA-64]

nosep [BUGS=X86-32] Disables x86 SYSENTER/SYSEXIT support.

nosmp [SMP] Tells an SMP kernel to act as a UP kernel,
and disable the IO APIC. legacy for "maxcpus=0".

nosoftlockup [KNL] Disable the soft-lockup detector.

noswapaccount [KNL] Disable accounting of swap in memory resource
controller. (See Documentation/controllers/memory.txt)

nosync [HW,M68K] Disables sync negotiation for all devices.

notsc [BUGS=X86-32] Disable Time Stamp Counter

nousb [USB] Disable the USB subsystem

nowb [ARM]

nptcg= [IA64] Override max number of concurrent global TLB
purges which is reported from either PAL_VM_SUMMARY or
SAL PALO.

numa_zonelist_order= [KNL, BOOT] Select zonelist order for NUMA.
one of ['zone', 'node', 'default'] can be specified
This can be set from sysctl after boot.
See Documentation/sysctl/vm.txt for details.

nr_uarts= [SERIAL] maximum number of UARTs to be registered.

ohci1394_dma=early [HW] enable debugging via the ohci1394 driver.
See Documentation/debugging-via-ohci1394.txt for more
info.

olpc_ec_timeout= [OLPC] ms delay when issuing EC commands
Rather than timing out after 20 ms if an EC
command is not properly ACKed, override the length
of the timeout. We have interrupts disabled while
waiting for the ACK, so if this is set too high
interrupts *may* be lost!

opl3= [HW,OSS]
Format: <io>

oprofile.timer= [HW]
Use timer interrupt instead of performance counters

osst= [HW,SCSI] SCSI Tape Driver
Format: <buffer_size>,<write_threshold>
See also Documentation/scsi/st.txt.

panic= [KNL] Kernel behaviour on panic
Format: <timeout>

parkbd.port= [HW] Parallel port number the keyboard adapter is
connected to, default is 0.
Format: <parport#>
parkbd.mode= [HW] Parallel port keyboard adapter mode of operation,
0 for XT, 1 for AT (default is AT).
Format: <mode>

parport= [HW,PPT] Specify parallel ports. 0 disables.
Format: { 0 | auto | 0xBBB[,IRQ[,DMA]] }
Use 'auto' to force the driver to use any
IRQ/DMA settings detected (the default is to
ignore detected IRQ/DMA settings because of
possible conflicts). You can specify the base
address, IRQ, and DMA settings; IRQ and DMA
should be numbers, or 'auto' (for using detected
settings on that particular port), or 'nofifo'
(to avoid using a FIFO even if it is detected).
Parallel ports are assigned in the order they
are specified on the command line, starting
with parport0.

parport_init_mode= [HW,PPT]
Configure VIA parallel port to operate in
a specific mode. This is necessary on Pegasos
computer where firmware has no options for setting
up parallel port mode and sets it to spp.
Currently this function knows 686a and 8231 chips.
Format: [spp|ps2|epp|ecp|ecpepp]

pas2= [HW,OSS] Format:
<io>,<irq>,<dma>,<dma16>,<sb_io>,<sb_irq>,<sb_dma>,<sb_dma16>

pas16= [HW,SCSI]
See header of drivers/scsi/pas16.c.

pause_on_oops=
Halt all CPUs after the first oops has been printed for
the specified number of seconds. This is to be used if
your oopses keep scrolling off the screen.

pcbit= [HW,ISDN]

pcd. [PARIDE]
See header of drivers/block/paride/pcd.c.
See also Documentation/blockdev/paride.txt.

pci=option[,option...] [PCI] various PCI subsystem options:
off [X86] don't probe for the PCI bus
bios [X86-32] force use of PCI BIOS, don't access
the hardware directly. Use this if your machine
has a non-standard PCI host bridge.
nobios [X86-32] disallow use of PCI BIOS, only direct
hardware access methods are allowed. Use this
if you experience crashes upon bootup and you
suspect they are caused by the BIOS.
conf1 [X86] Force use of PCI Configuration
Mechanism 1.
conf2 [X86] Force use of PCI Configuration
Mechanism 2.
noaer [PCIE] If the PCIEAER kernel config parameter is
enabled, this kernel boot option can be used to
disable the use of PCIE advanced error reporting.
nodomains [PCI] Disable support for multiple PCI
root domains (aka PCI segments, in ACPI-speak).
nommconf [X86-32,X86_64] Disable use of MMCONFIG for PCI
Configuration
nomsi [MSI] If the PCI_MSI kernel config parameter is
enabled, this kernel boot option can be used to
disable the use of MSI interrupts system-wide.
noioapicquirk [APIC] Disable all boot interrupt quirks.
Safety option to keep boot IRQs enabled. This
should never be necessary.
ioapicreroute [APIC] Enable rerouting of boot IRQs to the
primary IO-APIC for bridges that cannot disable
boot IRQs. This fixes a source of spurious IRQs
when the system masks IRQs.
noioapicreroute [APIC] Disable workaround that uses the
boot IRQ equivalent of an IRQ that connects to
a chipset where boot IRQs cannot be disabled.
The opposite of ioapicreroute.
biosirq [X86-32] Use PCI BIOS calls to get the interrupt
routing table. These calls are known to be buggy
on several machines and they hang the machine
when used, but on other computers it's the only
way to get the interrupt routing table. Try
this option if the kernel is unable to allocate
IRQs or discover secondary PCI buses on your
motherboard.
rom [X86] Assign address space to expansion ROMs.
Use with caution as certain devices share
address decoders between ROMs and other
resources.
norom [X86] Do not assign address space to
expansion ROMs that do not already have
BIOS assigned address ranges.
irqmask=0xMMMM [X86] Set a bit mask of IRQs allowed to be
assigned automatically to PCI devices. You can
make the kernel exclude IRQs of your ISA cards
this way.
pirqaddr=0xAAAAA [X86] Specify the physical address
of the PIRQ table (normally generated
by the BIOS) if it is outside the
F0000h-100000h range.
lastbus=N [X86] Scan all buses thru bus #N. Can be
useful if the kernel is unable to find your
secondary buses and you want to tell it
explicitly which ones they are.
assign-busses [X86] Always assign all PCI bus
numbers ourselves, overriding
whatever the firmware may have done.
usepirqmask [X86] Honor the possible IRQ mask stored
in the BIOS $PIR table. This is needed on
some systems with broken BIOSes, notably
some HP Pavilion N5400 and Omnibook XE3
notebooks. This will have no effect if ACPI
IRQ routing is enabled.
noacpi [X86] Do not use ACPI for IRQ routing
or for PCI scanning.
use_crs [X86] Use _CRS for PCI resource
allocation.
routeirq Do IRQ routing for all PCI devices.
This is normally done in pci_enable_device(),
so this option is a temporary workaround
for broken drivers that don't call it.
skip_isa_align [X86] do not align io start addr, so can
handle more pci cards
firmware [ARM] Do not re-enumerate the bus but instead
just use the configuration from the
bootloader. This is currently used on
IXP2000 systems where the bus has to be
configured a certain way for adjunct CPUs.
noearly [X86] Don't do any early type 1 scanning.
This might help on some broken boards which
machine check when some devices' config space
is read. But various workarounds are disabled
and some IOMMU drivers will not work.
bfsort Sort PCI devices into breadth-first order.
This sorting is done to get a device
order compatible with older (<= 2.4) kernels.
nobfsort Don't sort PCI devices into breadth-first order.
cbiosize=nn[KMG] The fixed amount of bus space which is
reserved for the CardBus bridge's IO window.
The default value is 256 bytes.
cbmemsize=nn[KMG] The fixed amount of bus space which is
reserved for the CardBus bridge's memory
window. The default value is 64 megabytes.

pcie_aspm= [PCIE] Forcibly enable or disable PCIe Active State Power
Management.
off Disable ASPM.
force Enable ASPM even on devices that claim not to support it.
WARNING: Forcing ASPM on may cause system lockups.

pcmv= [HW,PCMCIA] BadgePAD 4

pd. [PARIDE]
See Documentation/blockdev/paride.txt.

pdcchassis= [PARISC,HW] Disable/Enable PDC Chassis Status codes at
boot time.
Format: { 0 | 1 }
See arch/parisc/kernel/pdc_chassis.c

pf. [PARIDE]
See Documentation/blockdev/paride.txt.

pg. [PARIDE]
See Documentation/blockdev/paride.txt.

pirq= [SMP,APIC] Manual mp-table setup
See Documentation/x86/i386/IO-APIC.txt.

plip= [PPT,NET] Parallel port network link
Format: { parport<nr> | timid | 0 }
See also Documentation/parport.txt.

pmtmr= [X86] Manual setup of pmtmr I/O Port.
Override pmtimer IOPort with a hex value.
e.g. pmtmr=0x508

pnp.debug [PNP]
Enable PNP debug messages. This depends on the
CONFIG_PNP_DEBUG_MESSAGES option.

pnpacpi= [ACPI]
{ off }

pnpbios= [ISAPNP]
{ on | off | curr | res | no-curr | no-res }

pnp_reserve_irq=
[ISAPNP] Exclude IRQs for the autoconfiguration

pnp_reserve_dma=
[ISAPNP] Exclude DMAs for the autoconfiguration

pnp_reserve_io= [ISAPNP] Exclude I/O ports for the autoconfiguration
Ranges are in pairs (I/O port base and size).

pnp_reserve_mem=
[ISAPNP] Exclude memory regions for the
autoconfiguration.
Ranges are in pairs (memory base and size).

dynamic_printk Enables pr_debug()/dev_dbg() calls if
CONFIG_DYNAMIC_PRINTK_DEBUG has been enabled.
These can also be switched on/off via
<debugfs>/dynamic_printk/modules

print-fatal-signals=
[KNL] debug: print fatal signals
print-fatal-signals=1: print segfault info to
the kernel console.
default: off.

printk.time= Show timing data prefixed to each printk message line
Format: <bool> (1/Y/y=enable, 0/N/n=disable)

profile= [KNL] Enable kernel profiling via /proc/profile
Format: [schedule,]<number>
Param: "schedule" - profile schedule points.
Param: <number> - step/bucket size as a power of 2 for
statistical time based profiling.
Param: "sleep" - profile D-state sleeping (millisecs).
Requires CONFIG_SCHEDSTATS
Param: "kvm" - profile VM exits.

processor.max_cstate= [HW,ACPI]
Limit processor to maximum C-state
max_cstate=9 overrides any DMI blacklist limit.

processor.nocst [HW,ACPI]
Ignore the _CST method to determine C-states,
instead using the legacy FADT method

prompt_ramdisk= [RAM] List of RAM disks to prompt for floppy disk
before loading.
See Documentation/blockdev/ramdisk.txt.

psmouse.proto= [HW,MOUSE] Highest PS2 mouse protocol extension to
probe for; one of (bare|imps|exps|lifebook|any).
psmouse.rate= [HW,MOUSE] Set desired mouse report rate, in reports
per second.
psmouse.resetafter= [HW,MOUSE]
Try to reset the device after so many bad packets
(0 = never).
psmouse.resolution=
[HW,MOUSE] Set desired mouse resolution, in dpi.
psmouse.smartscroll=
[HW,MOUSE] Controls Logitech smartscroll autorepeat.
0 = disabled, 1 = enabled (default).

pss= [HW,OSS] Personal Sound System (ECHO ESC614)
Format:
<io>,<mss_io>,<mss_irq>,<mss_dma>,<mpu_io>,<mpu_irq>

pt. [PARIDE]
See Documentation/blockdev/paride.txt.

pty.legacy_count=
[KNL] Number of legacy pty's. Overwrites compiled-in
default number.

quiet [KNL] Disable most log messages

r128= [HW,DRM]

raid= [HW,RAID]
See Documentation/md.txt.

ramdisk_blocksize= [RAM]
See Documentation/blockdev/ramdisk.txt.

ramdisk_size= [RAM] Sizes of RAM disks in kilobytes
See Documentation/blockdev/ramdisk.txt.

rcupdate.blimit= [KNL,BOOT]
Set maximum number of finished RCU callbacks to process
in one batch.

rcupdate.qhimark= [KNL,BOOT]
Set threshold of queued
RCU callbacks over which batch limiting is disabled.

rcupdate.qlowmark= [KNL,BOOT]
Set threshold of queued RCU callbacks below which
batch limiting is re-enabled.

rdinit= [KNL]
Format: <full_path>
Run specified binary instead of /init from the ramdisk,
used for early userspace startup. See initrd.

reboot= [BUGS=X86-32,BUGS=ARM,BUGS=IA-64] Rebooting mode
Format: <reboot_mode>[,<reboot_mode2>[,...]]
See arch/*/kernel/reboot.c or arch/*/kernel/process.c

relax_domain_level=
[KNL, SMP] Set scheduler's default relax_domain_level.
See Documentation/cpusets.txt.

reserve= [KNL,BUGS] Force the kernel to ignore some iomem area

reservetop= [X86-32]
Format: nn[KMG]
Reserves a hole at the top of the kernel virtual
address space.

reset_devices [KNL] Force drivers to reset the underlying device
during initialization.

resume= [SWSUSP]
Specify the partition device for software suspend

resume_offset= [SWSUSP]
Specify the offset from the beginning of the partition
given by "resume=" at which the swap header is located,
in <PAGE_SIZE> units (needed only for swap files).
See Documentation/power/swsusp-and-swap-files.txt

retain_initrd [RAM] Keep initrd memory after extraction

rhash_entries= [KNL,NET]
Set number of hash buckets for route cache

riscom8= [HW,SERIAL]
Format: <io_board1>[,<io_board2>[,...<io_boardN>]]

ro [KNL] Mount root device read-only on boot

root= [KNL] Root filesystem

rootdelay= [KNL] Delay (in seconds) to pause before attempting to
mount the root filesystem

rootflags= [KNL] Set root filesystem mount option string

rootfstype= [KNL] Set root filesystem type

rootwait [KNL] Wait (indefinitely) for root device to show up.
Useful for devices that are detected asynchronously
(e.g. USB and MMC devices).

root_plug.vendor_id=
[ROOTPLUG] Override the default vendor ID

root_plug.product_id=
[ROOTPLUG] Override the default product ID

root_plug.debug=
[ROOTPLUG] Enable debugging output

rw [KNL] Mount root device read-write on boot

S [KNL] Run init in single mode

sa1100ir [NET]
See drivers/net/irda/sa1100_ir.c.

sbni= [NET] Granch SBNI12 leased line adapter

sc1200wdt= [HW,WDT] SC1200 WDT (watchdog) driver
Format: <io>[,<timeout>[,<isapnp>]]

scsi_debug_*= [SCSI]
See drivers/scsi/scsi_debug.c.

scsi_default_dev_flags=
[SCSI] SCSI default device flags
Format: <integer>

scsi_dev_flags= [SCSI] Black/white list entry for vendor and model
Format: <vendor>:<model>:<flags>
(flags are integer value)

scsi_logging_level= [SCSI] a bit mask of logging levels
See drivers/scsi/scsi_logging.h for bits. Also
settable via sysctl at dev.scsi.logging_level
(/proc/sys/dev/scsi/logging_level).
There is also a nice 'scsi_logging_level' script in the
S390-tools package, available for download at
http://www-128.ibm.com/developerworks/linux/linux390/s390-tools-1.5.4.html

scsi_mod.scan= [SCSI] sync (default) scans SCSI busses as they are
discovered. async scans them in kernel threads,
allowing boot to proceed. none ignores them, expecting
user space to do the scan.

selinux [SELINUX] Disable or enable SELinux at boot time.
Format: { "0" | "1" }
See security/selinux/Kconfig help text.
0 -- disable.
1 -- enable.
Default value is set via kernel config option.
If enabled at boot time, /selinux/disable can be used
later to disable prior to initial policy load.

selinux_compat_net =
[SELINUX] Set initial selinux_compat_net flag value.
Format: { "0" | "1" }
0 -- use new secmark-based packet controls
1 -- use legacy packet controls
Default value is 0 (preferred).
Value can be changed at runtime via
/selinux/compat_net.

serialnumber [BUGS=X86-32]

shapers= [NET]
Maximal number of shapers.

show_msr= [x86] show boot-time MSR settings
Format: { <integer> }
Show boot-time (BIOS-initialized) MSR settings.
The parameter means the number of CPUs to show,
for example 1 means boot CPU only.

sim710= [SCSI,HW]
See header of drivers/scsi/sim710.c.

simeth= [IA-64]
simscsi=

slram= [HW,MTD]

slub_debug[=options[,slabs]] [MM, SLUB]
Enabling slub_debug allows one to determine the
culprit if slab objects become corrupted. Enabling
slub_debug can create guard zones around objects and
may poison objects when not in use. Also tracks the
last alloc / free. For more information see
Documentation/vm/slub.txt.

slub_max_order= [MM, SLUB]
Determines the maximum allowed order for slabs.
A high setting may cause OOMs due to memory
fragmentation. For more information see
Documentation/vm/slub.txt.

slub_min_objects= [MM, SLUB]
The minimum number of objects per slab. SLUB will
increase the slab order up to slub_max_order to
generate a sufficiently large slab able to contain
the number of objects indicated. The higher the number
of objects the smaller the overhead of tracking slabs
and the less frequently locks need to be acquired.
For more information see Documentation/vm/slub.txt.

slub_min_order= [MM, SLUB]
Determines the mininum page order for slabs. Must be
lower than slub_max_order.
For more information see Documentation/vm/slub.txt.

slub_nomerge [MM, SLUB]
Disable merging of slabs with similar size. May be
necessary if there is some reason to distinguish
allocs to different slabs. Debug options disable
merging on their own.
For more information see Documentation/vm/slub.txt.

smart2= [HW]
Format: <io1>[,<io2>[,...,<io8>]]

smp-alt-once [X86-32,SMP] On a hotplug CPU system, only
attempt to substitute SMP alternatives once at boot.

smsc-ircc2.nopnp [HW] Don't use PNP to discover SMC devices
smsc-ircc2.ircc_cfg= [HW] Device configuration I/O port
smsc-ircc2.ircc_sir= [HW] SIR base I/O port
smsc-ircc2.ircc_fir= [HW] FIR base I/O port
smsc-ircc2.ircc_irq= [HW] IRQ line
smsc-ircc2.ircc_dma= [HW] DMA channel
smsc-ircc2.ircc_transceiver= [HW] Transceiver type:
0: Toshiba Satellite 1800 (GP data pin select)
1: Fast pin select (default)
2: ATC IRMode

snd-ad1816a= [HW,ALSA]

snd-ad1848= [HW,ALSA]

snd-ali5451= [HW,ALSA]

snd-als100= [HW,ALSA]

snd-als4000= [HW,ALSA]

snd-azt2320= [HW,ALSA]

snd-cmi8330= [HW,ALSA]

snd-cmipci= [HW,ALSA]

snd-cs4231= [HW,ALSA]

snd-cs4232= [HW,ALSA]

snd-cs4236= [HW,ALSA]

snd-cs4281= [HW,ALSA]

snd-cs46xx= [HW,ALSA]

snd-dt019x= [HW,ALSA]

snd-dummy= [HW,ALSA]

snd-emu10k1= [HW,ALSA]

snd-ens1370= [HW,ALSA]

snd-ens1371= [HW,ALSA]

snd-es968= [HW,ALSA]

snd-es1688= [HW,ALSA]

snd-es18xx= [HW,ALSA]

snd-es1938= [HW,ALSA]

snd-es1968= [HW,ALSA]

snd-fm801= [HW,ALSA]

snd-gusclassic= [HW,ALSA]

snd-gusextreme= [HW,ALSA]

snd-gusmax= [HW,ALSA]

snd-hdsp= [HW,ALSA]

snd-ice1712= [HW,ALSA]

snd-intel8x0= [HW,ALSA]

snd-interwave= [HW,ALSA]

snd-interwave-stb=
[HW,ALSA]

snd-korg1212= [HW,ALSA]

snd-maestro3= [HW,ALSA]

snd-mpu401= [HW,ALSA]

snd-mtpav= [HW,ALSA]

snd-nm256= [HW,ALSA]

snd-opl3sa2= [HW,ALSA]

snd-opti92x-ad1848=
[HW,ALSA]

snd-opti92x-cs4231=
[HW,ALSA]

snd-opti93x= [HW,ALSA]

snd-pmac= [HW,ALSA]

snd-rme32= [HW,ALSA]

snd-rme96= [HW,ALSA]

snd-rme9652= [HW,ALSA]

snd-sb8= [HW,ALSA]

snd-sb16= [HW,ALSA]

snd-sbawe= [HW,ALSA]

snd-serial= [HW,ALSA]

snd-sgalaxy= [HW,ALSA]

snd-sonicvibes= [HW,ALSA]

snd-sun-amd7930=
[HW,ALSA]

snd-sun-cs4231= [HW,ALSA]

snd-trident= [HW,ALSA]

snd-usb-audio= [HW,ALSA,USB]

snd-via82xx= [HW,ALSA]

snd-virmidi= [HW,ALSA]

snd-wavefront= [HW,ALSA]

snd-ymfpci= [HW,ALSA]

softlockup_panic=
[KNL] Should the soft-lockup detector generate panics.

sonypi.*= [HW] Sony Programmable I/O Control Device driver
See Documentation/sonypi.txt

specialix= [HW,SERIAL] Specialix multi-serial port adapter
See Documentation/serial/specialix.txt.

spia_io_base= [HW,MTD]
spia_fio_base=
spia_pedr=
spia_peddr=

sscape= [HW,OSS]
Format: <io>,<irq>,<dma>,<mpu_io>,<mpu_irq>

st= [HW,SCSI] SCSI tape parameters (buffers, etc.)
See Documentation/scsi/st.txt.

stacktrace [FTRACE]
Enabled the stack tracer on boot up.

sti= [PARISC,HW]
Format: <num>
Set the STI (builtin display/keyboard on the HP-PARISC
machines) console (graphic card) which should be used
as the initial boot-console.
See also comment in drivers/video/console/sticore.c.

sti_font= [HW]
See comment in drivers/video/console/sticore.c.

stifb= [HW]
Format: bpp:<bpp1>[:<bpp2>[:<bpp3>...]]

sunrpc.pool_mode=
[NFS]
Control how the NFS server code allocates CPUs to
service thread pools. Depending on how many NICs
you have and where their interrupts are bound, this
option will affect which CPUs will do NFS serving.
Note: this parameter cannot be changed while the
NFS server is running.

auto the server chooses an appropriate mode
automatically using heuristics
global a single global pool contains all CPUs
percpu one pool for each CPU
pernode one pool for each NUMA node (equivalent
to global on non-NUMA machines)

swiotlb= [IA-64] Number of I/O TLB slabs

switches= [HW,M68k]

sym53c416= [HW,SCSI]
See header of drivers/scsi/sym53c416.c.

sysrq_always_enabled
[KNL]
Ignore sysrq setting - this boot parameter will
neutralize any effect of /proc/sys/kernel/sysrq.
Useful for debugging.

t128= [HW,SCSI]
See header of drivers/scsi/t128.c.

tdfx= [HW,DRM]

test_suspend= [SUSPEND]
Specify "mem" (for Suspend-to-RAM) or "standby" (for
standby suspend) as the system sleep state to briefly
enter during system startup. The system is woken from
this state using a wakeup-capable RTC alarm.

thash_entries= [KNL,NET]
Set number of hash buckets for TCP connection

thermal.act= [HW,ACPI]
-1: disable all active trip points in all thermal zones
<degrees C>: override all lowest active trip points

thermal.crt= [HW,ACPI]
-1: disable all critical trip points in all thermal zones
<degrees C>: override all critical trip points

thermal.nocrt= [HW,ACPI]
Set to disable actions on ACPI thermal zone
critical and hot trip points.

thermal.off= [HW,ACPI]
1: disable ACPI thermal control

thermal.psv= [HW,ACPI]
-1: disable all passive trip points
<degrees C>: override all passive trip points to this
value

thermal.tzp= [HW,ACPI]
Specify global default ACPI thermal zone polling rate
<deci-seconds>: poll all this frequency
0: no polling (default)

tmscsim= [HW,SCSI]
See comment before function dc390_setup() in
drivers/scsi/tmscsim.c.

topology= [S390]
Format: {off | on}
Specify if the kernel should make use of the cpu
topology informations if the hardware supports these.
The scheduler will make use of these informations and
e.g. base its process migration decisions on it.
Default is off.

tp720= [HW,PS2]

trix= [HW,OSS] MediaTrix AudioTrix Pro
Format:
<io>,<irq>,<dma>,<dma2>,<sb_io>,<sb_irq>,<sb_dma>,<mpu_io>,<mpu_irq>

tsc= Disable clocksource-must-verify flag for TSC.
Format: <string>
[x86] reliable: mark tsc clocksource as reliable, this
disables clocksource verification at runtime.
Used to enable high-resolution timer mode on older
hardware, and in virtualized environment.

turbografx.map[2|3]= [HW,JOY]
TurboGraFX parallel port interface
Format:
<port#>,<js1>,<js2>,<js3>,<js4>,<js5>,<js6>,<js7>
See also Documentation/input/joystick-parport.txt

u14-34f= [HW,SCSI] UltraStor 14F/34F SCSI host adapter
See header of drivers/scsi/u14-34f.c.

uart401= [HW,OSS]
Format: <io>,<irq>

uart6850= [HW,OSS]
Format: <io>,<irq>

uhci-hcd.ignore_oc=
[USB] Ignore overcurrent events (default N).
Some badly-designed motherboards generate lots of
bogus events, for ports that aren't wired to
anything. Set this parameter to avoid log spamming.
Note that genuine overcurrent events won't be
reported either.

unknown_nmi_panic
[X86-32,X86-64]
Set unknown_nmi_panic=1 early on boot.

usbcore.autosuspend=
[USB] The autosuspend time delay (in seconds) used
for newly-detected USB devices (default 2). This
is the time required before an idle device will be
autosuspended. Devices for which the delay is set
to a negative value won't be autosuspended at all.

usbcore.usbfs_snoop=
[USB] Set to log all usbfs traffic (default 0 = off).

usbcore.blinkenlights=
[USB] Set to cycle leds on hubs (default 0 = off).

usbcore.old_scheme_first=
[USB] Start with the old device initialization
scheme (default 0 = off).

usbcore.use_both_schemes=
[USB] Try the other device initialization scheme
if the first one fails (default 1 = enabled).

usbcore.initial_descriptor_timeout=
[USB] Specifies timeout for the initial 64-byte
USB_REQ_GET_DESCRIPTOR request in milliseconds
(default 5000 = 5.0 seconds).

usbhid.mousepoll=
[USBHID] The interval which mice are to be polled at.

usb-storage.delay_use=
[UMS] The delay in seconds before a new device is
scanned for Logical Units (default 5).

usb-storage.quirks=
[UMS] A list of quirks entries to supplement or
override the built-in unusual_devs list. List
entries are separated by commas. Each entry has
the form VID:PID:Flags where VID and PID are Vendor
and Product ID values (4-digit hex numbers) and
Flags is a set of characters, each corresponding
to a common usb-storage quirk flag as follows:
a = SANE_SENSE (collect more than 18 bytes
of sense data);
c = FIX_CAPACITY (decrease the reported
device capacity by one sector);
h = CAPACITY_HEURISTICS (decrease the
reported device capacity by one
sector if the number is odd);
i = IGNORE_DEVICE (don't bind to this
device);
l = NOT_LOCKABLE (don't try to lock and
unlock ejectable media);
m = MAX_SECTORS_64 (don't transfer more
than 64 sectors = 32 KB at a time);
o = CAPACITY_OK (accept the capacity
reported by the device);
r = IGNORE_RESIDUE (the device reports
bogus residue values);
s = SINGLE_LUN (the device has only one
Logical Unit);
w = NO_WP_DETECT (don't test whether the
medium is write-protected).
Example: quirks=0419:aaf5:rl,0421:0433:rc

add_efi_memmap [EFI; x86-32,X86-64] Include EFI memory map in
kernel's map of available physical RAM.

vdso= [X86-32,SH,x86-64]
vdso=2: enable compat VDSO (default with COMPAT_VDSO)
vdso=1: enable VDSO (default)
vdso=0: disable VDSO mapping

vdso32= [X86-32,X86-64]
vdso32=2: enable compat VDSO (default with COMPAT_VDSO)
vdso32=1: enable 32-bit VDSO (default)
vdso32=0: disable 32-bit VDSO mapping

vector= [IA-64,SMP]
vector=percpu: enable percpu vector domain

video= [FB] Frame buffer configuration
See Documentation/fb/modedb.txt.

vga= [BOOT,X86-32] Select a particular video mode
See Documentation/x86/boot.txt and
Documentation/svga.txt.
Use vga=ask for menu.
This is actually a boot loader parameter; the value is
passed to the kernel using a special protocol.

vmalloc=nn[KMG] [KNL,BOOT] Forces the vmalloc area to have an exact
size of <nn>. This can be used to increase the
minimum size (128MB on x86). It can also be used to
decrease the size and leave more room for directly
mapped kernel RAM.

vmhalt= [KNL,S390] Perform z/VM CP command after system halt.
Format: <command>

vmpanic= [KNL,S390] Perform z/VM CP command after kernel panic.
Format: <command>

vmpoff= [KNL,S390] Perform z/VM CP command after power off.
Format: <command>

waveartist= [HW,OSS]
Format: <io>,<irq>,<dma>,<dma2>

wd33c93= [HW,SCSI]
See header of drivers/scsi/wd33c93.c.

wd7000= [HW,SCSI]
See header of drivers/scsi/wd7000.c.

wdt= [WDT] Watchdog
See Documentation/watchdog/wdt.txt.

xd= [HW,XT] Original XT pre-IDE (RLL encoded) disks.
xd_geo= See header of drivers/block/xd.c.

xirc2ps_cs= [NET,PCMCIA]
Format:
<irq>,<irq_mask>,<io>,<full_duplex>,<do_sound>,<lockup_hack>[,<irq2>[,<irq3>[,<irq4>]]]

norandmaps Don't use address space randomization. Equivalent to
echo 0 > /proc/sys/kernel/randomize_va_space

______________________________________________________________________

TODO:

Add documentation for ALSA options.
Add more DRM drivers.

</pre>

Is PC compatible with kernel

2009-04-03T01:07:14Z

Jzhang88:

<pre>
Boot up PC in debug mode

'''to view hard drive partition'''
#fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 20349 156280288+ 7 HPFS/NTFS

Partition table entries are not disk order

'''to view NIC settings'''
#ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:22:33:44:55
inet addr:192.168.1.252 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
....

lo Link encap:Local Loopback
int addr:127.0.0.1 Mask:255.0.0.0
....

If you do not see any /dev/??? or eth0 then you can try FOG Kernel Updates(require internet access).
WebUI > Other Information > Kernel Updates >Published Kernels
or
Building your own Custom Kernel
http://www.fogproject.org/wiki/index.php?title=FOGUserGuide&Itemid=51#Building_a_Custom_Kernel

</pre>