From Fedora Project Wiki

m
m (Changed category)
Line 2: Line 2:
 
-->
 
-->
  
= QA/TestCases/BootMethodsNetboot =
+
= Description =
== Description ==
 
 
IBM PowerPC products do not have a BIOS as typical intel-based architectures do.
 
IBM PowerPC products do not have a BIOS as typical intel-based architectures do.
  
=== Excerpt from [[wikipedia:OpenFirmware]] ===
+
== Excerpt 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.
 
'''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.
  
Line 15: Line 12:
 
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.
 
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.
  
{{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.}}
+
{{admon/tip|tftp required|This test will require access to a tftp server on the same network as the system under test.}}
  
== Steps To Reproduce ==
+
= Steps To Reproduce =
 
# Boot the system under test into OpenFirmare (several methods available ... will find specific instructions)
 
# 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>
 
# Boot the netboot.img from OpenFirmware by typing: <code>boot network:,\ppc\rhel4u3</code>
  
== Expected Results ==
+
= 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 stage#2 anaconda
  
[[Category:Installer Test Cases|BootMethodsNetboot]]
+
[[Category:Installer Boot Methods]]

Revision as of 17:15, 16 February 2009


Description

IBM PowerPC products do not have a BIOS as typical intel-based architectures do.

Excerpt 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.

Idea.png
tftp required
This test will require access to a tftp server on the same network as the system under test.

Steps To Reproduce

  1. Boot the system under test into OpenFirmare (several methods available ... will find specific instructions)
  2. Boot the netboot.img from OpenFirmware by typing: boot network:,\ppc\rhel4u3

Expected Results

  1. System should boot and start anaconda loader without error
  2. System can transition to stage#2 anaconda