3.14.4 Kernel

dad_ · 05-30-2014, 07:23 AM

Quote:

Originally Posted by Didier Spaier

Well, as you already know Slackware doesn't offer this kind of "convenience" (I quote this word because most Slackware users don't consider this level of automation being a convenience). Of course you are free to try a third-party tool like slapt-get, but I'm not sure it can help in case of a kernel upgrade (maybe someone who actually used it can tell you that).

About slackpkg, it can seem outdated if you want something more automated, but it does pretty well what it is intended to do.

Also, if you are not (yet) comfortable with Slackware, I'd suggest you stay with 14.1 at the moment instead of running -current, as its aim is mainly to test the future stable release.

I've been using Slackware x86(32 bit) on my desktop for around 10 years, since 9.0 AFAIR(and often used current without any major problems, aging stable offers very old packages unfortunately, new releases are rare). I'm getting lazy and really tired of managing some things manually(like frequently upgrading kernels, etc), I even considered to go ubuntu or debian on hdd upgrade, but Slackware64-14.1 DVD was handy, so decided to continue using it. BTW simple pre-compiled kernel upgrade is a relatively simple operation and could be easily automated even in case of initrd(and with optionally keeping old kernel image and modules). If you want something really unusual, you could configure and compile your own kernel from source manually.

PS. I remember times when even slackpkg was a 3rd party tool and was not recommended, only pkgtool was "official" then.

Didier Spaier · 05-30-2014, 07:48 AM

Quote:

Originally Posted by dad_

BTW simple pre-compiled kernel upgrade is a relatively simple operation and could be easily automated even in case of initrd(and with optionally keeping old kernel image and modules).

Well, not as simple as one may think as you have to populate the initrd tree in a way that depends on user's hardware and software configuration, and that's pretty much a hit or miss.

I don't know what guides Pat's choices but as he has a limited amount of time to maintain Slackware my guess is it's something like "if something can easily be done by the user to tweak his or her system's configuration, let he or she do it".

In this particular case the user can run /usr/share/mkinitrd/mkinitrd_command_generator.sh and tweak the results as he or she see fit.

But yes, if you feel that's too much of a hassle (and I can understand that), then maybe you'll be happier with a more automated distribution.

And maybe you'll come back to Slackware later

wvragga · 05-30-2014, 10:48 AM

Greetings All,

Getting kernel panic after recent upgrade via slackpkg.

Running Slackware 64 current.
ran slackpkg udate
slackpkg-install new
slackpkg-upgrade all

Toshiba Sattelite c655
vmlinux is pointing to 3.14.4-huge

Researched issue some and saw some similar issues that were corrected after
upgrading bios, so I upgraded bios to version 1.80 from 1.60 , trace is now longer but kernel panic still happening.

System is multi-boot with grub booting. Other OS Ubuntu, Win 7 64 booting fine.
Ran update-grub just in case menu showing Slackware 14.1.

Please advise on any method I can use to provide more specific info.

Thanks for an assistance!

Respects,
Ragga.