Failed to start Light Display Manage

(Juan Carlos Huanca Huarina) #1

after installing Parrot OS 4.0.1 in Virtualbox.
Restart and I have this message “Failed to start Light Display Manage”
execute the commands:
systemctl enable lightdm.service
and it is not solved


What version of Parrot are you running? (include version, edition, and architecture)

What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)

Configured to multiboot with other systems? (yes / no)

If there are any similar issues or solutions, link to them below:

If there are any error messages or relevant logs, post them below:

0 Likes

(cycox) #2

I am facing same issue in virtualbox
failed to start light display manager frastrating​:footprints::footprints::footprints: still searching on Google

0 Likes

(Finn) #3

Same for me.
Virtualbox 5.2.12 r122591 (Qt5.6.2)
Parrot OS 4.0.1!

systemctl status lightdm.service gives the following error.

0 Likes

#4
0 Likes

(Arry) #5

Virtualbox Version 5.2.12 Edition
Parrot OS 4.0.1
我的也出现了 相同问题

failed to start light display manager
See 'systemctl status lightdm.service ' for details.
0 Likes

(Pavel) #6

Here is a way, how to solve the problem with the VirtualBox

When you obtain the failure message about lightdm, simply press ALT+F1 and log in there. then:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install build-essential module-assistant
sudo m-a prepare

Insert Guest Additions ISO
mount /media/cdrom
sudo sh /media/cdrom/VBoxLinuxAdditions.run

reboot

3 Likes

(Finn) #7

That worked like a charm! Thanks!

0 Likes

(cycox) #8

Hope this will work for me also :wink::wink::wink:
Let me try this

0 Likes

#9

This is the only thing that has worked for me.
Big thanks!

0 Likes

#10

Thanks for this! For magical computer reasons it didn’t work right away, I had to sit AFK in a TTY shell lol. Thanks again!

0 Likes

#11

I couldn’t even install it… :frowning_face:
Hashes are matching but i can’t able to install it or run it as live.
vulnerbility assesment manager and LDM are failed while booting.
is there any way to fix it on live usb?

1 Like

(McCouman) #12

I have the same problem with security-, media- and net installation iso.
I’ll give it up soon. In addition, there is the German keyboard and the very annoying enter through the english keyboard.

Too bad, I wanted to set it up as the main operating system someday. But that will not work. A pity!

0 Likes

(Тош) #13

Thank you very much! Your recommendation really helps))

0 Likes

(FLAKO) #14

Buenas Noches Comunidad tenia el mismo problema con el failed-to-start-light-display-manage y la forma de solucionarlo fue utilizar una tarjeta grafica integrada a la Board y una vez instalado el SO:

Utilice esta ayuda :

TOTAL CREDITS A ==>>> https://docs.kali.org/general-use/install-nvidia-drivers-on-kali-linux <===

–//—

First, you’ll need to ensure that your system is fully upgraded and that your card supports CUDA.
Note: GPUs with a CUDA compute capability > 5.0 are recommended, but GPUs with less will still work.

apt update && apt dist-upgrade -y && reboot

Let’s determine the exact GPU installed, and check the kernel modules it’s using.

    root@kali:~# lspci -v
    01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970]
        Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express (v2) Legacy Endpoint, MSI 00
        Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024
        Kernel driver in use: nouveau
        Kernel modules: nouveau

Installation

Once the system has rebooted, we will proceed to install the OpenCL ICD Loader, Drivers, and the CUDA toolkit.

apt install -y ocl-icd-libopencl1 nvidia-driver nvidia-cuda-toolkit

During installation of the drivers the system created new kernel modules, so another reboot is required.
Verify Driver Installation

Now that our system should be ready to go, we need to verify the drivers have been loaded correctly. We can quickly verify this by running the nvidia-smi tool.

root@kali:~# nvidia-smi    
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 375.26                 Driver Version: 375.26                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 970     Off  | 0000:01:00.0      On |                  N/A |
| 36%   46C    P0    47W / 325W |    200MiB /  4036MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+                                                                        
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0       692    G   /usr/lib/xorg/Xorg                             198MiB |
+-----------------------------------------------------------------------------+ 

With the output displaying our driver and GPU correctly, we can now dive into benchmarking. Before we get too far ahead, let’s double check to make sure hashcat and CUDA are working together.

