I have installed 15 on my laptop (a Tuxedo BM15), and all is well. However, after upgrading, all is not well at all.

Right after starting eudev, the error comes:

Right after upgrading, I ran eliloconfig, and had it replace the entry.

I have brought the computer up with a boot USB stick. But then I have no network among other things. Right now, it's basically a brick.

It is reluctant to boot on its own. I need to go into the BIOS to chose the disk to boot (before upgrading). It has quirks, but otherwise fine.

Any help is greatly appreciated.

Did you run the mkinitrd script after the update ?

And did you upgrade the kernel modules as well as the kernel itself?

I have same problem on an old 32bits archos 10 netbook. Tried to increase the wait in the initrd but perhaps not enough. Still it boots with huge kernel.

Is this a 32bit Slackware OS? Perhaps you installed a non-SMP kernel together with a SMP kernel-modules package (or vice versa).
Also, eliloconfig may not be the best tool to use after upgrades since it makes some assumptions that may be correct for the initial installation but not for upgrades, and worse: it only configures one kernel for you.
You may want to learn how to edit /boot/efi/EFI/Slackware/elilo.conf and add your new kernel(s) manually so that you can always keep a known working kernel in your boot selection menu.

1 members found this post helpful.

I'm having the same problem. I guess the reason is I didn't run the mkinitrd script. I've got two questions:
- is there a way to salvage current installation?
- should I run mkinitrd manually after kernel upgrade, or is there other way?


Thank you for your help.

Almost certainly. But exactly how you do it will depend on a lot of info that you haven't given us yet. For example, which bootloader are you using, GRUB2 or elilo? Do you still have the old kernel and modules around anywhere? Can you boot from another system?
Yes you should. Run Patrick's /usr/share/mkinitrd/mkinitrd_command_generator.sh script first so that you know what modules to provide. And remember that you'll have to add a -k option if you're creating it for a new kernel, not the one that's currently running.

Thank you for your reply. It's elilo. Old modules are gone, just the new ones. I'm able to boot the system, but USB keyboard doesn't work, also no network. I have bootable USB Slackware instalation key, I'm able to mount partitions, which are:
/dev/sda1 /boot
/dev/sda2 swap
/dev/sda3 /
/dev/sda4 /home

Can I make it with this stuff?

Not sure. You say you have the new modules. What about the new kernel that goes with them? And the initrd to go with the kernel? You need a full matching set somewhere on your system.

Here are a couple of things to check:
1) Which kernel(s) do you currently have installed modules for? Look in /lib/modules.
2) If you have any installed modules at all, do you have a kernel image to go with them? Look in /boot as well as on your ESP. You can also find a list of what's currently installed in /var/lib/pkgtools/packages.

I gather you have a keyboard when you boot from your installation image so you should be able to check up on that. If you can find a matching set of kernel plus modules, you just need to make (or find) an initrd for the kernel and copy everything to the right places for a working boot.

If not, you will need to boot from something that gives you a network connection, like systemRescueCD, so that you can download what you need from a Slackware mirror.

I have only done what I have ever done:
After that, I ran eliloconfig. Previousy, I merely ran lilo, no longer valid on the modern 64-bit hardware.

Among the packages to upgrade was the kernel modules. That said, I have always used the huge kernel and never had to bother about modules or mkinitrd.

I would go with
where $kernel_version is the last you installed with according modules.

If it's ok this will create the initrd.gz
Then edit elilo.conf

If you have multiple kernel and initrds add at the previous command

I got myself a brand spanking new computer just for the release of 15. It's a 64 bit machine. I chose the huge option as far as I know.

Yes, I made the assumption that all was back to the good old ways. Apparently I have to learn new tricks to keep the system going.

I'm not sure this will be useful, but want to mention it, just in case. I have a System76 Pangolin that for whatever reason, doesn't like to boot with elilo. I've come to find out that tuxedo and system76 share a lot in common. Anyway, based on your posts in this thread I doubt the issue is with elilo, but just wanted to mention it.

You can use the Slackware 15.0 install disc as a rescue. With a UEFI system, boot the installation medium and there is an option called "Detect/boot any installed operating system". Assuming you did install all the 5.15.27 patches, modules, huge, generic, etc. Then it should find them and you should be able to select the huge kernel from there and boot the system. Once booted then you can make a new initrd the way Tonus mentioned.