Tips: Answering Questions/Solving Problems

Being there are so many variables involved in setting up a networked Linux operating systems, Support questions may go unanswerable if they do not provide the required logs/details needed to pinpoint the problem. (only post 20 line short log segments that are to the point- to keep the forum clean; for sharing larger logs: use pastebin)

START HERE: How to check logs in Linux

When asking a question, be sure to first check out/follow the Support Forum Guidelines .

Most importantly, be sure to include the right amount of details/logs for your question (I know I mentioned this, but logs/error msgs are really, really important especially for networking/hardware related questions).


If your question is a hardware problem, be sure to include exact hardware model and the driver (inxi command will give you info to share; start with inxi -h).


  1. Install exact kernel-headers first
  2. Download Driver
  3. Compile Driver/finish driver instructions
  4. modprobe driver
  5. lsmod to check status of driver

I find the best way to learn is to break something on Linux. Sure it can be frustrating, but these are the times we learn most :wink:

As a community, we all want to help each other, but if we can’t see what is going on in your system, we can’t fully understand your problem.

Start out with apropos command:

apropos topicNameHere

That will list various commands related to topicNameHere .

Then pick a command listed, and read the man page for it (man = manual page):

man CommandNameHere

This 2 step equation will give you plenty of reading material to better use the command line :slight_smile:

For example, to find editors:

apropos editor

For searching for drivers/errors/patterns in logs, try the grep command.

Example usage (search all files in /var/log for DriverName):

grep 'DriverName' /var/log/*

Read more about grep usage here:

man grep

Outside the man pages, look at one of many free online guides on the basics of Debian based Linux (Parrot is based on Debian). Go through the commands. Try different flags/combinations to gain a better understanding.

Then, when you do have a problem, it will be easier for you to describe it in a way we can better help you :slight_smile:

Most problems can be solved by viewing logs in /var/log directory and google searching the errors related to a problem

If it is a visual problem, take a look at /var/log/Xorg.0.log along with /home/Username/.xsession-errors

As has been mentioned, pertinent log segments along with clear, easy to understand questions will bring you the best results in asking questions here.

If you don’t follow the below format/include enough information, your question may be rejected or go unanswered:

Briefly describe your issue below:

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)

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:

Follow the above format: a clear concise question, making sure to include logs related to that question (for best possible results).

Thank you and Welcome! :slight_smile: