Slackware-current depmod can't find lib/modules
 

Hello Everyone,

I tried install slackware-current 32bit 3-21-2016. When i try
to log on i get depmod can't find /lib/modules/kernel-4.4.4
which is odd because, i have kernel-4.4.6.

Install kernel-modules-4.4.6. You need the modules that correspond to your running kernel.

EDIT: that's maybe not the issue, what says: "ls -l /var/log/pacakages/kmod*"?
And what says "uname -r"?

Hello Didier Spaier,

Can't log on to print out ls -l /var/log/pacakages/kmod*. This is the package in my
slackware-currecnt/a

kernel-modules-smp-4.4.6_smp-i686-1.txz

This the kernel files i have
a
kernel-firmware-20160310git-noarch-1.txt
kernel-firmware-20160310git-noarch-1.txz
kernel-firmware-20160310git-noarch-1.txz.asc
kernel-generic-4.4.6-i586-1.txt
kernel-generic-4.4.6-i586-1.txz
kernel-generic-4.4.6-i586-1.txz.asc
kernel-generic-smp-4.4.6_smp-i686-1.txt
kernel-generic-smp-4.4.6_smp-i686-1.txz
kernel-generic-smp-4.4.6_smp-i686-1.txz.asc
kernel-huge-4.4.6-i586-1.txt
kernel-huge-4.4.6-i586-1.txz
kernel-huge-4.4.6-i586-1.txz.asc
kernel-huge-smp-4.4.6_smp-i686-1.txt
kernel-huge-smp-4.4.6_smp-i686-1.txz
kernel-huge-smp-4.4.6_smp-i686-1.txz.asc
kernel-modules-4.4.6-i586-1.txt
kernel-modules-4.4.6-i586-1.txz
kernel-modules-4.4.6-i586-1.txz.asc
kernel-modules-smp-4.4.6_smp-i686-1.txt
kernel-modules-smp-4.4.6_smp-i686-1.txz
kernel-modules-smp-4.4.6_smp-i686-1.txz.asc

k
kernel-source-4.4.6_smp-noarch-1.txt maketag.ez
kernel-source-4.4.6_smp-noarch-1.txz tagfile

Still, I need the output of the two commands I indicated to investigate further. If you can't log in I do not know what we could do... Also, that you have a package in the distribution media does not tell if it is installed.

if you cant log in that simply means you didn`t install system properly at all, if you new to linux/slackware get on with full install, i tried to be smart as a debian refuge and i started with minimal install but finally my system weights 8.1 GB

Check your current kernel. It looks like you're still running 4.4.4, which could mean you never ran lilo after updating the kernel.

Hello Everyone,

@bassmadrigal I have slackware64 and slackware32 installed but when i updated the new i did not updated lilo i just keep the old entry. Which had a slackware32 bit entry.

So is it possible to have to different slackware's on the same system with lilo?

You would just need boot entries for each Slackware version along with linking the correct kernel. Then run lilo afterward to save your entry.

as far as i am aware he did update (upgrade) the system from 32bit-current to 64bit-current
i understand all of this mess is on one /root partition????


"So is it possible to have to different slackware's on the same system with lilo?"

does anyone understand that statement???

you can have 2,3,4.... as many as you want kernels on the same system, also you can have many systems on different / partitions - but you cannot have different system on the system,

get live cd boot it and print:

#fdisk -l
#cat /etc/lilo.conf (im not sure i have grub)

you can chroot your slackware and install kernel and lilo

Hello Everyone,

@przemo Yes you can have a 32bit slackware and 64bit slackware on the same system with lilo.

When you have both 32bit and 64bit versions of slackware installed
edit the lilo config. One of the 2 linux images is going to need a
/mnt/sda? infront of it then run lilo to update it.


# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda5
label = Slackware64
read-only
# Linux bootable partition config ends

# Linux bootable partition config begins
image = /mnt/sda6/boot/vmlinuz
root = /dev/sda6
label = Slackware32
read-only
# Linux bootable partition config ends

# Windows bootable partition config begins
other = /dev/sda1
label = Windows
table = /dev/sda
# Windows bootable partition config ends

This isn't necessarily true. It all just depends on where you put your kernel. You can have all your kernels for multiple Slackware versions -- or even different distros -- in one folder as long as they're named differently. So if you had put your 32bit vmlinuz file in your 64bit /boot directory and just called it vmlinuz32 (I always base the name off the kernel itself to keep them easily organized -- e.g. vmlinuz-huge-3.10.17, vmlinuz-generic-3.18.24, etc -- you could just add a 32 or 64 somewhere in there to distinguish between the two). Then you just use the correct name in your lilo.conf.

The main thing to make sure is that the root is set to the correct partition for the system and that the kernel (and initrd) are available when you run lilo to save your configuration.