Forum › Forums › New users › New Users and General Questions › Chromium Browser on 32-bit antiX
- This topic has 12 replies, 4 voices, and was last updated Dec 28-12:24 am by marcelocripe.
-
AuthorPosts
-
December 26, 2021 at 11:35 pm #73755Member
seaken64
Can someone please clarify for me the status of the Chromium browser on 32-bit?
I thought that Chromium dropped 32-bit. Yet it still have it in antiX 32-bit. It does not work on some of my older machines but it does still work on this Athlon 64 X2 even though I have antiX 32-bit installed. Maybe I am wrong about Chromium and 32-bit?
I know they dropped support for SSE3, I think?Incorrect. They REQUIRE at least SSE3. Maybe that is what I was thinking about. I googled it but I can’t nail down an official answer. Anyone know?Seaken64
Edit – I found the reason some of my 32-bit machines do not work with Chromium and some do. Some Pentium 4’s do not support SSE3. At least one of my Pentium 4’s does support SSE3. The one that does support SSE3, and thus works with Chromium, is a “Prescott” version of Pentium 4.
Bottom line – 32-bit is still supported in Chromium (but not Chrome) but SSE3 is required.
- This topic was modified 1 year, 4 months ago by seaken64.
- This topic was modified 1 year, 4 months ago by seaken64.
December 27, 2021 at 12:24 am #73758Memberseaken64
::OK, I think I figured this out. I think it is only CHROME that dropped 32-bit. Chromium is still being compiled with 32-bit support by some vendors, including Debian?
Some of what I read on the web leads me to believe 32-bit Chromium is dead. But I think it depends on the developer. And there are some Chromium-based browsers that also may still support 32-bit.
Still reading, and it’s getting harder to find 32-bit browser support. Most of the Chromium-based browsers do not work for my 32-bit machines. But Chromium itself seems to work. At least for now.
Seaken64
Edit – if it’s a Chromium based browser it will require SSE3. If the CPU does not have SSE3 it won’t work. So, it’s not 32-bit so much as it’s SSE3. Once again I forgot what the issue was. I misremebered that the problem was 32-bit.
- This reply was modified 1 year, 4 months ago by seaken64.
December 27, 2021 at 3:58 am #73776Member
schproodle
::But Chromium itself seems to work. At least for now.
Very well for my EeePC:
Info: Single Core model: Intel Atom N280 bits: 32 type: MT arch: Bonnell family: 6
model-id: 1C (28) stepping: 2 microcode: 218 cache: L2: 512 KiB bogomips: 6650
Speed: 1000 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 1000 2: 1000
Flags
[…]
pbe pdcm pebs pge pni pse sep ss sse sse2 ssse3 tm tm2 tsc vme xtprThanks for clarifying these issues. 🙂
EeePC, ASUSTek 1000HE - Atom N280, 1667 MHz, 32 bit - RAM 992.2 MiB
Kernel: 4.9.0-279-antix.1-486-smp i686 bits: 32 compiler: gcc v: 10.2.1
Desktop: IceWM 2.9.3 & zzzfm
Distro: antiX-21_386-full Grup Yorum 31 October 2021December 27, 2021 at 3:43 pm #73843MemberPPC
::I have one single 32bits machine available- and I tested- it installs Chromium from the package installer (so there’s a 32bis version available), but chromium fails to run on that laptop
P.
December 27, 2021 at 4:10 pm #73847Member
schproodle
::An interesting comparison. 32 bit, 1 G RAM and 1600 Mhz. Atom N280. What’s up? 8/
With chromium I tried to use the site: https://www.nhm.ac.uk/wpy/gallery/2016-night-blow?tags=ed.5. It was painfully slow – CPU on fire but with minimal memory usage. With Firefox it was just fine.
EeePC, ASUSTek 1000HE - Atom N280, 1667 MHz, 32 bit - RAM 992.2 MiB
Kernel: 4.9.0-279-antix.1-486-smp i686 bits: 32 compiler: gcc v: 10.2.1
Desktop: IceWM 2.9.3 & zzzfm
Distro: antiX-21_386-full Grup Yorum 31 October 2021December 27, 2021 at 4:14 pm #73850Memberseaken64
::I have one single 32bits machine available- and I tested- it installs Chromium from the package installer (so there’s a 32bis version available), but chromium fails to run on that laptop
P.
Yes, this is where it gets confusing. Chromium will install on the 32-bit version of antiX from the Package Installer. But it will not RUN unless your 32-bit machine supports SSE3.
I guess there is no easy way to know if a browser on the list will work or not. You just have to install it and try it. If it doesn’t work just uninstall it.
I had a similar issue with Otter-Browser on my P-III. I can install it and it even starts up. But it crashes as soon as you attempt to browse anywhere. I’m assuming because it needs at least SSE2. SeaMonkey also needs SSE2 and will not even start on this P-III. But I can run an earlier version which does not require SSE2.
The Package Installer does not indicate these things. You just have to try it out and then do your research if it doesn’t work. There is more room for information in Synaptic but I’m not sure if the package descriptions offer this information in Synaptic either. It’s a small problem and only effects us 32-bit users who have some old equipment that differs a little bit from the mainstream. It’s one of the costs of using old equipment.
Seaken64
December 27, 2021 at 4:19 pm #73852Memberseaken64
::An interesting comparison. 32 bit, 1 G RAM and 1600 Mhz. Atom N280. What’s up? 8/
With chromium I tried to use the site: https://www.nhm.ac.uk/wpy/gallery/2016-night-blow?tags=ed.5. It was painfully slow – CPU on fire but with minimal memory usage. With Firefox it was just fine.
I’m not sure. But I noticed a while ago that FirefoxESR seems to work on non-SSE2 systems just fine. It may have something to do with SSE2/SSE3. Chromium wants SSE3. FirefoxESR doesn’t seem to care.
Seaken64
December 27, 2021 at 4:34 pm #73857Member
schproodle
::I turned off hardware acceleration in chromium settings. Now OK. 🙂
EeePC, ASUSTek 1000HE - Atom N280, 1667 MHz, 32 bit - RAM 992.2 MiB
Kernel: 4.9.0-279-antix.1-486-smp i686 bits: 32 compiler: gcc v: 10.2.1
Desktop: IceWM 2.9.3 & zzzfm
Distro: antiX-21_386-full Grup Yorum 31 October 2021December 27, 2021 at 4:57 pm #73861Memberseaken64
December 27, 2021 at 4:57 pm #73862Member
marcelocripe
::Dear Seaken64 and Schproodle.
Xecure achieved a solution that was described in detail in the topic:
– – – – –
Caros Seaken64 e Schproodle.
O Xecure conseguiu uma solução que foi descrita com detalhes no tópico:
(O URL está no texto em idioma Inglês)December 27, 2021 at 5:02 pm #73863Member
schproodle
::Firefox was set to use hardware acceleration when available. :/
EeePC, ASUSTek 1000HE - Atom N280, 1667 MHz, 32 bit - RAM 992.2 MiB
Kernel: 4.9.0-279-antix.1-486-smp i686 bits: 32 compiler: gcc v: 10.2.1
Desktop: IceWM 2.9.3 & zzzfm
Distro: antiX-21_386-full Grup Yorum 31 October 2021December 27, 2021 at 6:03 pm #73865Memberseaken64
::Dear Seaken64 and Schproodle.
Xecure achieved a solution that was described in detail in the topic:
@marcelo, are you still using Chromium 88?
I feel like such a dolt. This is all just a re-hash of what we already discussed months ago, as that topic shows. It’s clear that I am having issues with my memory. And I need to start using search before I start a topic that has already been discussed in detail on the forum.
Anyway, thanks for the input. And for those who already knew all this stuff about Chromium and 32-bit from our previous discussions I thank you for your patience.
Seaken64
December 28, 2021 at 12:24 am #73924Member
marcelocripe
::I feel like such a dolt.
Don’t feel that way, you are not it.
The other topic “Chromium not working” has a generic title and does not mention what you are looking for “Chromium Browser on 32-bit antiX”, this topic is much easier to find due to the words used than the other. It was Xecure that understood my need to print the translated forum pages both for future consultation and to share the translated content in the Telegram and WhatsApp groups. Xecure as usual, is always very technical and considerate, brought detailed information for Chromium 64-bit and 32-bit. Both this thread you started and the other “How do I translate a forum page on 32-bit browser” are of interest to me, I’m able to keep up with the threads, but I can’t help with testing. The tests you can run and bring important information that interest me and that will certainly be of great use to other people who have 32-bit processors and each day, week or month find themselves with fewer options to keep the computer running.
antiX itself fights against planned obsolescence or even forced obsolescence of technology, but what is the point of having a fantastic operating system if there are no programs that work on it?
Hence the importance of your two topics, in addition to the others you created, I could learn and I’m sure other people also learned from your sharing of information.
Thank you so much for sharing your knowledge and your tests.@marcelo, are you still using Chromium 88?
Answer: Yes. But it is for exclusive use on the forum, as several people warned in the other thread about the risk of using an old or outdated internet browser.
The forum search is not that simple, depending on the typed text, more than 30 pages will be displayed, for the text “Chromium not working” 4 pages were displayed, it takes a long time to read them all, even more for those who depend on machine translation . I only found the topic quickly because I remembered the translated script, so I had to use the translator to find the English text. Often, the information we need is between the threads of the topic where, the title does not match the subject you are looking for, it is practically impossible to find the desired information.
I apologize if I didn’t understand your question in the other topic, too many words and the real meaning are unfortunately lost in machine translators.
– – – – –
I feel like such a dolt.
Não se sinta assim, pois você não é isto.
O outro tópico “Chromium not working” possui um título genérico e não faz menção ao que você está procurando “Chromium Browser on 32-bit antiX”, é muito mais fácil encontrar este tópico devido as palavras utilizadas do que o outro. Foi o Xecure que compreendeu a minha necessidade de imprimir as páginas do fórum traduzidas tanto pata consulta futura quanto para compartilhar o conteúdo traduzido nos grupos de Telegram e WhatsApp. O Xecure como de costume, é sempre muito técnico e atencioso, trouxe informações detalhadas para o Chromium de 64 bits e 32 bits. Tanto este tópico que você iniciou quanto o outro “How do I translate a forum page on 32-bit browser” são do meu interesse, eu estou conseguindo acompanhar os tópicos, mas não estou podendo ajudar com testes. Os testes você está podendo executar e trás informações importantes que me interessam e que certamente serão de grande utilidade para outras pessoas que possuem processadores de 32 bits e que a cada dia, semana ou mês se vê com menos opções de manter o computador funcionado.
O antiX por si só luta contra a obsolência programada ou até mesmo contra a obsolência forçada de tecnologia, mas para que serve ter um sistema operacional fantástico se não existem programas que funcionem nele?
Daí a importância dos seus dois tópicos, além dos outros que você criou, eu pude pude aprender e tenho certeza que outras pessoas também aprenderam com o seu compartilhamento de informações.
Muito obrigado por compartilhar o seu conhecimento e os seus testes.@marcelo, are you still using Chromium 88?
Resposta: Sim. Mas é para uso exclusivo no fórum, pois várias pessoas alertaram no outro tópico sobre o risco em utilizar um navegador de internet antigo ou desatualizado.
A busca no fórum não é tão simples assim, dependendo do texto digitado, mais de 30 páginas serão exibidas, para o texto “Chromium not working” foram exibidas 4 páginas, leva muito tempo ler todas elas, ainda mais para quem depende de tradução automática. Eu só encontrei o tópico rapidamente porque eu me lembrava da escrita traduzida, então eu tive que usar o tradutor para encontrar o texto em Inglês. Muitas vezes, a informação que precisamos está nas entrelinhas de tópico onde, o título não condiz com o assunto que você está procurando, é praticamente impossível encontrar a informação desejada.
Eu peço desculpas se eu não compreendi a sua pergunta no outro tópico, muitas palavras e o sentido real, infelizmente são perdidos nos tradutores automáticos.
-
AuthorPosts
- You must be logged in to reply to this topic.