Re: Problem : was What exactly does this mean?
Jake McHenry wrote: > Could the problem I'm seeing be a harddrive that went bad? The bios counts all > the new memory. Now when I go in, it says Kernel Panic. Cannot mount root > partition. How can I test this? > > Thanks, > Jake You might try toms boot disk. Pretty complete linux on a floppy. He has done a good job getting abunch of stuff onto a single floppy. Once up, you can mount your hard disk partitions and look around. Bret ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Problem : was What exactly does this mean?
Could the problem I'm seeing be a harddrive that went bad? The bios counts all the new memory. Now when I go in, it says Kernel Panic. Cannot mount root partition. How can I test this? Thanks, Jake ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: What exactly does this mean???
Jake McHenry wrote: > > I just installed some more memory, and now this is happening when I boot, even > when I try to boot to single user mode. > > INIT: PANIC: segmentation violation at 0x2ec54! sleeping for 30 seconds. > > It is in a loop of this, and won't stop! I let it sit for 2 hours and it was > still doing the same thing. I didn't touch anything. I shut it down with > > shutdown -F -h now > > no big deal. Put in the new memory, powered back on. Bios finds all the memory, > I didn't see if in the boot process it saw it or not, but then this started > happening. > Have you tried taking the original memory out and booting with just the new memory? Perhaps your new stick of memory is bad or not compatible. What type of memory are we talking here, dimms, simms? What amount of memory are you trying to put in? Have you appended the amount in lilo? Sometimes if you add, say, 128 mb in lilo it will freak out the kernel because part of the first mb is being used. In that case you need to append 127 mb. hth, kent -- "Neurosis is the way of avoiding non-being by avoiding being." - Paul Tillich, American theologian (1886-1965). ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: What exactly does this mean???
On Thu, Oct 05, 2000 at 04:58:13PM -0400, Jake McHenry wrote: > > I just installed some more memory, and now this is happening when I boot, even > when I try to boot to single user mode. > > INIT: PANIC: segmentation violation at 0x2ec54! sleeping for 30 seconds. > > It is in a loop of this, and won't stop! I let it sit for 2 hours and it was > still doing the same thing. I didn't touch anything. I shut it down with > > shutdown -F -h now > > no big deal. Put in the new memory, powered back on. Bios finds all the memory, > I didn't see if in the boot process it saw it or not, but then this started > happening. > > What do I do? Firstly, take the new RAM back out and verify that your system returns to a normal working condition. Second, if that works, download a copy of memtest86 (from http://reality.sgi.com/cbrady/memtest86), make a bootable floppy from it, put the new memory back in and run memtest86 for several hours (overnight is good). Conjecture: You've got either BAD memory, or memory that your motherboard doesn't like. -- Fred Smith -- [EMAIL PROTECTED] "And he will be called Wonderful Counselor, Mighty God, Everlasting Father, Prince of Peace. Of the increase of his government there will be no end. He will reign on David's throne and over his kingdom, establishing and upholding it with justice and righteousness from that time on and forever." --- Isaiah 9:7 (niv) -- ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
What exactly does this mean???
I just installed some more memory, and now this is happening when I boot, even when I try to boot to single user mode. INIT: PANIC: segmentation violation at 0x2ec54! sleeping for 30 seconds. It is in a loop of this, and won't stop! I let it sit for 2 hours and it was still doing the same thing. I didn't touch anything. I shut it down with shutdown -F -h now no big deal. Put in the new memory, powered back on. Bios finds all the memory, I didn't see if in the boot process it saw it or not, but then this started happening. What do I do? Thanks, Jake McHenry ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
