Re: [2008.12] Help with Om.2008.12 on microsd
Don't know if this is expected behaviour, but when I moved rw part before all other kernel parameters: r...@om-gta02:~# cat /boot/append-GTA02 rw console=tty0 loglevel=8 rootdelay=1 now Neo boots fine with Qi and finally shows Illume desktop and everything. 2009/1/4 Evgeny Karyakin anthropophag...@gmail.com: 2008/12/30 Andy Green a...@openmoko.com: Somebody in the thread at some point said: | Em Sab, Dezembro 27, 2008 04:06, Kosa escreveu: | I've been trying to boot 2008.12 from a microsd but it just can't. | It starts booting but then it stops with an Only GTA01 hardware | supported by ASoc driver message. | | Happens to me also, but after that message I also have the following | messages (not sure if they change from boot to boot): | | Unknown HZ value! (87) Assume 100. | mount: special device /dev/mmcblkp01 does not exist | ALSA: restoring mixer settings... | Configuring network interfaces... /usr/sbin/alsactl: load_state:1327: No | soundcards found... | ADDRCONF(NETDEV_UP): usb0: link is not ready | done. | | I can shutdown by holding the power button. | I have FDOM in the same card and it works fine. I was just meddling with this in NAND, I believe that ro on the kernel commandline is fatal for startup of 2008.12. When I removed it from Qi, 2008.08 started up OK. So check your U-Boot env if you're using that for ro, or try adding rw to /boot/append-GTA02 if you are on SD Card and Qi. It's pretty common to boot with rootfs ro initially... I have these problems also, and adding rw to append-GTA02 didn't solve it. Full content of my /boot/append-GTA02 is this: console=tty0 loglevel=8 rootdelay=1 rw (brainless copy-paste of everything related from Qi wiki page[1]). ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.12] Help with Om.2008.12 on microsd
2008/12/30 Andy Green a...@openmoko.com: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Em Sab, Dezembro 27, 2008 04:06, Kosa escreveu: | I've been trying to boot 2008.12 from a microsd but it just can't. | It starts booting but then it stops with an Only GTA01 hardware | supported by ASoc driver message. | | Happens to me also, but after that message I also have the following | messages (not sure if they change from boot to boot): | | Unknown HZ value! (87) Assume 100. | mount: special device /dev/mmcblkp01 does not exist | ALSA: restoring mixer settings... | Configuring network interfaces... /usr/sbin/alsactl: load_state:1327: No | soundcards found... | ADDRCONF(NETDEV_UP): usb0: link is not ready | done. | | I can shutdown by holding the power button. | I have FDOM in the same card and it works fine. I was just meddling with this in NAND, I believe that ro on the kernel commandline is fatal for startup of 2008.12. When I removed it from Qi, 2008.08 started up OK. So check your U-Boot env if you're using that for ro, or try adding rw to /boot/append-GTA02 if you are on SD Card and Qi. It's pretty common to boot with rootfs ro initially... I have these problems also, and adding rw to append-GTA02 didn't solve it. Full content of my /boot/append-GTA02 is this: console=tty0 loglevel=8 rootdelay=1 rw (brainless copy-paste of everything related from Qi wiki page[1]). Problem is, I can't even tell for sure if Neo (Qi actually) boots from uSD or NAND. Hurting my eyes on running on-screen log I saw something like Waiting for 1sec before rootfs, which suggests that it's Qi taking appeng-GTA02 into consideration. Still I have multiple read-only filesystem tar warnings. Every power-up after battery out+in gives Neo several seconds to boot up -- detailed logs on screen -- then it just switches off. Next boots freezes like described by other people in this thread. First successful boot freezed on these lines in on-screen log: asoc: WM8753 HiFi - s3c24xx-2c mapping ok asoc: WM8753 Voice - Bluetooth mappgin ok Only GTA01 hardware supported by ASoc driver Next successful boot ended up with previous lines plus this (... means long message): mount: special device /dev/mmcblk0p1 does not exist ALSA: ... ... load_state:1327: No soundcard found... usb0: link is not ready done. And it freezed again. uSD card must be good, because I can read-write it through notebook card reader and if I go to NAND menu and modify boot command line to load from uSD, it works just fine. Behaviour is unstable: I could boot (from NAND!) *once* while trying to boot from uSD/Qi , and it's the same with 2008.12 release as well as with 04.01.2009 testing. I also boot with SIM card inserted so weak uSD reader contacts shouldn't be an issue. Should I return to u-boot technique for starting up Neo? I wanted to give Qi a try for it is a modern way of doing things. [1]http://wiki.openmoko.org/wiki/Qi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: detect host type?
Maybe http://nmap.org/book/man-os-detection.html ? 2008/12/20 Joel Newkirk freerun...@newkirk.us: OK, an FR has just been plugged into the USB port on a random host PC. Is there any way for the FR to consistently identify if it is a windows, mac, or linux host? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Stage of GTA03 development?
2008/12/17 Laszlo KREKACS laszlo.krekacs.l...@gmail.com: For case design, I find these (among others) great: - http://www.om.vptt.ch/site/?page_id=53 - http://www.rasterman.com/files/gta03-idea-1.png - iphone Dunno... First link propose a case suggesting iPhone look, I think we shouldn't follow everything Apple come out with, and I second to pill case. When I first saw GTA02 look, I thought it's ugly, but that was just because it's unusual; now I like it and like a bottom hole around antenna. With relation to Raster's case, if you're going to get sliding number keyboard, we just enter a troublesome field of hardware modification difficulties as infamous buzz/echo problem has proved us: * It's a moving part and can be broken. * Software developers will enforce heavier requirement on users to use keyboard; programs can become more difficult to use without it. * Localization issues. Hopefully Openmoko (phones) will be wide-spread across the world, but will Openmoko (company) be able to make several lingual versions of keyboard? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [testing] WSOD gone
2008/12/7 Andreas Cyberfrag Fischer [EMAIL PROTECTED]: This is on the testing branch. Flash OM2008.9, switch to testing as described here: http://n2.nabble.com/Optimization-team-update-%2811-23-%7E-11-29%29-td1595015.html#a1600801 and do a full update (opkg update opkg upgrade). Will it bump all the software to the latest? I mean, will the phone end up with all software from 2008.x official release (kernel + graphics + qtopia dialer + gps + ...), but latest versions of them? I guess so. For a couple of weeks I just take http://downloads.openmoko.org/daily/testing/ images to play with, and constantly being ridicued by colleagues like what have you bought, a black screen with white letters? :-) . I must say in this textual state Neo performs very well. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: microsSD doesn't mount any more!
2008/12/8 Tony Berth [EMAIL PROTECTED]: On Fri, Dec 5, 2008 at 2:45 PM, Andy Green [EMAIL PROTECTED] wrote: | [ 30.365000] Buffer I/O error on device mmcblk0, logical block 8 Are there some glamo-mci errors floating around before that? some more feedback: I did format my card with 'http://www.sdcard.org/consumers/formatter/' but still doesn't work on FR. I get following dmesg: [ 73.055000] glamo-mci glamo-mci.0: Error after cmd: 0x8020 [ 73.055000] glamo-mci glamo-mci.0: Error after cmd: 0x8120 [ 73.06] mmcblk0: error -110 sending read/write command [ 73.065000] end_request: I/O error, dev mmcblk0, sector 0 [ 73.065000] Buffer I/O error on device mmcblk0, logical block 0 ... I suffered (and to some extent still suffering) with similar troubles and ended up completely blank SD card with dd if=/dev/random of=/dev/mmcblk0 command, and then repartition it with fdisk as described in wiki[1]. Also you can try slowing down glamo rate for SD access by getting some hints from[2], although the latter trick has to deal with another problem. [1] http://wiki.openmoko.org/wiki/Booting_from_SD#Partioning_the_SD_card [2] http://docs.openmoko.org/trac/ticket/1743#comment:4 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OM2008.x] praise for the new testing image
2008/12/5 Vadim, Efimov [EMAIL PROTECTED]: On Fri, 05 Dec 2008 08:05:19 +0300, John Lee [EMAIL PROTECTED] wrote: I would like to know how many people need this. My resource for qtopia is very limited and I need to decide what to fix first. mmm... how many people need USSD ? In Russia it is difficult get balance other way, and the USSD-message comes in cyrillic letters. also, we have many services via USSD... but, i'm not know how many freerunners sold in Russia. at least 20-30. There was a useful message[1] in openmoko-russia Google Groups list from Pavel Fertser, which essentially said: 1) First open one console and say: # mdbus -s -l org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device It will log everything device receiving. 2) Then issue following command in another console: # mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.Network.SendUssdRequest *102# 3) You should see network's answer in first window. Replace *102# with a sequence of your GSM operator. [1] http://groups.google.ru/group/openmoko-russia/msg/8018ee80bc2fab7a ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Bounties?
The only problem I see really is that there are many issues which are wrapped up together. For example, I'd happily pay AU$100 to have rock-solid with all the basic phone functionality, but for me this means suspend / resume, no echo, a simple (as in easy to use and understand) graphical volume control which can be adjusted during calls and automatically saves changes to the appropriate state file, PIM database and PIM synchronisation, Tasks / Calendar / alarms. From a user's perspective, these are kind of one big compound issue which I'd call give me equal functionality / reliability to a cheap nokia, whereas from a developer's perspective they're many small and widely diverse things that need to be done / improved. I certainly think it could be worth somebody setting up a bounties website, I believe I've seen similar things in the past... Looks sane. As virtually everybody want what you just enumerated, these $100-200-300-more(?) can be collected from large crowd of Openmoko users. Written once -- used by many. And yet it doesn't violate open source/development spirit. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: community Digest, Vol 107, Issue 18
Hello Dmitry! 2008/11/26 Дмитрий Попов [EMAIL PROTECTED]: I have Transend 2gb microSD card but problem with I/O according logs from Freerunner. According manuals : setenv bootargs glamo_mci.sd_max_clk=1000 But I haven't command like setenv Which pkg I need to install or maybe send me link to how-to. First thoroughly read http://wiki.openmoko.org/wiki/U-boot (hint: http://wiki.openmoko.org/wiki/U-boot#Bootloader_prompt), plus some additional advices can be found at http://docs.openmoko.org/trac/ticket/1743#comment:4 and further below. Please pay attention to your input as environment editing is a low-level task and things can break. And would you please change your e-mail name to something not using Cyrillic letters 'cause various mail archives like lists.openmoko.org and possibly nabble.com can't handle non-ASCII letters correctly. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 2Gb transend SD: issue
2008/11/26 Dmitry Popov [EMAIL PROTECTED]: Hi All Just I need only nice solution (some people have lost phone). I had some troubles with this procedure also, but I was assured here on the list that you can't break u-boot fatally doing this things. Just follow wiki[1] link to get familiar with getting u-boot console, and proceed to trac[2] link for step-by-step instructions, following by beni's success story. Another option (less safe definitely) can be reflashing[3] your NOR environment with snapshot from exactly the same revision of GTA02 which is already patched against this I/O problem; I don't think anybody would suggest you that. [1] http://wiki.openmoko.org/wiki/Bootloader [2] http://docs.openmoko.org/trac/ticket/1743#comment:4 [3] http://wiki.openmoko.org/wiki/Flashing_NOR ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OT]Software patents end? ??:) light at the end of tunnel
I think this movement will apply on newly-legalizing patents only, it will be too much counterforce against it. Patents is vital for software giants, it's just a basis of their market activity and relevancy. As of recent MP3 issue, open-source community can definitely apply just a little bit more willingness and forget about deprecated formats in favour of new ones. If there's a feeling among people like MP3 is a safe bay and Ogg-Vorbis/LAME/etc is uncertainty, it can be overcome easily. 2008/11/25 David Reyes Samblas Martinez [EMAIL PROTECTED]: Dear all, Is a little bit offtopic but due recent mp2/mp3 fight against pirat... sorry Sysvel, maybe is interesting to spread this little bit of hope to the Openmoko community Trough a local FOSS-friendly news site[1] I read there is a 180 degrees in Software pattent policy in US pattent office , it can invalidate almost ALL Software patents aviable. Yes, seems a Fools day joke but Slashdot also has articles about this here[2] and here[3]. I'm very excited, but is too late night for a in depth read of legal mambo jambo , may be someone with more legal skills can assure that is so awesome as it seems [1]http://www.barrapunto.org [2]http://yro.slashdot.org/yro/08/07/24/1458215.shtml [3]http://yro.slashdot.org/article.pl?sid=08/11/24/1713259 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
2008/11/24 Nikita V. Youshchenko [EMAIL PROTECTED]: Yes, I know that, but I'm unable to connect to the phone through DFU protocol because Neo don't offer itself as a device supporting DFU. Have you tried to connect usb cable AFTER freerunner started NOR u-boot? I haven't; will do that later at home since I have neither phone nor Linux box here at work... Thanks for the hint. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
2008/11/24 Andy Green [EMAIL PROTECTED]: My early problems with DFU disappeared after I took this approach in a script, it seems it can announce under two different PIDs (this one is for updating U-Boot): #!/bin/bash dfu-util -a 1 -d 0x1d50:0x5119 -D u-boot.udfu if [ $? -eq 1 ] ; then dfu-util -a 1 -d 0x1d50:0x5120 -D u-boot.udfu dfu-util -a 1 -d 0x1d50:0x5119 -D u-boot.udfu fi I'll try this as well, thanks, although listing of any connected DFU devices with dfu-util -l outputs nothing, which means desktop doesn't see Freerunner at all. I'll try Nikita's advice on connecting USB cable after starting NOR u-boot. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
2008/11/24 Paul Fertser [EMAIL PROTECTED]: It might be a silly suggestion but please double-check the usb cable used, try to connect directly to the motherboard (avoid front-panel connectors and usb hubs). May be you should try another PC. By no means (as you have no dboard) you could have damaged the NOR bootloader by dfu-util. It should just work. The battery must be charged before the flashing (you can even use any full-charged Nokia battery). Try removing the battery for some time (to ensure clean boot), then boot directly into the NOR uBoot, connect to PC and try to flash. If it doesn't work, use another cable/usb port/pc. This might also be the cause of it, I'll check, thanks. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
seems you experience the well known sd card issue. wiki and/or archives should offer a lot of postings on the issue. it boils down to setting sd_max_clk -- in your case in the nand boot environment since your fr seems unable to boot from sd at all. searching for sd_max_clk +openmoko should give you sufficient enough hits. Thanks for suggestion, I've found a lot of information on this. Now I have a disaster... Trying to follow http://docs.openmoko.org/trac/ticket/1743#comment:5 I entered /dev/ttyACM0 console and redefined bootcmd environment variable through minicom terminal emulator. Something went wrong -- I don't know what step caused it -- and since then Neo could still boot from NAND (kernel + rootfs) but couldn't be reflashed, it says something like writing past memory available, I guess it's because broken environment. I've found some promising info about Factory reset, but it wasn't in my NAND boot menu. Bad. Next I found Devirginator which promises to do that reset another way. One of the steps described in http://wiki.openmoko.org/wiki/Bootloader says that I need to make a shot of current env before modifying it writing it back in place. So I issued dfu-util -a u-boot_env -R -U env.in and this was the end. dfu-util said that no DFU device is present and exit. Now Neo can't even be seen as DFU device from my notebook. Although Freerunner boots its current software version, FSO milestone 4. What next? Resort to http://wiki.openmoko.org/wiki/Bricked or search for a guy with Debug board or ...? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
From: arne anka [EMAIL PROTECTED] like writing past memory available, I guess it's because broken environment. hardly. i'd rather think you try to flash the wrong partition. what exactly did you do and what exactly did dfu-util or the fr report? I already flashed Freerunner several times before with dfu-util -a u-boot -R -D uImage-XX.bin with no troubles, last time I tried uImage-2.6.24+r10+gitr6e2a723ef54ee2e739c34786981b2c508db803c1-r10-om-gta02.bin which is 1895768 bytes long so there shouldn't be a problem here. dfu-util now can't even locate GTA02 when it's in NOR menu state. dfu-util -l says nothing, and dmesg has this: [20575.933963] usb 3-1.4: new full speed USB device using ehci_hcd and address 36 [20582.407633] usb 3-1.4: new full speed USB device using ehci_hcd and address 37 [20588.431796] usb 3-1.4: device descriptor read/64, error -110 [20595.195357] usb 3-1.4: device descriptor read/64, error -110 [20595.335909] usb 3-1.4: new full speed USB device using ehci_hcd and address 38 [20601.865524] usb 3-1.4: new full speed USB device using ehci_hcd and address 39 [20608.656191] usb 3-1.4: device descriptor read/64, error -110 [20616.763672] usb 3-1.4: device descriptor read/64, error -110 [20616.838742] usb 3-1.4: new full speed USB device using ehci_hcd and address 40 [20623.245361] usb 3-1.4: device descriptor read/64, error -110 [24031.580522] usb 3-1.4: new full speed USB device using ehci_hcd and address 41 [24038.054249] usb 3-1.4: new full speed USB device using ehci_hcd and address 42 [24044.080009] usb 3-1.4: device descriptor read/64, error -110 [24050.142505] usb 3-1.4: device descriptor read/64, error -110 [24050.214373] usb 3-1.4: new full speed USB device using ehci_hcd and address 43 [24066.486002] usb 3-1.4: new full speed USB device using ehci_hcd and address 44 and many other lines related to it, so I'm sure I'm bricked. DFU functionality disappeared right after I tried to take a snapshot of u-boot environment with dfu-util -a u-boot_env -R -U env.bin From: Andy Green [EMAIL PROTECTED] If it's a Freerunner, just hold down that corner AUX button when you power on, you should get into a backup NOR copy of U-Boot and can DFU new stuff in from there. If you still get errors, post your dfu-util commandline. I'm in NOR menu already (see above) and dfu-util says that it writes u-boot piece past memory. Now thanks God all I have is working FSO m4 from where I can do something with this situation. For the original problem, actually my first suspect would be physical connectivity to the fingers in the uSD connector. A guy before found he had to add some paper on top of the SIM to push down enough to make reliable contact. Recent kernels have a workaround in that starts the card at slower clock until the first bulk transfer completed successfully when it is cranked up to 16MHz, that seemed to make the previous problems with some cards pretty much go away. I'm glad to hear it. It may be a good idea to have a backup rock-solid bare copy of working firmware somewhere inside Neo to restore it in such cases, although that tempting Factory reset option may be exactly what I'm talking about. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
2008/11/24 Andy Green [EMAIL PROTECTED]: | dfu-util -a u-boot -R -D uImage-XX.bin Hum the -a u-boot or -a 1 tells it to put stuff in the U-Boot partition, it's the wrong one: uImage-blah.bin is a kernel image. To flash the kernel, you need to tell it -a kernel or -a 3. Ah yes, missed that, I write it by memory. To fix it you need to put a U-Boot image into the u-boot partition again. Why do you think it's bricked? The NOR menu comes up OK on LCM, right? DFU is absent, dfu-util -l finds no suitable device to work with, maybe because I damaged it when I changed environment in minicom console or I uploaded wrong image onto that. AUX+POW on the phone, menu appears, dfu-util -l on desktop, and no DFU device found. I know no other way of flashing new u-boot image without DFU protocol working, except Debug board which I haven't. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: I/O problems with SD card
2008/11/24 Andy Green [EMAIL PROTECTED]: |DFU is absent, dfu-util -l finds no suitable device to work with, | maybe because I damaged it when I changed environment in minicom | console or I uploaded wrong image onto that. AUX+POW on the phone, | menu appears, dfu-util -l on desktop, and no DFU device found. |I know no other way of flashing new u-boot image without DFU | protocol working, except Debug board which I haven't. I'm not sure what's happening to you, but your dmesg traffic would be pretty normal if you were entering and then leaving U-Boot... the connection would indeed timeout (-110) when we leave U-Boot and load the kernel / crash or whatever. If you hold down the AUX / corner key when you power up, you should come up in NOR U-Boot with a menu on the LCM. If that's true, you should have 30s to do the DFU you want to do before it times out. Yes, I know that, but I'm unable to connect to the phone through DFU protocol because Neo don't offer itself as a device supporting DFU. I have Neo plugged in to desktop throught USB cable. AUX+POW gives me NOR boot menu and at the same time Neo must be visible to desktop as DFU-capable device within next 30 seconds, but it's not. That's why I (may be erroneously) call myself bricked -- I can boot Neo with it's currently installed software (FSO m4) but I can't update it's NAND to anything else since the moment I damaged(?) u-boot. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
