Ryfujk

What features enable the Su-25 Frogfoot to operate with such a wide variety of fuels?

Why is the Sun approximated as a black body at ~ 5800 K?

15% tax on $7.5k earnings. Is that right?

Doesn't the system of the Supreme Court oppose justice?

Change the color of a single dot in `ddot` symbol

What to do when eye contact makes your coworker uncomfortable?

How can ping know if my host is down

How do I fix the group tension caused by my character stealing and possibly killing without provocation?

Is this toilet slogan correct usage of the English language?

Is this part of the description of the Archfey warlock's Misty Escape feature redundant?

Why is the "ls" command showing permissions of files in a FAT32 partition?

Make a Bowl of Alphabet Soup

Creating two special characters

Stack Interview Code methods made from class Node and Smart Pointers

Does the Linux kernel need a file system to run?

Mimic lecturing on blackboard, facing audience

I found an audio circuit and I built it just fine, but I find it a bit too quiet. How do I amplify the output so that it is a bit louder?

Has the laser at Magurele, Romania reached a tenth of the Sun's power?

Is there a nicer/politer/more positive alternative for "negates"?

What does Apple's new App Store requirement mean

What does "Scientists rise up against statistical significance" mean? (Comment in Nature)

Why does AES have exactly 10 rounds for a 128-bit key, 12 for 192 bits and 14 for a 256-bit key size?

Why do ¬, ∀ and ∃ have the same precedence?

How much theory knowledge is actually used while playing?

Adding Linux kernel command line parameters

Linux command line best practices and tips?Favorite tricks with linux kernel boot parameters?How can i break my own linux kernelHow do I add xen kernel boot parameters in grub2?Choosing a device name under /dev from the kernel command lineRHEL6 kick start fails with kernel panic - not syncing errorIs there a Linux kernel boot parameter to configure an IPv6 address?using Linux as a bootloader?Add generic rescue kernel on GentooSend linux kernel paramters to VM guest in VMware

1 Answer
1

active

oldest

votes

0

If you are using Lilo as a bootloader, edit the relevant part of /etc/lilo.conf to look something like this:

image=/vmlinuz

        label=Linux

        append="vmalloc=foo"

        initrd=/initrd.img

        read-only

        root=/dev/sda1

Then, run lilo(8) to reinstall the bootloader with the new parameter.

Of course, I cannot tell you exactly how your /etc/lilo.conf should look, since this depends on the overall configuration of your system, but the interesting line is the one that reads append=. You can use such a line to pass any desired boot parameter to the kernel.

(If you prefer Grub as a bootloader, this is fine, but someone else must answer your question in that case, for I do not happen to use Grub.)

If you just want to try your vmalloc=foo for one boot, rather than to install it persistently, you can simply type vmalloc=foo or (assuming that you have labeled your kernel as "Linux") Linux vmalloc=foo at the boot prompt. The only trick is getting to the boot prompt, which your bootloader may be configured to suppress. Try holding down the shift key at boot time, which may prevent the bootloader from suppressing the prompt.

share|improve this answer

answered Jul 5 '12 at 1:54

thbthb

1012

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f405280%2fadding-linux-kernel-command-line-parameters%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

If you are using Lilo as a bootloader, edit the relevant part of /etc/lilo.conf to look something like this:

image=/vmlinuz

        label=Linux

        append="vmalloc=foo"

        initrd=/initrd.img

        read-only

        root=/dev/sda1

Then, run lilo(8) to reinstall the bootloader with the new parameter.

Of course, I cannot tell you exactly how your /etc/lilo.conf should look, since this depends on the overall configuration of your system, but the interesting line is the one that reads append=. You can use such a line to pass any desired boot parameter to the kernel.

(If you prefer Grub as a bootloader, this is fine, but someone else must answer your question in that case, for I do not happen to use Grub.)

If you just want to try your vmalloc=foo for one boot, rather than to install it persistently, you can simply type vmalloc=foo or (assuming that you have labeled your kernel as "Linux") Linux vmalloc=foo at the boot prompt. The only trick is getting to the boot prompt, which your bootloader may be configured to suppress. Try holding down the shift key at boot time, which may prevent the bootloader from suppressing the prompt.

share|improve this answer

answered Jul 5 '12 at 1:54

thbthb

1012

add a comment | 

0

If you are using Lilo as a bootloader, edit the relevant part of /etc/lilo.conf to look something like this:

image=/vmlinuz

        label=Linux

        append="vmalloc=foo"

        initrd=/initrd.img

        read-only

        root=/dev/sda1

Then, run lilo(8) to reinstall the bootloader with the new parameter.

Of course, I cannot tell you exactly how your /etc/lilo.conf should look, since this depends on the overall configuration of your system, but the interesting line is the one that reads append=. You can use such a line to pass any desired boot parameter to the kernel.

(If you prefer Grub as a bootloader, this is fine, but someone else must answer your question in that case, for I do not happen to use Grub.)

If you just want to try your vmalloc=foo for one boot, rather than to install it persistently, you can simply type vmalloc=foo or (assuming that you have labeled your kernel as "Linux") Linux vmalloc=foo at the boot prompt. The only trick is getting to the boot prompt, which your bootloader may be configured to suppress. Try holding down the shift key at boot time, which may prevent the bootloader from suppressing the prompt.

share|improve this answer

answered Jul 5 '12 at 1:54

thbthb

1012

add a comment | 

If you are using Lilo as a bootloader, edit the relevant part of /etc/lilo.conf to look something like this:

image=/vmlinuz

        label=Linux

        append="vmalloc=foo"

        initrd=/initrd.img

        read-only

        root=/dev/sda1

Then, run lilo(8) to reinstall the bootloader with the new parameter.

Of course, I cannot tell you exactly how your /etc/lilo.conf should look, since this depends on the overall configuration of your system, but the interesting line is the one that reads append=. You can use such a line to pass any desired boot parameter to the kernel.

(If you prefer Grub as a bootloader, this is fine, but someone else must answer your question in that case, for I do not happen to use Grub.)

If you just want to try your vmalloc=foo for one boot, rather than to install it persistently, you can simply type vmalloc=foo or (assuming that you have labeled your kernel as "Linux") Linux vmalloc=foo at the boot prompt. The only trick is getting to the boot prompt, which your bootloader may be configured to suppress. Try holding down the shift key at boot time, which may prevent the bootloader from suppressing the prompt.

share|improve this answer

answered Jul 5 '12 at 1:54

thbthb

1012

image=/vmlinuz

        label=Linux

        append="vmalloc=foo"

        initrd=/initrd.img

        read-only

        root=/dev/sda1

share|improve this answer

answered Jul 5 '12 at 1:54

thbthb

1012

answered Jul 5 '12 at 1:54

thbthb

1012

answered Jul 5 '12 at 1:54

thbthb

1012