News:

RCS Forums now online!

Main Menu
Menu

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.

Show posts Menu

Messages - MauryG5

#1
The problem persists on Debian; on Fedora, the team managed to work around it—even though logs from Chromium's startup still show Zygote-related failures. While the browser functions properly on Fedora, it remains non-functional on Debian. I've sent everything to Tim, providing both the Debian and Fedora logs and pointing out that, on Fedora, they've managed to get it working despite the Zygote issues. Version 156, which I just installed on Fedora, is currently working.
#2
So, can you confirm that the patch has fixed the issue?
#3
Tim sent me a link to a patch he released for testing; I'm posting the link here. I can't try it out myself right now, so please see if any of you can—thanks.

https://salsa.debian.org/chromium-team/chromium/-/commit/bac3c99cfd739269f7b6c73002e04461abdb4638
#4
I've just submitted the report to the Debian bug section; unfortunately, I don't have Tim's email address, so I can't CC him, but I imagine he'll see the report right away. In any case, the Raptor moderators are here, and I assume they've already read it and passed the information along.

Fortunately, Tim saw my message in the Debian bug report anyway and promptly replied, asking for specific details about the bug, which I sent him right away. Now we are waiting for him to fix the issue; he has everything he needs.
#5
TLE, you confirm too that it doesn't launch anymore. The problem affects all distributions, not just Fedora. If you try launching it from the terminal using the parameters I listed above, it works. The issue lies entirely in the startup process: it freezes when trying to read those two parameters, so a fix needs to be implemented upstream by Raptor...
#6
Operating Systems and Porting / Re: [NEWS] Linux 7.2
September 26, 2026, 10:57:04 AM
And yet, it works for me on all three distros I currently have installed. This is version 7.2.2 on Ubuntu; I have the same 7.2.2 on Debian—both compiled by me. On Fedora, I'm currently running version 7.2.7, which I installed recently.
#7
Hi everyone,

Just wanted to report an issue with Chromium on ppc64le running on my Raptor Blackbird (POWER9) under Debian / Ubuntu.

It seems a recent build/update broke startup compatibility, causing issues unless specific launch flags are passed.

Workaround / Temporary Fix:
Launching Chromium from the terminal with the following parameters bypasses the issue and allows the browser to run stable again:

chromium-browser --no-zygote --no-sandbox

System Details:

Host: Raptor Blackbird (IBM POWER9)

OS: Debian / Ubuntu / Fedora(ppc64le)

GPU: AMD Radeon RX 5700 XT

Hope this helps anyone else running into the same issue on ppc64le while waiting for an official package update/fix.

#8
User Zone / Re: problems uploading photos
August 16, 2026, 08:35:02 AM
So there was indeed a problem, well then I will soon try to upload a photo reduced in size to make it fit within the limits as usual and see if I can do it this time, I will update the discussion in case there are problems thanks.
#9
User Zone / Re: problems uploading photos
August 13, 2026, 12:30:04 PM
I can tell you that the error always refers to the size of the image, I use the resolution reduction to drastically reduce the file size, and yet nothing is wrong, I've always done it this way and up until now it has always worked, now for some time now I can't do it anymore, I don't understand...
#10
User Zone / problems uploading photos
August 10, 2026, 12:44:06 PM
Guys, I'm having a problem uploading photos. Even though I reduce the file size to less than 1MB, I use files around 500 KB or so. The site keeps telling me they're too big and won't let me upload them, even though I've always used files of that size. I've even tried smaller files than 500 KB, but the result is always the same. Can anyone tell me what's going on? I've tried contacting the site administrator twice, but I've never received a response.
#11
Hi, what currently works in RetroArch is FinalBurnArcade. With that, you can use Mame ROMs, which perform much better than our own Mame due to the usual lack of optimization on Power. I can't tell you what the Alpha version is, I don't know it. I tried installing the Naomi/Dreamcast FlyCast emulator; I mentioned it in another post a while ago with Classic. We managed to compile and install it, but it wouldn't run because of the part of the C++ code related to vector instructions, which are obviously only available for X86 and ARM. We had to tell the code to ignore that part, but unfortunately, I tried to run games like Capcom VS SNK 2, but unfortunately, it wouldn't run. We tried bypassing that part in every way, but it didn't work. The part in VSX/Altivec isn't there and would have to be written from scratch for Power. Yesterday I also started Super Model, a Sega Model 3 emulator, but unfortunately there are several problems there too. In that case, the story is paradoxical considering that the original card ran with PPC and therefore it should have been a walk in the park for Power, but unfortunately the usual parts written on X86 to optimize the code create a big problem for us because we necessarily have to go through those and obviously Power doesn't understand anything and we would need the JIT. Sega Rally 2 started, the audio is perfect but unfortunately there are obvious graphical glitches and it's not good in general.
#12
Good morning everyone, I've been wanting to improve the performance of old arcade games on Power for a while, but as was clear by now, there are some limitations with MAME due to the fact that there is no version optimized for Power, obviously, so as soon as you get to games like Street Fighter 3 from 1998/99, everything starts to slow down, unfortunately. Speaking with Gemini, I discovered that with Retroarch, it was possible to get much better performance because it doesn't work like MAME, which emulates every single cycle of the old CPUs and therefore puts a lot of work on the CPU. Having no optimization, it starts to crash, but it manages the emulation differently and more optimally. At that point, we took the sources and rebuilt Retroarch for Power, and to my great surprise, I installed SF3 and now the game runs great compared to MAME. So in the next few days I'll try other old arcade games that ran poorly on MAME to see how they perform on Retroarch, but I have to say I'm very satisfied with the result achieved.

It wasn't easy to find all the sources directly because GitHub seems to have put usernames and passwords on certain sources. After building the main RetroArch, we also had to rebuild the part that loads the actual arcade emulator because when we went to look for the cores, they said they were unavailable.
#13
After much fumbling with Gemini, which is also trial and error, we finally found the right path. Every new kernel Fedora installs puts a string with $ in the boot file, and petitboot can't read that file, resulting in an initrd error. We removed that string, and apparently the kernel is working properly again. We figured this out because it had me compare the 7.0.10 boot files with those of the rescue build, which actually works. That's when Gemini told me that that string is confusing petitboot.
#14
After a long time, I decided to put Fedora back among my distros to use on Power. I reinstalled it from scratch and I actually noticed the great step forward that Fedora has made on Power, responsive, fluid, made really well now as a desktop. The 7.0.9 kernel was installed when I installed it, a few days ago I installed 7.0.10, in the grub update it tells me in yellow therefore a warning, that it had found the Debian and Ubuntu kernels, normal I say, I also have those currently mounted and it's not the first time I have all 3 of them. The fact is that as soon as I reboot the new Kernel 7.0.10, from petitboot it tells me an initramfs error... I say, but how come I just updated the kernel and it doesn't work anymore? What the hell is going on? I had just decided to put Fedora back and already the problems are starting, is it possible? Now I'm wondering, having given that warning when it found the kernels of the other two, did it mean that it's running out of memory, given the error, in petitboot or is there another problem that prevents me from booting Fedora with both 7.0.9 (which no longer works) and 7.0.10. It only works with the rescue mode at the moment. I tried having it ignore the other kernels, I tried uninstalling and reinstalling the 7.0.10 kernel, I tried reinstalling some parts but nothing works. Any ideas?
#15
Power 12 will happen because Power's chief engineer, William Starke, spoke about it directly. He did an interview not long ago announcing Power 11 and that immediately after that, there will be a move to Power 12, which will also have a new production process. The point is that if it doesn't return to being completely open, unfortunately, we won't have a sequel to Power 9...