/usr/share/doc/installation-guide-powerpc/en/ch03s03.html is in installation-guide-powerpc 20160121ubuntu2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 | <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>3.3. Information You Will Need</title>
<link rel="stylesheet" type="text/css" href="install.css">
<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="index.html" title="Ubuntu Installation Guide">
<link rel="up" href="ch03.html" title="Chapter 3. Before Installing Ubuntu">
<link rel="prev" href="ch03s02.html" title="3.2. Back Up Your Existing Data!">
<link rel="next" href="ch03s04.html" title="3.4. Meeting Minimum Hardware Requirements">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr><th colspan="3" align="center">3.3. Information You Will Need</th></tr>
<tr>
<td width="20%" align="left">
<a accesskey="p" href="ch03s02.html"><img src="images/prev.png" alt="Prev"></a> </td>
<th width="60%" align="center">Chapter 3. Before Installing Ubuntu</th>
<td width="20%" align="right"> <a accesskey="n" href="ch03s04.html"><img src="images/next.png" alt="Next"></a>
</td>
</tr>
</table>
<hr>
</div>
<div class="sect1">
<div class="titlepage"><div><div><h2 class="title">
<a name="needed-info"></a>3.3. Information You Will Need</h2></div></div></div>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="idp43088448"></a>3.3.1. Documentation</h3></div></div></div>
<div class="sect3">
<div class="titlepage"><div><div><h4 class="title">
<a name="idp43089088"></a>3.3.1.1. Installation Manual</h4></div></div></div>
<p>
This document you are now reading, in plain ASCII, HTML or PDF format.
</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem"><p>
<a class="ulink" href="install.en.txt" target="_top">install.en.txt</a>
</p></li>
<li class="listitem"><p>
<a class="ulink" href="install.en.html" target="_top">install.en.html</a>
</p></li>
<li class="listitem"><p>
<a class="ulink" href="install.en.pdf" target="_top">install.en.pdf</a>
</p></li>
</ul></div>
</div>
<div class="sect3">
<div class="titlepage"><div><div><h4 class="title">
<a name="idp43094224"></a>3.3.1.2. Hardware documentation</h4></div></div></div>
<p>
Often contains useful information on configuring or using your hardware.
</p>
</div>
</div>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="fsohi"></a>3.3.2. Finding Sources of Hardware Information</h3></div></div></div>
<p>
In many cases, the installer will be able to automatically detect your
hardware. But to be prepared, we do recommend familiarizing
yourself with your hardware before the install.
</p>
<p>
Hardware information can be gathered from:
</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem"><p>
The manuals that come with each piece of hardware.
</p></li>
<li class="listitem"><p>
The BIOS setup screens of your computer. You can view these screens
when you start your computer by pressing a combination of keys. Check
your manual for the combination. Often, it is the <span class="keycap"><strong>Delete</strong></span>
or the <span class="keycap"><strong>F2</strong></span> key, but some manufacturers use other keys
or key combinations. Usually upon starting the computer there will
be a message stating which key to press to enter the setup screen.
</p></li>
<li class="listitem"><p>
The cases and boxes for each piece of hardware.
</p></li>
<li class="listitem"><p>
System commands or tools in another operating system, including file
manager displays. This source is especially useful for information
about RAM and hard drive memory.
</p></li>
<li class="listitem"><p>
Your system administrator or Internet Service Provider. These
sources can tell you the settings you need to set up your
networking and e-mail.
</p></li>
</ul></div>
<p>
</p>
<div class="table">
<a name="idp43102800"></a><p class="title"><b>Table 3.1. Hardware Information Helpful for an Install</b></p>
<div class="table-contents"><table class="table" summary="Hardware Information Helpful for an Install" border="1">
<colgroup>
<col>
<col>
</colgroup>
<thead><tr>
<th>Hardware</th>
<th>Information You Might Need</th>
</tr></thead>
<tbody>
<tr>
<td rowspan="6">Hard Drives</td>
<td>How many you have.</td>
</tr>
<tr><td>Their order on the system.</td></tr>
<tr><td>Whether IDE (also known as PATA), SATA or SCSI.</td></tr>
<tr><td>Available free space.</td></tr>
<tr><td>Partitions.</td></tr>
<tr><td>Partitions where other operating systems are installed.</td></tr>
<tr>
<td>Network interfaces</td>
<td>Type/model of available network interfaces.</td>
</tr>
<tr>
<td>Printer</td>
<td>Model and manufacturer.</td>
</tr>
<tr>
<td>Video Card</td>
<td>Type/model and manufacturer.</td>
</tr>
</tbody>
</table></div>
</div>
<p><br class="table-break">
</p>
</div>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="idp43118176"></a>3.3.3. Hardware Compatibility</h3></div></div></div>
<p>
Many products work without trouble on Linux. Moreover,
hardware support in Linux is improving daily. However, Linux still does
not run as many different types of hardware as some operating systems.
</p>
<p>
Drivers in Linux in most cases are not written for a certain
<span class="quote">“<span class="quote">product</span>”</span> or <span class="quote">“<span class="quote">brand</span>”</span> 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 <span class="quote">“<span class="quote">reference designs</span>”</span> 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.
</p>
<p>
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.
</p>
<p>
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 <span class="quote">“<span class="quote">vendor</span>”</span> and
<span class="quote">“<span class="quote">product</span>”</span> IDs, and the combination of these two is usually the same for any
product based on the same chipset.
</p>
<p>
On Linux systems, these IDs can be read with the <span class="command"><strong>lsusb</strong></span>
command for USB devices and with the <span class="command"><strong>lspci -nn</strong></span> 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
<span class="quote">“<span class="quote">1d6b:0001</span>”</span>.
</p>
<p>
An example for the output of <span class="command"><strong>lsusb</strong></span>: <span class="quote">“<span class="quote">Bus 001
Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub</span>”</span>, whereby 1d6b is
the vendor ID and 0002 is the product ID.
</p>
<p>
An example for the output of <span class="command"><strong>lspci -nn</strong></span> for an Ethernet
card: <span class="quote">“<span class="quote">03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)</span>”</span>.
The IDs are given inside the rightmost square brackets, i.e. here
10ec is the vendor- and 8168 is the product ID.
</p>
<p>
As another example, a graphics card could give the following output:
<span class="quote">“<span class="quote">04:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee
ATI RV710 [Radeon HD 4350] [1002:954f]</span>”</span>.
</p>
<p>
On Windows systems, the IDs for a device can be found in the Windows device
manager on the tab <span class="quote">“<span class="quote">details</span>”</span>, 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 <span class="quote">“<span class="quote">Hardware IDs</span>”</span> in the
device manager's details tab to actually see the IDs, as they are not
displayed by default.
</p>
<p>
Searching on the internet with the vendor/product ID, <span class="quote">“<span class="quote">Linux</span>”</span> and
<span class="quote">“<span class="quote">driver</span>”</span> 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
(<span class="quote">“<span class="quote">RTL8111</span>”</span>/<span class="quote">“<span class="quote">RTL8168B</span>”</span> in the network card example and <span class="quote">“<span class="quote">RV710</span>”</span> in the
graphics card example), can help.
</p>
<div class="sect3">
<div class="titlepage"><div><div><h4 class="title">
<a name="idp43133392"></a>3.3.3.1. Testing hardware compatibility with a Live-System</h4></div></div></div>
<p>
Ubuntu is also available as a so-called <span class="quote">“<span class="quote">live system</span>”</span> 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 Ubuntu, the easiest way is to run a
Ubuntu live system on it and try it out.
</p>
<p>
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 Ubuntu 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 <code class="classname">debian-installer</code>,
so installation of non-free components must be done manually if needed.
</p>
<p>
Information about the available variants of the Ubuntu live images
can be found at the <a class="ulink" href="http://www.ubuntu.com/download/" target="_top">download web page</a>.
</p>
</div>
</div>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="idp43138096"></a>3.3.4. Network Settings</h3></div></div></div>
<p>
If your computer is connected to a fixed network (i.e. an Ethernet or
equivalent connection — not a dialup/PPP connection) which is
administered by somebody else, you should ask your network's system
administrator for this information:
</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem"><p>
Your host name (you may be able to decide this on your own).
</p></li>
<li class="listitem"><p>
Your domain name.
</p></li>
<li class="listitem"><p>
Your computer's IP address.
</p></li>
<li class="listitem"><p>
The netmask to use with your network.
</p></li>
<li class="listitem"><p>
The IP address of the default gateway system you should route to, if
your network <span class="emphasis"><em>has</em></span> a gateway.
</p></li>
<li class="listitem"><p>
The system on your network that you should use as a DNS (Domain Name
Service) server.
</p></li>
</ul></div>
<p>
</p>
<p>
If the network you are connected to uses DHCP (Dynamic Host Configuration
Protocol) for configuring network settings, you don't need this information
because the DHCP server will provide it directly to your computer
during the installation process.
</p>
<p>
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.
</p>
<p>
If you use a WLAN/WiFi network, you should find out:
</p>
<div class="itemizedlist"><ul class="itemizedlist" type="disc">
<li class="listitem"><p>
The ESSID (<span class="quote">“<span class="quote">network name</span>”</span>) of your wireless network.
</p></li>
<li class="listitem"><p>
The WEP or WPA/WPA2 security key to access the network (if applicable).
</p></li>
</ul></div>
<p>
</p>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="ch03s02.html"><img src="images/prev.png" alt="Prev"></a> </td>
<td width="20%" align="center"><a accesskey="u" href="ch03.html"><img src="images/up.png" alt="Up"></a></td>
<td width="40%" align="right"> <a accesskey="n" href="ch03s04.html"><img src="images/next.png" alt="Next"></a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">3.2. Back Up Your Existing Data! </td>
<td width="20%" align="center"><a accesskey="h" href="index.html"><img src="images/home.png" alt="Home"></a></td>
<td width="40%" align="right" valign="top"> 3.4. Meeting Minimum Hardware Requirements</td>
</tr>
</table>
</div>
</body>
</html>
|