SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Just installed Slackware 10. Wiped the drive. Made one swap and one root partition. Tried to keep it simple. Installed all packages except a couple that I felt safe to say were not necessary at all.
Noticed something was wrong when ifconfig reported loopback address only. Saw that modprobe was looking for files under a 2.2.20 path instead of the 2.4.26 path which exists on the new system. Read through the forums a bit, and realized /etc/lilo.conf was set to use image vmlinuz instead of vmlinuz-ide-2.4.26. Changed that and ran /sbin/lilo Rebooted, and still running kernel 2.2.20-idepci according to uname -r By the way, there are no files in /boot with 2.2.20 version number, and 2.4.26 is there. I'm guessing the default vmlinuz image must be of that earlier version. However, I'm having difficulty determining what is calling it.
I can't post copies of much, since I can't get this machine networked yet. Although I've been messing with linux for over a year, I'm still pretty much a newbie at it (mostly Fedora and still somewhat dependent upon the GUI stuff). This is my first experience with Slackware. I'm fairly certain I didn't make any mistakes during the installation. Perhaps I did, or perhaps this is a bug of some sort. Your responses are appreciated.
The first download came from one of the sites at the above mentioned URL. After reading your reply, I tested the files by redownloading them using BitTorrent from linuxiso.org, and md5ing each. They matched. While waiting for the new download I wiped the partitions and set the system up again... twice. Keep getting the same thing... System wants to boot to 2.2.20, even though that kernel doesn't appear to be present.
I can only assume that I've missed a basic choice during installation. It's probably something so simple that it's easily overlooked by people who are comfortable w/ this distro. I followed the steps in the slackware.com/book. I downloaded and installed Debian on the same system a few days ago, which seemed to run as intended.
Question: Could installing from the cdrom only, without having access to a floppy drive cause this? The system I've been installing on has a faulty floppy controller. So, I have it disabled and have been using the cdrom to get the machine up to the point where it is on the network and can go from there.
You don't need a floppy disk if your system is able to boot the cd. A md5 check is good enough to ensure there is nothing wrong with the cd. The only thing I can think of is old data present on your harddisk already and appearing somewhere at boot time after installation. But the lack of a floppy can hardly cause the appearing of software not present on your cd.