Stuck in Blackscreen

Karl1903

New Member
Joined
Nov 9, 2024
Messages
1
Reaction score
0
Credits
14
Hey so I got a really big problem with my kali Linux. I don’t know what happened but when I start the computer I can choose between Kali GNU/Linux and Advanced options for Kali GNU/Linux. After it’s automatically choose the first option I get this Blackscreen (like on the picture). I already tried every special Kombination of alt ctrl and everything. I hope someone can help me. btw i am from Germany so I’m sorry for my English.
 

Attachments

  • IMG_4838.jpeg
    IMG_4838.jpeg
    1.5 MB · Views: 58


Hold down the shift key when booting starts.
You will then get a grub console mode menu. The top option should be selected. Press 'e' key to edit that line.
Scroll down to the "Linux /boot/vmlinuz- your kernel-root=UUID.." line. That is the line that tells Grub which kernel to boot with and the parameters to be passed to the kernel when it boots are placed at the end of this line.
Press 'e' key again to edit this line.
Move to the end of the line to the text that says "quiet splash" and then enter "nomodeset" after the word splash and before " mark ensuring there is a space between the new option and any other option.
It should look like "quiet splash nomodeset"
Once you have added the parameter, press Enter to accept the editing.
Then press 'b' to boot using that kernel and those parameters.
 
Hold down the shift key when booting starts.

Potentially the Escape key if installed as UEFI, at least that's what my dim memory is telling me. I haven't had to do this in quite a while.
 
The picture you attached isn't exactly a "black screen", the Kali splash is still there and obscuring some possibly very useful output...

So while a bad video mode is still the most common cause of hangs on boot, it could be a number of other things as. Try @GatorsFan's suggestion and use the "nomodeset" kernel parameter first.

If that doesn't solve it, remove "quiet" and "splash" add "systemd.unit=multi-user.target" so you boot in CLI mode and get all boot messages. Also, if you can boot into CLI mode, you'll be able to at least examine the issue further.
 


Top