Well, I built and tested this today. No joy. It does correctly pass the
mem=(5g) option to the kernel, but the kernel does not handle it. The
kernel seems to be truncating this value at 32 bits so my 5 gig system
actually boots with only 1 gig active.
I hacked grub to not pass the mem= option and it booted ok. Of course I
then realized that I had the 4gig config option in the kernel instead of
the 64gig option. duh! I'm rebuilding the kernel now to test again.
I expect we need a way to turn the mem= option on and off for individual
boot entries.
Tim Riker wrote:
>
> I hope to get to testing this tomorrow. The test machine serves many
> purposes so I've not been able to get on it yet.
>
> OKUJI Yoshinori wrote:
> >
> > As usual, I created a branch for preparing 0.5.95. You can access
> > the branch by specifying the tag `prepare_0_5_95'. I myself don't have
> > anything to be done until 0.5.95, so, Gordon, please release it
> > whenever you like. Ah... if Tim Riker reports that my patch for >4GB
> > memory works fine before the release, please apply it. I don't apply
> > it for now, since I don't know if it works or not and I cannot examine
> > it myself (I'm not so rich).
> >
> > Okuji
>
> --
> Tim Riker - http://rikers.org/ - short SIGs! <g>
> All I need to know I could have learned in Kindergarten
> ... if I'd just been paying attention.
--
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.
