Re: RedHat9 and my Cyrix-chip machine conflict (?)

[Bob McClure Jr <robertmcclure earthlink net>]

Sure wish you guys would

- Bottom post / top quote.  I'm having a heckuva time trying to figure
  out the sequence, here.

- Trim out the fat such as list footers and such.

I'll try to rearrange this and provide some useful comments.

On Wed, Oct 15, 2003 at 07:05:04PM -0400, Ocutique CTO wrote:
> ----- Original Message -----
> From: "Ocutique CTO" <ocutqcto twcny rr com>
> To: <redhat-install-list redhat com>
> Sent: Wednesday, October 15, 2003 12:07 PM
> Subject: Re: RedHat9 and my Cyrix-chip machine conflict (?)
> 
> 
> > Mr. Putra,
> >      Thanks for the info.  I'm not sure if i made this clear or not.  I'm
> > installing red hat 9.  As soon as it actually starts the package install
> > thats when im getting the error that gblic-common is failing.  So I'm not
> > sure if i will even have a text editor.  Do i go into the shell and try to
> > edit that file before i click the last next before the install?
> > thanks
> > ocutique
> > ----- Original Message -----
> > From: "Jhon Ramawi Putra" <jhonrp pamapersada com>
> > To: <redhat-install-list redhat com>
> > Sent: Wednesday, October 15, 2003 12:10 AM
> > Subject: Re: RedHat9 and my Cyrix-chip machine conflict (?)
> >
> >
> > > Hi Ocutique,
> > >
> > > There are a lot of ways to edit the file. If you want to edit from the
> > > shell, you can use "vi" text editor. Vi looks like "edit" in ms.
> windows,
> > > but without menu bar, so you have to remember the common commands of vi.
> > > But, if you prefer use a GUI Interface Text Editor, there are alot of
> text
> > > editor in RH9. After decide which program to use, then edit the files.
> > >
> > > Cheers,
> > >
> > > Jhon R Putra
> > >
> > > Note:
> > > some vi command:
> > > #>vi filename.ext (open filename.ext)
> > > When vi active :
> > > /kernel ==> to find word "kernel"
> > > /      ==> to find another location in file with last search string
> > > i      ==> to enter edit mode
> > > [esc]  ==> to enter browse mode
> > > x      ==> "del" function
> > > :w     ==> command write to file
> > > :q!    ==> command to close file without save
> > > :wq!   ==> command to close and save file
> > >
> > > -------------> there are alot of functions you can use, just see the
> > > manual page (man vi)
> > >
> > >
> > >
> > >
> > >
> > > "Ocutique CTO" <ocutqcto twcny rr com>
> > > Sent by: redhat-install-list-admin redhat com
> > > 15/10/2003 10:43
> > > Please respond to
> > > redhat-install-list redhat com
> > >
> > >
> > > To
> > > <redhat-install-list redhat com>
> > > cc
> > >
> > > Subject
> > > Re: RedHat9 and my Cyrix-chip machine conflict (?)
> > >
> > >
> > >
> > >
> > >
> > >
> > > How do I edit that file from the shell?  At what point during the
> install
> > > do
> > > I edit it?
> > > Thanks
> > > Ocutique
> > > ----- Original Message -----
> > > From: "Matthew Smith" <shaggydog3 yahoo com>
> > > To: <redhat-install-list redhat com>
> > > Sent: Tuesday, October 14, 2003 10:52 PM
> > > Subject: Re: RedHat9 and my Cyrix-chip machine conflict (?)
> > >
> > >
> > > > > >>
> > > > > >>Edit your /boot/grub/grub.conf file, find the
> > > > > >>"kernel" line for
> > > > > >>the kernel you're booting and add " noapic" to the
> > > > > >>end of the line:
> > > > > >>
> > > > > >>kernel /boot/vmlinuz-2.4.20-20.9 ro root=/dev/hda1
> > > > > >>hdd=ide-scsi noapic
> > > > > >>
> > > > > >>If you use grub, edit /etc/lilo.conf, find the
> > > > > >>clause that describes
> > > > > >>your kernel and add the line:
> > > > > >>
> > > > > >> append="noapic"
> > > > > >>
> > > > > >>to the end of the stanza.  If there is already an
> > > > > >>append line, add
> > > > > >>a space followed by "noapic" to it:
> > > > > >>
> > > > > >> append="hdc=ide-scsi noapic"
> > > > > >>
> > > > > >>then rerun lilo.
> > > > > >
> > > > > >
> > > > > > Thanks, my server thanks you too :)
> > > > >
> > > > > So I take it that it works now? ;-)
> > > >
> > > > Not sure if I responded already, but yep, it's working
> > > > great.  Thanks for the help :)
> > > >
> > > > Cheers,
> > > > Matt
> 
> There was an error installing glibc-common-2.3.2.5.  This can indicate media
> failure, lack of disk space, and/or hardware problems.  This is a fatal
> error and your install will be aborted.  Please verify your media and try
> your install again.
> 
> Thats the error message.  I tried installing lilo instead of grub.  Any more
> ideas.  I tried to edit those files but there was nothing in them.
> 
> Matt

Well, I gave up.  There was so dang much top posting going on that
I've not a clue who said what to whom.  Nevertheless, I'll give it a
shot.

The error given above is a bit of a red herring because it is a
"shotgun" answer, nearly all of whose possible causes are not the
problem.  The most common causes of this error are (not necessarily in
any particular order):

- Installing to ext3 filesystems (the default).  The install kernel is
  fragile about that.  (Beats me why they haven't fixed it.)  Instead,
  install to ext2 filesystems, and convert to ext3 afterwards.  See

http://www.rhil.net/docs/ext2-to-ext3.html

  for more details.

- Brain-damaged handling of DMA - that's a hardware problem.  Boot
  with "linux ide=nodma".  Users of SMP- or Athlon-based mobos may
  need to add "noapic".  The installed kernel may well work around the
  DMA problem better.

See http://www.rhil.net/docs/faq.html#install_dies for more clues.

Cheers,
-- 
Bob McClure, Jr.             Bobcat Open Systems, Inc.
robertmcclure earthlink net  http://www.bobcatos.com
Everyone wants to harvest, but few want to plow.