Re: gps via python, using dbus

[Matt]

Firstly thank for posting the code, very intresting to pore over.

However, it has not worked for me.
Any ideas ?

debian-gta02:~# python ogpsd_methods.py
Traceback (most recent call last):
   File "ogpsd_methods.py", line 8, in 
 constatus = 
obj.GetConnectionStatus(dbus_interface='org.freedesktop.Gypsy.Device')
   File "/var/lib/python-support/python2.5/dbus/proxies.py", line 68, in 
__call__
 return self._proxy_method(*args, **keywords)
   File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, 
in __call__
 **keywords)
   File "/var/lib/python-support/python2.5/dbus/connection.py", line 
622, in call_blocking
 message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: 
Method "GetConnectionStatus" with signature "" on interface 
"org.freedesktop.Gypsy.Device" doesn't exist

debian-gta02:~# python ogpsd_methods.py
Traceback (most recent call last):
   File "ogpsd_methods.py", line 8, in 
 constatus = 
obj.GetConnectionStatus(dbus_interface='org.freedesktop.Gypsy.Device')
   File "/var/lib/python-support/python2.5/dbus/proxies.py", line 68, in 
__call__
 return self._proxy_method(*args, **keywords)
   File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, 
in __call__
 **keywords)
   File "/var/lib/python-support/python2.5/dbus/connection.py", line 
622, in call_blocking
 message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: 
Method "GetConnectionStatus" with signature "" on interface 
"org.freedesktop.Gypsy.Device" doesn't exist



Sascha Wessel wrote:
>> Could someone kind and helpful post an example of python code to get gps 
>> data via dbus?
> 
> ogpsd_signals.py listens for gypsy signals
> ogpsd_methods.py calls gypsy methods once and exits
> ogpsd_resource.py requests the GPS resource from ousaged (power on while 
> running, see
> /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron)
> 
> Greetings,
> Sascha
> 
> 
> 
> 
> 
> ___
> 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

GPRS issue

[Armin ranjbar]

Hi all 

do anyone has any idea on this issue ? 
http://pastebin.com/m33955460


-- 
Armin ranjbar , System Administrator

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

Re: gps via python, using dbus

[Sascha Wessel]

On Tue, Sep 02, 2008 at 07:39:09PM +1000, Matt wrote:
> Firstly thank for posting the code, very intresting to pore over.
> 
> However, it has not worked for me.
> Any ideas ?

Many... the most common problem for me is a very high interrupt load;
more than 1000 per second in powertop. But there are others too...

However, one of the following may help:

* /etc/init.d/dbus restart
* /etc/init.d/fso-frameworkd restart
* reboot
* just wait and try again later


Greetings,
Sascha


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

Re: GPS Problem (maybe antenna?)

[Sebastian M.]

Quoting "Marco Trevisan (Treviño)" <[EMAIL PROTECTED]>:

> Ole Kliemann wrote:
>> Unfortunately I cannot help you. Just can tell you that I have exactly
>> the same problem. I'm now waiting for the fix for the GSM-buzz, so I can
>> send the FR to my distributor and get both the GSM and GPS fixed. ;-)
>
> Which distributor will give you them as warranty fixes?
>

In Germany (and the whole European Union, I guess) the retailers are  
forced to give a 2 years warranty and because of that they have to  
replace goods which have problems like an advertised feature not  
working (like the Freerunners GPS [-hardware] in my case).

As far as I know the same thing applies to distributors (in Germany  
and maybe EU as well).

Of course this may vary in your country (Germany/EU have a very strict  
consumer protection), so you should ask the company who sold the  
Freerunner to you.

Cheers, Sebastian

-- 
Sebastian M.
Student of Computer Science at the University of Kaiserslautern.


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

Re: Gesture Listener

[Jim Colton]

What I think happens is what I stated in my original mail.  ;)   Each
application that has registered a doLayout() callback with the gesture
listener gets laid out again and therefore each component of the layout will
know it's new position and dimension so that touch screen events for it can
be identified and acted upon.  A button component for example.

On Mon, Sep 1, 2008 at 9:37 PM, Joel Newkirk <[EMAIL PROTECTED]> wrote:

