2 BBB do not boot after opkg update and upgrade

GoogleGroups
1

Once again, no reboot after opkg upgrade

My BBB was working fine in 3.8.8, but I had a problem in installing easy_install. As I saw that the kernel has
already upgraded to 3.8.11, I tried again the upgrade through opkg update and opkg upgrade.

Things went fine, but maybe I did an error in asking for opkg upgrade again.

I then got

root@beaglebone:~# opkg upgrade
Upgrading kernel-module-openvswitch on root from 3.8.8-r23a.0 to 3.8.11-r23a.0…
Downloading http://feeds.angstrom-distribution.org/feeds/v2012.12/ipk/eglibc/armv7a-vfp-neon/machine/beaglebone/kernel-module-openvswitch_3.8.11-r23a.0_beaglebone.ipk.
Removing obsolete file /lib/modules/3.8.8/kernel/net/openvswitch/openvswitch.ko.
Upgrading kernel-module-bone-iio-helper on root from 3.8.8-r23a.0 to 3.8.10-r23a.1…
Downloading http://feeds.angstrom-distribution.org/feeds/v2012.12/ipk/eglibc/armv7a-vfp-neon/machine/beaglebone/kernel-module-bone-iio-helper_3.8.10-r23a.1_beaglebone.ipk.
Removing obsolete file /lib/modules/3.8.8/kernel/drivers/misc/cape/beaglebone/bone-iio-helper.ko.
Upgrading kernel-modules on root from 3.8.8-r23a.0 to 3.8.11-r23a.0…
Downloading http://feeds.angstrom-distribution.org/feeds/v2012.12/ipk/eglibc/armv7a-vfp-neon/machine/beaglebone/kernel-modules_3.8.11-r23a.0_beaglebone.ipk.
Installing kernel-devicetrees (3.8.11-r23a.0) to root…
Downloading http://feeds.angstrom-distribution.org/feeds/v2012.12/ipk/eglibc/armv7a-vfp-neon/machine/beaglebone/kernel-devicetrees_3.8.11-r23a.0_beaglebone.ipk.
Configuring kernel-module-openvswitch.
Configuring kernel-module-bone-iio-helper.
Configuring bonescript.
Job for bonescript.socket failed. See ‘systemctl status bonescript.socket’ and ‘journalctl -xn’ for details.
WARNING: could not open /lib/modules/3.8.10/modules.order: No such file or directory
WARNING: could not open /lib/modules/3.8.10/modules.builtin: No such file or directory
WARNING: could not open /lib/modules/3.8.11/modules.order: No such file or directory
WARNING: could not open /lib/modules/3.8.11/modules.builtin: No such file or directory
Collected errors:

  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/am335x-evmsk.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/omap3-beagle-xm.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/am335x-boneblack.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/omap3-tobi.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/am335x-bone.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/omap5-evm.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/omap4-panda.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/omap4-var-som.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/am335x-evm.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/omap3-beagle.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/omap3-evm.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/omap4-sdp.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/omap4-panda-es.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/omap4-panda-a4.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/am335x-tester.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • check_data_file_clashes: Package kernel-devicetrees wants to install file /boot/omap2420-h4.dtb
    But that file is already provided by package * kernel-image-3.8.8
  • pkg_run_script: package “bonescript” postinst script returned status 1.
  • opkg_configure: bonescript.postinst returned 1.

and the machine do not reboot again… Grrr !

Hope this will soon stabilize to a solid system …

Jacques

2

Once again, no reboot after opkg upgrade

My BBB was working fine in 3.8.8, but I had a problem in installing easy_install. As I saw that the kernel has
already upgraded to 3.8.11, I tried again the upgrade through opkg update and opkg upgrade.

Things went fine, but maybe I did an error in asking for opkg upgrade again.

On a system running software from before the 05.02 image, use --force-overwrite when opkg upgrading. The issue has been fixed from there one, but the is no way to provide a clean upgrade path for it. So .05.02 and onwards: opkg upgrade works without problems (minus bonescript, Jason is on that), for earlier you need --force-overwrite to drag in 3.8.11 and then everything is fine again (except bonescript, see above)

3

Finally everything is OK

With the SD card generated by

http://dominion.thruhere.net/koen/angstrom/beaglebone/BBB-eMMC-flasher-2013.05.02.img.xz

I could boot in 3.8.11 and
do
opkg update and opkg upgrade with no error and no messages after the second iteration.

Thanks !

Jacques

4

Hi,

How can I find out what image was installed on the BBB? For example, 2013-01-11 vs 2011-04-13 vs 2013-05-02?

Thanks,

Glen

5

try ‘uname -a’ which will give you the kernel version, and some idea on which release.
K

6

Hi Jacques,

I encountered the same problems updating/upgrading the bbb to 3.8.11. My bbb is sitting at #uboot. Guess it is in a non-recoverable state. There appears no image. Can access via USB/TLL cable though, from an ubuntu desktop (putty from Win7 doesn’t work).

From what I’m reading here, the only path to getting the bbb working again is:

  1. install on mSD card, say the, 05/03:

http://dominion.thruhere.net/koen/angstrom/beaglebone/?C=M;O=D

  1. then flash the eMMC with that 05/03 image.

Is this whole process (or reviving a dead bbb) documented somewhere… Can’t seem to find it.

Thanks.
/venkat

7

I posted what I did in a different thread.
http://beagleboard.org/Community/Forums?utm_expid=6702460-6&utm_referrer=http%3A%2F%2Fbeagleboard.org%2FSupport%2FHardware%20Support

I am not sure which version of the firmware that is on my mSD card, but when I am sitting in the boot menu I was able to tell the boot system to use an image that was up in my boot directory. like: uImage-3.8.8 and then boot, and then once the system was up, do another opkg with the force… of the current image (in my case 11) and then it has booted up fine.

Note: I use putty just fine from my Windows 7 machine to the FTDI cable… I now have it as one of my Saved Sessions of Putty.
To do it, needed to change Connection type to Serial, then type in the Serial line of the FTDI cable. In my case COM49 and enter the Speeed of 115200.

Kurt