home.social

#i686 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #i686, aggregated by home.social.

fetched live
  1. 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, […]

    novatopflex.wordpress.com/2026

  2. 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

  3. Fedora 44 proposes dropping i686 support

    The proposal has been officially withdrawn, citing that Fedora 44 targeting is too early.

    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 #Fedora44 #i686 #news #Tech #Technology #update
  4. 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]

  5. Is there any #Linux #Distro that specifically caters to older #i686 computers/laptops as a first class citizen?

  6. Trying to build an #i686 install iso for #NixOS

    It's been here for almost 6 hours. 3 Cores @ 100% utilization.

  7. Debian Trixie no longer provides 32-bit kernel

    Debian Trixie now officially withdraws support for the Linux 32-bit kernel, starting with kernel version 6.11.2. An upload of this version of the kernel was done today on October 6th, signifying that the i386 version of the kernel will no longer be available on Debian Trixie. The kernel maintainers and the release team have, therefore, concluded this support by posting this to the mailing list:

    This is a new upstream version with, as usual, many changes.
    
    Some significant changes to the package are:
    
      * [i386] Stop building kernel packages
      * udeb: Fold i2c-modules, efi-modules, leds-modules, acpi-modules,
        fancontrol-modules, srm-modules, and crc-modules into kernel-image
      * udeb: Fold event-modules and mouse-modules into input-modules
    
    The udeb changes will require some changes to package lists on the
    installer side.
    

    This means that all the i386 computers, even the most recent 32-bit only processors before the inception of 64-bit support, such as AMD Athlon XP Series and Intel Pentium 3, will no longer be able to upgrade to Debian Trixie from Debian Bookworm. However, some of the packages will remain to support i386 until either the upstream developers (that is, the real owner of the projects) or the downstream developers (that is, people that package a software for Debian) finally drop support.

    A bit unrelated, the udeb packaging has undergone two significant changes, which is to migrate 7 modules – that is, i2c-modules, efi-modules, leds-modules, acpi-modules, fancontrol-modules, srm-modules, and crc-modules – into the kernel-image udeb and two modules – that is, event-modules and mouse-modules – into the input-modules udeb.

    The full changelogs that lists what happened to the Linux package is as follows:

    A fuller list of changes in the package:
    
      * Properly disable common headers packages
      * [x86] Enable IPU6 MIPI drivers for Intel Alder Lake laptops
        (Closes: #994449, #1074441, #1060262, #1078170)
      * Drop "module: Avoid ABI changes when debug info is disabled" as we no
        longer try to maintain a module ABI
      * d/rules.real: Unset KBUILD_HOSTCFLAGS etc. instead of overriding to be
        empty
      * d/rules.d/Makefile.inc: Add scripts/include to header include path
      * d/config: Update with the help of kconfigeditor2
      * perf tools: Pass EXTRA_CFLAGS through to libbpf build again
      * d/control: Drop versions from Build-Depends that are satisfied since buster
      * d/control: Fix profiles for Build-Depends on bison, cpio, flex, xz-utils
      * d/control: Move bison, cpio, flex, xz-utils to Build-Depends-{Arch,Indep}
      * Compile with gcc-14 on all architectures
      * [arm64] Include modules for Lenovo Yoga C630 and Lenovo Miix 630 into D-I
        packages.
      * [riscv64] Enable STARFIVE_STARLINK_CACHE and PCIE_STARFIVE_HOST.
      * [riscv64] Enable PHY_STARFIVE_JH7110_DPHY_TX as a module.
      * [riscv64] Enable CLK_SOPHGO_SG2042_PLL, CLK_SOPHGO_SG2042_CLKGEN and
        CLK_SOPHGO_SG2042_RPGATE as modules.
      * [amd64] tools/arch/x86/intel_sdsi: Add intel-sdsi package for Intel SDSi
        provisioning tool (Closes: #1059362)
      * [amd64] drivers/accel/habanalabs: Enable DRM_ACCEL_HABANALABS
        (Habana's AI Processors)
      * [amd64] drivers/accel/ivpu: Enable DRM_ACCEL_IVPU (Intel NPU, formerly
        called Intel VPU) (Closes: #1079170)
      * [x86] Enable GPIO_WHISKEY_COVE, INTEL_BXT_PMIC_THERMAL as module.
      * [riscv64] udeb: Add rtc-modules to Provides of kernel-image
      * [riscv64] udeb: Ship mtd in kernel-image, drop mtd-core-modules and
        add it to to Provides of kernel-image.
      * [arm64] udeb: Add kernel modules to get USB/SATA/PCIe working on Rockchip
        RK3588
      * [arm64] Enable modules for MT8186 Chromebooks
      * udeb: Move i2c-hid-of-goodix module to fb-modules
      * [arm64] drivers/gpu/drm/panthor: Enable DRM_PANTHOR as module
      * [arm64] Enable SC_CAMCC_8280XP as module, camera clock controller on
        Lenovo ThinkPad X13s laptop.
      * [arm64] Enable SC_GCC_8180X, SM_GPUCC_8150, INTERCONNECT_QCOM_SC8180X and
        PINCTRL_SC8180X as modules in order to support Lenovo Flex 5G laptops.
      * [arm64] Include modules for Lenovo Flex 5G (Snapdragon SC8180X)
      * [arm64] enable Qualcomm X Elite modules
      * [arm64] Include modules for Qualcomm X Elite laptops
      * [arm64] Enable additional modules for rk356x devices
      * [arm64] Update rk3588 platform support
      * [rt] Update to 6.11-rt7
      * [riscv64] Enable INPUT_MISC (Closes: #1079501).
      * Revert "Make linux-libc-dev provide all cross packages".
      * [amd64] drivers/crypto/intel/iaa: Enable CRYPTO_DEV_IAA_CRYPTO
        (IAA Compression Accelerator Crypto Driver) (Closes: #1079272)
      * [powerpc] Explicitly disable CRASH_DUMP on 32-bit (Closes: #1079755)
      * [x86] ACPI: Enable ACPI_EC_DEBUGFS as module (Closes: #980555)
      * [i386] Stop building kernel packages
      * rtla: Switch to out-of-tree build
      * rtla: Enable verbose build
      * rtla: Build with dpkg's recommended compiler flags (regression in 6.9)
      * rtla: Fix missing debug symbols
      * rtla: Disable LTO
      * rtla: Set LD correctly for cross-build
      * objtool: Build with dpkg's recommended compiler flags (regression in
        6.5.1-1¬exp1)
      * [loong64] Enable kernel support for LBT instructions.
      * [loong64] Enable KVM and para-virt support.
      * [loong64] Enable USB EHCI and OHCI host support.
      * mm/damon: Enable DAMON, DAMON_VADDR, DAMON_PADDR, DAMON_SYSFS,
        DAMON_RECLAIM, DAMON_LRU_SORT
      * [x86] linux-cpupower: Add intel-speed-select command (Closes: #1036714)
      * drivers/net/wireless: Support some Wi-Fi 7 devices: enable ATH12K,
        MT7925E, MT7925U, MT7996E and RTW89_8922AE as modules (Closes: #1081114)
      * mm: set CONFIG_ZONE_DEVICE=y on arm64, loong64, ppc64, ppc64el, and
        riscv64, not only amd64. FS_DAX depends on it.
      * Revert "perf tools: Use $KBUILD_BUILD_TIMESTAMP as man page date" which is
        no longer useful
      * Fix some reproducibility issues (Closes: #1033663)
      * d/rules.real: Try harder to set the locale to C.UTF-8
      * udeb: Delete obsolete rtc-modules from kernel-image Provides
      * udeb: Fold i2c-modules into kernel-image (fixes FTBFS on alpha, sparc64)
      * udeb: Fold event-modules and mouse-modules into input-modules
      * udeb: Fold efi-modules into kernel-image
      * [arm64,armhf] udeb: Fold leds-modules into kernel-image
      * [amd64] udeb: Fold acpi-modules into kernel-image
      * [powerpc*] udeb: Fold fancontrol-modules into kernel-image
      * [alpha] udeb: Fold srm-modules into kernel-image
      * udeb: Fold crc-modules into kernel-image
      * [arm64,armhf] udeb: Add all watchdog drivers to kernel-image
        (Closes: #1081550)
      * Remove d/b/genorig.py in favour of uscan
      * net/netfilter/ipvs: Enable IP_VS_TWOS as module (Closes: #1082903)
      * libcpupower: Update symbols file for changes in 6.11.2-1~exp1.
      * [arm64] Enable drivers for AM64 SoC on HummingBoard-T (Closes: #1081837)
      * [arm64] udeb: Add kernel modules for I2C, USB and Ethernet on TI AM64
      * [arm64] udeb: Add kernel modules for RTC
      * [amd64] arch/x86: Enable CONFIG_ADDRESS_MASKING
        (Linear Address Masking support) (Closes: #1082296)
      * [armhf] Enable support for GPIOs, i2c, spi and G-sensor for Terasic's
        DE10-nano board.
    

    In the event that the i386 packages of the Linux kernel are not removed in the final release of Trixie, the next version of Debian will not support i386, or, at least, its kernel. You can see the package here, but it will take hours for the changes to propagate.

    A good alternative to Debian in your i386 systems is Arch Linux 32, but it’s better to just upgrade your systems to 64-bit if your processor allows.

    #1033663 #1036714 #1059362 #1060262 #1074441 #1078170 #1079170 #1079272 #1079501 #1079755 #1081114 #1081550 #1081837 #1082296 #1082903 #32Bit #980555 #994449 #Architecture #Debian #Debian13 #DebianTrixie #i386 #i686 #Linux #Technology #Trixie #update
  8. Ну чому не можна було дати тільки одну назву для одної архітектури. У процесорів для настільних ПК є 32-bit й 64-bit архітектур які називаються, або x86 і x86_64, або i386 і amd64 відповідно. А ще іноді 32-bit називають i686.

    Проблема ж у, тому що у різних місцях може прийматись тільки один варіант і важко запамʼятати де який.

    Для прикладу у репозиторіях Arch GNU/Linux пакунки мають мітку x86_64 архітектуру, а у Debina GNU/Linux - amd64.

    Перевірити архітектуру в терміналі можна кількома способами.

    1. Uname
     $ uname -m
     x86_64
    
    1. dpkg (debian)
     $ dpkg --print-architecture
     amd64
    

    #процесори #архітектури #cpu #processors #arch #architecture #x86 #i386 #i686 #x86_64 #amd64 #uname #dpkg #repos #linux

  9. naturally my llong/ullong patch doesn't work on #i686 because it's (probably) just reading a register and I don't know how u64s are passed on i686 (do they just spill? register pair? depends™?) and google is giving me shit because im stupid. turning my #abi #fiend card in at the reception :/

  10. Any suggestion about Gentoo Linux?
    I know Gentoo, but haven't used it that much.

    Is Gentoo can be reliable for low spec's machine as long the program code isn't sucks right?

    I want to use an old machine (2C/2T CPU with 3GB of RAM) to become reliable in my own production but still keep relevant to the newest certain software that I use.

    I'm, okay to wait for the compilation as long it doesn't take for hours of time

    #Gentoo #Linux #suckless #lowtechhardware #x86 #x86_64 #i686 #Funtoo

  11. @YesIKnowIT PsychOS has i686, i486, and i386 options, though the i386 option is a desktop environment for DOS rather than a full-blown operating system... psychoslinux.gitlab.io #linux #i686 #i486 #i386 #dos

  12. Just a quick reminder, I have a GNU/Linux distribution called "PsychOS" for running on older hardware (i686) and will hopefully soon release "PsychOS486" for those with even older hardware (i486DX/i586/i686), as long as you have 32MB of RAM for a console and 64MB for a GUI desktop, but 128MB would be much better. psychoslinux.gitlab.io #GNU #Linux #FOSS #PsychOS #i486 #i586 #i686 #32bit