Red Hat Linux 6.
ISBN: N/A Red Hat, Inc. 2600 Meridian Parkway Durham NC 27709 US 919-547-0012 1-888-733-4281 919-547-0024 docs@redhat.com 13588 Research Triangle Park NC 27713 © 1999 Red Hat, Inc. Alpha/SPARCInst(EN)-6.1-Print-RHI (01/00) Red Hat is a registered trademark and the Red Hat Shadow Man logo, RPM, the RPM logo, and Glint are trademarks of Red Hat, Inc. Linux is a registered trademark of Linus Torvalds. Motif and UNIX are registered trademarks of The Open Group.
Contents Red Hat Linux 6.1 Preface . ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... . v An Overview of this Manual . . .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... . v How to Provide Feedback .... .. ... ... .. ... .. ... ... .. ... .. ... ... .. ... ... .. ... .. ... ... .. ... . v Chapter 1 1.1 1.2 1.3 1.4 1.5 1.6 Chapter 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.
iv
Section 0.2:How to Provide Feedback Preface The Official Red Hat Linux Installation Guide contains most of the information necessary for the successful installation of Red Hat Linux on Alpha and SPARC systems. However, additional information necessary for Alpha and SPARC installations just wouldn’t fit in the Official Red Hat Linux Installation Guide; that information is available in this document.
vi Preface If you include the manual’s identifier, we’ll know exactly which version of this manual you have. If you have a suggestion, try to be as specific as possible when describing it. If you’ve found an error, please include the section number and some of the surrounding text so we can find it easily. We may not be able to respond to every message sent to us, but you can be sure that we read them all.
Section 1.1:Introduction 7 1 Information Specific to Red Hat Linux/Alpha 1.1 Introduction This chapter describes the differences between Red Hat Linux/Alpha and Red Hat Linux/Intel installations. While it provides a good overview of these differences, you should read the Official Red Hat Linux Installation Guide first. Concentrate on the chapters describing the installation process, because they will refer you to the appropriate parts of this document at the appropriate times.
Chapter 1:Information Specific to Red Hat Linux/Alpha 1.2 Installation Overview Installing Red Hat Linux on an Alpha system is slightly more complex than installing Red Hat Linux/Intel because a variety of Alpha machine architectures exist and many different models are supported. In general, the sequence of steps to a successful installation are: 1. 2. Create kernel and RAM disk diskettes from images available on the Red Hat Linux/Alpha CD. Create a MILO diskette, if necessary. 3.
Section 1.3:Support for Specific Hardware • For a MILO installation, you’ll need a 5 MB DOS-formatted partition to hold the MILO bootloader. For an SRM installation, you’ll need a 5 MB boot partition for the aboot secondary bootloader. • For both MILO and SRM, you’ll need at least one swap partition. Optimally, the size of the swap partition is twice the RAM of your system, up to 2 GB. • For both MILO and SRM, 120 MB is needed for a basic installation (un-select all "extra" items during the install).
Chapter 1:Information Specific to Red Hat Linux/Alpha Please Note The most recent list of hardware supported by Red Hat Linux/Alpha can be found at Red Hat’s website at http://www.redhat.com/hardware. Please check the website for up-to-date hardware compatibility information before you begin the installation. The website is the definitive source for hardware compatibility information. Hardware not explicitly listed is, by definition, not supported.
Section 1.3:Support for Specific Hardware Linux runs on a majority of the different Alpha systems that exist on the market and we are constantly working to increase the level of compatibility for all Alpha machines. If more information is made available to us about installing Red Hat Linux on a certain class of machine, it becomes easier to qualify that machine for support.
Chapter 1:Information Specific to Red Hat Linux/Alpha • Determining whether Red Hat Linux recognizes the hardware • Providing information on what drivers to use, what options to give to the kernel/module/driver, etc.
Section 1.3:Support for Specific Hardware 13 1.3.3 Alpha Systems Table 1–1, Alpha System Information provides a snapshot of Alpha hardware, the support provided by Red Hat for different Alpha hardware, whether each system supports MILO and/or SRM, and the MILO image file needed for your system (if your system supports MILO).
Chapter 1:Information Specific to Red Hat Linux/Alpha Machine Class Model Alias Digital XL-233 Alpha XL XL-266 XL Avanti AS 200 4/* MUSTANG AS 205 4/* Digital Personal Workstation XL Support SRM MILO MILO Level Capable Capable Image X Compatible but unsupported X X X LX3 X X AS 250 4/* M3 X X AS 255 4/* LX3+ X X AS 300 4/* MELMAC X X AS 400 4/* AVANTI X X PWS 433a, 433au MIATA X X PWS 500a, 500au MIATA X X PWS 600a, 600au MIATA X X Tier-3 Tier-2 xl.
Section 1.
Chapter 1:Information Specific to Red Hat Linux/Alpha Machine Class Model Alias Rawhide AS 4000 WRAN- Currently X GLER/DU- incomRANGO patible AS 4100 DODGE X AS 1200 TINCUP X AlphaBook Laptop ALPHABOOK Noname AXPpci33 NONAME EB64+ X Compatible but UDB/Mul- MULTIA unsupported tia X X X X EB64+ EB64+ X X eb64p.img AlphaPC64 CABRIOLET Compatible but unsupported X X cabrio.img X X Compatible but unsupported X X pc164.img X lx164.img X sx164.img X eb164.
Section 1.3:Support for Specific Hardware 17 Machine Class Model Alias EB66+ EB66+ EB66+ Compatible but unsupported X X eb66p.img EB66 EB66 EB66 Compatible but unsupported X X eb66.
Chapter 1:Information Specific to Red Hat Linux/Alpha Machine Class Model Takara (Takara?) TAKARA Unknown Unknown Unknown takara.img Ruffian AlphaPC 164UX Alias RUFFIAN Support SRM MILO MILO Level Capable Capable Image Compatible but unsupported X X ruffian.img 1.3.4 SCSI Adapters Table 1–2, SCSI Adapters provides information about which SCSI adapters are supported by Red Hat for use with a Red Hat Linux/Alpha system.
Section 1.3:Support for Specific Hardware Table 1–2 19 SCSI Adapters Vendor Driver/Module* Cards Supported Adaptec aic7xxx.o (static) 2902 Tier-2 aic7xxx.o (static) 2910 Tier-2 aic7xxx.o (static) 293x Tier-2 aic7xxx.o (static) 294x Tier-2 aic7xxx.o (static) 394x Tier-2 aic7xxx.o (static) 3985 Tier-2 aic7xxx.o (static) aic777x chipset Tier-2 aic7xxx.o (static) aic78xx chipset Tier-2 7810 Currently incompatible aic7xxx.o (static) 274x EISA Tier-3 aic7xxx.
Chapter 1:Information Specific to Red Hat Linux/Alpha Vendor Driver/Module* Cards Supported Red Hat Support Level IOMEGA ppa.o Zip Parallel Port Tier-2 imm.
Section 1.3:Support for Specific Hardware 21 Vendor Driver/Module* Cards Supported Red Hat Support Level Tekram tmscsim.o (static) DC390 Compatible but unsupported tmscsim.o (static) DC390T Compatible but unsupported tmscsim.o (static) DawiControl 2974 Compatible but unsupported mscsim.o (static) PCscsi/PCnet Compatible but unsupported mscsim.
Chapter 1:Information Specific to Red Hat Linux/Alpha Vendor Driver/Module* Cards Supported Red Hat Support Level BusLogic/Mylex BusLogic.o (static) FlashPoint LT (BT-930) Compatible but unsupported BusLogic.o (static) FlashPoint LT (BT-930R) Compatible but unsupported BusLogic.o (static) FlashPoint LT (BT-920) Compatible but unsupported BusLogic.o (static) FlashPoint DL (BT-932) Compatible but unsupported BusLogic.
Section 1.3:Support for Specific Hardware 23 Cards Supported Red Hat Support Level BusLogic.o (static) BT-956C Compatible but unsupported BusLogic.o (static) BT-956CD Compatible but unsupported BusLogic.o (static) BT-747C Compatible but unsupported BusLogic.o (static) BT-757C Compatible but unsupported BusLogic.o (static) BT-757CD Compatible but unsupported BusLogic.o (static) BT-545C Compatible but unsupported BusLogic.o (static) BT-540CF Compatible but unsupported BusLogic.
Chapter 1:Information Specific to Red Hat Linux/Alpha 1.3.5 Network Interface Cards Table 1–3, Network Interface Cards provides information about network interface cards and whether they’re supported by Red Hat for use with a Red Hat Linux/Alpha system. Table 1–3 Network Interface Cards Vendor Driver/Module Cards Supported Red Hat Support Level 3Com 3c509.o 3c509 Tier-2 3c509.o 3c509b (in ISA mode) Tier-2 3c509.o 3c579 Compatible but unsupported 3c59x.o 3c59x Tier-3 3c59x.
Section 1.3:Support for Specific Hardware 25 Vendor Driver/Module Cards Supported Red Hat Support Level Digital/Compaq de4x5.o 2104x Tier-2 de4x5.o 2114x Tier-2 de4x5.o 2124x Tier-2 de4x5.o Compaq DE500 Tier-2 de4x5.o Compaq DE504 Tier-2 tulip.o Generic DECChip Tulip Tier-2 tulip.o dc21x4x Tier-2 tulip.o Digital Tier-2 EtherWORKS PCI depca.o DE100 Tier-3 depca.o DE101 Tier-3 depca.o DE200 Turbo Tier-3 depca.o DE201 Turbo Tier-3 depca.o DE202 Turbo Tier-3 depca.
Chapter 1:Information Specific to Red Hat Linux/Alpha Cards Supported Red Hat Support Level sis900.o SiS 900 PCI Fast Ethernet Adapter Compatible but unsupported Yellowfin yellowfin.o Yellowfin Packet Engine Compatible but unsupported SMC epic100.o SMC83c17x EPIC Compatible but unsupported epic100.o SMC EtherPower II Vendor Driver/Module SiS Compatible but unsupported 1.3.
Section 1.3:Support for Specific Hardware 27 * Red Hat can only support drives which completely adhere to the ATAPI specification. Some DVD-ROMs and all Lite-On CD-ROMs do not adhere 100% to the ATAPI specification, and are therefore not supported. 1.3.7 Video Cards Table 1–5, Video Cards provides information about video cards and whether they’re supported by Red Hat for use with a Red Hat Linux/Alpha system.
Chapter 1:Information Specific to Red Hat Linux/Alpha Vendor X Server Digital/Compaq Cards Supported Red Hat Support Level PowerStorm 3D30 Currently TGA2 2MB unsupported PowerStorm 4D20 Currently TGA2 16MB unsupported XF86_3DLabs ZLXp-L1 Pixelvision Currently unsupported ZLXp-L2 Pixelvision Currently unsupported PowerStorm 4D40T “Bobcat” Ingergraph RealiZm Currently unsupported PowerStorm 4D50T “Puma” Ingergraph RealiZm Currently unsupported PowerStorm 4D60T “Leopard” Ingergraph RealiZm
Section 1.
Chapter 1:Information Specific to Red Hat Linux/Alpha Cards Supported Red Hat Support Level XF86_Mach64 ATI Xpert@Play 98 Tier-3 XF86_Mach64 ATI Xpert 98 Tier-3 XF86_Mach64 ATI Xpert XL Tier-3 XF86_Mach64 ATI Rage IIC Tier-3 XF86_Mach64 ATI Xpert@Play Tier-3 XF86_Mach64 ATI Xpert@Work Tier-3 XF86_Mach64 ATI 3D Xpression+ Tier-3 XF86_Mach64 ATI 3D Xpression Tier-3 XF86_Mach64 ATI Graphics Xpression Tier-3 XF86_Mach64 ATI Graphics Pro Turbo Tier-3 XF86_Mach64 ATI WinTurbo
Section 1.3:Support for Specific Hardware 31 Table 1–6 Sound Cards Vendor Digital Sound MIDI Drivers/Mod- Drivers/Mod- Cards ules ules Supported Red Hat Support Level Creative Labs opl3.o sb.o Sound Blaster Tier-3 opl3sa.o sb.o Sound Blaster Pro Tier-3 opl3sa2.o sb.o Sound Blaster 16/PNP Tier-3 opl3sa2.o/awe_wave.o sb.o Sound Blaster 32/64 AWE Tier-3 opl3.o sb.o ESS688 AudioDrive Tier-3 opl3.o sb.o ESS1688 AudioDrive Tier-3 opl3.o sb.o ESS1868 AudioDrive Tier-3 gus.o gus.
Chapter 1:Information Specific to Red Hat Linux/Alpha • PS/2 Mice • Serial mouse 1.3.10 Modems/FaxModems Most modems are supported, except for WinModems and software modems, since they rely on Windows drivers which are incompatible with Red Hat Linux. For supported modems, not all features are necessarily supported (for example, voice mail features). 1.3.
Section 1.3:Support for Specific Hardware The following printer drivers are available for Red Hat Linux 6.1: • Apple Dot Matrix • Apple Imagewriter, high-resolution • Apple Imagewriter, letter quality • Apple Imagewriter, low-resolution • C.
Chapter 1:Information Specific to Red Hat Linux/Alpha • Epson Stylus Color • HP DesignJet 650C • HP DeskJet 400/500C/520/540C • HP DeskJet 500 • HP DeskJet 550C/560C/6xxC series • HP DeskJet/DeskJet Plus • HP LaserJet 4 - dithered • HP LaserJet 4/5/6 series • HP LaserJet III* with Delta Row Compression • HP LaserJet III* with duplex capability • HP LaserJet IId/IIp/III* with TIFF compression • HP LaserJet Plus • HP LaserJet • HP PaintJet XL300 and DeskJet 1200C • HP PaintJe
Section 1.4:Choosing Diskette Images • Tek 4693d color printer, 4 bit mode • Tek 4693d color printer, 8 bit mode • Tektronics 4695/4696 inkjet plotter • Text-only printer • Xerox XES printers 1.3.14 Scanners Red Hat does not offer support for scanners, cameras, and similar peripherals. Such devices, if compatible, are considered compatible but unsupported. Most SANE-compatible scanners should work with Red Hat Linux. 1.4 Choosing Diskette Images Alpha machines are divided into classes.
Chapter 1:Information Specific to Red Hat Linux/Alpha Please Note Previous versions of Red Hat Linux/Alpha used different boot images. Now, however, all Alpha installations use the same kernel, so only one boot image is needed (images/generic.img). You no longer need to insert the kernel boot disk after an installation to copy over the kernel to the installed system. MILO is still machine specific, however, so you will need to find the appropriate MILO image file for your system.
Section 1.4:Choosing Diskette Images The rawrite command looks like the following (assuming your CD is drive D:): C:\> d: D:\> cd \dosutils D:\> dosutils> rawrite Rawrite first asks you for the filename of a diskette image; enter the directory and name of the image you wish to write.
Chapter 1:Information Specific to Red Hat Linux/Alpha Please Note If you have trouble with MILO, the first thing to try is a newer MILO image. If updated MILO versions are available, they can be found at: ftp://ftp.digital.com/pub/DEC/Linux-Alpha/Kernels/ MILO file names begin with milo-, which is followed by the system type and date. Refer to Section 1.4.1, Writing an Image File to a Diskette for instructions on how to make disks from disk images.
Section 1.5:MILO Installations The ARC and AlphaBIOS consoles are designed to load the Windows NT operating system. Like many other things in the Linux world, they’ve been made to do a job that they were never intended to do. In this case, they’re used to load Linux. When you power-on an ARC/AlphaBIOS console machine, you will see the firmware initialize the hardware, and you will see a boot menu. The initialization process varies greatly by machine.
Chapter 1:Information Specific to Red Hat Linux/Alpha Please refer to Section 1.4.1, Writing an Image File to a Diskette for instructions on writing image files to diskettes. Once you have these disks created, boot your Alpha machine into the ARC boot menu. The first step is to set up a boot menu entry to enable MILO to be loaded from floppy disk. At the boot menu, select the option Supplementary menu. Next, select the command: here, select the command Selections Menu.
Section 1.5:MILO Installations to commit the changes to NVRAM. Once you have saved your boot entry, [Esc] will get you back to the boot menu and you can now attempt to boot MILO. You should have a boot selection that looks something like this: LOADIDENTIFIER=Linux SYSTEMPARTITION=multi(0)disk(0)fdisk(0) OSLOADER=multi(0)disk(0)fdisk(0)\linload.exe OSLOADPARTITION=multi(0)disk(0)fdisk(0)\ OSLOADOPTIONS= This boot selection enables ARC to boot into MILO from the floppy using the linload.exe OS loader. 1.5.
Chapter 1:Information Specific to Red Hat Linux/Alpha to enter setup mode. You are going to add a boot selection that allows you to boot MILO from a floppy disk. Select the following command from the menu: Utilities -> OS Selection Setup.. Press [Insert] to add a new operating system selection. For the Boot Name parameter, enter something like: MILO Floppy to indicate that you are loading MILO from a floppy disk. Press [Tab] to get to the next field.
Section 1.
Chapter 1:Information Specific to Red Hat Linux/Alpha MILO will assume ext2 as the default filesystem, and so you have to explicitly tell MILO if the filesystem is something other than ext2. All of the commands that use filenames allow you to pass the file system using the -t [filesystem] option. So, if you wanted to list the contents of a SCSI CD-ROM, you might type the following: MILO> ls -t iso9660 scd0: Variables MILO contains some settable variables that help the boot process.
Section 1.5:MILO Installations 1.5.4 Booting with MILO The primary function of MILO is to boot the Linux kernel. To boot the installer to use the CD-ROM (assuming the CD-ROM drive is SCSI) the command would look similar to this: MILO> boot fd0:vmlinux.gz root=/dev/scd0 The installer should boot, and you should be able to proceed as normal. IDE CD-ROM devices use the standard IDE device references. If you need to use the RAM disk floppy as well, the boot command accepts the standard kernel parameters.
Chapter 1:Information Specific to Red Hat Linux/Alpha approximately 1 MB to 10 MB (2048 to 20480 sectors), depending on exactly what configuration for aboot you will be using. Its purpose is to provide space at the very beginning of the disk for aboot to write the boot block and object file that allows booting to kernels located within the disk labels. For more information on the process aboot uses to boot, please see the SRM Firmware HOWTO at http://www.alphalinux.org/faq/srm.html. 3.
Section 1.5:MILO Installations The 2 in 2/vmlinux.gz and /dev/sda2 are representative of the second disk label on the disk. The -fi and -fl options stand for ‘file’ and ‘flags,’ respectively. You can also choose a slightly different path that involves an extra prompt: boot dka0 Once you see the aboot> prompt, you can use similar kernel and root specifications to the ones used with the -fi and fl options mentioned above: aboot> 2/vmlinux.
Chapter 1:Information Specific to Red Hat Linux/Alpha This should show the partition you selected to be mounted as / to be currently mounted as /mnt. Temporarily make /mnt the root directory by issuing the command: # chroot /mnt Now, all you need to do is actually install MILO. First, insert your MILO disk into the floppy drive. Then you’ll need to issue a command which will vary slightly in syntax depending on your boot device.
Section 1.6:SRM Installations 49 Disk 0 Partition 1 If you wish to autoboot into Linux, set the OSLOADOPTIONS variable as described in Section 1.5.9, MILO Autoboot. Once you have done this, booting and running Linux on an Alpha system should be very similar to doing so on an x86 system. 1.5.9 MILO Autoboot In the ARC and AlphaBIOS consoles, the contents of the OSLOADOPTIONS parameter are passed to MILO as a command.
Chapter 1:Information Specific to Red Hat Linux/Alpha Device Description dvaXXX Floppy device ewaXXX Ethernet adapter mkaXXX SCSI tape device pkaXXX SCSI host adapter for the first SCSI bus. Further SCSI busses are denoted as pkbXXX... 1.6.1 Pre-Installation Information To make the Red Hat Linux/Alpha installation go smoothly, you’ll need some information before you begin: • The SRM device of the floppy drive. In most cases, the SRM device will be dva0.
Section 1.6:SRM Installations 1.6.2 SRM Variables The SRM console has several variables which store their values in NVRAM, therefore keeping them between reboots. To see the value of SRM console variables, type in the command: >>> show VAR Replace VAR with the name of the SRM console variable. To make listing variables easier, you can append an asterisk (*) at any point at the end of a variable name to show all variables that match the text typed so far.
Chapter 1:Information Specific to Red Hat Linux/Alpha In the above command, VAR is the name of the SRM console variable, and the empty quotes ("") denote a blank value. Some integer values cannot be cleared, but can be set to 0. Also note that some SRM console variables are integer in value, but boolean in nature. Several SRM console variables are worth mentioning: BOOT_FILE The BOOT_FILE variable is equivalent to the -file option of the SRM boot command.
Section 1.6:SRM Installations 53 1.6.4 Booting the Installer Now that you’ve created the kernel disk, you will need to boot into the Red Hat Linux installer. The boot command in the SRM console has a simple format and looks like this: >>> boot -file -flags "" Please Note The entire text of all boot flags must be enclosed in doublequotes. In the SRM console, the first floppy disk device is denoted as dva0.
Chapter 1:Information Specific to Red Hat Linux/Alpha 1.6.5 SRM Disk Partitioning Once you get to the fdisk program, press "b" for BSD-style disk labeling. BSD-style disk labeling is different in certain ways from the standard fdisk partitioning used in ARC/AlphaBIOS installations and on Intel installations: • The partitions are identified by letters (a:, b:, c:...) instead of numbers. • The partition types are different.
Section 1.6:SRM Installations 55 Follow the guidelines in the Official Red Hat Linux Installation Guide and in Section 1.5.5, Disk Partitioning for tips and techniques on how to divide your drive into partitions. 1.6.6 SRM Installation Process Install Red Hat Linux/Alpha as described in the Official Red Hat Linux Installation Guide. 1.6.7 Post-Installation Boot Setup Once the installation has been completed, the machine should be capable of booting directly from the SRM console.
Chapter 1:Information Specific to Red Hat Linux/Alpha 1.6.8 SRM Autoboot The SRM console has the ability to autoboot. It is controlled by the value of the AUTO_ACTION SRM console variable. AUTO_ACTION can be set to ‘halt’ or ‘boot’ to reflect the default power-on function of the Alpha machine when booted into the SRM console.
Section 1.6:SRM Installations 57 installed manually. The secondary loader initializes the hardware and loads the Linux kernel into memory so it can bootstrap the machine. Boot the installer. Switch to the command prompt on the TTY2 console with the following key combination: [Alt]-[F2]. After you’ve switched to the command prompt, verify that your root directory is mounted with the following command: # mount This should show the partition you selected to be mounted as / currently mounted as /mnt.
Chapter 1:Information Specific to Red Hat Linux/Alpha Now try to boot your machine as stated in Section 1.6.7, Post-Installation Boot Setup. 3. Q: Have you checked the Errata page on Red Hat’s website? A: Check Red Hat’s Errata page at http://www.redhat.com/errata for a solution to your problem.
Section 2.1:Supported Hardware 2 Information Specific to Red Hat Linux/SPARC This chapter describes the differences between Red Hat Linux/SPARC and Red Hat Linux/Intel installations. While it provides a good overview of these differences, you will find it easier to read through the Official Red Hat Linux Installation Guide first. The Official Red Hat Linux Installation Guide will refer you to the appropriate parts of this document at the appropriate time.
Chapter 2:Information Specific to Red Hat Linux/SPARC • external SCSI drives • CD-ROM drives (external and internal) • SCSI/Ether SBUS expansion cards • Any original equipment Sun monitor for the frame buffers listed Unsupported Hardware -- The following list contains hardware that is currently unsupported: • VME-based sun4m machines, such as the 4/690 • SPARC 5 Model 170 machines • sun4d (SS1000, SS2000) • sun4 architecture • Eurocard sun4c machines, called the "sun4e" under Solaris2.
Section 2.3:Console Commands 2. Determine whether you have sufficient memory to use a RAM disk-based installation. 3. Determine how you will boot the installation program. 4. Determine what installation method you will use. 5. Determine whether you will install Red Hat Linux/SPARC from a serial terminal. 6. Load and run the Red Hat Linux installation program. The remainder of this chapter looks at each of these steps in more detail. 2.
Chapter 2:Information Specific to Red Hat Linux/SPARC Where xx is used to specify the device type (such as sd for SCSI disks), a is the controller number, b, is the device’s unit number, and c is the partition number. Please refer to The Sun Hardware Reference if you have an older SPARC system and require additional information on its boot command syntax. 2.4 RAM Disk-Based Installation Criteria When the Red Hat Linux/SPARC installation starts, normally a RAM disk is loaded into memory.
Section 2.5:Choosing a Boot Method • Boot From CD-ROM -- The installation program is read directly from the Red Hat Linux/SPARC CD-ROM. • Boot From the Network -- The installation program is read from a TFTP server. 2.5.1 Booting From Diskette If your SPARC system has a diskette drive, you can boot the Red Hat Linux/SPARC installation program from a diskette. (Note that if your machine is an Ultra5 or Ultra10, you can’t boot from diskette and you’ll need to choose another boot method.
Chapter 2:Information Specific to Red Hat Linux/SPARC Then rawrite asks for a diskette drive to write the image to; enter a:. Finally, rawrite asks for confirmation that a formatted diskette is in the drive you’ve selected. After pressing [Enter] to confirm, rawrite copies the image file onto the diskette. If you need to make another diskette, label another diskette, and run rawrite again, specifying the appropriate image file.
Section 2.5:Choosing a Boot Method Please Note There have been reports that some systems with pre-2.0 PROMs cannot boot the Red Hat Linux/SPARC installation program from diskette. Also, PCI-based UltraSPARC machines cannot boot from diskette. If this is the case with your SPARC system, you will need to use another boot method. 2.5.2 Booting From CD-ROM If your SPARC system has a fully Sun-supported CD-ROM drive, you can boot directly from the Red Hat Linux/SPARC CD-ROM.
Chapter 2:Information Specific to Red Hat Linux/SPARC • Your network must be able to give your SPARC system its IP address via a rarp. • You must have a TFTP server that can download the Red Hat Linux/SPARC kernel and installation program to your SPARC system. TFTP Server Setup If you are going to set up a TFTP server on a Red Hat Linux system, simply install the latest tftp package using RPM, and make sure the line in inetd.conf that will run tftp is uncommented.
Section 2.6:Choosing an Installation Method The second part of the symlink name is the SPARC system’s architecture. Only sun4m and sun4c machines need this part. For our example, we’ll use sun4m. The IP address and architecture are separated by a dot, resulting in this symlink name: 0A0002FE.SUN4M The last step is figuring out what this symlink should point to. If you’re using a RAM disk, use one of these files: /images/tftp32.img -- for sun4c and sun4m /images/tftp64.
Chapter 2:Information Specific to Red Hat Linux/SPARC 2.6.1 CD-ROM Installation This is the most straightforward method. It requires a Red Hat Linux/SPARC CD-ROM, and a Sun-supported CD-ROM connected to your SPARC system. 2.6.2 FTP Installation This installation method requires a local area network connection and access to an FTP site with the Red Hat Linux/SPARC CD-ROM (or equivalent files). 2.6.
Section 2.9:Partitioning 69 serial terminal supports color. Note that a computer running kermit and connected to your SPARC system will display in color. At any prompt dialog during a serial installation (any dialog with an Ok button), you can press [Ctrl]-[Z] to start a subshell. To return to the installation program, enter exit at the shell prompt. When the installation is complete, simply boot normally, and Red Hat Linux should appear on your serial terminal.
Chapter 2:Information Specific to Red Hat Linux/SPARC spanning from cylinder 0 to the end of the disk. It shouldn’t be used in any way, but it must exist. You can still create other partitions as you normally would. Note that this partition will already exist on any disk that has been used under SunOS or Solaris. If you are partitioning a new disk, you can use fdisk’s s command to create a standard disk label (which includes the whole-disk partition).
Index Index A Alpha boot diskette, creating .............37 boot images .........................35 cable modems ......................32 CD-ROM devices ..................26 disk space needed ................... 8 diskette images .....................35 homepage ............................ 7 installation overview ............... 8 introduction to installing on ....... 7 ISDN adapters......................32 mice..................................31 MILO diskette, creating...........37 modems ..............
Index BSD style ...........................45 disk partitioning SRM .................................54 disk partitioning, SPARC ............69 disk-based installation for SPARC .68 diskette boot, creating .......................63 network boot, creating ............63 PCMCIA support, creating .......63 diskette boot commands, SPARC...64 diskette images for Alpha............35 diskette, making under a UNIX-like OS.................................64 diskette, making with MS-DOS.....
Index NFS Installation for SPARC ..........................68 P partitioning disks on Alpha..........45 R RAM disk diskette for Alpha, creating ...........................38 RAM disk, criteria for use on SPARC ...........................62 rawrite ..............................36 rawrite, creating installation diskette with ...............................63 S serial terminal installation for SPARC ...........................68 SILO configuration ...................69 SPARC boot method, choosing ...........
Index V variables MILO ................................44 SRM .................................51 W whole disk label .......................
