Hi,
I am running into problems with starting foundation model lately.
1. I had created an image using
linaro-image-lamp-genericarmv8-20140127-635.rootfs.tar.gz
2. It was booting fine initially.
3. The problem started happening after I attempted to build Groff package,
which was not getting build and the model was getting frozen (no response
to Ctrl + C, etc.). However I was able to restart the model by closing it
from the launch window and then restarting it.
Now, the model simply fails to launch successfully (hangs in the middle,
doesn't get to the command prompt).
Anyone knows whom should I report to about this?
Thanks,
Anil
Hi All,
Does anyone know of a way to go down to just one processor running the
armv8 FVP model?
This gets it down to 2 but this seems to be the minimum.
-C cluster0.NUM_CORES=1 \
-C cluster1.NUM_CORES=1 \
Trying to come up with ways to get a little more speed out the model.
Thanks!
--
Regards,
Tom
"Where's the kaboom!? There was supposed to be an earth-shattering
kaboom!" Marvin Martian
Tech Lead, Graphics Working Group | Linaro.org │ Open source software
for ARM SoCs
w) tom.gall att linaro.org
h) tom_gall att mac.com
Does anyone know how to increase the disk size on Foundation Model?
For some reason, the network connectivity to the foundation model (via ssh
localhost) doesn't work reliably. So my earlier attempts to mount my host
computer's drive and get things done doesn't work reliably either. Now I
am stuck with the initial 8GB or so hard disk on the foundation model which
is insufficient for any meaningful work.
Appreciate any help.
Thanks & Regards,
Anil
I am running into the following error on Foundation model, with the lamp OE
image, while trying to make and make install groff"
. . .
examples/rainbow.roff:85: multiplication overflow
examples/rainbow.roff:85: multiplication overflow
examples/rainbow.roff:85: multiplication overflow
examples/rainbow.roff:85: multiplication overflow
examples/rainbow.roff:85: multiplication overflow
examples/rainbow.roff:85: multiplication overflow
. . .
I suspect this could be some problem with the new image, because earlier I
was able to build and install it without any problem. This problem showed
up after I switched to the latest OE image (in the process of trying to
increase Disk size).
Further, I notice that some times the package build simply halts for no
apparent reason, which is another new artifact with the new OE image.
Anybody has faced these problems..?
