FC6 boot issue
 

hi every one i need some help in solving my problem.

when ever system is put on every thing is going right up to starting_udev after that nothing is displayed .....

but iam managing with kernel parameter mode=vesa.
i got this solution some where in forums

what might be the error is and why we are using mode=vesa kernel parameter

each and every time when i am giving mode=vesa first boot program is running ....


please some one help me .....

I'm a little confused. This is the first time you are trying to start it after an install? You could always throw a ' 3' at the end of your boot line and then check the logs.

hi nomb

no, there is no problem after the installation.
after 2-3 boots this problem rises

there is noting there in log files not even any thing about the booting also.

mode=vesa has to do with your graphics card. Which card do you have? Which driver is currently installed?

Also might be an idea to set which distro you're on in your LQ properties.

I've noticed it too - every once in a while (usually after rebooting because it hangs about half-way through "retrieving updates") it chokes immediately after udev. Still need to try the " 3" trick, but I'm assuming it's a "feature".

Turn the box off then back on, append "-single", get the firstboot garbage, and all is hunky-dory - until I try to get updates again!

(probably ought to start a new thread on that though)

monsm, what if my distro is "whatever I feel like loading this week"? ;-)

People, in a normal Fedora boot, the graphical boot screen is started when UDEV finishes, so the problem the OP reported was that the X system did not start correctly. Since the OP stated that the screen blanked and nothing happened after that, I'd suspect that the video card had been asked, by the X system, to display in a format (usually frequency) not supported by the monitor being used. (That suspicion is because a failure to start the X-system just gives you a boot to the login screen instead of the graphical boot. The suspicion could be confirmed by noting if the drive activity indicator light continues to "flicker" whilst the screen remains blank.)

As was noted, using the "vesa" option forces X to assume that your monitor/driver/video-card combination is a fairly old "enhanced VGA" type, which is a set of modes and frequencies that (almost) every monitor/driver/video-card combination supports.

The correct settings for the specific monitor, driver, and video card being used should be reviewed and corrected as necessary.

any one of u suggest me what updates i have to do for FC6

my monitor is samsung 17' flat
845Mother Board

PTrenholme;

I figured as much, since it went from "starting udev...[ok]" to blank screen. What I find odd is that sometimes, jiggling the mouse as it's going through the boot process sometimes seems to keep the process running.

(I'm reminded of a movie scene in which a guy unfamiliar with modern conveniences flushes a toilet, and the phone rings - totally unrelated, but if coincidence happens often enough, ya gotta wonder!)

I don't know about the OP, but on mine when it stops, it *stops* - no drive activity light "flicker", and if I leave it alone I can eventually hear the drives spin down. I don't know why passing " -single" works, but in my case it does. As with all intermittents, it doesn't happen often enough to be a problem, just often enough to be annoying when it does happen.

Not sure about the graphics, since it's onboard - system reports "Brookdale-G graphics chip", nothing else. Monitor is a Gateway EV700 (yeah, "boat anchor") :-)

neelendhar;

Updates on? If you mean software updates, I'd do them all, because I've done piecemeal updates, and sooner or later you reach a point where updating one thing breaks another. System Updater will do it. If you mean hardware updates, you might check the HCL at http://www.linuxquestions.org/hcl/

Sanc.

I am on PTrenholme side.

It is common for a Linux to have a mismatched video driver after a "perfect" installation. This is to say the installer seems to display the video screen faultlessly but the installed version fails completely.

I would just edit X configuration file and use "vesa" as the driver.

I had this issue an an old Sony Vaio with an intel 815 chipset. The issue wasn't in the "Driver" section of xorg.conf (set to i810) but in the "Monitor" section. I needed to track down the specs on the screen and put in horizontal sync & vertical refresh manually.

PT is right, as long as the screen is staying black, X is starting properly, just outside the range of the monitor/lcd. This is sometimes an issue even with the vesa driver.