Michael, I didn't see the beginning of this thread, so I may be off base
with this, but ...
I had a problem installing 7.0; I elected the command line option, i.e., I
just got a prompt upon coming up. I needed to do the "startx" on my own.
Upon the "startx" I received a XFree server error which would throw me back
to the command line. Turns out the X Windows setup did not work correctly.
All I had to do was to use Xconfigurator to go through the monitor and video
card setup once again. And then everything worked.
I apologize if this is from left field. You said something about starting X
so I thought this may be applicable.
----- Original Message -----
From: "Michael McLeod" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, March 18, 2001 6:55 PM
Subject: Re: RH 7 won't boot
> I had the opportunity to try another Hard drive, same problem. Can
anybody give
> me some insight on this strange problem?
> Thanks Michael
>
> Michael McLeod wrote:
>
> > The diagnostic utility is one that Western Digital has on their web
site. I
> > ran it again and this time had it write "0's" over the entire drive and
then
> > read them, no errors were found. Since this destroyed all data I tried
> > loading RH6, this went off without a hitch and ran fine. So, then I
tried
> > an upgrade to RH7. The upgrade completed ok but would boot to the logon
> > screen and then attempt to start "X" but has same problem. There are
> > sometimes errors reported during the boot process and sometimes it hangs
at
> > various points. But, for now the "Always Happens" error is the one
about
> > gdm already running. Could I have gotten a defective CD from Red Hat?
> > Seems strange that RH6 works or and RH 7 does not.
> > MIchael
> >
> > Michael McLeod wrote:
> >
> > > Not long after RH 7 was released I did a fresh install on my computer
> > > (not an Up grade) Everything worked well then about 2 months ago
Loadlin
> > > stopped working, that is, the boot process would hang someplace
> > > especially when X went to startup. The screen would just flash about
> > > every 10 seconds and finally display a message something like:
> > > .../var/run/gdm.pid gdm already running but seems to have been
murdered
> > > mysteriously
> > > this would be repeated again after about 20 seconds, finally the
> > > following messaged would be displayed:
> > > INIT:Id "x" respawnind to fast: disabled for 5 mi.
> > > I could still boot from Lilo or from disk. Then a few weeks later I
> > > could not boot from disk only Lilo.
> > > Since I am still in the experimental stage with Linux I just decided
to
> > > remove and reload the whole program. Well now it won't ever boot from
> > > disk and only 1/2 the time will it boot from Lilo.
> > > Linux lives in it's own 2 Gb hard drive, Western Digital, and I have
> > > run diagnostics on it all is OK. I have reviewed the Cmos settings,
> > > nothing seems to have changed. I have checked the 128 Meg of ram ant
it
> > > is ok. Winblows works fine on the other Hard drive. What could be
> > > going on? I'm really stuck, and new to Linux
> > > Michael
> > >
> > > _______________________________________________
> > > Redhat-list mailing list
> > > [EMAIL PROTECTED]
> > > https://listman.redhat.com/mailman/listinfo/redhat-list
> >
> > _______________________________________________
> > Redhat-list mailing list
> > [EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/redhat-list
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
