31
General OpenPOWER Discussion / Re: POWER11 on the horizon?
« on: December 18, 2024, 08:36:50 pm »
I haven't seen nor heard anything myself.
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.
32
Operating Systems and Porting / Re: [NEWS] Fedora 41 is out!
« on: December 07, 2024, 11:58:51 am »
As a contrary point, I've got F41 running fine on both the Blackbird and T2 here, and didn't have even many teething problems with the update. I wonder if a hardware glitch occurred at around the same time - Fedora doesn't do anything with the system firmware that I'm aware of. I agree with atomicdog that the pflash method is more reliable if you're concerned the BMC or PNOR firmware glitched.
33
Applications and Porting / Re: [GAMES] Quake 3 source port with Vulkan renderer (vkQuake3)
« on: December 04, 2024, 10:03:18 am »
I don't think this would work as written for the original PowerPC Q3VM, which was big-endian (little-endian PowerPC wasn't really a thing in those days). There may also be a few 32-64 bit edges, though I would think that would be minor.
34
Applications and Porting / Re: Firefox WebAssembly (WASM) on ppc64le? Jitsi Meet, Zoom, etc not working
« on: December 04, 2024, 10:01:53 am »Well that explains why certain interactive pages have been erroring "WebAssembly not defined" when checking the developer console.
I just chalked it up to my user.js template disabling WASM.
Although it may be possible to use some sort of Wasm interpreter or polyfill, obviously the best solution is to get the actual JIT working, of course. Otherwise, yes, there is no Wasm if there is no JIT.
35
Applications and Porting / Re: Firefox WebAssembly (WASM) on ppc64le? Jitsi Meet, Zoom, etc not working
« on: December 03, 2024, 12:15:44 pm »
It was working for awhile in internal test builds but changes to Firefox have caused it to crash on Wasm startup, deep within the code. I'm continuing to struggle with this and I'm trying to work on a better debugging setup as time permits.
A similar thing happens with Ion (second-stage) compilation, so they are probably related. Right now the JIT works but is limited to Baseline (first-stage) JS compilation and irregexp.
I haven't updated the patches for anything later than 128ESR yet but it's possible it may apply directly to more recent versions.
A similar thing happens with Ion (second-stage) compilation, so they are probably related. Right now the JIT works but is limited to Baseline (first-stage) JS compilation and irregexp.
I haven't updated the patches for anything later than 128ESR yet but it's possible it may apply directly to more recent versions.
36
Talos II / Re: AST disable jumper doesn't disable AST video
« on: November 30, 2024, 02:20:21 pm »
My T2 is nearly exactly the same setup, with the Raptor BTO WX7100. I have the disable jumper on and firmware in BOOTKERNFW. On this machine, the ASPEED video is indeed still active, but it's showing the last stage of Hostboot; my understanding is this is deliberate so you can still monitor boot messages before the GPU is activated. However, after Hostboot completes, Petitboot never shows up on the ASPEED output, only on the WX7100.
Out of curiosity, what does lshw say when you're in the operating system? On this system BMC video is listed as unclaimed (Fedora Linux 41), which is what I would expect.
And for the record,
This seems later than yours.
Out of curiosity, what does lshw say when you're in the operating system? On this system BMC video is listed as unclaimed (Fedora Linux 41), which is what I would expect.
Code: [Select]
*-pci:5
description: PCI bridge
product: POWER9 Host Bridge (PHB4)
vendor: IBM
physical id: 105
bus info: pci@0005:00:00.0
version: 00
slot: UOPWR.A100059-Node0-BMC
width: 32 bits
clock: 33MHz
capabilities: pci normal_decode bus_master cap_list
resources: memory:600c280000000-600c2ffefffff
*-pci
description: PCI bridge
product: AST1150 PCI-to-PCI Bridge
vendor: ASPEED Technology, Inc.
physical id: 0
bus info: pci@0005:01:00.0
version: 04
slot: BMC
width: 32 bits
clock: 33MHz
capabilities: pci normal_decode bus_master cap_list
resources: memory:600c280000000-600c2ffefffff
*-multimedia UNCLAIMED
description: Multimedia video controller
product: ASPEED Graphics Family
vendor: ASPEED Technology, Inc.
physical id: 0
bus info: pci@0005:02:00.0
version: 41
slot: BMC
width: 32 bits
clock: 33MHz
capabilities: cap_list
configuration: latency=0
resources: memory:600c280000000-600c280ffffff memory:600c281000000-600c28101ffff
And for the record,
Code: [Select]
root@tim-bmc:~# i2cget -y 12 0x31 0x00
0x0c
root@tim-bmc:~# i2cget -y 12 0x31 0x07
0x63
This seems later than yours.
37
General Hardware Discussion / Re: KVM cross-endian guest on POWER8 / IBM S822L
« on: November 19, 2024, 09:17:42 pm »
Just curious: not possible to run big on both host and guest? I'm not sure why that's happening to you, but I'm curious to see if it's the mismatch that's the problem, or running big that's the problem.
38
Operating Systems and Porting / Re: [NEWS] Fedora 41 is out!
« on: November 19, 2024, 09:14:23 pm »On my T2 v/AMD graphics, I upgraded to F41 from the terminal in Gnome via the dnf plugin as described on the Fedora website.
After restarting, the screen went blank for more than five minutes, during which time the machine didn't show up on the network. From experience I knew not to restart. I played a game of chicken with myself regarding connecting to the BMC via ethernet, which I won.
Eventually the login manager appeared.
I don't know if this will help anyone else, but it was my experience.
That's typical and expected. You can tail the log by logging in as root on another VTY. I didn't get a chance to update the Blackbird yet, but I plan to do so no later than the Thanksgiving long weekend.
39
Operating Systems and Porting / Re: [NEWS] Fedora 41 is out!
« on: November 17, 2024, 05:08:35 pm »
What exactly appears on screen? If you boot it from the BMC web interface, what appears on the virtual serial port output?
40
Firmware / Re: Idenitfy versions of firmwares
« on: October 21, 2024, 09:44:08 pm »
ITYM /etc/os-release:
Quote
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"
41
Firmware / Re: Idenitfy versions of firmwares
« on: October 20, 2024, 09:01:27 pm »I looked at the system and its storage organization and capacity:Quoteroot@talos:~# df -h
Filesystem Size Used Available Use% Mounted on
dev 175.9M 0 175.9M 0% /dev
tmpfs 209.2M 22.8M 186.4M 11% /run
/dev/mtdblock4 19.5M 19.5M 0 100% /run/initramfs/ro
/dev/mtdblock5 4.0M 3.1M 900.0K 78% /run/initramfs/rw
Is it normal to have /dev/mtdblock4 full at 100%?
Yes:
Quote
root@tim-bmc:~# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
dev 180156 0 180156 0% /dev
tmpfs 214212 80608 133604 38% /run
/dev/mtdblock4 20992 20992 0 100% /run/initramfs/ro
/dev/mtdblock5 4096 400 3696 10% /run/initramfs/rw
cow 4096 400 3696 10% /
tmpfs 214212 8 214204 0% /dev/shm
tmpfs 214212 0 214212 0% /sys/fs/cgroup
tmpfs 214212 0 214212 0% /tmp
tmpfs 214212 60 214152 0% /var/volatile
42
General CPU Discussion / Re: 3U HSF End of Life'd
« on: October 02, 2024, 09:21:48 pm »
Hopefully this is a sign S1 is coming out quickly, presumably with its own cooler.
43
Firmware / Re: Updating PNOR/BMC firmware on talos II Lite
« on: September 30, 2024, 10:30:33 pm »
You probably should be running the most current firmware anyway; there are other improvements. You don't need to update the FPGA, just the PNOR to get Petitboot up to date.
44
Blackbird / Re: Potential Aspeed slow failure?
« on: September 05, 2024, 11:46:52 am »
Glad to hear it self-resolved, at least.
45
Third Party CPU Discussion / Re: Why haven't we seen boards with Power9 / MicroWatt?
« on: August 29, 2024, 09:27:27 pm »
Yeah, I haven't found a RISC-V system remotely in POWER9's class, let alone Power10 or (presumably) S1. So far it's a lot of sizzle and very little steak.
I wouldn't mind a Raptor RISC-V system, but I wouldn't want it to distract from whatever the nextgen OpenPOWER box is. Although I say that as a PowerPC bigot, I think I would get a lot more out of that than any RISC-V system right now.
I wouldn't mind a Raptor RISC-V system, but I wouldn't want it to distract from whatever the nextgen OpenPOWER box is. Although I say that as a PowerPC bigot, I think I would get a lot more out of that than any RISC-V system right now.
