Unable to boot a compiled kernel [on hold]
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I am working on a project where I have start of by adding some system calls to a kernel (Linux 3.13.11 to be particular), after adding the calls and writing their prototype in the correct locations across the kernel image.
When I boot it I initially get stuck at: Loading Linux 3.13.11-ckt39-custom..
Loading initial ramdisk
I am by no means professional and unable to proceed from there. I tried removing splash and quiet it doesn't change a thing..and apparently after many tries (sometimes even 2nd try) I get kernel panic
EDIT: I am running on VirtualBox, and I tried without adding systemcalls as default with same issue. Where do you think it is going wrong?
boot linux-kernel grub2 virtual-machine kernel-panic
New contributor
put on hold as too broad by Romeo Ninov, JigglyNaga, Rui F Ribeiro, jimmij, RalfFriedl 2 days ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
1
down vote
favorite
I am working on a project where I have start of by adding some system calls to a kernel (Linux 3.13.11 to be particular), after adding the calls and writing their prototype in the correct locations across the kernel image.
When I boot it I initially get stuck at: Loading Linux 3.13.11-ckt39-custom..
Loading initial ramdisk
I am by no means professional and unable to proceed from there. I tried removing splash and quiet it doesn't change a thing..and apparently after many tries (sometimes even 2nd try) I get kernel panic
EDIT: I am running on VirtualBox, and I tried without adding systemcalls as default with same issue. Where do you think it is going wrong?
boot linux-kernel grub2 virtual-machine kernel-panic
New contributor
put on hold as too broad by Romeo Ninov, JigglyNaga, Rui F Ribeiro, jimmij, RalfFriedl 2 days ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
â JigglyNaga
2 days ago
I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
â Ahmed Nader
6 hours ago
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am working on a project where I have start of by adding some system calls to a kernel (Linux 3.13.11 to be particular), after adding the calls and writing their prototype in the correct locations across the kernel image.
When I boot it I initially get stuck at: Loading Linux 3.13.11-ckt39-custom..
Loading initial ramdisk
I am by no means professional and unable to proceed from there. I tried removing splash and quiet it doesn't change a thing..and apparently after many tries (sometimes even 2nd try) I get kernel panic
EDIT: I am running on VirtualBox, and I tried without adding systemcalls as default with same issue. Where do you think it is going wrong?
boot linux-kernel grub2 virtual-machine kernel-panic
New contributor
I am working on a project where I have start of by adding some system calls to a kernel (Linux 3.13.11 to be particular), after adding the calls and writing their prototype in the correct locations across the kernel image.
When I boot it I initially get stuck at: Loading Linux 3.13.11-ckt39-custom..
Loading initial ramdisk
I am by no means professional and unable to proceed from there. I tried removing splash and quiet it doesn't change a thing..and apparently after many tries (sometimes even 2nd try) I get kernel panic
EDIT: I am running on VirtualBox, and I tried without adding systemcalls as default with same issue. Where do you think it is going wrong?
boot linux-kernel grub2 virtual-machine kernel-panic
boot linux-kernel grub2 virtual-machine kernel-panic
New contributor
New contributor
edited 4 hours ago
New contributor
asked 2 days ago
Ahmed Nader
62
62
New contributor
New contributor
put on hold as too broad by Romeo Ninov, JigglyNaga, Rui F Ribeiro, jimmij, RalfFriedl 2 days ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as too broad by Romeo Ninov, JigglyNaga, Rui F Ribeiro, jimmij, RalfFriedl 2 days ago
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
â JigglyNaga
2 days ago
I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
â Ahmed Nader
6 hours ago
add a comment |Â
Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
â JigglyNaga
2 days ago
I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
â Ahmed Nader
6 hours ago
Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
â JigglyNaga
2 days ago
Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
â JigglyNaga
2 days ago
I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
â Ahmed Nader
6 hours ago
I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
â Ahmed Nader
6 hours ago
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
â JigglyNaga
2 days ago
I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
â Ahmed Nader
6 hours ago