root@kali:~# hashcat -I
OpenCL Info:
Platform ID #1
  Vendor  : NVIDIA Corporation
  Name    : NVIDIA CUDA
  Version : OpenCL 1.2 CUDA 8.0.0
  Device ID #1
    Type           : GPU
    Vendor ID      : 32
    Vendor         : NVIDIA Corporation
    Name           : GeForce GTX 970
    Version        : OpenCL 1.2 CUDA
    Processor(s)   : 13
    Clock          : 1240
    Memory         : 1009/4036 MB allocatable
    OpenCL Version : OpenCL C 1.2
    Driver Version : 375.26

It appears everything is working, let’s go ahead and run a benchmark test.
Benchmarking

root@kali:~# hashcat -b
OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: Geforce GTX 970, 1009/4095 MB allocatable, 13MCU

Hashtype: MD5
Speed.Dev.#1.....: 10443.1 MH/s
Hashtype: SHA1
Speed.Dev.#1.....: 3349.8 MH/s
Hashtype: SHA256
Speed.Dev.#1.....: 1321.8 MH/s

There are a multitude of configurations to improve cracking speed, not mentioned in this guide. However, we encourage you to take a look at the hashcat documentation for your specific cases.
Troubleshooting

In the event setup isn’t going as planned, we’ll install clinfo for detailed troubleshooting information.

apt install -y clinfo

OpenCL Loaders

It may be necessary to check for additional packages that may be conflicting with our setup. Let’s first check to see what OpenCL Loader we have installed. The NVIDIA OpenCL Loader and the generic OpenCL Loader will both work for our system.

root@kali:~# dpkg -l |grep -i icd
ii  nvidia-egl-icd:amd64                      375.26-2                             amd64        NVIDIA EGL installable client driver (ICD)
ii  nvidia-opencl-icd:amd64                   375.26-2                             amd64        NVIDIA OpenCL installable client driver (ICD)
ii  nvidia-vulkan-icd:amd64                   375.26-2                             amd64        NVIDIA Vulkan installable client driver (ICD)
ii  ocl-icd-libopencl1:amd64                  2.2.11-1                             amd64        Generic OpenCL ICD Loader

If mesa-opencl-icd is installed run:

apt remove mesa-opencl-icd

Since we have determined that we have a compatible ICD loader installed, we can easily determine which loader is currently being used.

root@kali:~# clinfo | grep -i "icd loader"
ICD loader properties
  ICD loader Name                                 OpenCL ICD Loader
  ICD loader Vendor                               OCL Icd free software
  ICD loader Version                              2.2.11
  ICD loader Profile                              OpenCL 2.1

As expected, our setup is using the open source loader that was installed earlier. Now, let’s get some detailed information about the system.
Querying GPU Information

We’ll use nvidia-smi once again, but with a much more verbose output.

root@kali:~# nvidia-smi -i 0 -q
Driver Version                      : 375.26
Attached GPUs                       : 1
GPU 0000:01:00.0
    Product Name                    : GeForce GTX 970
    Product Brand                   : GeForce
    Display Mode                    : Enabled
    Display Active                  : Enabled
    Persistence Mode                : Disabled
    Accounting Mode                 : Disabled
    Accounting Mode Buffer Size     : 1920
Temperature
        GPU Current Temp            : 47 C
        GPU Shutdown Temp           : 96 C
        GPU Slowdown Temp           : 91 C
    Clocks
        Graphics                    : 1101 MHz
        SM                          : 1101 MHz
        Memory                      : 3523 MHz
        Video                       : 1012 MHz
    Processes
        Process ID                  : 692
            Type                    : G
            Name                    : /usr/lib/xorg/Xorg
            Used GPU Memory         : 198 MiB

It looks like our GPU is being recognized correctly, so let’s use glxinfo to determine if 3D Rendering is enabled.

root@kali:~# glxinfo | grep -i "direct rendering"
direct rendering: Yes

The combination of these tools should assist the troubleshooting process greatly. If you still experience issues, we recommend searching for similar setups and any nuances that may affect your specific system.

TOTAL CREDITS A https://docs.kali.org/general-use/install-nvidia-drivers-on-kali-linux

2 Likes

Nvidia drivers install
(Abdullah Al Asif) #15

Stuck here forever!!! What to do?
It is my very first time with Parrot. Please help.

I’ve done all the three process. Using VirtualBox in Ubuntu 18.04 Host.

0 Likes

#16

I had this issue, I had to run Parrot in VMWare and it was fine, it seems to be an issue with the free version of VirtualBox

0 Likes

(ddser) #17

may be you can edit grub
“e”
grub.cfg add
" nolapic noapci noautomount nouveau.modeset=0 "
“ctrl -x”
good luck

0 Likes