RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 868030 - Recommend graphical installation on IBM Power Systems servers
Summary: Recommend graphical installation on IBM Power Systems servers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Installation_Guide
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jack Reed
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-18 23:23 UTC by Jack Reed
Modified: 2013-06-17 05:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-26 00:19:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jack Reed 2012-10-18 23:23:41 UTC 
As part of our discussions about improving the Power Systems section of the Installation Guide, Brent Baude from IBM's Linux Technology Center emailed me with a suggestion that the Installation Guide recommend using the graphical installer if installing on a graphical display, because on Power Systems anaconda defaults to the text installer.

So QE can compare what I have written with IBM's suggestions, I'll quote the relevant part of Brent's email here:


"I'll suggest some wording that you guys can refine.

'You should strongly consider using the graphical anaconda to install your system.  It is more feature rich and is the preferred installation method for RHEL.  Because POWER systems primarily use text consoles, anaconda will not automatically start a graphical installation.  You can start a graphical install through anaconda by passing an anaconda boot option of 'vnc'.  For more information, see (https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/sn-remoteaccess-installation.html#sn-remoteaccess-installation-vnc)  .  '

If we consider something like that (and I defer to your collective judgement there), then we might consider a slight change to:

'Finally, select the device containing the installation DVD. Yaboot is loaded from this device and you are presented with a boot: prompt. Press Enter or wait for the timeout to expire for the installation to begin.'

And we can hand edit the picture in 14.1 by showing the vnc parameter being passed.

boot:
* linux                    
boot: linux vnc  
Please wait, loading kernel...
"


I will add an admonition to the start of Chapter 14. Booting the Installer, explaining that the graphical installer is recommended on systems with a graphical display and that the vnc boot option is required.

I will edit the sentence regarding the boot: prompt to mention that the vnc boot option can be passed here.

I will also add a second piece of sample output to section 14.1 to include the output Brent provided, to demonstrate the vnc boot option being passed.

These updates will be available in the 6.4 edition of the Installation Guide.
Comment 3 Jack Reed 2013-02-26 00:19:57 UTC 
This bug has been verified and implemented for 6.4, so I am changing the status to CLOSED CURRENTRELEASE.
Note You need to log in before you can comment on or make changes to this bug.