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
1
Talos II / Re: Petitboot lock after Fedora 36 update
« on: Today at 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 ;)

2
Talos II / Re: Petitboot lock after Fedora 36 update
« on: Today at 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
14:mon>

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?

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

4
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


5
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.

6

The Haiku community now has little interest in PPC architecture :(

Maybe ravynOS, it's an interesting project.


7
General Discussion / Re: HighPoint SSD7505 RAID tools for ppc?
« on: August 12, 2022, 12:36:22 pm »
I bought a HighPoint SSD 7502 adapter for my Talos II and I am unhappy with it. With only one CPU, it's a misunderstanding. I knew I was going to have RAID problems and was mainly concerned with accessing two SSDs. Unfortunately this adapter takes up a long PCI slot and I can't use it together  with a video card.

8
GPU Compute / Accelerators / Re: AMD GPU at boot
« on: July 30, 2022, 06:53:43 am »
Apache NetBeans 14 works good. I tested it on AlmaLinux 9 nad Fedora 36.

9
Talos II / Re: Indium pads required for 18-core CPU on Talos II Lite?
« on: July 29, 2022, 05:59:05 pm »
I bought my Talos II with Power 9/18c from Vikings and did not get an indium pad either. To the same question I got the answer that thermal paste was enough. I applied it and it works without any problems.

10
I did initial tests of what I care about and it is not so tragic ;)
FDM 2D 512x512

11
I have tried several times to install FreeBSD 14.0-CURRENT powerpc64 BE on my Talos II,
unfortunately without a positive ending. I have tried several versions 220617, 220701, 220708
and each time the system installed without error messages but Petitboot did not see the system.
Yesterday I tried the 220715 version and also did not have success. So I decided to take a closer
look at it and found that the installer incorrectly fills /boot/etc/kboot.conf:

Code: [Select]
default=
='/kernel/kernel kernelname=/boot/kernel/kernel vfs.root.mountfrom=ufs:/dev/nda0p2'

After changing the entry to the following:

Code: [Select]
default=FreeBSD
FreeBSD='/kernel/kernel kernelname=/boot/kernel/kernel vfs.root.mountfrom=ufs:/dev/nda0p2'

I made the changes manually from the Petitbnoot shell. Just keep in mind that Petitboot mounts
read-only /boot by default. You have to unmount it and mount it with write permission. After the fix,
vi is helpful here, you need to unmount the partition and re-mount it read-only. Without this last
step and after direct loading of the system, the changes will not be saved. You have to repeat
them from the system level.

One final note about ZFS, by default FreeBSD on ppc64 does not support this filesystem. This
is due to Petitboot limitations. You have to compile the system yourself. The recipe can be found
here "FreeBSD/powerpc64 (POWER9) with ZFS on /".

Currently my Talos II is compiling the kernel on a single core since yesterday. I did it consciously
to have a benchmark  ;)

12
General OpenPOWER Discussion / Re: Forum signature size.
« on: July 17, 2022, 02:00:20 am »
I will check the link and the image.

Quote
Do you mind if I add your NZXT case shots to the Gallery?

Of course. I have nothing against.

13
General OpenPOWER Discussion / Forum signature size.
« on: July 16, 2022, 05:58:11 am »
Can you change the size of the signature from 300 to 1024 characters? Manipulating the colors of characters quickly exhausts this limit ;-)

14
Additionally, must remember to manually remove old kernels. The update script doesn't work in this regard either and the /boot directory gets clogged up quickly.

15
AlmaLinux 9 has the same problem. After manually updating the configuration of grub, you can see all your Linux kernels in the list  ;D

Pages: [1] 2