3.3. Information du behöver

3.3.1. Dokumentation

3.3.1.1. Installationshandbok

Det här dokumentet du nu läser, finns i ren ASCII, HTML eller PDF-format.

3.3.1.2. Maskinvarudokumentation

Innehåller ofta användbar information om hur du konfigurerar eller använder din maskinvara.

3.3.2. Hitta informationskällor för maskinvara

I många fall kan installationsprogrammet automatiskt identifiera din maskinvara. Men för att vara förberedd rekommenderar vi att du gör dig hemmastadd med din maskinvara före installationen.

Maskinvaruinformation kan samlas in från:

  • Handböckerna som kommer med varje maskinvarudel.

  • BIOS-inställningarna på din dator. Du kan se de här skärmarna när du startar din dator genom att trycka på en tangentkombination. Leta i din handbok efter kombinationen. Ofta är det tangenten Delete.

  • Förpackningarna och lådorna för varje del av maskinvaran.

  • Systemkommandon eller verktyg i ett annat operativsystem, inklusive filhanterarskärmar. Den här källan är speciellt användbar för information om RAM-minne och hårddisksutrymme.

  • Din systemadministratör eller Internetleverantör. De här källorna kan informera dig om de inställningar du behöver för att ställa in din nätverksanslutning och e-post.

Tabell 3.1. Maskinvaruinformation som behövs för en installation

Maskinvara Information du kan behöva
Hårddiskar Hur många du har.
Deras ordning i systemet.
Om IDE (även känd som PATA), SATA eller SCSI används.
Tillgängligt ledigt utrymme.
Partitioner.
Partitioner där andra operativsystem är installerade.
Nätverksinställningar Konfigurera ett nätverkssgränssnitt
Skrivare Modell och tillverkare.
Grafikkort Modell och tillverkare.


3.3.3. Maskinvarukompatibilitet

Många märkesprodukter fungerar utan problem på Linux. Mängden maskinvara som stöds av Linux ökar dagligen. Dock kan Linux fortfarande inte köra lika många olika typer av maskinvara som en del andra operativsystem.

Drivers in Linux in most cases are not written for a certain product or brand from a specific manufacturer, but for a certain hardware/chipset. Many seemingly different products/brands are based on the same hardware design; it is not uncommon that chip manufacturers provide so-called reference designs for products based on their chips which are then used by several different device manufacturers and sold under lots of different product or brand names.

This has advantages and disadvantages. An advantage is that a driver for one chipset works with lots of different products from different manufacturers, as long as their product is based on the same chipset. The disadvantage is that it is not always easy to see which actual chipset is used in a certain product/brand. Unfortunately sometimes device manufacturers change the hardware base of their product without changing the product name or at least the product version number, so that when having two items of the same brand/product name bought at different times, they can sometimes be based on two different chipsets and therefore use two different drivers or there might be no driver at all for one of them.

For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on which chipset they are based is to look at their device IDs. All USB/PCI/PCI-Express/ExpressCard devices have so called vendor and product IDs, and the combination of these two is usually the same for any product based on the same chipset.

On Linux systems, these IDs can be read with the lsusb command for USB devices and with the lspci -nn command for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are usually given in the form of two hexadecimal numbers, seperated by a colon, such as 1d6b:0001.

An example for the output of lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub, whereby 1d6b is the vendor ID and 0002 is the product ID.

An example for the output of lspci -nn for an Ethernet card: 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06). The IDs are given inside the rightmost square brackets, i.e. here 10ec is the vendor- and 8168 is the product ID.

As another example, a graphics card could give the following output: 04:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f].

On Windows systems, the IDs for a device can be found in the Windows device manager on the tab details, where the vendor ID is prefixed with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, you have to select the property Hardware IDs in the device manager's details tab to actually see the IDs, as they are not displayed by default.

Searching on the internet with the vendor/product ID, Linux and driver as the search terms often results in information regarding the driver support status for a certain chipset. If a search for the vendor/product ID does not yield usable results, a search for the chip code names, which are also often provided by lsusb and lspci (RTL8111/RTL8168B in the network card example and RV710 in the graphics card example), can help.

3.3.3.1. Testing hardware compatibility with a Live-System

Debian GNU/Linux is also available as a so-called live system for certain architectures. A live system is a preconfigured ready-to-use system in a compressed format that can be booted and used from a read-only medium like a CD or DVD. Using it by default does not create any permanent changes on your computer. You can change user settings and install additional programs from within the live system, but all this only happens in the computer's RAM, i.e. if you turn off the computer and boot the live system again, everything is reset to its defaults. If you want to see whether your hardware is supported by Debian GNU/Linux, the easiest way is to run a Debian live system on it and try it out.

There are a few limitations in using a live system. The first is that as all changes you do within the live system must be held in your computer's RAM, this only works on systems with enough RAM to do that, so installing additional large software packages may fail due to memory constraints. Another limitation with regards to hardware compatibility testing is that the official Debian GNU/Linux live system contains only free components, i.e. there are no non-free firmware files included in it. Such non-free packages can of course be installed manually within the system, but there is no automatic detection of required firmware files like in the debian-installer, so installation of non-free components must be done manually if needed.

Information about the available variants of the Debian live images can be found at the Debian Live Images website.

3.3.4. Nätverksinställningar

Om din dator är ansluten till ett nätverk dygnet runt (exempelvis via Ethernet eller liknande anslutning — inte en PPP-anslutning), bör du fråga din nätverksadministratör efter följande information.

  • Ditt datornamn (du kanske kan välja det här helt på egen hand).

  • Ditt domännamn.

  • Din dators IP-adress.

  • Nätmasken som används på ditt nätverk.

  • IP-adressen till den gateway som är standardrutten ut från ditt nätverk, om ditt nätverk har en gateway.

  • Systemet på ditt nätverk som du ska använda som en DNS-server (Domännamnstjänst).

Å andra sidan, om din administratör berättar för dig att en DHCP-server finns tillgänglig och rekommenderas, behöver du inte den här information då DHCP-servern kommer att ge ut den direkt till din dator under installationsprocessen.

If you have internet access via DSL or cable modem (i.e. over a cable tv network) and have a router (often provided preconfigured by your phone or catv provider) which handles your network connectivity, DHCP is usually available by default.

Om du använder ett trådlöst nätverk, bör du också ta reda på:

  • ESSID för ditt trådlösa nätverk.

  • WEP- och WPA/WPA2säkerhetsnyckel (om sådan används).