Briefly describe your issue below:
Hello,
So I’m a new user, (that’s maybe the cause of the error…) and I tried to install the Nvidia drivers with the help of this link : https://docs.parrotlinux.org/info/gpu-drivers/
I followed the step, and all seems to be good until the installation of Bumblebee and Primus.
At this step, my computer started making some huge noise (probably because the graphic card started) , and the troubles begun. When it comes to the optirun line, here’s the response :
[ 228.313710] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Problem parsing the config file[ 228.313749] [ERROR]Aborting because fallback start is disabled.
At first I wasn’t paying attention (that’s dumb) and I rebooted. At the start, I got the message below the post, and could not start Parrot in any way. I had to get to the recovery mode to delete Bumblebee and Optimus , rebooted, and it worked as in the beginning. I retried with the .run file on nvidia’s website, retried with the original link and the same thing occurred. I tried googling the first error message (the optirun one), and followed another link that told me to change a value in the xorg.conf.nvidia file, I rebooted, that did not help.
I searched on multiple forum, but did not found anything that worked.
I would appreciate any suggestion, because I need to work with graphic-vacuum software soon.
Thanks for reading and taking the time to respond me, and again please be kind with me, or I’ll call my mom.
What version of Parrot are you running? (include version (e.g. 4.6), edition(e.g. Home//KDE/OVA, etc.), and architecture (currently we only support amd64)
I tried on an Asus laptop, with a GTX 1050 ti, and the latest build of Parrotsec Mate edition (4.8).
What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)
Debian standard
Configured to multiboot with other systems? (yes / no)
yes
If there are any similar issues or solutions, link to them below:
If there are any error messages or relevant logs, post them below:
Picture of the screen with the start error :