Re: [FSO] milestone 5.1 on GTA02, opkg update failed

[Rod Whitby]

Alastair Johnson wrote:
> You can add equivalent feeds for directories under:
> http://openmoko.truebox.co.uk/repos/mazikeen/fso-milestone5/ipk
> 
> This is built using the fso makefile, but builds a few more packages
> than normal.

Alastair,

Is there a reason why you don't just add those few more packages to the
task-openmoko-feed.bb recipe - then those packages would automatically
appear in *all* official openmoko and fso distribution feeds.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: [FSO] Milestone 5, uBoot and SD, any success?

[Rod Whitby]

Andy Green wrote:
> Somebody in the thread at some point said:
> | On Wed, Feb 11, 2009 at 12:11 AM, Marc Bantle  wrote:
> |
> |> Until current rootfs' get fixed, I dropped the 'ro' option in
> |> the boot options.
> |
> | Thanks to all of you for you help. But I tried something else : Marek
> | Lindner just provided the steps for fixing the image. Here it is:
> |
> |  Not sure whether somebody was able to properly fix it or not. We
> (Chris and me)
> |  just ran into this issue and created a "fix" for the mount script.
> |  The /etc/init.d/checkroot.sh file in line 24 is the reason for the
> problem. It
> |  complains about a wrong file descriptor here: exec 9>&0  |  I removed the 2 exec lines (line 24 and line 85) and added a " <
> /etc/fstab"
> |  at the end of line 84.
> |
> | It worked for me.
> 
> It'd be great if we can get that change or something like it in the
> upstream that these images come from.

Rename the file from checkroot.sh to checkroot, and it achieves the same
effect (it is run in a shell instead of being sourced).

As I said previously, this was an upstream OE bug which made it's way
into FSO MS5 and has since been fixed upstream on OE.dev

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: FSO Milestone 5

[Rod Whitby]

Rename checkroot.sh to just checkroot (remove the .sh).
This is an upstream OE bug which made it's way into FSO ms5 - it also affected 
nslu2-linux SlugOS images.
-- Rod

-Original Message-
From: Joel Newkirk 
Date: Sunday, Feb 8, 2009 8:18 am
Subject: Re: FSO Milestone 5
To: Support for Openmoko Device Owners Reply-To: 
Support for Openmoko Device Owners 

