Thanks for the responses. Truly a wonderful community, I feel really welcomed to this new and probably my first (internet) community.
What worked until this point was using chroot to get to TTY using CTRL + ALT + F4
and then login to my account, used the command
startx
to boot in, there were no issues whatsoever from then on, besides small problems which I have described in the original post such as, starship issue on alacritty (which was easily fixed
).
What I have now done to weirdly Fix it
Iāll Give an update on what I have done according to what I was directed by flio & tbg and other posts I found in the forum.
First of all, I feel like I did things in the wrong order, but
my first attempt was to change my display manager version to a developmental version as tbg adviced. I assumed that this means the -git version of my display manager (to be honest, I donāt really know what a display manager really is except some basic understanding from searching it up).
I also assumed that my display manager could be either GDM, LightDM or SDDM as mentioned on the forum.
- I reinstalled Garuda Gnome flavor from scratch again.
- upon installation, followed by a reboot, I was welcomed with the Garuda Assistant prompt,
- Before doing anything here I decided to first switch my DM
- I figured that typing
systemctl status display-manager.service
showed me which Display Manager I was using, which was reported as GDM
I then closed the terminal as the status process was running for this service ? and I was about to change the service soā¦
- Then I opened up the software application (pamac ?) and searched for gdm
The Software app reported a few packages when searched for gdm, I could-not find any version ending with a -git or something like that. There is 3 available, gdm, gdm-prime & gdm-plymouth
Since my Razer Blade laptop has Nvidia Optimus, I went ahead and got the gdm-prime which is for optimus laptops apparently?
Another reason, I chose the GUI software app is because, it reported to me saying, itās gonna remove the existing gdm and replace it with gdm-prime, then I installed it along with all of its dependencies, which auto removed the existing gdm I believe.
Then, I checked for updates, there was no updates apparentlyā¦ so I just rebooted the system.
Unfortunately, the same problem still persistedā¦ so, switching to gdm-prime really did-not do anything for me here. I also tried the same thing with gdm-plymouth again after a second fresh installation of Garuda, and the results were same,
Note that, gdm-plymouth was on version 40.0 apprently ? the others were on 3.XX.X (check and change to real version later)
But on reboot, all 3, gdm, gdm-plymouth and gdm-prime, all looks like the new Gnome 40 desktop, even though the version reported is 3.XX.X.
Here is what I did next, Which Worked (kindah?), Which I should Have Done First
I then went on to what filo recommended me first, about removing āsplashā from the grub string.
this is easily achieved by
hitting the āEā key on Grub load screen
and then searching and removing āsplashā from the string, and using
hitting the CTRL + X key-Combination to continue to boot
This, then with no issues, booted me into my Desktop.
However, the only flaw was that this change is not permanent, similar to using startx to in the tty text terminal when stuck in the blank black screen on boot.
Thereforeā¦
I figured that this grub file must be located somewhere, and went ahead to try and edit the actual file which is read.
I found a few locations where a āgrub configuration fileā was located in my system.
/boot/grub/grub.conf
which Pointed me to the location of the template which is used to generate this file using
grub-mkconfig, the template file was located in
/etc/default
file named as grub
I opened up both files, removed āsplashā from the string, saved it. Rebooted system, Problem still persists. And I checked with hitting āEā on a second reboot to check if the change was applied, it was-not.
I then went ahead, and removed all instances of āsplashā in the main, auto-generated grub.conf file. (I could-not figure out how to make it auto generated using that grub-mkconfig mentioned in the file, as a comment.
Which then, Worked!
when booting in, it does generate some weird [OK] texts for like half a second though, but it does indeed work. Thanks to what filo suggested, I removed 'splashā from grub.
I obviously have a lot of concerns though, First of all, to be completely honest, I have no idea what I am doing, whatsoever, I am afraid this might break my system or somethingā¦ As I do intend to use Garuda as my main system, which will store many of my important files etc.
I know this āsolutionā which worked for me, really is-not a good way to do this, Please do let me know the proper was to go about this and point out my mistakes during this process, I did my best to look up what I can with the time I have.
P.S, I read the post about formatting, posts, I gave it a try, Hope I formatted correctly.
Once again, Thanks for all who are helping me, Much appreciated, Like I said, I am not a tech-savvy person and new to linux, so do explain a bit to your best in reponses. Thanks again 