DOCSLIB.ORG

Linux for Zseries: Device Drivers and Installation Commands (March 4, 2002) Summary of Changes

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Linux for Zseries: Device Drivers and Installation Commands (March 4, 2002) Summary of Changes Linux for zSeries Device Drivers and Installation Commands (March 4, 2002) Linux Kernel 2.4 LNUX-1103-07 Linux for zSeries Device Drivers and Installation Commands (March 4, 2002) Linux Kernel 2.4 LNUX-1103-07 Note Before using this document, be sure to read the information in “Notices” on page 207. Eighth Edition – (March 2002) This edition applies to the Linux for zSeries kernel 2.4 patch (made in September 2001) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2000, 2002. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Summary of changes .........v Chapter 5. Linux for zSeries Console || Edition 8 changes.............v device drivers............27 Edition 7 changes.............v Console features .............28 Edition 6 changes ............vi Console kernel parameter syntax .......28 Edition 5 changes ............vi Console kernel examples ..........28 Edition 4 changes ............vi Usingtheconsole............28 Edition 3 changes ............vii Console – Use of VInput ..........30 Edition 2 changes ............vii Console limitations ............31 About this book ...........ix Chapter 6. Channel attached tape How this book is organized .........ix device driver ............33 Who should read this book .........ix Tapedriverfeatures...........33 Assumptions..............ix Tape character device front-end........34 Tape block device front-end .........34 Part 1. Linux for zSeries Device Tape driver kernel parameter syntax ......35 drivers overview ..........1 Tapedriverkernelexample.........35 Tape driver module parameter syntax .....36 Tape driver module example ........36 Chapter 1. Common device support. 3 TapedevicedriverAPI..........37 Tapedriverexamples...........37 Chapter 2. Partitioning DASD .....5 Tape driver restrictions ..........38 Prerequisites ..............5 Tapedriverfurtherinformation........38 Why use partitions? ............5 Restrictions ...............5 Chapter 7. Generic cryptographic The partition table ............6 device driver ............39 zSeries disk layout (VTOC) .........6 Overview...............39 HMC settings..............40 Part 2. Linux for zSeries — zSeries Installing z90crypt ............41 device drivers ...........9 Decryptionusingz90crypt.........43 Otherfunctionsofz90crypt.........44 Chapter 3. Linux for zSeries DASD z90crypt header file ...........45 Crypto support for 31-bit emulation ......46 device driver ............11 Example of use: Apache ..........46 DASD overview .............11 DASD naming scheme using devfs ......11 DASD naming scheme without devfs ......12 Part 3. Linux for zSeries Network Partitioned DASD ............13 device drivers ...........49 DASD features .............14 DASD kernel parameter syntax ........15 Chapter 8. Linux for zSeries Channel DASD kernel example (using devfs) ......16 device layer ............51 DASD module parameter syntax .......17 Description ..............51 DASD module example ..........17 Channel device layer options ........52 DASD dynamic attach/detach ........17 Seealso................60 DASD – Preparingforuse.........18 Files .................61 DASD API (ioctl interface) .........19 DASD restrictions ............21 Chapter 9. Linux for zSeries Chapter 4. Linux for zSeries XPRAM CTC/ESCON device driver ......63 device driver ............23 CTC/ESCON features ...........63 CTC/ESCON with the channel device layer . 63 XPRAM features.............23 CTC/ESCON without the channel device layer . 64 Note on reusing XPRAM partitions ......23 CTC/ESCON – Preparing the connection ....66 XPRAM kernel parameter syntax .......24 CTC/ESCON – Recovery procedure after a crash . 69 XPRAM module parameter syntax.......25 © Copyright IBM Corp. 2000, 2002 iii Chapter 10. Linux for zSeries IUCV ifconfig - Configure a network interface ....144 device driver ............71 insmod - Load a module into the Linux kernel . 148 IUCVfeatures.............71 modprobe - Load a module with dependencies into IUCV kernel parameter syntax ........71 theLinuxkernel............150 IUCV kernel parameter example .......72 lsmod - List loaded modules ........153 IUCV module parameter syntax .......72 depmod - Create dependency descriptions for IUCV module parameter example .......72 loadable kernel modules..........154 IUCV – Preparing the connection .......73 mke2fs - Create a file system on DASD.....156 IUCV – Furtherinformation.........75 IUCV restrictions ............75 Chapter 14. VIPA – minimize outage IUCV Application Programming Interface (API) . 75 due to adapter failure ........157 Standard VIPA .............157 Chapter 11. Linux for zSeries LCS device driver ............93 Chapter 15. Kernel parameters ....159 LCS supported functions ..........93 ipldelay...............160 LCS channel device layer configuration .....93 maxcpus...............161 LCS channel device layer configuration example . 93 mem................162 || LCS kernel parameter syntax ........94 noinitrd...............163 LCSwarning..............95 ramdisk_size.............164 LCS restrictions .............95 ro.................165 root................166 Chapter 12. QETH device driver for vmhalt...............167 OSA-Express (QDIO) and HiperSockets. 97 cio_msg...............168 Naming conventions ...........97 Introduction ..............98 Chapter 16. Overview of the parameter Installing the modules ...........98 line file ..............169 QETH supported functions .........98 Parameters ..............170 Configuring QETH for OSA-Express and HiperSockets using the channel device layer . 99 Appendix A. Reference information 171 QETH parameter syntax..........101 LCS parameter syntax ..........171 OSA-Express feature in QDIO mode channel LCS module parameter syntax (without the devicelayerconfigurationexample......102 channel device layer) ...........171 HiperSockets channel device layer configuration OSA-Express and HiperSockets parameter syntax 172 example...............102 OSA-Express and HiperSockets driver command Examples: OSA-Express feature in QDIO mode . 103 syntax (without the channel device layer) ....172 Examples: HiperSockets ..........104 Linux for zSeries Major/Minor numbers ....173 OSA-Express feature in QDIO mode and HiperSockets – Preparing the connection ....105 Appendix B. Kernel building .....175 IP address takeover ...........106 Buildingthekernel...........175 OSA-Express feature in QDIO mode – Virtual IP Using ’config’ or ’oldconfig’ ........179 address (VIPA) .............107 Using ’menuconfig’ ...........184 QETH restrictions ............108 Kernel parameter options .........196 Priority queuing ............108 Glossary .............203 Part 4. Installation commands and parameters ............111 Notices ..............207 Trademarks..............208 Chapter 13. Useful Linux commands 113 dasdfmt - Format a DASD .........114 International License Agreement for dasdview - Display DASD Structure ......118 Non-Warranted Programs ......209 fdasd – DASD partitioning tool .......127 | snIPL – Remote control of Support Element (SE) Index ...............215 || functions...............134 zIPL – zSeries initial program loader .....138 iv Linux for zSeries: Device Drivers and Installation Commands (March 4, 2002) Summary of changes This revision contains changes to support the Linux for zSeries kernel loadable module for the Linux kernel version 2.4. | Edition 8 changes | New Information | v snIPL tool | v Setting up XPRAM dynamically | v Reference to Dump Tools manual | Changed Information | v Open-source LCS driver | v Corrected the separator (colon) between multiple guest-machine IDs in the iucv | kernel parameter and insmod command line. | v Added references to VIPA requirement for kernel built with CONFIG_DUMMY | kernel option. | This revision also includes maintenance and editorial changes. Technical changes | or additions to the text and illustrations are indicated by a vertical line to the left | of the change. | Deleted Information | v References to CONFIG_IP_ALIAS kernel option Edition 7 changes New Information v Option u added to fdasd. The option re-creates VTOC labels and keeps the partitions. v VIPA (virtual IP addressing) chapter v Installation instructions for qdio and qeth modules v z90crypt cryptographic device driver Changed Information This revision also includes maintenance and editorial changes. Technical changes or additions to the text and illustrations are indicated by a vertical line to the left of the change. Deleted Information v Parameter buffer_count (replaced by mem_in_k) in QETH © Copyright IBM Corp. 2000, 2002 v Edition 6 changes New Information v DASDview v Hipersockets Changed Information This revision also includes maintenance and editorial changes. Technical changes or additions to the text and illustrations are indicated by a vertical line to the left of the change. v OSA-Express – Clarifying editorial changes v fdasd – r and s options added v zIPL – Use of quotes Edition 5 changes New Information v VIPA v IP address takeover v Hipersockets Changed Information This revision also includes maintenance and editorial changes. Technical changes or additions to the text and illustrations are indicated by a vertical line to the left of the change. v OSA-Express – Updates for new cards v IUCV – New API v Kernel building restrictions. Edition 4 changes New Information v Channel device layer v Device file system v Tape driver v zIPL utility
Load more

