OM 2008.8 (With Zecke's feed) No dim, only screensaver
Hi everyone, instead of dimming my phone starts the X screensaver, which isn't very economical for my battery. Does anyone know how I can get the dimming back to work? I can't let it suspend because I need to charge my battery, obviously Kind regards, Jelle De Loecker ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: connecting a usb 3g modem
On Sun, Aug 31, 2008 at 6:41 PM, Andy Green [EMAIL PROTECTED] wrote: Sometimes when I use it on normal laptop, I get bogus DNS in UK. You mean like if you use host somedomain.com on your Linux system, when using the modem as the DNS server, you get complaints like malformed response etc.? I have had this complaint with ADSL modems - both Huawei and DLink. The solution is to set your Linux host's resolv.conf to directly query your ISP's DNS servers, or OpenDNS servers, or to run a caching DNS on your Linux host, possibly with ISP nameservers or OpenDNS servers set as forwarders. Surprisingly, that proprietary OS that most FOSS people hate to use... works just fine with the DNS implementation on the ADSL modems... a case of two brokens make one fixed? :-P Cheers Ed. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FSO compile error
On Sun, Aug 31, 2008 at 11:41 PM, Javi Roman [EMAIL PROTECTED] wrote: On Sun, Aug 31, 2008 at 5:14 PM, Michael 'Mickey' Lauer [EMAIL PROTECTED] wrote: 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? Yeah. See openembedded.org - GettingStarted. (In a nutshell: bitbake fso-image) I have not expressed myself very well, I was refering to the error: $ bitbake zhone -c rebuild ERROR: function do_compile failed 64 ERROR: log data follows (/home/jroman/HACK/FR/build/tmp/work/armv4t-angstrom-linux-gnueabi/zhone-0.0.0+gitr900105c27bd176fdca4e8f896b2c8221181491de-r7/temp/log.do_compile.7097) 65 | /home/jroman/HACK/FR/build/tmp/staging/i686-linux/usr/bin/python: can't open file 'setup.py': [Errno 2] No such file or directory 66 | FATAL: python setup.py build_ext execution failed. I wonder if this error is related with a wrong settings in git repository or git branch. Thanks -- Javi Roman Zhone compile problem was solved setting up properly: require conf/distro/include/fso-autorev.inc require conf/distro/include/moko-autorev.inc Thanks. -- Javi Roman ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia - kernel panic
On Mon, Sep 1, 2008 at 9:31 AM, Ali [EMAIL PROTECTED] wrote:
Hi,
This is the output of printenv on u-boot prompt.
=
menu_1=Boot from microSD (FAT+ext2): setenv bootargs ${bootargs_base}
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 ${mtdparts} init=/sbin/init
ro; mmcinit; fatload mmc 1 0x3200 ${sd_image_name}; bootm 0x3200
[...]
menu_9=Boot 200808 from microSD (FAT+ext3): setenv bootargs ${bootargs_base}
rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5 ${mtdparts} ro; mmcinit;
fatload mmc 1 0x3200 ${sd_image_name}; bootm 0x3200
Although a n00b at this myself, the only difference I can see between
menu_1 and menu_9 above is that menu_1 contains an init=/sbin/init
clause while menu_9 does not... however, when I tried Qtopia on SD
(FAT + ext2) I didn't muck around with any of this, and menu_1 worked
fine for me... is it possible that adding the init=/sbin/init clause
would help?
Ed.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Om2007 sound issue
its appear that Om2007 does not play sound when i receive call or sms ( by the way it play starting source when enters OS ) any idea ? when i restart pulseaudio , it returns : Sep 1 12:14:46 om-gta02 user.warn pulseaudio[1816]: alsa-util.c: Device default doesn't support 44100 Hz, changed to 48000 Hz. Sep 1 12:15:01 om-gta02 user.err pulseaudio[1827]: module.c: Failed to open module module-x11-bell: module-x11-bell.so: cannot open shared object file: No such file or directory Sep 1 12:15:01 om-gta02 user.err pulseaudio[1827]: main.c: Module load failed. by the way , how can i choose to silent or 'vibrate only' om2007 ? -- Armin ranjbar , System Administrator ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OM 2008.8 (With Zecke's feed) No dim, only screensaver
You only need the processor up to run the communications that initiate the correct charging levels - after that its automatic and you can suspend. BillK On Mon, 2008-09-01 at 09:10 +0200, Jelle De Loecker wrote: Hi everyone, instead of dimming my phone starts the X screensaver, which isn't very economical for my battery. Does anyone know how I can get the dimming back to work? I can't let it suspend because I need to charge my battery, obviously Kind regards, Jelle De Loecker ___ 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: New battery semi-charged but not charging, is protection-circuit broken?
On Mon, Sep 1, 2008 at 6:28 AM, Michael Shiloh [EMAIL PROTECTED] wrote: Did you update u-boot and kernel? There was a bug awhile back causing USB insertions to be only partially recognized. I have not updated UBoot and i cannot do it anymore since the battery has fallen significantly making it impossible to enter into USB ACM. I've used kernel from 2008.8 and FSO (2 days ago), nothing too recently. I thinki i've seen the bug you mention, when it requires to insert the USB twice in order to enter 'Charging status. But yet, no real current flows into the battery and the battery's reported capacity remains 0. Yesterday, the current_now started to show some non-zero values, but judging from the voltage_now, the battery did not actually charge. Michael, I would really like to know if there is any possibility of reviving the battery or if i should definitely contact the reseller for a new one, since i live in a different country from the reseller it and it will take some time to receive a new battery. Thank you for your interest, Kostis ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: connecting a usb 3g modem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Sun, Aug 31, 2008 at 6:41 PM, Andy Green [EMAIL PROTECTED] wrote: | Sometimes when I use it on normal laptop, I get bogus DNS in UK. | | You mean like if you use |host somedomain.com | on your Linux system, when using the modem as the DNS server, you get | complaints like malformed response etc.? No the dhcp client puts the DNS nameserver lines in, but they don't always work. There's another issue on my box somehow that later, NetworkManager overwrites it with old DNS nameserver line somehow, but now I realized why my connectivity breaks I stop NetworkManager for the duration and that solves it. | Surprisingly, that proprietary OS that most FOSS people hate to use... | works just fine with the DNS implementation on the ADSL modems... a | case of two brokens make one fixed? :-P Dread to think of it. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAki7tLQACgkQOjLpvpq7dMr+UwCfeGhoqAP0Q5bAG8nnJs9WnVNs fjgAnRNPXcFYBViVb2pm3KbqnOuaNqcz =pj+t -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: New battery semi-charged but not charging, is protection-circuit broken?
ankostis wrote: On Mon, Sep 1, 2008 at 6:28 AM, Michael Shiloh [EMAIL PROTECTED] wrote: Did you update u-boot and kernel? There was a bug awhile back causing USB insertions to be only partially recognized. I have not updated UBoot and i cannot do it anymore since the battery has fallen significantly making it impossible to enter into USB ACM. I've used kernel from 2008.8 and FSO (2 days ago), nothing too recently. I thinki i've seen the bug you mention, when it requires to insert the USB twice in order to enter 'Charging status. But yet, no real current flows into the battery and the battery's reported capacity remains 0. Yesterday, the current_now started to show some non-zero values, but judging from the voltage_now, the battery did not actually charge. Michael, I would really like to know if there is any possibility of reviving the battery or if i should definitely contact the reseller for a new one, since i live in a different country from the reseller it and it will take some time to receive a new battery. If you're feeling adventurous, try to revive the battery using Joerg's unofficial instructions [1], then update u-boot and kernel, then see if charging works better. If you're not feeling adventurous, ask your reseller for a new battery, and if it works, then return the old one as faulty. Michael [1] http://wiki.openmoko.org/wiki/Charging_battery_directly ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: New battery semi-charged but not charging, is protection-circuit broken?
ankostis wrote: On Mon, Sep 1, 2008 at 7:14 PM, Michael Shiloh [EMAIL PROTECTED] wrote: ankostis wrote: On Mon, Sep 1, 2008 at 6:28 AM, Michael Shiloh [EMAIL PROTECTED] wrote: Did you update u-boot and kernel? There was a bug awhile back causing USB insertions to be only partially recognized. I have not updated UBoot and i cannot do it anymore since the battery has fallen significantly making it impossible to enter into USB ACM. I've used kernel from 2008.8 and FSO (2 days ago), nothing too recently. I thinki i've seen the bug you mention, when it requires to insert the USB twice in order to enter 'Charging status. But yet, no real current flows into the battery and the battery's reported capacity remains 0. Yesterday, the current_now started to show some non-zero values, but judging from the voltage_now, the battery did not actually charge. Michael, I would really like to know if there is any possibility of reviving the battery or if i should definitely contact the reseller for a new one, since i live in a different country from the reseller it and it will take some time to receive a new battery. If you're feeling adventurous, try to revive the battery using Joerg's unofficial instructions [1], then update u-boot and kernel, then see if charging works better. If you're not feeling adventurous, ask your reseller for a new battery, and if it works, then return the old one as faulty. Michael [1] http://wiki.openmoko.org/wiki/Charging_battery_directly I've tried this already since the current voltage has fallen below the booting threshold, by supplying extra current from a separate supplier directly to the battery receptors. Yet i think Michael, that we are not dealing with a dead battery that needs reviving, but with a broken protection circuit that does not accept the charging current. If i could suggest a solution that would be first to deeply-discharge the battery in order to reset the protection-cpu, and then start charging it. Is this a viable solution? Interesting theory. I don't know how the protection circuit works, and whether deeply-discharging will reset it. You might post this question on the kernel list - the people who would know this should all be there. Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
Why would I want to do that to the debug board? http://wiki.openmoko.org/wiki/Debug_Board_v3 . If the usb id is 0403:6010 then its wrong isn't it? Also I don't understand this section of the wiki page: http://wiki.openmoko.org/wiki/OpenOCD#Known_Bugs_and_Troubleshooting Did you turn it on ? An easily made but devastating mistake is to forget to actually activate the CPU. Just connecting power is not enough ! Press and hold the power button until the boot loader does its count-down, or, in case there is no runnable boot loader, the CPU keeps itself busy. is the 'it' this part referring to the openmoko? I mean, isn't the whole point of a bricked openmoko the fact that it can't turn on? How am I supposed to activate the CPU if it won't turn on at all? I know the battery is fully charged because I checked the voltage. this is the openocd.cfg i am using: telnet port gdb_port # interface interface ft2232 jtag_speed 8 ft2232_device_desc Debug Board for Neo1973 ft2232_layout jtagkey ft2232_vid_pid 0x1457 0x5118 reset_config trst_and_srst jtag_device 4 0x1 0xf 0xe daemon_startup attach target arm920t little reset_run 0 arm920t working_area 0 0x20 0x4000 backup run_and_halt_time 0 5000 How do I check my debug board's uart console? I can't remember how to do it but I'm pretty sure I was able to screen onto it once. Actually maybe it is something with my debug board, I looked in the logs and saw this: [ 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 Do you know what to make of this error? Google search finds nothing =/. Lynn On Mon, Sep 1, 2008 at 12:43 AM, Neng-Yu Tu (Tony Tu) [EMAIL PROTECTED]wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Lynn- Lynn Nguyen ??: Yeah it's loading the correct openocd.cfg file. I even added random commands to it and i saw those commands in the error messages. I even used -f to be sure. * Could you check the .cfg file is comes with, it should called openocd-debugv2.cfg : 1. ft2232_vid_pid 0x1457 0x5118 2. And adjust jtag_speed to higher number (4 or 8, default is 0) * And is your debug board UART (terminal console) is working? If still not working, you might could erase the EEPROM content in the debug board again, return the default USB ID 0403 6010. They see if the UART and openocd could work. Regards, - -- Neng-Yu Tu (Tony Tu) Openmoko, Inc. Support. Some questions could be answered by reference following link: Wiki - http://wiki.openmoko.org Download - http://downloads.openmoko.org Freerunner Introduction - http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner 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. Does your openocd load neo1973 specific config? like tmp/openocd -f tmp/openocd-debugv2.cfg Usually it is because your USB vid/pid setting is not correct in the config file(load the wrong config file) Hope this helps. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAki7nRcACgkQmV6sZhhBn2/jIACgjEh/KVZXXdhD4sLyZh17d9gA DG4AnAmOZwoBDKSqNn3mua2WQnvi9xCp =wz/W -END PGP SIGNATURE- ___ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
diversity apps
I installed Diversity Nav and Diversity Wifi. Both work. Except IIRC DN needed 'Locations' to be run before I could get a map. Some AP's were listed on the map including my own. Unfortunately, while my GPS loc was accurate the my AP was shown to be a block away when I was only 10m from it. OTOH, DWifi picks up all three types of AP's in my neighborhood. Is it also supposed to display locations mapwise or is it more of a distance/directional locator? I googled Diversity but didn't find much in way of help. Thanks, radtek ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Undefined USB Device
When attempting to flash my FreeRunner from a Thinkpad Laptop with Ubuntu 7.10 installed, I get two USB devices after plugging in the FreeRunner and running dfu-util -l. I did have a USB mouse attached but I removed it and rebooted but I still get the same message. Even after rebooting with no USB devices connected and running dfu-util -l, I receive the response that one Undefined device is connected. Is there a way to specify which USB device is to be upgraded with dfu-util or is there a way to clear out all references to USB devices? Thanks, Mike -- Michael Fisher [EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Wifi 2008.8
2008/9/1 e hanks [EMAIL PROTECTED] No... No horror stories... I connect to my wpa encrypted network NP after setting up a wpa_supplicant.conf; however, I'm just using the gui under settings in the phone. How do I make the password persistent? I have to input it in everytime I reboot my phone. The utterly ridiculous keyboard makes this a tedious task. Use this (replace ESSID and PASSWEIRD with your values): wpa_passphrase ESSID PASSWEIRD /etc/wpa_supplicant/wpa_supplicant.conf (check what was written to wpa_supplicant.conf) After restarting wpa_supplicant you should get a connection. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Wifi 2008.8
e hanks wrote:
No... No horror stories...
I connect to my wpa encrypted network NP after setting up a
wpa_supplicant.conf; however, I'm just using the gui under settings in
the phone. How do I make the password persistent? I have to input it
in everytime I reboot my phone. The utterly ridiculous keyboard makes
this a tedious task.
BTW, despite mastering the usage of this keyboard I really think this
is a wrong approach guys. Sorry, if this is your baby, but I'll be
removing it if I can ASAP. Chalk me up for 'against'.
Anyway, I intentionally left the wpa_supplicant.conf paremeters (SSID
etc) blank figuring the gui would populate it. Is this the wrong
approach even though it works?
Thanks
radtek
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Hi, I can connect to my wpa with my supplicant file thus:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA:
network={
ssid=OMFGmySSID
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
scan_ssid=1
psk=omfgmysecretWPAkeyhere
priority=10
}
# Wildcard match for SSID (plaintext APs only). This example select any
# open AP regardless of its SSID.
network={
key_mgmt=NONE
priority=5
}
although i have to run a script (i call mine wifi.sh)consisting of
ifdown usb0
ifdown eth0
ifup eth0
udhcpc eth0
in order to get it to dhcp from the router. ie i power up the phone,
open a terminal window and run the above wifi.sh script and wait
(sometimes for a few minutes) until it discovers the ip settings from
the router.
This little shell script gets me onto my wpa router or any open router
that is available.
Please don't ask me for details as I am a non-programming nitwit
cobbling stuff out of other people's help files.
Good luck.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: Undefined USB Device
Hi, On Mon, Sep 1, 2008 at 11:39 PM, Michael Fisher [EMAIL PROTECTED] wrote: Is there a way to specify which USB device is to be upgraded with dfu-util Yes. Check out the dfu-util[1] page on the wiki References: 1) http://wiki.openmoko.org/wiki/Dfu-util -- Regards, Torfinn Ingolfsen ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: diversity apps
On Mon, Sep 1, 2008 at 11:18 PM, e hanks [EMAIL PROTECTED] wrote: I installed Diversity Nav and Diversity Wifi. Both work. Except IIRC DN needed 'Locations' to be run before I could get a map. Some AP's were listed on the map including my own. Unfortunately, while my GPS loc was accurate the my AP was shown to be a block away when I was only 10m from it. my 2008.8-upgrade is fully upgraded and diversity wifi never sees any wireless AP's. When going to settings -- wifi the AP's are visible. Mofi also sees the AP's Diversity nav displays the AP's, but it displays them all on top of eachother; pressing join or information gives nothing and pressing zoom zooms out... The AP's are also not shown on the right place http://diversity.projects.openmoko.org/ is not very informative.. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Undefined USB Device
2008/9/1 Michael Fisher [EMAIL PROTECTED] When attempting to flash my FreeRunner from a Thinkpad Laptop with Ubuntu 7.10 installed, I get two USB devices after plugging in the FreeRunner and running dfu-util -l. I did have a USB mouse attached but I removed it and rebooted but I still get the same message. Even after rebooting with no USB devices connected and running dfu-util -l, I receive the response that one Undefined device is connected. Is there a way to specify which USB device is to be upgraded with dfu-util or is there a way to clear out all references to USB devices? Do this in the following order: 1) put the Neo into NOR boot menu, i.e. press and hold AUX, then press Power button 2) after that connect the USB cable 3) on the Thinkpad as root: run dfu-util -l , and when the Neo is found, flash it ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Undefined USB Device
On my T61 laptop, it appears that the bluetooth adapter is identified by dfu-util as a target. I worked around it by turning off the bluetooth adapter. Matt Joachim Ott wrote: 2008/9/1 Michael Fisher [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] When attempting to flash my FreeRunner from a Thinkpad Laptop with Ubuntu 7.10 installed, I get two USB devices after plugging in the FreeRunner and running dfu-util -l. I did have a USB mouse attached but I removed it and rebooted but I still get the same message. Even after rebooting with no USB devices connected and running dfu-util -l, I receive the response that one Undefined device is connected. Is there a way to specify which USB device is to be upgraded with dfu-util or is there a way to clear out all references to USB devices? Do this in the following order: 1) put the Neo into NOR boot menu, i.e. press and hold AUX, then press Power button 2) after that connect the USB cable 3) on the Thinkpad as root: run dfu-util -l , and when the Neo is found, flash it ___ 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: Undefined USB Device
On Mon, Sep 1, 2008 at 6:19 PM, Torfinn Ingolfsen [EMAIL PROTECTED] wrote: Hi, On Mon, Sep 1, 2008 at 11:39 PM, Michael Fisher [EMAIL PROTECTED] wrote: Is there a way to specify which USB device is to be upgraded with dfu-util Yes. Check out the dfu-util[1] page on the wiki References: 1) http://wiki.openmoko.org/wiki/Dfu-util -- Regards, Torfinn Ingolfsen ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support Torfinn, Thanks for the infofinding that I can specify the USB device did it...flashing as I write. dfu-util --device 0x1457:0x5119 Mike -- Michael Fisher [EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS Problem (maybe antenna?)
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? -- 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
Lynn Nguyen wrote: An easily made but devastating mistake is to forget to actually activate the CPU. Just connecting power is not enough ! Press and hold the power button until the boot loader does its count-down, or, in case there is no runnable boot loader, the CPU keeps itself busy. is the 'it' this part referring to the openmoko? I mean, isn't the whole point of a bricked openmoko the fact that it can't turn on? How am I supposed to activate the CPU if it won't turn on at all? I know the battery is fully charged because I checked the voltage. it does refer to the phone. Turn it on means setting the power-management unit (PMU) into Active mode so that voltage is applied to the CPU. This might happen automatically when you plug in the USB cable, but if not you can do it by pressing the power button. If the device is bricked you will not see anything happen when you turn it on, but internally the CPU will be ready to accept a JTAG connection. Try following the sequence described at http://wiki.openmoko.org/wiki/Debug_Board_v2#Hardware_connection (which AFAIK should be the same for a v3 debug board). this is the openocd.cfg i am using: Looks OK to me. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Segfault on opkg upgrade
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
Xscreensaver phylosophy
Hi, I can't lock the screen on a Neo1973 with Debian. This is what the FAQ of xscreensaver says: /*** When I'm logged in as root, xscreensaver won't lock my screen! Don't log in as root. Please note that xscreensaver works fine as a screen saver when you are logged in as root: it will not, however, lock your screen when you are logged in as root. This is for good and insurmountable security reasons. In order for it to be safe for xscreensaver to be launched by xdm, certain precautions had to be taken, among them that xscreensaver never runs as root. In particular, if it is launched as root (as xdm is likely to do), xscreensaver will disavow its privileges, and switch itself to a safe user id (such as nobody.) An implication of this is that if you log in as root on the console, xscreensaver will refuse to lock the screen (because it can't tell the difference between root being logged in on the console, and a normal user being logged in on the console but xscreensaver having been launched by the xdm Xsetup file.) The solution to this is simple: you shouldn't be logging in on the console as root in the first place! (What, are you crazy or something?) Proper Unix hygiene dictates that you should log in as yourself, and su to root as necessary. People who spend their day logged in as root are just begging for disaster. ***/ I don't use XDM nor any display manager, don't want a display manager eating resources and don't want to write to log in (and don't know how to write). Anybody has a solution to this, excluding the Don't log in as root ? Best regards -- Juan Cañete Azorín hiroshima 45, Tchernobyl 86, Windows 95 ... Powered by Linux signature.asc Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: gta02, debian, fso: pairing (and using) bleutooth headset?
hi next step would be to get that sco_flowcontrol_patch in the kernel, i fear no... the next step is to get the bluetooth/gsm mixer settings and then coordinate the audio service (exact details depend on the bluez version) sco flowcontrol is the previous attempt to fix bluetooth audio on the desktop, so you don't need it. -- Brad ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
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 On Mon, Sep 1, 2008 at 5:03 PM, Mike Montour [EMAIL PROTECTED] wrote: Lynn Nguyen wrote: An easily made but devastating mistake is to forget to actually activate the CPU. Just connecting power is not enough ! Press and hold the power button until the boot loader does its count-down, or, in case there is no runnable boot loader, the CPU keeps itself busy. is the 'it' this part referring to the openmoko? I mean, isn't the whole point of a bricked openmoko the fact that it can't turn on? How am I supposed to activate the CPU if it won't turn on at all? I know the battery is fully charged because I checked the voltage. it does refer to the phone. Turn it on means setting the power-management unit (PMU) into Active mode so that voltage is applied to the CPU. This might happen automatically when you plug in the USB cable, but if not you can do it by pressing the power button. If the device is bricked you will not see anything happen when you turn it on, but internally the CPU will be ready to accept a JTAG connection. Try following the sequence described at http://wiki.openmoko.org/wiki/Debug_Board_v2#Hardware_connection (which AFAIK should be the same for a v3 debug board). this is the openocd.cfg i am using: Looks OK to me. ___ 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: gta02, debian, fso: pairing (and using) bleutooth headset?
Brad Midgley wrote: hi next step would be to get that sco_flowcontrol_patch in the kernel, i fear no... the next step is to get the bluetooth/gsm mixer settings and then coordinate the audio service (exact details depend on the bluez version) sco flowcontrol is the previous attempt to fix bluetooth audio on the desktop, so you don't need it. I put the gta02 .state file up on the Wiki, it is the closest I could get, it is based on the one wolfson had for gta01, but fixed for the control number on gta02. However there were some settings in gta01 that do not appear in gta02, not sure if they are relevant to BT though. Presuming this flips the right codec switches, how do you coordinate the audio service? I tried all the documented approaches both from the bluez site and the wiki, with no luck. (This issue isn't really debian/fso specific, a fix would presumably work for all dists). -- 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?
Jim Presuming this flips the right codec switches, how do you coordinate the audio service? what version of bluez-utils do you get? -- Brad ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Gesture Listener
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
Re: using openocd
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 ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
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... You should, as long as you have the ftdi_sio module loaded with the right vendor/product IDs for the debug board (0x1457/0x1458). Here's what I see when I plug in my debug board v2: usb 1-2: new full speed USB device using uhci_hcd and address 5 usb 1-2: new device found, idVendor=0451, idProduct=2046 usb 1-2: new device strings: Mfr=0, Product=0, SerialNumber=0 usb 1-2: configuration #1 chosen from 1 choice hub 1-2:1.0: USB hub found hub 1-2:1.0: 4 ports detected usb 1-2.1: new full speed USB device using uhci_hcd and address 6 usb 1-2.1: new device found, idVendor=1457, idProduct=5118 usb 1-2.1: new device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-2.1: Product: Debug Board for Neo1973 usb 1-2.1: Manufacturer: OpenMoko usb 1-2.1: configuration #1 chosen from 1 choice ftdi_sio 1-2.1:1.0: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT2232C usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB0 ftdi_sio 1-2.1:1.1: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT2232C usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB1 ___ 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 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
