On Thu, Jun 13, 2002 at 07:13:24AM -0400, Tom Allison wrote:
| This isn't an adequate engineering solution to the problem since it is
| contrary to what I understood about the liloconfig system.
| What does work is: linux mem=768M
| What was in lilo.conf that I removed was 'append "mem=128M" an
Ron Johnson wrote:
On Wed, 2002-06-12 at 20:13, Tom Allison wrote:
Tom Allison wrote:
I got a really interesting one.
I am running a stock K7 kernel from woody.
I recall seeing such things as cramfs, VFS, and initrd during the boot
sequence.
[snip]
Freeing initrd memory: 2700k freed
V
On Wed, 2002-06-12 at 20:13, Tom Allison wrote:
> Tom Allison wrote:
>
> > I got a really interesting one.
> >
> > I am running a stock K7 kernel from woody.
> > I recall seeing such things as cramfs, VFS, and initrd during the boot
> > sequence.
[snip]
> Freeing initrd memory: 2700k freed
> VFS:
On Wed, Jun 12, 2002 at 08:48:01PM -0400, Tom Allison wrote:
| Derrick 'dman' Hudson wrote:
| >On Wed, Jun 12, 2002 at 06:51:17PM -0400, Tom Allison wrote:
| >| The failure during boot is where the VFS fails to find the device at the
| >| address/location specified.
| >
| >How about double-checki
On Wed, Jun 12, 2002 at 10:07:40PM -0400, Joe Landman wrote:
| On Wed, 2002-06-12 at 21:13, Tom Allison wrote:
|
| > devfs: v1.10 (20020120) Richard Gooch
| > devfs: boot_options: 0x0
|
| No matter what else is a problem, the above is also very much a problem.
|
| Just say no to devfs.
I've bee
On Wed, 2002-06-12 at 20:48, Tom Allison wrote:
> >>I upgraded my RAM to replace the current 128M to 768M
> >>
> >>Now, when I boot it panics with a message that VFS can't mount
> >>the root device at 03:02.
> >>
> >
> >
> I selected the limit of 768M based on conversations with the MOBO MFG
> a
On Wed, 2002-06-12 at 21:13, Tom Allison wrote:
> devfs: v1.10 (20020120) Richard Gooch
> devfs: boot_options: 0x0
No matter what else is a problem, the above is also very much a problem.
Just say no to devfs. It mucks with device things in ways that cause
exactly the sort of problem you have.
Tom Allison wrote:
I got a really interesting one.
I am running a stock K7 kernel from woody.
I recall seeing such things as cramfs, VFS, and initrd during the boot
sequence.
I upgraded my RAM to replace the current 128M to 768M
Now, when I boot it panics with a message that VFS can't mount
Gerhard Gaussling wrote:
Am Mittwoch, 12. Juni 2002 22:51 schrieb Tom Allison:
I got a really interesting one.
I am running a stock K7 kernel from woody.
I recall seeing such things as cramfs, VFS, and initrd during the
boot sequence.
I upgraded my RAM to replace the current 128M to 768M
No
Derrick 'dman' Hudson wrote:
On Wed, Jun 12, 2002 at 06:51:17PM -0400, Tom Allison wrote:
| I figured out the floppy boot for memtest86.bin. It's running now (wall
| time == 1:12:24 elapsed).
| I am currently on test #7 of ??? and have no errors. I assume that it's
| at least nothing obviou
On Wed, 12 Jun 2002, Jamin W. Collins wrote:
> On Wed, 12 Jun 2002 19:01:24 -0500
> "Derrick 'dman' Hudson" <[EMAIL PROTECTED]> wrote:
>
> > memtest86 runs forever (until you stop it). You determine when you
> > think it's run long enough to elminate the possibility/probability of
> > errors.
>
On Wed, 12 Jun 2002 19:01:24 -0500
"Derrick 'dman' Hudson" <[EMAIL PROTECTED]> wrote:
> memtest86 runs forever (until you stop it). You determine when you
> think it's run long enough to elminate the possibility/probability of
> errors.
Not quite. Memtest86 will run all of it's test infinitely,
Am Mittwoch, 12. Juni 2002 22:51 schrieb Tom Allison:
> I got a really interesting one.
>
> I am running a stock K7 kernel from woody.
> I recall seeing such things as cramfs, VFS, and initrd during the
> boot sequence.
>
> I upgraded my RAM to replace the current 128M to 768M
>
> Now, when I boot
On Wed, Jun 12, 2002 at 06:51:17PM -0400, Tom Allison wrote:
| I figured out the floppy boot for memtest86.bin. It's running now (wall
| time == 1:12:24 elapsed).
| I am currently on test #7 of ??? and have no errors. I assume that it's
| at least nothing obviously wrong with the RAM.
memtest
Gary Hennigan wrote:
"Jamin W.Collins" <[EMAIL PROTECTED]> writes:
On Wed, 12 Jun 2002 16:51:06 -0400
"Tom Allison" <[EMAIL PROTECTED]> wrote:
I got a really interesting one.
I am running a stock K7 kernel from woody.
I recall seeing such things as cramfs, VFS, and initrd during the boot
s
On Wed, Jun 12, 2002 at 05:06:59PM -0400, Tom Allison wrote:
| Jamin W. Collins wrote:
| >Have you tested the new memory? Memtest86 is a great tool for doing just
| >this.
|
| I tried loading this in lilo and I got a fatal error that the kernel
| doesn't support ram disks
I suspect your lil
On Wed, Jun 12, 2002 at 04:59:14PM -0400, Tom Allison wrote:
> >Have you tested the new memory? Memtest86 is a great tool for doing just
> >this.
>
> I can't get it to boot in order to test it.
> I was assuming that since it was detected and was able to start booting
> from /dev/hda that it was i
On Wed, 2002-06-12 at 15:50, Jamin W.Collins wrote:
> On Wed, 12 Jun 2002 16:51:06 -0400
> "Tom Allison" <[EMAIL PROTECTED]> wrote:
>
> > I got a really interesting one.
> >
> > I am running a stock K7 kernel from woody.
> > I recall seeing such things as cramfs, VFS, and initrd during the boot
"Jamin W.Collins" <[EMAIL PROTECTED]> writes:
> On Wed, 12 Jun 2002 16:51:06 -0400
> "Tom Allison" <[EMAIL PROTECTED]> wrote:
>
> > I got a really interesting one.
> >
> > I am running a stock K7 kernel from woody.
> > I recall seeing such things as cramfs, VFS, and initrd during the boot
> > se
On Wed, 2002-06-12 at 15:59, Tom Allison wrote:
> Jamin W. Collins wrote:
>
> >On Wed, 12 Jun 2002 16:51:06 -0400
> >"Tom Allison" <[EMAIL PROTECTED]> wrote:
> >
> >>I got a really interesting one.
> >>
> >>I am running a stock K7 kernel from woody.
> >>I recall seeing such things as cramfs, VFS,
Jamin W. Collins wrote:
On Wed, 12 Jun 2002 16:51:06 -0400
"Tom Allison" <[EMAIL PROTECTED]> wrote:
I got a really interesting one.
I am running a stock K7 kernel from woody.
I recall seeing such things as cramfs, VFS, and initrd during the boot
sequence.
I upgraded my RAM to replace the c
On Wed, 12 Jun 2002 16:59:14 -0400
"Tom Allison" <[EMAIL PROTECTED]> wrote:
> Jamin W. Collins wrote:
>
> >Have you tested the new memory? Memtest86 is a great tool for doing
> >just this.
>
> I can't get it to boot in order to test it.
Memtest is it's own stand alone item. There is no need t
Jamin W. Collins wrote:
On Wed, 12 Jun 2002 16:51:06 -0400
"Tom Allison" <[EMAIL PROTECTED]> wrote:
I got a really interesting one.
I am running a stock K7 kernel from woody.
I recall seeing such things as cramfs, VFS, and initrd during the boot
sequence.
I upgraded my RAM to replace the c
On Wed, 12 Jun 2002 16:51:06 -0400
"Tom Allison" <[EMAIL PROTECTED]> wrote:
> I got a really interesting one.
>
> I am running a stock K7 kernel from woody.
> I recall seeing such things as cramfs, VFS, and initrd during the boot
> sequence.
>
> I upgraded my RAM to replace the current 128M to
I got a really interesting one.
I am running a stock K7 kernel from woody.
I recall seeing such things as cramfs, VFS, and initrd during the boot
sequence.
I upgraded my RAM to replace the current 128M to 768M
Now, when I boot it panics with a message that VFS can't mount the root
device at
25 matches
Mail list logo
