It seems to work now.
How can I get the serial console back during runin?
My development head:
http://dev.laptop.org/git/users/quozl/runin/log/
A temporary RPM for demonstrating the regression:
http://dev.laptop.org/~quozl/olpc-runin-tests-0.19.0-1.armv7hl.rpm
Install with
rpm -U
http://wiki.laptop.org/go/OLPC_Firmware_q2f10
That says:
* if the downloaded file is on a USB drive, type:
ok flash u:\q2f10.rom
But that didn't work for me.
It does work if I use disk: rather than u:.
Is that wiki page simply out of date? If so, what changed...? Or is
something
On Tue, May 01, 2012 at 12:26:57AM -0700, Hal Murray wrote:
http://wiki.laptop.org/go/OLPC_Firmware_q2f10
That says:
* if the downloaded file is on a USB drive, type:
ok flash u:\q2f10.rom
But that didn't work for me.
It does work if I use disk: rather than u:.
Interesting.
qu...@laptop.org said:
It does work if I use disk: rather than u:.
Interesting. What firmware version do you have installed at the moment?
I'm not sure what I had since I have fixed that by updating it to q2f10.rom
. Most likely it was the previously announced version.
Running q2f10.rom
Any ideas please, regarding the two latest queries :) ?
Regards,
Ajay
On Mon, Apr 30, 2012 at 1:00 PM, Ajay Garg a...@activitycentral.com wrote:
Thanks Martin and Jon for the replies.
On Sun, Apr 29, 2012 at 3:04 PM, Jon Nettleton jon.nettle...@gmail.comwrote:
On Sun, Apr 29, 2012 at 10:04
ajay wrote:
Any ideas please, regarding the two latest queries :) ?
Regards,
Ajay
On Mon, Apr 30, 2012 at 1:00 PM, Ajay Garg a...@activitycentral.com wrote:
Thanks Martin and Jon for the replies.
On Sun, Apr 29, 2012 at 3:04 PM, Jon Nettleton
Thanks Paul.
On Tue, May 1, 2012 at 8:03 PM, Paul Fox p...@laptop.org wrote:
ajay wrote:
Any ideas please, regarding the two latest queries :) ?
Regards,
Ajay
On Mon, Apr 30, 2012 at 1:00 PM, Ajay Garg a...@activitycentral.com
wrote:
Thanks Martin and Jon for the
which actually brings me back to my original question ::
Why is it so that putting the 'disable-mesh-script' in the 'start()' method
of '/etc/init.d/Networkmanager' works (always) for (re)boot; but never
works for resume-upon-suspend?
Regards,
Ajay
On Tue, May 1, 2012 at 8:07 PM, Ajay Garg
ajay wrote:
Thanks Paul.
On Tue, May 1, 2012 at 8:03 PM, Paul Fox p...@laptop.org wrote:
ajay wrote:
Any ideas please, regarding the two latest queries :) ?
Regards,
Ajay
On Mon, Apr 30, 2012 at 1:00 PM, Ajay Garg a...@activitycentral.com
wrote:
Thanks Paul.
I will give it a try myself.
Just one last question ::
I suppose that 'echo 0 /sys/class/net/eth0/lbs_mesh' is a hack that is
olpc-customised. So, I will be really grateful if you could point me to
some docs (a wiki page may be), that provide information as to how this
hack
Hi,
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC address expressed in hex.
In Nicaragua we are seeing cases where XOs have no hostname set, both
on XO-1 and XO-1.5. On XO-1 this is presumably because libertas
On Tue, May 1, 2012 at 11:29 AM, Daniel Drake d...@laptop.org wrote:
Hi,
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC address expressed in hex.
In Nicaragua we are seeing cases where XOs have no hostname
daniel wrote:
Hi,
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC address expressed in hex.
In Nicaragua we are seeing cases where XOs have no hostname set, both
on XO-1 and XO-1.5. On XO-1 this is
On Tue, 2012-05-01 at 20:50 +0530, Ajay Garg wrote:
Thanks Paul.
I will give it a try myself.
Just one last question ::
I suppose that 'echo 0 /sys/class/net/eth0/lbs_mesh' is a hack
that is olpc-customised. So, I will be really grateful if you could
point me to some docs (a wiki page
On Tue, May 1, 2012 at 3:55 PM, Ajay Garg a...@activitycentral.com wrote:
which actually brings me back to my original question ::
Why is it so that putting the 'disable-mesh-script' in the 'start()' method
of '/etc/init.d/Networkmanager' works (always) for (re)boot; but never works
for
On 05/01/2012 10:29 AM, Daniel Drake wrote:
As far as I can see, the hostname is not really of relevance to
anything except avahi.
But from avahi is how the other XO users identify who is online. I can
never remember which system has which XO-icon color -- but the name (as
shown on hover in
On Tue, May 01, 2012 at 02:10:28AM -0700, Hal Murray wrote:
Running q2f10.rom with that USB Flash drive plugged in...
ok dir u: says Can't open directory
ok dir disk: says
fat-file-system
(and files/dirs I that seem reasonable, including q2f10.rom that I loaded.)
In case it matters, this
Currently, XO hostnames are set on first boot in the following format:
xo-A-B-C
Where A, B and C are the last 3 bytes of the MAC address expressed in hex.
In Nicaragua we are seeing cases where XOs have no hostname set, both
on XO-1 and XO-1.5. On XO-1 this is presumably because libertas
Hi all.
I'll ask this straight ::
Is there an already tested-cum-recommended method, that could disable
mesh-network, both during reboots and resume-from-suspend?
Possible options (not tested by me) ::
a)
A driver, encapsulating the patch at
Just an updated version ::
Hi all.
I'll ask this straight ::
Is there an already tested-cum-recommended method, that could disable
mesh-network, both during reboots and resume-from-suspend?
Possible options (not tested by me) ::
a)
A driver, encapsulating the patch at
On Wed, May 02, 2012 at 09:14:26AM +0530, Ajay Garg wrote:
Is there an already tested-cum-recommended method, that could disable
mesh-network, both during reboots and resume-from-suspend?
Not that I know of.
But I'm curious, why do you need to do this? Is there some other
problem you think
Thanks James for the reply.
On Wed, May 2, 2012 at 9:21 AM, James Cameron qu...@laptop.org wrote:
On Wed, May 02, 2012 at 09:14:26AM +0530, Ajay Garg wrote:
Is there an already tested-cum-recommended method, that could disable
mesh-network, both during reboots and resume-from-suspend?
Not
On Wed, May 02, 2012 at 09:33:36AM +0530, Ajay Garg wrote:
Thanks James for the reply.
On Wed, May 2, 2012 at 9:21 AM, James Cameron qu...@laptop.org wrote:
On Wed, May 02, 2012 at 09:14:26AM +0530, Ajay Garg wrote:
Is there an already tested-cum-recommended method, that could
On Wed, May 2, 2012 at 9:39 AM, James Cameron qu...@laptop.org wrote:
On Wed, May 02, 2012 at 09:33:36AM +0530, Ajay Garg wrote:
Thanks James for the reply.
On Wed, May 2, 2012 at 9:21 AM, James Cameron qu...@laptop.org wrote:
On Wed, May 02, 2012 at 09:14:26AM +0530, Ajay Garg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed 02 May 2012 09:39:50 AM IST, James Cameron wrote:
On Wed, May 02, 2012 at 09:33:36AM +0530, Ajay Garg wrote:
Thanks James for the reply.
On Wed, May 2, 2012 at 9:21 AM, James Cameron qu...@laptop.org wrote:
On Wed, May 02, 2012 at
Hi,
On Wed, May 02 2012, Ajay Garg wrote:
Just wish to remove the mesh-icons from Neighborhood-View.
Have you considered just removing the icons directly?
diff --git a/src/jarabe/desktop/meshbox.py b/src/jarabe/desktop/meshbox.py
index 20dc413..0aa8c7f 100644
---
Yes Chris, that certainly is an option.
But removing the references to the device itself, would clean up both the
model and the view; whereas this (as I think) only removes the view.
Regards,
Ajay
On Wed, May 2, 2012 at 10:18 AM, Chris Ball c...@laptop.org wrote:
Hi,
On Wed, May 02 2012,
If all you wish to do is remove the mesh icons from the network
neighbourhood, why would you also want to clean up the model?
On Wed, May 02, 2012 at 10:29:45AM +0530, Ajay Garg wrote:
Yes Chris, that certainly is an option.
But removing the references to the device itself, would clean up both
Well.. Hmm.. So that it could mean less (leftover-half-bits) bugs to play
with :P
Regards,
Ajay
On Wed, May 2, 2012 at 10:42 AM, James Cameron qu...@laptop.org wrote:
If all you wish to do is remove the mesh icons from the network
neighbourhood, why would you also want to clean up the model?
Okay. Take care not to add any when you change all those lines of code.
;-)
On Wed, May 02, 2012 at 10:47:41AM +0530, Ajay Garg wrote:
Well.. Hmm.. So that it could mean less (leftover-half-bits) bugs to play with
:P
Regards,
Ajay
On Wed, May 2, 2012 at 10:42 AM, James Cameron
Haha.. Okies.. :) :)
Regards,
Ajay
On Wed, May 2, 2012 at 10:55 AM, James Cameron qu...@laptop.org wrote:
Okay. Take care not to add any when you change all those lines of code.
;-)
On Wed, May 02, 2012 at 10:47:41AM +0530, Ajay Garg wrote:
Well.. Hmm.. So that it could mean less
At least historically, I have been told that OLPC does not support the XS
in virtual environments.
This does not mean it is not possible; but officially OLPC may not be able
to support such VMs.
I vaguely recall the reasons for this; but as it has been a while, I will
leave the official
I've set this up primarily for testing. I don't plan on using it in
production.
Sameer
On May 1, 2012 8:21 PM, Samuel Greenfeld greenf...@laptop.org wrote:
At least historically, I have been told that OLPC does not support the XS
in virtual environments.
This does not mean it is not
33 matches
Mail list logo