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.

Messages - DKnoto

Pages: 1 2 [3] 4 5
On FreeBSD 14.0 ppc64 with clang 14.0.5 has the same thing.

Applications and Porting / Problem with std::numeric_limits<char>::max()
« on: November 03, 2022, 02:37:51 pm »
I'm porting my software to ppc64le and ran into a problem in the std::numeric_limits<char>::max() function. According to
the documentation, this operation should return the value CHAR_MAX which is 127. This is the case on x86_64 with gcc 11.3.1
compiler. Unfortunately on ppc64le the code compiled with gcc 12.2.1 returns the value UCHAR_MAX which is 255.

Test code:
Code: [Select]
printf("std::numeric_limits<char>::max() == %d\n", static_cast<int>(std::numeric_limits<char>::max()));

Clang 14.0.5 and IBM xlc 16.01.0001.0003 return the same value.

Have any of you encountered such a problem on distributions other than Fedora 36?


Operating Systems and Porting / Re: Trying out Chimera Linux
« on: November 03, 2022, 04:03:11 am »
I haven't used KDE in a long time, about 15 years ;-) I installed KDE on Talos II but I wasn't satisfied,
the graphics handling is somehow weird. When resizing the window, rendering runs terribly slow. But
I will try to play with it again. Configuring KDE to a usable state, I want KDE to look like my macOS
on my laptop, is tedious.

Talos II / Unsatisfactory performance of SSD drives
« on: November 01, 2022, 08:57:16 am »
I switched to the Talos II machine from a Dell Precision 7730 laptop. In the laptop I had an older-generation Samsung SSD,
a 970 Pro, connected via an M.2 connector to PCI 3.0. In the Talos II I used a 980 Pro connected to PCI 4.0 via an ICY BOX
PCIe 4.0 x4 - M.2 PCIe NVMe controller (up to 64 Gbit/s). I expected a read transfer of 5-6 GB/s and got 0.9 GB/s.
That's more than three times slower than on a laptop. Screenshots attached.

Is there any way to improve this?

Operating Systems and Porting / Re: Trying out Chimera Linux
« on: November 01, 2022, 05:12:06 am »
I tested this distribution some time ago on my Talos II. From my perspective, the most discouraging part is Gnome.
I've been using this DE for more than a decade and with each release it gets worse and worse. Features that I care
about and that were good are disappearing. The stability of add-ons that bring back old functionality is unsatisfactory.
Before they work properly, the version of Gnome changes and the adjustment process starts from the beginning.
This takes more and more work and is frustrating. Add-ons such as DING Gtk4, for example, do not work properly
with an add-on such as Dash-to-Dock. GJS crashes every now and then, normal work becomes an ordeal.

I'm more comfortable with the concept as presented by ravynOS, I'm rooting for this project,
unfortunately at this moment there is no version for ppc64/ppc64le.

Some time ago I compiled a version downloaded from
The PPC target compiles without problems but it's a 32 bit version and is nightmarishly slow.
For OGR28 it is about 10 times slower than the one for x86 on Intel i9-8950HK.

If you can then test the operation of XFS. I mean such a case when root directory is on XFS partition and during normal system operation we will turn off the power by pulling the cable. Won't Petitboot hang on startup when reading this partition.  Version 5.12.17+ leaves the XFS partition in such a state that Petitboot is unable to read it properly, the kernel module crashes.

Talos II / Re: Petitboot lock after Fedora 36 update
« on: October 13, 2022, 10:00:15 am »
I've had two more XFS falls in the past two weeks. Once after another kernel update and the other after an unexpected power outage. This is definitely too much, fixing this situation is tedious and time-consuming, I have to remove the drive from Talos II and put it in another computer. Petitboot is unable to skip the stage of reading the state of the file systems on the SSD and inserting a rescue system on the USB does nothing.

With the current state of Petitboot software, it is impractical to install the main file system on XFS.

Talos II / Re: Temperatures and rotational speed of fans
« on: October 08, 2022, 05:23:40 am »
At the moment I have 5 140 mm NOCTUA NF-A14 PWM fans. Three do the blowing
from the front, and 2 do the exhaust behind and above the CPU. The 2 fans from the
front I have connected to one slot.

"Pcie temperature" may be related to SSD temperature:

Code: [Select]
# smartctl -a /dev/nvme0 | grep Temp
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius
Temperature:                        45 Celsius
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               45 Celsius
Temperature Sensor 2:               51 Celsius

Talos II / Temperatures and rotational speed of fans
« on: September 28, 2022, 07:55:05 am »
I have a bit of a weird situation with the temperature and speed of the fans in my Talos II:

Should the control system not increase the speed to lower the temperature on this one sensor?

Talos II / Re: Petitboot lock after Fedora 36 update
« on: September 27, 2022, 11:19:47 am »
Problem solved. I took out the SSD drive, checked the XFS partitions on my laptop. Nothing wasn't happening, there weren't any mistakes. I put it in Talos and it works.
Magic ;)

