ok so I got this old core 2 duo machine, you know, a modern x64 intel computer. the Fedora 43 live usb doesn't boot on it, grub says something has a bad sector. but the same live usb works just fine on another computer, and i reimaged the usb drive just in case and it's still misbehaving. I don't think I'm gonna get this working, but I would be interested to know if Fedora dropped backwards compat with non-uefi systems or something like that
EDIT: fedora 43 supports x86_64_v1
alright, I've successfully managed to bring the Compiano Forte up to the latest Ubuntu Studio 24 Point Whatever and sound still works even, and I am completely stuffed with ï½¢thanksgivingï½£ just positively filled to the brim
I got clang 20 installed on this machine, which is important to building mollytime, but, uh huuuuuh, Ubuntu Studio 24 Point Whatever doesn't seem to have SDL3 available
glxinfo -B reports this machine has hardware accelerated 3D graphics supporting a maximum GL core version of 0.0 (and compat version of 2.1) so I guess for all intensive porpoises this machine does not in fact have hardware accelerated 3D graphics anymore
I didn't check, but I'm guessing SDL picked the software rendering pipeline, because the UI was a bit sluggish. however! all of the patches I tried played just fine, so the Core 2 Duo can handle the synth pipeline which is the important part
@halcy there's basically no good reason for this machine to be obsolete, except that infosec researchers are keeping the trash gyre alive with shit like this
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown
@c0dec0dec0de That's only 7/12 keys, though. I hear you can also write C#, for instance.
@aeva That's what I do! Compile binpkgs on a modern (from 2013) PC and then install them on 20-year-old x86 hardware. Works great for me, though lack of SSE2 requires me to patch some softwares on my own, Gentoo didn't do it for me.
(But I can't help you with Mollytime because I've no idea what that is and it's not in the Gentoo repositories, sorry)
@vaporeon_ I'm not using any special cpu intrinsics, so but the code assumes a 64 bit CPU. I don't know of any reason why a x64v1 CPU would not be able to use it.
If the 64bit constraint were worked around, the great reliance on 64 bit floating point math probably limits how far this can scale down.
@aeva In principle, I ran Gentoo on an Intel Core 2 Duo Mac Mini until that computer broke, so for a Core 2 Duo, you don't even need a second modern computer for compiling (though that would be faster), you can just install and use Gentoo.
I can confirm that Gentoo works on BIOS systems no problem, I've personally installed it on multiple systems that only have BIOS.
It has Clang 20 and libsdl3.
Although, if you don't actually want Gentoo, you just want your stuff to work: did you test yet whether the latest Debian boots from that USB stick? I remember installing it successfully on BIOS-only hardware a few years ago, but the latest version (Debian 13, which is the only one that has SDL3).
Unfortunately can't test it for you because they dropped 32-bit x86 support in that latest version
)
@aeva Good luck! (Let me know if you want any advice, I like talking about Gentoo, I don't know whether you've installed Gentoo before or not and I don't want to be condescending by explaining things that you already know)
In case it helps, I followed this article to set up building binary packages on the faster machine and installing them on the slower machine: https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart
Problem is that that requires an existing Gentoo machine, though... Or doing some stuff with Docker on a machine that runs some other distro, I guess
But compiling on a Core 2 Duo itself is 100% possible if you're OK with letting big compiles (like Clang and GCC) run overnight
@vaporeon_ I used to main gentoo, but that was probably around 2005 give or take. The main thing I remember is foss project maintainers tend to get really annoyed when you report bugs that were caused by building with -O3 😅
I don't mind having multi day long compilation jobs to install or update packages, I know to plan accordingly. I wouldn't mind pointers on how to get the most out of modern gentoo though.
@aeva Coincidentally, I recently installed Gentoo from 2007 on an old computer for retrocomputing purposes; the main difference I noticed was that some of the paths are different (and the ebuild format also is incompatible with newer ebuilds), but otherwise I could use it just like I use modern Gentoo
So I don't have useful advice here, but I think you'll be fine...
The latest revisions of the Gentoo Handbook apparently suggest XFS as the default filesystem now and I genuinely don't know why (they didn't do it in 2021, this is a very recent change), but ext4 is still completely fine, I use ext4 on all computers except for the "storage server" (actually a normal PC with two giant hard drives in it) with ZFS
My CFLAGS are just -O2 -pipe -march=native -fpermissive because I'm boring (and also because I'm not sure how to measure whether higher optimisations actually made the program run better or whether they just increased code size for nothing), plus I used app-portage/cpuid2cpuflag to set CPU_FLAGS_X86 in /etc/portage/make.conf to all the CPU flags that the processor supports (it'll run without that, but some programs like ffmpeg can enable more optimisations if they know which CPU flags are available)