Ppc64le: Difference between revisions
Rgdoliveira (talk | contribs) No edit summary |
Prabuanand (talk | contribs) (Removed Architectures Category) |
||
(44 intermediate revisions by 9 users not shown) | |||
Line 1: | Line 1: | ||
This page is used to describe the ppc64le port. | {{DISPLAYTITLE:ppc64le}} | ||
This page is used to describe the [https://en.wikipedia.org/wiki/Ppc64 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 [http://openpower.ic.unicamp.br/minicloud/ their] website for more info. | |||
= Hardware = | |||
You can buy [https://en.wikipedia.org/wiki/POWER8 POWER8] or [https://en.wikipedia.org/wiki/POWER9 POWER9] hardware from IBM or from other vendors. For example, the '''Raptor Computing System Blackbird''' workstation 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]{{dead link}} | |||
* IBM Power System S822LC for Big Data [http://www-03.ibm.com/systems/power/hardware/s822lc-big-data/index.html]{{dead link}} | |||
* IBM Power System S822LC for Commercial Computing [http://www-03.ibm.com/systems/power/hardware/s822lc-commercial/index.html]{{dead link}} | |||
* IBM Power System S822LC for High Performance Computing [IBM Power System S822LC for High Performance Computing] | |||
* IBM Power System S812L and S822L [http://www-03.ibm.com/systems/power/hardware/s812l-s822l/index.html]{{dead link}} | |||
* IBM Power System S824L [http://www-03.ibm.com/systems/power/hardware/s824l/index.html]{{dead link}} | |||
* IBM Power System S812 [http://www-03.ibm.com/systems/power/hardware/s812/index.html]{{dead link}} | |||
* IBM Power System S822 [http://www-03.ibm.com/systems/power/hardware/s822/index.html]{{dead link}} | |||
* IBM Power System S814 [http://www-03.ibm.com/systems/power/hardware/s814/index.html]{{dead link}} | |||
* IBM Power System S824 [http://www-03.ibm.com/systems/power/hardware/s824/index.html]{{dead link}} | |||
* IBM Power Enterprise Systems for the cloud [http://www-03.ibm.com/systems/power/hardware/enterprise-cloud/index.html]{{dead link}} | |||
* IBM Power System E850C [http://www-03.ibm.com/systems/power/hardware/e850c/index.html]{{dead link}} | |||
* IBM Power System E850 [http://www-03.ibm.com/systems/power/hardware/e850/index.html]{{dead link}} | |||
* IBM Power System E870 [http://www-03.ibm.com/systems/power/hardware/e870/index.html]{{dead link}} | |||
* IBM Power System E880 [http://www-03.ibm.com/systems/power/hardware/e880/index.html]{{dead link}} | |||
''' | '''Raptor Computing System''' also has machines: | ||
* Talos II [https://www.raptorcs.com/content/base/products.html] | |||
* Blackbird [https://www.raptorcs.com/content/base/products.html] | |||
'''Tyan''' also has machines: | |||
* Tyan TN76-BP016 | |||
* Tyan GT75-BP012 | |||
* Tyan TN71-BP012 | |||
'''Open Power''' machines: | |||
* 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] | |||
= Installation = | |||
The Alpine {{AlpineLatest}} ppc64le ISO is available [https://dl-cdn.alpinelinux.org/alpine/latest-stable/releases/ppc64le/alpine-standard-{{AlpineLatest}}-ppc64le.iso here]. | |||
The user login is '''root''' with no password. | |||
== Booting Alpine from CD-ROM using qemu == | |||
To start qemu using the Alpine ISO as CD-ROM, you can use a command similar to: | |||
{{cmd|$ doas qemu-system-ppc64 -device spapr-vlan,netdev{{=}}net0,mac{{=}}4C:45:42:45:79:F7 -netdev bridge,br{{=}}br0,id{{=}}net0 -m 8G -smp 16,sockets{{=}}16,cores{{=}}1,threads{{=}}1 -nodefaults -nographic -serial stdio -cdrom alpine-standard-{{AlpineLatest}}-ppc64le.iso}} | |||
If running on a ppc64le host, you can append {{ic|-enable-kvm}} to the above command. | |||
== Installing Alpine to hard-disk using qemu == | |||
Create a disk to install Alpine on it: | |||
{{cmd|$ qemu-img create alpine_disk.img 16G}} | |||
Start qemu attaching the created disk and using Alpine ISO as CD-ROM. Here is an example of the qemu command: | |||
{{cmd|$ doas 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-standard-{{AlpineLatest}}-ppc64le.iso}} | |||
Run the {{ic|setup-alpine}} script: | |||
{{cmd|setup-alpine}} | |||
After running the {{ic|setup-alpine}} script, select the disk (in this example, '''sda''') when the following configuration appears: | |||
<pre> | |||
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 | |||
</pre> | |||
When asked how you would like to use the disk, select '''sys''', and select '''yes''' when asked whether to erase the disk. | |||
{{note|Internet connection is required to complete the setup. {{issue|11384|The grub-ieee1275 and sfdisk are not included in ISO}.}}}} | |||
The installation will format the disk properly. After this finishes, type {{ic|reboot}}. | |||
== Booting Alpine from CD-ROM using qemu and saving modifications between reboots == | |||
When using Alpine in this mode, you need to use Alpine Local Backup ({{ic|lbu}}) to save your modifications between reboots. This requires some writable medium, usually removable. | |||
Create a disk to save Alpine modifications: | |||
{{cmd|$ qemu-img create alpine_disk.img 8G}} | |||
Start qemu attaching the created disk and using Alpine ISO as CD-ROM. Here is the example of the qemu command: | |||
{{cmd|$ doas 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-standard-{{AlpineLatest}}-ppc64le.iso}} | |||
Format the attached disk and add it to the {{path|/etc/fstab}} file: | |||
{{cmd|$ apk add {{pkg|e2fsprogs|arch=ppc64le}} | |||
$ mkfs.ext4 /dev/sda | |||
$ echo "/dev/sda /media/sda ext4 noauto,rw 0 0" >> /etc/fstab | |||
$ mkdir /media/sda | |||
$ mkdir /media/sda/cache}} | |||
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 {{ic|setup-alpine}} 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: | |||
{{cmd|$ 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 {{ic|lbu commit}} command, as the configurations are already done. | |||
It is important to know that, by default, {{ic|lbu}} only cares about modifications in {{path|/etc}} and its subdirectories, with the exception of {{path|/etc/init.d}}! | |||
= See also = | |||
* [[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. | |||
= Reference = | |||
* ABI - https://openpowerfoundation.org/?resource_lib=64-bit-elf-v2-abi-specification-power-architecture | |||
[[Category:Hardware]] | |||
[[Category:ppc64le]] |
Latest revision as of 15:53, 15 October 2024
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 or POWER9 hardware from IBM or from other vendors. For example, the Raptor Computing System Blackbird workstation 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][Dead Link]
- IBM Power System S822LC for Big Data [2][Dead Link]
- IBM Power System S822LC for Commercial Computing [3][Dead Link]
- IBM Power System S822LC for High Performance Computing [IBM Power System S822LC for High Performance Computing]
- IBM Power System S812L and S822L [4][Dead Link]
- IBM Power System S824L [5][Dead Link]
- IBM Power System S812 [6][Dead Link]
- IBM Power System S822 [7][Dead Link]
- IBM Power System S814 [8][Dead Link]
- IBM Power System S824 [9][Dead Link]
- IBM Power Enterprise Systems for the cloud [10][Dead Link]
- IBM Power System E850C [11][Dead Link]
- IBM Power System E850 [12][Dead Link]
- IBM Power System E870 [13][Dead Link]
- IBM Power System E880 [14][Dead Link]
Raptor Computing System also has machines:
Tyan also has machines:
- Tyan TN76-BP016
- Tyan GT75-BP012
- Tyan TN71-BP012
Open Power machines:
Installation
The Alpine 3.20.3 ppc64le ISO is available here.
The user login is root with no password.
Booting Alpine from CD-ROM using qemu
To start qemu using the Alpine ISO as CD-ROM, you can use a command similar to:
$ doas qemu-system-ppc64 -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-standard-3.20.3-ppc64le.iso
If running on a ppc64le host, you can append -enable-kvm
to the above command.
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 CD-ROM. Here is an example of the qemu command:
$ doas 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-standard-3.20.3-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 CD-ROM 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 CD-ROM. Here is the example of the qemu command:
$ doas 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-standard-3.20.3-ppc64le.iso
Format the attached disk and add it to the /etc/fstab file:
$ apk add e2fsprogs $ mkfs.ext4 /dev/sda $ echo "/dev/sda /media/sda ext4 noauto,rw 0 0" >> /etc/fstab $ mkdir /media/sda $ mkdir /media/sda/cache
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 subdirectories, 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