Quote:
Originally Posted by lansoar
Hi,
That's not a problem. Do that all the time with Fedora. :-)
Sounds like fun. I have not attempted such a thing before. (only once with a pkg, never with the kernel) Is there a good primer for bassmadrigal's suggestion? I'm not worried about breaking things. That's what these distros on this machine are for. I take it I'd have to reinstall 14.2_stable as a first step.
|
I was worried that by using the unstable/development Slackware -current your new Slackware experience might end up in frustration and that shouldn't be the case, since Slackware is a stable and wonderful distro.
If you are just learning Slackware & playing around with it, then your actual -current installation should be fine, and you have access to all the new packages/developments, but if you look for stability then installing Slackware 14.2 (stable) and the actual kernel from Slackware -current to suit your new HW, might be the way to go.
You'll need to backup your actual configuration/notes (at least the network part you struggled with), install Slackware 14.2 clean and follow bassmadrigal's advice to install the kernel from Slackware -current.
You can pick the kernel packages (you don't really need the sources) from here:
https://mirror.de.leaseweb.net/slack...slackware64/a/
And if supposedly you're using lilo to boot (I'm still a lilo user), then get some introduction about it here:
https://docs.slackware.com/slackbook:booting#lilo
And from here an example about the entries in /etc/lilo.conf booting different kernels:
https://www.linuxquestions.org/quest...3/#post2207242
I'd suggest using this multiple kernels scenario first, just to make sure you still have the alternative to boot the default kernel in case you messed something up with the new -current kernel installation.
Don't forget to run lilo every time after modifying /etc/lilo.conf and bassmadrigal's advice about update-pciids after your first boot with the new kernel (it'll need a reboot after that).