dfu-util refusing to flash correct qi image
Hi everyone, I'm trying to flash qi on my freerunner. I first tried the s3c6410 file, I thought that was the standard in all the freerunners. When *nothing* happened with that one I looked through my dmesg: s3c2410-ohci s3c2410-ohci: S3C24XX OHCI s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1 s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x4900 So, I tried the s3c2410 qi image, but then dfu-util says it's not meant for this device. Anyhow, no matter what qi image I try, nothing works. The kernel doesn't boot (and, yes, it's in the /boot folder), and I get NO blinking leds. Greetings, Jelle De Loecker ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: dfu-util refusing to flash correct qi image
Op zaterdag 06-12-2008 om 17:04 uur [tijdzone -0500], schreef Joel Newkirk: On Sat, 06 Dec 2008 22:24:44 +0100, Jelle De Loecker [EMAIL PROTECTED] wrote: Hi everyone, I'm trying to flash qi on my freerunner. I first tried the s3c6410 file, I thought that was the standard in all the freerunners. When *nothing* happened with that one I looked through my dmesg: s3c2410-ohci s3c2410-ohci: S3C24XX OHCI s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1 s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x4900 So, I tried the s3c2410 qi image, but then dfu-util says it's not meant for this device. Anyhow, no matter what qi image I try, nothing works. The kernel doesn't boot (and, yes, it's in the /boot folder), and I get NO blinking leds. Greetings, Jelle De Loecker Still one left to try, though: qi-s3c2442-master_2ad3ce6ff57753e3.udfu... ;) I'm using qi-s3c2442-andy_0d3272a8a81dab25.udfu (nov25) on my FR right now. :) j That did it, allright. I never thought to try it, since the instructions said to check the dmesg (which told me to use qi-s3c2410-master_2ad3ce6ff57753e3.udfu) or to use the 6410 image... Mystery solved, thanks. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Debian freezes
Sascha Wessel schreef: Hi, On Tue, Dec 02, 2008 at 08:09:21AM +0100, Jelle De Loecker wrote: From time to time, when I'm downloading certain files through apt-get, svn or cvs, or when I'm trying to compile something directly on my freerunner, it would just lock up. Freeze completely. I have to take out the batteries and restart the phone again. Unfortunately, when compiling the shr applications, it always starts from the beginning. So I can't resume a compile after one of these freezes. I haven't enabled the freerunner to go auto-standby. I had the same problem some time ago: after some i/o intensive tasks all fork/clone calls failed (reproducible). Since then I'm just running another kernel (not from the official debian repository) and I never saw the issue again... Greetings, Sascha What kernel ARE you using, then? Did you just compile one from source or ... ? Greetings, Jelle De Loecker ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Debian freezes
Hello everyone, From time to time, when I'm downloading certain files through apt-get, svn or cvs, or when I'm trying to compile something directly on my freerunner, it would just lock up. Freeze completely. I have to take out the batteries and restart the phone again. Unfortunately, when compiling the shr applications, it always starts from the beginning. So I can't resume a compile after one of these freezes. I haven't enabled the freerunner to go auto-standby. Greetings, Jelle De Loecker ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[DEBIAN] /tmp /var are too small
Hi everyone, I can't believe how fun it is to run Debian on the Freerunner, it's really working like a charm. I have one problem though: my tmpfs partitions are too small. They're all capped at 62 MiBs. Where does tmpfs come from? Is there a way to make it bigger? # df -h FilesystemSize Used Avail Use% Mounted on rootfs1.9G 415M 1.4G 24% / tmpfs 62M 0 62M 0% /lib/init/rw udev 10M 64K 10M 1% /dev tmpfs 62M 4.0K 62M 1% /dev/shm /dev/mmcblk0p17.5M 3.5M 3.6M 49% /boot tmpfs 62M 16K 62M 1% /tmp tmpfs 62M 0 62M 0% /var/lock tmpfs 62M 36K 62M 1% /var/run Greetings, Jelle De Loecker ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia: 4.3.3 too sloooooow
Lorn Potter schreef: Joerg Lippmann wrote: Hi! I tried something: I deleted (renamed) my root-directory. Now the 4.3.3-Version seems to be snappy as ever. Now what files caused the neo to be confused? My root-home had some MP3s, some JPGs, some OSM-Maps and several settings- and applications-directories. Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card. You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way. Qtopia scans your home partition when it boots. (I thought it did this for its media player or something) It's very annoying, I also have lots of OSM maps on my SD card. You can turn it off by doing this. Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf And change the [MountPoint0] section so it resembles this: -[ [MountPoint0] Name[] = SD Card Path=/dev/mmcblk0p1 Removable = 0 Applications = 0 Documents = 0 ContentDatabase = 0 ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
OM 2008.8 (With Zecke's feed) No dim, only screensaver
Hi everyone, instead of dimming my phone starts the X screensaver, which isn't very economical for my battery. Does anyone know how I can get the dimming back to work? I can't let it suspend because I need to charge my battery, obviously Kind regards, Jelle De Loecker ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Export data or true upgrade?
Hi everyone, Is there a way to export my data (sms messages, contacts, ...) so that I can flash the new ASU image without losing all my data again? Or is there a way to upgrade the installation through opkg? Thank you for your patience, Jelle De Loecker ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: preserving illume keyboard on update
Interesting! But who is openmoko? What group of persons decide this? And surely they must know about this? If not, and you want me to vent my frustration with the qpe keyboard somewhere else, just give me an address! I've made a list! :) I just hope this doesn't turn into something like the gimp-in-one-window struggle... Here's hoping for a good solution! Carsten Haitzler (The Rasterman) schreef: On Sun, 24 Aug 2008 01:53:47 +0200 Jelle De Loecker [EMAIL PROTECTED] babbled: the whole keyboard thing is a mess right now. illume has one - that seemingly people want. qpe has one that om wants. illume provides a gui config to turn it's keyboard on and off or launch a 3rd party vkbd app and use that. this gui is turned off by om and pretty much permanently inaccessible. qpe doesn't provide any way to say yes or no to getting its keyboard up. so basically qpe is playing the game of take my keyboard or dont use qpe right now, and illume is playing the game of do what you want - i have config for that, but that game is pretty much inaccessible. there is a dbus call you can use to fiddle with some config but that incantation needs a dbus session key (so you'll need to steal it from a running session or do this with a terminal on the FR itself), but this still will only affect illume and do nothing about qpe. this all needs to be resolved and so it'll be a mess until it's cleared up. the wiki is not really correct - it's well behind any development and it's not really understanding how the keyboard works, but that has been changing rapidly ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: preserving illume keyboard on update
There is a script on the wiki which enables you to install the full qwerty keyboard, unfortunately the last file gives a 404, which makes it rather useless. Is there a way, other then recompiling it, to get the good keyboard back? How does one get a dictionary for their own language, anyway? Or how do you get an Azerty keyboard? /Met vriendelijke groeten,/ *Jelle De Loecker* Kipdola Studios - Tomberg Russell Sears schreef: VictorSigma wrote: I currently have the 20080823 openmoko-qtopia-x11-image-om-gta02.jffs2 image flashed on my freerunner and it is working great. The problem is that it originally comes with the illume keyboard pre-installed but whenever I 'opkg update' the keyboard is changed to the qtopia version. Is there anyway to preserve the illume keyboard or reinstall it after the update? thanks rasterman explained this already. qpe (the monolithic binary blob that makes phone calls) is hardcoded to start up its own keyboard. If qpe registers its keyboard first, then you don't get the illume one anymore. I think the fix is to break disable the qpe keyboard somehow. I've tried breaking it's config file, but that crashes qpe, breaking phone calls... I got a bit further than that, and think I found the code (51% sure...) that turns the qpe keyboard on, but now I don't have time to deal with it anymore. If you time to mess with it, consider rebuilding qpe with this patch removed: http://git.openmoko.org/?p=qtopia.git;a=commit;h=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04 the diff: http://git.openmoko.org/?p=qtopia.git;a=blobdiff;f=src/server/phone/serverinterface/phonelauncher/phonelauncher_illume.cpp;h=405a0b654e9c34a390d18e3466242de5de1cc53d;hp=623258b15a27a969dd8a0926884792936f41103b;hb=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04;hpb=38d2a3923ef46b12279901e5a5dc4c84aeae5d6e A better approach would add a config option to turn qpe's keyboard off. The long-term goal is to replace it with the illume one, but OM will be supporting the qpe keyboard in the near-term... -Rusty ___ 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
Latest ASU image TangoGPS
Hi everyone, I got my FreeRunner today, I love the device already! I immediately upgraded to the ASU (since I saw no point in playing around with a deprecated software stack, even if it does work better) but for some reason TangoGPS doesn't work in it! Most buttons don't work (Map/Trip/...) the screen is useless, ... I went for the latest image from the 20th of august (since the last stable release couldn't receive SMS messages, which is quite important in a cell phone) Is anyone else having these problems with it? -- /Met vriendelijke groeten,/ *Jelle De Loecker* Kipdola Studios - Tomberg ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
