[SOLVED] installed Fedora Core, but computer won't reboot
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.
I have a laptop, installed with window XP. I just installed Fedora Core, re-formatted all parition on the system, and installed default packages. The installation was successful. But after I took out the installation CD and reboot the system, chose Fedora core (the only banner), the screen just become green, and nothing else from there.
The only thing I am not 100% sure is, during the installation, my monitor was probed as unrecognized. I have tried both 'go with default' and specify one "LCD 1024x...", but either way, after the installation, system won't reboot.
1. it could just be that your video is not properly driven. Try a liveCD and see what driver it uses. VGA or VESA are the most general.
2. some driver may be loading (or not) that totally hangs the system. Unlikely, and easy to rule out. Load up and when you get to the flat screen hit CTRL-ALT-F1. You should get a curses/ascii terminal (no gui) and a prompt to login. If you do, and can log in, your system is not hung and you only have a display issue. (CTRL-ALT-F7 should get you back to gui, such as it is.)
I am betting it is just the display issue, and if you can detect/use the correct monitor driver you will be doing the happy dance.
You note that the GRUB menu is displayed. When it appears, press the "e" key to edit the entry, and add a " 3" at the end of the kernel line. (Edit instructions are at the bottom of the screen.) Then press "b' to boot from the (temporarily) modified boot stanza.
That should boot you into a "no GUI" system. (If it doesn't do that, your Fedora installation has failed and needs to be redone.)
You should now see a Login prompt where you can enter "root" and, in the next line, your root password to log in as your system administrator.
Once logged in, enter the command dmesg | grep -i error to see if any boot error messages where reported. If there were any such messages, try to resolve them.
Then run the command grep -B3 -A5 '(E)' /var/log/Xorg.0.log to see if the last attempt to start the X-server produced and error messages. (The -B3 -A5 instructs the grep command to print the 3 lines before, and 5 lines after, any error lines in the Xorg log file.) That should tell you why the display isn't working. If it's not clear from there what you should do, post the error message(s) here for assistance. (Since you won't be able to cut and paste the messages, try to write then on paper before posting. Unless your short-term memory is a lot better than mine.)
(By the way, newer Fedora releases - since Fedora 12 - no longer use the ctrl-alt-f7 mentioned by wpeckham, and, in fact, the default X-server settings completely disable all ctrl-alt switching. That default can be changed, but that a different topic.)
No log file? Are you sure? (ls /var/log/ to check.) If there's really no Xorg.0.log file, that implies that you've never started the X-server on tty0.
So, do the "boot into Init level 3" thing again, and, instead pf logging in as "root," log in as your normal, non-privileged, user (if you've set up one), and run the startx script. That will attempt to start the X-server for the non-privileged user, and, if it fails, write some useful error messages on the terminal screen. (If the messages scroll off the screen, try startx | less so you can review the whole output.)
I suspect that your problem is that your video card is not being properly detected, and the incorrect driver is being loaded. If this is the case, you can log in as "root" and use the Xorg -configure to create an xorg.conf file in /root. Then edit that file so the driver in the "Device" section for your video card is correct, move it to /etc/X11/xorg.conf, and try the startx (after switching to a non-privileged user account) again. (Note that you may have an older version of the video card that requires an "obsolete" driver version, and the auto-detection may only be detection the brand, not the version.)
Oh, if you want to enable the use of the ctrl-alt-... switching, add a file like this:
to the /etc/X11/xorg.conf.d/ directory. (See man xorg.conf for details.) Since the defaults were changed with version 4 of the X-server, any distribution that uses the newer release will behave like Fedora unless the distribution designers change the X-server "preferred" defaults.
By the way, the reason I suggest running the startx script as a non-privileged user is to reduce the possibility that you'd make an open Internet connection as a privileged user which constitutes an avoidable security risk.
Last edited by PTrenholme; 02-19-2011 at 12:45 PM.
To refine, there have been some excellent suggestions. The problem has been narrowed down to a xorg video issue, not a boot issue. (Much thanks to PTrenholme!)
The suggestion that new versions of Fedora identify video hardware better is not well supported by experience or statistics, though I would tend to believe that newer Xorg install identify NEWER VIDEO HARDWARE better.
I know of many examples of older video hardware that worked fine on older versions, but does NOT work as well using the new drivers. In such cases there is always a way to back down to the older driver and get it to work, but it does take research and manual intervention.
I would learn all you can about what kind of video controller and monitor you have, the monitor characteristics (supported frequencies/modes etc), and drivers known to work with that controller. If all else fails you should be able to drop back to the basic VGA driver, although that may limit you to 600x800 resolution (the original basic VGA resolution options were quite limited).
By the way, newer Fedora releases - since Fedora 12 - no longer use the ctrl-alt-f7 mentioned by wpeckham, and, in fact, the default X-server settings completely disable all ctrl-alt switching. That default can be changed, but that a different topic.
Oh no they don't! The change is that the GUI has been moved to Ctrl-Alt-F1 instead of Ctrl-Alt-F7, and for a console log-in you need Ctrl-Alt-F2. I'm using F14 and I've just checked.
FYI, I jut upgraded my wife's system from F12 to F14, and I had to use the "basic video" installation mode because the Intel driver, used by default since her box has a Intel 915 video chipset on its mother board.
Because I'd installed using the "basic video" setting, the GRUB boot kernel lines were created with the nomodeset option on the line. So, when I tried to run startx with the Intel driver, I got the "No modeset kernel extensions" error, and no X-server. Changing the nomodeset to i915.modeset=1 fixed the problem, except that the initrd image loads its driver with the nomodeset option, so the screen is black while the system boots. (I could fix that by doing a mkinitrd omitting the video driver nonsense, but, for now, a couple minutes of "black screen" is no hardship. I can always run cat /var/log/boot.log if I suspect there was some problem during the boot.)
If you suspect that your problem is caused by a similar problem, run the command lspci -k | grep -A3 VGA to identify your hardware, and add the <hardware>.modeset=1 line to the kernel line in your /boot/grub/grub.conf file, where <hardware> is, of course, replace by the correct hardware name. (I haven't tried this, but just removing the nomodeset option might suffice.)
Last edited by PTrenholme; 02-21-2011 at 01:29 PM.