Re: *ALMOST* longing for Windows stability

Lonni J Friedman wrote:
On 12/6/06, Craig White <craigwhite@xxxxxxxxxxx> wrote:
On Wed, 2006-12-06 at 09:05 -0600, Michael Satterwhite wrote:
Lonni J Friedman wrote:
On 12/5/06, Michael Satterwhite <michael@xxxxxxxxxxx> wrote:
About an hour ago, I logged off my kde session. My LCD monitor
immediately went to a black screen - with no way of logging back
in -
when the session ended.

It took me 8 (eight) times going through a reboot process before
I could
get FC5 to present me with a login screen. The first 7 times, I got
either a black screen or an "Out of Range" error. Finally, it
presented
me with a login screen and I was able to get the system up.

I *KNOW* this isn't typical ... if it were, no one on the face of
the
planet would be running Fedora. Unfortunately, that doesn't make
my life
any easier - it is happening here.

There are some real experts here. I know, they've helped me out with
other problems. Does anyone know how to fix this? While a real
fix is
what's needed, even a bypass - a way to get back to a login
screen when
the system is acting up - would be a tremendous improvement.

It sounds like X is hanging/crashing. Can you boot to runlevel 3
successfully/reliably? if so, then you should do so, start X
manually, and grab the X log to review.

I really hate to show ignorance, but it's never stopped me before. From
the grub screen, how do I get it to boot to runlevel 3? I'm more than
willing to get information to help people help me.

I'd agree with the crash when I get the black screen, but I'm not sure
how that would cause the "Out of Range" errors.
----
Press 'e' at initial grub screen. Use arrow keys to move to 'kernel'
line. Press 'e' to edit

Add to end of line ' linux 3'
Press 'Enter' to save
Press 'b' to boot

or

After bootup, Press <Control><Alt><F2> to get a virtual console. Login
as root. Type 'init 3' and press enter (type 'init 5' to return to
runlevel 5 when you are done).

If you are at runlevel 3, you can probably just fix the setup anyway by
typing...

system-config-display --reconfig

I suspect that your 'sync' rates are set too high for your LCD which is
why I suggested that you post

It seems highly unlikely that the problem is xorg.conf, as he stated
that it works fine some small percentage of the time. Something bad
is happening elsewhere.

Adding to it, a Google shows that this has been seen by other people ...
and not necessarily all Fedora users. I know that my Windows 2000 boot
comes up 100% of the time. Before I did a switch, my Kubuntu 5.1 system
came up 100% of the time and didn't crash at logoff. I'll agree that
something is happening somewhere (I love being specific <g>), but I
haven't the foggiest what or where. That's why I turned to the experts
here. The amount of knowledge in this user base is astounding.



--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: *ALMOST* longing for Windows stability
    ... how do I get it to boot to runlevel 3? ... >> runlevel 5 when you are done). ... >> If you are at runlevel 3, you can probably just fix the setup anyway by ... and not necessarily all Fedora users. ...
    (Fedora)
  • Re: FC4 does not work, "out of the box" for me; GUI/X11 fails
    ... >4) When it reboots one of two things came up for me: ... When you boot into the rescue mode, after chrooting, you ... > to get into runlevel 3 and yum update and my problems could have ...
    (Fedora)
  • Unable to start a windows manager - need help
    ... When I boot it seems to boot clean but when it tries to go graphical it ... runlevel 5 has been reached ... Mar 3 20:08:48 linux kernel: bootsplash: status on console 0 changed to on ... Mar 3 20:08:48 linux kernel: bootsplash: silent jpeg found. ...
    (alt.os.linux.suse)
  • Re: [SLE] boot freeze and black screen
    ... >this stage the screen goes black and nothings else happens. ... log in as root on that tty and switch to runlevel 3. ... or you can examine the boot and system logs. ... probable reason is that the video driver is somehow corrupted (did you ...
    (SuSE)
  • Re: boot: linux single
    ... > which runlevel to boot into. ... you could type single which ... > you are now in full control to type any command you want. ...
    (linux.redhat)