If you manually invoke '/etc/init.d/checkroot.sh' once it's finished
>booting and is still read-only, it will correctly remount root to
>read/write...  This is the same checkroot.sh that is called early during 
>startup yet apparently fails to remount / rw at that time.  If you insert the 
>remount command near the top of checkroot.sh it WILL successfully remount 
>during initial boot, so it IS executing checkroot.sh during
>startup, but something is different between then and the manual invocation 
>from the terminal once booting has finished.  What??
>
>j
>
>On Fri, 06 Feb 2009 21:22:51 -0500, Simon Comeau Martel  
>wrote:
> You are right;
> 
> / is in read-only mode when I boot from Qi. (and in rw mode when I boot
> from uBoot)
> 
> The problem is not in 'checkroot.sh' itself; I compared that file from
> Milestone 5 to the one I had on a previous testing version which worked
> fine, and the file is exactly the same... Something must have change
> elsewhere.
> 
> --
> Simon Comeau Martel
> si...@comeau.info
> https://comeau.info
> 
> 
> Joel Newkirk wrote:
>> On Fri, 06 Feb 2009 18:57:03 -0500, Simon Comeau Martel
> 
>> wrote:
>>> I have no idea how it is possible.
>>>
>>> All I know is that if I boot Milestone 5 via Qi, get the following
>>> message in zhone:
>>>
>>> Usage: Requested ressource GSM with error.
>>>
>>> And the problem is reproducible; it happen every time.
>>>
>>
>> Read-only filesystem.  Once you've booted and see the GSM error in
> Zhone,
>> open a terminal and try "touch test" - you'll get an error noting that
> the
>> rootfs is read-only.  Qi mounts rootfs read-only at the start - I
> believe
>> /etc/init.d/checkroot.sh is where it's supposed to be remounted
> read/write.
>>
>> Many things will be 'broken' in this state, like you cannot SSH into it
>> because dropbear doesn't start properly when it can't write, and just
> about
>> everything with frameworkd is broken.
>>
>> Presuming this is the case (I'm betting;) try
>>
>> mount -o remount,rw /
>> /etc/init.d/frameworkd restart
>>
>> stop Zhone, restart it, and it should be able to activate GSM...
>>
>>
>> I've not worked through the logic in /etc/init.d/checkroot.sh or
> anything
>> yet to see where this is failing, but putting the remount command at the
>> top of that script will restore your FR to usefulness, remounting / rw
>> fairly early in the boot process.  (checkroot.sh is supposed to


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Experiences with GTA02 and OM2008.12 (was part of the "Brick" thread)

[Rod Whitby]

Craig Woodward wrote:
>  Wolfgang Spraul  wrote: 
>> Repeating rumors again and again still doesn't make them true.
> Within days of the December release there were questions about future
> GTA01 support, and it was said on the OM list that OM was no longer
> supporting the GTA01 in the OM2xxx images.  Admittedly, this was said
> by a non-OM employee (Rod Whitby), but nobody from OM spoke up to
> correct it.

I obviously don't represent Openmoko, and based my comments on the
release notes for those Om.x releases, and on public statements from
Openmoko developers - which may or may not correspond to overall
Openmoko strategy, depending on which developer is saying it ;-)

However, this is in the context of Openmoko moving to FSO-based images
"Real Soon Now", and the autobuilder for FSO-based images definitely
does support GTA01 - mainly because I maintain it, and up until recently
I only had a GTA01 to test with, and because Mickey and I want the
autobuilder to build for as many different phones as we can given the
resources available.

There has also been an update by Openmoko to gllin for the GTA01 since
Openmoko stopped releasing GTA01 Om.x images.

So you can't necessarily draw a "no support at all for GTA01" conclusion
from observing "no GTA01 Om.x images".

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: [Fwd: [openmoko-announce] Om 2008.12 & Beyond]

[Rod Whitby]

There are no new releases from downloads.openmoko.org which will work on
the GTA01.

You need to use FSO or Debian or perhaps Hacker:1 for the GTA01.

Openmoko no longer supports the GTA01 with the Om200x images.

-- Rod

Peter Rasmussen wrote:
> Anyone knows how this will work with the Neo 1973 (GTA01)?
> 
> I would like to just go ahead and see how it works, but as the release 
> notes have this warning:
> 
> *WARNING:* It is recommended that you back up your Neo prior to 
> installing any updates.
> 
> Do not attempt to install 2008.12 to the Neo 1973 (GTA01). It is not 
> compatible with this earlier model.
> 
> So it seems that it may not be such a good idea.
> 
> However, I do believe I have seen posts about GTA01, GTA02 and an 
> upcoming GTA03 being similar from what they expect from the HW that I 
> actually don't understand this warning?!
> 
> Will an attempt to install it brick my GTA01?
> 
> Thanks for any clarification,
> Peter
> 
> 
> 
> 
> 
> Subject:
> [openmoko-announce] Om 2008.12 & Beyond
> From:
> William Lai 
> Date:
> Fri, 19 Dec 2008 16:40:46 +0800
> To:
> annou...@lists.openmoko.org
> 
> To:
> annou...@lists.openmoko.org
> 
> 
> Dear Community,
> 
> The latest testing image for Om 2008 has been uploaded to our stable
> branch.  This is the fastest image to date.  Om 2008.12 is recommended
> for current users of Om 2008.9 and/or prior images. It includes general
> operating system improvements that enhance the speed and stability of
> your Neo.
> 
> To install the 2008.12 update on the Neo FreeRunner, download the Root
> Filesystem and the Kernel image files from:
> 
> Root Filesystem
> http://downloads.openmoko.org/releases/Om2008.12/Om2008.12-om-gta02.rootfs.jffs2
> 
> Kernel
> http://downloads.openmoko.org/releases/Om2008.12/Om2008.12-om-gta02.uImage.bin
> 
> **Note that flashing the Neo FreeRunner will overwrite all your existing
> data, so remember to do a backup.  There's also an upgrade path, but
> only the clean upgrade from Om2008.9 has been tested.  Please check:
> 
> http://lists.openmoko.org/pipermail/community/2008-December/037457.html
> 
> A full test report from our QA team can be found here:
> 
> http://people.openmoko.org/testing/software/GTA02/Testreport/Om2008.12-2/Om2008.12.2_test_report.pdf
> 
> Release notes along with known issues are here:
> 
> http://wiki.openmoko.org/wiki/Om_2008.12_Update
> 
> Many of you know that most of who's left here are focused on the next
> major release, Om 2009.  Although a date has not been set for this
> release, we're working around the globe, day and night, to get the right
> pieces to fit.
> 
> For starters, here are some updates on our current work plans:
> 
> * merging om.dev back to OE upstream
> * updating to andy tracking following this release
> * paroli:  http://code.google.com/p/paroli
> 
> Thanks everybody for you patience (and endurance).
> May the best days be ahead of us.
> 
> 
> 
> Openmoko Team
> 
> 
> 
> This message was sent using IMP, the Internet Messaging Program.
> 
> 
> 
> 
> 
> 
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Angstrom Repository Broken?

[Rod Whitby]

Rod Whitby wrote:
> Paul wrote:
>> Has anyone tried adding angstrom's repository and doing a opkg upgrade
>> lately?  It seems to break the FreeRunner.
> 
> I doubt that the Angstrom repository was ever designed to support the
> FreeRunner

To be precise, Angstrom does support the FreeRunner, but only if you are
running the Angstrom distribution on the FreeRunner.

My comments assume you are running one of the Openmoko distributions
(2007.x, 2008.x, FSO, SHR, FDOM, etc) on the FreeRunner.

If you are in fact running the Angstrom distribution, and the angstrom
feed no longer works for that distribution, then you should report the
error in the OpenEmbedded bug tracker.  But *only* do so if you are sure
that you are running the *Angstrom* distribution, not an
Openmoko-derived distribution.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Angstrom Repository Broken?

[Rod Whitby]

Paul wrote:
> Has anyone tried adding angstrom's repository and doing a opkg upgrade
> lately?  It seems to break the FreeRunner.

I doubt that the Angstrom repository was ever designed to support the
FreeRunner, and the fact that it somewhat worked previously was pure
coincidence due to somewhat compatible processors.

As the Angstrom repository moves forward with different compiler and
library versions, you can be sure it will sooner or later be
incompatible (as seems to already be the case by your report).

If you want an application that is in the Angstrom repository, then just
ask someone to add it to the task-openmoko-feed.bb recipe in
OpenEmbedded, and then it should automatically appear (courtesy of
correctly set up autobuilders) in the feeds for all the Openmoko
distributions.  Then you will know that those applications have been
compiled in a way to be compatible with the distribution you are running.

Remember, never mix feeds.  Use only the feed which is designed for the
distribution you are running.  If an application is not there, then ask
someone with OpenEmbedded commit rights to add it to task-openmoko-feed
(or if you don't know anyone, then submit a ticket to Openmoko).

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: python glib broken in fso-testing from today

[Rod Whitby]

Jim Ancona wrote:
> A followup for anyone who's interested. Since the bug I filed was marked 
> invalid and closed, I tried flashing today's image, only to have the 
> same problem.

I've re-opened the bug until the feeds and images are fixed.

> Based on the information provided by Mickey and Rob, I did 
> the following:
> 
> [EMAIL PROTECTED]:~# opkg remove -force-depends python-pygobject
> Removing package python-pygobject from root...
> [EMAIL PROTECTED]:~# opkg install 
> http://downloads.freesmartphone.org/fso-testing/feeds/armv4t/morgue/python-pygobject_2.14.2-r1_armv4t.ipk
>  
> 
> Downloading 
> http://downloads.freesmartphone.org/fso-testing/feeds/armv4t/morgue/python-pygobject_2.14.2-r1_armv4t.ipk
> Installing python-pygobject (2.14.2-r1) to root...
> Configuring python-pygobject
> 
> I then ran "/etc/init.d/frameworkd start" and waited a while for zhone 
> to connect. When it didn't, I rebooted. (I may not have waited long 
> enough.) After the reboot, Zhone connected and I was able to make a call.
> 
> This procedure will probably be neccessary to use any fso-testing image 
> until they fix the broken python-pygobject package.

I've removed the bad package from the FSO autobuilder, and it's
currently rebuilding the good package and images containing it.  Once
that's done it will rsync with the feeds area to deploy them.  That
rsync will also remove all the non-working images.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: fso-testing feed out of sync

[Rod Whitby]

>I have this working now, thanks. Yesterday git was being refused connection 
>but today it is working like a charm. I guess the problem may have been at my 
>end.

The git server was offline for some time.

>I can also confirm that the enlightenment issue is fixed in the lastest 
>fso-testing image on downloads.freesmartphone.org. I am not sure what the 
>issues will be with opkg when switching to this feed from the previous 
>shr.bearstech.com feed as there seem a lot of differences.

I would not recommend ever switching feeds on an image - I can only recommend 
flashing a new image from downloads.freesmartphone.org.

In fact the main reason for bringing downloads.fso  online was because there is 
no feed suitable for updating the fso3 milestone image due to a bitbake git 
fetcher problem, so you can't even use these feeds with that image.

The only thing I can recommend is to flash a new fso-testing image from 
downloads.freesmartphone.org, and use the feeds which come pre-configured in 
the image.

-- Rod


___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: fso-testing feed out of sync

[Rod Whitby]

Richard Cooke wrote:
> fso-testing is still broken. Out of desparation I have flashed the latest
> fso-testing image from downloads.freesmartphone.org. x.log still shows 
> enlightenment: symbol lookup error: enlightenment: undefined symbol:
> edje_scale_set
> 
> Any chance you could make the relevant ipks available please? I can't get
> the build system to work on my ubuntu box.

The autobuilder that feeds downloads.freesmartphone.org runs Ubuntu 7.10
and fso-testing builds fine there using the FSO Makefile at:

  http://downloads.freesmartphone.org/Makefile

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: fso-testing feed out of sync

[Rod Whitby]

Richard Cooke wrote:
> 
> -stacy wrote:
>> edje is out of sync with e/illume and friends:
>>
>> libedje0_0.9.9.043+cvs20080802-r0_armv4t.ipk
>> edje-utils_0.9.9.043+cvs20080802-r0_armv4t.ipk
>> edje-viewer_0.0.0+svnr35984-r1_armv4t.ipk
>> illume_0.0+svnr35984-r13_armv4t.ipk
>> e-wm_0.16.999.043+svnr35984-r11_armv4t.ipk

fso-testing on downloads.freesmartphone.org has:

 libedje0_0.5.0.043+svnr35984-r3
 edje-utils_0.5.0.043+svnr35984-r3
 edje-viewer_0.0.0+svnr35984-r1
 illume_0.0+svnr35984-r13
 e-wm_0.16.999.043+svnr35984-r11

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: What packages have cu and socat?

[Rod Whitby]

Erin Yueh wrote:
> Rod Whitby wrote:
>> Erin Yueh wrote:
>>> Hi,
>>> i use OE to build package and i upload socat package here. You may try 
>>> it on.
>>>
>>> http://cs1.cs.nyu.edu/~wcy203/socat_1.3.2.1-r1_armv4t.opk
>> Since you work at Openmoko, why didn't you just add socat to the
>> task-openmoko-feed bitbake recipe, and then re-run the openmoko
>> autobuilder to update the feed?
>>
>> Why would someone with an @openmoko.com address be putting pre-built
>> packages anywhere other than in the official openmoko feeds?
>>
>> -- Rod
> mmh. yeah, we do have this recipe in OE, but i don't have this 
> permission to add it to repository. I would cc this email to our distro 
> team.

Julian,

Does Openmoko build the 'task-openmoko-feed' recipe and publish that to
the official feeds?

Who should community members contact if they have a recipe which already
builds fine from the org.openmoko.dev git repository, and they just want
that package added to task-openmoko-feed so that it automatically
appears in the official feeds?

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: What packages have cu and socat?

[Rod Whitby]

Erin Yueh wrote:
> Hi,
> i use OE to build package and i upload socat package here. You may try 
> it on.
> 
> http://cs1.cs.nyu.edu/~wcy203/socat_1.3.2.1-r1_armv4t.opk

Since you work at Openmoko, why didn't you just add socat to the
task-openmoko-feed bitbake recipe, and then re-run the openmoko
autobuilder to update the feed?

Why would someone with an @openmoko.com address be putting pre-built
packages anywhere other than in the official openmoko feeds?

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: [EMAIL PROTECTED] gone?

[Rod Whitby]

sparky mat wrote:
> I am not able to find the FSO binaries/repository at
> shr.bearstech.com. Instead, I see that SHR binaries are present. I
> tried them out and there are (many) issues.

There is a shr-devel mailing list on which you can discuss those issues 
if you have an interest in getting them resolved.

> Just wondering why FSO builds were removed from here. This was my
> preferred build/repository.

FSO official feeds are now at downloads.freesmartphone.org - Mickey was 
supposed to send an email announcement, but that hasn't happened yet.

He did blog about it, but that's not really an announcement:
http://www.vanille-media.de/site/index.php/2008/09/18/staugstin-braunschweig-berlin-taipei/


So shr.bearstech.com is now used for the purpose which it's name 
proclaims - its' the feeds for the SHR distro.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Duplicates - they won't be fixed on the server, so fix it locallyor live with it

[Rod Whitby]

Joel Newkirk wrote:
> I've built and administered dozens of mailservers at ISPs, processing at
> one point over a million SMTP connections a day, so I've got some idea how
> 'hard' the problem is.  I also know what happens to servers and their
> resources when they're overtaxed.  But even from a more general
> perspective, hiding a problem never makes it go away.
> 
> I realize this thread is utterly off-topic of Openmoko support, and believe
> me I was hesitant to bring it up again for that reason.  But it really DOES
> need to be fixed, and this list is a reliable way of reaching several
> persons at Openmoko, persons who presumably have observed the effect
> themselves and can grasp the problem.  
> 
> Even with every message in this thread, it's still less than the number of
> duplicate messages received in a day...  ;)  And if your mail reader is
> advanced enough to offer duplicate-removal, it likely lets you ignore
> selected threads as well.

The point is that instead of endlessly discussing this on the list, where
nobody on the list can actually do anything directly about it, people with
experience such as yourself should contact the administrators of the
Openmoko mail infrastructure directly and fix it in private.

If the Openmoko mail administrators are not willing to even talk to you,
then there is even *less* chance that it will ever get fixed, and so
discussing it on the list is even less useful.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Duplicates - they won't be fixed on the server, so fix it locally or live with it

[Rod Whitby]

Q: How long has there been duplicates on the Openmoko mailing lists?
A: Since the list got so big that sita.openmoko.org can't handle it.

Q: How long has that been?
A: At least a year, maybe more.

Q: Has Openmoko done anything about it?
A: Doesn't seem so.  Must be a hard problem.

Q: Is Openmoko likely to fix it?
A: If they haven't fixed it by now, then chances are they probably won't.

Q: What should I do about it?
A: Don't email the list about - we all know already.

Q: How can I fix it locally for me?
A: Get a mail reader that understands that a message with a duplicate
   Message-Id header field doesn't need to be displayed to the user.

Can we stop now?

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Pdf Viewer and Spread Sheet for FSO Milestone 2

[Rod Whitby]

Offray Vladimir Luna Cárdenas wrote:
> I'm using FSO Milestone 2
...
> I want to use my Freerunner for my classes and for that I need, for the 
> moment, a pdf reader and an spread sheet.

epdfview is in the fso feeds at shr.bearstech.com

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: FSO compile error

[Rod Whitby]

>>> Am Sonntag 31 August 2008 12:42:45 schrieb Javi Roman:
 Does it exists any instructions details  that allows to build FSO
 image without MokoMakefie?

See http://shr.bearstech.com/README for an FSO-specific Makefile which
runs the FSO feeds autobuilder.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: MokoMakefile broken?

[Rod Whitby]

sparky mat wrote:
> I tried building FSO by following the instructions on the wiki. I get
> the following error.
> 
> Already on branch "bitbake-om"
> [ -d stamps ] || mkdir stamps
> touch stamps/bitbake
> ( [ -e stamps/openembedded ] && \
>   [ -e openembedded/.git ] ) || \
> ( git clone -n git://git.openembedded.net/git/openmoko.git
>  openembedded )
> Initialized empty Git repository in //openembedded/.git/
> fatal: The remote end hung up unexpectedly
> fetch-pack from 'git://git.openembedded.net/git/openmoko.git
> ' failed.
> make: *** [setup-openembedded] Error 1
> 
> Does anyone else get the same error?

This usually means that you're behind a corporate or ISP firewall which
does not allow the git protocol to traverse it.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: gtk+ libraries on FSO

[Rod Whitby]

