Pressing Ctrl-X or F10 does not boot Linux

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

up vote
2
down vote

favorite

1

I am new to Linux and trying out different distros. However, my laptop has ATI GPU (Asus N56D) due to which many distros didn’t boot successfully. After having google’d I found that I need to set "NOMODESET" kernel parameter.

I could edit the grub command line (by pressing ‘e’ at the grub) but unable to boot after pressing Ctrl+X or F10. Pressing Ctrl+X merely results in adding character 'x' at the cursor position. (This happens irrespective of linux distro).

Due to this I am unable to boot with the kernel parameter. Please suggest what is going wrong here.

share|improve this question

  • Are you able to get it boot without your additional parameter? And also, it’s nomodeset, no nomodset.
    – Risto Salminen
    Dec 6 ’13 at 9:58

  • @RistoSalminen Without additional parameter I can proceed further, but drops into shell prompt and no GUI.
    – Vaman Kulkarni
    Dec 6 ’13 at 11:07

  • So it happens only when you have set nomodeset parameter to kernel, that pressing Ctrl-x just adds ‘x’ there?
    – Risto Salminen
    Dec 6 ’13 at 11:08

  • Yes..thats right. After editing I am not able to get those changes into effect since Ctrl-X doesn’t work. I had to press Esc to discard changes.
    – Vaman Kulkarni
    Dec 6 ’13 at 12:28

  • Well, that’s such an interesting behaviour. I think this should be possible: when you have edited the cmdline, just press Enter and then b.
    – Risto Salminen
    Dec 6 ’13 at 12:38

up vote
2
down vote

favorite

1

I am new to Linux and trying out different distros. However, my laptop has ATI GPU (Asus N56D) due to which many distros didn’t boot successfully. After having google’d I found that I need to set "NOMODESET" kernel parameter.

I could edit the grub command line (by pressing ‘e’ at the grub) but unable to boot after pressing Ctrl+X or F10. Pressing Ctrl+X merely results in adding character 'x' at the cursor position. (This happens irrespective of linux distro).

Due to this I am unable to boot with the kernel parameter. Please suggest what is going wrong here.

share|improve this question

  • Are you able to get it boot without your additional parameter? And also, it’s nomodeset, no nomodset.
    – Risto Salminen
    Dec 6 ’13 at 9:58

  • @RistoSalminen Without additional parameter I can proceed further, but drops into shell prompt and no GUI.
    – Vaman Kulkarni
    Dec 6 ’13 at 11:07

  • So it happens only when you have set nomodeset parameter to kernel, that pressing Ctrl-x just adds ‘x’ there?
    – Risto Salminen
    Dec 6 ’13 at 11:08

  • Yes..thats right. After editing I am not able to get those changes into effect since Ctrl-X doesn’t work. I had to press Esc to discard changes.
    – Vaman Kulkarni
    Dec 6 ’13 at 12:28

  • Well, that’s such an interesting behaviour. I think this should be possible: when you have edited the cmdline, just press Enter and then b.
    – Risto Salminen
    Dec 6 ’13 at 12:38

up vote
2
down vote

favorite

1

up vote
2
down vote

favorite

1
1

I am new to Linux and trying out different distros. However, my laptop has ATI GPU (Asus N56D) due to which many distros didn’t boot successfully. After having google’d I found that I need to set "NOMODESET" kernel parameter.

I could edit the grub command line (by pressing ‘e’ at the grub) but unable to boot after pressing Ctrl+X or F10. Pressing Ctrl+X merely results in adding character 'x' at the cursor position. (This happens irrespective of linux distro).

Due to this I am unable to boot with the kernel parameter. Please suggest what is going wrong here.

share|improve this question

I am new to Linux and trying out different distros. However, my laptop has ATI GPU (Asus N56D) due to which many distros didn’t boot successfully. After having google’d I found that I need to set "NOMODESET" kernel parameter.

I could edit the grub command line (by pressing ‘e’ at the grub) but unable to boot after pressing Ctrl+X or F10. Pressing Ctrl+X merely results in adding character 'x' at the cursor position. (This happens irrespective of linux distro).

Due to this I am unable to boot with the kernel parameter. Please suggest what is going wrong here.

linux grub2

share|improve this question

share|improve this question

share|improve this question

share|improve this question

edited Dec 26 ’13 at 17:49

hildred

4,71122137

4,71122137

asked Dec 6 ’13 at 6:27

Vaman Kulkarni

12113

