Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am still very new to the world of linux...so any and all help would be greatly appreciated.
I am running RH 8.0...I have apache 2.* also running. Everything works fine except one minor problem.
It started out at first that if there is no direct activity at the keyboard...the monitor would just go black...of course I figured it was a screenserver or something...I read about the power management and as far as I know I set that to off. The monitor still goes black after awhile....can't seem to figure out how to make it stop. Well...every so often I touch the mouse or keyboard to make the monitor turn back on...but sometimes it doesn't come back on...when this happens...I notice that I cant get to the linux box from my other systems on the network anymore and no one can get to the site I have up...and I have to reboot the machine...then its good for a couple of hours again.
I have a similar problem as well, when it goes into "standby" or power down. It happens in Windows, and Linux. It might be the bios, I don't really know. I can't find a bios update either.
buff, kernel 2.4 is not really very stable.
With RH8, the problem gets even worse.
After one year using RH8 on my laptop, and experiencing all kind of lock-ups, I switched to a vanilla-kernel:
2.6
YES, it's in test phase but I can say it is much more stable under any condition than any 2.4 production release.
Give it a try.
If not, try to upgrade to the latest RH8 kernel rpm and crossfingers.
The problem is,now that linux becomes popular, we are stuck with a not_so_stable_2.4_kernel, which is light-years from stability kernel 2.2 used to have ( I had systems running for a year with 2.2), and also worse than 2.6 release, so, and for linux marketing image, we NEED distributions ship with 2.6 right now (And Linus knows!)
BEFORE REBOOTING WITH THIS UPGRADED KERNEL, read LILO HOWTO ( http://www.tldp.org/HOWTO/LILO.html ) so you can be sure you'll be able to boot your system.
OK, that's the mother of all linux questions: Kernel compile.
First you get the (vanilla) linux kernel (the one Linus releases) from any mirror cited in http://www.kernel.org/
I'd recommend you the 2.6.0-test5 one, but that one is meant to be "beta"; ALTHOUGH:
- After myself using 2.4 for two years on my laptop and lots of freezes, I tried 2.6 and not any more problems.
- A beta from Linus, the Man, is much much more stable than many commercial software.
- The process for building the kernel is much easier now with 2.6 than used to be with 2.4; just assure you got the qt or gtk development packages.
If despite these reasons you'd rather attach to the mainstream, then go for the 2.4.22
Note what you are downloading is a bunch of source code packed together, for which you'll have to:
- Configure (to choose options based on your hardware, etc...) the source.
- MAke the kernel.
- Make the modules (drivers)
- Install the kernel.
- Install modules.
- Rerun lilo, checking /etc/lilo.conf (If using grub, ask any other)
- reboot
BEFORE ALL OF THIS, I'd recommend some practice under a "disposable" system just in case....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.