LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-10-2018, 10:29 PM   #1
Ne01eX
Member
 
Registered: Mar 2018
Location: Ekaterinburg region, Ural, Russian Federation
Distribution: Slackware, RTK GNU/Linux
Posts: 173

Rep: Reputation: 22
Question Does anyone use the original config "generic" / "generic-smp"?


Subj. Without anyone modification.
 
Old 04-11-2018, 01:29 AM   #2
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,727

Rep: Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740Reputation: 740
https://en.wikipedia.org/wiki/Symmetric_multiprocessing

from some Slackware release announcement

Quote:
There are two kinds of kernels in Slackware. First there are the
huge kernels, which contain support for just about every driver in the
Linux kernel. These are primarily intended to be used for installation,
but there's no real reason that you couldn't continue to run them after
you have installed. The other type of kernel is the generic kernel, in
which nearly every driver is built as a module. To use a generic kernel
you'll need to build an initrd to load your filesystem module and
possibly your drive controller or other drivers needed at boot time,
configure LILO to load the initrd at boot, and reinstall LILO. See the
docs in /boot after installing for more information. Slackware's Linux
kernels come in both SMP and non-SMP types now. The SMP kernel supports
multiple processors, multi-core CPUs, HyperThreading, and about every
other optimization available. In our own testing this kernel has proven
to be fast, stable, and reliable. We recommend using the SMP kernel
even on single processor machines if it will run on them. Note that on
x86_64 (64-bit), all the kernels are SMP capable.
I do not know which was the first version that had this not, but is must have been a while back
 
Old 04-11-2018, 03:53 AM   #3
bormant
Member
 
Registered: Jan 2008
Posts: 337

Rep: Reputation: 196Reputation: 196
Use for what means? Are you about rebuild another kernel only?

Last edited by bormant; 04-11-2018 at 03:59 AM.
 
Old 04-11-2018, 05:06 AM   #4
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,617

Rep: Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046
I see no reason for myself to modify the generic kernel configuration these days. I used to compile custom kernels a lot but I am exclusively using Slackware's default generic configs now, combined with an initrd, done so for years.
 
2 members found this post helpful.
Old 04-11-2018, 06:44 AM   #5
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,239

Rep: Reputation: 1898Reputation: 1898Reputation: 1898Reputation: 1898Reputation: 1898Reputation: 1898Reputation: 1898Reputation: 1898Reputation: 1898Reputation: 1898Reputation: 1898
^^ +1
 
Old 04-11-2018, 07:10 AM   #6
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,121

Rep: Reputation: 3814Reputation: 3814Reputation: 3814Reputation: 3814Reputation: 3814Reputation: 3814Reputation: 3814Reputation: 3814Reputation: 3814Reputation: 3814Reputation: 3814
I only use a custom kernel on my Ryzen desktop, partially for better hardware support, but also because I need to enable CONFIG_RCU_NOCB_CPU in my kernel so I could pass rcu_nocbs=0-15 to the kernel (see this post for a few more details on why I need to do it). My other machines use either the generic or huge stock kernels.
 
Old 04-11-2018, 07:21 AM   #7
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,273
Blog Entries: 1

Rep: Reputation: Disabled
I only once used generic kernel. Since then only huge kernels. In my experience it is more secure when troubles come.

Edit: Maybe my post is little out of subject. If question is about custom kernel.

Last edited by igadoter; 04-11-2018 at 07:23 AM.
 
1 members found this post helpful.
Old 04-11-2018, 08:10 AM   #8
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: Slackware
Posts: 9,039

Rep: Reputation: 3903Reputation: 3903Reputation: 3903Reputation: 3903Reputation: 3903Reputation: 3903Reputation: 3903Reputation: 3903Reputation: 3903Reputation: 3903Reputation: 3903
Yeah I use the stock generic kernel.
 
Old 04-11-2018, 08:22 AM   #9
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 959

Rep: Reputation: 376Reputation: 376Reputation: 376Reputation: 376
Quote:
Originally Posted by Alien Bob View Post
I see no reason for myself to modify the generic kernel configuration these days. I used to compile custom kernels a lot but I am exclusively using Slackware's default generic configs now, combined with an initrd, done so for years.
Same.
 
Old 04-11-2018, 08:29 AM   #10
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware
Posts: 1,767
Blog Entries: 3

