Kali Linux 2016.1 Command buffer error
up vote
-1
down vote
favorite
I installed Kali 2016.1 (Rolling) version in VMWare Workstation. After installation of Kali and installing VMWare Tools, I noticed that the kernel release version was kali-4.3.0. I proceeded with upgrading it to a later version by modifying the /etc/apt/sources.list file with the URL to the rolling repo:
sudo apt-get update
sudo apt-get dist-upgrade
reboot
The upgrade appears to have happened successfully, however, the reboot simply ends up with a black screen. I changed to a tty screen by pressing ctrl+Alt+F3 and then typed in
service gdm3 restart
I am still left with a black screen error.
I noticed that the dmesg log file is full of the following error messages:
[drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command buffer error.
I do notice that the kernel version has upgraded as running
uname -r
returns
4.6.0-kali1-686-pae
Any pointers on what could be happening here?
Thanks
John
kali-linux
add a comment |
up vote
-1
down vote
favorite
I installed Kali 2016.1 (Rolling) version in VMWare Workstation. After installation of Kali and installing VMWare Tools, I noticed that the kernel release version was kali-4.3.0. I proceeded with upgrading it to a later version by modifying the /etc/apt/sources.list file with the URL to the rolling repo:
sudo apt-get update
sudo apt-get dist-upgrade
reboot
The upgrade appears to have happened successfully, however, the reboot simply ends up with a black screen. I changed to a tty screen by pressing ctrl+Alt+F3 and then typed in
service gdm3 restart
I am still left with a black screen error.
I noticed that the dmesg log file is full of the following error messages:
[drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command buffer error.
I do notice that the kernel version has upgraded as running
uname -r
returns
4.6.0-kali1-686-pae
Any pointers on what could be happening here?
Thanks
John
kali-linux
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I installed Kali 2016.1 (Rolling) version in VMWare Workstation. After installation of Kali and installing VMWare Tools, I noticed that the kernel release version was kali-4.3.0. I proceeded with upgrading it to a later version by modifying the /etc/apt/sources.list file with the URL to the rolling repo:
sudo apt-get update
sudo apt-get dist-upgrade
reboot
The upgrade appears to have happened successfully, however, the reboot simply ends up with a black screen. I changed to a tty screen by pressing ctrl+Alt+F3 and then typed in
service gdm3 restart
I am still left with a black screen error.
I noticed that the dmesg log file is full of the following error messages:
[drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command buffer error.
I do notice that the kernel version has upgraded as running
uname -r
returns
4.6.0-kali1-686-pae
Any pointers on what could be happening here?
Thanks
John
kali-linux
I installed Kali 2016.1 (Rolling) version in VMWare Workstation. After installation of Kali and installing VMWare Tools, I noticed that the kernel release version was kali-4.3.0. I proceeded with upgrading it to a later version by modifying the /etc/apt/sources.list file with the URL to the rolling repo:
sudo apt-get update
sudo apt-get dist-upgrade
reboot
The upgrade appears to have happened successfully, however, the reboot simply ends up with a black screen. I changed to a tty screen by pressing ctrl+Alt+F3 and then typed in
service gdm3 restart
I am still left with a black screen error.
I noticed that the dmesg log file is full of the following error messages:
[drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command buffer error.
I do notice that the kernel version has upgraded as running
uname -r
returns
4.6.0-kali1-686-pae
Any pointers on what could be happening here?
Thanks
John
kali-linux
kali-linux
asked Jun 23 '16 at 12:18
John
223210
223210
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
This Tip taken (from Pavel Rizzo): Kali Linux 2.0 broken, doesn't boot
It appears that one way to work around this issue is to install lightdm by dropping to the shell (tty2 - ctrl + alt + F2) and typing in:
sudo apt-get install lightdm
Choosing lightdm as default and then
sudo reboot
appears to bring up the kali login screen as GUI.
add a comment |
up vote
0
down vote
On grub screen press e to open grub parameters. Replace quiet
with nomodeset quiet splash
. To make this change permanent once you reach desktop, edit the same in /etc/default/grub
and run sudo update-grub
1
Can you explain why this would solve the problem? Please do not respond in comments; edit your answer to make it clearer and more complete.
– G-Man
Dec 7 at 20:30
add a comment |
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',
autoActivateHeartbeat: false,
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
});
}
});
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%2f291616%2fkali-linux-2016-1-command-buffer-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
This Tip taken (from Pavel Rizzo): Kali Linux 2.0 broken, doesn't boot
It appears that one way to work around this issue is to install lightdm by dropping to the shell (tty2 - ctrl + alt + F2) and typing in:
sudo apt-get install lightdm
Choosing lightdm as default and then
sudo reboot
appears to bring up the kali login screen as GUI.
add a comment |
up vote
1
down vote
This Tip taken (from Pavel Rizzo): Kali Linux 2.0 broken, doesn't boot
It appears that one way to work around this issue is to install lightdm by dropping to the shell (tty2 - ctrl + alt + F2) and typing in:
sudo apt-get install lightdm
Choosing lightdm as default and then
sudo reboot
appears to bring up the kali login screen as GUI.
add a comment |
up vote
1
down vote
up vote
1
down vote
This Tip taken (from Pavel Rizzo): Kali Linux 2.0 broken, doesn't boot
It appears that one way to work around this issue is to install lightdm by dropping to the shell (tty2 - ctrl + alt + F2) and typing in:
sudo apt-get install lightdm
Choosing lightdm as default and then
sudo reboot
appears to bring up the kali login screen as GUI.
This Tip taken (from Pavel Rizzo): Kali Linux 2.0 broken, doesn't boot
It appears that one way to work around this issue is to install lightdm by dropping to the shell (tty2 - ctrl + alt + F2) and typing in:
sudo apt-get install lightdm
Choosing lightdm as default and then
sudo reboot
appears to bring up the kali login screen as GUI.
edited Apr 13 '17 at 12:36
Community♦
1
1
answered Jun 23 '16 at 12:22
John
223210
223210
add a comment |
add a comment |
up vote
0
down vote
On grub screen press e to open grub parameters. Replace quiet
with nomodeset quiet splash
. To make this change permanent once you reach desktop, edit the same in /etc/default/grub
and run sudo update-grub
1
Can you explain why this would solve the problem? Please do not respond in comments; edit your answer to make it clearer and more complete.
– G-Man
Dec 7 at 20:30
add a comment |
up vote
0
down vote
On grub screen press e to open grub parameters. Replace quiet
with nomodeset quiet splash
. To make this change permanent once you reach desktop, edit the same in /etc/default/grub
and run sudo update-grub
1
Can you explain why this would solve the problem? Please do not respond in comments; edit your answer to make it clearer and more complete.
– G-Man
Dec 7 at 20:30
add a comment |
up vote
0
down vote
up vote
0
down vote
On grub screen press e to open grub parameters. Replace quiet
with nomodeset quiet splash
. To make this change permanent once you reach desktop, edit the same in /etc/default/grub
and run sudo update-grub
On grub screen press e to open grub parameters. Replace quiet
with nomodeset quiet splash
. To make this change permanent once you reach desktop, edit the same in /etc/default/grub
and run sudo update-grub
answered Dec 7 at 20:21
Dennis
1
1
1
Can you explain why this would solve the problem? Please do not respond in comments; edit your answer to make it clearer and more complete.
– G-Man
Dec 7 at 20:30
add a comment |
1
Can you explain why this would solve the problem? Please do not respond in comments; edit your answer to make it clearer and more complete.
– G-Man
Dec 7 at 20:30
1
1
Can you explain why this would solve the problem? Please do not respond in comments; edit your answer to make it clearer and more complete.
– G-Man
Dec 7 at 20:30
Can you explain why this would solve the problem? Please do not respond in comments; edit your answer to make it clearer and more complete.
– G-Man
Dec 7 at 20:30
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%2f291616%2fkali-linux-2016-1-command-buffer-error%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