[SOLVED] Kernel 4.19.0 breaks system boot - looking for kernel-huge-smp-4.14.78_smp-i686-1.txz
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.
Distribution: Slackware_x64 15.0 and slackware-current
Posts: 33
Rep:
Kernel 4.19.0 breaks system boot - looking for kernel-huge-smp-4.14.78_smp-i686-1.txz
The October 23 4.19.0 -i586 Kernel updates broke my system during booting. Looks like its a display driver issue. I searched my system for the October 20 released 4.14.78 -i586 txz packages on my system, but as Murphy always has the upper hand, those packages were not found on my system.
All of the slackware-current mirrors only have the latest 4.19.0 packages.
Q: Where can I get a set of the kernel-4.14.78 packages released on October 20 as the 4.14.78 version releases were working just fine and I'd like to be as updated as possible.
at Oct 20 19:41:13 UTC 2018
a/kernel-generic-4.14.78-i586-1.txz: Upgraded.
a/kernel-generic-smp-4.14.78_smp-i686-1.txz: Upgraded.
a/kernel-huge-4.14.78-i586-1.txz: Upgraded.
a/kernel-huge-smp-4.14.78_smp-i686-1.txz: Upgraded.
a/kernel-modules-4.14.78-i586-1.txz: Upgraded.
a/kernel-modules-smp-4.14.78_smp-i686-1.txz: Upgraded.
I got the system backup by reinstalling the 14.2 version kernel (4.4.14)
(Yes, from now on I will be sure that I have two boot options in LILO on the slackware-current version system)
Thanks in advance.
Last edited by rwyarbrough; 10-24-2018 at 09:16 PM.
Distribution: Slackware_x64 15.0 and slackware-current
Posts: 33
Original Poster
Rep:
Quote:
Originally Posted by Skaendo
Should be fixed with Oct 24 update.
Hi Skaendo,
Thanks for responding.
I'm running the i586 version and those posts and fixes are for the 64-bit version. The post also indicated that the i586 versions were OK, so I don't think that will fix my problem.
I *should* have been keeping at least one kernel back version bootable in LILO, so I'm to blame for my plight, but I am crossing my fingers someone can direct me to where I can download the October 20 4.14.78 i586 packages so I can at least get back to a recent working kernel load.
Hmm, usually there's old slackware64-current packages available from some mirror sites, but I can't find any for slackware-current. I also don't mirror slackware-current myself any more.
I suspect most people using 32-bit hardware are content to run 14.2 on it and there's just not much interest in 32-bit -current.
if can be useful, are reported by zerouno, this is the mirror that most probably is not using the --delete option of rsync (and where you can find what you are looking for in /slackware/a/)
Distribution: Slackware_x64 15.0 and slackware-current
Posts: 33
Original Poster
Rep:
Quote:
Originally Posted by ponce
if can be useful, are reported by zerouno, this is the mirror that most probably is not using the --delete option of rsync (and where you can find what you are looking for in /slackware/a/)
That was the perfect answer. It indeed has all the previous releases available there. Thank you so much! That mirror has been bookmarked for the next time I mess up royally...
Quote:
Originally Posted by ponce
IMHO, you will be better trying to fix your issue with the display driver...
Yes, definitely plan on doing so as I've been reading that 4.19 is the newest LTS version and the recommended kernel branch to use, but at the moment, that little thing that pays the bills called "a job" has me tied up from doing just that, so I needed a quick fix for the time being until I can get back to working on fixing the display driver issue on the 4.19.0 boot-up.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.