> Jim Colton wrote:
> >
> > So that the GUI applications work right, seems to me that they need to
> > be built using "Layout managers", the top manager in the GUI being
> > called with the new dimensions by this gesture listener... after the
> > orientation has changed.  Each manager calls doLayout() on each of
> > it's children.
>
> What do you think happens when a window is resized? ;)  It's usually an
> oversight if an app is written with the expectation of permanent
> unchanging window dimensions.  (even console-based Midnight Commander
> redraws itself to fit if its containing console is resized, though
> without the patch I'm polishing up it can't switch from horizontal to
> vertical layout automatically, just reshapes itself to fit)  Even
> developing for a purely cellphone environment with modal apps you
> shouldn't presume you'll always have the same dimensions - in three
> months there might be an updated model with a higher resolution, for
> example.
>
> j
>
>
> ___
> 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

Om 2008.8 update doesn't boot (it freeze) after removing battery

[Thomas Bertani]

On my fr, with om 2008.8 update the boot failed a lot of times,then it boots
but when I remove battery to shutdown (for freeze) and then I boot, I have
to reboot it a lot of times for get it booting correctly, it stops booting
when serverx starts...
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Pdf Viewer and Spread Sheet for FSO Milestone 2

[Offray Vladimir Luna Cárdenas]

Hi all,

I'm using FSO Milestone 2 and is the most beautiful and quick image of 
the three (ASU/Gtk/FSO) I have probed. The dialer is the only 
application with problems in responsiveness (almost 5 seconds to launch 
compared to the almost instantaneous of the other ones) and the first 
digit of the phone number only is seen when you type the second one, but 
I think that this will be corrected in another milestone. So, keep the 
good work :-)

I want to use my Freerunner for my classes and for that I need, for the 
moment, a pdf reader and an spread sheet. Do you have any advice or 
suggestion of something already packaged? I have being thinking in SIAG 
(Scheme In A Grid) for the spread sheet and now I'm trying to get it 
working on my desktop to see if makes sense to put it also in FR.

Cheers,

Offray

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

Re: Debian root password

[Chris Jenks]

On Sun, 31 Aug 2008, archon44 wrote:

> Chris Jenks wrote:
>>
>> I seem to have successfully installed debian on my SD card and am able to
>> boot to zhone, but when I try to ssh to [EMAIL PROTECTED] it won't take a
>> blank password. I am able to login to 2008.8 from the same host
>> successfully. I would try to reset the password from xterm, but no
>> keyboard appears when I press or hold the aux key! Any suggestions?
>>
> Try to ssh to your 2008.08/2007.02, chroot to microsd card filesystem
> mountpoint (for me it was /media/mmcb*) and then simply change your debian
> password. Worked for me

   This is a good solution. I was going to take it, but first I wanted to 
see if I could fix the problem by connecting the external USB keyboard I 
finally got a USB A - mini USB A (5 pin) adapter for. I was disappointed 
that the keyboard didn't seem to get power nor did it get recognized (Fn 
keys didn't work), so, not seeing a better way, I did a power cycle to 
reboot and waited through the fsck. After this the keyboard still didn't 
work, but then I reconnected the USB to the host I was able to shell in 
using a blank password. So the password was reset from non-blank to blank 
after a (second) hard reboot.
   I haven't researched the keyboard problem - I assume I need a powered 
hub, but I'll read. No need to address that here.

   Chris

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

Re: Om 2008.8 update doesn't boot (it freeze) after removing battery

[Marco Trevisan (Treviño)]

Thomas Bertani wrote:
> On my fr, with om 2008.8 update the boot failed a lot of times,then it 
> boots but when I remove battery to shutdown (for freeze) and then I 
> boot, I have to reboot it a lot of times for get it booting correctly, 
> it stops booting when serverx starts...

I got this too [1]. Applying one of the latest andy patches for glamo 
[2] to the stable kernel I fixed the problem.
If you want test, give a try to this kernel image [3].
Report in any case! ;)

Bye!


[1] http://lists.openmoko.org/nabble.html#nabble-td586044
[2] fix-glamo-crank-memory-to-90MHz.patch
[3] 
http://downloads.tuxfamily.org/3v1deb/openmoko/uImage-gta02-stable-glamo-video-patch%2bgitd744c88c149269b95ec068c8615e492375415d6d.bin

-- 
Treviño's World - Life and Linux
http://www.3v1n0.net/


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

Re: using openocd

[Michael Shiloh]

Tony, any idea what that error means? I searched a little and failed to 
find.

