RH6.1 Reboots durring instalation
ben hengst
server and news reader, nothing huge just an educational experement. the
reason that i am trying to install 6.1 is that i have a burnt copy (from
iso) and i'm tryng to do a minimal install to a 1g HDD I fgiggured that this
would be sufficent (slow but sufficent) but dirring the 'instalation of the
packets' the machene just reandomly reboots itself.. i have insalled linux
before and it went w/o a hitch (RH5.2 to a wintel box)
does any one have any clues??
thanks to all
ben heng...@osu.edu
William Baird
me) on what's happening:
I have a Sparc 2 that I've been trying to install RH6.1 on for a bit now.
It has one 4 GB drive, a 1 GB drive, and 32 MB ram.
It would appear to go fine until it locked up (consistantly) on the package
installation. As far as I could tell, there were bo error messages or
anything. It sucessfully partitioned the disk, but not installed anything.
After running back and forth from the phone (w/ redhat) and the system,
Redhat finally stated that there was a known problem with the current
cdrom iso has a problem (I suppose actually the kernel or installer)
in the form of a memory leak. If you have less than 128 MB of memory...:/
They claim it will be fixed in the next ISO.
Will
--
Will Baird email: wba...@acca.nmsu.edu http://acca.nmsu.edu/~wbaird/
Phantoms! Whenever I think I fully understand mankind's purpose on earth...
suddenly I see phantoms dancing in the shadows...[saying] pointly as words,
"What you know is nothing little man; what you have to learn, immense." - CD
Barbie LeVile
>
> Well, maybe I can lend a little bit of light (as much as redhat has shared with
> me) on what's happening:
>
> I have a Sparc 2 that I've been trying to install RH6.1 on for a bit now.
> It has one 4 GB drive, a 1 GB drive, and 32 MB ram.
>
> It would appear to go fine until it locked up (consistantly) on the package
> installation. As far as I could tell, there were bo error messages or
> anything. It sucessfully partitioned the disk, but not installed anything.
>
> After running back and forth from the phone (w/ redhat) and the system,
> Redhat finally stated that there was a known problem with the current
> cdrom iso has a problem (I suppose actually the kernel or installer)
> in the form of a memory leak. If you have less than 128 MB of memory...:/
>
mode, worked for me.
SS2/64mb/2.3gigs
but well, it was not worth the efford, but thats another thing
--
Barbie - Prayers are like junkmail for Jesus
"One World, One Web, One Program" - Microsoft Promotional Ad
"Ein Volk, Ein Reich, Ein Führer" - Adolf Hitler
bar...@toppoint.de http://www.amigaworld.com/barbie/index.html
SRGC 0.22: SR1 SR2+++ SR3--- h++++ b++ b--- UB++ IE- RN+ SR_D+++ W++
dk sh++++ ri++++ sa+++ ad+++ m+++(x+++) gm++ m+++ P+++(P*)
Stuart Butterfield
: >
: > It would appear to go fine until it locked up (consistantly) on the package
: > installation. As far as I could tell, there were bo error messages or
: > anything. It sucessfully partitioned the disk, but not installed anything.
: >
: > After running back and forth from the phone (w/ redhat) and the system,
: > Redhat finally stated that there was a known problem with the current
: > cdrom iso has a problem (I suppose actually the kernel or installer)
Barbie, I have exactly the same problem. After spending taking ages
to sort out how to get my old Sparc 1 to RARP/TFTP boot from my PC
Linux box, I was very annoyed when the installed crashed part way
through stage 2, as you said, at the package selection stage.
Have you heard any more on this? Is there an update?
I'd appreciate any information.
All the best.
Stuart
Barbie LeVile
>
> Barbie, I have exactly the same problem. After spending taking ages
> to sort out how to get my old Sparc 1 to RARP/TFTP boot from my PC
> Linux box, I was very annoyed when the installed crashed part way
> through stage 2, as you said, at the package selection stage.
>
> Have you heard any more on this? Is there an update?
>
> I'd appreciate any information.
>
boot it from the boot floppy image on the rh6.1cd, and run the install in
text mode, worked for me.
Stuart Butterfield
:
: you have a few options, use rh6.0 and update the distro then online,
Yep, I've got 6.0 on there already, but wanted to do a proper clean
new install. If I have to upgrade, so be it.
: boot it from the boot floppy image on the rh6.1cd, and run the install in
: text mode, worked for me.
: its supposed to be fixed in rh6.2
Understood, I'll give this a try.
Thanks for your help.
Stuart
Byron Smith
system format. But I also had 128megs of RAM (64megs onboard and 64megs on an sbus
addon) and it would just hang for a minute or 2. Then it worked fine. So it sounds
like a memory problem to me....
That was my 2 cents for the day.........
SysMatrix
Barbie LeVile wrote:
> William Baird wrote:
> >
> > Well, maybe I can lend a little bit of light (as much as redhat has shared with
> > me) on what's happening:
> >
> > I have a Sparc 2 that I've been trying to install RH6.1 on for a bit now.
> > It has one 4 GB drive, a 1 GB drive, and 32 MB ram.
> >
> > It would appear to go fine until it locked up (consistantly) on the package
> > installation. As far as I could tell, there were bo error messages or
> > anything. It sucessfully partitioned the disk, but not installed anything.
> >
> > After running back and forth from the phone (w/ redhat) and the system,
> > Redhat finally stated that there was a known problem with the current
> > cdrom iso has a problem (I suppose actually the kernel or installer)
> > in the form of a memory leak. If you have less than 128 MB of memory...:/
> >
> you can run the install from the floppy image on the cd when using text
> mode, worked for me.
> SS2/64mb/2.3gigs
> but well, it was not worth the efford, but thats another thing
>
Greg Leblanc
Byron Smith <sysm...@pernet.net> wrote:
> I installed RH6.1 fine on my SS2. I did notice that it would hang on
the file
> system format. But I also had 128megs of RAM (64megs onboard and
64megs on an sbus
> addon) and it would just hang for a minute or 2. Then it worked fine.
So it sounds
> like a memory problem to me....
Maybe it was just taking it's dear sweet time? Formatting is based on
disk access speed, right? Since on my SS20 disk read speed maxes out at
about 3.5MB/sec (the disk itself is capable of 7+MB/sec), and writes are
under 3MB/sec (post if you want the numbers), it could take a REALLY
long time to format.
[snip]
Greg
--
It's pronounced "sexy" not "scuzzy"!
Sent via Deja.com http://www.deja.com/
Before you buy.
Tandem&Unisys Utility
>
> > William Baird wrote:
> > >
> > > Well, maybe I can lend a little bit of light (as much as redhat has shared with
> > > me) on what's happening:
> > >
> > > I have a Sparc 2 that I've been trying to install RH6.1 on for a bit now.
> > > It has one 4 GB drive, a 1 GB drive, and 32 MB ram.
> > >
> > > It would appear to go fine until it locked up (consistantly) on the package
> > > installation. As far as I could tell, there were bo error messages or
> > > anything. It sucessfully partitioned the disk, but not installed anything.
> > >
> > > After running back and forth from the phone (w/ redhat) and the system,
> > > Redhat finally stated that there was a known problem with the current
> > > cdrom iso has a problem (I suppose actually the kernel or installer)
> > > in the form of a memory leak. If you have less than 128 MB of memory...:/
> > >
> > you can run the install from the floppy image on the cd when using text
> > mode, worked for me.
> > SS2/64mb/2.3gigs
> > but well, it was not worth the efford, but thats another thing
> >
> > --
We still get the same failure (ldconfig install hangs) even when running booting
from floppy. Does it make any difference if we allocate larger swap space -
does
this get used during the install?
Or should we be performing the instal sime other way?
We have Sun Sparc IPX 64Mb and not much disc space (400Mb + 850Mb)
Cliff Mould
(Amiga user too)
Tandem&Unisys Utility
We also have 64 Mb RAM but I have read the installation fails if it has
less than 128Mb. Trouble is, with 64Mb the new SWAP space you allocate doesnt
get used
during the installlation.
So what we did was...
1) REDUCE your physical memory to 32Mb.
This causes the install to use the SWAP space immediately after you set up
the partitions so it can perfomr the install.
2) Also set the SWAP space to 128Mb.
That way you have at least 128Mb total memory.
It worked for us and installed fine.
You can then replace the full 64 MB RAM
Cliff