Re: Kernel and Dual booting
To prevent opkg from upgrading the kernel try: opkg flag hold kernel-2.6.24 opkg flag hold kernel-image-2.6.24 Altho i think you only need to block the kernel-image-2.6.24 After getting a neo1973 kernel and a bad kernel that wouldnt boot from opkg, i do all my kernel upgrades with the dfu-util. Mikael Berthe wrote: * Olivier Berger [EMAIL PROTECTED] [2008-08-10 18:16 +0200]: Now I need to test if I can boot it on the SD. If it succeeds, I will then be able to flash OM 2008.8, and have switched between flash and SD. Dual booting is cool ;) Yes it is :) (Actually I'm running 2007 from flash and 2008.8 from SD, unlike you...) Yet I'm wondering if it isn't dangerous to do an opkg upgrade from the SD. Wouldn't that update the FR's kernel? If it does, then it could break booting from flash as the modules won't match anymore. Or is there a way to prevent opkg from flashing the kernel? It would be nice to upgrade /uImage.bin instead! -- MiKael ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- View this message in context: http://n2.nabble.com/Moving-my-2007.2-to-SD-to-try-2008.8-with-fallback-solution-tp682485p685836.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: full-keyboard for Om 2008.08?
Hmm figured out why my above fix was only working on my asu build and not my om2008.8 need to install http://buildhost.openmoko.org/daily-feed/armv4t/illume_0.0+svnr196-r12_armv4t.ipk this version seems to let me use whatever keyboard i like, which is how it should be. hope it doesnt magically disappear . . Dirk Bergstrom-2 wrote: DooD wrote: The files you need to edit are under /usr/lib/enlightenment/modules/illume/keyboards I believe there is a Full-QWERTY.kbd in there, just backup the Default.kbd and replace it with the Full-QWERTY.kbd mv Default.kbd Defaultbackup.kbd mv Full-QWERTY.kbd Default.kbd /etc/init.d/xserver-nodm restart I tried this, but I still get the standard keyboard. Somewhere along the line I installed the illume package with the 'qwerty' icon. Maybe that has something to do with this? Also, I see this interesting comment in Default.kbd: # if the key out is in quotes - q for example, then this key is used for # typing words and can be part of a dictionary match, any other key when # pressed will end the dictionary match (u can disable dictionary # matching in # a layout by not having any outputs in quotes) So, that implies that if I can just get the system to recognize alternate kbd files, I can turn off dictionary matching, which would make me rather happy. Hmmm, waitaminnit, looking at the files in that directory, I don't think they control the standard 2008.08 keyboard. I'm talking about the one where you flick up/down to shift to other layouts. Sigh. I guess I'm still stuck with the irritating keyboard. What's it called? -- Dirk Bergstrom [EMAIL PROTECTED] http://otisbean.com/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- View this message in context: http://n2.nabble.com/full-keyboard-for-Om-2008.08--tp681538p684042.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: full-keyboard for Om 2008.08?
The files you need to edit are under /usr/lib/enlightenment/modules/illume/keyboards I believe there is a Full-QWERTY.kbd in there, just backup the Default.kbd and replace it with the Full-QWERTY.kbd mv Default.kbd Defaultbackup.kbd mv Full-QWERTY.kbd Default.kbd /etc/init.d/xserver-nodm restart Some of the keys, arrows, return, tab, shift, backspace are invisible... not to hard to find them *hint* try holding your finger on the keyboard until it zooms in. Arne Zachlod wrote: Hello there! i like the new look of the freerunner, but what i don't like is the keyboard. is there a possibility to re-install a full qwerty KB or something like that? navigate in terminal with the standard-kb is terrible. thanks, Arne ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- View this message in context: http://n2.nabble.com/full-keyboard-for-Om-2008.08--tp681538p682407.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ASU - startup broken by upgrade?
I found that installing the newest e-wm and illume packages http://downloads.openmoko.org/openmoko-repository/ASU/armv4t/e-wm_0.16.999.042+cvs200807270730-r11_armv4t.ipk http://downloads.openmoko.org/openmoko-repository/ASU/armv4t/illume_0.0+svnr170-r7_armv4t.ipk caused this problem. when i reinstalled http://buildhost.openmoko.org/daily-feed/armv4t/e-wm_0.16.999.042+cvs20080722-r10_armv4t.ipk http://buildhost.openmoko.org/daily-feed/armv4t/illume_0.0+svnr152-r6_armv4t.ipk i was able to get xserver to run properly. only problem was if i had already used opkg to upgrade i could not get it to install the older packages Torfinn Ingolfsen wrote: Hello, It seems that today's 'opkg upgrade' broke the startup on my FreeRunner (I'm using ASU). /etc/init.d/rc complain that it can't find splash-write. Has anyone else seen this? Further investigation shows that it is a broken link now: [EMAIL PROTECTED]:~# which splash-write [EMAIL PROTECTED]:~# file /usr/bin/splash-write /usr/bin/splash-write: broken symbolic link to `/usr/bin/exquisite-write.sh' [EMAIL PROTECTED]:~# ll /usr/bin/splash-write /usr/bin/exquisite-write.sh ls: /usr/bin/exquisite-write.sh: No such file or directory lrwxrwxrwx1 root root 27 Jul 23 09:38 /usr/bin/splash-write - /usr/bin/exquisite-write.sh@ [EMAIL PROTECTED]:~# Perhaps it got changed: [EMAIL PROTECTED]:~# which exquisite-write /usr/bin/exquisite-write Ok, I'll fix the broken link so splash-write now points to exquisite-write. We'll see if that fixes everything. Nope, it didn't.. Seems the Xserevr doesn't tart up. Her is the contents of /tmp/x.log: -- [EMAIL PROTECTED]:~# more /tmp/x.log _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/om-gta02:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 (II) verbosity set to 5 Using GLAMO 3362 card (II) Screen: 16/16 depth/bpp (II) vram size:4194304, onscreen vram size:614400, offscreen vram size:3579904 (II) initialising offscreen pixmaps Extended Input Devices not yet supported. Impelement it at line 637 in kinput.c D-BUS per-session daemon address is: unix:abstract=/tmp/dbus-WqAYGaR9LT,guid=34e024cf41e115d377de317848900b44 [settings daemon] Forking. run with -n to prevent fork enlightenment: symbol lookup error: enlightenment: undefined symbol: ECORE_X_ATOM_E_VIRTUAL_KEYBOARD_STATE run-parts: /etc/X11/Xsession.d/90xXWindowManager exited with code 127 waiting for X server to shut down FreeFontPath: FPE built-ins refcount is 2, should be 1; fixing. Regards, Torfinn Ingolfsen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- View this message in context: http://n2.nabble.com/ASU---startup-broken-by-upgrade--tp660348p661836.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ASU, exposure doesn't work
Finally found how to get this one to work... the problem is with python-ecore package the newest one doesnt even seem to run camp wifi for me anymore. The version you want to install is from http://buildhost.automated.it/OM2007.2/packages/armv4t/python-ecore_0.2.1+cvs20080702-r1_armv4t.ipk If you cant get opkg to install it for you try -force-downgrade, which doesnt seem to work for me. so i just temporarily removed my armv4t-feed.conf from /etc/opkg, removed the package, then had opkg update and typed opkg install http://buildhost.automated.it/OM2007.2/packages/armv4t/python-ecore_0.2.1+cvs20080702-r1_armv4t.ipk This should work, goodluck Benedikt Schindler wrote: I am running ASU with a daily kernel and opkg-config from mwester. (kernel_2.6.24+git25+8533927964761f4e2078ccd8607b90f5acc60b93-r1_om-gta02.ipk) [EMAIL PROTECTED]:/# app-launcher.py exposure Can't connect to unix socket - starting daemon ... [EMAIL PROTECTED]:/# no more messages. nothing new in dmesg. nothing in /var/log/messages. does anyone know where to look for the problem? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- View this message in context: http://n2.nabble.com/ASU%2C-exposure-doesn%27t-work-tp661973p662542.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Flash ASU
Most of these instructions i have pulled off the wiki or from other e-mails, Do not hold me responsible if you brick your Freerunner while following them. Here is what has worked for me so far First you want to get the newest ASU rootfs from http://buildhost.openmoko.org/daily/freerunner/ The newest ASU rootfs for now is http://buildhost.openmoko.org/daily/freerunner/200807/20080722/Openmoko-openmoko-qtopia-x11-image-glibc-ipk-P1-Snapshot-20080722-om-gta02.rootfs.jffs2 After you have downloaded that you will want to go to http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner Following the instructions on the page download the dfu-util to the same directory as the rootfs.jffs2 http://downloads.openmoko.org/releases/Freerunner/dfu-util Now you will need to power down your Freerunner and power it into the NOR uBoot menu for flashing. (in short: press and hold aux then power) When the menu has come up attach the Freerunner to your host linux system via USB. *note* uBoot menu will not stay on for long, unless you scroll using the aux button Now open a terminal on the host linux system, go to the directory of your dfu-util and rootfs.jffs2,and run the command: *note* changing the name of the rootfs.jffs2 to whatever you downloaded ./dfu-util -a rootfs -R -D Openmoko-openmoko-qtopia-x11-image-glibc-ipk-P1-Snapshot-20080722-om-gta02.rootfs.jffs2 Let dfu-util run its magic, then you should be able to boot into the ASU. - Now if you installed the 200807022 ASU you will notice some problems, mainly that there is no keyboard! What you will need to do now is to opkg update and upgrade. Assuming your host linux system has internet you will want to follow the instructions in http://wiki.openmoko.org/wiki/USB_Networking On the host linux system commands ifconfig usb0 192.168.0.200 ssh [EMAIL PROTECTED] should allow you to connect to the phone. -- If you do not know how to use the vi editor on the Freerunner you may not be able to do this next part Also read the notes before updating your .conf files Once you have your phone connected to the internet you will want to change your opkg feeds. Manually you can just goto /etc/opkg and use vi *.conf, or you can download updated .confs from http://www.mikeasoft.com/~mike/opkg-asu.tar.gz On the phone just cd /etc and type wget http://www.mikeasoft.com/~mike/opkg-asu.tar.gz; followed by tar xzf opkg-asu* This will extract the *.conf files to /etc/opkg. *IMPORTANT NOTE1* If you change the neo1973-feed.conf to http://downloads.openmoko.org/openmoko-repository/ASU/neo1973, opkg will download a kernel for the neo1973 onto your freerunner, while it wont stop the phone from working it may stop the phone from having sound. *IMPORTANT NOTE2* The newest e-wm and illume packages do not seem to work, opkg upgrade may stop you from being able to boot into the ASU, tho you can still connect to it with ssh. For now i would recommend pointing /etc/opkg/armv4t.conf to http://buildhost.openmoko.org/daily-feed/armv4t and rerun opkg update before running opkg upgrade. *IMPORTANT NOTE3* opkg install http://buildhost.openmoko.org/daily-feed/om-gta02//kernel-image-2.6.24_2.6.24+git25+8533927964761f4e2078ccd8607b90f5acc60b93-r0_om-gta02.ipk does not seem to flash the kernel correctly and will cause the system to hang right as you power up your phone. you will need to reflash your kernel in order to be able to boot again. --- To get a keyboard working, and hopefully not kill your phone, try installing the above *.conf files, but before running opkg update or upgrade : rm /etc/opkg/om-gta02-d* echo src/gz daily-neo1973 http://buildhost.openmoko.org/daily-feed/neo1973; /etc/opkg/neo* echo src/gz daily-armv4t http://buildhost.openmoko.org/daily-feed/armv4t; /etc/opkg/arm* opkg install http://downloads.openmoko.org/openmoko-repository/ASU/armv4t/app-restarter_1.0+svn4552-r0_armv4t.ipk Now run opkg update, followed by opkg upgrade. Reboot your Freerunner and so long as you boot into the ASU you should be able to use the keyboard in Qtopia apps -- If you are going to be installing GTK apps, such as opkg install openmoko-terminal2 you will want to be able to use the keyboard, either you can have the keyboard automatically popup by installing matchbox-keyboard-im*.ipk, or you can install a theme with the qwerty button. To have the keyboard automagically popup cd /tmp mkdir matchbox-keyboard cd matchbox-keyboard wget http://www.ginguppin.de/files/keyboard-ipk.tar.bz2 tar -jxf keyboard-ipk.tar.bz2 opkg install matchbox-keyboard-im*.ipk cd .. rm -rf matchbox-keyboard *note* it will extract 3 files, you only need to install matchbox-keyboard-im*.ipk The other packages may completely replace the keyboard...
