http://wiki.laptop.org/go/OLPC_Firmware_q3a15
Lots of good stuff. Please help me test it!
My trac tickets are at http://dev.laptop.org/report/41 . If you click
on the Action Needed column, the test in release tickets will
collate together. Those tickets are ostensibly fixed in q3a15. It
On 29.10.2009, at 16:23, Hilaire Fernandes wrote:
2009/10/29 Bert Freudenberg b...@freudenbergs.de:
On 29.10.2009, at 02:47, Hilaire Fernandes wrote:
Under Etoys, If I keep down the mouse button and choose Save under
another name (I am not sure about the exact message), and save the
On Fri, Oct 30, 2009 at 9:11 AM, Bert Freudenberg b...@freudenbergs.de wrote:
On 29.10.2009, at 16:23, Hilaire Fernandes wrote:
2009/10/29 Bert Freudenberg b...@freudenbergs.de:
On 29.10.2009, at 02:47, Hilaire Fernandes wrote:
Under Etoys, If I keep down the mouse button and choose Save
Oops, sorry.
Post to the wrong devel list :-(
Lionel.
De : LASKE, Lionel (C2S)
Envoyé : vendredi 30 octobre 2009 15:05
À : 'sugar-de...@lists.sugarlabs.org'
Objet : XO 1.5 hang on Type your name screen
Hi all,
I've just upgraded our XO 1.5 to q13a13 firmware and to os34.
By
Lionel -
Step 1 is to take Mitch's advice of earlier today and upgrade to q3a15:
http://wiki.laptop.org/go/OLPC_Firmware_q3a15
- Ed
On Oct 30, 2009, at 10:06 AM, LASKE, Lionel (C2S) wrote:
Oops, sorry.
Post to the wrong devel list :-(
Lionel.
De : LASKE, Lionel
So I'm reminded of my first handheld computer,
and beaming between friends, my contact information,
like a business card, and sharing applications/ activities
by beaming them to someone in the proximity
by IR.
So fast forward to the WiFi age, and several
friends within a classroom or after school
In a LWN discussion thread on how google uses the kernel I found the following:
==
2) Mike asked why the kernel tries so hard to allocate memory - why not just
fail to allocate if there is too much pressure. Why isn't disabling overcommit
enough?
Posted Oct 24, 2009 1:26 UTC
Step 1 is to take Mitch's advice of earlier today and upgrade to q3a15:
http://wiki.laptop.org/go/OLPC_Firmware_q3a15
- First: the system “hang” (no response from mouse and
keyboard) when displaying the “Type your name” screen.
- Second: I can’t stop the booting
Please join us NOW reviewing the latest OLPC/Sugar community projects
over IRC Live Chat: (2PM EDT Boston Time Today/Friday)
http://forum.laptop.org/chat
Then type at bottom:
/join #olpc-meeting
AGENDA:
* New projects libraries -- teaching them Community Outreach:
On a whim, I posted to the open 80211s list to see if the wireless
card on the XO1.5B2 will support open 80211s. Here's the thread.
http://open80211s.com/pipermail/devel/2009-October/000368.html I must
admit that my understanding of open 80211s is fairly limited, but I
was hoping that the wireless
Hi, Sameer !
Are you sure open802.11s can be made to support to the Marvell chipsets ?
In any case, open802.11s implementation is certainly incompatible with the
standard OLPC 802.11s driver, since they implemented different versions of
the draft.
It is interesting to read that Mesh
On Fri, Oct 30, 2009 at 11:38 AM, Ed McNierney e...@laptop.org wrote:
On Oct 30, 2009, at 2:21 PM, Sameer Verma wrote:
to allow for meshing a la XO1
Sameer -
Are you in fact using 802.11s mesh networking on XO-1 machines? Or are you
rather using ad-hoc networking and collaboration
On Oct 30, 2009, at 3:32 PM, Sameer Verma wrote:
scenarios of a handful of XOs in the under-a-tree model
Sameer -
Under a tree, using mesh networking is pointless (unless, I suppose,
it is an extraordinarily large tree). Mesh networking allows packet
forwarding from node A to node B,
Thanks Ed but I can't upgrade to q3a15 due to the keyboard issue :-(
Lionel.
De : Ed McNierney [mailto:edmcnier...@gmail.com] De la part de Ed McNierney
Envoyé : vendredi 30 octobre 2009 15:12
À : LASKE, Lionel (C2S)
Cc : OLPC Devel
Objet : Re: XO 1.5 hang on Type your name
I'd said to lots of people that the XO
uses 802.11s mesh networking
and eventually ran into someone rather
geekie and otherwise impressively knowledgeable
who corrected me that they didn't implement the
whole standard (and people here say draft).
The Marvel driver is said to be closed source,
and
That's not correct. Many of us have run into this problem and done
the upgrade. As Richard pointed out, removing all power (disconnect
the AC adapter, remove the battery, count to 10, then reassemble) will
reset the EC and fix the problem. Power on the machine and press Esc
immediately
I can't quite understand the desire for definitive info combined
with your disappointment that you don't have 1.5 rumors. I don't
think we need rumors, and I and many other folks have been providing
definitive info about 1.5 for some time. And about the mesh, etc.
You don't say what
Thank you. And yes I'm conflicted.
Your summary and experience
give a good overview
and I'll point people to the
wiki.laptop.org if they need more
info.
Re: the XO 1.5 mesh implementation,
compatibility with other XO 1.0 and
an open source driver would be nice.
Not that I plan on hacking it,
as
On Fri, Oct 30, 2009 at 16:58, Richard A. Smith rich...@laptop.org wrote:
In a LWN discussion thread on how google uses the kernel I found the
following:
==
2) Mike asked why the kernel tries so hard to allocate memory - why not just
fail to allocate if there is too much
On 30.10.2009, at 09:27, Eben Eliason wrote:
On Fri, Oct 30, 2009 at 9:11 AM, Bert Freudenberg b...@freudenbergs.de
wrote:
On 29.10.2009, at 16:23, Hilaire Fernandes wrote:
2009/10/29 Bert Freudenberg b...@freudenbergs.de:
On 29.10.2009, at 02:47, Hilaire Fernandes wrote:
Under Etoys,
I mean the clock in the 802.11 MAC sublayer. This defines the basis of
the timing synchronization function (TSF) which is a core part of
802.11. Without synchronized clocks, nodes cannot communicate.
I talked with one of the 802.11 experts I know. He's quite sure
that there should be no
Remove all power and wait is by far the easiest way to reset a
keyboard, but ...
If one really could not get the keyboard to work, but wanted to upgrade
the firmware anyway, here is a recipe:
a) Get a USB stick, ideally factory-formatted with a FAT filesystem, but
ext2 will work too.
b) Put
On Fri, Oct 30, 2009 at 8:45 PM, John Gilmore g...@toad.com wrote:
I talked with one of the 802.11 experts I know. He's quite sure
that there should be no problem on Atheros hardware at least.
He has no problem transmitting arbitrary packets at arbitrary
times and no problem receiving packets
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard A. Smith wrote:
Working the table at the Boston book festival I was reminded how painful the
OOM stuff is on a gen 1.
The OOM problem on Gen 1 is a True Kernel Bug. The problem is that the
OOM killer just isn't working. Almost all the
24 matches
Mail list logo
