Adding more memory, system won't boot.

Adding more memory, system won't boot.

Post by Stephen Tanto » Sat, 07 Feb 1998 04:00:00



I added two new SIMMs to my system bringing it from 32M to 64.  But...
now linux
does not want to boot, It just sticks at starting kswapd.  Win95 didn't
seem to mind
at all.  I'm running Redhat 4.2 on a Aptiva S78 Pentium 200.  If anyone
could tell me
how I could get my system going again without reinstalling ( I just did
this not too long
ago ) I would greatly appreciate it.

S. T.

 
 
 

Adding more memory, system won't boot.

Post by Stephen Tanto » Sat, 07 Feb 1998 04:00:00


I added two new SIMMs to my system bringing it from 32M to 64.  But...
now linux
does not want to boot, It just sticks at starting kswapd.  Win95 didn't
seem to mind
at all.  I'm running Redhat 4.2 on a Aptiva S78 Pentium 200.  If anyone
could tell me
how I could get my system going again without reinstalling ( I just did
this not too long
ago ) I would greatly appreciate it.

S. T.

 
 
 

Adding more memory, system won't boot.

Post by gerald clar » Sat, 07 Feb 1998 04:00:00



> I added two new SIMMs to my system bringing it from 32M to 64.  But...
> now linux
> does not want to boot, It just sticks at starting kswapd.  Win95 didn't
> seem to mind
> at all.  I'm running Redhat 4.2 on a Aptiva S78 Pentium 200.  If anyone
> could tell me
> how I could get my system going again without reinstalling ( I just did
> this not too long
> ago ) I would greatly appreciate it.

> S. T.

Remove the SIMMS and see what happens.
--
Remove the -bogus- portions of my return address!
 
 
 

Adding more memory, system won't boot.

Post by Michael & Kristen Erns » Sun, 15 Feb 1998 04:00:00




>Remove the SIMMS and see what happens.
>--
>Remove the -bogus- portions of my return address!

I am having the same problem, RH4.2 going from 32 to 48MB.  Mine stops at
EXT2-fs error: group descriptor corrupted.  I have since went back to my
original 32MB and get the same error.  What gives?


 
 
 

1. adding memory and now linux won't boot

i have been running linux 1.1.64 for many months on a gw2000 minidesktop
486 with 8 meg's of memory.  i added an additional 8 meg's last week and
got cmos and dos to accept it.  when i tried to boot from my lilo floppy,
the system got as far as the file system checking, and then a register dump
appeared on the screen - a copy appears below;
unable to handle kernek NULL pointers deference at virtual address c0000001
current -> tss.cr3 = 00f51000, %cr3=00f51000
*pde=00102027
*pte=00000027
Oops=0002
EIP  0010:001669c4
eax:0019281c ebx:00000058 ecx:00000100 edx:000001f0 esi:00000001 es:0018
fs:0026 gs:002b ss:0018
corrupted stack pase
process fsch.ext2(pid:5, processor mr:4, stackpage=00f52000)
stacks 00000400 00e53878 006e078 00f52e74 0000000c
code: f3 66 6d 01 70 0c 89 f0 c1 e0 09 8b 15 9c 5b 18 00 01 42 18
Aiee, killing interrupt handler
release: fsck ext2 kernel stack corruption
remounting ...

and then the hard disk just spins.

please advise me as the proper course of action.  i miss not being able
to boot my linux system.  i'm an unix novice and would hate to think i just
wasted $300.   i was also considering upgrading my cache from 64k to 256k,
but after the above fiasco, i'm not so sure.

thanks for any assistance you might provide.
sincerely;
m

2. DNS Configuration

3. FreeBSD 4.2 won't boot - 'read error' on boot after install

4. Converting pseudo-tty to IP Address

5. System won't boot: Error message can't get /dev/console for controlling terminal

6. WABI & Solaris 2.5 ??

7. U5 won't boot from CD after adding 2nd HD

8. Need HP 540 printer driver

9. HELP!!! won't boot after adding RAM

10. Newbie Q: Added partition, linux won't boot

11. Added Memory - Now Can't Boot ???

12. Added SCSI and Linux won't boot!

13. Cloned a Sparc20 disk and Sparc10 won't boot off it without more memory.