The freeze is ofcourse if you install any Nvidia Drivers. ATM all i can do is run it without using my fans.

Can you please add more detail on how to reproduce this issue? So far, we have not seen anyone able to reproduce it.

The issue happen for me too.

The steps are

1. First i have Geforce RTX 3060
2. I used the last image 2023.4
3. I try to simple install with gnome on X11
4. The installed are well, when i reboot the computer can´t boot, in my case i have a black screen and keyboard does not respond.

Another important thing:

• I repeat the process, but i used the live cd for install and works well, but the driver nouveau not working. In this case i need to change driver for de factory. For these i do blacklist on nouveau and remove all nvidia packages. After i install factory driver and works well.

For Finish 2 problems in my view

The default driver not working, in my case Geforce RTX 3060
For some reason the live CD works better installed only (not hang on boot)

We released Kali 2024.1 last week, so if anyone has time, it would help to try it out, and confirm that the issue is still present with Kali 2024.1. Thanks in advance.

Yes the issue was solved on 2024.1

Fresh install or apt-get full-upgrade solve this issue. If they can't format boot on rescue mode and run full-upgrade

Cant find that on Nvidias page Debian 13 would have support and its still running Debian 13? Or is it a work around? Im afraid of having a black screen/hang after grub again without option to f7 and loose a bunch of work aswell as configs etc again.. If im not this time able to change drivers from chroot and a live usb as i know the issue this time. And will the install from Kalis website work?

Anyone have any updates?

no one?

Tried to install it still doesnt work instant hang/blackscreen after grub... please fix this im frying my GPU...

Not even sure if the Kali team actually knows what is getting reported here (the issue is IMHO quite confusingly written) and even not sure if the Kali team can fix this or if needs to be fixed by Linux Kernel or Nvidia...

Try loading without the splash. I tried I don't know how many different nvidia drivers, only to get the black screen after grub. SInce I've turned off the splash I haven't had any issues.

arnaudr, it is still present in 2024.1. I'm running an RTX 2060 Super and I've had a hell of a time getting nvidia drivers installed. If I disable the splash I'm able to login though, no freeze at the black screen. That is with a fresh install and only changes being made are the nvidia drivers.

Anyone considered that this could be an issue in the Nvidia drivers which is probably not maintained by the Kali team and as such out of their control?

All I know is that I'm not having any issues after removing the splash at login and that there seems to be an issue between Kali and any nvidia drivers. I know I tried numerous nvidia drivers and they all gave me pretty much the same trouble. I know I didn't even think about installing drivers when I first installed Kali. It wasn't until I realized the constant lightDM crashes I was experiencing was caused by the nouveau drivers or kernel module that came with the Kali install.

What do you mean with the splash @pBear? Well why would they do such a stupid update by changing to Debian 13 from 12 as thats the issue Nvidia says on its page it only support up to 12 if they haven update in couple weeks. This leaves almost 30% of users left for dead. Only way im able to login (found after lots of trial and error) is using recovery mode from advanced options then it loads a prompt which im reffered from to normal login screen. Im also using UEFI and "newer" based CPU and GPU could be that the error doesnt exist on older hardware.

edit: in /etc/default/grub or in /etc/default/grub.d/kali-themes.cfg? did you just comment out the 3 last bash lines in the .cfg file?
edit2 (for Kali team): seems like theres something with grub then?
edit3: according to gpt3 i should remove GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet" in /etc/default/grub, but i already have GRUB_CMDLINE_LINUXDEFAULT="quiet" and it still hangs after grub with a frozen "".

Do you think you could share your /etc/default/grub.d/kali-themes.cfg and /etc/default/grub @pBear?

Mine look like this, /etc/default/grub.d/kali-themes.cfg:

#Try to force a 16x9 mode first, then 16x10, then default
GRUB_GFXMODE="1280x720,1280x800,auto"
GRUB_THEME="/boot/grub/themes/kali/theme.txt"
#Add splash option to enable plymouth
if ! echo "$GRUB_CMDLINE_LINUX_DEFAULT" | grep -q splash; then
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT splash"
fi

/etc/default/grub:

#If you change this file, run 'update-grub' afterwards to update
#/boot/grub/grub.cfg.
#For full documentation of the options in this file, see:
#info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=lsb_release -i -s 2> /dev/null || echo Debian
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