Rep: Reputation: 1815Reputation: 1815Reputation: 1815Reputation: 1815Reputation: 1815Reputation: 1815Reputation: 1815Reputation: 1815Reputation: 1815Reputation: 1815Reputation: 1815
Quote:
Originally Posted by Alien Bob View Post
I see no reason for myself to modify the generic kernel configuration these days. I used to compile custom kernels a lot but I am exclusively using Slackware's default generic configs now, combined with an initrd, done so for years.
Moi aussi, generic-smp unmodified.
 
Old 04-11-2018, 09:08 AM   #11
jamesf
Member
 
Registered: Dec 2004
Location: USA
Distribution: Slackware 12, Slackware64 14.2
Posts: 236
Blog Entries: 1

Rep: Reputation: 56
I use the generic 64-bit slackware kernel after I build the initrd for it for my configuration.
 
Old 04-11-2018, 09:40 AM   #12
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,617

Rep: Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046Reputation: 6046
Quote:
Originally Posted by bassmadrigal View Post
I only use a custom kernel on my Ryzen desktop, partially for better hardware support, but also because I need to enable CONFIG_RCU_NOCB_CPU in my kernel so I could pass rcu_nocbs=0-15 to the kernel (see this post for a few more details on why I need to do it). My other machines use either the generic or huge stock kernels.
Thanks for the link, this is something I should apply for my Ryzen-powered build box. I had hard freezes when running QEMU virtual machines in virt-manager. Perhaps this will save me. I had just built a 4.14.33 kernel for the box but will now re-config and re-build the packages.
 
Old 04-11-2018, 10:00 AM   #13
Ne01eX
Member
 
Registered: Mar 2018
Location: Ekaterinburg region, Ural, Russian Federation
Distribution: Slackware, RTK GNU/Linux
Posts: 173

Original Poster
Rep: Reputation: 22
Question

Quote:
Originally Posted by bormant View Post
Use for what means? Are you about rebuild another kernel only?
Ru: Вот и мне интересно, зачем люди возятся с initrd и, вообще, - с модулями, если можно сразу запилить монолит под себя.
En: That's I'm wondering why people use the initrd and modules in general, if can immediately create the monolith for youself.

Ru: На одной из моих машин проставлена Slackware-Current с huge ядром (ванильным). Но она и работает, по большей части, для тестов именно самой Slackware-Current. :-)
En: One of my machines has Slackware-Current with a huge kernel (vanilla). But it works mostly for Slackware-Current tests. :-)

Ru: На другой я использую модифицированную версию ядра. Тоже huge. Для x86 и x86_64. Но это уже совсем не Slackware. :-)
En: On the other, I use a modified kernel version. huge. And for for x86 and for x86_64. But this is not Slackware. :-)

Ru: На самом деле, мне было интересно узнать, - есть ли вообще интерес к generic-ядрам. Увидел - есть. :-)
Ладно, хули, попробую предоставить и "generic" и "huge".


En: In fact, I was curious to know whether there is any interest in "generic" kernels at all. I saw - there is. :-)
Okay, I'll try to distribute and "generic" and "huge".

Last edited by Ne01eX; 04-11-2018 at 10:01 AM.
 
Old 04-11-2018, 10:43 AM   #14
mralk3
Senior Member
 
Registered: May 2015
Location: Utah, USA
Distribution: Slackware 14.2 || Slackware-current && CentOS
Posts: 1,372

Rep: Reputation: 737Reputation: 737Reputation: 737Reputation: 737Reputation: 737Reputation: 737Reputation: 737
I use a generic x86_64 kernel with an initrd.gz.
 
Old 04-11-2018, 11:59 AM   #15
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 8,923

Rep: Reputation: Disabled
Quote:
Originally Posted by Ne01eX View Post
En: In fact, I was curious to know whether there is any interest in "generic" kernels at all.
If not in Slackware 15.0, at least in the next version there won't be a huge kernel anymore anyway, so better be prepared.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
"a/kernel-generic-4.4.11-i586-1.txz" --> 486 support dropped at last? anscal Slackware 16 05-27-2016 11:04 PM
why the sound of "huge" kenerl is better that the "generic" kernel ? sdrkyj Slackware 2 02-06-2014 10:44 AM
Why "magic number "2.6.38 SMP mod_unload" should be "2.6.38 SMP" " ? rpatel Linux - Kernel 0 10-16-2012 03:35 AM
13.0 64 bit just Huge & Generic, no "smp" kernels installed acummings Slackware 2 10-01-2009 09:59 AM
Confused about "generic" vs. "386" linux kernel SaintDanBert Linux - Software 6 09-29-2009 11:51 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:05 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration