V.T. Eric Layton Posted September 1, 2016 Share Posted September 1, 2016 (Copied from a post at LinuxQuestions.org) === Modules Not Found Issue After Upgrade to 3.10.103 in Slack 14.1 This is the first time in over a decade of using Slackware that an update/upgrade of any kind crashed my system. I'm sad. After updating (using Slackpkg) the kernel from 3.10.17 to 3.10.103 and running LILO, the system would not reboot. It gave a kernel panic warning and a notice that the 3.10.103 modules could not be found, even though they were installed according to Slackpkg. My solution (for the moment, anyway) was to install the old 3.10.17 kernel from the installation media by using the command line and chrooting into my Slackware installation. All went well and I got my system back up, but I'm a bit gun shy about updating again, so I've blacklisted the kernel for the time being. Anyone else having issues with 3.10.103? __________________ V.T. Eric Layton Nocturnal Slacker Registered Linux User: #423757 Slackware Documentation Project === Whaddya' think about that? Quote Link to comment Share on other sites More sharing options...
securitybreach Posted September 1, 2016 Share Posted September 1, 2016 Ugh that sux I am very surprised that Slackware hasn't at least gotten to 4.0 I know Slackware is a little slow but d***: comhack@Cerberus ~ % uname -a Linux Cerberus 4.7.2-1-ARCH #1 SMP PREEMPT Sat Aug 20 23:02:56 CEST 2016 x86_64 GNU/Linux BTW Slackware was the first distro I installed back in 02 so we have a history.... 1 Quote Link to comment Share on other sites More sharing options...
wa4chq Posted September 1, 2016 Share Posted September 1, 2016 Sorry to hear the sad news. I'm also using Slackware 3.10.17.....I'm sceered to do updates. For one thing, I've never done it before, wouldn't know what to do and am a bit nervous that I'd really screw up .... Glad you were able to get things working again. 2 Quote Link to comment Share on other sites More sharing options...
ebrke Posted September 1, 2016 Share Posted September 1, 2016 Oh poop. That's a revolting development. 1 Quote Link to comment Share on other sites More sharing options...
V.T. Eric Layton Posted September 1, 2016 Author Share Posted September 1, 2016 Well, do-do occurs sometimes. My whole year has been a great rain shower of it; not that I'm complaining. There are always others worse off than I am. Anywho, Josh... I'm still running 14.1 Slack on my systems because I'm to lazy to reinstall with 14.2 right now. I'm going to install 14.2 in the new system once I assemble it later this winter; no sense it doing it twice. Oh, and 14.2 is running the 4.4.14 kernel. Oh, and Neil... it's not that difficult to upgrade the kernel, but don't do it via Slackpkg because it will clobber (delete) your old kernel. I was lazy yesterday and that's how I got into that bit of trouble. I couldn't revert to the old kernel because it was gone. I couldn't boot the system, so I had to do it the hard way... chroot. Directions from Pat V... Installation instructions:+------------------------+ Upgrade the packages as root: # upgradepkg kernel-*.txz If you are using an initrd, you'll need to rebuild it. For a 32-bit SMP machine, use this command: # /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.10.103-smp | bash For a 64-bit machine, or a 32-bit uniprocessor machine, use this command: # /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.10.103 | bash Please note that "uniprocessor" has to do with the kernel you are running, not with the CPU. Most systems should run the SMP kernel (if they can) regardless of the number of cores the CPU has. If you aren't sure which kernel you are running, run "uname -a". If you see SMP there, you are running the SMP kernel and should use the 3.10.103-smp version when running mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit systems should always use 3.10.103 as the version. If you are using lilo or elilo to boot the machine, you'll need to ensure that the machine is properly prepared before rebooting. If using LILO: By default, lilo.conf contains an image= line that references a symlink that always points to the correct kernel. No editing should be required unless your machine uses a custom lilo.conf. If that is the case, be sure that the image= line references the correct kernel file. Either way, you'll need to run "lilo" as root to reinstall the boot loader. If using elilo: Ensure that the /boot/vmlinuz symlink is pointing to the kernel you wish to use, and then run eliloconfig to update the EFI System Partition. Easy-peasy! NOTE: Always remember to blacklist your kernels in /etc/slackpkg/blacklist by removing the # from in front of the kernel entries in that text file. This way, Slackpkg will ignore all kernel updates. Weeeeeeeeeeeeeeee! 3 Quote Link to comment Share on other sites More sharing options...
Capt.Crow Posted September 1, 2016 Share Posted September 1, 2016 DAzzzzzzz.reelie wieerddd. Must try that upgrade coz I've never been able to break Slackware yet.. 1 Quote Link to comment Share on other sites More sharing options...
V.T. Eric Layton Posted September 1, 2016 Author Share Posted September 1, 2016 Oh, and you can grab the kernel goodies from any of the repos... Again from Pat V... Where to find the new packages:+-----------------------------+ Thanks to the friendly folks at the OSU Open Source Lab (http://osuosl.org) for donating FTP and rsync hosting to the Slackware project! :-) Also see the "Get Slack" section on http://slackware.com for additional mirror sites near you. Updated packages for Slackware 14.1: ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-generic-3.10.103-i486-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-generic-smp-3.10.103_smp-i686-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-headers-3.10.103_smp-x86-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-huge-3.10.103-i486-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-huge-smp-3.10.103_smp-i686-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-modules-3.10.103-i486-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-modules-smp-3.10.103_smp-i686-1.txz ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-source-3.10.103_smp-noarch-1.txz Updated packages for Slackware x86_64 14.1: ftp://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/linux-3.10.103/kernel-generic-3.10.103-x86_64-1.txz ftp://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/linux-3.10.103/kernel-headers-3.10.103-x86-1.txz ftp://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/linux-3.10.103/kernel-huge-3.10.103-x86_64-1.txz ftp://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/linux-3.10.103/kernel-modules-3.10.103-x86_64-1.txz ftp://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/linux-3.10.103/kernel-source-3.10.103-noarch-1.txz MD5 signatures: +-------------+ Slackware 14.1 packages: 1121a215f3af597c87fc18aa7d04cef1 kernel-generic-3.10.103-i486-1.txz 8aee03c88e4fca95302b6350df2ec13f kernel-generic-smp-3.10.103_smp-i686-1.txz 15f50b5ece93f19db77118dcb19692d5 kernel-headers-3.10.103_smp-x86-1.txz 8bd94dc6dd24ecc980bf75aabffcce5f kernel-huge-3.10.103-i486-1.txz 4f59f96b3053a6fdf31a7a82b78c941e kernel-huge-smp-3.10.103_smp-i686-1.txz 04a521fd17b3d03c91242c9f11dc0447 kernel-modules-3.10.103-i486-1.txz 2a7505fd7508b9b19759b614141f7996 kernel-modules-smp-3.10.103_smp-i686-1.txz 10ad031b1aafb3ceb94f391ba467a419 kernel-source-3.10.103_smp-noarch-1.txz Slackware x86_64 14.1 packages: 7136915c953b60a52fb7732998789fcc kernel-generic-3.10.103-x86_64-1.txz 26dc0f2b6adcbebd25716d7d249c78bc kernel-headers-3.10.103-x86-1.txz 4b03d7d4b3b117258d0813d6b87320c4 kernel-huge-3.10.103-x86_64-1.txz b4a5b76fd4536b32a7f6d21b3cb4a53d kernel-modules-3.10.103-x86_64-1.txz 16cbbf92568c22ef1023457dab1666ab kernel-source-3.10.103-noarch-1.txz Quote Link to comment Share on other sites More sharing options...
Capt.Crow Posted September 1, 2016 Share Posted September 1, 2016 The mist clears slightly. Already running 14.2 Jumped on that the minute it appeared on Heanet.mirror 1 Quote Link to comment Share on other sites More sharing options...
saturnian Posted September 2, 2016 Share Posted September 2, 2016 There are always others worse off than I am. Hey, you stole my line! Seriously, that's something I remind myself of whenever things aren't going so well. Or I'll say something like, "There are literally billions of people around this world who are worse off than I am!" Sad but true, the more you think about it. 1 Quote Link to comment Share on other sites More sharing options...
wa4chq Posted September 2, 2016 Share Posted September 2, 2016 Thanks for the info, Eric..... Still looks like magic to me.... If I had a spare lappy, I'd give it try. Quote Link to comment Share on other sites More sharing options...
V.T. Eric Layton Posted September 3, 2016 Author Share Posted September 3, 2016 It's a special kind of magic, Neil. In the RF Communications electronics field, we used to refer to it as "FM." 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.