SLES9 bootloader for PPC iSeries
Hi. I'd just like to post notice of a difference between SLES8 and SLES9
autoyast that needs to be configured for iSeries PPC (power4) logical
partitions. For installing SLES8, I can get away with a simple bootloader
section:
<bootloader>
<activate config:type="boolean">false</activate>
<location>/dev/hda1</location>
</bootloader>
The booting is actually controlled by an i5/OS instance running that is
hosting the disk. But without any hardware change, if I try to install
SLES9, the above doesn't work. I get a message within i5/OS stating:
"--0007: IPL source not valid." I used YaST to output a CHRP bootloader
section which works fine after a little tweaking, but it is quite long:
<bootloader>
<activate config:type="boolean">true</activate>
Hi, Yes, SLES8 bootloader for PPC and other architectures was very generic and we had several issues with the different types of hardware and platforms. In SLES9 hardware and platform specific options are available to cover all scenarios. I am not a PPC bootloader expert, but AFAIK you can remove the following sections which will be filled automatically: global, sections, initrd_modules Carl Pecinovsky wrote:
Hi. I'd just like to post notice of a difference between SLES8 and SLES9 autoyast that needs to be configured for iSeries PPC (power4) logical partitions. For installing SLES8, I can get away with a simple bootloader section:
<bootloader> <activate config:type="boolean">false</activate> <location>/dev/hda1</location> </bootloader>
The booting is actually controlled by an i5/OS instance running that is hosting the disk. But without any hardware change, if I try to install SLES9, the above doesn't work. I get a message within i5/OS stating: "--0007: IPL source not valid." I used YaST to output a CHRP bootloader section which works fine after a little tweaking, but it is quite long:
<bootloader> <activate config:type="boolean">true</activate>
chrp <default>linux</default> <global config:type="list"><key>timeout</key> <value config:type="integer">100</value> <key>boot</key> <value>/dev/iseries/vda1</value> <key>activate</key> <value config:type="boolean">true</value> <key>default</key> <value>linux</value> </global><module>ipr</module> <module>iseries_veth</module> /dev/iseries/vda1 ppc <location>boot</location>false /dev/iseries/vda1 <sections config:type="list"> <section config:type="list"><key>image</key> <value>/boot/vmlinux</value> <key>label</key> <value>linux</value> <key>root</key> <value>/dev/iseries/vda3</value> <key>initrd</key> <value>/boot/initrd</value> <key>append</key> <value>selinux=0 elevator=cfq</value> </section> </sections> </bootloader>I wonder if this section can be cut down, or what all the options mean (like
)? Carl Pecinovsky (507) 253-3861, TL: 553-3861, email: csky@us.ibm.com "It is never safe to look into the future with eyes of fear." --E.H Harriman
participants (2)
-
Anas Nashif
-
Carl Pecinovsky