Re: [FSO] Wifi in M5 no longer functioning
I'm having the same problem.
Dylan Semler wrote:
It seems that my prior FSO wifi configuration no longer works with M5.
r...@om-gta02:~# ifup eth0
WPA: Configuring Interface
ioctl[SIOCGIFFLAGS]: No such device
Could not get interface 'eth0' flags
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIFINDEX]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 7 value 0x0 - Failed to disable WPA in the driver.
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
wpa_supplicant: /usr/sbin/wpa_supplicant daemon failed to start
FAILED
ifconfig: SIOCGIFFLAGS: No such device
eth0 No such device
ifconfig: SIOCGIFFLAGS: No such device
I'm using WPA2 configured as follows:
# cat /etc/wpa_supplicant/cat wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid=private
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk=private
priority=50
}
And I've added the line: wpa-conf
/etc/wpa_supplicant/wpa_supplicant.conf beneith the line iface eth0
inet dhcp in /etc/network/interfaces.
This configuration has worked for all other distributions thus far.
Is something different this time around?
Dylan
___
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
Zhone won't install - still relying on libpython2.5-1.0
I flashed the newest FSO testing image, which doesn't come with zhone installed anymore. When I try to install zhone I get the error: ERROR: Cannot satisfy the following dependencies for zhone: libpython2.5-1.0 I have libpython2.6-1.0 installed, and trying to install the older version just gives more dependency errors. Any ideas? It would be nice to be able to install a phone on FSO. Marcus ___ 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)
You don't need to mess with uboot environment anymore. Download the kernel in the android forum at forum.koolu.org in the Android Pre-built image... thread, where the kernel is under 2M. Android works well, but the phone is unusable still in my opinion. It's so quiet that you can't hear ANYTHING with any background noise such as in a car, on the street, with music in the background. This is being worked on, but if you're looking for a usable phone, this isn't it yet. Don't get me wrong, I love it, and actually feel quite motivated to help resolve this volume issue, because otherwise it's a great environment. Gothnet wrote: Craig Woodward wrote: Funny you mention that... it's the last on my list, since I've tried most of the others but this one has failed to boot after several attempts. I got a new uSD card just for this setup to see if thats what's preventing the boot. Two things I found that stop boots on android images I've used are - SD card partitions and uboot. If you're using uboot you must alter the uboot environment to be able to use a larger kernel. The default limit is 2MB. The way I did it was to grab the uboot env using dfu-util ... basically follow the instructions http://wiki.openmoko.org/wiki/Bootloader#What_if_I_borked_my_bootloader_environment_and_don.27t_get_a_prompt_anymore.3F here but edit the environment.in file to set a kernel partition size of 3 or so MB. There's also a way to do it using the uboot command line but I'm not familiar with that. The SD card *must* be formatted with two partitions. The second one *must* be ext3. The first I usually format as FAT 16, though FAT 32 may work too. The first partition will appear to android as its SD card, the second will be used for its data/config store. I don't know what size to recommend, but it's worked with 2/6GB on my 8GB card. HTH. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Call Volume on wired headset
I'm using the latest testing milestone of FSO, and am trying to get the wired headset working better on zhone calls. The earbud volume is rather weak. I've altered gsmheadset.state control.3 values to 1 (from 87). It's turned up the volume a bit, but still not enough. I also changed the value of control.6 to 1 as well. Maybe I'm not getting how this works. I tried the maximum value of control.3 (120 or something), but that seemed to make it quieter. Can someone guide me on how to make the wired headset louder. It's now a law in Ontario that you have to use hands-free while driving, and right now, I won't be able to hear anything with noise created driving on the highway. Thanks, Marcus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Re: Call Volume on wired headset
Hey Al, Phone's gta02 with FSO milestone 4.1. I changed the values back up to 127 and 7, and rebooted, and then made a call, with no difference. I wonder does FSO or zhone not use the .state files? Just to be clear, I'm changing the gsmheadset.state file at /usr/share/openmoko/scenarios Marcus On Wed, Jan 14, 2009 at 12:13 PM, Al Johnson openm...@mazikeen.demon.co.ukwrote: On Wednesday 14 January 2009, Marcus Stong wrote: I'm using the latest testing milestone of FSO Please quote the actual version number to avoid confusion. As I understand it 'latest milestone' is currently 4.1. It also helps to know whether you have gta01 or gta02 as the mixer channel numbers are apparently different. , and am trying to get the wired headset working better on zhone calls. The earbud volume is rather weak. I've altered gsmheadset.state control.3 values to 1 (from 87). It's turned up the volume a bit, but still not enough. That's odd - setting it to 1 should give almost no output, at least on a gta02. Mine is at 96 and maxmum is 127. I also changed the value of control.6 to 1 as well. From what? Mine is at 7 (maximum) Maybe I'm not getting how this works. I tried the maximum value of control.3 (120 or something), but that seemed to make it quieter. That's very strange. It seems as though you are editing the correct controls, and the differences should be obvious given the large level changes you seem to be making. I can't test it myself until I've resoldered my headset, but I've not had any problems with it in the past when changing audio settings. i haven't checked to see that FSO does actually use the gsmheadset.state when the headset is plugged in. I assume you are editing the file, saving the changes then starting a new phone call to test the settings. Can someone guide me on how to make the wired headset louder. It's now a law in Ontario that you have to use hands-free while driving, and right now, I won't be able to hear anything with noise created driving on the highway. ___ 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
Once a whiner
I'd just like to say, for all the whiners using om 2008.x (I've been one just recently, too), try FSO testing. I've been using it for a few days, and everything seems to work like a charm compared to OM2008.x. Suspend works great, battery life is killer, boot time is good, telephony seems solid. Granted there's no UI for wifi and no bluetooth support, it's still eons ahead of OM2008 as far as I can tell. Really, I think everyone needs to get over om2008, including open moko, because it just doesn't work. But I have renewed faith in my phone now that I've installed FSO. Great job FSO team! ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Suspend in om2008.12
Isn't suspend one of the things that was suppose to be fixed in om2008.12, or was this one of the things that never got fixed? It seems like the last FDOM had a more stable suspend/resume than this. Marcus On Tue, Dec 23, 2008 at 4:21 PM, Marc Bantle openm...@rcie.de wrote: Marcus Stong schrieb: Is it just me, or does suspend freeze on om2008.12. I flashed the latest stable images to my freerunner, but it won't wake up when in suspend. I've rebooted several times. Any suggestions? To me it seems that suspend as well as shutdown hang for a while and therefore a manual resume is not honored. If I give it the time to suspend (estimated 5 min.) it will resume properly. While suspend can be initiated by a short click on the power button, I need to press for 3 seconds or more to resume. I personally prefer resuming by a simple click of the power button as in om-testing. Cheers, Marc ___ 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
Suspend in om2008.12
Is it just me, or does suspend freeze on om2008.12. I flashed the latest stable images to my freerunner, but it won't wake up when in suspend. I've rebooted several times. Any suggestions? Marcus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Stable Upgrade Anytime Soon?
It's been over a month now that opkg upgrade has produced nothing whatsoever. I know the back to basics are being worked on, but does anyone know how long until something makes it to the stable feed? I know part of my frustration relating to me venting on the whole sad story thread has been partially because it really seems like nothing is happening. I realize there's a testing feed, but I don't really have the time to go through all the steps to make it work for a while. I don't see why it's taking so long to pass anything to the stable feed. It's not like it's really stable to begin with, so there isn't much to lose. The dialer crashes, suspend freezes, and there's low call volume using FDOM or OM2008.9. I really would like to see a carrot dangled in front of my nose... that's always been the fun with this phone, and there haven't been too many carrots lately. Marcus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
I agree with this whole thread of Openmoko's fatal mistake of moving on to GTA03 with GTA02 still being unstable and unusable as a primary phone. If GTA02 gets left behind in the dust without ever working properly, it doesn't say much for their company. If Openmoko feels the hardware of GTA02 is inadequate to even bother making it a stable phone, there should be some sort of recall and free replacement with a GTA03. $399 for a phone that never worked properly is pretty hard to swallow, and even harder to swallow when the company expects people to buy a new phone while blatantly ignoring that same community of users who have invested time and money in developing and testing their original phones. - Marcus Karthik Kumar wrote: I clearly don't blame the developers here myself. I blame Openmoko's selfish management (probably it's board of directors or C*Os) for this. I am sure that a developer who talks back against this will just get fired/have to face bad consequences. What would be the best way to 'convince' or 'force' the management to change their decisions? Does anyone know a lawyer? -Karthik On Fri, Dec 12, 2008 at 11:23 PM, Paul pault...@gmail.com wrote: My experience, as I'm sure with many other people, with my freerunner has been frustrating most of the time. To say, its all on the user is wrong. Granted the community could be better, however, its hard to contribute when everything is so fragmented. For instance, about the echo problem, one of the developers for OpenMoko stated Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. Wait a sec. If the developers know the issues, What's preventing the if statement that would prevent hundreds of hours of tweaking, testing, and frustration for the community? Let's be honest here FIC is making a pretty penny off of OpenMoko, using very old hardware selling at a premium price (2.5g not even EDGE). Yet we are OK with that. What the community DOES expect is basic support, for starters a phone that makes calls without echoing, doesn't drop connection and sends and receives text messages reliably as the Number 1 priority. If I'm not mistaken, the majority of the working code in OpenMoko is from Trolltech. In addition FSO has a very nice distro and the Freerunner isn't even its main device. Yet more than 1 year AFTER the release of the 1974, we still have MAJOR issues from a basic install of Om. Then we read stuff like this. OM is moving more focus to gta03 now, so my current resource for qtopia is fairly limited. It becomes evident that FIC and Openmoko cares less about creating reliably working software then it does about moving products. (not blaming the developers here, they get pressure) Follow the next link and I think I've made my case. http://www.cafepress.com/openmoko_inc Now with that said, I will be posting online my howtos including scripts to make a kinda stable variant of FDOM soon. Been too busy reflashing my phone. On Fri, Dec 12, 2008 at 1:28 AM, Karthik Kumar karthikku...@gmail.com wrote: You should have fixed the GTA02 months back, when you released it. Instead, you people are working on GTA03/Neo Whatever. It proves that you don't care about the community, You just care about the bunch of people who might want to buy your upcoming phones, who sponsor your own selfish causes and suffer while you are working on GTA04. -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ 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
Re: Sad Story
A quick thought...if Openmoko feels the hardware of GTA02 is inadequate to even bother making it a stable phone, should there not be some sort of recall and free replacement with a GTA03. $399 for a phone that never worked properly is pretty hard to swallow, and even harder to swallow when the company expects people to buy a new phone while somewhat ignoring that same community of users who have invested time and money in developing and testing their original phones. Speaking from the perspective of a web developer, if I make a piece of shit site that doesn't work properly, my clients are going to demand that it works properly. If I neglect to do that and move on to the next project, I would run out of clients pretty fast... - Marcus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Qtopia Extended GPS Application and Auto Rotate
I've installed Qtopia Extended, but can't seem to find any GPS app anywhere, and the claims of Dynamic Screen Rotation leaves me scratching my head as well. You can manually rotate in settings, but it's far from Dynamic. Can someone point me in the right direction? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qtopia Extended GPS Application and Auto Rotate
Does mapping demo have any of the functionality of tangogps? I can't even seem to zoom in or out or move around the map, let alone add POIs or the sort. Does anyone know if there are any plans to port over tangogps? On Sat, Oct 4, 2008 at 12:40 PM, Philippe Guillebert [EMAIL PROTECTED] wrote: Marcus Stong wrote: I've installed Qtopia Extended, but can't seem to find any GPS app anywhere, and the claims of Dynamic Screen Rotation leaves me scratching my head as well. You can manually rotate in settings, but it's far from Dynamic. Can someone point me in the right direction? Hi, I can answer the first part : in order to get the GPS application (named mapping demo) : - open the menu - open applications (the colored boxes) - in the list, you should have the mapping demo. Didn't tested it yet, since I'm indoors. I second you on the screen rotation part. But on the whole, Qt Extended 4.4 is really useable and fast (especially if you load the smart theme, and use the latest mwester kernel). Thank you Lorn for your excellent work ! -- Phyce ___ 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
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
Zecke Repo
Does anyone know if the Zecke Repo was shut down? When I opkg update using the testing.conf file I've been using, I get: * Failed to download http://people.openmoko.org/~zecke/om2008.8-testing/all/Packages.gz, error 404 * Failed to download http://people.openmoko.org/~zecke/om2008.8-testing/all/Packages.sig, error 404 * Failed to download http://people.openmoko.org/~zecke/om2008.8-testing/armv4t/Packages.gz, error 404 * Failed to download http://people.openmoko.org/~zecke/om2008.8-testing/armv4t/Packages.sig, error 404 * Failed to download http://people.openmoko.org/~zecke/om2008.8-testing/neo1973/Packages.gz, error 404 * Failed to download http://people.openmoko.org/~zecke/om2008.8-testing/neo1973/Packages.sig, error 404 * Failed to download http://people.openmoko.org/~zecke/om2008.8-testing/om-gta02/Packages.gz, error 404 * Failed to download http://people.openmoko.org/~zecke/om2008.8-testing/om-gta02/Packages.sig, error 404 It used to work fine. I reflashed the rootfs and kernel, but now can't upgrade with the Zecke repo. Marcus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Mofi issue on 2008.8 stable
Edit the file /usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py On line 82 change: init() to _init() (add an underscore at the start) That fixes the problem. Marcus Yorick Moko wrote: On Wed, Aug 27, 2008 at 6:56 AM, Lisa [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tried to start Mofi (v2) and get this Traceback (most recent call last): ~ File /usr/lib/mofi/mofi_gui.py, line 30, in module ~import gtk ~ File /usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py, line 82, in module ~init() NameError: name 'init' is not defined ~ Any ideas on how to fix this? ~ Thanks, ~ Lisa -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFItN6Z1sOMhsR36UsRAjOIAJ4y7o3jzAISwsRYQ+8Tuo2vwoQ+CACgmrgg KQaEvtHa7YYqHaMDuzbFetI= =2px+ -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support 1 why not try mofi 0.3?? 2. it's a know error: in /usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py, line 82, change init to _init. I don't know if a bug report is in order or not ___ 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
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, and have upgraded using the testing.conf Any ideas how to fix this? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