Recommended publications
  • The Linux Kernel Module Programming Guide
    The Linux Kernel Module Programming Guide Peter Jay Salzman Michael Burian Ori Pomerantz Copyright © 2001 Peter Jay Salzman 2007−05−18 ver 2.6.4 The Linux Kernel Module Programming Guide is a free book; you may reproduce and/or modify it under the terms of the Open Software License, version 1.1. You can obtain a copy of this license at http://opensource.org/licenses/osl.php. This book is distributed in the hope it will be useful, but without any warranty, without even the implied warranty of merchantability or fitness for a particular purpose. The author encourages wide distribution of this book for personal or commercial use, provided the above copyright notice remains intact and the method adheres to the provisions of the Open Software License. In summary, you may copy and distribute this book free of charge or for a profit. No explicit permission is required from the author for reproduction of this book in any medium, physical or electronic. Derivative works and translations of this document must be placed under the Open Software License, and the original copyright notice must remain intact. If you have contributed new material to this book, you must make the material and source code available for your revisions. Please make revisions and updates available directly to the document maintainer, Peter Jay Salzman <[email protected]>. This will allow for the merging of updates and provide consistent revisions to the Linux community. If you publish or distribute this book commercially, donations, royalties, and/or printed copies are greatly appreciated by the author and the Linux Documentation Project (LDP).
    [Show full text]
  • Troubleshooting Passwords
    Troubleshooting Passwords The following procedures may be used to troubleshoot password problems: • Performing Password Recovery with an Existing Administrator, page 1 • Performing Password Recovery with No Existing Administrator, page 1 • Performing Password Recovery for the Linux Grapevine User Account, page 2 Performing Password Recovery with an Existing Administrator To perform password recovery for a user (administrator, installer or observer) where there exists at least one controller administrator (ROLE_ADMIN) user account, take the following steps: 1 Contact the existing administrator to set up a temporary password for the user that requires password recovery. Note The administrator can set up a temporary password by deleting the user's account and then recreating it with the lost password. The user can then log back into the controller to regain access and change the password once again to whatever he or she desires. 2 The user then needs to log into the controller with the temporary password and change the password. Note Passwords are changed in the controller GUI using the Change Password window. For information about changing passwords, see Chapter 4, Managing Users and Roles in the Cisco Application Policy Infrastructure Controller Enterprise Module Configuration Guide. Performing Password Recovery with No Existing Administrator The following procedure describes how to perform password recovery where there exists only one controller administrator (ROLE_ADMIN) user account and this account cannot be successfully logged into. Cisco Application Policy Infrastructure Controller Enterprise Module Troubleshooting Guide, Release 1.3.x 1 Troubleshooting Passwords Performing Password Recovery for the Linux Grapevine User Account Note We recommend that you create at least two administrator accounts for your deployment.
    [Show full text]
  • Version 7.8-Systemd
    Linux From Scratch Version 7.8-systemd Created by Gerard Beekmans Edited by Douglas R. Reno Linux From Scratch: Version 7.8-systemd by Created by Gerard Beekmans and Edited by Douglas R. Reno Copyright © 1999-2015 Gerard Beekmans Copyright © 1999-2015, Gerard Beekmans All rights reserved. This book is licensed under a Creative Commons License. Computer instructions may be extracted from the book under the MIT License. Linux® is a registered trademark of Linus Torvalds. Linux From Scratch - Version 7.8-systemd Table of Contents Preface .......................................................................................................................................................................... vii i. Foreword ............................................................................................................................................................. vii ii. Audience ............................................................................................................................................................ vii iii. LFS Target Architectures ................................................................................................................................ viii iv. LFS and Standards ............................................................................................................................................ ix v. Rationale for Packages in the Book .................................................................................................................... x vi. Prerequisites
    [Show full text]
  • Xen and the Linux Console Or: Why Xencons={Tty,Ttys,Xvc} Will Go Away
    Xen and the linux console or: why xencons={tty,ttyS,xvc} will go away. by Gerd Hoffmann <[email protected]> So, what is the Linux console? Well, there isn't a simple answer to that question. Which is the reason for this paper in the first place. For most users it probably is the screen they are sitting in front of. Which is correct, but it also isn't the full story. Especially there are a bunch of CONFIG_*_CONSOLE kernel options referring to two different (but related) subsystems of the kernel. Introducing virtual terminals (CONFIG_VT) Well, every linux user knows them: Virtual terminals. Using Alt-Fx you can switch between different terminals. Each terminal has its own device, namely /dev/tty<nr>. Most Linux distributions have a getty ready for text login on /dev/tty{1-6} and the X-Server for the graphical login on /dev/tty7. /dev/tty0 is a special case: It referes to the terminal which is visible at the moment. The VT subsystem doesn't draw the characters itself though, it has hardware specific drivers for that. The most frequently used ones are: CONFIG_VGA_CONSOLE VGA text console driver, this one will drive your VGA card if you boot the machine in VGA text mode. CONFIG_FRAMEBUFFER_CONSOLE Provides text screens on top of a graphical display. The graphical display in turn is driven by yet another driver. On x86 this very often is vesafb. Other platforms have generic drivers too. There are also a bunch of drivers for specific hardware, such as rivafb for nvidia cards.
    [Show full text]
  • MC-1200 Series Linux Software User's Manual
    MC-1200 Series Linux Software User’s Manual Version 1.0, November 2020 www.moxa.com/product © 2020 Moxa Inc. All rights reserved. MC-1200 Series Linux Software User’s Manual The software described in this manual is furnished under a license agreement and may be used only in accordance with the terms of that agreement. Copyright Notice © 2020 Moxa Inc. All rights reserved. Trademarks The MOXA logo is a registered trademark of Moxa Inc. All other trademarks or registered marks in this manual belong to their respective manufacturers. Disclaimer Information in this document is subject to change without notice and does not represent a commitment on the part of Moxa. Moxa provides this document as is, without warranty of any kind, either expressed or implied, including, but not limited to, its particular purpose. Moxa reserves the right to make improvements and/or changes to this manual, or to the products and/or the programs described in this manual, at any time. Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes no responsibility for its use, or for any infringements on the rights of third parties that may result from its use. This product might include unintentional technical or typographical errors. Changes are periodically made to the information herein to correct such errors, and these changes are incorporated into new editions of the publication. Technical Support Contact Information www.moxa.com/support Moxa Americas Moxa China (Shanghai office) Toll-free: 1-888-669-2872 Toll-free: 800-820-5036 Tel: +1-714-528-6777 Tel: +86-21-5258-9955 Fax: +1-714-528-6778 Fax: +86-21-5258-5505 Moxa Europe Moxa Asia-Pacific Tel: +49-89-3 70 03 99-0 Tel: +886-2-8919-1230 Fax: +49-89-3 70 03 99-99 Fax: +886-2-8919-1231 Moxa India Tel: +91-80-4172-9088 Fax: +91-80-4132-1045 Table of Contents 1.
    [Show full text]
  • Linux Kernel and Driver Development Training Slides
    Linux Kernel and Driver Development Training Linux Kernel and Driver Development Training © Copyright 2004-2021, Bootlin. Creative Commons BY-SA 3.0 license. Latest update: October 9, 2021. Document updates and sources: https://bootlin.com/doc/training/linux-kernel Corrections, suggestions, contributions and translations are welcome! embedded Linux and kernel engineering Send them to [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/470 Rights to copy © Copyright 2004-2021, Bootlin License: Creative Commons Attribution - Share Alike 3.0 https://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Document sources: https://github.com/bootlin/training-materials/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/470 Hyperlinks in the document There are many hyperlinks in the document I Regular hyperlinks: https://kernel.org/ I Kernel documentation links: dev-tools/kasan I Links to kernel source files and directories: drivers/input/ include/linux/fb.h I Links to the declarations, definitions and instances of kernel symbols (functions, types, data, structures): platform_get_irq() GFP_KERNEL struct file_operations - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/470 Company at a glance I Engineering company created in 2004, named ”Free Electrons” until Feb.
    [Show full text]
  • El Núcleo Linux
    El núcleo Linux Josep Jorba Esteve PID_00174426 GNUFDL • PID_00174426 El núcleo Linux Índice Introducción ................................................... ....... 5 Objetivos ................................................... ............ 6 1. El núcleo del sistema GNU/Linux .............................. 7 2. Personalización o actualización del núcleo................... 15 3. Proceso de configuración y compilación ...................... 18 3.1. Compilación antigua de la rama 2.4.x del núcleo . 20 3.2. Migración de 2.4 a la rama 2.6.x del núcleo. 25 3.3. Compilación de la rama 2.6.x del núcleo . 27 3.4. Compilación del núcleo en Debian (Debian Way)............. 30 4. Aplicación de parches al núcleo ................................ 35 5. Módulos del núcleo ............................................... 38 5.1. DKMS: módulos recompilados dinámicamente . 41 6. Virtualización en el núcleo ..................................... 44 6.1. KVM ............................................ .............. 46 7. Futuro del núcleo y alternativas ............................... 53 8. Taller de configuración del núcleo a las necesidades del usuario................................................... ...... 58 8.1. Configuración del núcleo en Debian . 58 8.2. Configuración del núcleo en Fedora/Red Hat . 61 8.3. Configuración de un núcleo genérico . 63 Resumen ................................................... ............ 66 Actividades ................................................... ......... 67 Bibliografía ..................................................
    [Show full text]
  • Enabling Hardware Accelerated Video Decode on Intel® Atom™ Processor D2000 and N2000 Series Under Fedora 16
    Enabling Hardware Accelerated Video Decode on Intel® Atom™ Processor D2000 and N2000 Series under Fedora 16 Application Note October 2012 Order Number: 509577-003US INFORMATIONLegal Lines and Disclaimers IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. A “Mission Critical Application” is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death. SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked “reserved” or “undefined”.
    [Show full text]
  • Practical Practical
    PRACTICAL PRACTICAL GPLCOMPLIANCE GPLCOMPLIANCE A GUIDE FOR STARTUPS, SMALL ABUSINESSES GUIDE FOR STARTUPS, AND ENGINEERS SMALL BUSINESSES AND ENGINEERS ARMIJN HEMEL, MSC AND SHANE COUGHLAN ARMIJN HEMEL, MSC AND SHANE COUGHLAN Copyright © 2017 Linux Foundation All rights reserved. This book or any portion thereof may not be reproduced or used in any manner whatsoever without the express written permission of the publisher except for the use of brief quotations in a book review and certain other noncommercial uses permitted by copyright law. Printed in the United States of America First Edition, 2017 ISBN: 978-0-9989078-0-2 1 Letterman Drive Building D Suite D4700 San Francisco CA 94129 Phone/Fax: +1 415 723 9709 https://linuxfoundation.org About the Authors Shane Coughlan Shane Coughlan is an expert in communi- cation, security, and business development. His professional accomplishments include spearheading the licensing team that elevated Open Invention Network into the largest patent non-aggression community in history, establishing the leading professional network of open source legal experts, and aligning stakeholders to launch both the first law journal and the first law book dedicated to open source. He currently leads the OpenChain community as Program Manager. Shane has extensive knowledge of open source governance, internal process development, supply chain management, and community building. His experience includes engagement with the enterprise, embedded, mobile, and automotive industries. Armijn Hemel Armijn Hemel is the owner of Tjaldur Software Governance Solutions. He is an active re- searcher of and internationally recognized expert in open source license compliance and supply chain management. He studied computer science at Utrecht University in The Netherlands, where he pioneered reproducible builds with NixOS.
    [Show full text]
  • Compiling Your Own Kernel Getting the Kernel Configuring the Kernel
    Williams College Meeting 4 Compiling Your Own Kernel In this meeting, we will use several tools to: • download the latest stable kernel • customize the kernel config file • compile the kernel and kernel modules • set the default system kernel to be a kernel of your choosing • explore the kernel source code using the LXR Cross Referencer Getting the Kernel The kernel source code is available at kernel.org. On the main page, there is a big yellow box that says Latest Stable Kernel. It may be tempting to press that button. Resist the urge: clicking that link will download the latest stable kernel as a compressed “tarball”. A tarball is good for today, but we don’t want to live in the present. The kernel source is actively developed by a heterogeneous community of developers, with updates and changes managed using git. We want to get the Linux source using git so that we can access the history of old kernel versions, as well as access new releases when they are published. Step one for today’s meeting is to find the “mainline” Linux source’s git repository. • Where is mainline kernel’s git repository? What are the meanings of the following terms (in relationship to the Linux development process), and how are they represented in the Linux git repository? • mainline • longterm • stable • prepatch (Hint: Use git to clone this repository to a directory called linux-stable-src/, and explore the git repository using git-log, git-branch, and git-tag.) • Now execute the command: $ uname -r What is the output? • What is a “distribution” kernel? • Is your system using a mainline or distribution kernel? Configuring the Kernel There are many good online guides for building your kernel.
    [Show full text]
  • Debian GNU/Linux Installation Guide
    Debian GNU/Linux Installation Guide July 31, 2021 Debian GNU/Linux Installation Guide Copyright © 2004 – 2021 the Debian Installer team This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License. Please refer to the license in Appendix F. Build version of this manual: 20210730. i Contents 1 Welcome to Debian 1 1.1 What is Debian? . 1 1.2 What is GNU/Linux? . 1 1.3 What is Debian GNU/Linux? . 2 1.4 What is the Debian Installer? . 3 1.5 Getting Debian . 3 1.6 Getting the Newest Version of This Document . 3 1.7 Organization of This Document . 3 1.8 About Copyrights and Software Licenses . 4 2 System Requirements 5 2.1 Supported Hardware . 5 2.1.1 Supported Architectures . 5 2.1.2 Three different ARM ports . 6 2.1.3 Variations in ARM CPU designs and support complexity . 6 2.1.4 Platforms supported by Debian/armhf . 6 2.1.5 Platforms no longer supported by Debian/armhf . 8 2.1.6 Multiple Processors . 8 2.1.7 Graphics Hardware Support . 8 2.1.8 Network Connectivity Hardware . 8 2.1.9 Peripherals and Other Hardware . 8 2.2 Devices Requiring Firmware . 8 2.3 Purchasing Hardware Specifically for GNU/Linux . 9 2.3.1 Avoid Proprietary or Closed Hardware . 9 2.4 Installation Media . 9 2.4.1 CD-ROM/DVD-ROM/BD-ROM . 9 2.4.2 Network . 10 2.4.3 Hard Disk . 10 2.4.4 Un*x or GNU system .
    [Show full text]
  • Debian GNU/Linux Installation Guide
    Debian GNU/Linux Installation Guide July 31, 2021 Debian GNU/Linux Installation Guide Copyright © 2004 – 2021 the Debian Installer team This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License. Please refer to the license in Appendix F. Build version of this manual: 20210730. i Contents 1 Welcome to Debian 1 1.1 What is Debian? . 1 1.2 What is GNU/Linux? . 1 1.3 What is Debian GNU/Linux? . 2 1.4 What is the Debian Installer? . 3 1.5 Getting Debian . 3 1.6 Getting the Newest Version of This Document . 3 1.7 Organization of This Document . 3 1.8 About Copyrights and Software Licenses . 4 2 System Requirements 5 2.1 Supported Hardware . 5 2.1.1 Supported Architectures . 5 2.1.2 CPU, Main Boards, and Video Support . 6 2.1.2.1 CPU . 6 2.1.2.2 I/O Bus . 6 2.1.3 Laptops . 6 2.1.4 Multiple Processors . 6 2.1.5 Graphics Hardware Support . 6 2.1.6 Network Connectivity Hardware . 7 2.1.6.1 Wireless Network Cards . 7 2.1.7 Braille Displays . 7 2.1.8 Hardware Speech Synthesis . 7 2.1.9 Peripherals and Other Hardware . 7 2.2 Devices Requiring Firmware . 7 2.3 Purchasing Hardware Specifically for GNU/Linux . 8 2.3.1 Avoid Proprietary or Closed Hardware . 8 2.4 Installation Media . 8 2.4.1 CD-ROM/DVD-ROM/BD-ROM . 9 2.4.2 USB Memory Stick .
    [Show full text]