Pressing Ctrl-X or F10 does not boot Linux
up vote
2
down vote
favorite
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
|
show 2 more comments
up vote
2
down vote
favorite
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
Are you able to get it boot without your additional parameter? And also, it'snomodeset
, nonomodset
.
– 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 setnomodeset
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 pressEsc
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
|
show 2 more comments
up vote
2
down vote
favorite
up vote
2
down vote
favorite
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
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
linux grub2
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'snomodeset
, nonomodset
.
– 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 setnomodeset
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 pressEsc
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
|
show 2 more comments
Are you able to get it boot without your additional parameter? And also, it'snomodeset
, nonomodset
.
– 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 setnomodeset
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 pressEsc
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
|
show 2 more comments
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
add a comment |
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
add a comment |
up vote
1
down vote
I had the same problem and the following worked out:
Ctrl+Shift+fn+F10
add a comment |
up vote
1
down vote
up vote
1
down vote
I had the same problem and the following worked out:
Ctrl+Shift+fn+F10
I had the same problem and the following worked out:
Ctrl+Shift+fn+F10
edited Nov 24 '16 at 5:06
Tomasz
8,80852863
8,80852863
answered Nov 24 '16 at 3:41
loguem
111
111
add a comment |
add a comment |
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.
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
Required, but never shown
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
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Are you able to get it boot without your additional parameter? And also, it's
nomodeset
, nonomodset
.– 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