Re: Modifying 353 (xo-1) to apply the dev.laptop.org/ticket/10195 fix
by Mikus Grinbergs
Quozl wrote:
>> A symptom that I frequently observe is that 'iwlist eth0 scan'
>> (as root) does not show the radio signals that other XO_1s do show.
>
> Use scan-wifi in OpenFirmware in order to exclude the operating
> system configuration from the problem.
Thank you, thank you, thank you. This gives me a 'starting point'.
To 'scan-wifi', the "bad" XO-1s return lines like this:
RSSI: 0 SSID: Channel 1
...
RSSI: 0 SSID: Channel 1
RSSI: 41 SSID: Channel 1
To 'scan-wifi', the "good" XO-1s return lines like this:
RSSI: 0 SSID: Channel 1
... <more such lines than the "bad" XO-1s>
RSSI: 0 SSID: Channel 1
RSSI: 85 SSID: 2WIRE241 Channel 11
Note that both the "bad" XO1-s and the "good" XO-1s __will__ connect via
the (non-adhoc) mesh interface -- to me that says the silicon is working
-- though I do not know if the AP radio signal in the "bad" XO-1s is too
attenuated (bad antenna connection?) to be detected.
Thanks again, mikus
13 years, 4 months
Re: F14 os3 development image released (XO-1 and XO-1.5)
by Paul Fox
david(a)lang.hm wrote:
> On Fri, 26 Nov 2010, Samuel Greenfeld wrote:
>
> > On 11/26/2010 9:43 PM, Bernie Innocenti wrote:
> >> * Automatic power management seem to have improved a lot and is
> >> almost unnoticeable. However, can't we disable it while the
> >> laptop is on AC?
> >
> > I'm pretty certain I recall reading that XOs show the charging indicator
> > light to show they have enough external power to charge. The charging
> > light does not necessarily indicate that there is external power to
> > charge the battery and run the laptop at the same time purely from an
> > external power source.
> >
> > XO's do not presume that the external power source is an AC adapter,
> > allowing a wide range of input tolerances before you damage the
> > computer.
>
> that's fine for the default, but there should be some way to tell the
> system that when I plug it in to external power, that can be considered AC
> and disable automatic power management.
the dim, blank, and sleep timers can all be set separately for the
externally powered case, and set to 0 to disable them completely. by
default they're set the same for both battery and external power. the
one setting that's different in the default config is that on battery,
they system will eventually shut down on its own. on external power,
it will not.
(btw -- that last setting (when to shut down when sleeping) is set to
just 1 hour. since the 1.5 can stay asleep for several days before the
battery goes, one hour is probably a bit aggressive.
paul
>
> David Lang
>
> > There is a somewhat stale wiki page at
> > http://wiki.laptop.org/go/Battery_and_power with a lot of user comments
> > about what happens if you try to charge an XO via various alternative means.
> >
> > ---
> > SJG
> > _______________________________________________
> > Devel mailing list
> > Devel(a)lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
> >
> _______________________________________________
> Devel mailing list
> Devel(a)lists.laptop.org
> http://lists.laptop.org/listinfo/devel
=---------------------
paul fox, pgf(a)laptop.org
13 years, 5 months
F14 os3 development image released (XO-1 and XO-1.5)
by Daniel Drake
Thanks to everyone who provided feedback on os2. New build is ready:
http://wiki.laptop.org/go/F14_for_XO (any help on the wiki page appreciated!)
http://build.laptop.org/F14/os3/
Notably, suspend/resume is much more reliable and the graphics
glitches are gone.
Fixed tickets are:
#10460 DCON bad state on first suspend
#10461 XO-1.5 messes up serial console during resume
#10464 boot partition not mounted on partitioned XO-1
#10467 serial console getty unusable after S/R
#10478 'About my Computer' shows: :"Wireless Firmware: Not Available"
#10455 libertas-related slab corruption
#10459 libertas cfg80211 slab corruption
and:
Latest F14 updates
Linux 2.6.35.9
UVC + ldusb support
xorg.conf.d for cleaner X configuration
Firmware Q3A61 for XO-1.5
Please test and feed back!
Daniel
13 years, 5 months
F14 os2 testing images available for XO-1 and XO-1.5
by Daniel Drake
Hi,
Simon has built new Fedora 14 images for XO-1 and XO-1.5, available here:
http://build.laptop.org/F14/os2/
These efforts are now official so we'll step towards making this into
a proper release. There are still some pretty obvious issues though,
which we'll be working through.
Bug reports are now accepted, please put them in the "F14" milestone
on http://dev.laptop.org. If your bug is definitely within the realms
of the Sugar components included in the build (as opposed to OS-level
issues), the ticket would be better off on SugarLabs trac. If in doubt
you can file on dev.laptop.org or ask on this mailing list.
The big changes in this stream are below. I don't plan on making any
more, would prefer to focus on fixing and stability from now on.
Fedora 14
Sugar 0.90
GNOME 2.32
Linux 2.6.35.8
XO-1 switched from jffs2 to partitioned image: jffs2 boot, ubifs root
XO-1.5 switched from ext3 to ext4
Old OS images are not retained after olpc-update
http://lists.laptop.org/pipermail/devel/2010-September/029889.html
Activation initramfs split from "run" initramfs (for faster boot)
"Run" initramfs slimmed down to 1.9mb (no python in any non-activation
bootpath) (for faster boot)
Package list trimmed for a smaller image (even though we've likely
still grown from the F11 days, as Fedora gets bigger and bigger)
To install on XO-1 you need the .onu and .uim files, and the OFW
command to flash is:
update-nand u:\foo.onu
Daniel
13 years, 5 months
Initial F14 developers-only release for XO and XO-1.5
by Daniel Drake
Hi,
After seeing the community help significantly with F11-on-XO
development, I'm wondering if we can do something similar for a future
release. So, I've taken the first few steps in getting OLPC's
technologies rebased on Fedora 14 and Linux v2.6.35.
The result has lots of problems, but I figure that publishing the work
so far is the first step in getting things fixed.
Things are in such an early stage that I'm labelling this as a
developers-only release. To name a few: Sugar crashes all the time,
the XO-1.5 camera doesn't work, there are some funky graphics bugs on
XO-1, no power management, DCON doesn't work right on either laptop,
desktop switching lands you at a blank screen.
For now, please don't file bugs unless you include patches. And, to
take 1 bite at a time out of this huge task, lets ignore all but the
biggest sugar issues for now because there is plenty of OS work to be
done first. (or alternatively lets take sugar issues directly to SL
trac)
And the links:
2.6.35 kernel is in git://dev.laptop.org/olpc-2.6 branch olpc-2.6.35
OS build is done from 'f14' branch of olpc-os-builder
First released images are at http://build.laptop.org/F14/os1/
Trac is at http://dev.laptop.org/milestone/F14 (basically my immediate
TODO), please don't file tickets unless you include patches in these
early days
Note: I haven't tested those exact images (since Chris @ OLPC built
them), so boot-testing them can be the first task for someone. I have
been working from the same codebases making local images successfully,
so they will probably work (to the extent that things are working).
At this point this is all something put together by me in my spare
time. It's not known if or when OLPC would start working on an
official release from these efforts. But I figure that if we get
things properly stabilized and all the work is done cleanly, we'll
find one way or another to get this in the hands of deployments.
Daniel
13 years, 5 months
Re: XO-1.75 progress
by Ed McNierney
Marvell's Armada SoC family is complicated. There are multiple product lines, and multiple products in each product line, with new ones coming along all the time. So it's hard to nail down just which device is the "latest and greatest" at any time.
OLPC is (unsurprisingly) doing something a little unusual. We're trying to create a laptop (first) and then a tablet, each of which is a really full-function, general-purpose device. If you look at Marvell's ARM product selector guide and try to figure out which SoC is recommended for a laptop, you won't find one. And if you look for tablets you find either (a) SoCs for e-book readers or (b) SoCs for entertainment devices.
Our decision path is based on the obvious criteria of power consumption and cost, but we also need devices that support the interfaces we need as well. There are a lot of devices to connect to an SoC, and the decision tree for finding the SoC that fits well is tricky (mainly because a lot of interfaces may be available, but muxed in a way that makes X unusable if you want to use Y, etc.
In considering performance and cost, we want to look at processors that won't be shiny new when we have a product available, and won't be at the top of the performance curve then, either. The "high-end" SoC of last spring, when we got started, won't be the high-end SoC when a product is available. All of that led us to the Armada 610 product line.
I can't really comment much on the Marvell Mobylize product pages - the one you linked to is one I've never seen before - and they're not really pertinent to what OLPC is doing. Marvell wants to get a lot of vendors using their SoCs in a variety of different ways, so they're motivated to have a variety of sample offerings. In fact, the tablet you pointed to claims to use the Armada 168 SoC, but when you look at http://www.mobylize.org/about the last question says:
"Which Marvell processors are being used with the Moby prototype?
The Moby concept is based on Marvell's high-performance, highly scalable and low-power Marvell® ARMADA™ 610 application processor. Marvell is also making available a reference design for developing and testing applications."
You can get Marvell's spec sheets on the Armada 168 and Armada 610 SoCs at:
http://www.marvell.com/products/processors/applications/armada_100/armada...
http://www.marvell.com/products/processors/applications/armada_600/armada...
- Ed
P.S. I think I answered the touchscreen questions in my reply to Bert, but yes, we're also using the XO-1 case because that's what we have now. That saves many hundreds of thousands of dollars.
On Nov 11, 2010, at 8:42 AM, NoiseEHC wrote:
> Okay, I will rephrase my questions maybe I will get a real answer to them:
>
> 1.
> Is there any reason why do you use the latest and greatest Marvell SoC instead of an old (and maybe cheaper) one? Like the tablets on the "Marvell product platform page" do?
>
> 2.
> There were plans for touch screen and bigger display for the XO 1.75. What happened to those plans? Do you use the XO-1 case because there is what you have now, or because those plans were scrapped?
>
> Thanks!
13 years, 5 months
Re: XO-1.75 progress
by Ed McNierney
> Two questions:
>
> 1.
> Here (under Tech Specs)
> http://bit.ly/bdr0Cz
> it specs the 10" tablet with an ARMADA 168. Why did not you go with that
> processor? Would not that be cheaper?
That's a Marvell product platform page, not OLPC's.
>
> 2.
> What happened to the bigger display and the touch panel plan? As I see
> on the pictures the machines have the old 7.5" display.
Again, those are Marvell pictures, not OLPC's, and Marvell has lots of other folks interested in building their tablets. In fact, the world is full of 7" 16:9 tablet folks.
But the most pertinent answer is that we're talking about XO-1.75 right now, which is a laptop. An OLPC-3 tablet is a long way away and it's not really useful to discuss/speculate on it now. We're working on XO-1.75.
- Ed
>
> Thanks!
>
> _______________________________________________
> Devel mailing list
> Devel(a)lists.laptop.org
> http://lists.laptop.org/listinfo/devel
13 years, 5 months
XO-1.75 progress
by Chris Ball
Hi all,
OLPC Engineering had a trip to Taipei for the XO-1.75 motherboard
bringup last week. The 1.75 machine lives in the same industrial
design (display, case, batteries) as the XO-1/XO-1.5, but uses an
ARM system-on-chip from Marvell -- the Armada 610/MMP2.
There's still a great deal of driver and basic bringup work ongoing,
but we're at a point where we can share details and photos:
http://wiki.laptop.org/go/XO_1.75_A1
http://wiki.laptop.org/go/XO1.75_Bringup
http://wiki.laptop.org/go/File:XO1.75_A1_bringup.jpg
http://dev.laptop.org/~lennert/20101109148.jpg
http://dev.laptop.org/~lennert/20101108144.jpg
http://dev.laptop.org/~lennert/20101108146.jpg
http://dev.laptop.org/~cjb/1.75/1.75-a1-dmesg
http://dev.laptop.org/~cjb/1.75/xo-1.75-broughtup.jpg
The grand plan is to first move to the new ARM motherboard in the
old industrial design (XO-1.75), then move to that same motherboard
in a new tablet industrial design (XO-3). Of course, there tend to
be a lot of changes to OLPC's grand plans before devices ship!
Software-wise, we're running XO-EC and Open Firmware at the low level,
and Fedora 12 with Sugar and GNOME for the OS. We plan on moving up
to Fedora 13 or 14 as they become available for ARM. (An easy way
to help us out would be to help the Fedora ARM team with their mass
rebuilds for newer Fedora releases.)
As usual, we'll be running a Developers Program with these machines
once we've got past the necessary initial hardware fixes and made a
larger volume of boards. That's going to take several months, but
we wanted you to know that it will be coming.
Thanks!
- Chris, on behalf of the OLPC Engineering team.
--
Chris Ball <cjb(a)laptop.org>
One Laptop Per Child
13 years, 5 months
