[SOLVED] Slackware arm current - no usable web browser?
Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If anyone is instrested, Chromium-ungoogled 102.0.5005.115 package for Slackware Armv7 is avalible.
Sorry to say i have not bothered to compile Chromium as i only use Chromium-ungoogled, due to the compile time.
Enjoy
I am and thank you for your effort. This is saving me the 46+ hours build time.
Despite Exaga supplying the 64bit kernel for kernel, I found my system to be really slow. The 32 on the other hand just runs so well and I much prefer having the stable release, your browser build just completes it.
Last edited by pm_a_cup_of_tea; 06-30-2022 at 08:30 AM.
Despite Exaga supplying the 64bit kernel for kernel, I found my system to be really slow.
Depending on how you're using the RPi, don't forget you can set the 'gpu_mem=' setting in the config.txt file to allocate the available RAM. I always have mine set at 'gpu_mem=32' because I rarely use the desktop. Gotta say Slackware AArch64 on the RPi4 is pretty damned quick.
I am and thank you for your effort. This is saving me the 46+ hours build time.
Despite Exaga supplying the 64bit kernel for kernel, I found my system to be really slow. The 32 on the other hand just runs so well and I much prefer having the stable release, your browser build just completes it.
Some reasons why i will be sticking with Slackare ARM 15.0 (32 bit)
As the RPI 4 i have with 4 GB Ram (512 MB used for GPU) i dont really see any reason to use 64bit even thow the cpu suports ARMv8.
There is as far as i know (What i have read) no Widevine for Aarch64, solution is to use 32bit version from chromiumOS.
So i am guessing one has to have multilib on Aarch64 to be able to run Widevine 32bit in 64bit system? (As i understand, this is the official solution for RPI) https://github.com/raspberrypi/Raspb...4bit/issues/11
This also means that one has to have a 32bit chromium web browser installed anyway in order to be able to view DRM streams.
So, i will be sticking with Slackware ARM 15.0 as long as i can.
Happy with my setup, the system and programs are stable and reliable after some patches, updates and tweeks =)
Packages that i patched as described on my github, glibc
And upgraded python3 to 3.9.13
Last edited by Minime_2003; 06-30-2022 at 06:51 PM.
Thanks for the reply. I setup up the config.txt in my usual manner but I'll reinstall and see. I am sure its either me or my hardware
Sure thing. As always, each user will have to do some tinkering and find the most suitable balance for their test-case/usage.
The reason why I say Slackware AArch64 is pretty damned quick, and what I'm basing it on, is the increase in compiling times on the RPi4 [4GB] compared to Slackware ARM 15.0. For example, on the same machine, running Slackware ARM 15.0 it'll build 'google-go-lang_1.17.9' pkg in approx. 35 minutes, and when running Slackware AArch64 the same pkg will build in approx. 25 minutes. I use the same SSD storage drive and have a 8GB /swap partition on both OS.
If anyone is instrested, Chromium-ungoogled 103.0.5060.114 package for Slackware Armv7 is avalible.
At the moment i have not compiled Chromium 103.0.5060.114, however i might be adding this at some point if i can find the time.
Sorry for that.
Sure thing. As always, each user will have to do some tinkering and find the most suitable balance for their test-case/usage.
The reason why I say Slackware AArch64 is pretty damned quick, and what I'm basing it on, is the increase in compiling times on the RPi4 [4GB] compared to Slackware ARM 15.0. For example, on the same machine, running Slackware ARM 15.0 it'll build 'google-go-lang_1.17.9' pkg in approx. 35 minutes, and when running Slackware AArch64 the same pkg will build in approx. 25 minutes. I use the same SSD storage drive and have a 8GB /swap partition on both OS.
It was absolutely my hardware. I purchased a new SSD and that did wonders
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
