Recent Posts

91

Operating Systems and Porting / Re: Debian 12 status?

« Last post by MauryG5 on October 27, 2024, 12:57:35 pm »

I tried to compile a 6.11.4 kernel with 4K pages after updating the firmware but it still doesn't work. However, I was unable to update the mesa drivers, it tells me they are up to date but probably another procedure is needed to install them. I then decided to compile a 6.1.114 long-term support kernel and that works fine and I'm using it now while waiting for the problems for the new Kernels to be resolved. I have been able to verify that the problem occurs from version 6.2.X onwards, something has been changed in the Kernel and Debian 12 no longer works. However, the thing that I still don't understand is why Debian 11, which is older, works fine with all Kernels including 6.11.X, while Debian 12 doesn't work... A regression that I don't understand...

92

User Zone / Re: Gentoo installation issue

« Last post by bernie on October 24, 2024, 11:01:53 pm »

Thank you. I had not figured it out. In the meantime, I had taken the config from the dist kernel, changed it to Power9 and 4K page size and have been running with that. I had not disabled VSX myself. However, looking back, I think my error was that I installed the kernel with the instructions in the PPC handbook, not the PPC64 handbook. That included make-ing the pmac32_defconfig target, which I did think suspicious at the time, but went ahead and did anyway, not realising that I was reading the wrong handbook. I'm going to assume for now that that's how VSX became disabled.

Thank you for your help.

93

User Zone / Re: Gentoo installation issue

« Last post by draconx on October 22, 2024, 08:20:58 pm »

Since it's been some time maybe you've figured all this out already, but...

So I compiled a kernel with the options that I thought best, but it won't boot with that kernel. The console output shows:

Code: [Select]

Run /init as init process
init[1]: illegal instruction (4) at 3fff894c8fe0 nip 3fff894c8fe0 lr 3fff894bcbdc code 1 in ld64.so.2[3fff89488000+4e000]
init[1]: code: 7ca32a14 7ca92850 78bfd183 41820084 73ea0001 7c070166 7d2a4b78 38c00010
init[1]: code: 39600020 39800030 381fffff 7fe8fb78 <f0000050> 41820020 2c200000 7c004f98
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
<snip>


The kernel booted just fine and successfully loaded the first userspace application (/init).
This program then crashed when it executed an illegal instruction in ld64.so.2.

The output above shows that the faulting instruction was <f0000050>.  This is a VSX instruction (xxpermdi) which should normally be supported on POWER9, so my guess is that you have booted a kernel with VSX support disabled (CONFIG_VSX=n) but your userspace is compiled to use VSX unconditionally (e.g., built with gcc -mvsx).

94

Firmware / Re: Idenitfy versions of firmwares

« Last post by mparnaudeau on October 22, 2024, 03:27:13 pm »

I am so glad to announce you that the update has been applied successfully! Fans run now at 1800 and 1700 RPM ... so the machine seems so quite!

I was a bit scary and wanted to be sure not making a mistake, so it tool much time but now I can use it without complaints from my wife 

@carlosgonz To be honest, with all these components and various versions (here different versions of BMC but with the same Linux git sha1 ...), I think that's not clear at all. But I applaud Raptor CS for their machines and their work. My Talos 2 is great and I love PowerPC.

@ClassicHasClass Thank you for the feedback

Ah, I was about to forget: the scp transfer worked after I added the option -O, I found that on a forum: "it an issue with OpenSSH client. Since OpenSSH 9.0, the client uses SFTP protocol by default. To use the legacy protocol, the -O option must be specified."

I am impatient to come back to some more productive work with my Talos 2!

95

Blackbird / IPL cycle failure

« Last post by Borley on October 22, 2024, 01:03:08 pm »

I have recently been unable to boot one of my Blackbirds (Rev 1.02). This thread will serve as notes for my troubleshoot.

Problem: The board BMC starts when mains power is available and the bottom left LED (D7000) flashes rapidly for 2-3 seconds before entering into a slower pulse indicating BMC bringup. However, upon starting chassis power, the board immediately restarts back to BMC bringup. System fans just barely begin to turn before it resets like this.

I can log into the BMC without issue and it reports (possibly old) critical failures:

Code: [Select]

HIGH Error: xyz.openbmc.project.Common.Error.InternalFailure Aug 27, 2022 5:24:36 AM
HIGH Error: open_power.Host.Boot.Error.Checkstop Aug 27, 2022 4:41:00 AM
HIGH Error: open_power.Host.Error.MaintenanceProcecure Aug 27, 2022 4:40:47 AM
HIGH Error: open_power.Host.Error.Event Aug 27, 2022 4:40:46 AM

