Port-ofppc archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Pegasos dmesg



Argh. Well, the latest "1.2" firmware was built-on 20051216 (revision 2B5
production run) and you're running a slightly older firmware. Unfortunately,
in the newer ones, it's fixed;

memory@0:
name             "memory"
linux,phandle    0fc54a00 (264587776)
available        00000000 00010000 00024d74 00fdb28c 01800000 00400000
                 0294b007 00000ff9 02a4c000 0d1b1000 0fbffab4 0000054c
reg              00000000 40000000
device_type      "memory"

I'm not sure exactly how you're meant to do it with broken "available"
properties, I think Linux worked through sheer random chance and lucky
memory mappings. The internal firmware memory allocator is fairly happy
to claim() memory for you, so what might be best is to do some little
tests, find out how much memory you have (reg) and then try and allocate
256MB chunks of it. Knock it down by ~8MB every time, until you get a
successful claim.. then keep claiming like that until you have something
approaching the "reg" dictated size of memory allocated.

I know it's pretty stupid, but that's all I can suggest. I do not think
it's prudent to drag out a firmware nobody has touched in 2 years and
start handing it around (I have NO idea if we even have any working 2B2,
2B3 boards left hanging around, not to mention G3 and G4 cards for them)
just to get NetBSD working.

--
Matt Sealey <matt%genesi-usa.com@localhost>
Genesi, Manager, Developer Relations

matthew green wrote:
hi matt.

   Is this a Pegasos I or II?

II.  so far netbsd only runs on pegasosII afaik.
Either way I think it's a firmware bug. What version do you have?

i have...

Welcome to SmartFirmware(tm) for bplan Pegasos2 version 1.2 (20040810112413)
SmartFirmware(tm) Copyright 1996-2001 by CodeGen, Inc.
All Rights Reserved.
Pegasos BIOS Extensions Copyright 2001-2004 by bplan GmbH.
All Rights Reserved.


thanks for responding,


.mrg.

-- Matt Sealey <matt%genesi-usa.com@localhost>
   Genesi, Manager, Developer Relations
matthew green wrote:
   > hi matt,
> > i'm wondering if you have any clue about another pegasos issue
   > we're having.  basically, the OFW seems to be stealing most of
   > my ram for it's own purposes.
> > my machine has 512mb ram in it, and linux sees all this. when
   > i boot netbsd, i only see ~240MB or so, and this comes from the
   > available property in /memory:
> > reg 0:20000000
   > available             0:1000000
   >                       1800000:E400000
> > ie, the entire top 256mb is not available and a couple of chunks
   > from the first 256mb are also taken.
> > i put another 512mb ram in and now it says: > > reg 0:40000000
   > available             0:1000000
   >                       1800000:E400000
> > and netbsd still sees only the same about of ram. of the 1024mb
   > installed, netbsd has 231mb available after booting.
> > if i ignore the "available" and use "reg" i hang when attaching
   > rtas at mainbus.  i tried finding regions to steal back from
   > OFW, but at best i found one 0x40000 sized area that didn't
   > cause some sort of lossage.
> > > do you have any idea why the prom is not providing this ram? > > thanks. > > > .mrg.



Home | Main Index | Thread Index | Old Index