Lynn Nguyen wrote:
> 
> I get:
> 
> [  459.596147] usb 3-1.3: new full speed USB device using uhci_hcd
> and address 27
> [  459.744465] usb 3-1.3: device not accepting address 27, error -71
> 
> 
> I don't have any USBs showing up in tty when I plug it in.
> 
> Lynn
> 
> On Mon, Sep 1, 2008 at 7:59 PM, Michael Shiloh <[EMAIL PROTECTED] 
> > wrote:
> 
> Lynn Nguyen wrote:
>  > I tried the sequence but still the same errors.
>  >
>  > Should I have a /dev/ttyUSB1 when I plug in the debug board?
> because i
>  > dont...
>  >
>  > Lynn
> 
> Did you check other devices? It may have shown up on a different tty.
> 
> what does dmesg or tail -f /var/log/messages say as you plug in the USB
> cable?
> 
> Michael


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

Re: Om 2008.8 update doesn't boot (it freeze) after removing battery

[Thomas Bertani]

thanks

2008/9/2 "Marco Trevisan (Treviño)" <[EMAIL PROTECTED]>

> Thomas Bertani wrote:
> > On my fr, with om 2008.8 update the boot failed a lot of times,then it
> > boots but when I remove battery to shutdown (for freeze) and then I
> > boot, I have to reboot it a lot of times for get it booting correctly,
> > it stops booting when serverx starts...
>
> I got this too [1]. Applying one of the latest andy patches for glamo
> [2] to the stable kernel I fixed the problem.
> If you want test, give a try to this kernel image [3].
> Report in any case! ;)
>
> Bye!
>
>
> [1] http://lists.openmoko.org/nabble.html#nabble-td586044
> [2] fix-glamo-crank-memory-to-90MHz.patch
> [3]
>
> http://downloads.tuxfamily.org/3v1deb/openmoko/uImage-gta02-stable-glamo-video-patch%2bgitd744c88c149269b95ec068c8615e492375415d6d.bin
>
> --
> Treviño's World - Life and Linux
> http://www.3v1n0.net/
>
>
> ___
> 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: using openocd

[Kees Jongenburger]

On Mon, Sep 1, 2008 at 6:33 AM, Lynn Nguyen <[EMAIL PROTECTED]> wrote:
> Hey All,
>
> I was wondering if anyone was using the Neo1973 (GTA01v4) with Debug board
> v3. I used the openocd.cfg available on the wiki and I get this problem:
> Info:openocd.c:82 main(): Open On-Chip Debugger (2006-08-01 12:00 CEST)
> Info:configuration.c:50 configuration_output_handler(): Command
> ft2232_device_desc not found
> Info:configuration.c:50 configuration_output_handler(): Command
> ft2232_layout not found
> Info:configuration.c:50 configuration_output_handler(): Command
> ft2232_vid_pid not found
> Error:   jtag.c:1219 jtag_init(): No valid jtag interface found (ft2232)
>
> It seems like openocd is having some trouble with ft2232 because I don't see
> anything wrong with those commands.

yes , perhaps libft2232 is not enabled in you openocd build?


greetings

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

Re: Pdf Viewer and Spread Sheet for FSO Milestone 2

[Christopher Allan Webber]

If you install Debian, it comes with FSO (and pretty much looks the same
out of the box), but you have access to all of debian's packages.  From
there you could install either xpdf of evince

sudo apt-get install evince
sudo apt-get install xpdf

I'm not sure how well openoffice, that beast, would be able to run on
the openmoko.  Gnumeric is a bit more lightweight than open office,
iirc.  You could try that.

Hope that helps!
 - Chris

Offray Vladimir Luna Cárdenas <[EMAIL PROTECTED]> writes:

> Hi all,
>
> I'm using FSO Milestone 2 and is the most beautiful and quick image of 
> the three (ASU/Gtk/FSO) I have probed. The dialer is the only 
> application with problems in responsiveness (almost 5 seconds to launch 
> compared to the almost instantaneous of the other ones) and the first 
> digit of the phone number only is seen when you type the second one, but 
> I think that this will be corrected in another milestone. So, keep the 
> good work :-)
>
> I want to use my Freerunner for my classes and for that I need, for the 
> moment, a pdf reader and an spread sheet. Do you have any advice or 
> suggestion of something already packaged? I have being thinking in SIAG 
> (Scheme In A Grid) for the spread sheet and now I'm trying to get it 
> working on my desktop to see if makes sense to put it also in FR.
>
> Cheers,
>
> Offray
>
> ___
> 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

