Fedora List <fedora-olpc-list@redhat.com>
by Mikus Grinbergs
> I copied both files to a usb drive then booted with holding the esc key.
> Then 'copy-nand u:\os3.img' then it copied and I got back the firmware
> prompt. It did not bark about wrong crc or something like that. Then I
> switched the XO-1 off then switched on and all I can get is a Boot
> failed error message. Reimaging with 802 works so it is not a hardware
> fault. How could others run this stuff?
The problem is simple - the copy-nand erased *all* of nand -
including the /security/develop.sig file you had stored there.
Then the firmware determined that you were trying to boot an
unsecured build onto (what it now thought was) a secure XO - and
gave you the error.
One thing you might do is to place a /security directory on an usb
drive (even the one with the image), then copy your develop.sig to
that directory, and have that drive present when you try the boot.
Once you are able to get to the firmware 'ok' prompt again, you
might enter 'disable-security' (without quotes). That will,
independently of the nand contents, mark your XO as not needing
security verification by the firmware.
The way to minimize the chance of what you experienced is, when the
'copy-nand' finishes, to __not__ switch the XO off, but to rather
just enter 'boot' at the firmware prompt. That ought to allow the
new build to come up (giving you a chance to again copy your
developer key into the XO nand).
mikus
14 years, 9 months
New F11-for-XO1 build is available and needs testing
by Steven M. Parrish
I have taken over creating builds for the XO1 from Daniel, and have created a
new build of F11 for the XO1. This build "OS3" includes the pretty boot
animations, and also replaces olpcsound with csound.
I would apprectiate testing and feedback. I will have another build out early
next week as well.
Builds can be downloaded from http://dev.laptop.org/~smparrish/xo-1/builds/
The usual cautions apply: this is development code, there will be
bugs. Installation instructions: use copy-nand to install os3.img with
os3.crc.
Steven
=====================================================
Steven M. Parrish
-------------------------------------------------------------------------------------------------
gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0
http://tuxbrewr.fedorapeople.org/
irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar
14 years, 9 months
Re: New F11-for-XO1 build is available and needs testing
by Mikus Grinbergs
Tomeu, I have great difficulty in dealing with your responses to
the posts I make. What I had written was a reply to Steven Parrish
asking "I would appreciate testing and feedback". It was my intent
to provide feedback on "system-related" matters that in my opinion
deserved being brought to the notice of "system-related" developers.
You either trust what I report, or you don't. I am a volunteer, not
under any contract to delve into the causes of problems. If the
descriptions I give are not enough for you to recognize a problem --
fine -- let my concern lie until someone more important than me
encounters it (or let the matter die if noone else sees it).
If you thought I was asking for your help to solve a problem for
__me__, you were wrong. I mentioned what was my concern in order to
"alert" developers that there may be something that might affect the
perception of the __product__ (if it were delivered "as is").
> Some if the info here may help?
> https://dev.laptop.org/ticket/9324
No, it didn't. There are too many references to other tickets and
to other facilities such as GTK, for me to understand what's what.
In any case, when running the "OS3 build", there is no change in the
text size of the Journal View entries, nor in the text size of the
"Menu Bar" in firefox, when I change the value in .Xresources
> Explaining where that message was logged and including the full logs may help
I really do not understand why you are asking this, unless by simply
questioning the *way* I said something, you intend to reject *what*
I said.
I started firefox by typing in its name at the command line in
Terminal. The message subsequently appeared on the screen in that
Terminal session. [The message also appeared within the output of
the 'Error Console' in firefox, when I explicitly looked at that.]
"Including full logs may help" -- I am unaware of any "full logs"
written by firefox. And the only other logs I can think of - those
in /var/log - in my opinion contain nothing about running firefox.
mikus
14 years, 9 months
Re: New F11-for-XO1 build is available and needs testing
by James Cameron
On Sun, Aug 02, 2009 at 11:26:55AM +0200, Tomeu Vizoso wrote:
> What about yum update? Specially as F11 has deltarpm.
How can you simply ensure (as a user) that yum update will adopt a
specific set of versions that match the build that was done? Isn't it
simpler to use either olpc-update or the image file?
--
James Cameron
http://quozl.linux.org.au/
14 years, 9 months
Re: New F11-for-XO1 build is available and needs testing
by Mikus Grinbergs
> This build "OS3" includes the pretty boot
> animations, and also replaces olpcsound with csound.
> I would apprectiate testing and feedback.
Disclaimer: perhaps off-topic Usability report :
Was running Firefox 3.5 (*not* the Activity). Noticed two things:
* The font size (for things like the Menu Bar) was too large, with
the result that various dropdowns (and settings windows) ran off
the bottom edge of my XO-1 screen -- so I could not click on any
buttons located at the bottom. I wonder if this has anything
to do with the font size in Journal View also being too large.
* The following error was logged several times:
Obtaining the module object from Python failed
Traceback:
can't import cStringIO
<type 'exceptions.ImportError'>:
/usr/lib/python2.6/lib-dynaload/timemodule,so:
undefined symbol: PyExc_ValueError
mikus
p.s.
Pretty boot has "awkward interval" before/after rotating dots.
For me, sound works with "OS3" on XO-1 (though perhaps not as
loud as with other builds).
14 years, 9 months
sugar rawhide livecd image
by Peter Robinson
Hi All,
I've done a Fedora Rawhide based snapshot. Now that the mass rebuild
is done for the step up it i686 I'd like to get some testing done so
that we can see what impact, if any, we'll see on the XO-1 with its
i586+cmov processor so that we can get bugs filed and things fixed as
early in the current rawhide rotation to ensure we get a well
supported F12 release. I'm going to do a new rawhide based snapshot
1-2 times a week. Let me know of any issues you see on is so we can
track them.
Cheers,
Peter
http://dozer.roving-it.com/fedora/livecd-fedora-livecd-sugar-200908011435...
14 years, 9 months
Re: F11 for the X01- shutdown
by Yioryos Asprobounitis
--- On Wed, 7/29/09, Mikus Grinbergs <mikus(a)bga.com> wrote:
> From: Mikus Grinbergs <mikus(a)bga.com>
> Subject: Re: F11 for the X01- shutdown
> To: fedora-olpc-list(a)redhat.com
> Cc: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
> Date: Wednesday, July 29, 2009, 8:25 PM
> > Yet another log of random
> shutdown.
>
> I noticed from the /var/log/messages content enclosed in
> your recent post that your processor is running at 497.488
> MHz. My XO-1s are running at around 430.911 MHz.
> Are you overclocking your XO-1 ?
Fro the last 1 year+ :)
The olpc.fth is in my Ubuntu/swap containing SDcard (follows)
_However_ both random shutdown and X problems are happening also without the SDcard when the XO is using the original f110XO1/os2 olpc.fth
--------------------------------------------------
SDcard olpc.fth:
14 years, 9 months
Re: F11 for the X01- shutdown
by Mikus Grinbergs
> What version of XO firmware is installed?
Q2E41
>> | Exception: OFW is not mounted, cannot read deployment keys
>
> That's odd. Why isn't /ofw mounted?
>
> # mount ...
> none on /ofw type promfs (rw)
> # grep ofw /etc/fstab
> none /ofw promfs defaults 0 0
Did not have that in my /etc/fstab. Don't know how that happened --
most likely through me having copied my fstab file over from an
earlier build which did not provide that particular entry.
With 'build os3' I made sure that the /etc/fstab that came with the
build was not truncated - and now /ofw gets mounted (and with
'/usr/sbin/olpc-update-query' I see the same results as does James).
mikus
14 years, 9 months
Image created with XO-1 scripts doesn't boot
by Juliano Bittencourt
Hello all,
Since I'm currently living in Rwanda (with an overpriced slow
connection), I though it would save me some time if I built my F11
images locally.
I copied the scripts of the xo-1 branch at git and ran them to
generate and os.img file. Everything went fine and after 3 days
(downloading rpms) I got the image.
I copied it to my XO-1, but it didn't booted. The machines
freezes after ofw loads the ramdisk. No Linux kernel message at all.
Some idea of what could be happening?
Thanks,
Juliano
Juliano Bittencourt <juliano(a)lec.ufrgs.br>
Laboratório de Estudos Cognitivos - LEC
Address: Rua Ramiro Barcelos, 2600 - Bairro Santa Cecília - Porto
Alegre - RS - Brasil
Phone: +55 51 3308 5250 and +55 51 3308 5690
14 years, 9 months