I say possibly because these errors are old and have been in the log since before this boot issue manifested itself.

Troubleshoot:

1) Re-seat all components, cables
Reseated RAM, CPU, fan connectors, power connectors and tested with PCI devices and all rear+front I/O disconnected - issue persists

2) Check power supply
Checked power supply health with a tester - PSU is functioning properly
Attempted bootup with a different PSU (also tested functional) - issue persists

3) Reflash PNOR, BMC
-Pending-

This Blackbird board typically only sees occasional use for testing, with the only recent change being that I'd started leaving mains power (behind a UPS) connected 24/7 when it is between usage. It is upsetting to have boards costing north of a thousand USD just randomly quit on me, though I will try my best to recover it. Any input is welcome.

96

Operating Systems and Porting / Re: Problems with new Kernels on Debian 12

« Last post by MauryG5 on October 22, 2024, 11:53:12 am »

In any case I don't understand one thing Daniel, if Kernel 6.1.X works, why shouldn't the subsequent ones? What changes from 6.2 onwards to give these problems? In fact it seems that it is always a graphics card problem because I noticed that it loads the Kernel regularly and then when it has to do the classic switch from AST to Radeon, the list screen that it executes when it loads comes back and then it freezes at that point... So it really seems that it doesn't switch to the graphics card. I wonder if in fact as you said, if you try to update the mesa drivers and the firmware, as you made me do at the time to start the Radeon on Debian 10, the thing can be resolvable but I also wonder how it is possible that 6.1 works at this point given this problem if it is this, of firmware and mesa drivers... Maybe from 6.2 there are new AMD Radeon drivers that need these updates and therefore it is not on purpose but at this point I wonder, why on Debian 11 it works fine with any new Kernel and Debian 12 which in theory should start already more updated, does not work anymore? Is it possible that the firmware of Debian 12 is older than the one you made me update at the time on 10 and 11? Or that the Mesa drivers are older than those in the same way? All this is very strange...In any case I entered the repositories to update the firmware and then I ran the update and it actually updated some parts of AMD GPU, then I tried to search for a Mesa update but it tells me they are updated but the version it brings me is 22 and I think that instead it should be updated to 24 if I'm not mistaken... Is it possible to update the Mesa drivers to the latest stable version? If so, what commands should be executed?

97

Operating Systems and Porting / Re: Problems with new Kernels on Debian 12

« Last post by MauryG5 on October 22, 2024, 06:36:33 am »

So it's a known issue on 12 as far as I can see damn. Using the default one which is 6.1.32 it works fine but I might try to compile a 6.11.X with 4K pages at this point... at least see if it works like that...

98

Operating Systems and Porting / Re: Problems with new Kernels on Debian 12

« Last post by pocock on October 22, 2024, 02:36:51 am »

Back in July I made a series of posts in this thread about the kernel on Debian 12

I did not find a quick solution so I am running my patched 5.10.0-8-powerpc64le-4k kernel package on Debian 12

The 6.x kernels were giving problems as described in the other thread.  The 5.10.x kernel has been stable for me.

99

Firmware / Re: Idenitfy versions of firmwares

« Last post by ClassicHasClass on October 21, 2024, 09:44:08 pm »

ITYM /etc/os-release:

root@tim-bmc:~# uname -a
Linux tim-bmc 5.0.7-a8a208fa7346ad643e8f6100c49cb7b8468b6d38 #1 Wed Feb 19 11:44:38 UTC 2020 armv6l GNU/Linux
root@tim-bmc:~# cat /etc/os-release
ID="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="2.7.0-dev"
VERSION_ID="2.7.0-dev-571-g67efd9872"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 2.7.0-dev"
BUILD_ID="2.7.0-dev"
OPENBMC_TARGET_MACHINE="talos"

100

Firmware / Re: Idenitfy versions of firmwares

« Last post by carlosgonz on October 21, 2024, 09:03:44 pm »

I have Blackbird Pnor v2.10 from v2.0, however your BMC/PNOR v2.7 looks like  a devel version from where else.
When i first started with my Blackbird i was lost, i didnt know where to start, as PowerPC is different with X86, 2 years later having my Blackbird and investing tons of time in PowerPC knowledge, now my Blackbird works like a Charm and i dont plans to go back to x86.

 Kudos for Raptor! Special Thanks to Raptor Engineering!