From Fedora Project Wiki

mNo edit summary
m (internal link cleaning)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<!-- page was renamed from QA/TestCases/BootMethodsNetworkBootUsingNetbootImg
{{QA/Test_Case
-->
|description=IBM PowerPC products do not have a BIOS as typical intel-based architectures do.  Instead, they offer Open Firmware.  Open Firmware provides an interactive shell where you can configure the boot process.


= QA/TestCases/BootMethodsNetboot =
From [[wikipedia:OpenFirmware]] ..
== Description ==
<pre>
IBM PowerPC products do not have a BIOS as typical intel-based architectures do.
Open Firmware (also, 'OpenBoot') is a hardware-independent firmware (computer
software which loads the operating system), developed by Sun Microsystems, and
used in post-NuBus PowerPC-based Apple Macintosh computers, Sun Microsystems
SPARC based workstations and servers, IBM POWER systems, and PegasosPPC
systems, among others. On those computers, Open Firmware fulfills the same
tasks as BIOS does on PC computers.


=== Excerpt from [[wikipedia:OpenFirmware]] ===
It is accessed by a user by a Forth-based shell interface. Forth is a powerful
high level language. For example, it is possible to program Open Firmware to
solve the Tower of Hanoi problem.[1]  


It was going to be described by IEEE standard IEEE-1275, which was not
reaffirmed by the OFWG and has been officially withdrawn by IEEE.
Unfortunately, this means it is unavailable from the IEEE.
</pre>


'''Open Firmware''' (also, '''OpenBoot''') is a hardware-independent firmware (computer software which loads the operating system), developed by Sun Microsystems, and used in post-NuBus PowerPC-based Apple Macintosh computers, Sun Microsystems SPARC based workstations and servers, IBM POWER systems, and PegasosPPC systems, among others. On those computers, Open Firmware fulfills the same tasks as BIOS does on PC computers.
{{admon/tip|tftp required|This test will require access to a tftp server on the same network as the system under test.  For information on installing and configuring a tftpserver, consult the [http://docs.fedoraproject.org/install-guide/f{{FedoraVersion}}/en-US/html/s1-netboot-tftp.html installation guide].}}
 
|actions=
It is accessed by a user by a Forth-based shell interface. Forth is a powerful high level language. For example, it is possible to program Open Firmware to solve the Tower of Hanoi problem.[1]
# Boot the system under test into Open Firmare. A key sequence may be required to direct the system to boot Open Firmware.
 
# Locate the file {{filename|images/netboot/ppc64.img}} from the installation source.  Copy this file into a directory accessible by your tftpserver.  For example, <pre> cp images/netboot/ppc64.img /var/lib/tftpboot/</pre>
It was going to be described by IEEE standard IEEE-1275, which was not reaffirmed by the OFWG and has been officially withdrawn by IEEE. Unfortunately, this means it is unavailable from the IEEE.
# Direct the system under test to boot this file.  For example, from Open Firmware you may issue a command similar to <pre>boot network:,\ppc64.img</pre>
 
# Proceed through installation as desired
{{Admon/tip | This test will require access to a tftp server on the same network as the system under test.  Place the netboot.img from the tree (RHEL4=images/pseries/netboot.img or RHEL3=images/netboot.img) in a path accessible to the tftp server.}}
|results=
 
== Steps To Reproduce ==
# Boot the system under test into OpenFirmare (several methods available ... will find specific instructions)
# Boot the netboot.img from OpenFirmware by typing: <code>boot network:,\ppc\rhel4u3</code>
 
== Expected Results ==
 
# System should boot and start anaconda loader without error
# System should boot and start anaconda loader without error
# System can transition to stage#2 anaconda
# System can transition to [[Anaconda/Stage|stage2]] anaconda
}}


[[Category:Installer Test Cases|BootMethodsNetboot]]
[[Category:Installer Boot Methods]]

Latest revision as of 15:10, 18 September 2016

Description

IBM PowerPC products do not have a BIOS as typical intel-based architectures do. Instead, they offer Open Firmware. Open Firmware provides an interactive shell where you can configure the boot process.

From wikipedia:OpenFirmware .. 

 Open Firmware (also, 'OpenBoot') is a hardware-independent firmware (computer
 software which loads the operating system), developed by Sun Microsystems, and
 used in post-NuBus PowerPC-based Apple Macintosh computers, Sun Microsystems
 SPARC based workstations and servers, IBM POWER systems, and PegasosPPC
 systems, among others. On those computers, Open Firmware fulfills the same
 tasks as BIOS does on PC computers.

 It is accessed by a user by a Forth-based shell interface. Forth is a powerful
 high level language. For example, it is possible to program Open Firmware to
 solve the Tower of Hanoi problem.[1] 

 It was going to be described by IEEE standard IEEE-1275, which was not
 reaffirmed by the OFWG and has been officially withdrawn by IEEE.
 Unfortunately, this means it is unavailable from the IEEE.
tftp required
This test will require access to a tftp server on the same network as the system under test. For information on installing and configuring a tftpserver, consult the installation guide.


How to test

  1. Boot the system under test into Open Firmare. A key sequence may be required to direct the system to boot Open Firmware.
  2. Locate the file images/netboot/ppc64.img from the installation source. Copy this file into a directory accessible by your tftpserver. For example, 
     cp images/netboot/ppc64.img /var/lib/tftpboot/
  3. Direct the system under test to boot this file. For example, from Open Firmware you may issue a command similar to 
    boot network:,\ppc64.img
  4. Proceed through installation as desired

Expected Results

  1. System should boot and start anaconda loader without error
  2. System can transition to stage2 anaconda
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Installer_Boot_Methods_Netboot_(ppc)&oldid=473247"