Hi Harald,
this means you need to boot with vmalloc=something-bigger. The
framebuffer needs to be vmalloc'ed. So if you have a relatively
small amount of RAM, and the BIOS is configured for 256MB
framebuffer size, the kernel-selected vmalloc area is smaller
than what we need
Hi Chris,
On Wed, Jun 03, 2009 at 01:59:41AM -0400, Chris Ball wrote:
Hi Harald,
this means you need to boot with vmalloc=something-bigger. The
framebuffer needs to be vmalloc'ed. So if you have a relatively
small amount of RAM, and the BIOS is configured for 256MB
Don't believe everything you read on a wiki.
OFW has included support for partitioned NAND since the first production
shipments, dating back to January 2008. The idea is to have a small
boot partition that can be in any format that OFW supports - JFFS2,
ext2, FAT, or even a .zip archive.
On Wed, Jun 3, 2009 at 11:34 AM, Peter Robinson pbrobin...@gmail.com wrote:
What version of XO software are you running? Have you tried SOAS or
one of the F11/rawhide test images to see if that improves speed at
all over 8.2.1?
SoaS boot on XO-1 hw is fairly slow, but as you say it has more
On Tue, Jun 2, 2009 at 10:51 PM, da...@lang.hm wrote:
On Tue, 2 Jun 2009, Tiago Marques wrote:
Hi all,
I have some questions to whom might be able to answer them.
It would be cool to have that 2nd SD card slot(?) at the top available in
the final design, are you considering that option?
On Wed, Jun 03, 2009 at 12:26:34PM +0100, Tiago Marques wrote:
I would have some uses for the slot, even if internal, like a SWAP
device.
Even after the massive memory and flash size increase?
--
James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/
I am curious if a number of other deployments have encountered this
problem or just us.
We find that the XO occasionally hangs on shutdown. We are using 0.82
I have created a ticket for this
http://dev.laptop.org/ticket/9319
I realize that OLPC has roughly zero resources to fix problems like
On Wed, Jun 3, 2009 at 14:21, Bryan Berry br...@olenepal.org wrote:
I am curious if a number of other deployments have encountered this
problem or just us.
We find that the XO occasionally hangs on shutdown. We are using 0.82
I have created a ticket for this
bryan wrote:
I am curious if a number of other deployments have encountered this
problem or just us.
We find that the XO occasionally hangs on shutdown. We are using 0.82
I have created a ticket for this
http://dev.laptop.org/ticket/9319
I realize that OLPC has roughly zero
Yes, mostly as a safety precaution, especially when there will be a full
fledged Gnome Desktop and other heavier applications. The on-board flash is
a terrible place to accomodate SWAP, unless we end up with 8GiB and proper
wear levelling for the flash blocks.
1GB is a lot more than I would expect
2009/6/3 Tomeu Vizoso to...@sugarlabs.org:
Maybe you are seeing the issue discussed here?
http://lists.laptop.org/pipermail/devel/2009-May/024414.html
I think so too, but an explanation of what is on the screen at the
point of the hang would not go amiss.
My tentative plans are to roll
daniel wrote:
2009/6/3 Tomeu Vizoso to...@sugarlabs.org:
Maybe you are seeing the issue discussed here?
http://lists.laptop.org/pipermail/devel/2009-May/024414.html
I think so too, but an explanation of what is on the screen at the
point of the hang would not go amiss.
My
2009/6/3 Bobby Powers bobbypow...@gmail.com:
hey Dan,
I tried to summarize the issues here:
http://wiki.laptop.org/go/Bootanim
is there more I should address? how would you avoid using
VT_WAITACTIVE? I have some free time, so I can try to fix these over
the next few days.
In similar
I tried to summarize the issues here:
http://wiki.laptop.org/go/Bootanim
is there more I should address? how would you avoid using
VT_WAITACTIVE? I have some free time, so I can try to fix these over
the next few days.
In similar fashion to this:
peter wrote:
I tried to summarize the issues here:
http://wiki.laptop.org/go/Bootanim
is there more I should address? how would you avoid using
VT_WAITACTIVE? I have some free time, so I can try to fix these over
the next few days.
In similar fashion to this:
I tried to summarize the issues here:
http://wiki.laptop.org/go/Bootanim
is there more I should address? how would you avoid using
VT_WAITACTIVE? I have some free time, so I can try to fix these over
the next few days.
In similar fashion to this:
peter wrote:
hi peter --
bootanim does both the boot-time animation and the shutdown
ul-warning screen. it does the boot animation in an extremely
efficient manner, shaving 10 or 11 seconds off our current boot
times:
10 or 11 seconds off what? the previous bootanim
On Wed, Jun 3, 2009 at 6:06 PM, Peter Robinson pbrobin...@gmail.com wrote:
I tried to summarize the issues here:
http://wiki.laptop.org/go/Bootanim
is there more I should address? how would you avoid using
VT_WAITACTIVE? I have some free time, so I can try to fix these over
Hi Tiago,
I have some questions to whom might be able to answer them.
It would be cool to have that 2nd SD card slot(?) at the top
available in the final design, are you considering that option?
No. That's where the wifi module will go, connected (electrically,
not mechanically) via
I'm thinking about ext4, but I must confess that my experience with ext2
has been pretty frustrating. The ext2/3 on-disk format has sprouted many
new features over time. Supporting people who plug in disks that are
formatted with the latest fancy feature, then complain that an old
Guylhem Aznar wrote:
Approx timings from pressing on the power button on my test machine
using an old 2.6.22 on a jffs2 partition
2 seconds with the screen turned off
There is very little that can be done to reduce that 2 seconds, which is
dominated by the time it takes to read the
21 matches
Mail list logo
