Hi Jerry, Hi John,
Thanks for your help.
If you change the LO tag for a laptop before the first boot of an image,
its value will get picked up and used.
Great ! I did'nt know that default language could be change directly in the
firmware.
I guess it depends of the SKU value. Could I set
Let us know if you have any further questions ... I expect some from
every new Forth user. ;-)
--
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
On Mon, Mar 25, 2013 at 3:16 AM, lio...@olpc-france.org wrote:
Great ! I did'nt know that default language could be change directly in the
firmware.
I guess it depends of the SKU value. Could I set French with an English
keyboard ?
Yes. LO is for system language, KL is for keyboard language.
Thanks for testing.
On Sat, Mar 23, 2013 at 2:43 AM, Tom Parker t...@carrott.org wrote:
No sound in TamTam or Speak on 3 out 5 XO-1.75s. Speak hung when saying a
sentence, scratch failed to start with an error in it’s log about missing
sound driver. Record hangs when you take a photo on those
Here is a screen capture from the XO-1 I'm using to test the procedure:
http://laske.fr/tmp/SHF8080270B.jpg
You appear to be using a developer key. If you are going to be
installing a custom build on all the laptops I would encourage you to
disable the security system altogether as the last
Battery life on XO-4 C2 seems significantly improved over previous builds.
We would be interested in a confirmation or otherwise of this in the power
log analysis.
I guess you are comparing to 13.1.0 build 36?
The big difference here is that 13.1.0 build 36 has automatic power
management
On 26/03/13 05:00, Daniel Drake wrote:
On Sat, Mar 23, 2013 at 2:43 AM, Tom Parker t...@carrott.org wrote:
On Karearea, the UI did not respond to mouse clicks or keyboard input, but
the neighbourhood/friends/activity list keys worked. After 3 reboots this
started working and we discovered the
On 24/03/13 17:56, Gary Martin wrote:
Physics still has the top of screen problem on XO-1.75 but is working very well
on XO-4.
How critical do you think this one is?
It's quite annoying if you happen to build something in physics that
extends to the top of the screen and certainly doesn't
On Sun, Mar 24, 2013 at 4:34 PM, Paul Fox p...@laptop.org wrote:
i think the point john (gilmore) was making is that it's a bad
precedent that simply because a) systemd offers a second-rate API for
scheduling events, and b) we only have a couple of uses for an event
scheduler, that we should
Hi all,
Thanks for your answer.
Let us know if you have any further questions ... I expect some from every
new Forth user. ;-)
You're right, it's hard to enter in Forth language :-{
I've added a olpc.fth file in the boot directory of my key with following
commands:
copy-nand
Hi Richard,
You appear to be using a developer key. If you are going to be installing
a custom build on all the laptops I would encourage you to disable the
security
system altogether as the last step in your olpc.fth step with
'disable-security'. Then some of the gotchas that occur with
Yes, add a comment line to the start of file, so that the file is
recognised. I also suggest encoding the work as a program
definition. So the file might be:
\ automatic installer by lio...@olpc-france.org
: installer
copy-nand u:\21007xx0.img eval
change-tag LO fr_FR.UTF-8 eval
;
On Mon, Mar 25, 2013 at 5:20 PM, lio...@olpc-france.org wrote:
Hi Richard,
You appear to be using a developer key. If you are going to be installing
a custom build on all the laptops I would encourage you to disable the
security
system altogether as the last step in your olpc.fth step
Yes, add a comment line to the start of file, so that the file is
recognised. I also suggest encoding the work as a program definition. So
the file might be:
YEES It works !
You're my new Forth Hero !
Lionel.
___
Devel mailing
Well for one you have to have those keys present for your installed os to
run either on that stick or by copying the developer key to the XO.
But then you have to make sure that the developer key is re-installed
anytime you reflash the XO. Also if for some other reason the dev keys are
removed
On Mon, Mar 25, 2013 at 11:23:39PM +0100, lio...@olpc-france.org wrote:
Hmmm. Change-tag without reboot ? Is there any way to do that ?
Yes, it is possible. For XO-4 it is easy. For XO-1 it disables
keyboard during the actions. If you have a bug in the code at this
time, you have to remove
On Mon, Mar 25, 2013 at 7:07 PM, James Cameron qu...@laptop.org wrote:
On Mon, Mar 25, 2013 at 06:50:00PM -0400, Richard Smith wrote:
But maybe you don't need to do that, if you are only changing one tag?
How many tags are you changing? If one, then finish the script with
the tag change.
special command to reboot without the lock. No way around it as you
can only unlock with a reboot. I suppose you could do the security
disable first and then when you see that its 'ww' rather than 'wp'
continue on with the re-flash and then the LO change as the last step.
I had a vague
I thought you should set the dk manufacturing tag, but I
just noticed that is only supported on XO-1 and 1.5!
wp and ww are different tags, you can't just change the
tag value with change-tag.
wad
On Mar 25, 2013, at 7:07 PM, James Cameron wrote:
On Mon, Mar 25, 2013 at 06:50:00PM -0400,
On 03/25/2013 02:03 PM, Richard Smith wrote:
Battery life on XO-4 C2 seems significantly improved over previous builds.
We would be interested in a confirmation or otherwise of this in the power
log analysis.
I guess you are comparing to 13.1.0 build 36?
The big difference here is that 13.1.0
On Mon, 2013-03-25 at 22:19 -0400, Richard A. Smith wrote:
On 03/25/2013 02:03 PM, Richard Smith wrote:
Battery life on XO-4 C2 seems significantly improved over previous builds.
We would be interested in a confirmation or otherwise of this in the power
log analysis.
I guess you are
21 matches
Mail list logo
