As it ages, the microSD card takes longer and longer to erase and
write blocks.
Eventually the time it takes to erase and write may exceed the few
seconds between end of reflashing and the reboot power cycle.
In those situations, use fs-update instead of the four button method,
and leave the
On Sun, Feb 18, 2018 at 3:17 PM, James Cameron wrote:
> Either there is an SD card in the external slot with unsupported partition
> table, or there is a fault with the internal microSD card or slot.
>
I reflashed it a 2nd time and it came back to life (boots properly, for
Either there is an SD card in the external slot with unsupported partition
table, or there is a fault with the internal microSD card or slot.
--
James Cameron
http://quozl.netrek.org/
___
Devel mailing list
Devel@lists.laptop.org
Attached photo (in-lined below) should be an easy firmware/boot issue to
solve I hope! Can anybody remind me what's need / what I need to try next?
Clarif: this is an XO-1.5 (SKU100) with:
- up-to-date RTC clock
- up-to-date firmware (Q3C17)
- up-to-date OS (OLPC OS 13.2.9)
And yet I can no
related to OFW version
Quite normal, as Samuel said.
Fix this by upgrading your operating system, or copy only the startup sound
from a later operating system into the boot partition:
sudo rsync
rsync://updates.laptop.org/build-13.2.0_xo1.75-13/root/boot/jingle.wav
/bootpart/boot
Hi all,
Ive got a sound issue on a XO 1.75 that seems to be related to firmware
version.
In Q4D34
The sound test on firmware works perfectly: both playing and recording.
At startup, instead of the sweet XO sound Ive got two short Beep.
No activity cant play sound: neither Tam-Tam
It sounds like you are trying to upgrade firmware without upgrading your OS.
As of Q4D26 the startup sound was moved to be stored on the internal
storage instead of in the firmware. The two beeps therefore are expected
if the OS does not have a copy of the startup sound on disk to use.
Which OS
Quite normal, as Samuel said.
Fix this by upgrading your operating system, or copy only the startup
sound from a later operating system into the boot partition:
sudo rsync
rsync://updates.laptop.org/build-13.2.0_xo1.75-13/root/boot/jingle.wav
/bootpart/boot/
On Sun, Jul 21, 2013 at 03:38:27PM
Hi All,
Any plans on updating OFW's nandblaster to make better use of the
updated naming scheme? Looking at #nb-secure-def and #nb-update-def
for the 1.75 think that maybe become fs2.zip and fs1.zip for the 1.5 but
what should fs.zd be? Just to prevent mixing up images between the
arches maybe
No plans that I am aware of yet.
In the meanwhile, you can easily use the underlying words directly on
your USB drive:
u:\fs2.zd nb-auto-channel $nb-tx \ XO-1.75
u:\fs1.zd nb-auto-channel $nb-tx \ XO-1.5
or for nb-secure:
u:\fs2.zip u:\fs2.zd nb-auto-channel #nb-secure \ XO-1.75
I'm curious, why do you have security enabled?
Because that's the way they were shipped to me from the factory (or from
whoever I purchased the unit from).
mikus
___
Devel mailing list
Devel@lists.laptop.org
DISCLAIMER: I am not asking for help; I'm just sharing my experiences.
With q2f11.rom on one of my vintage-1997 XO-1s, I could __not__ install
('copy-nand') os12 (12.1.0) from an USB stick -- sooner or later OFW
always stopped on a file read error. I finally flashed q2f05.rom to
that XO-1
On Fri, Jun 01, 2012 at 09:58:09PM -0500, Mikus Grinbergs wrote:
p.s. I also tried q2f11jb.rom - and nearly bricked the XO-1 (I do
not have security deactivated).
I'm curious, why do you have security enabled?
--
James Cameron
http://quozl.linux.org.au/
On 24 January 2012 02:36, Martin Langhoff martin.langh...@gmail.com wrote:
On Mon, Jan 23, 2012 at 7:54 AM, Richard A. Smith rich...@laptop.org wrote:
Hmmm... Something else is the problem here. You can't damage the processor
via thermal overload because it has an automatic clock back off. If
On 01/23/2012 01:32 AM, Sridhar Dhanapalan wrote:
On 23 January 2012 17:20, James Cameronqu...@laptop.org wrote:
I thought you were doing this test to detect early units that may have
a failed heat spreader, and you were doing it at the time of reflashing
because that's when you had some
We are using a custom olpc.fth to present a boot menu so that users
can easily flash their XOs. As a precaution, we run a lid switches
test before the OS installation begins. Some of our XOs have older,
less effective heat spreaders, and we would like to catch these before
they get burnt-out by
is confusing some teachers. Ideally we
only want to run the heat spreader test part of it, so that the test
is transparent and the user doesn't need to close the lid.
Is this possible?
Yes. I don' have a 1.5 with me at the moment but from looking at the
OFW source I think you want ' .temp-rise '.
ok
On Mon, 2012-01-23 at 13:00 +1100, Sridhar Dhanapalan wrote:
We are using a custom olpc.fth to present a boot menu so that users
can easily flash their XOs. As a precaution, we run a lid switches
test before the OS installation begins. Some of our XOs have older,
less effective heat spreaders,
the lid.
Is this possible?
Yes. I don' have a 1.5 with me at the moment but from looking at the
OFW source I think you want ' .temp-rise '.
ok .temp-rise
That should run the thermal test and print a pass fail message. It also
returns back a true or false on the stack
On 01/23/2012 12:23 AM, Jerry Vonau wrote:
Thanks, looking into that part of OFW code.
.temp-rise returns a ? from the OK prompt.
Ah... I see its part of the /switches node .
Try this:
ok select /switches
ok .temp-rise
--
Richard A. Smith rich...@laptop.org
One Laptop per Child
On 01/23/2012 12:17 AM, Jerry Vonau wrote:
Is this possible?
I thought with the physical layout of the motherboard, CPU towards the
outside of the screen lid, that e-book mode would be the hardest on the
XO in terms of heat dissipation. Given there in no active cooling, is
the heat spreader
On 01/23/2012 12:41 AM, Richard A. Smith wrote:
On 01/23/2012 12:23 AM, Jerry Vonau wrote:
Thanks, looking into that part of OFW code.
.temp-rise returns a ? from the OK prompt.
Ah... I see its part of the /switches node .
Try this:
oops.. forgot to get back out of that device node
The heat spreader test is always run in e-book mode, because that's what
the immediately preceeding test does.
I imagine you would get different results if you didn't run it in e-book
mode. I imagine that over a large sample, the results would be
considerably different.
For the user training
On Mon, Jan 23, 2012 at 04:59:55PM +1100, Sridhar Dhanapalan wrote:
How can we parse the output? Our attempts so far have been unreliable
- Jerry has details.
You should find it very reliable when used correctly.
Don't parse the output. Instead, call temp-rise and use the value on
the stack,
On Mon, Jan 23, 2012 at 05:03:29PM +1100, Sridhar Dhanapalan wrote:
On 23 January 2012 16:56, James Cameron qu...@laptop.org wrote:
The heat spreader test is always run in e-book mode, because that's what
the immediately preceeding test does.
I imagine you would get different results if
On 23 January 2012 17:20, James Cameron qu...@laptop.org wrote:
I thought you were doing this test to detect early units that may have
a failed heat spreader, and you were doing it at the time of reflashing
because that's when you had some control.
Yes, that's the primary reason. Our initial
On Mon, Jan 23, 2012 at 05:32:05PM +1100, Sridhar Dhanapalan wrote:
On 23 January 2012 17:20, James Cameron qu...@laptop.org wrote:
I thought you were doing this test to detect early units that may have
a failed heat spreader, and you were doing it at the time of reflashing
because that's
On Wed, Sep 21, 2011 at 11:39 PM, Mitch Bradley w...@laptop.org wrote:
Yeah, what James said.
That said, in most cases the mount/unmount penalty is not bad, because in
cases where it was, I did some caching to make it less onerous. Cases in
point include JFFS2, where mount is inherently
if its partner ramdisk/kernel can
only be found in a zip file.
Could you take a quick look, does this look solid?
One lingering question is how OFW deals with mounting/unmounting.
I know that some words (in some contexts?) cause the disk to be
mounted, then the command to be executed, then the disk
, and the network,
where I cache the DHCP result.
If you have problems, tell me. My intention is that subsequent mounts
should be fast enough.
On 9/21/2011 11:39 AM, James Cameron wrote:
On Wed, Sep 21, 2011 at 04:21:42PM +0100, Daniel Drake wrote:
One lingering question is how OFW deals
Hi,
Right now, our signed images included in the boot partition:
signed initramfs and kernel (runrd.zip runos.zip), used for secure boot
unsigned initramfs and kernel (vmlinuz initrd.img), used in unsecure
mode, but identical the the files in the signed tarballs
I'd like to change the unsecure
, and its value matches osxx.img.md5]
My bypass is to try the copy-nand again (sometimes switching USB sockets
at the XO-1) - usually the retry completes.
Is there something I can type in at the ok prompt that would make OFW
more tolerant - so that my copy-nand would not stop in the middle
You might try patching OpenFirmware to not turn off the
card between
subsequent accesses. To do this, assuming you are
using Q2E45, add the
following early in your olpc.fth file:
dev /sd
patch 2drop cb! card-power-off
Is this also true for the XO-1.5 q3a62? or is an XO-1-only
On Sun, Mar 13, 2011 at 11:27:44PM -0700, Yioryos Asprobounitis wrote:
You might try patching OpenFirmware to not turn off the
card between
subsequent accesses.? To do this, assuming you are
using Q2E45, add the
following early in your olpc.fth file:
??? dev /sd
??? patch 2drop
On 03/13/2011 01:15 AM, Sridhar Dhanapalan wrote:
With firmware Q2E45 on an XO-1 (yes, I finally got it unlocked!), I
type 'menu' at the ok prompt.
On an XO-1.5, I get a very useful list of icons that run different
hardware tests. On this XO-1, I only get an array of square outlines.
The
On 3/13/2011 8:09 AM, Richard A. Smith wrote:
On 03/13/2011 01:15 AM, Sridhar Dhanapalan wrote:
With firmware Q2E45 on an XO-1 (yes, I finally got it unlocked!), I
type 'menu' at the ok prompt.
On an XO-1.5, I get a very useful list of icons that run different
hardware tests. On this XO-1,
On 03/13/2011 11:21 AM, Mitch Bradley wrote:
Not expected but not surprising. The graphical hardware
tests/diagnostics were developed for the 1.5. In XO 1.0 we only had the
text based tests. I suspect that the 1.5 graphics stuff came along for
the ride when we started building newer XO-1
It may well be the quality of the non-high-priced SD cards I use, but
with q2e42 and later OFW versions, when several specific XO-1s are
booted, OFW will occasionally (but not consistently) time out when
trying to read the developer key from the SD card. My usual bypass is
to unplug all external
G'day Mikus,
Fristly, use disable-security so that the developer key is not required
to be present. Is there a good reason for not disabling the security
system? However, if you are booting the laptop from the SD card this
may merely move the problem from developer key recognition to booting.
With firmware Q2E45 on an XO-1 (yes, I finally got it unlocked!), I
type 'menu' at the ok prompt.
On an XO-1.5, I get a very useful list of icons that run different
hardware tests. On this XO-1, I only get an array of square outlines.
The first (top-left) is blue. The others are black. Clicking
got the same result with 2 x XO1 Q2E45 (dextrose439dg and 373pyg)
have not used 'menu' before, always used 'help' to see options
Tony
With firmware Q2E45 on an XO-1 (yes, I finally got it unlocked!), I
type 'menu' at the ok prompt.
On an XO-1.5, I get a very useful list of icons that run
When booting the XO-1 (q2e45) or XO-1.5 (q3a61) from an ext3 formatted USB
stick or external SDcard, the OFW reports that the ext3 journal needs
recovery.
However, stopping the boot process at this exact point (power button),
rebooting from the internal flash/nand (running F14 builds
while the feature flag is set.
The flag is EXT3_FEATURE_INCOMPAT_RECOVER defined in linux/ext2_fs.h,
value 0x0004, and is read from field s_feature_incompat in struct
ext2_super_block. This is done in line 53 of ext2fs/sb.fth
http://tracker.coreboot.org/trac/openfirmware/browser/ofw/fs/ext2fs/sb.fth
[Training a team in mx so brief.]
Just discovered that when security is disabled, OFW Q3A41 will probe
int:/boot/bootfw.zip but not u:/boot/bootfw.zip .
So OFW upgrades trigger automatically after an OS upgrade (where the
newer bootfw.zip is on the internal disk), but not from USB
On 14 October 2010 16:36, Martin Langhoff martin.langh...@gmail.com wrote:
[Training a team in mx so brief.]
Just discovered that when security is disabled, OFW Q3A41 will probe
int:/boot/bootfw.zip but not u:/boot/bootfw.zip .
So OFW upgrades trigger automatically after an OS upgrade (where
On Thu, Oct 14, 2010 at 11:54 AM, Daniel Drake d...@laptop.org wrote:
This is probably not the fault of OFW per say, but the fault of the
olpc.fth file shipped in the OS distribution which is executed when
security is disabled.
Then it's 10.1.1 :-)
m
--
martin.langh...@gmail.com
mar
2010/10/14 Martin Langhoff martin.langh...@gmail.com
[Training a team in mx so brief.]
That's interesting. Can you say any more about that?
Out of touch but still interested,
Jameson
___
Devel mailing list
Devel@lists.laptop.org
On Thu, Oct 14, 2010 at 5:49 PM, Jameson Quinn jameson.qu...@gmail.com wrote:
2010/10/14 Martin Langhoff martin.langh...@gmail.com
[Training a team in mx so brief.]
That's interesting. Can you say any more about that?
Out of touch but still interested,
A fantastic project in Nayarit, Mx --
2010/10/14 Martin Langhoff martin.langh...@gmail.com
On Thu, Oct 14, 2010 at 5:49 PM, Jameson Quinn jameson.qu...@gmail.com
wrote:
2010/10/14 Martin Langhoff martin.langh...@gmail.com
[Training a team in mx so brief.]
That's interesting. Can you say any more about that?
Out of touch
if you want.
Gonzalo
On Mon, Sep 20, 2010 at 10:19 PM, Mitch Bradley w...@laptop.org wrote:
http://wiki.laptop.org/go/OLPC_Firmware_q3a58 is a new OFW release for
XO-1.5. It fixes problems with the audio CODEC
protection settings and includes new EC firmware
On 09/21/2010 11:46 AM, Gonzalo Odiard wrote:
Hi Mitch
I applied it but doesn't restart when finish. The XO doesn't turn off if
you press the power button. I needed to disconnect dc input and the battery.
Firmware reflash disables the EC which means all buttons are inactive.
So having to
http://wiki.laptop.org/go/OLPC_Firmware_q3a58 is a new OFW release for
XO-1.5. It fixes problems with the audio CODEC
protection settings and includes new EC firmware.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo
[ background: working with a local team in a process that needs to be
quick. Booting linux would take way too long and throw our logistics
out of whack ]
Is there a straightforward way to have a signed forth script (local
team has its own keys) that creates/installs a minimal file to a known
a minimal file to a known
location?
We just need to install a config file under /etc ...
as far as i know, writing to the ext3 root partition from OFW is
officially unsupported. the boot partition is ext2 precisely
because ext3 can't be written reliably from OFW.
if you can put the file
(local
team has its own keys) that creates/installs a minimal file to a
known location?
We just need to install a config file under /etc ...
as far as i know, writing to the ext3 root partition from OFW is
officially unsupported. the boot partition is ext2 precisely
because ext3
On Wed, Aug 25, 2010 at 8:38 PM, James Cameron qu...@laptop.org wrote:
ok copy u:\ethni.pdf int:2,\versions\run\852\etc\test.pdf
ext3 journal needs recovery
Not writing to the ext2 filesystem because of unsupported extensions
Flushbuf error
ok
Hi James!
THANKS for trying this out. Yeah,
http://wiki.laptop.org/go/OLPC_Firmware_q3a48
* Fixes a SD card timeout problem with ADATA 4GB and 8GB SD cards
* User interface improvements in test /keyboard to help catch a stuck
key problem seen in the factory
* Resume-from-S3 now works with Windows XP
Current OFW has a bug in its delegated lease support
http://dev.laptop.org/ticket/10118 which affects one of our headline
features for the 10.x.y series.
Not sure how high antitheft ranks for 10.2.0 (10.1.1?)...
cheers,
m
--
martin.langh...@gmail.com
mar...@laptop.org -- School Server
/olpc-configure
@@ -16,16 +16,20 @@ XO_VERSION=0
get_xo_version() {
# This requires an OFW that runs setup-smbios at boot.
- [ -e /sys/class/dmi/id/product_name ] || return
-
- name=$(/sys/class/dmi/id/product_name)
- version=$(/sys/class/dmi/id/product_version
On Wed, 2009-11-25 at 15:36 -0500, Richard A. Smith wrote:
The person who build/releases the firmware (me or mitch) would modify the
spec files we have for the firmware and then build the rpm.
Editing the spec file is manual but I have some scripts that automate making
and releasing the
-off and reboot
show-x
Reflash returned, unexpectedly .security-failure
;
[then]
[ifndef] ?ofw-reflash
\ Check for new firmware.
: ?ofw-reflash ( -- )
${DN}${PN}\bootfw.zip expand$
['] (boot-read) catch if 2drop exit then
img$ firmware-up-to-date? if exit then
img$ do
Hi,
How did RPM packaging of OpenFirmware work in previous OLPC OS release
cycles?
Who did it, and how?
We need to restart this process for
http://dev.laptop.org/ticket/9573
http://dev.laptop.org/ticket/9628
I'm happy to help out, but knowing what happened previously would be
useful.
Daniel
to investigating it further due to time constraints. I think
the KVM people use a OFW release as well so it might be worth looking
at how they compile their version of it. I also wasn't sure what the
signing requirements were of a XO OFW build would be.
Peter
On 11/25/09, Daniel Drake d...@laptop.org
Hi,
How did RPM packaging of OpenFirmware work in previous OLPC OS release
cycles?
Who did it, and how?
The person who build/releases the firmware (me or mitch) would modify the spec
files we have for the firmware and then build the rpm.
Editing the spec file is manual but I have some
it further due to time constraints. I think
the KVM people use a OFW release as well so it might be worth looking
at how they compile their version of it. I also wasn't sure what the
signing requirements were of a XO OFW build would be.
The .rom file is signed outside of any .rpm stuff. .rpms
Mitch,
Does q3a15 automatically throttle the processor in case of overheating?
If so, is there a way to check if it is working? cat /proc/cpuinfo maybe?
Thanks!
On Fri, Oct 30, 2009 at 6:52 AM, Mitch Bradley w...@laptop.org wrote:
http://wiki.laptop.org/go/OLPC_Firmware_q3a15
Lots of good
If you think you might be having troubles with overheating
on your XO-1.5, the heat spreader is suspect. After removal
(to change the SD, check out the motherboard, etc)
and sometimes even before then, the heat spreader doesn't
make good contact with the VX855 and the CPU.
I suggest bending
Emiliano Pastorino wrote:
Mitch,
Does q3a15 automatically throttle the processor in case of overheating?
Yes
If so, is there a way to check if it is working? cat /proc/cpuinfo maybe?
Here is a test you can do with Open Firmware:
ok show-temperature (cr many
That command runs the CPU
There is a way to check the temperature under Linux. It involves the
lmsensors package, but I don't know the exact details.
Yes, that's what I've been using. The package is lm_sensors, if installed,
you just have to type sensors and you get the temperature in ºC.
I've already checked that
Rafael Ortiz
On Tue, Nov 3, 2009 at 10:54 AM, Mitch Bradley w...@laptop.org wrote:
Emiliano Pastorino wrote:
Mitch,
Does q3a15 automatically throttle the processor in case of overheating?
Yes
If so, is there a way to check if it is working? cat /proc/cpuinfo maybe?
Here is a test
Emiliano Pastorino wrote:
There is a way to check the temperature under Linux. It involves
the lmsensors package, but I don't know the exact details.
Yes, that's what I've been using. The package is lm_sensors, if
installed, you just have to type sensors and you get the
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
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
scp dev.laptop.org:~wmb/q3a11c.rom
Consider this a pre-release of q3a12 ...
Highlights:
a) The Via Thermal Monitor is on. That prevents overheating.
b) fs-update has several improvements:
1) Now handles large chunk sizes correctly
2) dir int:\ immediately after fs-update now works
3) Better
to it at all, if the hang is caused by an oops, we can
have a patch that traps calls to die() and bug() and jumps to
OFW. This is what KGDB does, so there is some precedent.
We could also have some magic in the EC to look for a sequence
of keys that signals a low-level handler to kick into OFW
On Thu, Sep 17, 2009 at 05:10:06AM -0400, Paul Fox wrote:
but the issue is that there's no such key on the XO keyboard: SysRq/PrtSc
doesn't exist.
Key to the left of frame and above erase is still free isn't it? ;-)
The legend matches my idea of switching to OFW. Another system hiding
On Wed, Sep 16, 2009 at 11:18:17AM +0800, Mitch Bradley wrote:
It is gratifying that so many people like the idea of being able to zap
back into OFW from Linux - especially since I got such intense pushback
when I first proposed leaving OFW resident on OLPC.
Why? Security reasons?
Martin
Martin Dengler wrote:
On Wed, Sep 16, 2009 at 11:18:17AM +0800, Mitch Bradley wrote:
It is gratifying that so many people like the idea of being able to zap
back into OFW from Linux - especially since I got such intense pushback
when I first proposed leaving OFW resident on OLPC
Another objection, now that I think about it, is that some people didn't
like the way I made OFW coexist within Linux's virtual address space by
injecting a page directory entry at the top of one of Linux's page
tables. Admittedly, the solution that I chose is rather brute force
scarce serial ports. so OFW is a
win, for my current uses.
In theory we could make one OLPC kernel debuggable by another OLPC,
just using the WiFi interfaces and a simple matter of software.
kgdb should be able to use an ethernet, if the Ethernet driver
implements the NETPOLL interface. I think
(returning to?) the resident
OFW command line interface. when invoked, you can do all the
usual OFW peeking and poking, and even play pong. (and, since
linux is still active, you can royally trash your system if
you're not careful.)
there's no SysRq key on the XO keyboard, so you'll need to use
on the XO, openfirmware stays resident when linux runs, and is
accessible via an API specified in arch/x86/kernel/ofw.c. i've
just pushed a commit to our 2.6.30 kernel branch that adds a
sysrq hook (SysRq-y) for starting (returning to?) the resident
OFW command line interface. when invoked, you
to?) the resident
OFW command line interface.
This is one of the coolest hacks I've heard about in a while. Nice
work (and to the giants upon whose shoulders etc. etc.)!
paul
Martin
pgpNPnN48GYYa.pgp
Description: PGP signature
___
Devel mailing list
) for starting (returning to?) the resident
OFW command line interface.
This is one of the coolest hacks I've heard about in a while. Nice
work (and to the giants upon whose shoulders etc. etc.)!
to be honest, i knew it could be done because i had heard rumor
that blaketh had done it earlier
into OFW or
its predecessor. (L1 was the top left key in the keypad to the left
of the main keyboard.) We shipped it that way for decades without
trouble.
There are some pretty obscure keys on the XO keyboard -- howabout
something like holding down the leftmost and rightmost gradually
increasing
that order, with no intervening keys or key-ups) got you into OFW or
its predecessor. (L1 was the top left key in the keypad to the left
of the main keyboard.) We shipped it that way for decades without
trouble.
There are some pretty obscure keys on the XO keyboard -- howabout
something like
, this time. custom key combinations
would require more extensive changes to the input drivers than i
was willing to take on last night.
On Sun workstations, the L1-A key combination (pressed in exactly
that order, with no intervening keys or key-ups) got you into OFW or
its predecessor
It is gratifying that so many people like the idea of being able to zap
back into OFW from Linux - especially since I got such intense pushback
when I first proposed leaving OFW resident on OLPC.
___
Devel mailing list
Devel@lists.laptop.org
http
http://wiki.laptop.org/go/OLPC_Firmware_q2e41
This release is the culmination of a series of mini-releases that change
the boot order when the system is in the factory, so that the
manufacturing test operating system image will boot even if an SD card
is inserted during production steps.
2009/3/29 Martin Langhoff martin.langh...@gmail.com:
Hi Mitch, devel@,
while I finish other work, in the back of my mind I am drafting my
workplan for finishing off the 'delegated leases' stuff.
One of my assumptions so far is that OFW does not care at all about
the leases. All the lease
Hi Mitch, devel@,
while I finish other work, in the back of my mind I am drafting my
workplan for finishing off the 'delegated leases' stuff.
One of my assumptions so far is that OFW does not care at all about
the leases. All the lease checks and USB/Wifi retrieval is all
happening in the Linux
Trying to test the fix for #8976 , I am stumped at what I thought
would be a trivial step - clearing the AK flag. My laptop has ak and
dk flags set, and I have both leases handy in case something goes
wrong. The NAND has a good signed image.
The only hint I was able to find was in a script in
I've just released OFW Q2E24 (
http://wiki.laptop.org/go/OLPC_Firmware_q2e24 ) which is a test
candidate for the upcoming 8.2.1 release. There are a couple of things
that could use some testing, so I'm soliciting help.
Firstly, if you have 2 or more XOs and are willing to overwrite the NAND
Mitch Bradley wrote:
Secondly, if you have a USB CD-ROM drive, you could help me by testing
it with OFW. To do so:
Will an external DVD-RW drive work or only a CD?
a) Remove all other USB storage devices (FLASH keys and the like) from
the XO
b) Put a CD-ROM that has an ISO-9660
Chris Marshall wrote:
Mitch Bradley wrote:
Secondly, if you have a USB CD-ROM drive, you could help me by
testing it with OFW. To do so:
Will an external DVD-RW drive work or only a CD?
I'd like to find that out too.
___
Devel mailing list
testing-boun...@lists.laptop.org wrote on 12/12/2008 12:03:44 PM:
Chris Marshall wrote:
Mitch Bradley wrote:
Secondly, if you have a USB CD-ROM drive, you could help me by
testing it with OFW. To do so:
Will an external DVD-RW drive work or only a CD?
I'd like to find
Michail Bletsas wrote:
Yes, external DVD-RW and DVD drives work with DVD and DVD-R media.
Any chance of building a DVD-decoder into OFW? ;-)
Hmm, I probably have one of those lying around somewhere ...
Oh, here's one in my toolbox, next to the rusty fishhooks, the X-Ray
glasses
http://dev.laptop.org/~wmb/q2e19a.rom is a test build that purports to
fix http://dev.laptop.org/ticket/8451#comment:7 (This Time For Sure !)
If anybody is just itching to test a bleeding edge OFW, this is your
chance. (Okay, so it's not really all that bleeding. It's not too
different from
On 5 Oct 2008, at 10:48, Mitch Bradley wrote:
http://dev.laptop.org/~wmb/q2e19a.rom is a test build that purports to
fix http://dev.laptop.org/ticket/8451#comment:7 (This Time For Sure !)
If anybody is just itching to test a bleeding edge OFW, this is your
chance. (Okay, so it's not really
into the mouse test phase as soon as I
touched the right hand section of the touchpad it left the mouse test
and went to the next test.
2.) When I ran test mouse from the ofw prompt the screen was left
black until I hit enter a few times.
3.) Another problem is when you run 'test mouse' from the ofw
1 - 100 of 156 matches
Mail list logo