Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - FlyingBlackbird

Pages: 1 [2]
16
I am using the statistical programming language R (which is available for ppc64le as ready-to-use package) a lot for data management and analytics
but the development IDE RStudio Desktop (https://rstudio.com/products/rstudio/download/#download) is still not available.

Could anybody compile RStudio successfully on ppc64le?

BTW: RStudio Server seems to be available (I did not test it so far) but "only" dockerized:

https://github.com/ppc64le/build-scripts/tree/master/rstudio
https://support.rstudio.com/hc/en-us/articles/236077788-Running-RStudio-Server-on-IBM-Power8


17
Did anybody of you manage to use a NVMe SSD together with a SATA HDD (booting Linux from the SSD)?

The combination of
  • Samsung EVO Plus 970 TB NVMe SSD in the PCIe x8 slot
  • Seagate IronWolf Pro 8 TB (ST8000NE0004) SATA III HDD in SATA-2
  • Asus BW-16D1HT Retail BluRay Writer in SATA-1
  • Fedora Server 31 installed on the SSD
caused many drop-outs (= disabled) of the SATA devices (HDD and BluRay) during the boot phase of Linux.

Without an SSD I can always boot successfully Linux from the same HDD

I have also tried another PCIe to M.2 NVMe hardware with the same problems
  • RaidSonic ICY BOX IB-PCI214M2-HSL M.2 to PCIe adapter and
  • Delock M.2 PCI Express x4 card
to exclude an adapter incompatibility issue.

petitboot always recognized SATA devices until booting of Linux causes the SATA devices to be disabled.
After rebooting (without power off) petitboot then also did not show the SATA devices anymore until I power-off and restart.
"Rescan devices" in petitboot does not help...

Fedora Server 31 log with the SATA drop-outs shown in dmesg:

Code: [Select]
[    0.990585] ata3: SATA max UDMA/133 abar m2048@0x600c100000000 port 0x600c100000200 irq 30
[    1.487812] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.507342] ata3.00: ATA-10: ST8000NE0004-1ZF11G, EN01, max UDMA/133
[    1.507345] ata3.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    6.557731] ata3.00: qc timeout (cmd 0xec)
[    6.557737] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[    6.557738] ata3.00: revalidation failed (errno=-5)
[   16.557020] ata3: softreset failed (1st FIS failed)
[   26.557020] ata3: softreset failed (1st FIS failed)
[   61.556654] ata3: softreset failed (1st FIS failed)
[   61.556656] ata3: limiting SATA link speed to 3.0 Gbps
[   66.556654] ata3: softreset failed (1st FIS failed)
[   66.556656] ata3: reset failed, giving up
[   66.556658] ata3.00: disabled

[    0.990587] ata4: SATA max UDMA/133 abar m2048@0x600c100000000 port 0x600c100000280 irq 30
[    1.487797] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.491980] ata4.00: ATAPI: ASUS    BW-16D1HT, 3.10, max UDMA/133
[    1.499775] ata4.00: configured for UDMA/133
[   97.577022] ata4: softreset failed (1st FIS failed)
[  107.577021] ata4: softreset failed (1st FIS failed)
[  142.576654] ata4: softreset failed (1st FIS failed)
[  147.576654] ata4: softreset failed (1st FIS failed)
[  147.576656] ata4: reset failed, giving up
[  147.576658] ata4.00: disabled

18
Blackbird / Documentation of Blackbird LEDs on the board
« on: January 28, 2020, 03:15:44 pm »
I can see four spots on the Blackbird board having LEDs in different colors and blinking/non-blinking.

What do the diverse LEDs on the board signal?

I have looked at the schematics (delivered on the recovery CD) and also read the labels printed on the PCB but I cannot find answers.

My current interpretation is:

  • Top right corner: Standby PSU Act: The orange power status LED on the mainboard will turn green if the system is powering on.
  • Top left corner: Status LEDs BMC (green, blue, orange) labled: Net1, Net2, HDD, UID, Power, Net3 - blue lights mean booting of OpenBMC
  • Bottom left corner: D7000 near AST 2500 (always blinking in green) - LED green PM BMC Reset (PM_BMC_HBLED_R_L)
  • Bottom center: D10103 Reset - always on, green light

19
Two of my 8 Cores of my brand-new IBM Power9 8-core are dead, how can I get more diagnostic information (could be my Blackbird, a defective CPU or maybe a firmware issue)?

And: Is there a way to re-enable the cores?

Initially it worked for a few days with 8 cores, but suddenly two cores disappeared (I did not realize that immediately)...

Ubuntu Server as well as petitboot are only showing 6 working cores (cat /proc/cpuinfo).

Funny thing within the little tragedy: The CPU is still working with 6 cores ;-)

Excerpt from my pb-sos msglog file:

