Re: asus pi-p65up5 w/ >64M anyone? was: [linux-kernel] ext2fs problems with >64M ram

C.J. Beyer (cj@styx.phy.Vanderbilt.Edu)
Mon, 15 Dec 1997 19:25:14 -0600 (CST)


The motherboard has OS/2 memory >64M disabled. It does appear
that there is some kind of memory hole just after 65535k.
If I don't pass mem=64M at boot it autodetects about 1024k more
memory. I guess I'm getting the ext2fs errors because it is the first
program to try and use the higher memory. I'm using the 2.0.33-pre3
kernel now, so its not the ext corruption problem.

Does anyone out there run >64M of ram on this motherboard?

C.J. Beyer
cj@styx.phy.vanderbilt.edu
http://styx.phy.vanderbilt.edu/~cj/

On Mon, 15 Dec 1997, Linux Kernel - Mike Tubby wrote:

> At 11:09 15/12/97 -0600, you wrote:
> >
> >Hi, I just replaced the 64M of memory in my dual PPro 200 with
> >128M (2 64M edo chips) but I cannot get the computer to run with
> >the extra ram. If pass the argument mem=64M everything seems to
> >run fine. If I dont pass any arguments at boot, I get an error
> >right after the partition check:
> >
> >EXT2-fs error (device 08:02): ext2_check_descriptors: Inode bitmaps for
> >group 0 not in group (block 32772)!
> >EXT2-fs: group descriptors corrupted !
> >kernel panic: VFS: Unable to mount root fs on 08:02
> >
> >
>
> ... snip...
>
> Sounds like memory to me with the 64M boundary. Things to check:
>
> a) your BIOS settings - memory above 64M may be set for special
> support required for OS/2, if you have a AMI BIOS this is usually
> called "Support for memory above 64M : Non-OS2"
>
> b) get a copy of memtest86-1.3.tar.gz unzip it and run it
> (preferrably over night) and see what the heck's going on.
>
> (NB. memtest86-1.3.tar.gz was recently on the kernel mailing
> list and is referred to on the web site somewhere - if
> really stuck I'll mail it to you)
>
> Mike
>
> --
> Michael J Tubby B.Sc. G8TIC
> Technical Director, Thorcom Systems Limited
> Tel: 01 905 756700 (intl: +44 1 905 756 700)
> Fax: 01 905 755777 (intl: +44 1 905 755 777)
> Web: http://www.thorcom.com
> Email: mike@thorcom.com
>