FedoraThis forum is for the discussion of the Fedora Project.
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.
I have many questions regarding software packages, etc., but first I have to get the system running right.
After x amount of time (sometimes at the login screen, sometimes after running for hours) the input devices freeze up. Caps Lock and Scroll Lock lights on keyboard light up, and the only solution seems to be a hard reboot. At first I thought it was Mozilla, but it happens even when Mozilla is not running.
I'm using GNOME in Fedora Core 1. The machine itself is a couple of years old -- ~1 Ghz AMD CPU, 128 megs of RAM, 40 gig HD -- but I've run other distros on much weaker machines with few problems.
Had a similar problem -- input device freezes -- with a Slackware distro years ago and it had to do with memory leakage, but that doesn't seem to be the problem this time, based on what the system monitor is telling me -- though the system does seem to want to dip deep into the swap drive for some unknown reason.
Hardware is probably not the problem -- everything checks out OK.
What's going on? Would more mem solve the problem?
Can anybody help me? Anybody have any ideas on why the system freezes up?
This is the problem with Linux as far as it being "ready for the desktop". In my experience it works great as a web server or mail server, but when you set it up for everyday use, there's always at least one annoying little bug that makes it easier -- in terms of getting day-to-day stuff done -- to work with a commercial OS.
I had a similar problem in Fedora Core 2 with Gnome also. It turned out to be my hardware. I would go into your BIOS and turn off everything having to do with hardware (especially monitor and video card) going into stand-by or power-save mode.
Note: I also had a problem with Windows similar to this so it wasn't just Linux doing it for me... it was everything.