LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   " Is it really needed in 2012 to support using a non-SMP i486 kernel on Slackware? " (https://www.linuxquestions.org/questions/slackware-14/is-it-really-needed-in-2012-to-support-using-a-non-smp-i486-kernel-on-slackware-942248/)

yars 05-02-2012 03:52 PM

Quote:

Originally Posted by TobiSGD (Post 4667891)
And how are you building a non-SMP kernel if your machine isn't able to run the SMP kernel?

On what mashines is older than Pentium 4 (Socket 478 - Prescott, if I am not mistaken) can run the SMP-kernel?

TobiSGD 05-02-2012 06:14 PM

The SMP kernel in its -current form can run on any CPU that does support PAE. So anything newer then Pentium Pro (except the Banias Pentium Ms) and Athlon can run that kernel. That this kernel supports SMP does not mean that it need multi-core, multi-CPU or Hyperthreading machine.

yars 05-03-2012 04:17 AM

Quote:

Originally Posted by TobiSGD (Post 4668885)
The SMP kernel in its -current form can run on any CPU that does support PAE. So anything newer then Pentium Pro (except the Banias Pentium Ms) and Athlon can run that kernel. That this kernel supports SMP does not mean that it need multi-core, multi-CPU or Hyperthreading machine.

Then, the more it makes sense to abandon the non-SMP kernel. I think, a very old machines are not so much to worry about compatibility with them.

TobiSGD 05-03-2012 04:48 AM

I personally think that Slackware should not drop support for the Pentium Ms and the K6-II(I) CPUs (and may be some of the VIA CPUs, I can't find information about the status of PAE on those chips). Slackware is well known for running without problems on older hardware, and many people still use those machines, especially in countries were newer hardware is expensive and money is in short supply. Dropping the non-SMP kernel would basically mean dropping recent Slackware for those people.

Of course a simple work-around for this situation would be to not enable PAE by default in the SMP kernel and then drop the non-SMP one. A user that needs PAE can easily compile a kernel with PAE enabled. That is simply not possible the other way around.

Or am I missing something? Question: Why is PAE enabled in the newer SMP kernels?

jtsn 05-03-2012 06:12 AM

The main problem is, that a PAE capable kernel can't boot on a Non-PAE machine and a Non-PAE kernel can't use more than 4 gigabytes of memory.

Actually that's a design flaw in the Linux kernel and must be fixed upstream. PAE should be detected at runtime and activated if available.

GazL 05-03-2012 06:29 AM

Quote:

Originally Posted by jtsn (Post 4669288)
The main problem is, that a PAE capable kernel can't boot on a Non-PAE machine and a Non-PAE kernel can't use more than 4 gigabytes of memory.

While the first of those is a problem, the second is merely an inconvenience. I'm with Tobi' smp-enabled/pae-disabled default kernel looks to be the best option to get everyone up and running. Those who need PAE can enable it themselves post-install.

rigelan 05-03-2012 07:11 AM

Quote:

Originally Posted by kingbeowulf (Post 4665777)
Correct. If you want Nvidia you need to blacklist nouveau regardless of kernel, or compile a new kernel.

Perhaps this is part of the "Your mileage may vary" claim. I had tried and tried to install NVIDIA, but NOUVEAU was always being loaded with the huge, preventing the proprietary from being installed. Blacklisting seemed to never work for me. Then I tried the generic, and low and behold the blacklisting worked. Perhaps I was missing something - but this was how I got it to work for my machines.

yars 05-03-2012 09:17 AM

Quote:

Originally Posted by jtsn (Post 4669288)
The main problem is, that a PAE capable kernel can't boot on a Non-PAE machine and a Non-PAE kernel can't use more than 4 gigabytes of memory.

On a very old machines, such as Pentium-Pro based, PAE is not needed for works. Also, find the parts for these machines every day is all more is difficult.

jheengut 02-09-2013 04:52 AM

Quote:

Originally Posted by TobiSGD (Post 4665855)
Dropping the non-SMP kernel would currently prevent anyone from installing Slackware on Pentium M machines, since the SMP kernel has PAE enabled by default, which is not supported by Pentium Ms with Banias core.
So the non-SMP kernel is at least necessary to build a SMP kernel with PAE disabled.

that's true i just installed slack on a friends machine since it is the only kernel without pae that could be used.

Celyr 02-09-2013 11:53 AM

Quote:

Originally Posted by jtsn (Post 4669288)
The main problem is, that a PAE capable kernel can't boot on a Non-PAE machine and a Non-PAE kernel can't use more than 4 gigabytes of memory.

Actually that's a design flaw in the Linux kernel and must be fixed upstream. PAE should be detected at runtime and activated if available.

Too much overhead :o

WiseDraco 02-09-2013 12:23 PM

i personally not use hardware running on slack, who not be minima of i686
on other hand - i see, there is be folks, who used old i586 hardware with current slack.
i think, then we can see, what bonus we have if going to i686 smp only - there is huge gap in performance? or in what? if we have a significant leap from going to i686 kernel, when we have consider that. if no - i cannot see, why not sit on an old tradition...?

Didier Spaier 02-09-2013 01:05 PM

Quote:

Originally Posted by WiseDraco (Post 4887730)
if no - i cannot see, why not sit on an old tradition...?

As a reminder the question is asked by Pat in a file called BROKEN.TXT in /extra. This doesn't say why but I would tend to guess what he had in mind: less maintenance work and/or less payload for the ISO's and/or the installer, possibly making room for other stuff (only a guess, of course). Meanwhile, I also saw this post which you could interpret as "we will keep non-SMP" -- or not as this is not explicitly stated.

Anyway it amazes what how Pat's "offhand comments" (in his own words) can (certainly unwillingly) spread FUD in our very sensitive community. Or trigger what we call here "une tempête dans un verre d'eau" :)

As a side note I find sometimes difficult to really understand if reactions from us are expected or not, probably because English is not my native language.

grindstone 02-09-2013 10:04 PM

It's about the pain, isn't it--compatibility. I was going to say that, if other-than-very-painful, please retain non-smp compatibility if-only for memory reasons.

Up until a month ago, I had Actual i486 & Ppro industrial pc's running it. Purely for space reasons, threw it all out (after a protracted moment of silence and some mental rhapsodizing about damned kids not appreciating kilobytes) and replaced it all with wall-wart-driven "gadgets".

It's not just another lame Geezer-nostalgia rant, more a commentary on a lost decade of an economy. The industrial stuff...well few have had anything to spend on capital equipment for a Good While (tm).

Arguably a narrow use-case, but I'd bet it's larger than people think. New software doesn't support old hardware. Old hardware comes as part of 6- and 7-figure machinery and equipment. Retrofitting/upgrades are within 25% of all-new hardware (aka prohibitive to financial people seeking ever-faster paybacks).

Okay, it turns-out this was a Geezer-rant. It's just a reaction from having been through this pinch a few times before in other forms. Heavy machines and equipment last for decades. Talking to them is ever-more-difficult, but that's not Pat's problem and it's not any of the Slackware Team's problem. I have nothing but gratitude for them.

If i486 survives another rev--great! After that, call it a nice-to-have and let the world move-on (but light a candle first and scream "Gawd save the Queen!", will you?)

jtsn 02-11-2013 01:59 AM

Quote:

Originally Posted by Celyr (Post 4887714)
Too much overhead :o

Please explain.


All times are GMT -5. The time now is 01:32 AM.