Linux kernel will soon drop ~~i386~~ (32-bit) support

3 years ago by activistPnk to c/permacomputing

The article title is “Debian Likely Moving Away From i386 In The Near Future” but according to the article Debian will drop i386 support because it will be dropped from the kernel. Seems like bad news for permacomputing folks.

(EDIT) modified the title since it seems more accurate to say that 32-bit support is being dropped. (reference)

bigbadmoose 9 points 3 years ago

You're using a 386? Dont make me laugh

path: 0 6269383, hotness: undefined, score: 9, children: 10
Ephera 9 points 3 years ago

This isn't talking about the microprocessor model from 1985, if that's what you're thinking.

Rather, that microprocessor was the first to introduce the x86 32-bit architecture, which is getting discontinued here.
So, that includes some hardware still manufactured in the early 2000s...

path: 0 6269383 6270100, hotness: undefined, score: 9, children: 6
Aggravationstation 6 points 3 years ago

Yea I have a 32 bit machine from 2007.

path: 0 6269383 6270100 6274036, hotness: undefined, score: 6, children: 3
activistPnk 3 points 3 years ago

That’s quite interesting because the spy chips¹ began in 2008ish. So people who avoid the spy chips are losing options. There may not be many 64bit machines that pre-date the spy chips (edit: there might be a 5-year span of 64-bit AMD spy-free chips). I’m lucky to have a machine from 2008 just before the anti-consumer chips came out. IIUC there is only one modern architecture that avoids the spy chips: the IBM Power11.

1: spy chips → Intel’s Management Engine/ARM trustzone/AMD’s Platform Security Processor; tech that is anti-non-corporate consumer

path: 0 6269383 6270100 6274036 6276446, hotness: undefined, score: 3, children: 2
tallship 1 point 3 years ago

Um.... Are you referring to the most ubiquitous OS worldwide nowadays... Minix?

path: 0 6269383 6270100 6274036 6276446 6299382, hotness: undefined, score: 1, children: 1
purplemonkeymad 3 points 3 years ago

No, that is not what it means. i386 is specifically the set of instructions that the 386 introduced. Later processors from intel added additional instructions, those were rolled into i686 as a set. i686 contains i386 so it can still run programs that target that, but a 386 can't run a i686 program.

i386 and i686 are both x86 32 bit instruction sets.

What is happening is that the kernel will no longer support i386 as a target. So any processor that does not support at least i686 will stop working. This is basically anything before around a pentium 3 (iirc might be wrong about exact CPU.) Vista era computers should not be effected.

The confusing part is that some distros have already dropped all 32bit for other reasons, but it would mean it would be hard for distros going forward to support 386 era processors.

path: 0 6269383 6270100 6275513, hotness: undefined, score: 3, children: 1
GenderNeutralBro 2 points 3 years ago

The Linux kernel dropped i386 support back in 2012: https://www.phoronix.com/news/MTI0OTg

I think any reference to i386 nowadays really refers to i686. Debian, for example, officially dropped support even for i586 with Stretch back in 2017: https://web.archive.org/...

So I think the linked article really does mean that they are dropping all 32-bit x86 support.

path: 0 6269383 6270100 6275513 6286230, hotness: undefined, score: 2, children: 0
CameronDev 6 points 3 years ago

It pairs well with my RTX4090 :D

path: 0 6269383 6269634, hotness: undefined, score: 6, children: 1
Klear 3 points 3 years ago

I think your GPU might be bottlenecking you.

path: 0 6269383 6269634 6273700, hotness: undefined, score: 3, children: 0
RandAlThor 2 points 3 years ago

Your windows boots up in what, a day and a half?

path: 0 6269383 6270009, hotness: undefined, score: 2, children: 0
Draconic_NEO 3 points 3 years ago

The CADT model at it's finest. It's funny because Linux is considered the de facto choice for legacy hardware because it runs so well on it, or at least used to. The fact is the development model used by distros (and apparently also the Linux kernel as well) is absolutely awful, and it inevitably hurts movements that depend on it such as Permacomputing.

path: 0 6288394, hotness: undefined, score: 3, children: 0
lmemsm 2 points 5 months ago

At least operating systems like FreeDOS and NetBSD will still be supporting 32 bit platforms for a while. Also, ELKS is incredible if you're interested in 16 bit Linux.

path: 0 23863200, hotness: undefined, score: 2, children: 1
activistPnk 1 point 5 months ago

Thanks for the feedback.. that’s good news considering I recently bought a 2nd-hand NAS that’s 32bit.

path: 0 23863200 23869393, hotness: undefined, score: 1, children: 0
feoh 1 point 3 years ago

So it's interesting reading all the folks talking about permacomputing and the like.

And I think there's merit to keeping those architectures around.

But let's turn this on its head, shall we? Where do we get the people who still have that hardware who are willing to actively take part in Linux kernel development?

Like, to become facile enough with the process, tools and codebase to be able to bear the load of writing new security patches as vulnerabilities are found?

It's a hard problem. The number of people actively contributing to Linux is large in aggregate but VANISHINGLY small when it comes to any particular area of interest.

path: 0 6296961, hotness: undefined, score: 1, children: 0
Sandra 1 point 3 years ago
path: 0 6273695, hotness: undefined, score: 1, children: 0
milicent_bystandr 1 point 3 years ago

bad news for permacomputing folks

it can still be custom compiled in, right?

path: 0 6333044, hotness: undefined, score: 1, children: 1
activistPnk 1 point 3 years ago

I don’t have a deep knowledge of the kernel to know if it’s as easy as simply adding in a separate module.

path: 0 6333044 6347816, hotness: undefined, score: 1, children: 0
permacomputing
permacomputing

@lemmy.sdf.org

login for more options
370
22
1

"In a time where computing epitomizes industrial waste, permacomputing encourages the maximizing of hardware lifespans, minimizing energy use and focussing on the use of already available computational resources." (from the permacomputing wiki)

See also: !permacomputing@slrpnk.net

go to feed...