Ppc64le: Difference between revisions

From Alpine Linux
m (Added links; style, expression changes)
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This page is used to describe the ppc64le port.
This page is used to describe the [https://en.wikipedia.org/wiki/Ppc64 ppc64le] port.


== Testing (for developers) ==
= Testing (for developers) =


The hosting sponsor for the ppc64le port operate a miniCloud service which will provide Alpine ppc64le images for testing.
The hosting sponsor for the '''ppc64le''' port operates a miniCloud service, which provides ppc64le images to Alpine for testing.


View their website at http://openpower.ic.unicamp.br/minicloud/ for more info.
View [http://openpower.ic.unicamp.br/minicloud/ their] website for more info.


== Hardware ==
= Hardware =
You can buy POWER8 hardware from IBM or other vendors, for example the IBM S812LC server is reasonably price competitive to similar x86 servers and fully supported by the ppc64le port.
These are the IBM machines model that would support Alpine Linux:
   
   
You can buy [https://en.wikipedia.org/wiki/POWER8 POWER8] hardware from IBM or from other vendors. For example, the '''IBM S812LC''' server is reasonably priced, competitive when compared to similar x86 servers, and is fully supported by the ppc64le port.
The following are the '''IBM''' machine models that would support Alpine Linux:
* IBM Power System S821LC  [http://www-03.ibm.com/systems/power/hardware/s821lc/index.html]
* IBM Power System S821LC  [http://www-03.ibm.com/systems/power/hardware/s821lc/index.html]
* IBM Power System S822LC for Big Data [http://www-03.ibm.com/systems/power/hardware/s822lc-big-data/index.html]
* IBM Power System S822LC for Big Data [http://www-03.ibm.com/systems/power/hardware/s822lc-big-data/index.html]
Line 29: Line 29:
* IBM Power System E880 [http://www-03.ibm.com/systems/power/hardware/e880/index.html]
* IBM Power System E880 [http://www-03.ibm.com/systems/power/hardware/e880/index.html]


Tyan also has machines:


'''Tyan''' also has machines:
* Tyan TN76-BP016  
* Tyan TN76-BP016  
* Tyan GT75-BP012
* Tyan GT75-BP012
Line 36: Line 36:




Open Power machines:
'''Open Power''' machines:
 
* Rackspace Barreleye [https://www.nextplatform.com/2015/10/19/rackspace-forges-first-barreleye-openpower-servers/]
* Rackspace Barreleye [https://www.nextplatform.com/2015/10/19/rackspace-forges-first-barreleye-openpower-servers/]
* Google Zaius [https://cloudplatform.googleblog.com/2016/10/introducing-Zaius-Google-and-Rackspaces-open-server-running-IBM-POWER9.html]
* Google Zaius [https://cloudplatform.googleblog.com/2016/10/introducing-Zaius-Google-and-Rackspaces-open-server-running-IBM-POWER9.html]


== Installation ==
= Installation =
 
The Alpine 3.7.0 ppc64le ISO is available [http://rsync.alpinelinux.org/alpine/v3.7/releases/ppc64le/alpine-vanilla-3.7.0-ppc64le.iso here].


The Alpine 3.6.2 ppc64le ISO is available at: http://rsync.alpinelinux.org/alpine/v3.6/releases/ppc64le/alpine-vanilla-3.6.2-ppc64le.iso <br>
The user login is '''root''' with no password.
The user login is "root" with no password.
<br><br>


*''' Booting Alpine from CDROM using qemu'''
== Booting Alpine from CDROM using qemu ==


To start qemu using the Alpine ISO as cdrom, you can use a command similar to:<br>
To start qemu using the Alpine ISO as cdrom, you can use a command similar to:
$ sudo qemu-system-ppc64 -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-vanilla-3.6.1.ppc64le.iso  
$ sudo qemu-system-ppc64 -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-vanilla-3.7.0.ppc64le.iso  


<br>
== Installing Alpine to hard-disk using qemu ==
* '''Installing Alpine to hard-disk using qemu'''


Create a disk to install Alpine on it <br>
Create a disk to install Alpine on it:
$ qemu-img create alpine_disk.img 16G
$ qemu-img create alpine_disk.img 16G
<br><br>


Start qemu attaching the created disk and using Alpine ISO as cdrom. An example of a qemu command <br>
Start qemu attaching the created disk and using Alpine ISO as cdrom. Here is an example of the qemu command:
$ sudo qemu-system-ppc64 -hda alpine_disk.img -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-vanilla-3.6.1-ppc64le.iso
$ sudo qemu-system-ppc64 -hda alpine_disk.img -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-vanilla-3.7.0-ppc64le.iso
<br><br>


Run the setup-alpine script <br>
Run the <code>setup-alpine</code> script:
$ setup-alpine
$ setup-alpine
<br><br>


Run "setup-alpine" command and select the disk (in this example 'sda') when the following configuration appears: <br>
After running the <code>setup-alpine</code> script, select the disk (in this example, '''sda''') when the following configuration appears:
Available disks are: <br>
<pre>
sda  (17.2 GB QEMU    QEMU HARDDISK) <br>
Available disks are:
sda  (17.2 GB QEMU    QEMU HARDDISK)
Which disk(s) would you like to use? (or '?' for help or 'none') [none] : sda
Which disk(s) would you like to use? (or '?' for help or 'none') [none] : sda
<br><br>
</pre>


When asked about how you would like to use the disk select 'sys' and select 'yes' when asked about erasing the disk.<br>
When asked how you would like to use the disk, select '''sys''', and select '''yes''' when asked whether to erase the disk.
The installation will format the disk properly and after it finishes type 'reboot'.


<br><br>
The installation will format the disk properly.  After this finishes, type <code>reboot</code>.
* '''Booting Alpine from CDROM using qemu and saving modifications between reboots'''


When using Alpine in this mode, you need to use Alpine Local Backup (lbu) to save your modifications between reboots and that requires some writable medium, usually removable. <br><br>
== Booting Alpine from CDROM using qemu and saving modifications between reboots ==


Create a disk to save Alpine modifications <br>
When using Alpine in this mode, you need to use Alpine Local Backup (<code>lbu</code>) to save your modifications between reboots.  This requires some writable medium, usually removable.
$ qemu-img create alpine_disk.img 8G
<br><br>


Start qemu attaching the created disk and using Alpine ISO as cdrom. An example of a qemu command <br>
Create a disk to save Alpine modifications:
$ sudo qemu-system-ppc64 -hda alpine_disk.img -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-vanilla-3.6.1-ppc64le.iso 
$ qemu-img create alpine_disk.img 8G  
<br><br>


Format the attached disk and add it to /etc/fstab file: <br>
Start qemu attaching the created disk and using Alpine ISO as cdrom. Here is the example of the qemu command:
$ apk add e2fsprogs  <br>
$ sudo qemu-system-ppc64 -hda alpine_disk.img -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-vanilla-3.7.0-ppc64le.iso 
 
Format the attached disk and add it to the {{path|/etc/fstab}} file:
<pre>
$ apk add e2fsprogs   
$ mkfs.ext4 /dev/sda  <br>
$ mkfs.ext4 /dev/sda  <br>
$ echo "/dev/sda        /media/sda      ext4    noauto,rw 0 0" >> /etc/fstab  <br>
$ echo "/dev/sda        /media/sda      ext4    noauto,rw 0 0" >> /etc/fstab  <br>
$ mkdir /media/sda  <br>
$ mkdir /media/sda  <br>
$ mkdir /media/sda/cache <br>
$ mkdir /media/sda/cache <br>
<br>
</pre>
 
Set <code>lbu</code> to write to the attached disk, setting <code>LBU_MEDIA=sda</code> in the {{path|/etc/lbu/lbu.conf}} file.
 
Run the <code>setup-alpine</code> command, and select the following configurations when asked:
* Enter where to store configs: <code>('floppy', 'sda', 'usb' or 'none') [none]: sda </code>
* Enter apk cache directory <code>(or '?' or 'none') [/media/sda/cache]: /media/sda/cache</code>
 
The last step is to commit the changes:
$ lbu commit


Set lbu to write in the attached disk, setting LBU_MEDIA=sda in /etc/lbu/lbu.conf file
After performing these configurations, you can reboot Alpine and the modifications will be saved. The next time a change happens, you just need to run the <code>lbu commit</code> command, as the configurations are already done.
<br><br>


Run "setup-alpine" command and select the following configurations when asked: <br>
It is important to know that, by default, <code>lbu</code> only cares about modifications in {{path|/etc}} and its subfolders, with the exception of {{path|/etc/init.d}}!
- Enter where to store configs ('floppy', 'sda', 'usb' or 'none') [none]: sda <br>
- Enter apk cache directory (or '?' or 'none') [/media/sda/cache]: /media/sda/cache <br>
<br>


Last step is to commit the changes <br>
= See also =
$ lbu commit
* [[Alpine_local_backup|Alpine local backup]] - For more information about how to use <code>lbu</code> and how to include a new folder to backup.
<br><br>


After doing this configurations, you can reboot your alpine and modifications will be saved. The next time a change happens, you just need to run "lbu commit" command, as the configurations are already done.<br>
= Reference =
It is import to know that by default lbu only cares about modifications in /etc and its subfolders, with the exception of /etc/init.d!. For more information about how to use lbu and include new folder to backup: https://wiki.alpinelinux.org/wiki/Alpine_local_backup
* ABI - https://openpowerfoundation.org/?resource_lib=64-bit-elf-v2-abi-specification-power-architecture


== Reference ==
[[Category:Hardware]]
* ABI : https://openpowerfoundation.org/?resource_lib=64-bit-elf-v2-abi-specification-power-architecture

Revision as of 05:58, 7 December 2017

This page is used to describe the ppc64le port.

Testing (for developers)

The hosting sponsor for the ppc64le port operates a miniCloud service, which provides ppc64le images to Alpine for testing.

View their website for more info.

Hardware

You can buy POWER8 hardware from IBM or from other vendors. For example, the IBM S812LC server is reasonably priced, competitive when compared to similar x86 servers, and is fully supported by the ppc64le port.


The following are the IBM machine models that would support Alpine Linux:

  • IBM Power System S821LC [1]
  • IBM Power System S822LC for Big Data [2]
  • IBM Power System S822LC for Commercial Computing [3]
  • IBM Power System S822LC for High Performance Computing [IBM Power System S822LC for High Performance Computing]
  • IBM Power System S812L and S822L [4]
  • IBM Power System S824L [5]
  • IBM Power System S812 [6]
  • IBM Power System S822 [7]
  • IBM Power System S814 [8]
  • IBM Power System S824 [9]
  • IBM Power Enterprise Systems for the cloud [10]
  • IBM Power System E850C [11]
  • IBM Power System E850 [12]
  • IBM Power System E870 [13]
  • IBM Power System E880 [14]


Tyan also has machines:

  • Tyan TN76-BP016
  • Tyan GT75-BP012
  • Tyan TN71-BP012


Open Power machines:

  • Rackspace Barreleye [15]
  • Google Zaius [16]

Installation

The Alpine 3.7.0 ppc64le ISO is available here.

The user login is root with no password.

Booting Alpine from CDROM using qemu

To start qemu using the Alpine ISO as cdrom, you can use a command similar to:

$ sudo qemu-system-ppc64 -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-vanilla-3.7.0.ppc64le.iso 

Installing Alpine to hard-disk using qemu

Create a disk to install Alpine on it:

$ qemu-img create alpine_disk.img 16G

Start qemu attaching the created disk and using Alpine ISO as cdrom. Here is an example of the qemu command:

$ sudo qemu-system-ppc64 -hda alpine_disk.img -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-vanilla-3.7.0-ppc64le.iso

Run the setup-alpine script:

$ setup-alpine

After running the setup-alpine script, select the disk (in this example, sda) when the following configuration appears:

Available disks are:
sda   (17.2 GB QEMU     QEMU HARDDISK)
Which disk(s) would you like to use? (or '?' for help or 'none') [none] : sda

When asked how you would like to use the disk, select sys, and select yes when asked whether to erase the disk.

The installation will format the disk properly. After this finishes, type reboot.

Booting Alpine from CDROM using qemu and saving modifications between reboots

When using Alpine in this mode, you need to use Alpine Local Backup (lbu) to save your modifications between reboots. This requires some writable medium, usually removable.

Create a disk to save Alpine modifications:

$ qemu-img create alpine_disk.img 8G 

Start qemu attaching the created disk and using Alpine ISO as cdrom. Here is the example of the qemu command:

$ sudo qemu-system-ppc64 -hda alpine_disk.img -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-vanilla-3.7.0-ppc64le.iso  

Format the attached disk and add it to the /etc/fstab file:

$ apk add e2fsprogs  
$ mkfs.ext4 /dev/sda  <br>
$ echo "/dev/sda        /media/sda      ext4    noauto,rw 0 0" >> /etc/fstab  <br>
$ mkdir /media/sda  <br>
$ mkdir /media/sda/cache <br>

Set lbu to write to the attached disk, setting LBU_MEDIA=sda in the /etc/lbu/lbu.conf file.

Run the setup-alpine command, and select the following configurations when asked:

  • Enter where to store configs: ('floppy', 'sda', 'usb' or 'none') [none]: sda
  • Enter apk cache directory (or '?' or 'none') [/media/sda/cache]: /media/sda/cache

The last step is to commit the changes:

$ lbu commit 

After performing these configurations, you can reboot Alpine and the modifications will be saved. The next time a change happens, you just need to run the lbu commit command, as the configurations are already done.

It is important to know that, by default, lbu only cares about modifications in /etc and its subfolders, with the exception of /etc/init.d!

See also

  • Alpine local backup - For more information about how to use lbu and how to include a new folder to backup.

Reference

* ABI - https://openpowerfoundation.org/?resource_lib=64-bit-elf-v2-abi-specification-power-architecture