1
User Zone / Re: Fedora or Suse ppc
« on: August 22, 2024, 03:39:44 pm »
I have the same problem on Fedora 39 on Talos. Restarting doesn't work. You have to turn the machine off and on. I got used to it
![Wink ;)](https://forums.raptorcs.com/Smileys/default/wink.gif)
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.
My Talos II, Fedora 39:Could it be a Talos II Lite?Code: [Select]Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 72
...
Socket(s): 1
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 72
On-line CPU(s) list: 0-71
Model name: POWER9, altivec supported
Model: 2.3 (pvr 004e 1203)
Thread(s) per core: 4
Core(s) per socket: 18
Socket(s): 1
Frequency boost: enabled
CPU(s) scaling MHz: 61%
CPU max MHz: 3800,0000
CPU min MHz: 2166,0000
Caches (sum of all):
L1d: 576 KiB (18 instances)
L1i: 576 KiB (18 instances)
L2: 4,5 MiB (9 instances)
L3: 90 MiB (9 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-71
Vulnerabilities:
Gather data sampling: Not affected
Itlb multihit: Not affected
L1tf: Mitigation; RFI Flush, L1D private per thread
Mds: Not affected
Meltdown: Mitigation; RFI Flush, L1D private per thread
Mmio stale data: Not affected
Reg file data sampling: Not affected
Retbleed: Not affected
Spec rstack overflow: Not affected
Spec store bypass: Mitigation; Kernel entry/exit barrier (eieio)
Spectre v1: Mitigation; __user pointer sanitization, ori31 speculation barrier enabled
Spectre v2: Mitigation; Software count cache flush (hardware accelerated), Software link stack flush
Srbds: Not affected
Tsx async abort: Not affected
# # # # # # # ##### ###### # # #### # #
# # ## # # # # # # # ## # # # # #
# # # # # # ## ##### ##### # # # # ######
# # # # # # ## # # # # # # # # #
# # # ## # # # # # # # ## # # # #
#### # # # # # ##### ###### # # #### # #
Version 5.1.3 Based on the Byte Magazine Unix Benchmark
Multi-CPU version Version 5 revisions by Ian Smith,
Sunnyvale, CA, USA
January 13, 2011 johantheghost at yahoo period com
------------------------------------------------------------------------------
Use directories for:
* File I/O tests (named fs***) = /home/dknoto/Oprogramowanie/Unix-Bench/byte-unixbench-master/UnixBench/tmp
* Results = /home/dknoto/Oprogramowanie/Unix-Bench/byte-unixbench-master/UnixBench/results
------------------------------------------------------------------------------
1 x Dhrystone 2 using register variables 1 2 3 4 5 6 7 8 9 10
1 x Double-Precision Whetstone 1 2 3 4 5 6 7 8 9 10
1 x Execl Throughput 1 2 3
1 x File Copy 1024 bufsize 2000 maxblocks 1 2 3
1 x File Copy 256 bufsize 500 maxblocks 1 2 3
1 x File Copy 4096 bufsize 8000 maxblocks 1 2 3
1 x Pipe Throughput 1 2 3 4 5 6 7 8 9 10
1 x Pipe-based Context Switching 1 2 3 4 5 6 7 8 9 10
1 x Process Creation 1 2 3
1 x System Call Overhead 1 2 3 4 5 6 7 8 9 10
1 x Shell Scripts (1 concurrent) 1 2 3
1 x Shell Scripts (8 concurrent) 1 2 3
72 x Dhrystone 2 using register variables 1 2 3 4 5 6 7 8 9 10
72 x Double-Precision Whetstone 1 2 3 4 5 6 7 8 9 10
72 x Execl Throughput 1 2 3
72 x File Copy 1024 bufsize 2000 maxblocks 1 2 3
72 x File Copy 256 bufsize 500 maxblocks 1 2 3
72 x File Copy 4096 bufsize 8000 maxblocks 1 2 3
72 x Pipe Throughput 1 2 3 4 5 6 7 8 9 10
72 x Pipe-based Context Switching 1 2 3 4 5 6 7 8 9 10
72 x Process Creation 1 2 3
72 x System Call Overhead 1 2 3 4 5 6 7 8 9 10
72 x Shell Scripts (1 concurrent) 1 2 3
72 x Shell Scripts (8 concurrent) 1 2 3
========================================================================
BYTE UNIX Benchmarks (Version 5.1.3)
System: talos2: GNU/Linux
OS: GNU/Linux -- 6.8.11-200.fc39.ppc64le -- #1 SMP Sun May 26 19:56:17 UTC 2024
Machine: ppc64le (unknown)
Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8")
00:13:10 up 14:27, 3 users, load average: 0.17, 0.23, 0.09; runlevel 2024-06-06
------------------------------------------------------------------------
Benchmark Run: czw cze 06 2024 00:13:10 - 00:41:21
72 CPUs in system; running 1 parallel copy of tests
Dhrystone 2 using register variables 43482427.2 lps (10.0 s, 7 samples)
Double-Precision Whetstone 4958.8 MWIPS (10.0 s, 7 samples)
Execl Throughput 3584.1 lps (29.9 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 499495.6 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 128933.5 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 1587747.4 KBps (30.0 s, 2 samples)
Pipe Throughput 789756.5 lps (10.0 s, 7 samples)
Pipe-based Context Switching 54265.4 lps (10.0 s, 7 samples)
Process Creation 4442.8 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 5002.6 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 4411.7 lpm (60.0 s, 2 samples)
System Call Overhead 739118.2 lps (10.0 s, 7 samples)
System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 43482427.2 3726.0
Double-Precision Whetstone 55.0 4958.8 901.6
Execl Throughput 43.0 3584.1 833.5
File Copy 1024 bufsize 2000 maxblocks 3960.0 499495.6 1261.4
File Copy 256 bufsize 500 maxblocks 1655.0 128933.5 779.1
File Copy 4096 bufsize 8000 maxblocks 5800.0 1587747.4 2737.5
Pipe Throughput 12440.0 789756.5 634.9
Pipe-based Context Switching 4000.0 54265.4 135.7
Process Creation 126.0 4442.8 352.6
Shell Scripts (1 concurrent) 42.4 5002.6 1179.8
Shell Scripts (8 concurrent) 6.0 4411.7 7352.8
System Call Overhead 15000.0 739118.2 492.7
========
System Benchmarks Index Score 998.1
------------------------------------------------------------------------
Benchmark Run: czw cze 06 2024 00:41:21 - 01:09:46
72 CPUs in system; running 72 parallel copies of tests
Dhrystone 2 using register variables 577677974.0 lps (10.0 s, 7 samples)
Double-Precision Whetstone 211750.9 MWIPS (9.9 s, 7 samples)
Execl Throughput 32708.5 lps (29.9 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 11708757.2 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 3254020.0 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 22886575.0 KBps (30.0 s, 2 samples)
Pipe Throughput 18331410.8 lps (10.0 s, 7 samples)
Pipe-based Context Switching 2564695.6 lps (10.0 s, 7 samples)
Process Creation 75847.8 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 110553.5 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 14402.6 lpm (60.1 s, 2 samples)
System Call Overhead 23145656.7 lps (10.0 s, 7 samples)
System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 577677974.0 49501.1
Double-Precision Whetstone 55.0 211750.9 38500.2
Execl Throughput 43.0 32708.5 7606.6
File Copy 1024 bufsize 2000 maxblocks 3960.0 11708757.2 29567.6
File Copy 256 bufsize 500 maxblocks 1655.0 3254020.0 19661.8
File Copy 4096 bufsize 8000 maxblocks 5800.0 22886575.0 39459.6
Pipe Throughput 12440.0 18331410.8 14735.9
Pipe-based Context Switching 4000.0 2564695.6 6411.7
Process Creation 126.0 75847.8 6019.7
Shell Scripts (1 concurrent) 42.4 110553.5 26073.9
Shell Scripts (8 concurrent) 6.0 14402.6 24004.3
System Call Overhead 15000.0 23145656.7 15430.4
========
System Benchmarks Index Score 18698.4
[root@talos2 ~]# nvram -v -p ibm,skiboot --print-config
NVRAM size 589824 bytes
NVRAM contains 4 partitions
"ibm,skiboot" Partition
--------------------------
Is fast reboot on or off?
$ sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
In an era where vendors increasingly seek to use proprietary software in the devices around us to exert control over their users, the desire for open source software has expanded to the firmware that allows our machines to function, and platforms which individuals can trust and control have never been more important. However, changes to hardware platforms in recent years such as the Intel ME, vendor-supplied binary blobs and vendor-signed firmware images have repeatedly set back efforts to create open source firmware for the computers we use. The release of Power servers with 99% open source firmware excited many who had been searching for a computer they could trust, but one proprietary firmware blob remained: that of the Ethernet controller. This is the story of how that blob was reverse engineered and replaced with an open source replacement, delivering the first machine with desktop-class performance and 100% open source firmware in many years.
This talk is about how I reverse engineered the final remaining firmware blob on the Talos II/Blackbird POWER9 systems, enabling it to be replaced with an open source replacement, in an intensive reverse engineering effort that spanned several years.
The talk will begin by introducing the open source firmware movement and its practical and ethical motivations, and note the obstacles to delivering fully open source firmware for contemporary x86 and other platforms and explaining the motive behind the project, before moving onto a more technical discussion of the adventure of firmware reverse engineering and the obstacles encountered.
Subjects I intend to cover include: how the original proprietary firmware was reverse engineered from scratch with only limited knowledge of device internals; the long history of Broadcom NIC architecture and its evolution over time; the tools that had to be developed to enable the device probing, testing and reversing process; the story of a horrifying but necessary detour into reversing x86 real mode code and the novel methodology used to aid reversing; how modern NICs allow BMCs in servers to share network ports with the host, and the security hazards this creates; and how fully open source firmware was created legally using a clean room process.
This talk will be accessible to audiences unfamiliar with POWER9 or the open source firmware community, but is also intended to cover some new ground and be of interest to those familiar with the project. The talk will mainly be of interest to those interested in open source firmware and issues such as owner control and the security and auditability issues caused by proprietary firmware, and to those interested in reverse engineering.
Have you considered re-flashing the firmware as MPC7500 suggested?