Howto provide decent backgroud infos about problems?

[Thorben Krueger]

Could someone perhaps whip up a shellscript to be run on any OM
installation to determine the answers to most (technical) FAQs?

This would help people a lot with communicating issues.

(For instance, I have totally forgotten which uImage is currently
residing in my FR, or even which uboot version.)

In the long term, it would be nice to have such an "info-tool"
preinstalled in every image.

Just my suggestions.

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

Re: using openocd

[Lynn Nguyen]

So um, how do you reset the eeprom? I'm sorry, I don't have much experience
in this error.

Also, I was thinking that ft2232 was not enabled for my openocd build and
when I tried to build openocd from the source code with ft2232 enabled, I
kept getting random errors. So, I just used apt-get install openocd instead.
I figured most people just used apt-get install and so that should be
alright right?

Lynn

On Tue, Sep 2, 2008 at 11:47 AM, Kees Jongenburger <
[EMAIL PROTECTED]> wrote:

> On Mon, Sep 1, 2008 at 6:33 AM, Lynn Nguyen <[EMAIL PROTECTED]> wrote:
> > Hey All,
> >
> > I was wondering if anyone was using the Neo1973 (GTA01v4) with Debug
> board
> > v3. I used the openocd.cfg available on the wiki and I get this problem:
> > Info:openocd.c:82 main(): Open On-Chip Debugger (2006-08-01 12:00
> CEST)
> > Info:configuration.c:50 configuration_output_handler(): Command
> > ft2232_device_desc not found
> > Info:configuration.c:50 configuration_output_handler(): Command
> > ft2232_layout not found
> > Info:configuration.c:50 configuration_output_handler(): Command
> > ft2232_vid_pid not found
> > Error:   jtag.c:1219 jtag_init(): No valid jtag interface found (ft2232)
> >
> > It seems like openocd is having some trouble with ft2232 because I don't
> see
> > anything wrong with those commands.
>
> yes , perhaps libft2232 is not enabled in you openocd build?
>
>
> greetings
>
> ___
> 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: Howto provide decent backgroud infos about problems?

[Matt]

I'd suggest going further and having a tool which gathers logs, file 
versions, config files, some hardware diagnostics, etc
Tar all the results and attach them to support tickets.

~ Matt


Thorben Krueger wrote:
> Could someone perhaps whip up a shellscript to be run on any OM
> installation to determine the answers to most (technical) FAQs?
> 
> This would help people a lot with communicating issues.
> 
> (For instance, I have totally forgotten which uImage is currently
> residing in my FR, or even which uboot version.)
> 
> In the long term, it would be nice to have such an "info-tool"
> preinstalled in every image.
> 
> Just my suggestions.
> 
> ___
> 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: Howto provide decent backgroud infos about problems?

[Thorben Krueger]

problem with a tar is: not easy to see the relevant informations at a
first glance. who goes around untarring files attached to dubious bug
reports?

2008/9/2 Matt <[EMAIL PROTECTED]>:
> I'd suggest going further and having a tool which gathers logs, file
> versions, config files, some hardware diagnostics, etc
> Tar all the results and attach them to support tickets.
>
> ~ Matt
>
>
> Thorben Krueger wrote:
>> Could someone perhaps whip up a shellscript to be run on any OM
>> installation to determine the answers to most (technical) FAQs?
>>
>> This would help people a lot with communicating issues.
>>
>> (For instance, I have totally forgotten which uImage is currently
>> residing in my FR, or even which uboot version.)
>>
>> In the long term, it would be nice to have such an "info-tool"
>> preinstalled in every image.
>>
>> Just my suggestions.
>>
>> ___
>> 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
>

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

Debian root password

[Joachim Ott]

2008/9/2 Chris Jenks <[EMAIL PROTECTED]>

>   I haven't researched the keyboard problem - I assume I need a powered
> hub, but I'll read. No need to address that here.


By the default, the Neo is in device mode. You have to put it into host mode
and give power to the usb port. See here for the commands:
http://wiki.openmoko.org/wiki/Neo_FreeRunner_FAQ#USB
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support

Can bad NAND blocks cause USB's "device descriptor read/64, error -110" ?

[sledge]

Hello dear all,

