SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
so I got 4.4.111 sitting here, the whole kit boodel' source and everything, and I am wondering if anyone else has installed this update on 14.2 stable without incident?so I got 4.4.111 sitting here, the whole kit boodel' source and everything, and I am wondering if anyone else has installed this update on 14.2 stable without incident?
This is -stable. Fine for me after the update. Go for it.
so I got 4.4.111 sitting here, the whole kit boodel' source and everything, and I am wondering if anyone else has installed this update on 14.2 stable without incident?
No problems here. Just remember if you're using the Nvidia blob that you'll have to recompile drivers once you reboot.
so I got 4.4.111 sitting here, the whole kit boodel' source and everything, and I am wondering if anyone else has installed this update on 14.2 stable without incident?
I upgradepkg the works then made initrd, edited lilo and ran lilo. Everything worked as it should on Slackware64 14.2
Did you use the generic kernel? If so, make sure you generate a new initrd. Other than that, I don't know what other configuration might need to be done with grub.
Did you use the generic kernel? If so, make sure you generate a new initrd. Other than that, I don't know what other configuration might need to be done with grub.
$ sudo update-grub
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-huge-4.4.111
Found linux image: /boot/vmlinuz-huge
Found linux image: /boot/vmlinuz-generic-4.4.111
Found linux image: /boot/vmlinuz-generic
Found Windows 10 (loader) on /dev/sda1
Found Slackware Linux (Slackware 14.2) on /dev/sda5
Found Solus (3) on /dev/sda6
/usr/sbin/grub-probe: error: unknown filesystem.
done
without making a new initrd. but it doen't make sense as it sees everything I have plus that as if it is a separate entity file system.
I do not know why it'd need that, its update a kernel before and have been running it every since. Are you really really sure it needs that?
I really really wanted to just release 4.15 today, but things haven't
calmed down enough for me to feel comfy about it, and Davem tells me
he still has some networking fixes pending. Laura Abbott found and
fixed a very subtle boot bug introduced this development cycle only
yesterday, and it just didn't feel right to say that we're done.
So I'm doing an rc9 instead. I don't particularly like to, but I like
it even less releasing something that doesn't seem baked enough.
Some people have already started sending me pull requests for 4.16
(generally because they aren't expecting to be online next week and
expected the merge window to open). I appreciate it, and I'll keep
them queued up, I just won't start applying them quite yet.
Anyway, rc9 is mostly arch updates (x86, arm, powerpc, mips) and
drivers (gpu, networking and md). And some core networking. And then
there's various random misc fallout (tracing, bpf, and new selftests)
I really expect no more delays after this. We've had rc9's before, but
they have been pretty rare (the last one was 3.1-rc9 back in 2011 -
that release went all the way to rc10, and I really don't think we'll
do that this time _despite_ all the CPU bug mitigation craziness).
Linus
---
Last edited by cwizardone; 01-23-2018 at 03:32 AM.
Reason: Typo.
We recommend that OEMs, cloud service providers, system manufacturers, software vendors and end users stop deployment of current versions, as they may introduce higher than expected reboots and other unpredictable system behavior.
So, are they suggesting to go back to 20171117, or the older 20170707 release? Both contain the same revision for my processor, so it doesn't matter in my case, but once again intel are being vague and unhelpful with their announcements.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
as soon as I get this other system up to par.. back to Slack
