Re: Om2009 testing release 4
On Tue, 26 May 2009, Alexander Shulgin wrote: Finally it works for me after qi reflash. :) -- Alex I thought it was working too until I got a couple calls. The callers hung up after not being able to hear me at all. Isn't anyone else having this problem? I'm using the latest u-boot, kernel and root in testing, all dated May 21st, on a stock Freerunner, flashed to v11 of the GSM firmware. I suppose I can see if qi fixes it, but every time I try qi I get WSOD. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
On Sat, 23 May 2009, David Fokkema wrote: On Fri, 2009-05-22 at 19:07 +0300, Alexander Shulgin wrote: On Fri, May 22, 2009 at 6:24 PM, Chris Jenks ch...@jenks.us wrote: On Fri, 22 May 2009, Alexander Shulgin wrote: Hi, Just flashed the latest images and now I get this on boot: In: /var/cache: No space left on device (+ a few more, /var/lock among them) The phone boots up to om-gta02 login prompt. X doesn't start and usb networking doesn't work either. Tried to reformat uSD card, but this didn't help (didn't expect this to work, however). What can I do about the problem? Anyone else getting the same? -- Alex I didn't even notice the /var/cache problem (wasn't paying attention), and I haven't had any problem with the X server, but I can confirm the usb networking problem - I don't get a usb0 interface on my connected desktop as I did with the testing version from the 9th. Also, I tracked the problem down to the root image - the u-boot and kernel images, flashed back to the working images on the 9th, don't fix the problem. ... Oh, silly me. I just realized I didn't reflash the boot loader. Will try a bit later. As to your usb0 problem, you might want to read the release notes. The fact that it doesn't show up means that finally, the usb0 issue is fixed. Hopefully, you'll never see usb0 again. Congratulations! David -- Alex I'll check into that. As for the problem with illume not starting, I was able to get it started only after letting the freerunner run for a few hours. Maybe it was too busy during the first minutes after booting to get around to launching illume. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
On Wed, 20 May 2009, Joerg Reisenweber wrote: Am Mi 20. Mai 2009 schrieb Chris Jenks: Apparently the qi version hosted there is mislabeled as 2.6.28, since I checked what got installed and it is indeed 2.6.29-rc2. Errr, Qi-version, kernel version??? /j Ouch! Yes, I meant kernel. I also just switched back to u-boot after getting the WSOD with the current Qi and current kernel. The new GSM updater that boots and runs from uSD is very nice. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
On Thu, 14 May 2009, Angus Ainslie wrote: On May 13, 2009 03:11:36 pm einstein 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? If you installed the kernel from http://downloads.openmoko.org/distro/testing/NeoFreerunner/ Then you have the 2.6.29-rc2 kernel. To verify uname -a Angus Apparently the qi version hosted there is mislabeled as 2.6.28, since I checked what got installed and it is indeed 2.6.29-rc2. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi causes WSOD (was Re: [2008.testing] WSOD)
On Mon, 23 Feb 2009, Jeffrey Ratcliffe wrote: 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. [...] 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. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS device missing in debian
On Thu, 4 Sep 2008, Joachim Breitner wrote: Hi, Manual_Debian is still of interest to people who, well, want to do it manually, or learn more about the system. But if it confuses people then yes, go ahead and delete it. Greetings, Joachim It seems useful to me. Maybe enlarge the disclaimer at the top? I hate to get rid of any resource that might help me avoid bugging the generous people here. Regarding the gps device, I noticed that occasionally when I cat /dev/ttySAC1 I get little snippets of text, like $GPZDA,00, and ,,99.99,99.9, although I usually get nothing. I was surprised in 2008.8 when cat /dev/ttySAC1 kept listing output as it was generated - more like tail -f. However, tail -f /dev/ttySAC1 gives no output for debian. Is the driver module for the gps compiled into the kernel, or is it supposed to be loaded? My lsmod gives: Module Size Used by rfcomm 36692 0 l2cap 21380 5 rfcomm bluetooth 54880 4 rfcomm,l2cap ipv6 253796 18 ohci_hcd 22284 0 snd_soc_neo1973_gta02_wm8753 8200 0 snd_soc_s3c24xx_i2s 4120 1 snd_soc_neo1973_gta02_wm8753 snd_soc_s3c24xx 4736 1 snd_soc_neo1973_gta02_wm8753 snd_soc_wm8753 29376 1 snd_soc_neo1973_gta02_wm8753 snd_soc_core 27488 3 snd_soc_neo1973_gta02_wm8753,snd_soc_s3c24xx,snd_soc_wm8753 snd_pcm_oss40384 0 snd_mixer_oss 14976 1 snd_pcm_oss snd_pcm73733 3 snd_soc_s3c24xx,snd_soc_core,snd_pcm_oss snd_timer 20388 1 snd_pcm snd_page_alloc 6376 1 snd_pcm snd46740 7 snd_soc_neo1973_gta02_wm8753,snd_soc_wm8753, snd_soc_core,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer Thanks, Chris ___ 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: Debian root password
On Sun, 31 Aug 2008, archon44 wrote: Chris Jenks wrote: I seem to have successfully installed debian on my SD card and am able to boot to zhone, but when I try to ssh to [EMAIL PROTECTED] it won't take a blank password. I am able to login to 2008.8 from the same host successfully. I would try to reset the password from xterm, but no keyboard appears when I press or hold the aux key! Any suggestions? Try to ssh to your 2008.08/2007.02, chroot to microsd card filesystem mountpoint (for me it was /media/mmcb*) and then simply change your debian password. Worked for me This is a good solution. I was going to take it, but first I wanted to see if I could fix the problem by connecting the external USB keyboard I finally got a USB A - mini USB A (5 pin) adapter for. I was disappointed that the keyboard didn't seem to get power nor did it get recognized (Fn keys didn't work), so, not seeing a better way, I did a power cycle to reboot and waited through the fsck. After this the keyboard still didn't work, but then I reconnected the USB to the host I was able to shell in using a blank password. So the password was reset from non-blank to blank after a (second) hard reboot. I haven't researched the keyboard problem - I assume I need a powered hub, but I'll read. No need to address that here. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Testing WIFI and GPS hardware
On Fri, 15 Aug 2008, arne anka wrote: strength of 27/94 according to the iwlist eth0 scan command. Other people have reported that WIFI to unsecured WAPs worked out-of-the-box, i think, you need at least to associate with the ap, ie use iwconfig to set the ap and maybe the channel. OK, I se the ESSID and channel (obtained from iwlist eth0 scan) with iwconfig eth0 essid myap iwconfig eth0 channel 11 I notice that the output of iwconfig eth0 gives a setting for the access point: eth0 AR6000 802.11g ESSID:myap Mode:Managed Frequency:2.462 GHz Access Point: 00:B4:63:97:AD:27 Bit Rate=1 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Power Management:off Link Quality:188/94 Signal level:-163 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:13 Invalid misc:0 Missed beacon:13 and ifconfig eth0 gives values for received and transmitted data: eth0 Link encap:Ethernet HWaddr 00:1F:3F:BE:45:2B inet6 addr: f58b::263:ceff:fd87:ed25/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:429957 errors:0 dropped:0 overruns:0 frame:0 TX packets:12080 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:607951527 (579.7 MiB) TX bytes:128021 (125.0 KiB) but if I start pinging an external IP address from the Freerunner and pull the USB cable, pings stop returning until I plug the cable back in and restart networking on the host. Although I couldn't get WIFI to work under the Locations graphical application (which says Searching for your location and then ERROR: Unable to locate a fix when I turn on GPS), I haven't heard of much success from others either. not sure, what you're talking about -- wifi or gps? Sorry, I meant GPS, not WIFI. [...] - do echo 1 /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron cat /dev/ttySAC1 and watch the output, after a while the should be lines with all fields filled I see the same group of lines repeating: $GPRMC,,V,,N*53 $GPVTG,N*30 $GPGGA,,0,00,99.99,,*48 $GPGSA,A,1,99.99,99.99,99.99*30 $GPGSV,1,1,00*79 $GPGLL,,V,N*64 $GPZDA,00,00*48 but I'm not sure how to interpret them. Thanks for your help! Yours, Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