My new FR (DateCode 20080725) is suspected to having bad NAND blocks:
It had been suffering kernel panics etc. after as soon as I reflashed it
with Om2008.8 on 20080831. Subsequent reflashings rendered my FR less
unstable.

I'm still suffering with USB cdc_ether, I'm getting `device descriptor
read/64, error -110' and no solution found out there on the net helps.

Last time tried with:
u-boot,rootfs (20080902) -- from Openmoko_update page
kernel (20080902, too) -- from daily page.
(!)With the 20080826 kernel from releases/_update page says wrong image
format whatsoever.. (and still does if I try to revert to the 20080826 one)

Tried everything I could google, no cure:
* I have usbnet, cdc_ether compiled as modules. uhci_hcd, too, -- modprobe
-r uhci_hcd (re-insert) does not help;
* http://wiki.openmoko.org/wiki/Uboot#Troubleshooting 
 - /dev/ttyACM0 gets created OK, from NAND and from NOR
* I use the USB cable supplied in my packaging, even tried the other one.
* Could not try out
http://n2.nabble.com/Om-2008.8%3A-usb%3A-unable-to-enumerate-USB-device-tp680918p719848.html,
because I don't know where to get the u-boot'er any more fresh than I have
(1.3.2, Aug 26)

Thanks for helping pushing this through towards an initially-usable FR; and
keep up the great good work, lads!

-- 
sledge
-- 
View this message in context: 
http://n2.nabble.com/Can-bad-NAND-blocks-cause-USB%27s-%22device-descriptor-read-64%2C-error--110%22---tp835094p835094.html
Sent from the Openmoko Support mailing list archive at Nabble.com.


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

Re: Segfault on opkg upgrade

[Colan Lash]

On Mon, Sep 1, 2008 at 6:03 PM, Rob Tymensen <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 1, 2008 at 8:39 AM, Richard Cooke
> <[EMAIL PROTECTED]> wrote:
>>
>> I have flashed FSO milestone 2 and changed the .conf files in /etc/opkg to
>> point to the fso-testing feed at shr.bearstech.com. opkg update seems to
>> complete successfully but opkg uggrade produces a segfault.
>>
>>snip
>
>> [EMAIL PROTECTED]:~# opkg upgrade
>> Upgrading angstrom-version on root from 1:-20080729-r1 to 1:-20080901-r1...
>> Downloading
>> http://shr.bearstech.com/fso-testing/ipk/om-gta02/angstrom-version_-20080901-r1_om-gta02.ipk
>> Segmentation fault
>> [EMAIL PROTECTED]:~#
>>
>> --
>
>
> Had the same problem.  I downloaded the images from bearstech instead
> of milestone 2 and flashed that.  Then when I ran the update/upgrade
> it worked like a charm.
>
> -Rob
>
> ___
> 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: 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: GPS Problem (maybe antenna?)

[Marco Trevisan (Treviño)]

Sebastian M. wrote:
> Quoting "Marco Trevisan (Treviño)" <[EMAIL PROTECTED]>:
>> Which distributor will give you them as warranty fixes?
> In Germany (and the whole European Union, I guess) the retailers are  
> forced to give a 2 years warranty and because of that they have to  
> replace goods which have problems like an advertised feature not  
> working (like the Freerunners GPS [-hardware] in my case).
> 
> As far as I know the same thing applies to distributors (in Germany  
> and maybe EU as well).

I'm in EU too: Italy, but I've bought the Freerunner in Germany 
(HandHeld-Linux) I was just wondering if they could replace/fix the 
phone if I'll send them for a gps/gsm fix...
Cause this is a common problem for all the first-stock freerunners.

-- 
Treviño's World - Life and Linux
http://www.3v1n0.net/


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

Re: Can bad NAND blocks cause USB's "device descriptor read/64, error -110" ?

[Andy Green]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Somebody in the thread at some point said:
| Hello dear all,
|
| My new FR (DateCode 20080725) is suspected to having bad NAND blocks:
| It had been suffering kernel panics etc. after as soon as I reflashed it
| with Om2008.8 on 20080831. Subsequent reflashings rendered my FR less
| unstable.

Copy of the panic backtrace would be interesting if you can get ahold of
it.  Usually every panic is a story although there's no guarantee we can
figure it out.

The kernel image itself is CRC-checked by U-Boot before it is run.  So
it is doubtful we can say that kernel is corrupted by "bad NAND".

| I'm still suffering with USB cdc_ether, I'm getting `device descriptor
| read/64, error -110' and no solution found out there on the net helps.