#If your computer has multiple operating systems installed, then you
#probably want to run os-prober. However, if your computer is a host
#for guest OSes installed via LVM or raw disk devices, running
#os-prober can cause damage to those guest OSes as it mounts
#filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false

#Uncomment to enable BadRAM filtering, modify to suit your needs
#This works with Linux (no patch required) and with any kernel that obtains
#the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

#Uncomment to disable graphical terminal
#GRUB_TERMINAL=console

#The resolution used on graphical terminal
#note that you can use only modes which your graphic card supports via VBE
#you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

#Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

#Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

#Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

I believe the error is here but burther info would be good:
if ! echo "$GRUB_CMDLINE_LINUX_DEFAULT" | grep -q splash; then
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT splash"
fi

Update, tried to edit kali-themes.cfg to:
#Try to force a 16x9 mode first, then 16x10, then default
GRUB_GFXMODE="1280x720,1280x800,auto"
GRUB_THEME="/boot/grub/themes/kali/theme.txt"
#Add splash option to enable plymouth
if ! echo "$GRUB_CMDLINE_LINUX_DEFAULT"; then
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT"
fi

Aswell as commenting it out but neither worked. Still same _ hang. Also looks like Nvidia have added some support for Debian 13/"sid" https://wiki.debian.org/NvidiaGraphicsDrivers.

@0xgreyhound sorry, just saw this. By splash I mean the splash screen that shows up during boot, after the boot menu. I believe it's also referred to as Plymouth. That I could be wrong about. You can try it by pushing 'E' at the boot menu to edit whichever boot option you currently have highlighted and then at the end of one of the lines there is 'ro quiet splash' Just remove splash and see if you can boot that way. It's worked for me, then you can edit it out of your grub config.

Sorry about the formatting... Anyone able to point me to a link where I can find some info on formatting

I didn't make any changes to my grub files on this install. I used grub-customizer.

kali-themes.cfg:

#Try to force a 16x9 mode first, then 16x10, then default
GRUB_GFXMODE="1280x720,1280x800,auto"
GRUB_THEME="/boot/grub/themes/kali/theme.txt"
#Add splash option to enable plymouth
if ! echo "$GRUB_CMDLINE_LINUX_DEFAULT" | grep -q splash; then
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT splash"
fi

grub:
#If you change this file, run 'update-grub' afterwards to update
#/boot/grub/grub.cfg.
#For full documentation of the options in this file, see:
#info -f grub -n 'Simple configuration'

GRUB_DEFAULT="0"
GRUB_TIMEOUT="3"
GRUB_DISTRIBUTOR="lsb_release -i -s 2> /dev/null || echo Debian"
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

#If your computer has multiple operating systems installed, then you
#probably want to run os-prober. However, if your computer is a host
#for guest OSes installed via LVM or raw disk devices, running
#os-prober can cause damage to those guest OSes as it mounts
#filesystems to look for things.
GRUB_DISABLE_OS_PROBER="true"

#Uncomment to enable BadRAM filtering, modify to suit your needs
#This works with Linux (no patch required) and with any kernel that obtains
#the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

#Uncomment to disable graphical terminal
#GRUB_TERMINAL="console"

#The resolution used on graphical terminal
#note that you can use only modes which your graphic card supports via VBE
#you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE="1920x1080x24"

#Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"

#Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

#Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

export GRUB_MENU_PICTURE="/usr/share/backgrounds/kali-16x9/backtrack-1-hand.png"
#GRUB_THEME="/boot/grub/themes/kali/theme.txt"
export GRUB_COLOR_NORMAL="light-cyan/black"
export GRUB_COLOR_HIGHLIGHT="red/black"

I have a similar problem with 2024.1. I made a fresh single boot install with no issues, everything installed as expected and booted up just fine. After installing the proprietary nVidia drivers as outlined in the Kali documentation, my system would freeze immediately after grub. I tinkered with this for weeks and somehow discovered that my system will boot just fine if I hit "e" on the grub screen and remove the "splash" parameter.

I'd be happy to provide some logs if that would be helpful but I'd just need a quick bit of guidance finding the correct log files (i'm still new to linux".

If this problem is with the proprietary Nvidia driver some one probably should report a bug to Nvidia.