Just joined the list and saw this as my first post. Tonight I upgraded my
BP6 system from two 500Mhz Celerons to two 366Mhz units overclocked to 605Mhz.
Much to my surprise, when I rebooted I noticed I only have 64MB of memory
at the Linux level, although the BIOS reports all 256MB.
Nothing like joining a list to find the first post answers my question.
(I upgraded the BIOS right before the New-Year and hadn't run a "top" to
notice the lack of memory.)
Thanks!
>
> Hello to all!
>
> Brian Hall wrote:
> >
> > I don't believe this is a kernel problem. I had a similar experience with the
> > 2.2.13 kernel when I flashed my Abit BH6 v1.1 BIOS to the latest image. After
> > eliminating the other possiblities (I had added more RAM at the same time), I
> > flashed back to the original image and all the RAM was detected automatically
> > again. I am a little mystified as to the mechanism, but I was sufficiently
> > careful in my troubleshooting to believe the BIOS is the problem, and your note
> > confirms this.
> >
>
> I did a BIOS update from orig. version (don't know the version, but the
> date was 06/08/99) to NJ last week and no other change, so it was
> obvious to me
> that _only_ the different BIOS could be the reason linux (all kernels -
> 2.0.36,
> 2.2.5, 2.2.10, 2.2.12 & 2.2.13 - from all installed systems ) detected
> only 64
> of 288 MB. Before, I thought all the guys reporting these things with
> fairly modern
> boards were hallucinating or something, as I never had such probs with
> my 2
> "outdated" Gigabyte HX boards since 2.0.32 !
> I guess the BIOS mem. detection routines were changed in a
> "non-standard" way
> by Award and/or Abit - so my decision was to return to the state before,
> as I
> haven't (yet) encountered really _serious_ problems neither with the
> board as a
> whole nor with a Seagate 20G HD on the HPT 366 (prim. master) - only
> somewhat
> long (recovery) pauses when tranferring lots of files (not accompanied
> by syslog
> entries, however). So the reason I gave the NJ BIOS a try was the hope
> for an
> improved HPT366 BIOS, but I preferred the correct RAM detection to
> that...
>
> > I'd recommend you send a note to Abit telling them to undo whatever change
> > they've made to RAM detection/initialization for all their most recent BIOSes.
> >
> > On 13-Jan-2000 Aaron Longfield wrote:
> > > Hello:
> > >
> > > I upgraded to 2.2.14 and the kernel doesn't find all my memory anymore.
> > > I have 128M on an Abit BX6r2 motherboard using the latest BIOS (bxrnw).
> > > The BIOS reports the full 128M, but Linux only finds 64M. If I pass the
> > > kernel "mem=128M" it gets all my RAM though. My kernel config is
> > > attached. Everything was fine on 2.2.13, and other boxes I have on 2.2.14
> > > all the memory is found (also 128M machines, different motherboards
> > > though).
> > >
> > > -Aaron Longfield
> > > [EMAIL PROTECTED]
> > >
> >
>
> CU
>
> Juergen
> --
> =- To unsubscribe, email [EMAIL PROTECTED] with the -=
> =- body of "unsubscribe linux-abit". -=
>
--
Kevin Carpenter
Kevin's Home Page: http://www.monrou.com/kevinc
(Expressing his comments from home in St. Louis, where this message originated)
--
=- To unsubscribe, email [EMAIL PROTECTED] with the -=
=- body of "unsubscribe linux-abit". -=
