Raptor Computing Systems Community Forums (BETA)
Software => Applications and Porting => Topic started by: vddvss on December 14, 2019, 02:13:48 pm
-
I am pleased to announce a DNF repository for PPC64LE Chromium and Ungoogled Chromium builds. The repo should work for RHEL or CentOS, but it is only tested on Fedora. These builds only work for POWER9 little endian.
Thanks to awordnot for much of the work on the patches and dftxbs3e for work on Ungoogled Chromium.
Further details and source, as well as tarballs and RPMs that should work on any RPM-based distro, are available at https://gitlab.com/chromium-ppc64le/chromium-ppc64le (https://gitlab.com/chromium-ppc64le/chromium-ppc64le).
Installation
To enable the repository, run:
sudo dnf config-manager --add-repo=https://gitlab.com/chromium-ppc64le/chromium-ppc64le/raw/master/chromium-ppc64le.repo
Alternatively, you can download the chromium-ppc64le.repo (https://gitlab.com/chromium-ppc64le/chromium-ppc64le/raw/master/chromium-ppc64le.repo) file from the repository and place it in /etc/yum.repos.d.
After adding the repository, run:
Standard Chromium
sudo dnf install chromium-browser-stable
Ungoogled Chromium
sudo dnf install ungoogled-chromium-browser-stable
Important Note for Existing Users of Ungoogled Chromium
In order to allow parallel installation of both versions of Chromium, this repository contains a patch to change the default location of the Ungoogled Chromium profile from ~/.config/chromium to ~/.config/ungoogled-chromium.
To use your existing profile with Ungoogled Chromium, simply run:
mv ~/.config/chromium ~/.config/ungoogled-chromium
Notes on Binaries
This build includes a number of additional patches and features:
Patches Included
- Patch (https://gitlab.com/chromium-ppc64le/chromium-ppc64le/docker-root/patches/chrome/enable-vaapi.patch) to enable GPU-accelerated video decoding
- Patch (https://gitlab.com/chromium-ppc64le/chromium-ppc64le/docker-root/patches/chrome/change-user-agent.patch) to change the browser's user agent string to be the same as the official Chrome build on Linux, which helps reduce the browser's fingerprinting surface
- Patch (https://gitlab.com/chromium-ppc64le/chromium-ppc64le/docker-root/patches/chrome/skia-vsx-instructions.patch) to enable use of POWER VSX instructions in the skia rendering engine
Features Enabled
- Link-time optimized builds
- PulseAudio integration
- Non-free codecs
Build Logs
The logs for the build and repo creation are available under GitLab pipelines (https://gitlab.com/chromium-ppc64le/chromium-ppc64le/pipelines).
-
Great job, it was a long time since I wanted to understand how Chromium was installed, of which Raptor had spoken well and recommended for Power. Just installed and I must say that it works very well. Thanks vddvss for the procedure!
-
Hi, even if I registered at the site where the link takes me, I could not find these patches for the GPU you are talking about ... How should I download and install them if I wanted to do it for my AMD RX 5700 XT in case is compatible of course ... The browser already works very well, but if there is a way to further increase the performance and make better use of the graphics card it would be the best ...
-
Hi, even if I registered at the site where the link takes me, I could not find these patches for the GPU you are talking about ... How should I download and install them if I wanted to do it for my AMD RX 5700 XT in case is compatible of course ... The browser already works very well, but if there is a way to further increase the performance and make better use of the graphics card it would be the best ...
Could you go to chrome://gpu then click 'Copy Report to Clipboard`, save it as a file, and post as an attachment here?
-
Sorry but are we obliged to register on the site just to download a patch? It seems excessive to me ... Now for example it denies me access ...
-
Sorry but are we obliged to register on the site just to download a patch? It seems excessive to me ... Now for example it denies me access ...
I guess the link is using the wrong path (perhaps to a private repo or the internal CI/CD artefacts).
Nevertheless I think you can find the patches here eg. in the master branch:
https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/tree/master/docker-root/patches/chrome
-
Yes good Flying, with your link you will arrive direct. But the questions are 2 for me. First, what exactly is the Patch to activate the acceleration of the dedicated graphics card? Question 2, how do you...
-
I'm wondering what do you want to patch?
…
Notes on Binaries
This build includes a number of additional patches and features:
Patches Included
- Patch (https://gitlab.com/chromium-ppc64le/chromium-ppc64le/docker-root/patches/chrome/enable-vaapi.patch) to enable GPU-accelerated video decoding
- Patch (https://gitlab.com/chromium-ppc64le/chromium-ppc64le/docker-root/patches/chrome/change-user-agent.patch) to change the browser's user agent string to be the same as the official Chrome build on Linux, which helps reduce the browser's fingerprinting surface
- Patch (https://gitlab.com/chromium-ppc64le/chromium-ppc64le/docker-root/patches/chrome/skia-vsx-instructions.patch) to enable use of POWER VSX instructions in the skia rendering engine
…
-
First, great job in doing this! Much appreciated.
- Patch (https://gitlab.com/chromium-ppc64le/chromium-ppc64le/docker-root/patches/chrome/change-user-agent.patch) to change the browser's user agent string to be the same as the official
While I understand why this is done, it will result in under-reporting of POWER hardware, and my main concern is that Google may look at (in the worst case) no one using POWER (due to the string reporting x86_64) and continue to reject patches. I don't know if this is a real concern or not, but thought I'd throw it out there for comments.
Worst case the architecture will become just like the rest of the UA string -- spoofed into whatever is most commonly expected for compatibility reasons. We're not there yet though in terms of market research.
-
yes Tim is right, the use of Chromium Power must not be hidden from Google, we have to show that we are here too and that Power has real support is a community that loves and uses it ...
-
Hi All,
I'm trying to install chromium-browser-stable but getting error 500 when trying to download https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/jobs/682882047/artifacts/raw/docker-root/target/chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm
Is this something temporary?
Just for the record, I've succeeded installing ungoogled-chromium-browser-stable.
Thank you all.
-
Hi, maybe there is some error in the command you give, I did the procedure as it is done above by the friend VDDVSS. First I installed the rpmfusion repositories for as the first command says, I copied it the same, then I ran the Chromium installation and it was fine and I did it more than once so it ran perfectly ...
-
Hi,
Thanks, but still did not work. I've followed the instructions and even downloaded again chromium-ppc64le.repo and saved (replaced) it on etc/yum.repos.d
One additional piece of information: I had chromium installed before, removed it to try to fix another issue and then could not reinstall it following the procedure described by VDDVSS. I then installed ungoogled-chromium, where I'm writing this reply.
Any other idea? I've copy/pasted the full command/response below.
Regards
[claudio@localhost ~]$ sudo dnf install chromium-browser-stable
Chromium PPC64LE 5.8 kB/s | 3.0 kB 00:00
Ungoogled Chromium PPC64LE 5.9 kB/s | 3.0 kB 00:00
Dependencies resolved.
=================================================================================================================================
Package Architecture Version Repository Size
=================================================================================================================================
Installing:
chromium-browser-stable ppc64le 84.0.4147.125-1 chromium-ppc64le 66 M
Transaction Summary
=================================================================================================================================
Install 1 Package
Total download size: 66 M
Installed size: 287 M
Is this ok [y/N]: y
Downloading Packages:
[MIRROR] chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm: Status code: 500 for https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/jobs/682882047/artifacts/raw/docker-root/target/chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm (IP: 172.65.251.78)
[MIRROR] chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm: Status code: 500 for https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/jobs/682882047/artifacts/raw/docker-root/target/chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm (IP: 172.65.251.78)
[MIRROR] chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm: Status code: 500 for https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/jobs/682882047/artifacts/raw/docker-root/target/chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm (IP: 172.65.251.78)
[MIRROR] chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm: Status code: 500 for https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/jobs/682882047/artifacts/raw/docker-root/target/chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm (IP: 172.65.251.78)
[FAILED] chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm: Status code: 500 for https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/jobs/682882047/artifacts/raw/docker-root/target/chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm (IP: 172.65.251.78)
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Error downloading packages:
Status code: 500 for https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/jobs/682882047/artifacts/raw/docker-root/target/chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm (IP: 172.65.251.78)
-
If you look at the Chromium Gitlab page (https://gitlab.com/chromium-ppc64le/chromium-ppc64le/) there is a download link how to install on other RPM based distributions:
sudo rpm -Uvh https://github.com/chromium-ppc64le/chromium-ppc64le/releases/download/v84.0.4147.89-1/chromium-browser-stable-84.0.4147.89-1.ppc64le.rpm
This should work.
Edit: Don't miss to "sudo dnf install liberation-fonts"
-
If you look at the Chromium Gitlab page (https://gitlab.com/chromium-ppc64le/chromium-ppc64le/) there is a download link how to install on other RPM based distributions: sudo rpm -Uvh https://github.com/chromium-ppc64le/chromium-ppc64le/releases/download/v84.0.4147.89-1/chromium-browser-stable-84.0.4147.89-1.ppc64le.rpm
This should work.
Edit: Don't miss to "sudo dnf install liberation-fonts"
Tnanks a lot! Worked!
-
Hi,
Now I've updated the system (there were 27 updates) and Chromium is failing to update automatically (Plasma Desktop Workspace).
Is there any manual procedure I can do to update chromium? see below the error message, it's the same issue I circumvented when downloading through the rpm command.
Thanks in advance.
Status code: 500 for https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/jobs/682882047/artifacts/raw/docker-root/target/chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm (IP: 172.65.251.78); Last error: Status code: 500 for https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/jobs/682882047/artifacts/raw/docker-root/target/chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm (IP: 172.65.251.78)
-
Nothing you can do. Status code: 500 is an Internal Server Error.
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
Source: Wikipedia (https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_server_errors)
-
This is the latest release:
https://github.com/chromium-ppc64le/chromium-ppc64le/releases/tag/v84.0.4147.125-1
You can install this RPM.
-
Update: it worked but broke the update (through the UI/KDE or dnf update).
I had to uninstall using an RPM command in order to update other applications and kernel.
It seems the two methods (dnf and rpm) do not get along very well.
-
Wondering if you could re-base the build with the latest version 86? Many thanks
-
And btw is this gitlab repo sharing the same patches as that of https://github.com/leo-lb/ungoogled-chromium?
-
Guys can anyone tell me how to install Chromium on Debian? I did several tests but I never succeeded ...
-
Sorry guys but what happened to Chromium on Power? How come we are stuck at version 84.0.4147.125 and it doesn't update anymore? Has something happened or you have to run some new repository installation that I don't know?
-
I'm also a bit curious about what's happening with the Chromium port...Firefox is still very painful to use (no JIT) and it doesn't look like anyone has updated the Ungoogled/POWER port for a while now?
Typing this from a Blackbird on Ungoogled Chromium... ;)
-
And if you say that you are one who directly follows the development the thing is serious ... I also tried to install the ungogled version on Ubuntu but it gives me the same error as the normal version, it is not available ...
-
I did some digging around today, it looks like the repositories are still being updated, and 88 might be buildable as of around a week ago:
https://github.com/leo-lb/ungoogled-chromium/commit/362ec8584e373b798f9e3e45f4791b2dae2d0ee3
I'll have to give it a try at some point...
-
However https://gitlab.com/chromium-ppc64le/chromium-ppc64le seems out-of-date
It is so frustrating that upstream chrome does not accept these patches https://github.com/leo-lb/ungoogled-chromium/blob/master/patches/series
-
Moral of the story we are still unfortunately still from what I see ... It didn't take, Chromium is the best on Power and not having it updated yet is bad ...
-
Hi guys sorry but I can't install Chromium from this package found in the link of the good TLE. Can you tell me how to install this package on Debian? Thanks, obviously I got the tar.xz archive to be able to install it on Debian ...
-
I am going to give it a try to revive the chromium-ppc64le project
here is my work on version 85 which is quite trivial to patch
https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/merge_requests/1
I will be slowly upgrading the project to version 91
-
Great as always, always thanks for your valuable work on our favorite platform! Let us know how it goes!
-
Okay, folks, the RPM for v85 is now available at https://gitlab.com/chromium-ppc64le/chromium-ppc64le
-
Okay, folks, the RPM for v85 is now available at https://gitlab.com/chromium-ppc64le/chromium-ppc64le
Great! I've already updated. DNF asked to confirm non-official source.. but I trust and praise you tle for your efforts!
-
Okay, folks, the RPM for v85 is now available at https://gitlab.com/chromium-ppc64le/chromium-ppc64le
Great! I've already updated. DNF asked to confirm non-official source.. but I trust and praise you tle for your efforts!
For corporate or security environment, I highly recommend you to clone the repo then `make dev` then `make chromium` or `make ungoogled-chromium` on your local box.
-
Okay, folks, the RPM for v85 is now available at https://gitlab.com/chromium-ppc64le/chromium-ppc64le
Great! I've already updated. DNF asked to confirm non-official source.. but I trust and praise you tle for your efforts!
For corporate or security environment, I highly recommend you to clone the repo then `make dev` then `make chromium` or `make ungoogled-chromium` on your local box.
That's for sure. The only question that remains is who is going to check the source code?
Anyway, CORPORATE, IMHO, means MS, VMWare, RHEL, Oracle, SAP, IBM and many others proprietary softwares that companies and governments trust blindly. Another step further, maybe based on the same arguments ("we trust our IT providers"), most corporations are ok with Intel/AMD and any other blob inside their servers. They even trust cloud providers with their virtualized servers, which they have no guarantee whatsoever of what's "inside".
-
Hi friend TLE, great job you are great. I too have updated the repositories and installed version 85 that you compiled and am using it right now. Thanks for your work for the Open Power community! After a long time we finally have an update of this great browser!
-
v86 is out https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/releases/v86.0.4240.198-1
-
v86 is out https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/releases/v86.0.4240.198-1
Thank you tle! This post is being posted on Chromium v86!
-
Great job, only thing I wanted, asking you is how to install the Debian version. I know I have to download and unpack the tarball but then for the installation I can't find the correct command ...
-
Could you please elaborate a bit more?
-
Yes of course, in practice I download the tarball with Chromium, when I decompress the file, he extracts the file but does it without any extension and apparently this is a problem because if I try to install with the sudo dpkg command, it does not accept it and it gives me error. I tried to look for guides on how to install but unfortunately without success because it always gave me a pat that is no longer present or obsolete. Of course now this is new and I haven't tried to decompress it yet but I wanted to know before acting, if there is any particular command to use or something else to install ...
-
Yes of course, in practice I download the tarball with Chromium, when I decompress the file, he extracts the file but does it without any extension and apparently this is a problem because if I try to install with the sudo dpkg command, it does not accept it and it gives me error. I tried to look for guides on how to install but unfortunately without success because it always gave me a pat that is no longer present or obsolete. Of course now this is new and I haven't tried to decompress it yet but I wanted to know before acting, if there is any particular command to use or something else to install ...
What is the exact error?
-
v87 RPM is out https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/releases/v87.0.4280.67-1
-
Great job as always TLE, as soon as I can I update. The exact error I don't remember, I can try again to give the command and see what happens with this new version. If it still gives me error I will post the exact output of what happens ...
-
v87 RPM is out https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/releases/v87.0.4280.67-1
Thanks tle!
-
Exactly after I do the regular extraction of the archive, the file I get is: chromium-browser-stable-87.04280.67-1. I see that the .deb extension is missing but I tried in any case to give the command: sudo dpkg -i chromium-browser-stable-87.04280.67-1 and he gives me an error with the words: error: the chromium archive -browser-stable-87.04280.67-1 is not a normal file. I also tried to give the classic sudo apt-get install chromium-browser-stable-87.04280.67-1 but again nothing. What do you think am I wrong and what command exactly does it take to install this chromium package on Debian? I think that with this command I do, it doesn't work because it wants .deb extensions and I don't have it on this archive so I think it takes another command ...
-
There is _no_ debian package. The tar.xz is an archive of google binary. You can extract the content then run `./chrome` to start the app.
-
Hi TLE, I ran the command you told me and I started it also on Ubuntu. But my question now arises spontaneously, that is, how do I get the executable file with icon to open like any other installed application? Currently I am forced to always open the shell and give the command you told me to use it, but I would like it to be present already ready like all the other applications ... How should you do it? Thank you
-
You can create a launcher in your local (~/.local/share/applications/chromium-browser.desktop) or global (/usr/share/applications/chromium-browser.desktop) with following content of https://gist.github.com/runlevel5/633e3cbb6c50a78ae3c29ebc9a3db7a8
-
do you mean that I have to go to that path that you wrote me and create the chromium-browser.desktop directory and insert a text file with that link inside it?
-
do you mean that I have to go to that path that you wrote me and create the chromium-browser.desktop directory and insert a text file with that link inside it?
Yes
-
Hi TLE, you had to stop with the development of Chromium apparently, there are no more new versions since I'm seeing and I don't know where to get the sources after 87 to be able to compile it myself unfortunately ...
-
Hi TLE, you had to stop with the development of Chromium apparently, there are no more new versions since I'm seeing and I don't know where to get the sources after 87 to be able to compile it myself unfortunately ...
I've been fully occupied at work. I will try to find time to bump the version to latest. I am more than happy to teach you how to if you are interested.
-
Hello TLE friend, of course I am very interested in doing it, then having a teacher like you is an honor for me! I tried to compile Chromium 87 myself, when you published the sources and the procedure I managed without problems, if the procedure is always the same I have no problems doing it, the problem is that I don't know where to find the sources of the other versions like 88 or 89 etc etc ... If I found the sources I think I would have no problem compiling, always repeat, the procedure is always the same otherwise you should just teach me the new one ... free yourself for the next version ... :)
-
Guys we stopped at version 87 while Google with its Chrome arrived at version 93 and beta 94 ... We have to recover the lost ground otherwise we will be left behind ...
-
All the sources code for the build can be found in https://gitlab.com/chromium-ppc64le
-
Except that I always see up to version 87, besides I don't see anything or at least I don't know how to see the next sources ... Also I see that the most recent files are from 3 months ago ... How can I find the sources from 88 to 93?
-
Check the URL in https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/blob/master/container-root/Makefile#L31-32
-
I keep finding only up to version 87 and with last work done 4 months ago ... I can't find anything else unfortunately ... Or I don't know how to do the right procedure to find it ...
-
Yes because I and other contributors to the project have not time to port all patches to 87 or newer yet
I keep finding only up to version 87 and with last work done 4 months ago ... I can't find anything else unfortunately ... Or I don't know how to do the right procedure to find it ...
-
I understand, then we are waiting for you to bring the latest patches and thus be able to have the new sources to compile ... Come on, we are with you!
-
Guys, you have abandoned the development of Chromium on Power from what I see ... unfortunately everything has stopped for months ... If there were the sources I would have compiled it myself but unfortunately there is nothing beyond the version 87, a real shame because it is the browser that is best of all damn ... :-\
-
Raptor may be willing to pick this up but since Google has refused to upstream the POWER support, and Chromium is not exactly a "typical" free software product, in the current economy this would have to be under some type of bounty system. Frankly, on our side if we're going to invest in a browser development project we'd probably pick Firefox over Chromium given Google's apparent public stance on owner control / individual data rights.
Our question is: is this something that would be palatable? It's a lot of work, so it'd have to be probably in the several thousand USD range (or, worse, significantly more depending on just how Google managed to break the builds in the interim), but if there are (say) a hundred or more Chromium users here that would come down to $100 or less a person. If it worked, we could even make it a subscription type development service; assuming the user numbers are even close to accurate, something like $50 annually and you all always have an up-to-date Chromium browser with builds for Debian / Fedora.
Thoughts welcome! 8)
-
I wouldn't spend much effort into Chromium development. First, Google sucks. Second, Chromium is just fine, it works. I'm on version 93 or 94. But if you're on 70, 80 or 90 doesn't play a role.
But I'm willing to donate for Firefox improvements. To make it on par or surpass Chromium.
And I assume Mozilla is accepting upstream POWER support?
I'm pretty sure, in the long run it's better/ easier to support Firefox.
-
I wouldn't spend much effort into Chromium development. First, Google sucks.
That was never in any doubt. ;)
Second, Chromium is just fine, it works. I'm on version 93 or 94. But if you're on 70, 80 or 90 doesn't play a role.
But I'm willing to donate for Firefox improvements. To make it on par or surpass Chromium.
That would be most welcome. We'll kick this around a bit on our side and figure out if / how to make that happen, and whether it makes more sense to e.g. try to directly fund Cameron or if it might make more sense to add some of our resources to his efforts (i.e. determine if he's time or cash limited right now on the Firefox port).
And I assume Mozilla is accepting upstream POWER support?
Yes. Firefox's issues stem purely from performance problems in regard to the lack of JIT etc., and they are willing to accept patches.
I'm pretty sure, in the long run it's better/ easier to support Firefox.
There is a bit of a marketshare (IE6-type) problem here, Chromium is all that many developers write for these days (right or wrong, this is just the way things are) and as a result it is still important to have Chromium support on POWER if it is to remain a viable desktop platform. That said, if Firefox works better and we can really hammer home the privacy aspects (e.g. get Mozilla to start changing some stances on e.g. DRM in the browser) there might be a way back from the brink.
-
Guys sorry, I understand what you are saying but the fact remains that to date, Chromium is the only browser that works without problems on Power there is little to do. Firefox still lacks the strength of Chromium and whether we want it or not, that's the way it is. In my opinion we must have Chromium on Power and it also seems strange to me that you Raptor tell me about Firefox when you were the first to support Chromium on Power ... What should you do to get the new sources after version 87? If there is a pod, let's use it and continue to carry on what is currently the only complete and totally usable browser on Power ... In my opinion at the moment there is nothing else we can do ... new sources ...
-
I would also be willing to donate for Firefox improvements. The web has coalesced around chrome/blink only because there is so much inertia on its side and I'd rather help against that inertia. For perspective, is it not the same as with x86 vs POWER?
-
But then excuse me, using the wiki procedure that Raptor published last year, are you still unable to get the sources for the new version of Chromium today? I wanted to understand if by doing that procedure I can get the latest version or not ...
https://wiki.raptorcs.com/wiki/Porting/Chromium_(New)
-
I just tried to carry out this procedure but it can no longer be used because some parts are now missing, I had to imagine it in reality ... I would like to understand at this point what procedure uses for example @TLE, to obtain now as now the Chromium code to be able to then fill in ... Now you have to get the unofficial one of course ...
As for the development of Firefox or Chromium, from what I currently see is that Firefox continues not to be at the height of the situation, some sites do not load them, for that famous lack of jit, while instead Chromium still loads everything and well, so to date unfortunately, Chromium is the only really good browser on Power whether we like it or not! We must therefore do something so that there is a development or one or the other but real, otherwise we risk no longer having a decent browser for our systems ... I don't understand why Google has made this move, Chromium is an open source project therefore free and developable if I'm not mistaken so why suddenly boycott our version? What have we done to Google? It seems absurd to me ... We still need a browser that is up to par and today Firefox is still not, there is little to do!
-
It's pretty much time dependence. My day job is ... different.
-
Classic obviously no one says that Forefox's problem depends on you indeed, we just have to thank you for the great work you do and we know that your job is not to develop it. I'm just saying that at the moment Chromium is the only good and well-functioning browser on Power and I think we have to do everything to carry it forward, even unofficially as we did from version 85 to version 87. Only now we are stopped because the friend TLE doesn't even have time to get down to getting the source code. When he finds the time I hope he will show me too how he does it so I can see if I can learn the procedure and thus contribute to the development of Chromium on Power ...
-
Ei TLE, we are in the Christmas period, now we hope you can get back to work on the Chromium code that we have been waiting for for a long time ... Give us some good news so please ... :)
-
Guys, I inform you that given the stalemate that has arisen on Chromium, I wrote directly to Raptor to point out what is becoming a problem for our Power systems or the lack of a well-functioning browser for our architecture. Unfortunately Firefox, you all know that despite the efforts to be praised by his friend Classic Has, he still cannot browse all sites, there are sites he cannot even enter. So it is clear that something needs to be done to solve this problem otherwise we will be out of global navigation which in 2022 is unthinkable for a modern computer. Evidently TLE is no longer able to develop versions after 87 and we have been stuck for some time now. Raptor is meeting to decide what to do and I hope they find a solution soon. If anyone needs Chromium continuity support let me know I'm happy to help.
-
Which site does not work with Chromium 87?
-
I was talking about Firefox not working on some sites, not Chromium ... Firefox is not working on some sites today.
-
Maury, as you've mentioned elsewhere, this seems to be something specific to Ubuntu's Firefox package. Fedora's doesn't have problems like you describe and neither does (to the best of knowledge) Void. If Ubuntu's screwing up their build somehow, that's probably not something that can be fixed on Mozilla's end. What do the Ubuntu port maintainers say about it?
-
No Classic, I was talking about Firefox in general, I was not talking about Firefox on Ubuntu specifically, attention. The problem Firefox has on Ubuntu is that it has a probable conflict with Ubuntu security software and consequently doesn't make Firefox bookmark work but I'm not talking about that. I am talking about the current limitations that Firefox has on some sites where either it does not go at all or is struggling and I am not referring to the Ubuntu version of the Firefox on Power in general. For the bookmarks problem we have reopened the problem with the friend amock who also uses Ubuntu, we wrote that this problem still exists and if they can solve it but I am referring to the navigation problems in general of Firefox not to bookmarks ... Firefox on Power, unfortunately it still reveals less performing and with some limitations compared to Chromium and this creates a big problem since Chromium has remained stationary and or sooner or later if it will no longer be updated, the time will come that we will no longer be able to use it and if Firefox continue with these limitations, we will be out of navigation on a global level ... I also encountered the same problems when I was using Fedora. I haven't used Fedora for a short time, but until recently when I was using it, the problem was still the same on Firefox.
-
Please be more specific about what's not working in Firefox (preferably an example website). I haven't encountered any problems myself, but Mozilla is willing to accept fixes, and we've gotten them upstreamed easily in the past. If it's a performance problem, however, then that's what the JIT is designed to fix, and it is progressing rapidly.
-
An example that I can give you quick, tried a few days ago, I tried to enter the Motorola site, I simply did www.motorola.com, did it more than once and none of the times Firefox managed to enter ... Now I don't have tried with the latest version ...
-
Motorola (com/ IT/ DE) works. Do you have another example?
Funnily, the site is on Firefox smoother than on Chromium.
-
ok I'll try version 96 too, thanks. For other examples I have to make a local mind and review because being that I always use it very little I do not remember all the sites where I had problems ... In the meantime I try with the 96 version if it goes to me too. Thank you
-
Works fine here too (Fedora), also Fx96.
-
No guys, apparently the problem lies specifically in the Ubuntu version of Firefox. It seems that the problem of the inability to save the history and save the sites in the bookmark is not the only defect of Firefox on Ubuntu. The absurd thing that I don't understand is why only on Ubuntu, Firefox should be the same for everyone but obviously they use some damn type of software that conflicts with some parts of Firefox and nobody notices it because it is not used a lot. For example, the www.philips.it site is also lacking. Enter the home page but if you try to go to the audio video section for example, a # symbol appears in front of the address and it does nothing, it does not go to that page. Everything then retried with Firefox ESR on Debian and everything works fine.
-
Must be something about their build config. Have you posted a bug report? Screenshots could help. There are ways to easily tank a Firefox build, which (even though the default Fedora package works fine) I build my own from source.
-
With my friend Amock, we talked about these reports, he also uses Ubuntu and gave me a link where to report the problem related to the bookmark that has always plagued the Ubuntu version. In the meantime he told me that he too makes his source and he explained how to do it and he also told me that if you do it from the source, then these problems are not encountered. I tried to do it myself as a source but I couldn't. You Classic can you try to give me the exact procedure to be able to build it myself from source and see if I can do it with yours? Maybe there is something in your procedure that doesn't work and I can't build it myself ... Regarding the bug report we wrote on this site but we haven't received any new answers yet, unfortunately ...
https://bugzilla.mozilla.org/show_bug.cgi?id=1591164
-
If it's a Ubuntu related bug you have to report it to Ubuntu not Mozilla. I guess you have to enable something in the Firefox settings to get it work. I know a few people using Firefox on Ubuntu and never heard about that problem.
-
Ok but these people you say use the Power version? Because from what I understand, the problem occurs on Power not on X86 ... I wrote in that forum because my friend Amock told me that there was a report made to that site and that they had already tried to solve it but without success. If I knew who is using Firefox on Ubuntu I could ask directly if something should be enabled but I think it is our version of Power that suffers from these annoying bugs ...
-
I can't give you the exact procedure for Ubuntu (I build on Fedora), so the packages will differ. You'll need, at minimum, Mercurial (hg), Python 3 with pip and dev libraries, gcc, clang, nodejs, rust+cargo and development headers for GTK, and probably other packages I can't think of off the top of my head. Firefox comes with vendored sqlite, NSS and most media libraries, so you shouldn't need those to build (in fact, using the system libraries has sometimes been problematic, so I recommend against it).
Once you have done, get a copy of mozilla-release and use the .mozconfigs I report here (I would start with a debug build first and ensure that works to avoid LTO-PGO variables) like https://www.talospace.com/2022/01/firefox-96-on-power.html and do a ./mach build in the source directory. Also refer to notes on https://firefox-source-docs.mozilla.org/setup/linux_build.html (minus the bootstrap part, because you already have the proper packages).
-
Thank you Classic for your always valuable information. Meanwhile, I have good news on the Chromium front, Raptor gave me this link ...
https://quickbuild.io/~raptor-engineering-public/+archive/ubuntu/chromium/+packages…
-
Guys I have noticed a strange thing since I have been using Chromium 97. There are some videos on You Tube that I get errors and they don't load. Then the same videos I go to play them with Firefox and they work regularly. It seems that there has been a step back from Chromium to Power and instead Firefox has taken a decisive step forward. I am using Debian as a distro and like Firefox now version 91.06 ESR has arrived which works really well, by the way I take this opportunity to congratulate my friend Classic for the excellent work he does on Firefox for Power. Returning to Chromium, it is really strange that a browser like him that grinds everything on the web, now has some difficulties. Obviously I have installed all the additional files that Raptor has published together with the main version of Chromium 97 ... Do you have any idea of what happens ...
-
Guys sorry but apart from the Debian and derivative versions, is there a Fedora or other version of Chromium up to date? I have not seen anything at the moment it seems to me ...
-
Hi All,
I've just upgraded to Fedora 36 (I was already on kernel 5.17) and the upgrade broke my Chromium. I've tried downloading chromium-common_83.0.4103.116-1~deb10u3~ppc64elb4_ppc64el.deb from https://quickbuild.io/~raptor-engineering-public/+archive/ubuntu/chromium/+build/543052 but the install fails with error message "ile /usr/lib from install of chromium-common-83.0.4103.116-2.ppc64le conflicts with file from package filesystem-3.16-2.fc36.ppc64le".
Any ideas?
Thanks in advance.
-
Have you tried with version 87? 83 is now too old I think ... And then I go back to my same previous question, haven't they released any of the new versions in RPM package for Fedora? The 8X series are too old versions now ...
-
It's 87 from https://gitlab.com/chromium-ppc64le/chromium-ppc64le, the ungoogled chrome. Standard chromium fail to download:
[FAILED] chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm: Status code: 500 for https://gitlab.com/chromium-ppc64le/chromium-ppc64le/-/jobs/682882047/artifacts/raw/docker-root/target/chromium-browser-stable-84.0.4147.125-1.ppc64le.rpm (IP: 2606:4700:90:0:f22e:fbec:5bed:a9b9)
-
However it is very strange because the standard Chromium version 87 has always worked well on Fedora ... Anyway what I don't know is because nobody talks about new versions that are currently available for Debian and derivatives, I have not found anything about these new versions, made for Fedora ... Here in the forum, no one knows anything apparently and it's even stranger ...
-
Hi Maury,
I've found this one from Raptor: https://quickbuild.io/~raptor-engineering-public/+archive/ubuntu/chromium/+build/543247 and got excited because it's recent 2022-05-15 and updated version.
I've tried downloading and installing the following packages:
chromium-101.0.4951.64-2.ppc64le.rpm chromium-driver-101.0.4951.64-2.ppc64le.rpm
chromium-common-101.0.4951.64-2.ppc64le.rpm chromium-l10n-101.0.4951.64-2.noarch.rpm
but all (except chromium-l10n-101.0.4951.64-2.noarch) gives me an error message:
- nothing provides libjsoncpp.so.24()(64bit) needed by chromium-101.0.4951.64-2.ppc64le
- nothing provides libwebp.so.6()(64bit) needed by chromium-101.0.4951.64-2.ppc64le
which I could not find on the web.
Package chromium-l10n-101.0.4951.64-2.noarch gives me a different error: file /usr/lib from install of chromium-l10n-101.0.4951.64-2.noarch conflicts with file from package filesystem-3.16-2.fc36.ppc64le
Any ideas?
-
But I didn't understand where you got the RPM files to tell the truth. Apart from that, I have no idea where to find those libraries of course, here the most knowledgeable about Fedora are Classic Has and TLE, except that Classic works on Firefox and so I think you don't use Chromium, TLE used and uses Chromium but I don't have idea if you currently have the latest version installed. I tried to ask but no one answered unfortunately. Maybe MPC7500 knows something because he also used Fedora a lot ... I've been using Debian for some time now, so no more problems thankfully but honestly I've always wondered how to make Chromium work new on Fedora .. .
-
I haven't used Fedora for ages.
But both packages (jsoncpp, libwebp) are available for Fedora:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1886948
https://koji.fedoraproject.org/koji/buildinfo?buildID=1913713
You could also take a look at
https://wiki.raptorcs.com/wiki/Porting/Chromium_(New)
No idea, if it's up-to-date.
-
Thanks MPC7500, I'll try to install them and then Chromium.
-
Thanks MPC7500, I'll try to install them and then Chromium.
It's a while since my last update with this project. I was getting frustrated with the huge amount of work to get it going (plus I was a bit burned out at work too). So if you feel like to contribute to the project, please let me know. I am more than happy to guide people through the process to keep it supported a bit further.
-
Hi TLE, thanks for offering help and support. I turn the Blackbird once a week and I do not have much time either. Anyway, if you can provide some guidance I can try but I'm really not familiar with Git or building code. Regards
-
Quick update: GitLab has officially support podman as runner.
I've updated all repos to schedule builds on workers that run podman instead of docker. This is a big win because it has taken me lots of time to get Docker built and run correctly on CentOS/RHEL/Fedora distros
-
Chromium is a beast! It took avg 1h30 to 2h to compile everything from scratch with my 8 core CPU :(
I want to keep the chromium-ppc64le project up to date but with huge amount wasted on waiting, I don't think I could be productive because my time for OSS has been scarce due to other commitment
Wondering if anyone could donate an agent or two with access to as many cores as possible? Great thanks
-
Now you know how much pain it was to build TenFourFox. That was about 14 hours with the G5 tied up roaring away.
-
Yes TLE, I also confirm what you say because once I tried compiling version 87 and I remember that it took hours to complete the cycle, I have an 8 core. But excuse me are you building the latest version Raptor supports with Debian? I switched to Debian for some time and I use this one and in fact I don't see Fedora versions for example...
-
I am building the RPM version for RHEL/Fedora.
-
Great job well, after so much finally, Chromium is back on Fedora too, it's missing from that famous 87 version when it was still Chromium with Google exsperince, now we can't use it on Power anymore but at least having Chromium is always great, well done great job!
-
I've read that from version 113, Chrome will get more specific support for gpu usage called WebGPU, I've also read that it's coming to Linux as well. Do you think we too will be able to have this possibility once it arrives on Linux?
-
I am building the RPM version for RHEL/Fedora.
Hey, any updates on this? Are these available anywhere? The parent post provides a repo, but try as I might I can't actually download or install anything from it.
-
From what I remember, when my friend TLE has some application ready, he publishes it immediately in the appropriate discussion so I deduce that he is still stuck on this version of Chromium for Fedora... It's been a long time since Chromium is no longer available on Fedora Power version...
-
doesn't work for me on fedora 38 or opensuse tumbleweed, worked fine on opensuse leap 15.4 and 15.5, the RPMs that is, but the binary builds dont work either
-
Yeah, I'm also wondering what the best solution is. I don't like Chromium, but sometimes I need to have access to it, and hopping over to my MacBook Air or Windows desktop isn't necessarily the best solution.
-
doesn't work for me on fedora 38 or opensuse tumbleweed, worked fine on opensuse leap 15.4 and 15.5, the RPMs that is, but the binary builds dont work either
It no longer work on F38. I have not touched this for a quite awhile. If you have capacity, please give it a try to see if we have to patch anything for F38
-
doesn't work for me on fedora 38 or opensuse tumbleweed, worked fine on opensuse leap 15.4 and 15.5, the RPMs that is, but the binary builds dont work either
If you have capacity, please give it a try to see if we have to patch anything for F38
I don't, or I would, and I'd probably be porting more stuff to opensuse if I did. I'm only on fedora right now because of the lack of libs and packages for opensuse on ppc64le. Idk how big endian tumbleweed is.
-
Here are build scripts, also for Chromium
https://github.com/ppc64le/build-scripts