
- #KALI LINUX STARTX NOT FOUND DRIVERS#
- #KALI LINUX STARTX NOT FOUND DRIVER#
- #KALI LINUX STARTX NOT FOUND SOFTWARE#
If only I could find a way to start i3 using my normal config file I might have access to my desktop and make finding a solution more easier. I tried to solve config file issue by using i3 -c In my xinitrx, but it wouldn't start with sudo startx Once in while sudo startxmight allow me to start a session, but it would be in root, I wouldn't have my usual config, it would use the default config in /etc/i3/config, also while in i3 I would be able to exist with the default command. I decided to reinstall all xorg related packages and remove my configs and reinstall my display driver, that's xf86-video-amdgpu, but still, to no avail, it doesn't start. I tried using an older version of xinit, nothing. it will then give gui with startx command as well. you can later make a symbolic link to gdm3 with the name startx. I decide to open use xinit to start the display, using xinit - :1, nothing. its not backtrack 5 to use startx command for gui in kali use gdm3 command.

I decided to run startx, to restart X, nothing. final choice is re-install from scratch obviously.I restarted i3 using it's default restart command mod+shift+r, and suddenly I was existed out of my current session.Depending on the error message you can make the necessary modifications to get your system back to normal Use the start, X, and gdm3 commands (and services) at the terminal and see if any errors show up. something else I'd be trying is to use the terminal interface to your advantage.If you cannot log in to GUI by 'startx', there may be graphics issues. If GUI is not displayed, press CTRL+ALT+F1 to go back to tty1 (CLI). If GUI is not displayed, press ALT+SysRq+R and then press CTRL+ALT+F7. Log in to CLI with non-root user and execute 'startx'. For instance, /var/log/Xorg.0.log ones related to X, dmesg for ones related to the kernel, /var/log/dpkg.log for ones related to packaging, etc. Generally speaking, logging in to GUI with root privilege on debian is not good. That way you can narrow down which log files you should be consulting.

Namely, does it feel like it proceeds all the way like it used to or does it drop at the final few moments with X simply not working.

#KALI LINUX STARTX NOT FOUND DRIVER#
Basically, when I upgraded the rest of the system the binary driver itself wouldn't work because it needed to be re-compiled to suit the updated circumstances
#KALI LINUX STARTX NOT FOUND DRIVERS#
I remember in the past when I had to deal with Nvidia drivers I experienced something similar.

Try: systemctl enable gdm systemctl start gdm.
#KALI LINUX STARTX NOT FOUND SOFTWARE#
