Does anyone use the original config "generic" / "generic-smp"?
 

Subj.:D Without anyone modification.

https://en.wikipedia.org/wiki/Symmetric_multiprocessing

from some Slackware release announcement

I do not know which was the first version that had this not, but is must have been a while back

Use for what means? Are you about rebuild another kernel only?

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.

^^ +1

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.

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.

Yeah I use the stock generic kernel.

Same.

Moi aussi, generic-smp unmodified.

I use the generic 64-bit slackware kernel after I build the initrd for it for my configuration.

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.

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".

I use a generic x86_64 kernel with an initrd.gz.

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.

the only reason for an initrd are the file system drivers, at least for me.
back the days I always rebuild the generic-smp, but with extX drivers inbuild, than I did not need the initrd
today I use the huge kernel, it works. initrd is too stressful, creating it gives me nothing than work and a wast of time.

I use exclusively the generic/generic-smp. From starts.

In fact, I do not remember preciselly how looks the native installer, as I use the hard way (literally: manual installation), and having an external USB hard-drive of 500GB, hosting both x86 and x86_64 installations (in different partitions, of course) including local mirrors, with everything kept up2date.

I do not know why, but I feel that the combination of generic(-smp) and initrd works better.

For a 'normal' no-frills installation, you don't need an initrd if you are happy with a huge kernel.
In case you want to use RAID, LVM or LUKS, you are required to use an initrd.

Time for saving kernel-configs? :D

I pretty much use the generic kernels and an initrd. Installing a new initrd with elilo is easier and safer than ever. Just build the image mount the vfat filesystem under /boot if its not already and and go.

This is super nice too because typically you can copy the system to any, including very different machines and with an initrid update and maybe a few deletes of things under /etc/udev/persistent.... its good to go.

...if your not using proprietary drivers, such as NVidia. :-D :-D :-D

Huge kernel going away some day?
 

Didier, thanks for the heads up. Trying generic is on my “some day” list, but I’ve had no great reason not to just run huge. If it’s going to go away in the next version or two, I’ll go figure out how to do it with grub, although on reading the instructions it doesn’t sound like there’s much to it, if everything goes smoothly.

Has anyone here ever had trouble switching to generic?

I use the generic kernel and an initrd to reduce RAM usage. Also, although I have never seen it, apparently it has been reported that the huge kernel can suffer from conflicts on certain hardware. It is faster to build an initrd than to create a monolith with additional options.

If i feel like running a patched kernel once in a while (usually the postfactum patches for me), i'll copy over the currently running generic config to build from, then adjust the few new options for what the patches provide. Other than that i'll also use the generic config with no changes if i feel like compiling the latest mainline kernel.

I exclusively use the 64-bit huge smp kernel.

Slackware's stability is a key feature to me. By using the same kernel binary as some other Slackware users, I am less likely to have bugs in my systems' kernels that other people do not find.