Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Tonight I was trying to install Slackware 12.1 on an old computer I have. It was running Slackware 12.0 previously. The specs are; 533Mhz Celeron, 256MB RAM and two HDDs with the capacities of 80GB and 9GB.
Slackware 12.0 had previously ran fine with no problems. My main reason for upgrading was to simply start fresh.
I expected it to go smoothly, but the computer really started to show its age. While installing the packages, about five or six of them failed (some where also required packages) with a 'fatal error' message.
I had previous checked the MD5 of the ISO and just to be sure I verified the disk twice on my primary computer. No problems there.
So now that my drive is starting to die (I guess that it is about time too) and pretty much useless, how can I install Slackware? Unfortunately, my BIOS doesn't support USB booting.
Okay, by using a loop back device I managed to get Slackware installed without a flaw. The trouble I'm having now is that I get a kernel panic on boot. I'm unable to copy it all out, but it happens quite late in the boot process (after DHCP is polled).
The last two lines are as follows...
EIP: [<d0af452e>] de_set_media+0x15e/0x170 [de2104x] SS:ESP 0068:c08e5e54
Kernel panic - not syncing: Fatal exception in interrupt
Seems to have something to do with a drive, but nothing had been changed since the previous installation of Slackware 12.0.
Big thanks to any replies.
Last edited by pxumsgdxpcvjm; 05-27-2008 at 07:06 AM.
This is a strange problem. After a few reboots (with nothing changed), it came right and I managed to login. I'm sure it won't last long, but I'll try removing another dead CD-ROM drive from the system (as I suspect that may be the cause of the kernel panic). Anyway, before I do that tomorrow, has anyway had this sort of issue before and do know what caused this? I would like to fix it as I'm sure I'll end up seeing again.
I know that the CD drive is on its last legs. Not too much of an issue since I have a USB drive (although I cannot boot from it). I ended up installing Slackware thanks to the loopback device node with the ISO added on the USB drive.
Other then that random kernel panic on startup, the system seems fine.
I did a little looking around and it seems to be a kernel bug. This one here. It's fixed in the latest kernel release, so it looks like I'll have to upgrade my kernel.
Last edited by pxumsgdxpcvjm; 05-29-2008 at 06:04 PM.
Yea. I just tried running Memtest68+. Not problems found on the first pass and I expect the same once the second is complete. I'm pretty sure that my issue is due to that kernel bug, but I'll have to compile it in order to be sure.
Yea. Just complied a new kernel for the machine. Seems to be working flawlessly now.
So compiling a new kernel solved the problem. What were your omissions? What was changed? You should post the results so as to provide others with information in case someone searches and finds the posts. With a complete solution to the problem being posted then everyone benefits.