Hi Venkat, I've got the same problem after upgrading BBB. Did you able to fix the problem finally, pls? Rgds.
Anisul On Sunday, May 12, 2013 2:51:09 AM UTC+10, Venkat Bommakanti wrote: > > Hi, > > I was able to install the > BBB-eMMC-flasher-2013.05.08.img.xz<http://www.google.com/url?q=http%3A%2F%2Fdominion.thruhere.net%2Fkoen%2Fangstrom%2Fbeaglebone%2FBBB-eMMC-flasher-2013.05.08.img.xz&sa=D&sntz=1&usg=AFQjCNGaBs_2lP26953TjXo1LqDXh4_1aw>image > fine via an uSD card. However, in an attempt to fetch some latest > python packages, when I ran the: > opkg update > opkg upgrade > while it was running, At the end of the process, I noticed the following > error summary: > ... > Collected errors: > * opkg_finalize_intercepts: Failed to open dir > /tmp/opkg-EJegmu/opkg-intercept-AmeBYC: No such file or directory. > * rm_r: Failed to open dir /tmp/opkg-EJegmu/opkg-intercept-AmeBYC: > No such file or directory. > root@bbb-01:~# > ... > > 'am wondering if it is an error with the installation (via setuptools ?) > of some python module it fetched. I have seen errors like this in past, > with race conditions during setuptools usage. setuptools (and possibly via > distutils) uses /tmp/ to unravel sources/eggs during the install process > and the error msg above refers to /tmp/. Hence the presumption. There are > no other clues. > > I could no longer boot the bbb in this errored out install. None of the > user LEDs would come on despite power being ON. Only recurse was to reflash > the pristine 05/08/13 image, and then things are fine > > So it appears, the above upgrade method is still not fully functional. > > /venkat > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
