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!
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.
Everytime I boot Fedora 10 it freezes at the blue/white bar and won't continue booting until I press a key and I have to continue doing so until it completely boots. Is this a bug or something? Does anyone know how to remedy this?
I had a similar problem on my HP laptop. The solution was to add the nohpet option to the GRUB boot kernel line. (The option tells the kernel to not use the High Precision Event Timer. Relying on the timer can, for some processors, cause the "wait for event" code to branch to needing a key-press to register the event. Note: Just pushing the "shift" key seemed to work for me.)
If you're not familiar with editing GRUB when you boot, just push the <Escape> key when the boot menu is displayed, move to the Fedora boot lin, press "e", move to the kernel=" line, push "e" again, go to the end of the line and enter " nohpet", press <return> and the "b" to boot from the modified instructions.)
Note that modifying the GRUB boot sequence this way is temporary, for testing to see if this is the fix you need. If your boot works, you'll need to edit /boot/grub/grub.conf to make the change permanent. (You'll need to be "root" to edit the file. Try [b]su -c 'gedit /boot/grub/grub.conf')
Sure. "rhgb" is the "Red Hat Graphic Boot." If you remove it. you'll see the log-on activity output. Sometimes usefull, sometimes not. You can see the same output by pressing <escape> when the rhgb "booting" bar is displayed.
The "quiet" suppresses the kernel boot messages from going to the screen. (Take it out, and the messages will fill several screen, and you can't scroll back into them.) Most of those messages are what you'll see if you enter the dmesg command in a terminal window. Note, however, that if you'd removed it, you might have gotten a clue about your boot problem, since the messages would have stopped at about the point where you needed to press a key. In this cas, I don't think the messages would have helped, but it's worth a shot when you have problems when the kernal is loading.
If by "it" you mean the rhgb, then "yes," except you should see either [OK], [WARNING], or [ERROR], but no "[DONE]."
But, as I said, it's easier to just press the escape key when the boot starts unless, for some reason, the F10 boot process has a problem with your display. (If I remember the F10 "changes" documentation I briefly skimmed, one change in the F10 boot process was a change to a "built-in" display system for use during the boot.)