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.
About a month ago I installed Fedora 3 on my aging PIII 733. The installation went without a hitch.
Since that time I have not had a great deal of time to work with it. I got the nvidia drivers installed for the GeForce card and I managed to get my DTV card configured. So far so good.
About a week ago after a night of learning about Fedora 3 and playing with it retired for night. At this point I just switched off the monitor and went to bed, leaving linux running and in X. (Whe should I have to shut it down? It IS Linux after all)
It was about 3 days before I got back to it. I turned the monitor back on and opend Firefox to do some browsing when I found that my keyboard had stopped working. Nothing I could do would bring the keyboard back, so using the mouse, I restarted the machine. The keyboard came back after the restart.
Once again when I had finished for the night, I left the machine on. And again it was a few days until I returned.
Last night I turned on the monitor, moved the mouse and pressed the space bar. All that stuff you do to wake a sleeping machine. Buy the time the desktop appeared there was an error waiting for me. Some error to do with Firefox and some 'Default user' thing. However, that was not the problem. Firefox opened again, all by itself and the error appeared again. And again and again and again. Within seconds I had about 30 firefoxs open all displaying this error. There was nothing I could do. I could not even get to the menu option to close the machine down. As everytime I clicked the menu it dissappeared as 'focus' was taken to the next Firefox error.
I had to press the RESET button. Something that I would expect to have to do on a Windows problem.
I have no idea what is wrong with this Fedora 3. This same machine, in the past has run Fedora 2, and several different versions of Redhat, right back to Redhat 5.
Anyone else had this sort of problem, waking an idle Fedora 3?
Distribution: Have used Yellow Dog, thinking Mandrake for X86 System
As far as waking your FC3 setup I can't really help you. Are you sure that your keyboard is properly configured? The Firefox thing just sounds like a bug with Firefox, try updating your version of Firefox, or report the bug to the people at Firefox.
Now as far as having to hit the restart button, you really should never have to do that. You can bring up another console by pressing "ctrl-alt-Ff9(other numbers will work too)" From there you can kill the X server "su - killall XFree86" and that should fix your problems. Then you can just restart X and your back in again. If your system is locked up and you can't change consoles, you can probably ssh in from another machine on your network (providing you have one) and kill the offending processes that are chewing up all that CPU