I only suggested a reinstall because there appears to be a number of things 
wrong with Frank's system. I don't know if they are all Aurora-related, and 
I'm not sure if they will all go away once Aurora is uninstalled. Often, a 
system can look fine even when it isn't (and is slowly dying). Aurora (or 
something else) _may_ (I'm not sure) have damaged the system configuration in 
some way. An Aurora uninstall may give the appearance of a cure, but there 
may still be some subtle problems. Because of this, a clean reinstall is the 
safest thing to do.

On Sat, 28 Jul 2001 18:52, Jose M. Sanchez wrote:
> HUH???? That's a pretty long way to go IMHO...
>
> Why not just boot into text mode and
>
> "rpm -e 'rpm -qa | grep aurora'"
>
> -JMS
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Sridhar Dhanapalan
> Sent: Friday, July 27, 2001 9:31 AM
> To: James S Bear; [EMAIL PROTECTED]
> Cc: NEWBIE Mandrake List
> Subject: Re: [newbie] Strange X problem I have never had before. (damn
> thing crashed again.)
>
>
> Don't use Aurora -- it's more trouble than it's worth. Do a fresh
> reinstall
> (just in case), making sure to format (but _don't_ low-level format as
> James
> suggested below!) the partition before installing. When you get to
> choose the
> boot loader, choose either LILO or GRUB, but _without_ graphics (i.e.
> text-only). Your bootup may not look as pretty but at least it should
> work.
>
> On Fri, 27 Jul 2001 12:13, James S Bear wrote:
> > I've had this same problem.  The only way I've found to cure it is to
> > do a low-level format and start all over.  This brings to my mind a
> > question:
> >
> > How efficient is the formatting of ext2?  Compared to a dos format, it
> >
> > takes next to no time.  I've always been taught that haste makes
> > waste, but I understand that possibly it is just easier to format
> > ext2.  Can anybody explain to me why it takes so much less time to
> > format ext2?
> >
> > jim
> >
> > Quoting Franki <[EMAIL PROTECTED]>:
> > > Hi guys,
> > >
> > > just wondering if anyone can give me any ideas on this:
> > >
> > > The system:
> > > 200 Ppro
> > > 64mb ram.
> > > S3Virge 2MB
> > > ReiserFS
> > >
> > >
> > > The Problem:
> > >
> > > System boots in vga=788 mode with Aurora perfectly.
> > >
> > > when starting x, (after using drakconf and trying progressively
> > > lower res and color) the system locks up tight..
> > >
> > > monitor starts flashing "no sync signal" and CTRL-ALT-DEL, or
> > > CTRL-ALT-BACKSPACE or anything else works either..
> > >
> > > altough the number lock and caps key lights are still working, so it
> > >
> > > doesn't look like a total lockup..
> > >
> > >
> > > can't switch to another terminal either..
> > >
> > >
> > > Latest problem, after another crash, this time haing tried 640x480
> > > bit,,, the system is reporting this no boot (unsucessful boot I
> > > might add.
> > >
> > > INIT: version 2.78 booting
> > > INIT: /etc/inittab[6]: id field too long (max 4 characters)
> > > INIT: /etc/inittab[7]: id missing action field
> > >
> > > a heap of other stuff like that,,, then :
> > >
> > > Enter runlevel:
> > >
> > > no mater what I select, it tells me "INIT: no more processes left on
> > >
> > > this runlevel"
> > >
> > >
> > >
> > > anyone know how to fix that? I have just reinstalled this thing 3
> > > times, don't want to make it 4 if it can be avoided..
> > >
> > >
> > > The daft thing was, I had KDE running perfectly, had upgraded the
> > > kernel to 2.2.19 and did all my usual config stuff..
> > >
> > > Then I tried to load aurora, got that working, then X disappeared,
> > > and now it appears that I have had a data coruption as well.
> > >
> > > This is not going well at all...
> > >
> > >
> > > any help, suggestions, general cursing,, anything at all is most
> > > welcome..
> > >
> > >
> > > regards
> > >
> > > Frank
> >
> > Ignorance is underrated

-- 
Sridhar Dhanapalan.
        "There are two major products that come from Berkeley:
        LSD and UNIX. We don't believe this to be a coincidence."
                -- Jeremy S. Anderson


Reply via email to