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.
Greetings, I just bought a new hard disk today and thought I'd add the 10.1 distribution to my computer. Unfortunatelly, after some trouble and system re-building the system seems to be working fine with the previous hard disk (which has winxp on it) and shows the new hard disk (a western digital 120gb) as not initialized.
Now when I tried installing slack 10.1 a couple of times the system hung right after the line:
Real Time Clock Driver v1.10f
Right underneath was the cursor blinking. No keys could be pressed no nothing.
I've also tried to install SuSE but the system hangs even before I get to see any info (press esc to see information, but pressing it doesn't do anything)
Weird thing is this noon, before all this, I added the disk and tried to install SuSE. I was at the point of selecting packages, when I saw it had no apache, so I thought I'd install slack. When I rebooted, the bios failed to find both hard disk on the first ide channel (though it always finds my dvd-rw on the second channel) and then I started moving, removing and changing things. Now the system is as before, but I can't load the kernel. Any ideas? Thanks for reading this and sorry for the long post.
PS: I'm starting to think that it's not the new hard disk's fault. I've created a small partition in windows and started using it. It seems fine. But why the heck won't a linux kernel load?
I should add that I had a faulty northbridge fan (I've no idea since when, but the system was stable) but got it replaced today.
Well, thanks for the tries, but it had nothing to do with it. I found some slack boot up screens and what seemed to follow after the real time clock driver, was the floppy. Then I thought...wait, but I've disabled the floppy from the bios. That was it, when I re-enabled it (even though there's no physical floppy device in the pc) the kernel loaded right away. But it's rather weird isn't it? I mean 2 mainstream linux distributions halting because I've disabled the floppy from the bios? Nowadays that pc's without a floppy are more common I feel this should be corrected.
Now, I'll have to spend the next few days configuring my machine, but hopefully my hardware should keep going for a few years more.