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.
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.
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
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.
Last edited by Didier Spaier; 03-22-2016 at 03:12 PM.
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
@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?
@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
@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.
One of the 2 linux images is going to need a
/mnt/sda? infront of it then run lilo to update it.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.