Description of problem: Unable to boot Fedora 30 on a hardware where Fedora 24 was running fine (AMD Barton 2800+) Version-Release number of selected component (if applicable): I don't know since the system doesn't boot, but it apparently contains libsystemd-shared-241.so How reproducible: 100% Steps to Reproduce: 1. Boot Fedora-Xfce-Live-i386-30-1.2.iso from DVD Actual results: System locked up in initramfs (dracut-049-26.git20181204.fc30): systemd[1]: No hostname configured. systemd[1]: Set hostname to <localhost>. traps: systemd[1] trap invalid opcode ip:b7c977ca sp:bf95a270 error:0 in libsystemd-shared-241.so[b7bc6000+16c000] Core dump to |/bin/false pipe failed systemd[1]: Caught <ILL>, core dump failed (child 189, code=killed, status=4/ILL). systemd[1]: freezing execution. Expected results: Boots fine Additional info: CPU: AMD Barton 2800+
Systemd itself does not do anything special, it just uses the default distro flags. I think this is an effect of https://fedoraproject.org/wiki/Changes/Update_i686_architectural_baseline_to_include_SSE2. https://en.wikipedia.org/wiki/List_of_AMD_Athlon_XP_microprocessors#Athlon_XP_%22Barton%22_(Model_10,_130_nm) seems to say that AMD Barton does not support SSE2. I think it's unlikely that this can be fixed: systemd just happens to be one of the first programs started, but other programs would crash the same way.
Correct, the AMD Athlon XP 2800+ does not support SSE2 (only SSE), so it is no longer supported by Fedora.
Yep, sorry. Your hardware is simply not supported by Fedora anymore. You'll need to switch to some other distribution on it. I know this is disappointing, but we can't support everything.
Thanks for pointing out this change which I wasn't aware of. This is sad news. Does it make sense to keep releasing e.g. Fedora-Xfce-Live-i386-30-1.2.iso if it is built from software compiled for new processors only, with "x86_64 systems" and "multi-lib RPMs" in mind? I'm affraid that reasons given for the mentioned change don't apply to i386 ISOs with lightweight spins like Xfce...
It makes some limited sense. Programs running in 32bit mode use less memory, so they can be useful even for hardware which has 64bit. And people still use 32 bit images in VMs and such. There have been various noises to drop support for x86 completely. So far this hasn't happened, but it's just a question of time. The truth is that almost all developers use and have been using 64-bit hardware exclusively for many years, so there's almost no testing and bug-fixing done for 32-bit intel. The support is very weak and will only become worse over time.