Re: Can bad NAND blocks cause USB's device descriptor read/64, error -110 ?
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
Re: GPS Problem (maybe antenna?)
On Wed, Sep 03, 2008 at 03:59:02AM +0200, Marco Trevisan (Treviño) wrote: 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. Bought mine from handheld too. :) I already asked them about GPS. If it's not working they'll fix it. With GSM it will be the same I think. As I said, just waitin' for the GSM fix to send them my FR. Ole pgp271Eba7YRe.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Mofi: Error with first_iface when connecting
I get an error when attempting to connect to my wifi network using Mofi 0.3 beta: connecting to foxrun Auto-generating ~/.mofi_wpa_supplicant.conf foxrun encryption: ['0x0', '0x0', '0x0', '0x8'] - WPA? Traceback (most recent call last): File /usr/lib/mofi/uiMofiPanel.py, line 97, in connect_ap mofi_wap_autoconf.generate_wpa_supplicant([ssid]) File /usr/lib/mofi/mofi_wpa_autoconf.py, line 77, in generate_wpa_supplicant print WPA Conf generated. Run wpa_supplicant -i%s -c%s -B to sue the configuration%(first_iface, os.path.join(os.environ['HOME'], '.mofi_wpa_supplicant.conf')) UnboundLocalError: local variable 'first_iface' referenced before assignment I'm using OM 2008.8 on a freerunner. Any ideas how to fix this? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Alsa scenarios , mixer
Le 14117ième jour après Epoch, Dale Maggee écrivait: Armin ranjbar wrote: Dear all , i have two question regarding FR audio subsystem : 1 i need to when any of alsa scenario files are loading , i need to make modification but i really wonder when which will get loaded 2 i need to know exactly what each element of alsamixer doing ? I wrote a shell script which tells you which state is currently loaded, using this you can figure out what each state file is for: May I suggest a small update to your script, to check if multiple files are matching current alsa status? #!/bin/sh CS=/tmp/current.state alsactl -f $CS store Match=0 for F in `ls /usr/share/openmoko/scenarios/*.state`; do #echo Comparing with $F if [ `diff $CS $F` = ]; then echo Current statefile is: $F Match=1 fi done; [ $Match == 0 ] echo Current state matches no file! Anyway, this script is usefull when trying to check what's up with the sound, and that jack insertion do nothing on sound :( ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: using openocd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lynn Nguyen wrote: 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? i used apt-get install openocd , it's alright Lynn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBSL6XBRFuNemPXNFjAQKQ+Af9GXk5EOdxX/lzzkfhuerfXyHEk6VEKqe0 Mo0jmyTT7E+Zmq6KxV/1/84w/so80DFCnaJIhyAQaVMdGGs5TMIKfCleKY334loB bSrZKJqESG+RlrbmkpAYERJAnMW/ntOlx6QgKyoGkv7fWzqJD/bA598JNJ2Llb4T QKrOQKadPNNW8l3azjiM4adTyTul86NkOIwh/NH948yWH/yJJitn7j3wucLQwVPr rkbVkgDud28VFscm9uHzuC/6JQ8HrUhrWgFPm9t3dmsXFM0SpzV6rKX3npMAEZTq lyaqkjlxdGkFZhCBiUVo5FABXw6YCNLefcJfNEuVN6w1NSuWKlTtmA== =RSYJ -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS Problem (maybe antenna?)
On Wed, Sep 03, 2008 at 01:40:44PM +0200, Joachim Ott wrote: 2008/9/3 Ole Kliemann [EMAIL PROTECTED] On Wed, Sep 03, 2008 at 03:59:02AM +0200, Marco Trevisan (Treviño) wrote: ... I wonder what the date code of your Neo's are. Mine is 20080619, and I have GPS working ok (with tangoGPS in 2007.2) and with the SD-card in place. 20080617 is my date code. GPS is working for most people. I guess it's an individual problem with my device. pgpmwxvmrAfzz.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
GPS device missing in debian
I understand that the GPS device is accessed through /dev/s3c2410_serial1 in debian rather than through /dev/ttySAC1 as under 2008.8 (BTW, GPS under 2008.8 worked for me). However, I'm not getting any s3c2410_serial1 appearing in my /dev, and my debian is up to date, with kernel 2.6.24. All that dmesg says about s3c2410_serial1 is: s3c2440-uart.1: s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440 I couldn't find a module to load. I know other people have this working in debian, but I thought I followed the wiki closely. Any suggestions? Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS device missing in debian
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 moin, which krnl do you use? did you get it from OM or form debian? i am running debian with kernel/modules from OM-daily (20080902) and my GPS-device is under /dev/ttySAC1 .. regards, morlac Am 03.09.2008 um 21:14 schrieb Chris Jenks: I understand that the GPS device is accessed through /dev/s3c2410_serial1 in debian rather than through /dev/ttySAC1 as under 2008.8 (BTW, GPS under 2008.8 worked for me). However, I'm not getting any s3c2410_serial1 appearing in my /dev, and my debian is up to date, with kernel 2.6.24. All that dmesg says about s3c2410_serial1 is: s3c2440-uart.1: s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440 I couldn't find a module to load. I know other people have this working in debian, but I thought I followed the wiki closely. Any suggestions? Chris - -BEGIN CONTACT BLOCK- eMail: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] - --END CONTACT BLOCK-- - -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS$/IT;d-;s:;a?;C++(+++);UL;P++(+++); L++(+++);E---;W++;N(+);o?;K?;!w;!O;!M+;!V;PS(+);PE; Y+;PGP++;t+(++);5(+)++;X(+);R*;tv-+;b++(+++);DI++; D++(+++);G(+)++;e;h-()++;r++;y++; - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFIvumrr81gVylJyzERAoPMAJ9Gx+qkec+qc6v38FMCnPtjXos3BQCg1fdI hMMtPXJDamx1XALIr60ZfTM= =1YmZ -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS device missing in debian
Chris Jenks wrote: I installed using the script at http://wiki.debian.org/DebianOnFreeRunner and, after turning on GPS, tried cat /dev/ttySAC1 but this just returns to the prompt without showing any data. Then I found the /dev/s3c2410_serial1 mentioned at http://wiki.openmoko.org/wiki/Manual_Debian#GPS but now I realize that page is obsolete (relative to the first). If http://wiki.openmoko.org/wiki/Manual_Debian is obsolete it should be deleted. Since I've not installed Debian yet I'm not qualified to make that decision. Can I get some confirmation that Manual_Debian is obsolete so that it can be deleted? Thanks, Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Alsa scenarios , mixer
François TOURDE wrote: Le 14117ième jour après Epoch, Dale Maggee écrivait: SNIP! I wrote a shell script which tells you which state is currently loaded, using this you can figure out what each state file is for: May I suggest a small update to your script, to check if multiple files are matching current alsa status? SNIP! good point, I had it exiting for maximum speed, it never occured to me that there might be multiple identical statefiles. Thanks. Anyway, this script is usefull when trying to check what's up with the sound, and that jack insertion do nothing on sound :( it does for me: [EMAIL PROTECTED]:~# ./findstate Current statefile is: /usr/share/openmoko/scenarios/stereoout.state (plug in headset) [EMAIL PROTECTED]:~# ./findstate Current statefile is: /usr/share/openmoko/scenarios/headset.state [EMAIL PROTECTED]:~# also when I use the headset in a call it uses gsmheadset.state rather than gsmhandset.state (I'm using 2007.2) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
