People,
I have not used my FreeRunner for ages and probably should donate it
someone who can make use of it but a thought occurred to me: It would
be good to have something that could act like a SMS server eg I have a
demand where if an (urgent) email comes into a particular account, that
On Sat, Dec 21, 2013 at 12:34 PM, Ed Kapitein e...@kapitein.org wrote:
Hi Phil,
I did the same thing, but It is of limited use, a lot of mail is in HTML
format and hard to convert to SMS.
Also, you need to strip the headers etc.
So you might want to write a script first and run it on
On Sat 21 December 2013 12:34:49 Ed Kapitein wrote:
On 12/21/2013 11:58 AM, Philip Rhoades wrote:
People,
I have not used my FreeRunner for ages and probably should donate it
someone who can make use of it but a thought occurred to me: It would
be good to have something that could act
hi,
i just did apt-get dist-upgrade and the install went fine. but now
qtmoko get's stuck in the boot process at no more processes left in
this runlevel. I can still ssh into the system, but don't know where to
go from there to fix it if it is fixable. so if you have any suggestions
on how to
On Saturday, December 21, 2013 06:23:09 PM robin wrote:
hi,
i just did apt-get dist-upgrade and the install went fine. but now
qtmoko get's stuck in the boot process at no more processes left in
this runlevel. I can still ssh into the system, but don't know where to
go from there to fix it
many thanks for the advice:
this is what I am getting:
root@neo:~# /etc/init.d/qtmoko-neo stop
root@neo:~# . /opt/qtmoko/qpe.env
root@neo:/root# qpe
NeoKbdDriverPlugin:create()
Before call NeoKbdHandler()
56788 0
writeFile failed /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-
On Saturday, December 21, 2013 08:07:38 PM robin wrote:
many thanks for the advice:
this is what I am getting:
root@neo:~# /etc/init.d/qtmoko-neo stop
root@neo:~# . /opt/qtmoko/qpe.env
root@neo:/root# qpe
NeoKbdDriverPlugin:create()
Before call NeoKbdHandler()
56788 0
writeFile
so apparently there is something wrong:
# uname -r
gives
# 2.6.34-qtmoko-v55
so I got your kernel:
# wget http://qtmoko.sourceforge.net/debian/gta02/armel/linux-image-2.6.39-
qtmoko-gta02_58-1_armel.deb
and installed it:
# dpkg -i linux-image-2.6.39-qtmoko-gta02_58-1_armel.deb
but I still have
On Saturday, December 21, 2013 08:51:04 PM robin wrote:
so apparently there is something wrong:
# uname -r
gives
# 2.6.34-qtmoko-v55
so I got your kernel:
# wget http://qtmoko.sourceforge.net/debian/gta02/armel/linux-image-2.6.39-
qtmoko-gta02_58-1_armel.deb
and installed it:
# dpkg -i
booting in my case is from SD-Card.
so how do I manage to have the right kernel being used?
br
robin
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
I think you have to check the symbolic link /boot/uImage.bin
it seems to point to the old kernel -v55 so you should remove it and
make it point to -v58.
Le samedi 21 décembre 2013 à 20:58 +, robin a écrit :
booting in my case is from SD-Card.
so how do I manage to have the right kernel
thanks adrien,
now I am a step further:
#uname -r
2.6.39-qtmoko-v58
and if I do:
root@neo:/boot# ls -l
total 5300
-rw-r--r-- 1 root root 866858 Mar 22 2013 System.map-2.6.34-qtmoko-v55
-rw-r--r-- 1 root root 790690 Nov 29 16:28 System.map-2.6.39-qtmoko-v58
-rw-r--r-- 1 root root 33 Mar
hi radek,
I went back to your previous reply and issued the commands that you
suggested. now this is the output with the newer kernel loaded:
root@neo:~# . /opt/qtmoko/qpe.env
root@neo:/root# qpe
NeoKbdDriverPlugin:create()
Before call NeoKbdHandler()
Cannot open input device for Headset Jack
13 matches
Mail list logo