This can be to do with the host PC USB device, cables, stack as well as
Freerunner.  Are there any other exotic variations of that in your host
PC dmesg or is it only that?

| Last time tried with:
| u-boot,rootfs (20080902) -- from Openmoko_update page
| kernel (20080902, too) -- from daily page.
| (!)With the 20080826 kernel from releases/_update page says wrong image
| format whatsoever.. (and still does if I try to revert to the 20080826
one)

That's a funny error to get, can it actually DFU anything reliably?
That is also using the dodgy USB connection of course...

- -Andy

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAki98T4ACgkQOjLpvpq7dMpJHQCfW5H0o85lQdh8H1siLHev4Ml1
Jd0An0sDcAqCg3O6Xxam5xmp27ADEztI
=Wnwd
-END PGP SIGNATURE-

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

Re: Pdf Viewer and Spread Sheet for FSO Milestone 2

[Offray Vladimir Luna Cárdenas]

Hi,

Rod Whitby escribió:
> 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
>
>   

Thanks Rod, I will try it in the FR. I have installed on the Desktop and 
is working like a charm.

Cheers,

Offray

> ___
> 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: Pdf Viewer and Spread Sheet for FSO Milestone 2

[Offray Vladimir Luna Cárdenas]

Hi Christopher,

Christopher Allan Webber escribió:
> If you install Debian, it comes with FSO (and pretty much looks the same
> out of the box), but you have access to all of debian's packages.  From
> there you could install either xpdf of evince
>
> sudo apt-get install evince
> sudo apt-get install xpdf
>
> I'm not sure how well openoffice, that beast, would be able to run on
> the openmoko.  Gnumeric is a bit more lightweight than open office,
> iirc.  You could try that.
>
> Hope that helps!
>  - Chris
>
>   

Thanks. I will try epdfview from the bearstech repository and Siag which 
seems even lighter than Gnumeric and I will share the results. Debian 
will wait for a while because I'm trying to keep things as minimal as 
possible.

Cheers,

Offray

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

Re: gta02, debian, fso: pairing (and using) bleutooth headset?

[Brad Midgley]

Jim

The best fit for this older version is talking to the service via
d-bus. At one point I had python and d-bus working well enough to fire
off the audio service as in the example at
http://wiki.bluez.org/wiki/HOWTO/AudioDevices#python1

Combined with the right state file, you should get a bluetooth headset
working if the hardware is right. If it doesn't work, I would keep the
call and bluetooth play going and fiddle with mixer settings via
something like alsamixer to see if you can get any noise at all.
Perhaps run something that plays an mp3 at the same time and you'll
know if you find instead a way to get system audio out onto bluetooth.

Brad

On Mon, Sep 1, 2008 at 10:57 PM, Jim Morris <[EMAIL PROTECTED]> wrote:
> Brad Midgley wrote:
>> Jim
>>
>>> Presuming this flips the right codec switches, how do you coordinate the 
>>> audio service?
>>
>> what version of bluez-utils do you get?
>>
>
> Whichever one 2008.8 has as my opkg points to that feed.
>
> bluez-utils - 3.23-r4 -
> bluez-utils-alsa - 3.23-r2 -
> bluez-utils-compat - 3.23-r4 -
>
>
> --
> Jim Morris, http://blog.wolfman.com
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>



-- 
Brad

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

Re: gta02, debian, fso: pairing (and using) bleutooth headset?

[Jim Morris]

Brad Midgley wrote:
> Jim
> 
> The best fit for this older version is talking to the service via
> d-bus. At one point I had python and d-bus working well enough to fire
> off the audio service as in the example at
> http://wiki.bluez.org/wiki/HOWTO/AudioDevices#python1
> 
> Combined with the right state file, you should get a bluetooth headset
> working if the hardware is right. If it doesn't work, I would keep the
> call and bluetooth play going and fiddle with mixer settings via
> something like alsamixer to see if you can get any noise at all.
> Perhaps run something that plays an mp3 at the same time and you'll
> know if you find instead a way to get system audio out onto bluetooth.
> 

I already tried all that, including the python script. I've tried everything on 
the bluez wiki and
the OM wiki.

I think I have the .state file correct, no way of really knowing. I can't get 
anything to play
through the headset be it a test wave file via aplay or gsm in a call.

