#i686 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #i686, aggregated by home.social.
-
AlmaLinux 10.2 Lavender Lion Beta supports older CPUs while RHEL moves on
https://web.brid.gy/r/https://nerds.xyz/2026/05/almalinux-10-2-beta-lavender-lion/
-
AlmaLinux 10.2 Lavender Lion Beta supports older CPUs while RHEL moves on
https://fed.brid.gy/r/https://nerds.xyz/2026/05/almalinux-10-2-beta-lavender-lion/
-
AlmaLinux 10.2 Lavender Lion Beta supports older CPUs while RHEL moves on
https://fed.brid.gy/r/https://nerds.xyz/2026/05/almalinux-10-2-beta-lavender-lion/
-
Hype for the Future 139L → GNU Cross Compiler (GCC) System Architecture Matrix
Introduction The following table represents a matrix of x86-architecture system central processing units (CPUs) with respects to functionality, including both 32-bit and 64-bit system processors: Legacy Intel ProcessorArchitectureExtensionsi386i386--i486i486--i586 = pentiumi586--lakemont (Intel Lakemont MCU)i586--pentium-mmxi586MMXpentiumproi686--i686i686--pentium2i686MMXpentium3, pentium3mi686MMX, SSEpentium-mi686MMX, SSE, SSE2pentium4, pentium4mi686MMX, SSE, SSE2prescotti686MMX, SSE, […] -
Hype for the Future 139L → GNU Cross Compiler (GCC) System Architecture Matrix
Introduction The following table represents a matrix of x86-architecture system central processing units (CPUs) with respects to functionality, including both 32-bit and 64-bit system processors: Legacy Intel ProcessorArchitectureExtensionsi386i386--i486i486--i586 = pentiumi586--lakemont (Intel Lakemont MCU)i586--pentium-mmxi586MMXpentiumproi686--i686i686--pentium2i686MMXpentium3, pentium3mi686MMX, SSEpentium-mi686MMX, SSE, SSE2pentium4, pentium4mi686MMX, SSE, SSE2prescotti686MMX, SSE, […] -
Hype for the Future 139L → GNU Cross Compiler (GCC) System Architecture Matrix
Introduction The following table represents a matrix of x86-architecture system central processing units (CPUs) with respects to functionality, including both 32-bit and 64-bit system processors: Legacy Intel ProcessorArchitectureExtensionsi386i386--i486i486--i586 = pentiumi586--lakemont (Intel Lakemont MCU)i586--pentium-mmxi586MMXpentiumproi686--i686i686--pentium2i686MMXpentium3, pentium3mi686MMX, SSEpentium-mi686MMX, SSE, SSE2pentium4, pentium4mi686MMX, SSE, SSE2prescotti686MMX, SSE, […] -
Hype for the Future 139L → GNU Cross Compiler (GCC) System Architecture Matrix
Introduction The following table represents a matrix of x86-architecture system central processing units (CPUs) with respects to functionality, including both 32-bit and 64-bit system processors: Legacy Intel ProcessorArchitectureExtensionsi386i386--i486i486--i586 = pentiumi586--lakemont (Intel Lakemont MCU)i586--pentium-mmxi586MMXpentiumproi686--i686i686--pentium2i686MMXpentium3, pentium3mi686MMX, SSEpentium-mi686MMX, SSE, SSE2pentium4, pentium4mi686MMX, SSE, SSE2prescotti686MMX, SSE, […] -
Hype for the Future 140E → GNU Cross Compiler (GCC) System Architecture Matrix
Introduction The following table represents a matrix of x86-architecture system central processing units (CPUs) with respects to functionality, including both 32-bit and 64-bit system processors: Legacy Intel ProcessorArchitectureExtensionsi386i386--i486i486--i586 = pentiumi586--lakemont (Intel Lakemont MCU)i586--pentium-mmxi586MMXpentiumproi686--i686i686--pentium2i686MMXpentium3, pentium3mi686MMX, SSEpentium-mi686MMX, SSE, SSE2pentium4, pentium4mi686MMX, SSE, SSE2prescotti686MMX, SSE, […] -
Ich bin vorerst begeistert von #emmabuntus #emmabuntüs #Debian
das #toughbook ist gefühlt älter als Steinkohle, #i686 #32bit.
Das angedachte #puppylinux wollte nicht (und einige andere 32bit- #distribution en ebenso), dafür hab ich #emmabuntus gefunden...Schaut mal rein!
-
Ich bin vorerst begeistert von #emmabuntus #emmabuntüs #Debian
das #toughbook ist gefühlt älter als Steinkohle, #i686 #32bit.
Das angedachte #puppylinux wollte nicht (und einige andere 32bit- #distribution en ebenso), dafür hab ich #emmabuntus gefunden...Schaut mal rein!
-
Debian officially takes out i686 disk images!
Debian 13 “Trixie” has just been released today to bring many improvements and new versions of packages, such as GNOME 48, KDE Plasma 6.3, and Linux 6.15 LTS. As we have speculated earlier back last year that the i686 support was declining, further evidenced by Debian taking out the i686 kernels, our speculations made last October were made right.
Debian has joined the majority of the distros that no longer provided the i686 architecture support for kernel and for installation disks. Starting from Debian 13 “Trixie”, you can no longer use the Debian installer disks made for the i686 processors. Anyone who still uses the i686 version of Debian 12 “Bookworm” won’t be able to upgrade to Trixie.
If you’re looking into upgrading to Trixie, consider one of the following options:
- If your computer’s processor supports the 64-bit instructions (the oldest processors that support them are AMD Athlon 64 and Intel Pentium 4 Prescott, Cedar Mill, or higher), you’ll need to back up your crucial data and re-install Debian with the 64-bit installers.
- If your computer’s processor only supports 32-bit (older Intel Pentium 4, Pentium 3 or older, and AMD Athlon XP or older), you have one of the two options.
- Stay on Debian 12 “Bookworm”
- Find another Linux distribution that supports 32-bit, such as Arch Linux 32
#amd64 #Debian #Debian13 #Debian13Trixie #DebianTrixie #i386 #i686 #news #Tech #Technology #Trixie #update
-
Debian officially takes out i686 disk images!
Debian 13 “Trixie” has just been released today to bring many improvements and new versions of packages, such as GNOME 48, KDE Plasma 6.3, and Linux 6.15 LTS. As we have speculated earlier back last year that the i686 support was declining, further evidenced by Debian taking out the i686 kernels, our speculations made last October were made right.
Debian has joined the majority of the distros that no longer provided the i686 architecture support for kernel and for installation disks. Starting from Debian 13 “Trixie”, you can no longer use the Debian installer disks made for the i686 processors. Anyone who still uses the i686 version of Debian 12 “Bookworm” won’t be able to upgrade to Trixie.
If you’re looking into upgrading to Trixie, consider one of the following options:
- If your computer’s processor supports the 64-bit instructions (the oldest processors that support them are AMD Athlon 64 and Intel Pentium 4 Prescott, Cedar Mill, or higher), you’ll need to back up your crucial data and re-install Debian with the 64-bit installers.
- If your computer’s processor only supports 32-bit (older Intel Pentium 4, Pentium 3 or older, and AMD Athlon XP or older), you have one of the two options.
- Stay on Debian 12 “Bookworm”
- Find another Linux distribution that supports 32-bit, such as Arch Linux 32
#amd64 #Debian #Debian13 #Debian13Trixie #DebianTrixie #i386 #i686 #news #Tech #Technology #Trixie #update
-
Debian officially takes out i686 disk images!
Debian 13 “Trixie” has just been released today to bring many improvements and new versions of packages, such as GNOME 48, KDE Plasma 6.3, and Linux 6.15 LTS. As we have speculated earlier back last year that the i686 support was declining, further evidenced by Debian taking out the i686 kernels, our speculations made last October were made right.
Debian has joined the majority of the distros that no longer provided the i686 architecture support for kernel and for installation disks. Starting from Debian 13 “Trixie”, you can no longer use the Debian installer disks made for the i686 processors. Anyone who still uses the i686 version of Debian 12 “Bookworm” won’t be able to upgrade to Trixie.
If you’re looking into upgrading to Trixie, consider one of the following options:
- If your computer’s processor supports the 64-bit instructions (the oldest processors that support them are AMD Athlon 64 and Intel Pentium 4 Prescott, Cedar Mill, or higher), you’ll need to back up your crucial data and re-install Debian with the 64-bit installers.
- If your computer’s processor only supports 32-bit (older Intel Pentium 4, Pentium 3 or older, and AMD Athlon XP or older), you have one of the two options.
- Stay on Debian 12 “Bookworm”
- Find another Linux distribution that supports 32-bit, such as Arch Linux 32
#amd64 #Debian #Debian13 #Debian13Trixie #DebianTrixie #i386 #i686 #news #Tech #Technology #Trixie #update
-
Debian officially takes out i686 disk images!
Debian 13 “Trixie” has just been released today to bring many improvements and new versions of packages, such as GNOME 48, KDE Plasma 6.3, and Linux 6.15 LTS. As we have speculated earlier back last year that the i686 support was declining, further evidenced by Debian taking out the i686 kernels, our speculations made last October were made right.
Debian has joined the majority of the distros that no longer provided the i686 architecture support for kernel and for installation disks. Starting from Debian 13 “Trixie”, you can no longer use the Debian installer disks made for the i686 processors. Anyone who still uses the i686 version of Debian 12 “Bookworm” won’t be able to upgrade to Trixie.
If you’re looking into upgrading to Trixie, consider one of the following options:
- If your computer’s processor supports the 64-bit instructions (the oldest processors that support them are AMD Athlon 64 and Intel Pentium 4 Prescott, Cedar Mill, or higher), you’ll need to back up your crucial data and re-install Debian with the 64-bit installers.
- If your computer’s processor only supports 32-bit (older Intel Pentium 4, Pentium 3 or older, and AMD Athlon XP or older), you have one of the two options.
- Stay on Debian 12 “Bookworm”
- Find another Linux distribution that supports 32-bit, such as Arch Linux 32
#amd64 #Debian #Debian13 #Debian13Trixie #DebianTrixie #i386 #i686 #news #Tech #Technology #Trixie #update
-
Debian officially takes out i686 disk images!
Debian 13 “Trixie” has just been released today to bring many improvements and new versions of packages, such as GNOME 48, KDE Plasma 6.3, and Linux 6.15 LTS. As we have speculated earlier back last year that the i686 support was declining, further evidenced by Debian taking out the i686 kernels, our speculations made last October were made right.
Debian has joined the majority of the distros that no longer provided the i686 architecture support for kernel and for installation disks. Starting from Debian 13 “Trixie”, you can no longer use the Debian installer disks made for the i686 processors. Anyone who still uses the i686 version of Debian 12 “Bookworm” won’t be able to upgrade to Trixie.
If you’re looking into upgrading to Trixie, consider one of the following options:
- If your computer’s processor supports the 64-bit instructions (the oldest processors that support them are AMD Athlon 64 and Intel Pentium 4 Prescott, Cedar Mill, or higher), you’ll need to back up your crucial data and re-install Debian with the 64-bit installers.
- If your computer’s processor only supports 32-bit (older Intel Pentium 4, Pentium 3 or older, and AMD Athlon XP or older), you have one of the two options.
- Stay on Debian 12 “Bookworm”
- Find another Linux distribution that supports 32-bit, such as Arch Linux 32
#amd64 #Debian #Debian13 #Debian13Trixie #DebianTrixie #i386 #i686 #news #Tech #Technology #Trixie #update
-
Fedora: Vorschlag für die Entfernung von i686 zurückgezogen
https://linuxnews.de/fedora-vorschlag-fuer-die-entfernung-von-i686-zurueckgezogen/ #fedora #32bit #i686 -
Fedora: Vorschlag für die Entfernung von i686 zurückgezogen
https://linuxnews.de/fedora-vorschlag-fuer-die-entfernung-von-i686-zurueckgezogen/ #fedora #32bit #i686 -
Fedora: Vorschlag für die Entfernung von i686 zurückgezogen
https://linuxnews.de/fedora-vorschlag-fuer-die-entfernung-von-i686-zurueckgezogen/ #fedora #32bit #i686 -
Fedora: Vorschlag für die Entfernung von i686 zurückgezogen
https://linuxnews.de/fedora-vorschlag-fuer-die-entfernung-von-i686-zurueckgezogen/ #fedora #32bit #i686 -
Fedora: Vorschlag für die Entfernung von i686 zurückgezogen
https://linuxnews.de/fedora-vorschlag-fuer-die-entfernung-von-i686-zurueckgezogen/ #fedora #32bit #i686 -
Fedora 44 proposes dropping i686 support
Fedora 44, which will be released on March 31st, 2026, will mark the first Fedora Linux release without the i686 support, because this kind of support will be wiped entirely. This proposal says that the Fedora team proposes dropping the 32-bit multilib support and stopping package builds for the i686 architecture. The thread discussing the proposal can be found here.
Earlier, Fedora had stopped building installer and live images for the i686 architecture and for the package repositories, including the Linux kernel, starting from Fedora 31 released on October 8th, 2019. This proposal, if accepted, will be done in just two steps:
- Packages built for the i686 architecture are no longer included in x86_64 repositories (dropping “multilib” support, i.e. support for running 32-bit userspace on a 64-bit host).
- Packages are no longer built for the i686 architecture.
The first step will be done before the massive rebuild, and can be reversed easily if needed, since it doesn’t require retrying the bootstrap process for the reversal process. After the first step is done, the transition period will start with at least four weeks to complete the transition. During this period, packages will have to go through the adaptation process to make sure that they work correctly in the new configuration that doesn’t rely on the 32-bit multilib libraries. For example, Wine will have to enable the new WoW64 configuration.
The first step is planned to be implemented as early as possible during the Fedora 44 development cycle before the mass rebuild phase on January 14th, 2026. After that, the second step, which is irreversible, will be performed after the transition period finishes.
When this change is successfully implemented, any i686 packages will be removed upon performing the system upgrade to avoid any potential issues.
We will let you know once the FESCO approves or rejects the proposal.
-
Fedora 44 proposes dropping i686 support
Fedora 44, which will be released on March 31st, 2026, will mark the first Fedora Linux release without the i686 support, because this kind of support will be wiped entirely. This proposal says that the Fedora team proposes dropping the 32-bit multilib support and stopping package builds for the i686 architecture. The thread discussing the proposal can be found here.
Earlier, Fedora had stopped building installer and live images for the i686 architecture and for the package repositories, including the Linux kernel, starting from Fedora 31 released on October 8th, 2019. This proposal, if accepted, will be done in just two steps:
- Packages built for the i686 architecture are no longer included in x86_64 repositories (dropping “multilib” support, i.e. support for running 32-bit userspace on a 64-bit host).
- Packages are no longer built for the i686 architecture.
The first step will be done before the massive rebuild, and can be reversed easily if needed, since it doesn’t require retrying the bootstrap process for the reversal process. After the first step is done, the transition period will start with at least four weeks to complete the transition. During this period, packages will have to go through the adaptation process to make sure that they work correctly in the new configuration that doesn’t rely on the 32-bit multilib libraries. For example, Wine will have to enable the new WoW64 configuration.
The first step is planned to be implemented as early as possible during the Fedora 44 development cycle before the mass rebuild phase on January 14th, 2026. After that, the second step, which is irreversible, will be performed after the transition period finishes.
When this change is successfully implemented, any i686 packages will be removed upon performing the system upgrade to avoid any potential issues.
We will let you know once the FESCO approves or rejects the proposal.
-
Fedora 44 proposes dropping i686 support
Fedora 44, which will be released on March 31st, 2026, will mark the first Fedora Linux release without the i686 support, because this kind of support will be wiped entirely. This proposal says that the Fedora team proposes dropping the 32-bit multilib support and stopping package builds for the i686 architecture. The thread discussing the proposal can be found here.
Earlier, Fedora had stopped building installer and live images for the i686 architecture and for the package repositories, including the Linux kernel, starting from Fedora 31 released on October 8th, 2019. This proposal, if accepted, will be done in just two steps:
- Packages built for the i686 architecture are no longer included in x86_64 repositories (dropping “multilib” support, i.e. support for running 32-bit userspace on a 64-bit host).
- Packages are no longer built for the i686 architecture.
The first step will be done before the massive rebuild, and can be reversed easily if needed, since it doesn’t require retrying the bootstrap process for the reversal process. After the first step is done, the transition period will start with at least four weeks to complete the transition. During this period, packages will have to go through the adaptation process to make sure that they work correctly in the new configuration that doesn’t rely on the 32-bit multilib libraries. For example, Wine will have to enable the new WoW64 configuration.
The first step is planned to be implemented as early as possible during the Fedora 44 development cycle before the mass rebuild phase on January 14th, 2026. After that, the second step, which is irreversible, will be performed after the transition period finishes.
When this change is successfully implemented, any i686 packages will be removed upon performing the system upgrade to avoid any potential issues.
We will let you know once the FESCO approves or rejects the proposal.
-
Fedora 44 proposes dropping i686 support
Fedora 44, which will be released on March 31st, 2026, will mark the first Fedora Linux release without the i686 support, because this kind of support will be wiped entirely. This proposal says that the Fedora team proposes dropping the 32-bit multilib support and stopping package builds for the i686 architecture. The thread discussing the proposal can be found here.
Earlier, Fedora had stopped building installer and live images for the i686 architecture and for the package repositories, including the Linux kernel, starting from Fedora 31 released on October 8th, 2019. This proposal, if accepted, will be done in just two steps:
- Packages built for the i686 architecture are no longer included in x86_64 repositories (dropping “multilib” support, i.e. support for running 32-bit userspace on a 64-bit host).
- Packages are no longer built for the i686 architecture.
The first step will be done before the massive rebuild, and can be reversed easily if needed, since it doesn’t require retrying the bootstrap process for the reversal process. After the first step is done, the transition period will start with at least four weeks to complete the transition. During this period, packages will have to go through the adaptation process to make sure that they work correctly in the new configuration that doesn’t rely on the 32-bit multilib libraries. For example, Wine will have to enable the new WoW64 configuration.
The first step is planned to be implemented as early as possible during the Fedora 44 development cycle before the mass rebuild phase on January 14th, 2026. After that, the second step, which is irreversible, will be performed after the transition period finishes.
When this change is successfully implemented, any i686 packages will be removed upon performing the system upgrade to avoid any potential issues.
We will let you know once the FESCO approves or rejects the proposal.
-
Fedora 44 proposes dropping i686 support
Fedora 44, which will be released on March 31st, 2026, will mark the first Fedora Linux release without the i686 support, because this kind of support will be wiped entirely. This proposal says that the Fedora team proposes dropping the 32-bit multilib support and stopping package builds for the i686 architecture. The thread discussing the proposal can be found here.
Earlier, Fedora had stopped building installer and live images for the i686 architecture and for the package repositories, including the Linux kernel, starting from Fedora 31 released on October 8th, 2019. This proposal, if accepted, will be done in just two steps:
- Packages built for the i686 architecture are no longer included in x86_64 repositories (dropping “multilib” support, i.e. support for running 32-bit userspace on a 64-bit host).
- Packages are no longer built for the i686 architecture.
The first step will be done before the massive rebuild, and can be reversed easily if needed, since it doesn’t require retrying the bootstrap process for the reversal process. After the first step is done, the transition period will start with at least four weeks to complete the transition. During this period, packages will have to go through the adaptation process to make sure that they work correctly in the new configuration that doesn’t rely on the 32-bit multilib libraries. For example, Wine will have to enable the new WoW64 configuration.
The first step is planned to be implemented as early as possible during the Fedora 44 development cycle before the mass rebuild phase on January 14th, 2026. After that, the second step, which is irreversible, will be performed after the transition period finishes.
When this change is successfully implemented, any i686 packages will be removed upon performing the system upgrade to avoid any potential issues.
We will let you know once the FESCO approves or rejects the proposal.
-
Demoting i686-PC-windows-gnu to Tier 2
https://blog.rust-lang.org/2025/05/26/demoting-i686-pc-windows-gnu/
#HackerNews #Demoting #i686-PC-windows-gnu #to #Tier #2 #RustProgramming #WindowsDevelopment #i686 #Tier2
-
Demoting i686-PC-windows-gnu to Tier 2
https://blog.rust-lang.org/2025/05/26/demoting-i686-pc-windows-gnu/
#HackerNews #Demoting #i686-PC-windows-gnu #to #Tier #2 #RustProgramming #WindowsDevelopment #i686 #Tier2
-
Demoting i686-PC-windows-gnu to Tier 2
https://blog.rust-lang.org/2025/05/26/demoting-i686-pc-windows-gnu/
#HackerNews #Demoting #i686-PC-windows-gnu #to #Tier #2 #RustProgramming #WindowsDevelopment #i686 #Tier2
-
Demoting i686-PC-windows-gnu to Tier 2
https://blog.rust-lang.org/2025/05/26/demoting-i686-pc-windows-gnu/
#HackerNews #Demoting #i686-PC-windows-gnu #to #Tier #2 #RustProgramming #WindowsDevelopment #i686 #Tier2
-
¡Me caigo y me levanto!
:catjoy: :CrabVibe: :bunbounce: :aplauso: :crabsb: :flower: :frogwow: :madotsuki: :roier: :smugdance:
#Windows #WindowsXP #WindowsVista #Windows7 #Windows8 #Windows10 #WindowsServer #WindowsServer2003 #GNU #Linux #GNULinux #GNU_Linux #32Bit #32Bits #i386 #i486 #i586 #i686 #PAE #PhysicalAddressExtension #ChatGPT
-
¡Me caigo y me levanto!
:catjoy: :CrabVibe: :bunbounce: :aplauso: :crabsb: :flower: :frogwow: :madotsuki: :roier: :smugdance:
#Windows #WindowsXP #WindowsVista #Windows7 #Windows8 #Windows10 #WindowsServer #WindowsServer2003 #GNU #Linux #GNULinux #GNU_Linux #32Bit #32Bits #i386 #i486 #i586 #i686 #PAE #PhysicalAddressExtension #ChatGPT
-
¡Me caigo y me levanto!
:catjoy: :CrabVibe: :bunbounce: :aplauso: :crabsb: :flower: :frogwow: :madotsuki: :roier: :smugdance:
#Windows #WindowsXP #WindowsVista #Windows7 #Windows8 #Windows10 #WindowsServer #WindowsServer2003 #GNU #Linux #GNULinux #GNU_Linux #32Bit #32Bits #i386 #i486 #i586 #i686 #PAE #PhysicalAddressExtension #ChatGPT
-
¡Me caigo y me levanto!
:catjoy: :CrabVibe: :bunbounce: :aplauso: :crabsb: :flower: :frogwow: :madotsuki: :roier: :smugdance:
#Windows #WindowsXP #WindowsVista #Windows7 #Windows8 #Windows10 #WindowsServer #WindowsServer2003 #GNU #Linux #GNULinux #GNU_Linux #32Bit #32Bits #i386 #i486 #i586 #i686 #PAE #PhysicalAddressExtension #ChatGPT
-
¡Me caigo y me levanto!
:catjoy: :CrabVibe: :bunbounce: :aplauso: :crabsb: :flower: :frogwow: :madotsuki: :roier: :smugdance:
#Windows #WindowsXP #WindowsVista #Windows7 #Windows8 #Windows10 #WindowsServer #WindowsServer2003 #GNU #Linux #GNULinux #GNU_Linux #32Bit #32Bits #i386 #i486 #i586 #i686 #PAE #PhysicalAddressExtension #ChatGPT
-
-
-
-
-
-
All hardware is supported, there are no known bugs and you even get OTA updates once a month including the latest security patches from #Google. At 7 years old, it's still a perfectly usable daily driver.
But what about the #Teclast tablet? It got stuck on #Android5.1 right out of the gate, only receiving a few patch updates. And you can see why: It sports a rather esoteric #Intel #i686 (32-bit x86) SoC and being a very cheap device, it was not economically feasible to keep it updated.
[2/4]
