From 1ea73eea5ecc6a8ed901316049259aee737ee554 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 7 Oct 2005 19:51:38 +0000 Subject: move manual to top-level directory, split out of debian-installer package --- da/hardware/hardware-supported.xml | 345 ++++++++++++++++++++++++ da/hardware/hardware.xml | 21 ++ da/hardware/installation-media.xml | 317 +++++++++++++++++++++++ da/hardware/memory-disk-requirements.xml | 47 ++++ da/hardware/network-cards.xml | 214 +++++++++++++++ da/hardware/supported-peripherals.xml | 186 +++++++++++++ da/hardware/supported/alpha.xml | 432 +++++++++++++++++++++++++++++++ da/hardware/supported/arm.xml | 96 +++++++ da/hardware/supported/hppa.xml | 17 ++ da/hardware/supported/i386.xml | 37 +++ da/hardware/supported/ia64.xml | 3 + da/hardware/supported/m68k.xml | 39 +++ da/hardware/supported/mips.xml | 52 ++++ da/hardware/supported/mipsel.xml | 146 +++++++++++ da/hardware/supported/powerpc.xml | 248 ++++++++++++++++++ da/hardware/supported/s390.xml | 21 ++ da/hardware/supported/sparc.xml | 82 ++++++ 17 files changed, 2303 insertions(+) create mode 100644 da/hardware/hardware-supported.xml create mode 100644 da/hardware/hardware.xml create mode 100644 da/hardware/installation-media.xml create mode 100644 da/hardware/memory-disk-requirements.xml create mode 100644 da/hardware/network-cards.xml create mode 100644 da/hardware/supported-peripherals.xml create mode 100644 da/hardware/supported/alpha.xml create mode 100644 da/hardware/supported/arm.xml create mode 100644 da/hardware/supported/hppa.xml create mode 100644 da/hardware/supported/i386.xml create mode 100644 da/hardware/supported/ia64.xml create mode 100644 da/hardware/supported/m68k.xml create mode 100644 da/hardware/supported/mips.xml create mode 100644 da/hardware/supported/mipsel.xml create mode 100644 da/hardware/supported/powerpc.xml create mode 100644 da/hardware/supported/s390.xml create mode 100644 da/hardware/supported/sparc.xml (limited to 'da/hardware') diff --git a/da/hardware/hardware-supported.xml b/da/hardware/hardware-supported.xml new file mode 100644 index 000000000..94f0d7a3d --- /dev/null +++ b/da/hardware/hardware-supported.xml @@ -0,0 +1,345 @@ + + + + + Supported Hardware + + + +Debian does not impose hardware requirements beyond the requirements +of the Linux kernel and the GNU tool-sets. Therefore, any +architecture or platform to which the Linux kernel, libc, +gcc, etc. have been ported, and for which a Debian +port exists, can run Debian. Please refer to the Ports pages at + for +more details on &arch-title; architecture systems which have been +tested with Debian. + + + +Rather than attempting to describe all the different hardware +configurations which are supported for &arch-title;, this section +contains general information and pointers to where additional +information can be found. + + + + Supported Architectures + + + +Debian &release; supports eleven major architectures and several +variations of each architecture known as 'flavors'. + + + + + + + + ArchitectureDebian Designation + SubarchitectureFlavor + + + + + + Intel x86-based + i386 + + vanilla + + speakup + + linux26 + + + + Motorola 680x0 + m68k + Atari + atari + + Amiga + amiga + + 68k Macintosh + mac + + VME + bvme6000 + + mvme147 + + mvme16x + + + + DEC Alpha + alpha + + generic + + jensen + + nautilus + + + + Sun SPARC + sparc + + sun4cdm + + sun4u + + + + ARM and StrongARM + arm + + netwinder + + riscpc + + shark + + lart + + + + IBM/Motorola PowerPC + powerpc + CHRP + chrp + + PowerMac + powermac, new-powermac + + PReP + prep + + APUS + apus + + + + HP PA-RISC + hppa + PA-RISC 1.1 + 32 + + PA-RISC 2.0 + 64 + + + + Intel ia64-based + ia64 + + + + + + MIPS (big endian) + mips + SGI Indy/Indigo 2 + r4k-ip22 + + r5k-ip22 + + Broadcom BCM1250 (SWARM) + sb1-swarm-bn + + + + MIPS (little endian) + mipsel + Cobalt + cobalt + + DECstation + r4k-kn04 + + r3k-kn02 + + Broadcom BCM1250 (SWARM) + sb1-swarm-bn + + + + IBM S/390 + s390 + + tape + + vmrdr + + + + + + +This document covers installation for the +&arch-title; architecture. If you are looking +for information on any of the other Debian-supported architectures +take a look at the +Debian-Ports pages. + + + +This is the first official release of &debian; for the &arch-title; +architecture. We feel that it has proven itself sufficiently to be +released. However, because it has not had the exposure (and hence +testing by users) that some other architectures have had, you may +encounter a few bugs. Use our +Bug Tracking System to report any +problems; make sure to mention the fact that the bug is on the +&arch-title; platform. It can be necessary to use the +debian-&architecture; mailing list +as well. + + + + + + +&supported-alpha.xml; +&supported-arm.xml; +&supported-hppa.xml; +&supported-i386.xml; +&supported-ia64.xml; +&supported-m68k.xml; +&supported-mips.xml; +&supported-mipsel.xml; +&supported-powerpc.xml; +&supported-s390.xml; +&supported-sparc.xml; + + Graphics Card + + + +You should be using a VGA-compatible display interface for the console +terminal. Nearly every modern display card is compatible with +VGA. Ancient standards such CGA, MDA, or HGA should also work, +assuming you do not require X11 support. Note that X11 is not used +during the installation process described in this document. + + + +Debian's support for graphical interfaces is determined by the +underlying support found in XFree86's X11 system. The newer AGP video +slots are actually a modification on the PCI specification, and most +AGP video cards work under XFree86. Details on supported graphics +buses, cards, monitors, and pointing devices can be found at +. Debian &release; ships +with XFree86 version &x11ver;. + + + +The XFree86 X11 window system is only supported on the SGI Indy. The +Broadcom BCM1250 evaluation board has standard 3.3v PCI slots and supports +VGA emulation or Linux framebuffer on a selected range of graphics cards. +A compatibility listing for +the BCM1250 is available. + + + +The XFree86 X11 window system is supported on some DECstation models. The +Broadcom BCM1250 evaluation board has standard 3.3v PCI slots and supports +VGA emulation or Linux framebuffer on a selected range of graphics cards. +A compatibility listing for +the BCM1250 is available. + + + + + + Laptops + + +Laptops are also supported. Laptops are often specialized or contain +proprietary hardware. To see if your particular laptop works well +with GNU/Linux, see the +Linux Laptop pages + + + + + + +Multiple Processors + + + +Multi-processor support — also called ``symmetric multi-processing'' +or SMP — is supported for this architecture. The standard Debian +&release; kernel image was compiled with SMP support. This should not +prevent installation, since the SMP kernel should boot on non-SMP systems; +the kernel will simply cause a bit more overhead. + + + +In order to optimize the kernel for single CPU systems, you'll have to +replace the standard Debian kernel. You can find a discussion of how +to do this in . At this time +(kernel version &kernelversion;) the way you disable SMP is to deselect +``symmetric multi-processing'' in the ``General'' section of the +kernel config. + + + + + + + + Multiple Processors + + +Multi-processor support — also called ``symmetric +multi-processing'' or SMP — is supported for this architecture. +However, the standard Debian &release; kernel image does not support +SMP. This should not prevent installation, since the standard, +non-SMP kernel should boot on SMP systems; the kernel will simply use +the first CPU. + + + +In order to take advantage of multiple processors, you'll have to +replace the standard Debian kernel. You can find a discussion of how +to do this in . At this time +(kernel version &kernelversion;) the way you enable SMP is to select +``symmetric multi-processing'' in the ``General'' section of the +kernel config. + + + + + + Multiple Processors + + +Multi-processor support — also called ``symmetric +multi-processing'' or SMP — is supported for this architecture, +and is supported by a precompiled Debian kernel image. Depending on your +install media, this SMP-capable kernel may or may not be installed by +default. This should not prevent installation, since the standard, +non-SMP kernel should boot on SMP systems; the kernel will simply use +the first CPU. + + + +In order to take advantage of multiple processors, you should check to see +if a kernel package that supports SMP is installed, and if not, choose an +appropriate kernel package. + +You can also build your own customised kernel to support SMP. You can find +a discussion of how to do this in . At this +time (kernel version &kernelversion;) the way you enable SMP is to select +``symmetric multi-processing'' in the ``General'' section of the +kernel config. + + + + diff --git a/da/hardware/hardware.xml b/da/hardware/hardware.xml new file mode 100644 index 000000000..166cb9ab1 --- /dev/null +++ b/da/hardware/hardware.xml @@ -0,0 +1,21 @@ + + + + + System Requirements + + + +This section contains information about what hardware you need to get +started with Debian. You will also find links to further information +about hardware supported by GNU and Linux. + + + +&hardware-supported.xml; +&installation-media.xml; +&supported-peripherals.xml; +&memory-disk-requirements.xml; +&network-cards.xml; + + diff --git a/da/hardware/installation-media.xml b/da/hardware/installation-media.xml new file mode 100644 index 000000000..88ff2c209 --- /dev/null +++ b/da/hardware/installation-media.xml @@ -0,0 +1,317 @@ + + + + + Installation Media + + + +This section will help you determine which different media types you can use to +install Debian. For example, if you have a floppy disk drive on your machine, +it can be used to install Debian. There is a whole chapter devoted media, +, which lists the advantages and +disadvantages of each media type. You may want to refer back to this page once +you reach that section. + + + + Floppies + + +In some cases, you'll have to do your first boot from floppy disks. +Generally, all you will need is a +high-density (1440 kilobytes) 3.5 inch floppy drive. + + + +For CHRP, floppy support is currently broken. + + + + + CD-ROM/DVD-ROM + + + +Whenever you see CD-ROM in this manual, it applies to both +CD-ROMs and DVD-ROMs, because both technologies are really +the same from the operating system's point of view, except for some very +old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI. + + + +CD-ROM based installation is supported for some architectures. +On machines which support bootable CD-ROMs, you should be able to do a +completely +floppy-less +tape-less +installation. Even if your system doesn't +support booting from a CD-ROM, you can use the CD-ROM in conjunction +with the other techniques to install your system, once you've booted +up by other means; see . + + + +Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all +non-standard CD interfaces supported by Linux are supported by the +boot disks (such as Mitsumi and Matsushita drives). However, these +models might require special boot parameters or other massaging to get +them to work, and booting off these non-standard interfaces is +unlikely. The Linux CD-ROM HOWTO +contains in-depth information on using CD-ROMs with Linux. + + + +USB CD-ROM drives are also supported, as are FireWire devices that +are supported by the ohci1394 and sbp2 drivers. + + + +IDE/ATAPI CD-ROMs are supported on all ARM machines. +On RiscPCs, SCSI CD-ROMs are also supported. + + + +On SGI machines, it is possible to boot from CD and images are provided. +To start the install, simply choose the System installation +entry in the firmware. The Broadcom BCM1250 supports standard IDE devices, +including CD-ROM drives, but CD images for this platform are currently not +provided because the firmware doesn't recognize CD drives. + + + +On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive +capable of working with a logical blocksize of 512 bytes. Many of the +SCSI CD-DROM drives sold for the PC market do not have this +capability. If your CD-ROM drive has a jumper labeled "Unix/PC" or +"512/2048", place it in the "Unix" or "512" position. + + + +CD 1 contains the installer for the r3k-kn02 subarchitecture +(the R3000-based DECstations 5000/1xx and 5000/240 as well as +the R3000-based Personal DECstation models), CD 2 the +installer for the r4k-kn04 subarchitecture (the R4x00-based +DECstations 5000/150 and 5000/260 as well as the Personal DECstation +5000/50). + + + +To boot from CD, issue the command boot +#/rzid +on the firmware prompt, where # is the +number of the TurboChannel device from which to boot (3 on most +DECstations) and id is the SCSI ID of the +CD-ROM drive. If you need to pass additional parameters, they can +optionally be appended with the following syntax: + + + +boot +#/rzid +param1=value1 param2=value2 ... + + + + + Hard Disk + + + +Booting the installation system directly from a hard disk is another option +for many architectures. This will require some other operating system +to load the installer onto the hard disk. + + + +In fact, installation from your local disk is the preferred +installation technique for most &architecture; machines. + + + +Although the &arch-title; does not allow booting from SunOS +(Solaris), you can install from a SunOS partiton (UFS slices). + + + + + USB Memory Stick + + + +Many Debian boxes need their floppy and/or CD-ROM drives only for +setting up the system and for rescue purposes. If you operate some +servers, you will probably already have thought about omitting those +drives and using an USB memory stick for installing and (when +necessary) for recovering the system. This is also useful for small +systems which have no room for unnecessary drives. + + + + + Network + + + +You can also boot your system over the network. +This is the preferred installation technique for +Mips. + + + +Diskless installation, using network booting from a local area network +and NFS-mounting of all local filesystems, is another option. + + + +After the operating system kernel is installed, you can install the +rest of your system via any sort of network connection (including +PPP after installation of the base system), via FTP or HTTP. + + + + + Un*x or GNU system + + + +If you are running other Unix-like system, you could use it to install +&debian; without using the &d-i; described in the rest of the +manual. This kind of install may be useful for users with otherwise +unsupported hardware or on hosts which can't afford downtimes. If you +are interested in this technique, skip to the . + + + + + Supported Storage Systems + + + +The Debian boot disks contain a kernel which is built to maximize the +number of systems it runs on. Unfortunately, this makes for a larger +kernel, which includes many drivers that won't be used for your +machine (see to learn how to +build your own kernel). Support for the widest possible range of +devices is desirable in general, to ensure that Debian can be +installed on the widest array of hardware. + + + +Generally, the Debian installation system includes support for floppies, +IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and +drives, USB, and FireWire. The file systems supported include FAT, +Win-32 FAT extensions (VFAT), and NTFS, among others. + + + +The disk interfaces that emulate the ``AT'' hard disk interface which +are often called MFM, RLL, IDE, or ATA are supported. Very old 8 bit +hard disk controllers used in the IBM XT computer are supported only +as a module. SCSI disk controllers from many different manufacturers +are supported. See the +Linux Hardware Compatibility HOWTO +for more details. + + + +Pretty much all storage systems supported by the Linux kernel are +supported by the Debian installation system. Note that the current +Linux kernel does not support floppies on the Macintosh at all, and +the Debian installation system doesn't support floppies for Amigas. +Also supported on the Atari is the Macintosh HFS system, and AFFS as a +module. Macs support the Atari (FAT) file system. Amigas support the +FAT file system, and HFS as a module. + + + +Any storage system supported by the Linux kernel is also supported by +the boot system. The following SCSI drivers are supported in the default +kernel: + + + + +Sparc ESP + + + + +PTI Qlogic,ISP + + + + +Adaptec AIC7xxx + + + + +NCR and Symbios 53C8XX + + + + +IDE systems (such as the UltraSPARC 5) are also supported. See +Linux for SPARC Processors FAQ +for more information on SPARC hardware supported by the Linux kernel. + + + +Any storage system supported by the Linux kernel is also supported by +the boot system. The following SCSI drivers are supported in the default +kernel: + + + + +Qlogic ISP + + + + +NCR and Symbios 53c8xx + + + + +Adaptec AIC7xxx + + + + +IDE disks are also supported. Note, however, that on many systems, +the SRM console is unable to boot from IDE drives, and the Jensen is +unable to boot from floppies. (see + +for more information on booting the Jensen) + + + +Any storage system supported by the Linux kernel is also supported by +the boot system. Note that the current Linux kernel does not support +floppies on CHRP systems at all. + + + +Any storage system supported by the Linux kernel is also supported by +the boot system. Note that the current Linux kernel does not support +the floppy drive. + + + +Any storage system supported by the Linux kernel is also supported by +the boot system. + + + +Any storage system supported by the Linux kernel is also supported by +the boot system. This means that FBA and ECKD DASDs are supported with +the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl). + + + + + + diff --git a/da/hardware/memory-disk-requirements.xml b/da/hardware/memory-disk-requirements.xml new file mode 100644 index 000000000..6bb18618e --- /dev/null +++ b/da/hardware/memory-disk-requirements.xml @@ -0,0 +1,47 @@ + + + + + Memory and Disk Space Requirements + + + +You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk +space. For a minimal console-based system (all standard packages), +250MB is required. If you want to install a reasonable amount of +software, including the X Window System, and some development programs +and libraries, you'll need at least 400MB. For a more or less complete +desktop system, you'll need a few gigabytes. + + + +On the Amiga the size of FastRAM is relevant towards the total memory +requirements. Also, using Zorro cards with 16-bit RAM is not +supported; you'll need 32-bit RAM. The amiboot +program can be used to disable 16-bit RAM; see the +Linux/m68k FAQ. Recent kernels should +disable 16-bit RAM automatically. + + + +On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. +Many users have reported problems running the kernel itself in Fast +RAM, so the Atari bootstrap will place the kernel in ST-RAM. The +minimum requirement for ST-RAM is 2 MB. You will need an additional +12 MB or more of TT-RAM. + + + +On the Macintosh, care should be taken on machines with RAM-based +video (RBV). The RAM segment at physical address 0 is used as screen +memory, making the default load position for the kernel unavailable. +The alternate RAM segment used for kernel and RAMdisk must be at least +4 MB. + + + +FIXME: is this still true? + + + + diff --git a/da/hardware/network-cards.xml b/da/hardware/network-cards.xml new file mode 100644 index 000000000..4b7bd9f31 --- /dev/null +++ b/da/hardware/network-cards.xml @@ -0,0 +1,214 @@ + + + + + Network Connectivity Hardware + + + + + +Most PCI and many older ISA network cards are supported. +Some network interface cards are not supported by most Debian +installation disks, such as AX.25 cards and protocols; +NI16510 EtherBlaster cards; Schneider & Koch G16 cards; +and the Zenith Z-Note built-in network card. Microchannel (MCA) network +cards are not supported by the standard installation system, but see +Linux on MCA for some (old) +instructions, and the +Linux MCA discussion archives. +FDDI networks are also not supported by the installation disks, both +cards and protocols. + + + + + +As for ISDN, the D-channel protocol for the (old) German 1TR6 is not +supported; Spellcaster BRI ISDN boards are also not supported by the +&d-i;. + + + + + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. Again, see + for complete details. + + + + + +The following network interface cards (NICs) are supported from the bootable +kernel directly: + + + + +Sun LANCE + + + + + +Sun Happy Meal + + + + + + + +The following network interface cards are supported as modules. They +can be enabled once the drivers are installed during the setup. +However, due to the magic of OpenPROM, you still should be able to +boot from these devices: + + + + +Sun BigMAC + + + + + +Sun QuadEthernet + + + + +MyriCOM Gigabit Ethernet + + + + + + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. Support for the built-in DECChip +(Tulip) Ethernet on many Alpha models is compiled directly into the +kernel. For other cards, you may need to load your network driver as a +module. + + + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + + + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + + + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + + + +Due to kernel limitations only the onboard network interfaces on +DECstations are supported, TurboChannel option network cards currently +do not work. + + + +Any network interface card (NIC) supported by the Linux kernel are +also be supported by the boot disks. All network drivers are compiled +as modules so you need to load one first during the initial network +setup. The list of supported network devices is: + + + + +Channel to Channel (CTC) or ESCON connection (real or emulated) + + + + + +lcs: OSA-2 Token Ring/Ethernet or OSA-Express Fast Ethernet + (non-QDIO) + + + + +Inter-User Communication Vehicle (IUCV) - available for VM + guests only + + + + +qeth: OSA-Express in QDIO mode / HiperSockets + + + + + + + + +The following network interface cards are supported directly by the +boot disks on NetWinder and CATS machines: + + + + + PCI-based NE2000 + + + + + + DECchip Tulip + + + + + + +The following network interface cards are supported directly by the +boot disks on RiscPCs: + + + + + Ether1 + + + + + Ether3 + + + + + EtherH + + + + + + +If your card is mentioned in the lists above, the complete installation +can be carried out from the network with no need for CD-ROMs or floppy +disks. + + + +Any other network interface card (NIC) supported by the Linux kernel +should also be supported by the boot disks. You may need to load your +network driver as a module; this means that you will have to install +the operating system kernel and modules using some other media. + + + + diff --git a/da/hardware/supported-peripherals.xml b/da/hardware/supported-peripherals.xml new file mode 100644 index 000000000..bedc8ed93 --- /dev/null +++ b/da/hardware/supported-peripherals.xml @@ -0,0 +1,186 @@ + + + + + Peripherals and Other Hardware + + +Linux supports a large variety of hardware devices such as mice, +printers, scanners, PCMCIA and USB devices. However, most of these +devices are not required while installing the system. + + + +USB hardware generally works fine, only some +USB keyboards may require additional configuration +(see ). + + + +Again, see the +Linux Hardware Compatibility HOWTO +to determine whether your specific hardware is supported by Linux. + + + +Package installations from XPRAM and tape are not supported by this +system. All packages that you want to install need to be available on a +DASD or over the network using NFS, HTTP or FTP. + + + +The Broadcom BCM1250 evaluation board offers standard 3.3v 32 bit and 64 +bit PCI slots as well as USB connectors. + + + +The Broadcom BCM1250 evaluation board offers standard 3.3v 32 bit and 64 +bit PCI slots as well as USB connectors. The Cobalt RaQ has no support for +additional devices but the Qube has one PCI slot. + + + + + Purchasing Hardware Specifically for GNU/Linux + + + +There are several vendors, who ship systems with Debian or other +distributions of GNU/Linux +pre-installed. You might pay more +for the privilege, but it does buy a level of peace of mind, since you can +be sure that the hardware is well-supported by GNU/Linux. + + + +Unfortunately, it's quite rare to find any vendor shipping +new &arch-title; machines at all. + + + +If you do have to buy a machine with Windows bundled, carefully read +the software license that comes with Windows; you may be able to +reject the license and obtain a rebate from your vendor. See + for complete details. + + + +Whether or not you are purchasing a system with Linux bundled, or even +a used system, it is still important to check that your hardware is +supported by the Linux kernel. Check if your hardware is listed in +the references found above. Let your salesperson (if any) know that +you're shopping for a Linux system. Support Linux-friendly hardware +vendors. + + + + Avoid Proprietary or Closed Hardware + + +Some hardware manufacturers simply won't tell us how to write drivers +for their hardware. Others won't allow us access to the documentation +without a non-disclosure agreement that would prevent us from +releasing the Linux source code. + + + +Another example is the proprietary hardware in the older +Macintosh line. In fact, no specifications or documentation have ever +been released for any Macintosh hardware, most notably the ADB +controller (used by the mouse and keyboard), the floppy controller, +and all acceleration and CLUT manipulation of the video hardware +(though we do now support CLUT manipulation on nearly all internal +video chips). In a nutshell, this explains why the Macintosh Linux +port lags behind other Linux ports. + + + +Since we haven't been granted access to the documentation on these +devices, they simply won't work under Linux. You can help by asking +the manufacturers of such hardware to release the documentation. If +enough people ask, they will realize that the free software community +is an important market. + + + + + + Windows-specific Hardware + + +A disturbing trend is the proliferation of Windows-specific modems and +printers. In some cases these are specially designed to be operated by +the Microsoft Windows operating system and bear the legend +``WinModem'' or ``Made especially for Windows-based computers''. This +is generally done by removing the embedded processors of the hardware +and shifting the work they do over to a Windows driver that is run by +your computer's main CPU. This strategy makes the hardware less +expensive, but the savings are often not passed on to the +user and this hardware may even be more expensive than equivalent +devices that retain their embedded intelligence. + + + +You should avoid Windows-specific hardware for two reasons. The first +is that the manufacturers do not generally make the resources +available to write a Linux driver. Generally, the hardware and +software interface to the device is proprietary, and documentation is +not available without a non-disclosure agreement, if it is available +at all. This precludes its being used for free software, since free +software writers disclose the source code of their programs. The +second reason is that when devices like these have had their embedded +processors removed, the operating system must perform the work of the +embedded processors, often at real-time priority, +and thus the CPU is not available to run your programs while it is +driving these devices. Since the typical Windows user does not +multi-process as intensively as a Linux user, the manufacturers hope +that the Windows user simply won't notice the burden this hardware +places on their CPU. However, any multi-processing operating system, +even Windows 2000 or XP, suffers from degraded performance when +peripheral manufacturers skimp on the embedded processing power of +their hardware. + + + +You can help this situation by encouraging these manufacturers to +release the documentation and other resources necessary for us to +program their hardware, but the best strategy is simply to avoid this +sort of hardware until it is listed as working in the +Linux Hardware Compatibility HOWTO. + + + + + + + Fake or <quote>Virtual</quote> Parity RAM + + +If you ask for Parity RAM in a computer store, you'll probably get +virtual parity memory modules instead of +true parity ones. Virtual parity SIMMs can often +(but not always) be distinguished because they only have one more chip +than an equivalent non-parity SIMM, and that one extra chip is smaller +than all the others. Virtual-parity SIMMs work exactly like non-parity +memory. They can't tell you when you have a single-bit RAM error the +way true-parity SIMMs do in a motherboard that implements +parity. Don't ever pay more for a virtual-parity SIMM than a +non-parity one. Do expect to pay a little more for true-parity SIMMs, +because you are actually buying one extra bit of memory for every 8 +bits. + + + +If you want complete information on &arch-title; RAM issues, and what +is the best RAM to buy, see the +PC Hardware FAQ. + + + +Most, if not all, Alpha systems require true-parity RAM. + + + + + + diff --git a/da/hardware/supported/alpha.xml b/da/hardware/supported/alpha.xml new file mode 100644 index 000000000..816c89c8b --- /dev/null +++ b/da/hardware/supported/alpha.xml @@ -0,0 +1,432 @@ + + + + + CPU, Main Boards, and Video Support + + +Complete information regarding supported DEC Alphas can be found at +Linux Alpha HOWTO. The +purpose of this section is to describe the systems supported +by the boot disks. + + + +Alpha machines are subdivided into different system types because there +are a number of generations of motherboard and supporting chip-sets. +Different systems (``sub-architectures'') often have radically different +engineering and capabilities. Therefore, the process of installing and, +more to the point, booting, can vary from system to system. + + + +The following table lists the system types supported by the Debian +installation system. The table also indicates the code +name for these system types. You'll need to know this code +name when you actually begin the installation process: + + + + + + + + + + + + Hardware Type + AliasesMILO image + + + + + + ALCOR + AlphaStation 500 5/266.300 + Maverick + alcor + + AlphaStation 500 5/333...500 + Bret + alcor + + AlphaStation 600/266...300 + Alcor + alcor + + AlphaStation 600/300...433 + XLT + xlt + + + + BOOK1 + AlphaBook1 (laptop) + Alphabook1/Burns + book1 + + + + AVANTI + AlphaStation 200 4/100...166 + Mustang + avanti + + AlphaStation 200 4/233 + Mustang+ + avanti + + AlphaStation 205 4/133...333 + LX3 + avanti + + AlphaStation 250 4/300 + M3+ + avanti + + AlphaStation 255 4/133...333 + LX3+ + avanti + + AlphaStation 300 4/266 + Melmac + avanti + + AlphaStation 400 4/166 + Chinet + avanti + + AlphaStation 400 4/233...300 + Avanti + avanti + + + + EB164 + AlphaPC164 + PC164 + pc164 + + AlphaPC164-LX + LX164 + lx164 + + AlphaPC164-SX + SX164 + sx164 + + EB164 + EB164 + eb164 + + + + EB64+ + AlphaPC64 + Cabriolet + cabriolet + + AlphaPCI64 + Cabriolet + cabriolet + + EB64+ + EB64+ + eb64p + + + + EB66 + EB66 + EB66 + eb66 + + EB66+ + EB66+ + eb66p + + + + JENSEN + DEC 2000 Model 300(S) + Jensen + N/A + + DEC 2000 Model 500 + Culzen + N/A + + DECpc 150 + Jensen + N/A + + + + MIATA + Personal WorkStation 433a + Miata + miata + + Personal WorkStation 433au + Miata + miata + + Personal WorkStation 466au + Miata + miata + + Personal WorkStation 500a + Miata + miata + + Personal WorkStation 500au + Miata + miata + + Personal WorkStation 550au + Miata + miata + + Personal WorkStation 600a + Miata + miata + + Personal WorkStation 600au + Miata + miata + + + + MIKASA + AlphaServer 1000 4/200 + Mikasa + mikasa + + AlphaServer 1000 4/233..266 + Mikasa+ + mikasa + + AlphaServer 1000 5/300 + Mikasa-Pinnacle + mikasa + + AlphaServer 1000 5/300 + Mikasa-Primo + mikasa + + + + NAUTILUS + UP1000 + Nautilus + N/A + + UP1100 + Galaxy-Train/Nautilus Jr. + N/A + + + + NONAME + AXPpci33 + Noname + noname + + UDB + Multia + noname + + + + NORITAKE + AlphaServer 1000A 4/233...266 + Noritake + N/A + + AlphaServer 1000A 5/300 + Noritake-Pinnacle + N/A + + AlphaServer 1000A 5/333...500 + Noritake-Primo + N/A + + AlphaServer 800 5/333...500 + Corelle + N/A + + AlphaStation 600 A + Alcor-Primo + N/A + + Digital Server 3300 + Corelle + N/A + + Digital Server 3300R + Corelle + N/A + + + + PLATFORM 2000 + P2K + P2K + p2k + + + + RAWHIDE + AlphaServer 1200 5/xxx + Tincup/DaVinci + N/A + + AlphaServer 4000 5/xxx + Wrangler/Durango + N/A + + AlphaServer 4100 5/xxx + Dodge + N/A + + Digital Server 5300 + Tincup/DaVinci + N/A + + Digital Server 7300 + Dodge + N/A + + + + RUFFIAN + DeskStation AlphaPC164-UX + Ruffian + ruffian + + DeskStation RPL164-2 + Ruffian + ruffian + + DeskStation RPL164-4 + Ruffian + ruffian + + DeskStation RPX164-2 + Ruffian + ruffian + + DeskStation RPX164-4 + Ruffian + ruffian + + Samsung AlphaPC164-BX + Ruffian + ruffian + + + + SABLE + AlphaServer 2000 4/xxx + Demi-Sable + N/A + + AlphaServer 2000 5/xxx + Demi-Gamma-Sable + N/A + + AlphaServer 2100 4/xxx + Sable + N/A + + AlphaServer 2100 5/xxx + Gamma-Sable + N/A + + + + TAKARA + 21164 PICMG SBC + Takara + takara + + + + TITAN + AlphaServer ES45 + Privateer + N/A + + UNKNOWN + Yukon + N/A + + + + TSUNAMI + AlphaServer DS10 + Webbrick + N/A + + AlphaServer DS20 + Catamaran/Goldrush + N/A + + AlphaServer DS20E + Goldrack + N/A + + AlphaServer ES40 + Clipper + N/A + + DP264 + DP264 + N/A + + SMARTengine 21264 PCI/ISA SBC + Eiger + N/A + + UNKNOWN + Warhol + N/A + + UNKNOWN + Windjammer + N/A + + UP2000 + Swordfish + N/A + + XP1000 + Monet/Brisbane + N/A + + XP900 + Webbrick + N/A + + + + WILDFIRE + AlphaServer GS160 + Wildfire + N/A + + AlphaServer GS320 + Wildfire + N/A + + + + XL + XL-233...266 + XL + xl + + + + diff --git a/da/hardware/supported/arm.xml b/da/hardware/supported/arm.xml new file mode 100644 index 000000000..2c330b5bc --- /dev/null +++ b/da/hardware/supported/arm.xml @@ -0,0 +1,96 @@ + + + + + CPU, Main Boards, and Video Support + + + +Each distinct ARM architecture requires its own kernel, because of +this the standard Debian distribution only supports installation on +a number of the most common systems. The Debian userland however may be used by any ARM CPU including xscale. + + + + + +Most ARM CPUs may be run in either endian mode, however almost every +current system implementation uses little-endian mode. Debian +currently only supports little-endian ARM systems. + + + + + +The common supported systems are + + + +Netwinder + + +This is actually the name for the group of machines +based upon the StrongARM 110 CPU and Intel 21285 Nothbridge it +comprises machines are: Netwinder (possibly one of the most common ARM +boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq +personal server (cps, aka skiff). + + + + + +Bast + + +This is a modern ARM 920 board with a 266MHz Samsung +processor. It has integrated IDE, USB, Serial, Parallel, audio, video, +flash and two ethernet ports. This system has a good bootloader which +is also found on the CATS and Riscstation systems. + + + + + +RiscPC + + +This machine is the oldest supported hardware it was released +in 1994. It has RISC OS in ROM, Linux can be booted from that OS using +linloader. The RiscPC has a modular CPU card and typicaly has a 30MHz +610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has +integrated IDE, SVGA video, parallel port, single serial port, ps 2 +keyboard and proprietay mouse port. The proprietary module expansion +bus allows for up to eight expansion cards to be fitted depending on +configuration, several of these modules have Linux drivers. + + + + + +Riscstation + + +This is an inexpensive 56MHz 7500FE based machine with +integrated video, IDE, PS2 keyboard and mouse and two serial +ports. Its lack of processing power was made up for by its price. It +may be found in two configurations one with RISC OS and one with a +simple bootloader. + + + + + +LART + + +This is a modular open hardware platform intended to be built +be enthusiasts. To be useful to install Debian it requires its KSB +expansion board. + + + + + + + + diff --git a/da/hardware/supported/hppa.xml b/da/hardware/supported/hppa.xml new file mode 100644 index 000000000..6f3c8c8ee --- /dev/null +++ b/da/hardware/supported/hppa.xml @@ -0,0 +1,17 @@ + + + + + CPU, Main Boards, and Video Support + + +The are two major support &architecture; flavors: +PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted +at 32-bit processors whereas the 2.0 architecture is targeted to +the 64-bit processors. Some systems are able to run either kernel. +In both cases, the userland is 32-bit. There is the possibility of +a 64-bit userland in the future. + + + + diff --git a/da/hardware/supported/i386.xml b/da/hardware/supported/i386.xml new file mode 100644 index 000000000..725a5169b --- /dev/null +++ b/da/hardware/supported/i386.xml @@ -0,0 +1,37 @@ + + + + + CPU, Main Boards, and Video Support + + +Complete information concerning supported peripherals can be found at +Linux Hardware Compatibility HOWTO. +This section merely outlines the basics. + + + + CPU + + +Nearly all x86-based processors are supported; this includes AMD and +VIA (former Cyrix) processors as well. Also the new processors like +Athlon XP and Intel P4 Xeon are supported. However, Linux will +not run on 286 or earlier processors. + + + + + I/O Bus + + +The system bus is the part of the motherboard which allows the CPU to +communicate with peripherals such as storage devices. Your computer +must use the ISA, EISA, PCI, the Microchannel Architecture (MCA, used +in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL +bus). + + + + + diff --git a/da/hardware/supported/ia64.xml b/da/hardware/supported/ia64.xml new file mode 100644 index 000000000..0dabd4a41 --- /dev/null +++ b/da/hardware/supported/ia64.xml @@ -0,0 +1,3 @@ + + + diff --git a/da/hardware/supported/m68k.xml b/da/hardware/supported/m68k.xml new file mode 100644 index 000000000..6e165f6e7 --- /dev/null +++ b/da/hardware/supported/m68k.xml @@ -0,0 +1,39 @@ + + + + CPU, Main Boards, and Video Support + + +Complete information concerning supported M68000 based +(&architecture;) systems can be found at the +Linux/m68k FAQ. This section merely +outlines the basics. + + + +The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged +Memory Management Unit) and a FPU (floating-point unit). This +includes the 68020 with an external 68851 PMMU, the 68030, and better, +and excludes the ``EC'' line of 680x0 processors. See the +Linux/m68k FAQ for complete details. + + + +There are four major flavors of supported +&architecture; flavors: Amiga, Atari, Macintosh +and VME machines. Amiga and Atari were the first two systems to which +Linux was ported; in keeping, they are also the two most +well-supported Debian ports. The Macintosh line is supported +incompletely, both by Debian and by the Linux kernel; see +Linux m68k for Macintosh for project +status and supported hardware. The BVM and Motorola single board +VMEbus computers are the most recent addition to the list of machines +supported by Debian. Ports to other &architecture; architectures, +such as the Sun3 architecture and NeXT black box, are underway but not +yet supported by Debian. + + + + + + diff --git a/da/hardware/supported/mips.xml b/da/hardware/supported/mips.xml new file mode 100644 index 000000000..5b4c53f27 --- /dev/null +++ b/da/hardware/supported/mips.xml @@ -0,0 +1,52 @@ + + + + + CPU, Main Boards, and Video Support + + +Debian on &arch-title; currently supports two subarchitectures: + + + + +SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and +Challenge S. Since these machines are very similar, whenever this document +refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. + + + + +Broadcom BCM1250 (SWARM): this is an ATX form factor evaluation board from +Broadcom based on their SiByte processor family. + + + + +Complete information regarding supported mips/mipsel machines can be found +at the Linux-MIPS homepage. In the +following, only the systems supported by the Debian installer will be +covered. If you are looking for support for other subarchitectures, please +contact the +debian-&architecture; mailing list. + + + + CPU + + +On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400 and R5000 +processors are supported by the Debian installation system on big endian +MIPS. The Broadcom BCM1250 evaluation board comes with an SB1250 chip with +two cores which are supported in SMP mode by this installer. + + + +Some MIPS machines can be operated in both big and little endian mode. For +little endian MIPS, please read the documentation for the mipsel +architecture. + + + + + diff --git a/da/hardware/supported/mipsel.xml b/da/hardware/supported/mipsel.xml new file mode 100644 index 000000000..a0d355211 --- /dev/null +++ b/da/hardware/supported/mipsel.xml @@ -0,0 +1,146 @@ + + + + + CPU, Main Boards, and Video Support + + +Debian on &arch-title; currently supports three subarchitectures: + + + + +DECstation: various models of the DECstation are supported. + + + + +Cobalt Microserver: only MIPS based Cobalt machines are covered here. +This included the Cobalt Qube, RaQ, Qube2 and RaQ2, and the Gateway +Microserver. + + + + +Broadcom BCM1250 (SWARM): this is an ATX form factor evaluation board from +Broadcom based on their SiByte processor family. + + + + +Complete information regarding supported mips/mipsel machines can be found +at the Linux-MIPS homepage. In the +following, only the systems supported by the Debian installer will be +covered. If you are looking for support for other subarchitectures, please +contact the +debian-&architecture; mailing list. + + + + CPU/Machine types + + + +Currently only DECstations with R3000 and R4000/R4400 CPUs are +supported by the Debian installation system on little endian MIPS. +The Debian installation system works on the following machines: + + + + + + + + System TypeCPUCode-name + Debian subarchitecture + + + + + + DECstation 5000/1xx + R3000 + 3MIN + r3k-kn02 + + DECstation 5000/150 + R4000 + 3MIN + r4k-kn04 + + DECstation 5000/200 + R3000 + 3MAX + r3k-kn02 + + DECstation 5000/240 + R3000 + 3MAX+ + r3k-kn02 + + DECstation 5000/260 + R4400 + 3MAX+ + r4k-kn04 + + Personal DECstation 5000/xx + R3000 + Maxine + r3k-kn02 + + Personal DECstation 5000/50 + R4000 + Maxine + r4k-kn04 + + + + + +All Cobalt machines are supported which have a serial console (which is +needed for the installation). + + + +The Broadcom BCM1250 evaluation board comes with an SB1250 chip with two +cores which are supported in SMP mode by this installer. + + + + + Supported console options + + +Serial console is available on all supported DECstations (9600 bps, +8N1). For using serial console, you have to boot the installer image +with the "console=ttySx" kernel parameter (with "x" being the number +of the serial port you have your terminal connected to - usually "2", +but "0" for the Personal DECstations). On 3MIN and 3MAX+ (DECstation +5000/1xx, 5000/240 and 5000/260) local console is available with the +PMAG-BA and the PMAGB-B graphics options. + + + +If you have a Linux system to use as serial terminal, an easy way +is to run cu (part of the uucp package) on it. +Example: + + + +cu -l /dev/ttyS1 -s 9600 + + + + + +where the option "-l" (line) sets the serial port to use and "-s" (speed) +sets the speed for the connection (9600 bits per second). + + + +Both Cobalt and Broadcom BCM1250 use 115200 bps. + + + + + diff --git a/da/hardware/supported/powerpc.xml b/da/hardware/supported/powerpc.xml new file mode 100644 index 000000000..7373a693d --- /dev/null +++ b/da/hardware/supported/powerpc.xml @@ -0,0 +1,248 @@ + + + + + CPU, Main Boards, and Video Support + + +There are four major supported &architecture; +flavors: PMac (Power-Macintosh) PReP, Apus, and CHRP machines. Ports +to other &architecture; architectures, such as +the Be-Box and MBX architecture, are underway but not yet supported by +Debian. We may have a 64bit port (Power3) in the future. + + + +Apple (and briefly a few other manufacturers - Power Computing, for +example) makes a series of Macintosh computers based on the PowerPC +processor. For purposes of architecture support, they are categorized +as NuBus, OldWorld PCI, and NewWorld. + + + +Macintosh computers using the 680x0 series of processors are not in +the PowerPC family but are instead m68k machines. Those models start +with `Mac II' or have a 3-digit model number such as Centris 650 +or Quadra 950. Apple's pre-iMac PowerPC model numbers have four digits. + + + +NuBus systems are not currently supported by debian/powerpc. The +monolithic Linux/PPC kernel architecture does not have support for +these machines; instead, one must use the MkLinux Mach microkernel, +which Debian does not yet support. These include the following: + + + + +Power Macintosh 6100, 7100, 8100 + + + + +Performa 5200, 6200, 6300 + + + + +Powerbook 1400, 2300, and 5300 + + + + +Workgroup Server 6150, 8150, 9150 + + + + +A linux kernel for these machines and limited support is available at + + + + +OldWorld systems are most Power Macintoshes with a floppy drive and a +PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are +OldWorld machines. The beige colored G3 systems are also OldWorld. + + + +The so called NewWorld PowerMacs are any PowerMacs in translucent +colored plastic cases. That includes all iMacs, iBooks, G4 systems, +blue colored G3 systems, and most PowerBooks manufactured in and after +1999. The NewWorld PowerMacs are also known for using the `ROM in RAM' +system for MacOS, and were manufactured from mid-1998 onwards. + + + +Recently introduced Macintosh systems have hardware which is more well +supported by the 2.4 Linux kernel. For some, the 2.2 kernel just +doesn't work. The new-powermac flavor, which uses the 2.4 kernel, has +been added to keep up with the hardware. The new-powermac flavor may +also be installed on other OldWorld and NewWorld machines. Machines +for which new-powermac is highly recommended are flagged with an +asterisk below. + + + +Specifications for Apple hardware are available at +AppleSpec, +and, for older hardware, +AppleSpec Legacy. + + + + + + + + + + + Model Name/Number + Architecture + + + + + + Apple + iMac Bondi Blue, 5 Flavors, Slot Loading + powermac-NewWorld + + iMac Summer 2000, Early 2001 + powermac-NewWorld + + * iBook, iBook SE, iBook Dual USB + powermac-NewWorld + + * iBook2 + powermac-NewWorld + + Power Macintosh Blue and White (B&W) G3 + powermac-NewWorld + + * Power Macintosh G4 PCI, AGP, Cube + powermac-NewWorld + + * Power Macintosh G4 Gigabit Ethernet + powermac-NewWorld + + * Power Macintosh G4 Digital Audio, Quicksilver + powermac-NewWorld + + PowerBook G3 FireWire Pismo (2000) + powermac-NewWorld + + PowerBook G3 Lombard (1999) + powermac-NewWorld + + * PowerBook G4 Titanium + powermac-NewWorld + + Performa 4400, 54xx, 5500 + powermac-OldWorld + + Performa 6360, 6400, 6500 + powermac-OldWorld + + Power Macintosh 4400, 5400 + powermac-OldWorld + + Power Macintosh 7200, 7300, 7500, 7600 + powermac-OldWorld + + Power Macintosh 8200, 8500, 8600 + powermac-OldWorld + + Power Macintosh 9500, 9600 + powermac-OldWorld + + Power Macintosh (Beige) G3 Minitower + powermac-OldWorld + + Power Macintosh (Beige) Desktop, All-in-One + powermac-OldWorld + + PowerBook 2400, 3400, 3500 + powermac-OldWorld + + PowerBook G3 Wallstreet (1998) + powermac-OldWorld + + Twentieth Anniversary Macintosh + powermac-OldWorld + + Workgroup Server 7250, 7350, 8550, 9650, G3 + powermac-OldWorld + + + + Power Computing + PowerBase, PowerTower / Pro, PowerWave + powermac-OldWorld + + PowerCenter / Pro, PowerCurve + powermac-OldWorld + + + + UMAX + C500, C600, J700, S900 + powermac-OldWorld + + + + APS + APS Tech M*Power 604e/2000 + powermac-OldWorld + + + + Motorola + Starmax 3000, 4000, 5000, 5500 + powermac-OldWorld + + Firepower, PowerStack Series E, PowerStack II + prep + + MPC 7xx, 8xx + prep + + MTX, MTX+ + prep + + MVME2300(SC)/24xx/26xx/27xx/36xx/46xx + prep + + MCP(N)750 + prep + + + + IBM RS/6000 + 40P, 43P + prep + + Power 830/850/860 (6070, 6050) + prep + + 6030, 7025, 7043 + prep + + p640 + prep + + B50, 43P-150, 44P + chrp + + + + Amiga Power-UP Systems (APUS) + A1200, A3000, A4000 + apus + + + + + + diff --git a/da/hardware/supported/s390.xml b/da/hardware/supported/s390.xml new file mode 100644 index 000000000..3de7074d1 --- /dev/null +++ b/da/hardware/supported/s390.xml @@ -0,0 +1,21 @@ + + + + + S/390 and zSeries machine types + + +Complete information regarding supported S/390 and zSeries machines can +be found in IBM's Redbook + +Linux for IBM eServer zSeries and S/390: Distributions in +chapter 2.1 or at the +technical details web page at +developerWorks. +In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; +Multiprise 2000, G3 and G4 machines are supported with IEEE floating +point emulation and thus degraded performance. + + + + diff --git a/da/hardware/supported/sparc.xml b/da/hardware/supported/sparc.xml new file mode 100644 index 000000000..4ee2352eb --- /dev/null +++ b/da/hardware/supported/sparc.xml @@ -0,0 +1,82 @@ + + + + + CPU, Main Boards, and Video Support + + +Currently the &architecture; port supports +several types of Sparc systems. The most common identifiers for Sparc +systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not +support very old sun4 hardware. However, the other systems are +supported. Sun4d has been tested the least of these, so expect +possible problems with regard to the kernel stability. Sun4c and +Sun4m, the most common of the older Sparc hardware, includes such +systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5, +10, and 20, respectively. The UltraSPARC class systems fall under the +sun4u identifier, and are supported using the sun4u set of install +images. Some systems that fall under these supported identifiers are +known to not be supported. Known unsupported systems are the AP1000 +multicomputer and the Tadpole Sparcbook 1. See the +Linux for SPARCProcessors FAQ +for complete information. + + + + Memory Configuration + + +Some older Sun workstations, notably the Sun IPX and Sun IPC have +memory banks located at fixed locations in physical memory. Thus if +the banks are not filled gaps will exist in the physical memory space. +The Linux installation requires a contiguous memory block into which +to load the kernel and the initial RAMdisk. If this is not available a +`Data Access Exception' will result. + + + +Thus you must configure the memory so that the lowest memory block is +contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks +are mapped in at 16Mb boundaries. In effect this means that you must have +a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. +In this case 4Mb is not sufficient. + + + +Example: +In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four +SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS +connectors]. You must therefore install the 16Mb SIMM in bank 0; it is +then recommended to install the 4Mb SIMM in bank 2. + + + + + Graphics Configuration + + +Especially in the case of older Sun workstations, it is very common +for there to be an onboard framebuffer which has been superseded (for +example the bwtwo on a sun IPC), and an SBUS card containing a later +probably accelerated buffer is then plugged in to an SBUS slot. +Under Solaris/SunOS this causes no problems because both cards are +initialised. + + + +However with Linux this can cause a problem, in that the boot PROM +monitor may display its output on this additional card; however the +linux kernel boot messages may then be directed to the original on +board framebuffer, leaving no error messages on +the screen, with the machine apparently stuck loading the RAMdisk. + + + +To avoid this problem, connect the monitor (if required) to the video +card in the lowest numbered SBUS slot (on motherboard card counts +as below external slots). Alternatively it is possible to use a serial +console. + + + + -- cgit v1.2.3