chub
n00b
Joined: 21 Feb 2008
Posts: 23
Location: Cape Town, South Africa
|
 Posted: Mon Nov 23, 2020 3:40 pm Post subject: IBM PowerPC pSeries P770+ (POWER7) ppc64 (Big Endian) |
 |
|
Hi Forum members, it has been a while for me posting on this forum.
I have been given access to an IBM pSeries p770+. I'm using the HMC, to access the console of the LPAR. Created the virtual optical device named "cdrom". if I named it different the manual firmware boot example doesn't work, and I need to change the boot command.
Here is some information available of the LPAR:
| Code: | (chroot) localhost / # lscpu
Architecture: ppc64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Big Endian
CPU(s): 48
On-line CPU(s) list: 0-47
Thread(s) per core: 4
Core(s) per socket: 1
Socket(s): 12
NUMA node(s): 2
Model: 2.1 (pvr 004a 0201)
Model name: POWER7 (architected), altivec supported
Hypervisor vendor: pHyp
Virtualization type: para
L1d cache: 384 KiB
L1i cache: 384 KiB
NUMA node0 CPU(s):
NUMA node10 CPU(s): 0-47
Physical sockets: 16
Physical chips: 1
Physical cores/chip: 4
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Mitigation; RFI Flush
Vulnerability Spec store bypass: Mitigation; Kernel entry/exit barrier (fallback)
Vulnerability Spectre v1: Mitigation; __user pointer sanitization, ori31 speculation barrier enabled
Vulnerability Spectre v2: Mitigation; Indirect branch cache disabled, Software link stack flush
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
|
Issues with install-powerpc-minimal-20201121T103535Z.iso
kernel module ibmvfc
kernel module ibmvscsi
kernel module ibmveth
none of the modules are available, which means, I cannot see any storage attached to the LPAR booting from the Gentoo minimal livecd.
I require these tools to be on the minimal cd to get multipath setup properly, in order for the WWID storage devices to show up under /dev/mapper.
My current work around is to use a much older iso from another distribution CentOS-7 in this particular case to boot in ppc64 Architecture, since ppc64le is not supported on on this model, at least. I could be mistaken and I will gladly try to boot ppc64le if there is a way from Gentoo.
| Code: | (chroot) localhost / # uname -a
Linux localhost.localdomain 3.10.0-1160.el7.ppc64 #1 SMP Wed Sep 30 02:20:51 UTC 2020 ppc64 POWER7 (architected), altivec supported CHRP IBM,9117-MMD GNU/Linux |
Should I rather go with Yaboot Confiuration, or grub2?
| Code: | | https://wiki.gentoo.org/wiki/GRUB_on_Open_Firmware_(PowerPC) |
only seems to mention Apple Products. Yaboot seems to be the recommended bootloader for IBM, but Using yaboot on IBM hardware says I have to undo my root partition and move it to the same disk, which means no lvm for rootfs. Neither does it mention any use of initrd.
On sles11, there is a fat16 partition where yaboot lives.
to configure it, I run /usr/sbin/lilo, which then copies over the kernel + initrd from /boot to this vfat partition where yaboot resides. This works fine, because the initrd sets up the multpathd first, then lvm, followed by finding the rootfs on the lvm.
| Code: | # fdisk -l /dev/mapper/3600507680c8185a370000000000001eb
Disk /dev/mapper/3600507680c8185a370000000000001eb: 107.4 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders, total 209715200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 32768 bytes / 32768 bytes
Disk identifier: 0x66ee0a00
Device Boot Start End Blocks Id System
/dev/mapper/3600507680c8185a370000000000001eb_part1 * 2048 417791 207872 6 FAT16
/dev/mapper/3600507680c8185a370000000000001eb_part2 417792 168048639 83815424 8e Linux LVM
# ls -la
total 27044
drwxr-xr-x 3 root root 16384 Jan 1 1970 .
drwxrwxrwt 70 root root 12288 Nov 23 17:24 ..
-rwxr-xr-x 1 root root 6353707 Nov 17 17:11 initrd.001
drwxr-xr-x 3 root root 4096 Nov 17 17:11 ppc
-rwxr-xr-x 1 root root 20883480 Nov 17 17:11 vmlinux.001
-rwxr-xr-x 1 root root 412163 Nov 17 17:11 yaboot
-rwxr-xr-x 1 root root 355 Nov 17 17:11 yaboot.cnf
|
On sles12/15 there is a PowerPC Prep Partition + ext2 grub partition (/boot) similar scenario as above.
| Code: | # fdisk -l /dev/mapper/36001738c7c805e060000000000f24dea
Disk /dev/mapper/36001738c7c805e060000000000f24dea: 200 GiB, 214748364800 bytes, 419430400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 3CB272A3-A3F1-B042-BFA3-00E34045B469
Device Start End Sectors Size Type
/dev/mapper/36001738c7c805e060000000000f24dea-part1 2048 18431 16384 8M PowerPC PReP boot
/dev/mapper/36001738c7c805e060000000000f24dea-part2 18432 2115583 2097152 1G Linux filesystem
/dev/mapper/36001738c7c805e060000000000f24dea-part3 2115584 419430366 417314783 199G Linux LVM |
I currently have two LUNs associated with the LPAR. 1st LUN the size of 1GiB, meant for PowerPC Prep Partition and /boot. The 2nd LUN with a size of 90GiB, which contains LVM. Where the rootfs logical volumes are placed.
I have installed sys-kernel/dracut-050-r2 to setup the initrd and ensure that ibmvscsi and multipath runs first before lvm2 activates the volume groups. (just like on the sles12/15 installations). Only problem is, they are ppc64le, so I am guessing here that I cannot use their partitions to boot.
This is my current fstab on this new Gentoo ppc64 POWER7 LPAR:
| Code: | (chroot) localhost / # cat /etc/fstab
# /etc/fstab: static file system information.
/dev/disk/by-id/scsi-36e0008410036ab5c5041ac53000000f0-part2 /boot ext2 noauto,noatime 1 2
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0
/dev/mapper/system_vg-root_lv / ext4 rw,relatime,seclabel,data=ordered,noatime 0 1
/dev/mapper/system_vg-swap_lv none swap sw 0 1
none /var/tmp/portage tmpfs size=16G,nr_inodes=1M 0 0
|
Any insight or ideas? |
|
Gentoo on PPC
