Re: [Shr-User] opkg upgrade fail and can't boot FR to desktop
On Thu, 2009-05-21 at 13:02 +1200, Robin Paulson wrote: 2009/5/21 Daniel.Li lida_m...@163.com: I've just done sed -i 's/testing/unstable/g' /etc/opkg/* opkg update;opkg upgrade and now I'm getting this too... I can still get in via ssh. It look as though e is missing a library: $ enlightenment_start.oe Enlightenment : using user default E - PID=1530, do_precache=0 /usr/bin/enlightenment: error while loading shared libraries: libecore_evas-ver-pre-01.so.0: cannot open shared object file: No such file or directory Add SHR mail list I remove .e folder, and have another lib missing. $ enlightenment_start.oe E - PID=1662, do_precache=0 /usr/bin/enlightenment: error while loading shared libraries: libecore_evas.so.0: cannot open shared object file: No such file or directory this was a major bug with the new naming scheme in e - there's argument as to whether shr caused the problem, or enlightenment did; i won't comment either way. apparently it's been fixed now, although at the time a few of us hacked it by creating symlinks from libecore_evas.so to libecore_evas-ver-pre-01.so (or vice versa, i can't remember). this was criticised as being very hacky, but there you go I upgrade just a few minutes before send this mail and tried below without luck. How can I solve the problem? Anyone helps? ln -s /usr/lib/libecore_evas-ver-pre-svn-01.so.0 libecore_evas.so.0 ln -s /usr/lib/libecore_fb-ver-pre-svn-01.so.0 libecore_fb.so.0 ln -s /usr/lib/libecore_x-ver-pre-svn-01.so.0 libecore_x.so.0 ln -s /usr/lib/libecore_txt-ver-pre-svn-01.so.0 libecore_txt.so.0 ln -s /usr/lib/libecore_input-ver-pre-svn-01.so.0 libecore_input.so.0 ln -s /usr/lib/libecore_ipc-ver-pre-svn-01.so.0 libecore_ipc.so.0 ln -s /usr/lib/libedje-ver-pre-svn-01.so.0 libedje.so.0 ln -s /usr/lib/libembryo-ver-pre-svn-01.so.0 libembryo.so.0 ln -s /usr/lib/libecore_job-ver-pre-svn-01.so.0 libecore_job.so.0 ln -s /usr/lib/libecore_job-ver-pre-svn-01.so.0 libecore_job.so.0 ln -s /usr/lib/libecore_file-ver-pre-svn-01.so.0 libecore_file.so.0 ln -s /usr/lib/libecore_con-ver-pre-svn-01.so.0 libecore_con.so.0 ln -s /usr/lib/libehal-ver-pre-svn-01.so.0 libehal.so.0 ln -s /usr/lib/libedbus-ver-pre-svn-01.so.0 libedbus.so.0 ln -s /usr/lib/libecore_imf_evas-ver-pre-svn-01.so.0 libecore_imf_evas.so.0 ln -s /usr/lib/libecore_imf-ver-pre-svn-01.so.0 libecore_imf.so.0 ln -s /usr/lib/libevas-ver-pre-svn-01.so.0 libevas.so.0 ln -s /usr/lib/libecore-ver-pre-svn-01.so.0 libecore.so.0 ln -s /usr/lib/libeina-ver-pre-svn-01.so.0 libeina.so.0 $ enlightenment_start.oe E - PID=1786, do_precache=0 ESTART: 0.00026 [0.00026] - begin ESTART: 0.01106 [0.01080] - signals done ESTART: 0.02173 [0.01067] - determine prefix e_prefix_determine() DYNAMIC DETERMINED PREFIX: /usr ESTART: 0.04540 [0.02367] - prefix done ESTART: 0.04708 [0.00168] - eina init ESTART: 0.08354 [0.03646] - intl init ESTART: 0.09212 [0.00858] - parse args ESTART: 0.09747 [0.00535] - arg parse done ESTART: 0.09825 [0.00078] - ecore init ESTART: 0.12793 [0.02968] - ecore_file init ESTART: 0.13390 [0.00597] - more ecore ESTART: 0.13488 [0.00098] - x connect Enlightenment Error Enlightenment cannot initialize its X connection. Have you set your DISPLAY variable? E17: Begin shutdown procedure! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Daniel.Li lida_m...@163.com PALFocus (http://palfocus.oicp.net) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-User] opkg upgrade fail and can't boot FR to desktop
2009/5/22 Daniel.Li lida_m...@163.com: ln -s /usr/lib/libecore_evas-ver-pre-svn-01.so.0 libecore_evas.so.0 ln -s /usr/lib/libecore_fb-ver-pre-svn-01.so.0 libecore_fb.so.0 ln -s /usr/lib/libecore_x-ver-pre-svn-01.so.0 libecore_x.so.0 ln -s /usr/lib/libecore_txt-ver-pre-svn-01.so.0 libecore_txt.so.0 ln -s /usr/lib/libecore_input-ver-pre-svn-01.so.0 libecore_input.so.0 ln -s /usr/lib/libecore_ipc-ver-pre-svn-01.so.0 libecore_ipc.so.0 ln -s /usr/lib/libedje-ver-pre-svn-01.so.0 libedje.so.0 ln -s /usr/lib/libembryo-ver-pre-svn-01.so.0 libembryo.so.0 ln -s /usr/lib/libecore_job-ver-pre-svn-01.so.0 libecore_job.so.0 ln -s /usr/lib/libecore_job-ver-pre-svn-01.so.0 libecore_job.so.0 ln -s /usr/lib/libecore_file-ver-pre-svn-01.so.0 libecore_file.so.0 ln -s /usr/lib/libecore_con-ver-pre-svn-01.so.0 libecore_con.so.0 ln -s /usr/lib/libehal-ver-pre-svn-01.so.0 libehal.so.0 ln -s /usr/lib/libedbus-ver-pre-svn-01.so.0 libedbus.so.0 ln -s /usr/lib/libecore_imf_evas-ver-pre-svn-01.so.0 libecore_imf_evas.so.0 ln -s /usr/lib/libecore_imf-ver-pre-svn-01.so.0 libecore_imf.so.0 ln -s /usr/lib/libevas-ver-pre-svn-01.so.0 libevas.so.0 ln -s /usr/lib/libecore-ver-pre-svn-01.so.0 libecore.so.0 ln -s /usr/lib/libeina-ver-pre-svn-01.so.0 libeina.so.0 $ enlightenment_start.oe E - PID=1786, do_precache=0 ESTART: 0.00026 [0.00026] - begin ESTART: 0.01106 [0.01080] - signals done ESTART: 0.02173 [0.01067] - determine prefix e_prefix_determine() DYNAMIC DETERMINED PREFIX: /usr ESTART: 0.04540 [0.02367] - prefix done ESTART: 0.04708 [0.00168] - eina init ESTART: 0.08354 [0.03646] - intl init ESTART: 0.09212 [0.00858] - parse args ESTART: 0.09747 [0.00535] - arg parse done ESTART: 0.09825 [0.00078] - ecore init ESTART: 0.12793 [0.02968] - ecore_file init ESTART: 0.13390 [0.00597] - more ecore ESTART: 0.13488 [0.00098] - x connect have you tried a more recent version of shr? they may have fixed this by now if not, there are more e libraries (possibly also misnamed), in sub-dirs of /usr/lib/evas/ i'm not confident this is related to your problem though; i don't recognise the error messages you're geting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-User] opkg upgrade fail and can't boot FR to desktop
On Fri, 2009-05-22 at 00:26 +1200, Robin Paulson wrote: have you tried a more recent version of shr? they may have fixed this by now What version do u suggest, I'm using 0427-unstable. Recent version of SHR, do u mean shr-testing? And I have found there are some problems in latest shr-testing version. As I know, 05XX (sorry I don't remember it) has a 1 pixel shutdown menu issue. Is it solved? if not, there are more e libraries (possibly also misnamed), in sub-dirs of /usr/lib/evas/ i'm not confident this is related to your problem though; i don't recognise the error messages you're geting I hope NOT to re-flash the device. Anyway, if there is really no way to go. OK, just re-flash it :( -- Daniel.Li lida_m...@163.com PALFocus (http://palfocus.oicp.net) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-User] opkg upgrade fail and can't boot FR to desktop
2009/5/22 Daniel.Li lida_m...@163.com: What version do u suggest, I'm using 0427-unstable. Recent version of SHR, do u mean shr-testing? err, i'd suggest om2009, actually. shr (stable hybrid release, apparently...) got to be far too annoying. the newest version of -unstable might have fixed these bugs, but it might have introduced more as well have you tried running opkg upgrade again? And I have found there are some problems in latest shr-testing version. As I know, 05XX (sorry I don't remember it) has a 1 pixel shutdown menu issue. Is it solved? nope, not in -testing. more issues with e and i couldn't get a connection to my phone network are you subscribed to the shr list, they might have better ideas what's happening? if not, there are more e libraries (possibly also misnamed), in sub-dirs of /usr/lib/evas/ i'm not confident this is related to your problem though; i don't recognise the error messages you're geting I hope NOT to re-flash the device. Anyway, if there is really no way to go. OK, just re-flash it :( ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
opkg upgrade fail and can't boot FR to desktop
Dear List, I just run opkg update and opkg upgrade a few minutes before. And when I shutdown FR and boot it again, it can't boot to desktop. It shows btusb_intr_complete: hci0 urb c7020b20 failed to resubmit (19) btusb_send_frame: hci0 urb c7020b20 submission failed How can I solve the problem? -- Daniel.Li lida_m...@163.com PALFocus (http://palfocus.oicp.net) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: opkg upgrade fail and can't boot FR to desktop
I just run opkg update and opkg upgrade a few minutes before. And when I shutdown FR and boot it again, it can't boot to desktop. any chance, you did that with usb cable still plugged in? in the rare cases, i reboot with the usb plugged in, the boot fails with a black screen with a bit of backlighting. It shows btusb_intr_complete: hci0 urb c7020b20 failed to resubmit (19) btusb_send_frame: hci0 urb c7020b20 submission failed looks rather like bluetooth stuff. is bt connected via usb internally? anyway, i rather doubt it has something to do with your problem. - what was upgraded? maybe the kernel and now modules don't match or vice versa? - did you shut down totally, removed the battery and started again? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: opkg upgrade fail and can't boot FR to desktop
On Wed, 2009-05-20 at 11:53 +0200, arne anka wrote: I just run opkg update and opkg upgrade a few minutes before. And when I shutdown FR and boot it again, it can't boot to desktop. any chance, you did that with usb cable still plugged in? usb is not connected in the rare cases, i reboot with the usb plugged in, the boot fails with a black screen with a bit of backlighting. I reboot again with usb connect, still can't boot to desktop with the same error. It shows btusb_intr_complete: hci0 urb c7020b20 failed to resubmit (19) btusb_send_frame: hci0 urb c7020b20 submission failed looks rather like bluetooth stuff. is bt connected via usb internally? I never used BT, even didn't have BT device. anyway, i rather doubt it has something to do with your problem. Really? - what was upgraded? maybe the kernel and now modules don't match or vice versa? Humm... So what module (file) or kernel should I use. - did you shut down totally, removed the battery and started again? Yes. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Daniel.Li lida_m...@163.com PALFocus (http://palfocus.oicp.net) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: opkg upgrade fail and can't boot FR to desktop
2009/5/20 Daniel.Li lida_m...@163.com: It shows btusb_intr_complete: hci0 urb c7020b20 failed to resubmit (19) btusb_send_frame: hci0 urb c7020b20 submission failed how far booted is it? can you connect over ssh? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: opkg upgrade fail and can't boot FR to desktop
On Wed, 2009-05-20 at 23:01 +1200, Robin Paulson wrote: 2009/5/20 Daniel.Li lida_m...@163.com: It shows btusb_intr_complete: hci0 urb c7020b20 failed to resubmit (19) btusb_send_frame: hci0 urb c7020b20 submission failed how far booted is it? can you connect over ssh? Humm... I can login ssh via usb cable. :) But I don't know what's wrong and where to start to find problem? :( -- Daniel.Li lida_m...@163.com PALFocus (http://palfocus.oicp.net) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: opkg upgrade fail and can't boot FR to desktop
It shows btusb_intr_complete: hci0 urb c7020b20 failed to resubmit (19) btusb_send_frame: hci0 urb c7020b20 submission failed looks rather like bluetooth stuff. is bt connected via usb internally? I never used BT, even didn't have BT device. still, the fr has bt and its drivers are included. - what was upgraded? maybe the kernel and now modules don't match or vice versa? Humm... So what module (file) or kernel should I use. that was a quick idea -- as long as we don't know if kernel/modules were upgraded at all, nobody can't tell anything. when did you upgrade the last time before that? and, most important, what distribution are you using? (_always_ prefix mail's subject!) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: opkg upgrade fail and can't boot FR to desktop
On Wed, 2009-05-20 at 13:07 +0200, arne anka wrote: - what was upgraded? maybe the kernel and now modules don't match or vice versa? Humm... So what module (file) or kernel should I use. that was a quick idea -- as long as we don't know if kernel/modules were upgraded at all, nobody can't tell anything. when did you upgrade the last time before that? I flashed FR and didn't upgrade before this afternoon. I have run opkg list_upgradable, and found there are lots of stuff wait upgrading. so I just opkg upgrade. and, most important, what distribution are you using? (_always_ prefix mail's subject!) openmoko-shr-image-glibc-ipk--20090427-om-gta02.rootfs.tar.gz -- Daniel.Li lida_m...@163.com PALFocus (http://palfocus.oicp.net) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[shr] Re: opkg upgrade fail and can't boot FR to desktop
and, most important, what distribution are you using? (_always_ prefix mail's subject!) openmoko-shr-image-glibc-ipk--20090427-om-gta02.rootfs.tar.gz you could have added that to the subject already! it really increases the chance of shr users seeing that and responding! when you can log in via usb, your system at least basically works, first step would be to check, if just X has issues. - look for log files regarding X, in a common linux installation that would be in /var/log/X.org.*.log - check with logread or what tool allows access to in-memory logs - start X manually, probably with startx ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
opkg upgrade fail and can't boot FR to desktop
On Wed, 2009-05-20 at 22:10 +0200, Jeffrey Ratcliffe wrote: 2009/5/20 Daniel.Li lida_m...@163.com: I just run opkg update and opkg upgrade a few minutes before. And when I shutdown FR and boot it again, it can't boot to desktop. It shows btusb_intr_complete: hci0 urb c7020b20 failed to resubmit (19) btusb_send_frame: hci0 urb c7020b20 submission failed I've just done sed -i 's/testing/unstable/g' /etc/opkg/* opkg update;opkg upgrade and now I'm getting this too... I can still get in via ssh. It look as though e is missing a library: $ enlightenment_start.oe Enlightenment : using user default E - PID=1530, do_precache=0 /usr/bin/enlightenment: error while loading shared libraries: libecore_evas-ver-pre-01.so.0: cannot open shared object file: No such file or directory Add SHR mail list I remove .e folder, and have another lib missing. $ enlightenment_start.oe E - PID=1662, do_precache=0 /usr/bin/enlightenment: error while loading shared libraries: libecore_evas.so.0: cannot open shared object file: No such file or directory Regards Jeff ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Daniel.Li lida_m...@163.com PALFocus (http://palfocus.oicp.net) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-User] opkg upgrade fail and can't boot FR to desktop
2009/5/21 Daniel.Li lida_m...@163.com: I've just done sed -i 's/testing/unstable/g' /etc/opkg/* opkg update;opkg upgrade and now I'm getting this too... I can still get in via ssh. It look as though e is missing a library: $ enlightenment_start.oe Enlightenment : using user default E - PID=1530, do_precache=0 /usr/bin/enlightenment: error while loading shared libraries: libecore_evas-ver-pre-01.so.0: cannot open shared object file: No such file or directory Add SHR mail list I remove .e folder, and have another lib missing. $ enlightenment_start.oe E - PID=1662, do_precache=0 /usr/bin/enlightenment: error while loading shared libraries: libecore_evas.so.0: cannot open shared object file: No such file or directory this was a major bug with the new naming scheme in e - there's argument as to whether shr caused the problem, or enlightenment did; i won't comment either way. apparently it's been fixed now, although at the time a few of us hacked it by creating symlinks from libecore_evas.so to libecore_evas-ver-pre-01.so (or vice versa, i can't remember). this was criticised as being very hacky, but there you go ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community