12113

  • Are you able to get it boot without your additional parameter? And also, it’s nomodeset, no nomodset.
    – Risto Salminen
    Dec 6 ’13 at 9:58

  • @RistoSalminen Without additional parameter I can proceed further, but drops into shell prompt and no GUI.
    – Vaman Kulkarni
    Dec 6 ’13 at 11:07

  • So it happens only when you have set nomodeset parameter to kernel, that pressing Ctrl-x just adds ‘x’ there?
    – Risto Salminen
    Dec 6 ’13 at 11:08

  • Yes..thats right. After editing I am not able to get those changes into effect since Ctrl-X doesn’t work. I had to press Esc to discard changes.
    – Vaman Kulkarni
    Dec 6 ’13 at 12:28

  • Well, that’s such an interesting behaviour. I think this should be possible: when you have edited the cmdline, just press Enter and then b.
    – Risto Salminen
    Dec 6 ’13 at 12:38

  • Are you able to get it boot without your additional parameter? And also, it’s nomodeset, no nomodset.
    – Risto Salminen
    Dec 6 ’13 at 9:58

  • @RistoSalminen Without additional parameter I can proceed further, but drops into shell prompt and no GUI.
    – Vaman Kulkarni
    Dec 6 ’13 at 11:07

  • So it happens only when you have set nomodeset parameter to kernel, that pressing Ctrl-x just adds ‘x’ there?
    – Risto Salminen
    Dec 6 ’13 at 11:08

  • Yes..thats right. After editing I am not able to get those changes into effect since Ctrl-X doesn’t work. I had to press Esc to discard changes.
    – Vaman Kulkarni
    Dec 6 ’13 at 12:28

  • Well, that’s such an interesting behaviour. I think this should be possible: when you have edited the cmdline, just press Enter and then b.
    – Risto Salminen
    Dec 6 ’13 at 12:38

Are you able to get it boot without your additional parameter? And also, it’s nomodeset, no nomodset.
– Risto Salminen
Dec 6 ’13 at 9:58

Are you able to get it boot without your additional parameter? And also, it’s nomodeset, no nomodset.
– Risto Salminen
Dec 6 ’13 at 9:58

@RistoSalminen Without additional parameter I can proceed further, but drops into shell prompt and no GUI.
– Vaman Kulkarni
Dec 6 ’13 at 11:07

@RistoSalminen Without additional parameter I can proceed further, but drops into shell prompt and no GUI.
– Vaman Kulkarni
Dec 6 ’13 at 11:07

So it happens only when you have set nomodeset parameter to kernel, that pressing Ctrl-x just adds ‘x’ there?
– Risto Salminen
Dec 6 ’13 at 11:08

So it happens only when you have set nomodeset parameter to kernel, that pressing Ctrl-x just adds ‘x’ there?
– Risto Salminen
Dec 6 ’13 at 11:08

Yes..thats right. After editing I am not able to get those changes into effect since Ctrl-X doesn’t work. I had to press Esc to discard changes.
– Vaman Kulkarni
Dec 6 ’13 at 12:28

Yes..thats right. After editing I am not able to get those changes into effect since Ctrl-X doesn’t work. I had to press Esc to discard changes.
– Vaman Kulkarni
Dec 6 ’13 at 12:28

Well, that’s such an interesting behaviour. I think this should be possible: when you have edited the cmdline, just press Enter and then b.
– Risto Salminen
Dec 6 ’13 at 12:38

Well, that’s such an interesting behaviour. I think this should be possible: when you have edited the cmdline, just press Enter and then b.
– Risto Salminen
Dec 6 ’13 at 12:38

1 Answer
1

active

oldest

votes

up vote
1
down vote

I had the same problem and the following worked out:

Ctrl+Shift+fn+F10

share|improve this answer

    Your Answer

    StackExchange.ready(function() {
    var channelOptions = {
    tags: “”.split(” “),
    id: “106”
    };
    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’,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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

    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f103989%2fpressing-ctrl-x-or-f10-does-not-boot-linux%23new-answer’, ‘question_page’);
    }
    );

    Post as a guest

    Required, but never shown

    1 Answer
    1

    active

    oldest

    votes

    1 Answer
    1

    active

    oldest

    votes

    active

    oldest

    votes

    active

    oldest

    votes

    up vote
    1
    down vote

    I had the same problem and the following worked out:

    Ctrl+Shift+fn+F10

    share|improve this answer

      up vote
      1
      down vote

      I had the same problem and the following worked out:

      Ctrl+Shift+fn+F10

      share|improve this answer

        up vote
        1
        down vote

        up vote
        1
        down vote

        I had the same problem and the following worked out:

        Ctrl+Shift+fn+F10

        share|improve this answer

        I had the same problem and the following worked out:

        Ctrl+Shift+fn+F10

        share|improve this answer

        share|improve this answer

        share|improve this answer

        edited Nov 24 ’16 at 5:06

        Tomasz

        8,81852863

        8,81852863

        answered Nov 24 ’16 at 3:41

        loguem

        111

        111

            draft saved
            draft discarded

            Thanks for contributing an answer to Unix & Linux Stack Exchange!

            • Please be sure to answer the question. Provide details and share your research!

            But avoid

            • Asking for help, clarification, or responding to other answers.
            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.

            Some of your past answers have not been well-received, and you’re in danger of being blocked from answering.

            Please pay close attention to the following guidance:

            • Please be sure to answer the question. Provide details and share your research!

            But avoid

            • Asking for help, clarification, or responding to other answers.
            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.

            draft saved

            draft discarded

            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin(‘.new-post-login’, ‘https%3a%2f%2funix.stackexchange.com%2fquestions%2f103989%2fpressing-ctrl-x-or-f10-does-not-boot-linux%23new-answer’, ‘question_page’);
            }
            );

            Post as a guest

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Required, but never shown

            Related Post

            Leave a Reply

            Your email address will not be published. Required fields are marked *