Code: [Select]
[   56.324724294,6] CORE[0]: HW_PROC_ID=0 PROC_CHIP_ID=0 EC=0x23 OK
[   56.324726725,6] CORE[0]: PIR=00000004 OK (4 threads)
[   56.324729109,6]     Cache: I=32 D=32/512/10240/0
[   56.324757258,6] CORE[1]: HW_PROC_ID=1 PROC_CHIP_ID=0 EC=0x23 OK
[   56.324759514,6] CORE[1]: PIR=0000000c OK (4 threads)
[   56.324761974,6]     Cache: I=32 D=32/512/10240/0
[   56.324790184,6] CORE[2]: HW_PROC_ID=2 PROC_CHIP_ID=0 EC=0x23 OK
[   56.324792498,6] CORE[2]: PIR=00000014 OK (4 threads)
[   56.324794826,6]     Cache: I=32 D=32/512/10240/0
[   56.324824587,4] CORE[3]: HW_PROC_ID=3 PROC_CHIP_ID=0 EC=0x23 UNAVAILABLE
[   56.324912952,6] CORE[3]: PIR=0000001c UNUSABLE (4 threads)
[   56.324915586,6]     Cache: I=32 D=32/512/10240/0
[   56.324945482,6] CORE[4]: HW_PROC_ID=4 PROC_CHIP_ID=0 EC=0x23 OK
[   56.324947787,6] CORE[4]: PIR=00000024 OK (4 threads)
[   56.324950086,6]     Cache: I=32 D=32/512/10240/0
[   56.324980722,6] CORE[5]: HW_PROC_ID=5 PROC_CHIP_ID=0 EC=0x23 OK
[   56.324983113,6] CORE[5]: PIR=00000028 OK (4 threads)
[   56.324985419,6]     Cache: I=32 D=32/512/10240/0
[   56.325017618,4] CORE[6]: HW_PROC_ID=6 PROC_CHIP_ID=0 EC=0x23 UNAVAILABLE
[   56.325099991,6] CORE[6]: PIR=00000034 UNUSABLE (4 threads)
[   56.325102540,6]     Cache: I=32 D=32/512/10240/0
[   56.325134927,6] CORE[7]: HW_PROC_ID=7 PROC_CHIP_ID=0 EC=0x23 OK
[   56.325137083,6] CORE[7]: PIR=0000003c OK [boot] (4 threads)
[   56.325139792,6]     Cache: I=32 D=32/512/10240/0
[   56.325175402,6] IPLPARAMS: v0x70 Platform family/type: ibm,p9-openbmc/rcs,blackbird

Code: [Select]
# cat /proc/cpuinfo
processor : 0
cpu : POWER9, altivec supported
clock : 2154.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 1
cpu : POWER9, altivec supported
clock : 2154.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 2
cpu : POWER9, altivec supported
clock : 2154.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 3
cpu : POWER9, altivec supported
clock : 2154.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 4
cpu : POWER9, altivec supported
clock : 2154.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 5
cpu : POWER9, altivec supported
clock : 2154.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 6
cpu : POWER9, altivec supported
clock : 2154.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 7
cpu : POWER9, altivec supported
clock : 2154.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 8
cpu : POWER9, altivec supported
clock : 2220.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 9
cpu : POWER9, altivec supported
clock : 2220.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 10
cpu : POWER9, altivec supported
clock : 2220.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 11
cpu : POWER9, altivec supported
clock : 2220.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 16
cpu : POWER9, altivec supported
clock : 2204.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 17
cpu : POWER9, altivec supported
clock : 2204.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 18
cpu : POWER9, altivec supported
clock : 2204.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 19
cpu : POWER9, altivec supported
clock : 2204.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 20
cpu : POWER9, altivec supported
clock : 2204.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 21
cpu : POWER9, altivec supported
clock : 2204.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 22
cpu : POWER9, altivec supported
clock : 2204.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 23
cpu : POWER9, altivec supported
clock : 2204.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 28
cpu : POWER9, altivec supported
clock : 2303.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 29
cpu : POWER9, altivec supported
clock : 2170.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 30
cpu : POWER9, altivec supported
clock : 2170.000000MHz
revision : 2.3 (pvr 004e 1203)

processor : 31
cpu : POWER9, altivec supported
clock : 2170.000000MHz
revision : 2.3 (pvr 004e 1203)

timebase : 512000000
platform : PowerNV
model : C1P9S01 REV 1.01
machine : PowerNV C1P9S01 REV 1.01
firmware : OPAL
MMU : Radix

20
I have installed Ubuntu Server 19.10 with Gnome and lightdm and use the Xorg config from the wiki to enable full HD resolution (https://wiki.raptorcs.com/wiki/Troubleshooting/GPU#Display_stuck_at_default_low_resolution_with_AST_HDMI_GPU).

According to the brief spec (https://www.aspeedtech.com/products.php?fPath=20&rId=440) the AST2500 also supports 1920x1200@60 Hz but I could not successfully enable this resolution.

How do I have to configure Xorg (or is it an error in the spec?)?

My steps tried so far (using the cvt tool to create a modeline for the Xorg.conf and adding this to the Xorg conf file as described in the above link):

Code: [Select]
# usage: cvt [-v|--verbose] [-r|--reduced] X Y [refresh]
cvt 1920 1200 60
cvt -r 1920 1200 60
cvt 1920 1200 30

I have also added the modeline name to the "modes" line of the display (without success):

Ubuntu is never using this resolution and does also not offer it in the display resolution settings dialog of Gnome.

21
Firmware / Mount USB drive in petitboot to write pb-sos files
« on: January 27, 2020, 12:42:23 pm »
How can I mount a writable USB drive? I have tried many ways (where mount is even showing rw) but the files are not stored on the drive once I plug it into another machine.

It looks like there is an transient overlay file system...

Code: [Select]
# show available devices
ls /var/petitboot/mnt/dev/
# create a mount point
mkdir /mnt/usb
# mount your usb drive
mount /var/petitboot/mnt/dev/sdb /mnt/usb-stick  # is mounted read-only

I have tried various remounts, device paths, options etc. but with no success...

Pages: 1 [2]