Kernel parameters - Revision history

TpUser0: PAE linked

2017-03-12T16:09:49Z

PAE linked

TpUser0: /* Typical parameters used on ThinkPads */ lapic, forcepae

2017-03-12T14:15:22Z

‎Typical parameters used on ThinkPads: lapic, forcepae

Thinker: /* Typical parameters used on ThinkPads */ - SATA problems

2006-03-10T13:32:23Z

‎Typical parameters used on ThinkPads: - SATA problems

Thinker: /* Typical parameters used on ThinkPads */ - suspend2

2006-03-10T13:27:41Z

‎Typical parameters used on ThinkPads: - suspend2

Wyrfel: /* Framebuffer related parameters for ThinkPads */

2006-03-10T01:05:04Z

‎Framebuffer related parameters for ThinkPads

Wyrfel at 01:03, 10 March 2006

2006-03-10T01:03:33Z

Wyrfel at 09:53, 14 October 2005

2005-10-14T09:53:44Z

Wyrfel at 10:20, 2 August 2005

2005-08-02T10:20:30Z

84.191.152.242 at 15:28, 1 August 2005

2005-08-01T15:28:39Z

84.191.152.242 at 14:41, 1 August 2005

2005-08-01T14:41:20Z

@@ Line 34: / Line 34: @@
 | {{bootparm|speedstep_coppermine|???}} || supposed to tell the kernel that you have a speedstep capable coppermine processor, but could possibly not work anymore with newer kernels
 |-
-| {{bootparm|forcepae|}} || tells the kernel that the CPU supports Physical Address Extension (PAE), even if it is not the list of supported CPU flags (see [[Intel Pentium M (Dothan)]])
+| {{bootparm|forcepae|}} || tells the kernel that the CPU supports [[PAE|Physical Address Extension (PAE)]], even if it is not the list of supported CPU flags (see [[Intel Pentium M (Dothan)|Pentium M Dothan]])
 |-
 |}

@@ Line 23: / Line 23: @@
 |-
 | {{bootparm|nolapic|}} || tells the kernel not to use the local APIC (use if you have problems with ACPI)
 |-
 | {{bootparm|noresume|}}<br />{{bootparm|noresume2|}} || boots without resuming after a suspend-to-disk (for [[swsusp]] and [[Software Suspend 2|suspend2]], respectively)
@@ Line 31: / Line 33: @@
 |-
 | {{bootparm|speedstep_coppermine|???}} || supposed to tell the kernel that you have a speedstep capable coppermine processor, but could possibly not work anymore with newer kernels
 |-
 |}

@@ Line 15: / Line 15: @@
 |-
 | {{bootparm|acpi_sleep|s3_bios}} || makes the system call the video BIOS to reenable video on resume from suspend-to-ram (use this if you experience a blank display after resume while your system seems elsewise awake)
 |-
 | {{bootparm|idebus|66}} || set IDE bus speed to 66 MHz (66 is maximum supported)

@@ Line 20: / Line 20: @@
 | {{bootparm|nolapic|}} || tells the kernel not to use the local APIC (use if you have problems with ACPI)
 |-
-| {{bootparm|noresume|}} || boots without resuming after a suspend-to-disk
+| {{bootparm|noresume|}}<br />{{bootparm|noresume2|}} || boots without resuming after a suspend-to-disk (for [[swsusp]] and [[Software Suspend 2|suspend2]], respectively)
 |-
-| {{bootparm|resume|/dev/hdaX}} || tells the kernel where to find the suspend-to-disk image to resume from
+| {{bootparm|resume|/dev/hdaX}}<br />{{bootparm|resume2|/dev/hdaX}} || tells the kernel where to find the suspend-to-disk image to resume from (for [[swsusp]] and [[Software Suspend 2|suspend2]], respectively)
 |-
 | {{bootparm|root|/dev/hdaX}} || tells the kernel where to find the root filesystem
@@ Line 29: / Line 29: @@
 |-
 |}
 ==Framebuffer related parameters for ThinkPads==
 The following table gives an overview of the kernel parameters typically needed on ThinkPads.

@@ Line 36: / Line 36: @@
 |-
 | {{bootparm|vga|835}} || for 1400x1050 framebuffer resolution
 |-
 | {{bootparm|video|radeonfb:vesa:1400x1050-32@60}}  || for using accelerated radeonfb framebuffer

@@ Line 27: / Line 27: @@
 |-
 | {{bootparm|speedstep_coppermine|???}} || supposed to tell the kernel that you have a speedstep capable coppermine processor, but could possibly not work anymore with newer kernels
 |-
 | {{bootparm|vga|835}} || for 1400x1050 framebuffer resolution
@@ Line 33: / Line 40: @@
 |-
 |}
 [[Category:Glossary]]