Short of reverse engineering both bluez and the audio driver and the kernel and 
the gsm drivers, I
really don't see any other way of getting it to work, and I really don;t have 
an infinite amount of
time to play with this stuff.

Obviously OM never tested any of this, so its possible it is broken in the H/W, 
and could never
work, who knows?

Thanks for your help though.

Is there a better version of bluez utils? I could easily build a new version, 
but I suspect I also
need to build a new kernel if I go that route. There is no mention in bluez of 
chips routing the pcm
audio directly to the audio card, so it is possible bluez doesn't support that 
option anyway?

-- 
Jim Morris, http://blog.wolfman.com


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

Re: gta02, debian, fso: pairing (and using) bleutooth headset?

[Brad Midgley]

Jim

> I already tried all that, including the python script. I've tried everything 
> on the bluez wiki and
> the OM wiki.

ok

> Is there a better version of bluez utils? I could easily build a new version, 
> but I suspect I also
> need to build a new kernel if I go that route. There is no mention in bluez 
> of chips routing the pcm
> audio directly to the audio card, so it is possible bluez doesn't support 
> that option anyway?

you could make sure /etc/bluetooth/audio.conf has

SCORouting=PCM

but I believe that was the default in 3.23.

the newer versions of bluez will do things differently or with better
integration with the other services, but it isn't likely to change
what works and doesn't work.

next we could try going down the road of routing audio through hci.
the bluetooth adapter should support this and as long as gsm gets
routed to the cpu it should be possible. this part really won't work
on neo so I wouldn't be able to help test it since that's all I have.

testing the pieces might be easier: if there is a way to record your
gsm conversation then we'd know it is possible to at least route it
into the cpu. then we'd need to see if you can run an audio app on the
handset and have it use bluetooth.

-- 
Brad

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

Re: Can bad NAND blocks cause USB's "device descriptor read/64, error -110" ?

[sledgeas]

Thanks for answering, Andy,

Andy Green rašė:
> Copy of the panic backtrace would be interesting if you can get ahold of
> it.  Usually every panic is a story although there's no guarantee we can
> figure it out.
>
Kernel panic just came out once (when I first launched the `Locations') 
, then I reflashed the kernel (as was suggested in #openmoko because of 
maybe bad blocks) and no other panics I've experienced so far.
I have no debug board. Are there any other ways [logs] of obtaining that 
late kernel panic?
> | I'm still suffering with USB cdc_ether, I'm getting `device descriptor
> | read/64, error -110' and no solution found out there on the net helps.
>
> This can be to do with the host PC USB device, cables, stack as well as
> Freerunner.  Are there any other exotic variations of that in your host
> PC dmesg or is it only that?
>
Well, are you sure? Because I get cdc_usb without problems (/dev/ttyACM0 
created OK).
Is cdc_ether protocol so much different [complex] that it is being 
affected by cable or other hardware (or FR's hardware-based fault?), 
whilst I get a normal cdc_ether behaviour.
Maybe it's the u-boot bug, killing off usb completely? -> 
http://n2.nabble.com/Om-2008.8%3A-usb%3A-unable-to-enumerate-USB-device-tp680918p719848.html
But I find no other [older/testing?] u-boot to try out with. Could you 
guys recommend any flavours?

Yesterday I have reflashed kernel from 20080901 to 20080902 and, after 
pressing around power (with buggy Om2008's suspend) got this:
usb 6-1: device descriptor read/64, error -84
But that exotic variation was only once. After reboot it swayed back to 
-110.
> | (!)With the 20080826 kernel from releases/_update page says wrong image
> | format whatsoever.. (and still does if I try to revert to the 20080826
> one)
>
> That's a funny error to get, can it actually DFU anything reliably?
> That is also using the dodgy USB connection of course...
>
The exact error is (with NAND and NOR u-booter):
2097152 bytes read:OK
Wrong image format for bootm command
ERROR: can't get kernel image!

And it happens always (even yesterday) with 
http://downloads.openmoko.org/releases/Om2008.8-update/Om2008.8-gta02-20080826.uImage.bin
So we cannot blame it on dfu (unless it is kernel-version sensitive :)) 
and dodgy connection, as any newer (testing) kernels and roofss get 
always flashed ok.
Should I try older kernel?

Let's make my FR happen,

-- 
sledge

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