sparky mat wrote:
> 
> Sure - as soon as you (or someone else) tells me what the name of the
> OpenEmbedded recipe that needs to be added to task-openmoko-feed is ?
> 
> Is this the bit bake recipe?

Yes.  You would have saved a round of emails if you had put the name of
it in that message too (assuming you know which one it is that you want).

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: zip missing

[Rod Whitby]

sparky mat wrote:
> I can't find any package named zip (apart from official feeds, i am
> using feed from http://shr.bearstech.com/fso-unstable/ipk/armv4t/ )

zip is now available in the fso/shr feeds.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: gtk+ libraries on FSO

[Rod Whitby]

sparky mat wrote:
> It doesn't seem to have come up yet! No firefox-3.0 available.

It's there now.  There was a problem earlier in the feed build which I
had to fix before it could complete.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: gtk+ libraries on FSO

[Rod Whitby]

sparky mat wrote:
> Could you also add gtk+-2.0 development libraries to the feed as well?

Sure - as soon as you (or someone else) tells me what the name of the
OpenEmbedded recipe that needs to be added to task-openmoko-feed is ?

> Btw, I am having trouble building FSO (as I have mentioned in another
> thread). No one has responded so far :-(

Seems to be building fine on the autobuilder.  Replicate that build
environment (see http://shr.bearstech.com/README for details) and you
should be fine.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: gtk+ libraries on FSO

[Rod Whitby]

Tom Rethaller wrote:
> I'd like to use pygtk on FSO, but i can't find any gtk package there :
> http://shr.bearstech.com/fso-testing/ipk/

The python-pygtk-dev package is already in the feeds:

http://shr.bearstech.com/fso-testing/ipk/armv4t/python-pygtk-dev_2.10.4-ml8_armv4t.ipk

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: gtk+ libraries on FSO

[Rod Whitby]

sparky mat wrote:
> While trying to fulfil the dependencies for compiling Firefox 3 on FSO
> (on the phone), I realized that GTK+ libraries are not there. Apart from
> the official repositories, i use the one at shr.beartech.com
> . But I can't find gtk+ dev libraries anywhere.

I've just added firefox 3 to task-openmoko-feed, which means that it
should appear on shr.bearstech.com within the next hour or so.

That should save you some time trying to build it on the device.

Note that *everything* in the fso feeds is cross-compiled.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: emdebian toolchain?

[Rod Whitby]

arne anka wrote:
> is it possible to use the emdebian tools to build packages for debian on  
> the fr?
> that qemubuilder is rather slow compared to cross compiling with the  
> mokomakefile ...

Wow, I never thought I'd see the day that someone refers to a
MokoMakefile build as the fast option :-)

-- Rod
-- MokoMakefile author

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Installing applications in FSO

[Rod Whitby]

digger vermont wrote:
> On Wed, 2008-08-27 at 18:31 +0200, Michael 'Mickey' Lauer wrote:
>> Am Mittwoch 27 August 2008 18:16:53 schrieb sparky mat:
>>> Is it possible to install applications to FSO? (trying FSO for the first
>>> time)
>> Sure. To make the .desktop files appear you need to set the category = 
>> Office 
>> or change some xdg configuration file which I don't know offhand.
>>
> In the same vein.  I've been tracking
> http://shr.bearstech.com/fso-testing/
> 
> If I add opkg.conf files for
> http://downloads.openmoko.org/repository/testing/
> 
> and do an opkg upgrade will fso get muddled up?  Should I add some "arch
> feed-name priority" lines?

Never mix feeds.  Period.

Ask someone with OE commit privs to add whatever applications you want
in the fso-testing feeds to simply add that application's name to
task-openmoko-feed.bb and it will be automatically built.

If you need a specific application ipk from a different feed, then
download the ipk and install it manually, using your judgement to
determine whether it's dependencies are going to screw your system up.
Take a full backup of your rootfs first.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Latest ASU image & TangoGPS

[Rod Whitby]

Jelle De Loecker wrote:
> I immediately upgraded to the ASU (since I saw no point in playing
> around with a deprecated software stack, even if it does work better)
> but for some reason TangoGPS doesn't work in it! Most buttons don't work
> (Map/Trip/...) the screen is useless, ...
> 
> I went for the latest image from the 20th of august (since the last
> "stable" release couldn't receive SMS messages, which is quite important
> in a cell phone)

If you're talking about an image from buildhost, that's not ASU.

Nothing on buildhost is official ASU or ASU updates.

There is only one ASU image released so far, and only one set of feeds
(zecke's) and neither are on buildhost.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: opkg software repository extremely small? no gpsd? no openmoko-browser2?

[Rod Whitby]

Timo Jyrinki wrote:
> 2008/8/16 Thorben Krueger <[EMAIL PROTECTED]>:
>> So gpsd and browser stuff is only to be had via _unofficial_
>> repositories? huh. Getting started page in the wiki should mention
>> that
> 
> It was different until last week or so, when huge amounts of packages
> disappeared. Tangogps, gpsd, openmoko-browser2 all used to be in the
> default repositories.

That's simply because they stopped autobuilding task-openmoko-feed

Dunno why ...

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: How to compile assassin?

[Rod Whitby]

Rorschach wrote:
> Okay I already asked it but noone gave me an answer: how was assassin 
> compiled on the neo because I can't. I can't execute ./autgen.sh because of a 
> lot of missing dependencies. So do you really have compiled everything by 
> hand?
> 
> I mean someone obviously compiled assassin on om2008.8, else we couldn't use 
> it. But how did he?

Most (if not all) images and packages are cross-compiled on an x86 host.

That's not to say you can't (or shouldn't) native compile things on the
neo, just that most people are not doing that, so you can't expect it to
work out of the box.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Openmoko Flasher - Unable to Flash Root File System - Error 60

[Rod Whitby]

Dr. H. Nikolaus Schaller wrote:
> Am 13.08.2008 um 14:35 schrieb Rod Whitby:
>> Please advise people to use '-a rootfs' instead of '-a 5', since -a 5
>> will break the next time that Openmoko decides to change the mtd  
>> layout
>> (as did happen between GTA01 and GTA02).
> 
> Ah, that explains everything.
> 
> Does someone have a good list of all allowed values of -a? And, are  
> they the same between GTA01 and GTA02?

At least the following are:

u-boot, kernel, rootfs

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Unable to Flash Root File System - Error 60

[Rod Whitby]

Jay Vaughan wrote:
> Here is how I do it:
> 
> DYLD_LIBRARY_PATH=/Applications/OpenMoko\ Flasher\ 1.2.app/Contents/ 
> MacOS/../Resources/ /Applications/OpenMoko\ Flasher\ 1.2.app/Contents/ 
> MacOS/dfu-util -a 5 -R -D  openmoko-image.jffs2

Please advise people to use '-a rootfs' instead of '-a 5', since -a 5 
will break the next time that Openmoko decides to change the mtd layout 
(as did happen between GTA01 and GTA02).

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Differences between daily builds and Om2008.8

[Rod Whitby]

Believe it or not, those directories do *not* contain ASU/Om2008.08

Hopefully the Openmoko build team will fix this soon, as it's obviously 
causing a great deal of confusion and damaged software configurations.

-- Rod
[Top-posted to match existing layout]

Max Kiva wrote:
> You can pick from any of the directories listed here
> 
> http://buildhost.openmoko.org/daily/freerunner/200808/
> 
> 
> - Original Message 
> From: abatrour <[EMAIL PROTECTED]>
> To: support@lists.openmoko.org
> Sent: Wednesday, 13 August, 2008 11:55:07 AM
> Subject: Re: Differences between daily builds and Om2008.8
> 
> 
> Am I missing something? How do I get this updated 2008.8? I wan't to try it
> out and also update the wiki

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Unable to Flash Root File System - Error 60

[Rod Whitby]

Markku wrote:
> I'm not able to flash my Neo Freerunner root file system. I'm using Mac OS
> 10.5.4, and using the OpenMoko Flasher 1.4 to try to flash it. I'm able to
> flash kernels fine, but when I try to flash the root file system (I'm trying
> to flash it with OM2008.8.rootfs.jffs2, I get the following errors:
> 
> On the FreeRunner (while in uBoot):
> Starting DFU DOWNLOAD to partition "factory"
> End of write exceeds partition end

Use "-a rootfs" on the dfu-util command line.  You're writing to the 
wrong partition.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Differences between daily builds and Om2008.8

[Rod Whitby]

sparky mat wrote:
> I flashed the latest build (2008.8.11) from 
> http://buildhost.openmoko.org/daily/freerunner/
> 
> USB networking is gone. Glamo doesn't seem to be installed by default 
> either. And, Om2008.8 doesn't update anything on 'opkg upgrade'.
> 
> So, how is this different (configuration wise) from the Om2008.8 
> release? Daily builds were behaving differently on and before the 
> Om2008.8 release, as well. So, if changes were made onto a different 
> branch for the 08.08.08 release, shouldn't it be merged into the trunk?

buildhost does not build Om2008.8 - it builds org.openmoko.dev which is 
completely different from org.openmoko.asu.testing (which is what I say 
it should build).

See http://docs.openmoko.org/trac/ticket/1809 for details.

As to why this situation is allowed to continue by Openmoko, is beyond 
my understanding.

-- Rod



___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Trouble flashing 2008.08

[Rod Whitby]

Brian C wrote:
> Mike MacHenry wrote:
>> The problem is I can't figure out which of roughly 50 files from the
>> this list I should download.
>>
>> http://buildhost.openmoko.org/daily/freerunner/200808/20080806/
> 
> You are looking for:
> 
> The ASU/2008.8 rootfs
> http://buildhost.openmoko.org/daily/freerunner/200808/20080806/openmoko-qtopia-x11-image-om-gta02.jffs2

FYI, that image is not ASU/2008.08, since buildhost builds from the 
org.openmoko.dev branch, not the org.openmoko.asu.* branches.

So whilst it might give an idea of what ASU might look like, it will 
certainly have lots of bugs and features (e.g. the FSO theme) which 
definitely are not in the image you get when you build from the correct 
branch.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Re: Neo Freerunner hangs

[Rod Whitby]

Vimal Joseph wrote:
> On Fri, Aug 1, 2008 at 5:32 PM, Andy Green <[EMAIL PROTECTED]> wrote:
> 
>> Try holding the power button down for "10 seconds" next time, if that
>> does turn it off then my thoughts would turn towards Glamo-related
>> problems.  Otherwise something even more 'orrible is happening.
> 
> I'v erased the nand kernel and nand rootfs and flashed
>  Openmoko-Freerunner-20080424-om-gta02.rootfs.jffs2
>  uImage-2.6.24+git20080424-om-gta02.bin
> 
> Still the same problem. Nothing happens when holding the power button
> for 10 seconds, no response.

If you have a debug board, hook it up and look for some output from 
u-boot after you preset the reset button on the debug board.  If it 
stops after printing the u-boot version line but before printing the 
Glamo identification line, then it's probably the Glamo problem.

See the kernel list for details.

-- Rod

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support