Linux Getting Started and Basic Troubleshooting Guide v1.10

Introduction

So, you've ventured into the strange world of Linux, leaving behind Windows/Mac OS X. Linux can be a difficult learning experience for the uninitiated. We have included some advice from the top Linux forum experts for success in Linux.

Linux unfortunately is not always as simple as install and go. Normally the OS will be operational after the first initial installation but you may notice some limitations or problems. This guide aims to address the common problems associated with Linux. It is important to understand that Linux is not Windows. There are fundemential differences between Windows/Mac OS X and Linux but that is not to say that there is absolutely no overlap. Using Linux means diving into the world of the command line. The command line is not scary. In fact both Mac OS X and Windows have their own command lines, but they are less apparent in the normal operation of the operating system.

Learning commands improves your knowledge of both the underpinnings of Mac OS X and Windows. Many concepts and commands such as sudo are cross-compatible with Mac OS X, as Mac OS X has its roots in Free BSD, a close descendant of Linux. Do not worry if you do not understand all of the commands to begin with. That comes with practice and patience. Many of the mainstream Linux distributions are relatively graphical, so you can get a good feel for Linux before you take a plunge into the deep end.

Google is your best friend here. If you have an issue, chances are, you're not the only one! Also, most distributions come with a user manual. Please refer to these resources before posting a question to Tom's Hardware.

When you have a problem that you are absolutely sure cannot be solved by Google, please ask! Although we want to help each and every single one of you users out there, it can't be done. We really don't want to answer the same few questions again and again so we have more time to answer the really big unique questions this guide doesn't cover. When posting a question, be sure to include as much data as you can obtain about the nature of the problem, how it happened and your hardware configuration.

Index
Common Linux Issues
Linux Power Optimisation Guide
Linux Glossary
Helpful Linux Links

This thread has been marked for improvement by amdfangirl. Suggestions and comments are appreciated. Contributors will be noted.

If you wish to contribute something to the Linux/Free BSD stickies please contribute here:

http://www.tomshardware.com/forum/ [...] ion-thread

Contributors: bmouring, Pyroflea, amdfangirl

Common Linux Issues

Google is your best friend here. If you have an issue, chances are, you're not the only one! Also, most distributions come with a user manual. Please refer to these resources before posting a question to Tom's Hardware.

Linux is through with explanations on why something works. If you understand what Linux is telling you, you can more easily fix the problem. Most of the time, Linux provides the answer for you and tells you why. It doesn't always pop up a new window to tell you. Running the program via the terminal will pop up the program and also any helpful warnings errors encountered will be displayed in the terminal window. Many programs will have what is called a logfile. Logfiles document record what actions a programme took.

System-wide programmes tend to put logs in /var/log, user programs tend to keep logs in your home folder, /home/$USER, however usually it's either a file or a folder that's prefixed with a '.', making it hidden unless you specify that hidden files are shown.

When Faced with a Hardware Issue, Make Sure the Kernel Sees/Knows the Hardware
With device plugged in, first things first" issue a ls$BUS_OF_DEVICE (e.g. lspci for PCI and PCIe, PCI-X, PCMCIA, etc. etc.). Take note that it shows up. Also handy, check the kernel logs that it shows up and has reasonable information about device config/bringup as well (easy method: from terminal, issue dmesg|less to get the kernel log into the less text pager, you can then use / to search for something in particular, by default it's case sensitive)

a. My wireless won't work!

1. Update your Linux, make sure you get the newest updates for it.

2. See if any restricted drivers are available. Ubuntu and Linux Mint tend to offer them to you. Install them and see what happens. Restricted drivers on Fedora must be manually installed

3. Identify what wireless card you have. Open terminal and type in

4. For Fedora, attempt to find which package you need from: http://rpmfusion.org/ Detailed instructions on how to install the package are avalible on the rpm fusion website.

Open source wireless documentation for your wireless card can be found here:

http://linuxwireless.org/

5. Attempt to install the Windows wireless driver with NDISwrapper:

http://sourceforge.net/projects/ndiswrapper/

If you are using Ubuntu or Linux Mint, NDISwrapper should already be installed. A guide on how to use NDISwrapper is show here:

https://help.ubuntu.com/community/W [...] diswrapper

The NDISwrapper wiki is located here:

http://sourceforge.net/apps/mediaw [...] =Main_Page

6. See if the wireless device is supported by other Linux distributions. Sometimes a more cutting edge distribution such as Fedora will have already have had the latest open source driver installed.

b. My Ethernet/LAN doesn't work!

Follow the same instructions as question a, but omit NDISwrapper, it doesn't work for wired connections.

c. Will Linux work on my computer? Is my hardware supported?

1. If you are using an Intel Macintosh, chances are since your hardware configuration is so common, it will be supported.

However, if not, search the internet for your motherboard and graphics card to see if

2. Test it for yourself! As a general rule, if something doesn't work in LiveCD mode, it won't work out of the box when you install it.

3. If it still refuses to work, you should try a text based installer. They are marked "alternate" installation CDs.

4. See if the hardware is supported by other Linux distributions. Sometimes a more cutting edge distribution such as Fedora will have already have had the latest open source driver installed.

d. Will my Windows software work in Linux?

1. Native Linux applications are normally your best options. Native applications work better and are more stable.

A recommended list can be found here:

http://www.tomshardware.com/forum/ [...] de#t869710

2. WINE can be used to run Windows software, please be aware it does not work with all software.

A guide is available here:

http://www.tomshardware.com/forum/ [...] de#t869711

Useful Linux terms:
APT - The package manager for Ubuntu, Linux Mint and Ubuntu based Linux.
.DEB - File format designed for Debian based software
Distro or Distribution - A special flavour of Linux, designed to cater to a particular audience.
Terminal - A command-line interface method for controlling a Unix-like operating system
.RPM - RPM Pacakage Manger, an executable file format that installs software, often used with yum (fedora), urmpi (mandriva) and etc.
OS or Operating System - A software that manages computer hardware resources. Examples include: Unix, FreeBSD, Windows, Mac OS X, Linux.
VM or Virtual Machine - An application which imitates a seperate computer so another guest operating system can reside in host operating system. Similar to an emulator.
YUM - The package manager for Fedora and Red-hat Linux.
WINE - Wine is not an emulator - A library of data designed to run Windows applications natively on Linux without copying Windows.

This topic has been desticky in top of the forum by Amdfangirl