Talos II / Re: Petitboot lock after Fedora 36 update
« on: September 27, 2022, 07:06:11 am »
I am one step further in analyzing the problem. I looked at the /var/log/obmc-console.log log and found something like this:
Code: [Select]

Welcome to Petitboot
Info: Waiting for device discovery

[    6.722018] XFS: Assertion failed: !(fields & XFS_ILOG_DFORK) || (len == in_f->ilf_dsize), file: fs/xfs/xfs_log_recover.c, line: 3103
cpu 0x14: Vector: 700 (Program Check) at [c000000fda48b1c0]
    pc: c0080000011146bc: assfail+0x54/0x60 [xfs]
    lr: c008000001114694: assfail+0x2c/0x60 [xfs]
    sp: c000000fda48b450
   msr: 900000000282b033
  current = 0xc000000fda442100
  paca    = 0xc000000fff726e00   irqmask: 0x03   irq_happened: 0x01
    pid   = 655, comm = pb-discover
kernel BUG at fs/xfs/xfs_message.c:110!
Linux version 5.5.0-openpower1 (root@raptor-build-public-staging-01) (gcc version 6.5.0 (Buildroot 2019.05.3-06769-g7bdd570165)) #2 SMP Thu Feb 20 02:19:47 UTC 2020
enter ? for help
[c000000fda48b4b0] c00800000113bf74 xlog_recover_inode_pass2+0xaac/0xac0 [xfs]
[c000000fda48b590] c00800000113d980 xlog_recover_items_pass2+0x68/0xd0 [xfs]
[c000000fda48b5e0] c00800000113dc34 xlog_recover_commit_trans+0x24c/0x2f0 [xfs]
[c000000fda48b680] c00800000113deb0 xlog_recovery_process_trans+0x1d8/0x210 [xfs]
[c000000fda48b6f0] c00800000113e1b8 xlog_recover_process_data+0xc0/0x1a0 [xfs]
[c000000fda48b760] c00800000113e608 xlog_do_recovery_pass+0x1a0/0x740 [xfs]
[c000000fda48b8f0] c00800000113f3e0 xlog_do_log_recovery+0xb8/0x1c0 [xfs]
[c000000fda48b930] c00800000113f518 xlog_do_recover+0x30/0x210 [xfs]
[c000000fda48b9b0] c00800000113f7c0 xlog_recover+0xc8/0x1b0 [xfs]
[c000000fda48ba30] c008000001126754 xfs_log_mount+0x34c/0x3d8 [xfs]
[c000000fda48bac0] c0080000011160a8 xfs_mountfs+0x530/0xa10 [xfs]
[c000000fda48bb70] c00800000111ca30 xfs_fc_fill_super+0x3c8/0x5f0 [xfs]
[c000000fda48bc10] c0000000001f6758 get_tree_bdev+0x248/0x2e0
[c000000fda48bcb0] c00800000111b788 xfs_fc_get_tree+0x20/0x40 [xfs]
[c000000fda48bcd0] c0000000001f5ac8 vfs_get_tree+0x48/0x160
[c000000fda48bd50] c00000000022973c do_mount+0x7fc/0xba0
[c000000fda48bdd0] c00000000022a010 sys_mount+0xc0/0x180
[c000000fda48be20] c00000000000b50c system_call+0x5c/0x68
--- Exception: c01 (System Call) at 00007fff8dfdb6c4
SP (7ffff8318960) is in userspace

Then it's something with an SDD drive and an XFS file system on that drive. I took out the SSD disk and Petitboot came back to life :)

BTW. Does it make sense to replace Petitboot 1.12 with 1.13?

Talos II / Re: Petitboot lock after Fedora 36 update
« on: September 27, 2022, 12:32:36 am »
This is what this upgrade step is called, I don't know exactly what the Fedora installer is upgrading then.

Talos II / Petitboot lock after Fedora 36 update
« on: September 26, 2022, 12:07:45 pm »
Today, after the Fedora 36 update, I had an unpleasant surprise. The first phase of the system update went as usual without any problems.
Then, as recommended, I restarted the machine and the firmware update phase began. After this process was completed, it was rebooted
again and here are the problems:
  • Petitboot did not detect the disk, there is no list of possible kernels to load;
  • USB keyboard stopped working, locked on all USB sockets
  • the "Power" button stopped working, I couldn't turn off the machine
  • At the bottom of the screen, Petitboot wrote the message "Info: Waiting for device discovery"
Any ideas?

Minor fix, after the next restart the "Power" key works.

I made a video of how the boot process works: Petiboot after F36 firmware update

I spoke to Kallisti5 some time ago about PPC, but he was not interested and basically dissuaded me. I am a Haiku user and was very keen on the system. You'll even find me on the authors list, I've thrown in a few minor tweaks to the system. I even tried to compile Haiku on a PPC but the task overwhelmed me, I can't devote that much time to it.

I think helloSystem is dead compared to ravynOS.

Pages: 1 2 [3] 4 5