that solved the issue!
many thanks,
best regards
robin
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
On Sunday, December 22, 2013 08:11:47 AM robin wrote:
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
the directory is there:
#ls
2.6.34-qtmoko-v55 2.6.39-qtmoko-v58
# depmod
# reboot
did not work so I had a look at depmod and thought that the -a option might
be what I need, that though expect something lice /etc/modules.conf which
did not find, but I find /etc/modules: so I did this:
# cat
doing lsmod I get the following if that is of any help
root@neo:~# lsmod
Module Size Used by
ipt_REJECT 1943 1
iptable_filter 958 1
ip_tables 9486 1 iptable_filter
ip6t_REJECT 2294 1
xt_tcpudp 1921 2
On Sunday, December 22, 2013 08:05:25 PM robin wrote:
# cat /etc/modules
g_ether
ppp_generic
joydev
bq27000_battery
This is not correct. From rootfs docs it should be:
echo g_ether /etc/modules
echo ppp_generic /etc/modules
echo bq27x00_battery /etc/modules
echo ohci_hcd /etc/modules
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
15 matches
Mail list logo
