Re: netboot/install on power architecture

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
I got the solution to PReP boot partition from this maillist about one year before.

You can try this:
Add such a line in your kickstart configuration file:
part None --fstype "PPC PReP Boot" --size 8

This PReP boot partition problem has nothing with the versions of rhelas3.

Good luck!


Rgds,
WangNan

Inactive hide details for Joerg Maier <JMAIER@xxxxxxxxxx>Joerg Maier <JMAIER@xxxxxxxxxx>




          Joerg Maier <JMAIER@xxxxxxxxxx>
          Sent by: kickstart-list-bounces@xxxxxxxxxx

          2004-06-07 14:41
          Please respond to Discussion list about Kickstart



To: Discussion list about Kickstart <kickstart-list@xxxxxxxxxx>
cc:
Subject: Re: netboot/install on power architecture


Thank you very much, that solved the problem.
Now i still have the problem that anaconda does not accept partition
parameters in the ks.cfg. I took them from anaconda-ks.cfg which was
created during a manual installation. the chrp boot partition is missing.
i will try with newer versions of rhelas3.

Newertheless, the hint that of can pass parameters to the netboot-image is
a big help.

Best Regards,
Joerg Maier

JS20 Service Team
IBM Deutschland Entwicklung GmbH - Lab Boeblingen
phone: 49-7031-16-4762 (T/L: 120-4762)
mail: jmaier@xxxxxxxxxx
http://www.de.ibm.com/entwicklung/



Wang Nan Chen <chenwn@xxxxxxxxxx>
Sent by: kickstart-list-bounces@xxxxxxxxxx
02.06.2004 11:54
Please respond to
Discussion list about Kickstart


To
Discussion list about Kickstart <kickstart-list@xxxxxxxxxx>
cc

Subject
Re: netboot/install on power architecture






Are you working with an power arch machine with an open firmware? If so,
at open firmware prompt, you can trigger the noninteractive network
installatin by running such a command:

0>boot /pci@400000000211/pci@2/ethernet@1:
ks=nfs:NFS_SERVER_IP:/PATH_TO_KSCFG/ks.cfg

Here, "/pci@400000000211/pci@2/ethernet@1" is device info of my working
NIC. Please find your own exact string from SMS menu.

After getting boot image by bootp, this client machine will launch that
image. And, "ks=nfs:..." will be passed to that image as kernel parameter.


Rgds,
WangNan

Joerg Maier <JMAIER@xxxxxxxxxx>




Joerg Maier <JMAIER@xxxxxxxxxx>
Sent by: kickstart-list-bounces@xxxxxxxxxx
2004-06-02 17:36
Please respond to Discussion list about Kickstart


To: kickstart-list@xxxxxxxxxx
cc:
Subject: netboot/install on power architecture


He,

i have a question regarding automated installation (without any
interaction) and the location of the kickstart file. Pxeboot is not
supported by architecture reason. dhcp-option filename is used to give
redhat-netboot-image filename to the client.

I did not find any possibility to tell the network-booting client where to

get the ks.cfg file. Is it not possible to use kickstart in this specific
environment? Then i have to write a expect script, maybe python with
module pexpect, but this seems this is hard to maintain through different
version.

Best Regards,
Joerg Maier


JS20 Service Team
IBM Deutschland Entwicklung GmbH - Lab Boeblingen
phone: 49-7031-16-4762 (T/L: 120-4762)
mail: jmaier@xxxxxxxxxx
http://www.de.ibm.com/entwicklung/


_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list



_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list

GIF image


[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux