[debian] FSO/e17
I'd be really interested to hear how people are using Debian with FSO and e17. After installing both, my .xsession now has just #!/bin/sh enlightenment_start I've set the theme to Illume (how do I get Illume2?). 1. The resolution seems doubled that of SHR, and makes everything hard to read. 2. The SIM Auth dialog only appears approximately every 10th boot, and even when it does appear, the OK button is ghosted. Not being able to enter the PIN means that none of the phone apps work, of course. 3. The e keyboard doesn't come up when needed, although literki seems to work ok. Any ideas how I can fix these, especially, #2? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Using the Freerunner as a modem for a laptop
On Mon, Nov 30, 2009 at 10:04:28PM +0100, Sven Hartrumpf wrote: Use DHCP now to connect to your device, that should be it. Sorry, what do I type or launch exactly? Well, as I said, with network-manager, or equivalent, it is trivial. Without, you probably need a section in /etc/network/interfaces like: auto eth1 iface eth1 inet dhcp address 192.168.0.200 netmask 255.255.255.0 Regards Jeff signature.asc Description: Digital signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Using the Freerunner as a modem for a laptop
On Fri, Nov 27, 2009 at 11:50:09AM +0100, Sven Hartrumpf wrote: How can I setup the Freerunner (SHR of 2009-09) as a modem for a laptop (so that the Freerunner acts like a surfstick or similar)? I've just updated the http://wiki.openmoko.org/wiki/Tethering page to include the FSO method, which is by far the easiest. signature.asc Description: Digital signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Bounty for Navit delopment - Free freerunner - anyone?
2009/6/8 Yorick Moko yorickm...@gmail.com: I suggest you all try the new navit (http://download.navit-project.org/navit/openmoko/svn/navit-svn-2308_armv4t.opk) it has a few improvements which MAKE IT USABLE WITH OSM (seems like it was already usable with mapguide reiseplanner): *added a 20 MB cache for the FR *there was a bug until a few days ago which made the navigation to recalculate at every update (mostly with OSM) time to calculate route is now acceptable and re-calculating also! I confirm that with svn-2308 I was able yesterday for the first time to use Navit to navigate with my FR. This found a couple of new problems - the voice is far too quiet - which I assume is an alsa problem, and it navigates to the current position if you pick an impossible destination - i.e. on a road where no cars are allowed. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Best graphics performance?
On May 26, 2009 10:42pm, Sten Kvamme s...@kvamme.se wrote: What distro will give the best graphics performance? I've been wondering about this, specifically because Navit seems really slow on SHR or Debian. I'm using a OSM of Germany, although I'd like to have the whole of Europe covered if it were usable. With just Germany, the FR struggles to keep up with the car on the motorway. At lower speeds, it just about manages it. Navigation is a completely impossible, as the extra load means the graphics just can't keep up. Anybody else struggling with Navit? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[OT] 85-ifupdown.rules
Is there anyone out there running Jaunty? I modified my /etc/udev/rules.d/85-ifupdown.rules file as per the wiki whilst I was still running Intrepid, but it kept the changes with the update to Jaunty, and this has killed my network. If someone running Jaunty could post their /etc/udev/rules.d/85-ifupdown.rules, I would be grateful. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [OT] 85-ifupdown.rules
2009/5/19 Chris Syntichakis ch...@c-64.mobi: I have the 9.04 but there is no such file under the /etc/rules.d Not /etc/rules.d, but /etc/udev/rules.d/85-ifupdown.rules Thanks for trying. Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re: The myth of missed phone calls (was: OM2008.12 - basic usage instructions?)
On May 15, 2009 4:24am, Joerg Reisenweber jo...@openmoko.org wrote: I really wonder how you may get different results on this procedure than the ones supposed, when using NOR uBoot and the unmodified uSD-image according to the README and wiki-instructions. I suspect I let it boot from Qi. Could you please check your NOR-uBoot version (you find it first line of uBoot menu). Could you please also tell us if you by any chance changed your uBoot env. U-Boot 1.3.2-moko12 (May 9 2008 - 10:28:48). I haven't changed the uBoot env intentionally. If you could attach a photo of FR screen after flashing (yes you may start the flash procedure once again), this would be highly appreciated. I'll try and get to this over the weekend. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
2009/5/13 Chris Jenks ch...@jenks.us: I've been playing with the beta Om 2009 consisting of fso-paroli-image, uImage 2.6.38 and Qi 1.0.2 dated 5/8-5/9 but was getting the WSOD when resuming from suspend. I replaced Qi with u-boot 1.3.1 and can now resume properly. Although, from what I understand, 2.6.28 uboot don't suspend properly. I have Qi and 2.6.29 in flash, which works fine, and 2.6.28 on an SD, which gives me WSOD - i.e. the kernel is really at fault, not Qi. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
On May 13, 2009 11:11pm, einstein mailingl...@freeyourphone.de wrote: i have the same problem. i switch to uboot back so i can use the suspend. where i can find the 2.6.29 kernel? with the 2.6.29 kernel the problem is fixed? I use the 2.6.29 kernel from SHR-testing, and with that and Qi, suspend/resume works properly. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: The myth of missed phone calls (was: OM2008.12 - basic usage instructions?)
2009/5/3 Joerg Reisenweber jo...@openmoko.org: # scp location-of-image /dev/mmcblk0 This seemed to work. Booting from the uSD then took the requisite ~6min. I didn't get the green d_o_n_e, however, and it took me to a login prompt. How can I verify the version of the firmware? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: The myth of missed phone calls (was: OM2008.12 - basic usage instructions?)
2009/5/10 Ali alish...@interchange.ubc.ca: In QtE it's under the modem tab of the hardware settings. Or you can use mickeyterm http://wiki.openmoko.org/wiki/OpenmokoFramework/mickeyterm I got the login prompt with a hint of green so I was worried as well, but it turned out fine. Excellent. Thank you for the pointer. It reports GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko11 So that seems OK. Exiting, I get: Exception in thread Thread-1 (most likely raised during interpreter shutdown): Traceback (most recent call last): File /usr/lib/python2.6/threading.py, line 522, in __bootstrap_inner File /usr/lib/python2.6/threading.py, line 477, in run File /usr/bin/mickeyterm, line 553, in reader type 'exceptions.OSError': [Errno 9] Bad file descriptor Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: The myth of missed phone calls (was: OM2008.12 - basic usage instructions?)
2009/5/10 Johny Tenfinger seba.d...@gmail.com: You can also use SHR Settings - Phone - Modem information. So I can. Thanks Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[debian] can't install zhone
# apt-get install zhone Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: zhone: Depends: libevas-engines (= 0.9.9.050+svn20090204) E: Broken packages Are Debian users using a different dialer? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[debian] xfce startup problems
I'm getting the following errors in .xsession-errors when starting xfce: matchbox-wm: unable to open theme: /usr/share/themes/Xfce/matchbox/theme.xml (xfce4-panel:2373): xfce4-panel-WARNING **: xfce4-panel is not running (xfce4-settings-helper:2374): xfce4-settings-helper-CRITICAL **: XI is not present or too old. (xfce4-settings-helper:2374): xfce4-settings-helper-CRITICAL **: Failed to initialize the Xkb extension. (xfce4-settings-helper:2374): xfce4-settings-helper-CRITICAL **: Failed to initialize the Accessibility extension. (xfce4-settings-helper:2374): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8 How do I get a keyboard up? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: The myth of missed phone calls (was: OM2008.12 - basic usage instructions?)
2009/5/1 Joerg Reisenweber jo...@openmoko.org: Am Fr 1. Mai 2009 schrieb Jeffrey Ratcliffe: 2009/4/23 Joerg Reisenweber jo...@openmoko.org: We recommend flashing MOKO11 using the uSD method described in http://wiki.openmoko.org/wiki/GSM/Flashing#uSD-card_Image I'd like to do this, but my uSD card isn't recognised by my host machine. How can I mount a directory on my host machine from the FR? you don't have any directory. Instructions clearly state to dd to the physical device in /dev I have to access the image from somewhere. At 270Mb, it is to big to fit in flash at the same time as an OS. I can't plug in 2 uSDs, so I would like to mount the directory where the image is stored on the host computer, so that I can dd to the device in /dev Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: The myth of missed phone calls (was: OM2008.12 - basic usage instructions?)
2009/4/23 Joerg Reisenweber jo...@openmoko.org: We recommend flashing MOKO11 using the uSD method described in http://wiki.openmoko.org/wiki/GSM/Flashing#uSD-card_Image I'd like to do this, but my uSD card isn't recognised by my host machine. How can I mount a directory on my host machine from the FR? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR testing] opkg error
2009/4/23 D. Gassen dirk.gas...@web.de: I did force it: opkg install -nodeps task-shr-minimal-x I don't think that the missing dependency on glibc-binary-localedata- en-gb does break things (I haven't noticed anything) it made opkg upgrade stop complaining. Thanks. Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[SHR testing] Phonelog borks Dbus
If I start Phonelog, it crashes, borking Dbus along the way. I seem to have to reboot the phone to sort things out. What can I do to fix this? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re: [SHR testing] Phonelog borks Dbus
On Apr 23, 2009 12:49pm, Adam Jimerson vend...@gmail.com wrote: Which SHR-Testing are you using? In the release prior to the 4/16 one I have noticed that and got use to restarting my phone at the first sign of something crashing. In the latest release this seems fixed, I am able to use the phonelog just fine, after the wait while it gets the information or what ever it does. In the latest release the only way I have been able to bork Dbus is if I try and go into the Settings and change something before my phone is registered with my network. I downloaded the image a couple of days ago, and have been opkg update and upgrading daily. Up to now, I have not managed to get Phonelog to start, and after every attempt, nothing else works either. If I don't start Phonelog, then I can access the settings, etc. OK. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[SHR testing] opkg error
I'm getting the following errors after opkg update;opkg upgrade: Collected errors: * ERROR: The following packages conflict with e-wm-menu-shr: * e-wm-menu * * ERROR: Cannot satisfy the following dependencies for task-shr-minimal-x: * glibc-binary-localedata-en-gb * What can I do to fix them? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR testing] opkg error
2009/4/23 Yorick Moko yorickm...@gmail.com: don't know about the localedate thingy, but try opkg remove -force-depends e-wm-menu opkg install e-wm-menu-shr Thanks. That sorted out the one error. Anyone else with ideas on the other one? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[SHR] Vibrate only on alarm
ATM, the alarm app rings a nice old alarm clock ring. Is there any way of getting it to honour the profile, and when needed only vibrate? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re: [FSO 5.1] Preventing screen blanking
On Apr 7, 2009 9:50am, Ingvaldur Sigurjonsson i...@telia.com wrote: I've read the manual/wiki and I read the mailinglist but I cant recall when I read about that stuff so here it comes again... I looked before posting too... You can use 'mdbus' for this kind of stuff by using the dbus-methods provided by the /org/freesmartphone/Usage (org.freesmartphone.ousaged): I think that now FSO is not being funded, I'll switch to SHR, as previously suggested. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[FSO 5.1] Preventing screen blanking
Whilst using the FR for navigation, it would be helpful if the screen didn't blank. In illume's power setup menu, there are two options, blank time, and suspend time. However, blank seems to affect only the backlight, and suspend turns off the screen. If I switch both to off, the backlight still gets turned off after 30s and the screen itself 10s after. How can I prevent either the backlight or the screen from turning off? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO 5.1] WSOD on resume
2009/3/11 Andy Green a...@openmoko.com: Sure, although I think at least one of them will be false / gone away in HEAD. Unfortunately, its worse than that. With the andy-tracking kernel (+ modules - I hope I installed them correctly by simply unpacking them in /), I get no USB - no power, no networking, nothing. Flash the 2.6.28 kernel, and it's all back. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO 5.1] WSOD on resume
2009/3/10 Andy Green a...@openmoko.com: uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin Well it's from Jan 5th. If you're feeling adventurous (you can back out using that uImage anyway) try this kernel http://people.openmoko.org/andy/uImage-moredrivers-GTA02_andy-tracking-15ca3dafb2662db4.bin That fixes it for me! Thanks. It gives me a few error messages on boot. Would you like me to post them? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Qi causes WSOD (was Re: [2008.testing] WSOD)
2009/2/22 Jeffrey Ratcliffe jeffrey.ratcli...@gmail.com: The only other thing I did around the same time was to replace uBoot with Qi. To test this, I booted into NOR, thereby using uBoot, and then booted the 2.4.24 image again (which I had reflashed). Resume then works without WSOD. i.e. Qi, for me at least, causes WSOD. The suspend process seems different, too - with uBoot, the fade to black is gradual, but with Qi, it is more or less instantaneous, with a click, as if a relay was switching. I'll get the friend of mine to redo the SD/GPS fix to make sure that has nothing to do with it, but I doubt it. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
On Feb 24, 2009 2:31am, Andy Green a...@openmoko.com wrote: Suspend and resume on 2.6.24 only works by luck, it's not telling us much. OK. You are saying that with uBoot+2.6.24, it wasn't suspending properly, hence resume worked, but with Qi+2.6.24, suspend worked, but resume is broken. Why does Qi/uBoot affect this? What distro do I need to flash to test this properly (ie which diistro is using 2.6.28 or 2.6.29)? FSO? I understand that I can't simply flash 2.6.29 onto 2008.12 as the userspace file structure is different. Which kernel is Debian using 2.6.24? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[2008.testing] WSOD
My FR suffers from the buzzing problem, and so I got a friend of mine who does that sort of soldering every day as part of his job to do the big-C fix, and whilst he was at it, the SD/GPS fix. Ever since the fixes were done, my FR gets the WSOD, i.e. on resume, the screen goes white, and then fades to black, starting in the middle. Without the SD card, the white screen take much longer to fade, and then to vertical light grey stripes of various widths, a bit like a faded barcode. I assume that the big-C fix can have nothing to do with this, but I wondered if the SD/GPS fix could. Removing the 10pF cap, however made no difference, I still never get the FR to come out of resume properly. The only other thing I did around the same time was to replace uBoot with Qi. To see if a more recent kernel would make a difference, I flashed uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin, but resume problems remain. Any ideas what I can do to sort this out? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi
2009/2/1 Joachim Ott jo.o...@googlemail.com: And while you're on the converting trip: convert your obsolete mmcblk0p1 into a swap partition: Excellent idea. The trouble is that it is only 8Mb, rather than the 64Mb or 128Mb I see recommended. My SD card reader doesn't seem to recognise uSD cards in adapters, and I don't see gparted in an openmoko repository, so I am going to reformat and start again. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[Debian] Can't shutdown
If I shutdown now, the ssh session is kill, and the wm closes down. init sends a kill signal, and then asks for either the root password or ctrl-d, neither of which of course are possible because of the lack of keyboard. Therefore the shutdown hangs. How do I get around this? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[debian] navit
I can't find any recent navit packages for Debian. Do I have to roll my own? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [Debian] Can't shutdown
2009/2/1 Jeffrey Ratcliffe jeffrey.ratcli...@gmail.com: shutdown now Figured it out. This should be: /etc/init.d/halt stop Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi
2009/1/31 Andy Green a...@openmoko.com: So need to remove what you have in partition 1, and add a kernel named /boot/uImage-GTA02.bin into partition 2 (since that's your rootfs), which should be ext2 or better ext3. Thanks. The Debian installer had put the kernel in the root of /dev/mmcblk0p1, not in a boot subdirectory. I added a boot subdirectory with symlinks to the kernel and now it's all working. Why is the journalling of ext3 better? Would the kernel also be better off in an ext3 fs? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi
2009/1/31 Andy Green a...@openmoko.com: Ext3 is better IMO because it can soak up a lot of casual damage that ext2 can't. With my usage pattern I am randomly powering things off all the time I appreciate how ext3 never makes any difficulty for me about that. Whereas after a day of it ext2 is on its knees. OK. You've convinced me. Is there a way of backing up /dev/mmcblk0p2, repartitioning the uSD with one partition, formatting it to ext3, and restoring the backup? Or is it quicker to wipe, repartition, format and install from scratch? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Qi
I bought myself an 8Gb uSD and installed Debian on it, but it wouldn't boot. u-boot simply said it couldn't find the uImage.bin, which is in /dev/mmcblk0p1, with the rest in /dev/mmcblk0p2. I read that Qi might work better, so I flashed the latest from the /andy directory (18.12.08). I added root=/dev/mmcblk0p2 loglevel=8 rootdelay=5 to append-GTA02 on /dev/mmcblk0p1 When I press the power button, it flashes the red LED twice, vibrates very briefly, and then boots from NAND (2008.testing). From NAND, I can mount /dev/mmcblk0p1 and /dev/mmcblk0p2 (both ext2) with no bother. What can I do to boot from uSD? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Bootloader
2008/10/26 Lin Mac [EMAIL PROTECTED]: for the SD issue, kernels in http://downloads.openmoko.org/daily/ (I was useing testing-om-gta02-20081024.uImage.bin) and http://moko.mwester.net/download/uImage-gta02-g291a9d50_mwester-stable.bin fix the problem, while others(om2008.9, debian,...) don't. Are we likely to see a kernel with this fix in 2008.x and Debian in the near future? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Bootloader
2008/10/26 xiangfu [EMAIL PROTECTED]: if you plug you Freerunner and there is /dev/ttyACM0. i think it is work. i always use cu. there is what i always do : - --- chown uucp.uucp /dev/ttyACM0 cu -l /dev/ttyACM0 GTA01Bv4 # setenv boot_menu_timeout 65000 GTA01Bv4 # saveenv - I needed sudo chown uucp.uucp /dev/ttyACM0 and sudo cu -l /dev/ttyACM0 but that got me going. I assume the reason that minicom didn't work is that I didn't use sudo (but got no error message). cu complained without sudo that it didn't have permission. Thanks for the help Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Bootloader
In order to use the workaround in https://docs.openmoko.org/trac/ticket/1743, I'm trying to access the bootloader, following the instructions in http://wiki.openmoko.org/wiki/Bootloader. I boot into U-boot OK, but when I select Set the console to USB I get press AUX to get back to boot menu for maybe a second before I get the boot menu again, and minicom /dev/ttyACM0 stays offline. I've tried chown uucp.uucp /dev/ttyACM0 I'm using Ubuntu 8.10. What am I missing? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: NetworkManager in Intrepid breaks my FreeRunner's Internet connection
2008/10/13 digger vermont [EMAIL PROTECTED]: Recently something changed with NetworkManager in Intrepid, don't know what. With the auto usb0 line in the interfaces file NM decided that They started using the 0.7 version of NetworkManager, which isn't quite finished. it to make it the default route when I plugged it in. I could see the nm-applet going around and then a notification that I was connected to the Freerunner. Looking at connections with nm-applet there were tabs for both the wireless and usb0 with usb0 marked as default. I kinda remember an Ubuntu bug-report concerning the default route in NM. There are plenty of those. I can post them if anyone is interested. Any way my solution was to comment out auto usb0 and manually use ifup usb0 (actually sudo ifdown usb0 sudo ifup usb0 is what I use). Are you saying that you type sudo ifdown usb0 sudo ifup usb0 every time you plug in your FR? I'm beginning to conclude that I will have to remove NM and set up everything manually. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: opkg upgrade FATAL
2008/8/11 arne anka [EMAIL PROTECTED]: or should a file a bug? yes. i think the module is not necessary anymore and no package should have a dependency upon it. https://docs.openmoko.org/trac/ticket/1819 ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
2008/8/5 Andy Green [EMAIL PROTECTED]: Do they say the buzzing is consistent, or it comes and goes? I've not asked in any detail. What frequency of coming and going has been reported? Are we talking seconds or minutes? Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
2008/8/5 Andy Green [EMAIL PROTECTED]: Like Ole says when I started looking at it, by calling a landline in the same room and listening to its receiver lying on the desk, it varied tremendously and not in a repeatable way. Eg, it appeared to vary by orientation of the phone, but when I traced the path backwards, the buzz did not return. OK. Confirming this - the buzzing seems to come and go in waves of varying frequency. Even without touching the phone, the buzzing just comes and goes. Also, I had to keep whistling during this to provoke transmission actions that seem to be the start of the issue. You obviously need a signal generator for repeatability - unless you have perfect pitch... Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Worrisome output from opkg -test update in 2007.2
2008/8/2 Olivier Berger [EMAIL PROTECTED]: Doing an opkg remove gtk+-fastscaling and opkg upgrade gtk+ solved the issue, I think. YMMV though. I needed opkg remove -force-depends gtk+-fastscaling but otherwise this sorted out the error messages. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Factory-fresh phone and dropbear
Is there any mileage in including opkg update and upgrade in a line in /etc/network/interfaces, so that it is automatic on being connected? Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
