search

JaKooLit / Debian-Hyprland

Automated Hyprland installer for Debian 13 Trixie and Debian SID (unstable)
GNU General Public License v3.0
667 stars 63 forks source link

Installation with Nvidia #125

Open CentillionJinx opened 1 month ago

CentillionJinx commented 1 month ago

Issue: PXL_20240710_141402698

Steps to recreate: Fresh installation of Kali Linux, as per the video's instructions, except for the download software page (with the desktop env choices) where I opted for all of the tools, but not the desktop env, hence still ending up with a cli interface, and midway through installation (./install.sh), after cloning hyprland, towards the ending iirc, is when u will face this issue. Rebooting just causes kernel panic due to unaccounted nodes. Basically unbootable.

Reason: Possibly ticking yes to the Nvidia option in the installation process. Do relook into it. Shall try without the inbuilt Nvidia altercation, and update accordingly.

JaKooLit commented 1 month ago

Debian being Debian........

its the same issue when installing SDDM https://github.com/JaKooLit/Debian-Hyprland/issues/2

Suggest the following Reboot - force reboot if necessary cd Debian-Hyprland ./install-scripts/nvidia.sh

once nvidia is succesfully installed reboot

and then re-ran the install.sh again

CentillionJinx commented 1 month ago

Re run install.sh without Nvidia option?

JaKooLit commented 1 month ago

Re run install.sh without Nvidia option?

suggest to fix the nvidia first

if you have nvidia of course

CentillionJinx commented 1 month ago

Didn't resolve the problem. Unfortunately I too am not sure what exactly is the problem since, the installation was normal, I ran nvidia.sh and rebooted prior to install.sh, where I specified that I do not have a Nvidia GPU, and the installation was completed, prompting me to reboot, which thereafter, booted and got stuck on wifi firmware issue which doesn't even make sense to me. So yea stuck at that point (stuck as in not explicit error but just not moving forward with the boot sequence, hence causing me to speculate it's not necessarily the iwl's issue which is stopping boot, idk tbh)