← Older revision		Revision as of 09:53, 14 October 2005
Line 1:		Line 1:
−	Some aspects of the Linux kernels behaviour are controllable via so called kernel parameters. These are parameters similar to the ones that you would provide for a command like {{~~cmd~~\|ls}} or {{~~cmd~~\|cp}} in a shell, only that they are appended to the kernel/image line in your bootmanagers config file (for lilo this would typically be {{path\|/etc/lilo.conf}}, for grub it would be {{path\|/boot/grub/menu.lst}}).	+	Some aspects of the Linux kernels behaviour are controllable via so called kernel parameters. These are parameters similar to the ones that you would provide for a command like {{cmduser\|ls}} or {{cmduser\|cp}} in a shell, only that they are appended to the kernel/image line in your bootmanagers config file (for lilo this would typically be {{path\|/etc/lilo.conf}}, for grub it would be {{path\|/boot/grub/menu.lst}}).

	An example line from grub could look like this:		An example line from grub could look like this:

@@ Line 12: / Line 12: @@
 ! parameter !! description
 |-
-| acpi=off || disables ACPI (keeps it from overriding APM)
+| {{bootparm|acpi|off}} || disables ACPI (keeps it from overriding APM)
 |-
-| acpi_sleep=s3_bios || makes the system call the video BIOS to reenable video on resume from suspend-to-ram (use this if you experience a blank display after resume while your system seems elsewise awake)
+| {{bootparm|acpi_sleep|s3_bios}} || makes the system call the video BIOS to reenable video on resume from suspend-to-ram (use this if you experience a blank display after resume while your system seems elsewise awake)
 |-
-| idebus=66 || set IDE bus speed to 66 MHz (66 is maximum supported)
+| {{bootparm|idebus|66}} || set IDE bus speed to 66 MHz (66 is maximum supported)
 |-
-| nolapic || tells the kernel not to use the local APIC (use if you have problems with ACPI)
+| {{bootparm|nolapic|}} || tells the kernel not to use the local APIC (use if you have problems with ACPI)
 |-
-| noresume || boots without resuming after a suspend-to-disk
+| {{bootparm|noresume|}} || boots without resuming after a suspend-to-disk
 |-
-| resume=/dev/hdaX || tells the kernel where to find the suspend-to-disk image to resume from
+| {{bootparm|resume|/dev/hdaX}} || tells the kernel where to find the suspend-to-disk image to resume from
 |-
-| root=/dev/hdaX || tells the kernel where to find the root filesystem
+| {{bootparm|root|/dev/hdaX}} || tells the kernel where to find the root filesystem
 |-
-| speedstep_coppermine=??? || supposed to tell the kernel that you have a speedstep capable coppermine processor, but could possibly not work anymore with newer kernels
+| {{bootparm|speedstep_coppermine|???}} || supposed to tell the kernel that you have a speedstep capable coppermine processor, but could possibly not work anymore with newer kernels
 |-
-| vga=835 || for 1400x1050 framebuffer resolution
+| {{bootparm|vga|835}} || for 1400x1050 framebuffer resolution
 |-
-| video=radeonfb:vesa:1400x1050-32@60  || for using accelerated radeonfb framebuffer
+| {{bootparm|video|radeonfb:vesa:1400x1050-32@60}}  || for using accelerated radeonfb framebuffer
 |-
 |}

← Older revision		Revision as of 15:28, 1 August 2005
Line 1:		Line 1:
−	Some aspects of the Linux kernels behaviour are controllable via so called kernel parameters. These are parameters similar to the ones that you would provide for a command like ls or cp in a shell, only that they are appended to the kernel/image line in your bootmanagers config file (for lilo this would typically be {{path\|/etc/lilo.conf}}, for grub it would be {{path\|/boot/grub/menu.lst}}).	+	Some aspects of the Linux kernels behaviour are controllable via so called kernel parameters. These are parameters similar to the ones that you would provide for a command like {{cmd\|ls}} or {{cmd\|cp}} in a shell, only that they are appended to the kernel/image line in your bootmanagers config file (for lilo this would typically be {{path\|/etc/lilo.conf}}, for grub it would be {{path\|/boot/grub/menu.lst}}).

	An example line from grub could look like this:		An example line from grub could look like this:

@@ Line 1: / Line 1: @@
-Some aspects of the Linux kernels behaviour are controllable via so called kernel parameters. These are parameters similar to the ones that you would provide for a command like ls or cp in a shell, only that they are appended to the kernel/image line in your bootmanagers config file (for lilo this would typically be /etc/lilo.conf, for grub it wouuld be /boot/grub/menu.lst).
+Some aspects of the Linux kernels behaviour are controllable via so called kernel parameters. These are parameters similar to the ones that you would provide for a command like ls or cp in a shell, only that they are appended to the kernel/image line in your bootmanagers config file (for lilo this would typically be {{path|/etc/lilo.conf}}, for grub it would be {{path|/boot/grub/menu.lst}}).
 An example line from grub could look like this:
   kernel /lfskernel-2.6.9 root=/dev/hda6 rw idebus=66 vga=791 splash=silent acpi_sleep=s3_bios
-For a complete overview of all available parameters see <code>/lib/modules/`uname -r`/source/Documentation/kernel-parameters.txt</code>.
+For a complete overview of all available parameters see {{path|/lib/modules/`uname -r`/source/Documentation/kernel-parameters.txt}}.
 ==Typical parameters used on ThinkPads==