Thanks Robert, upgrading to a new image is a really big deal as I have so many apts and pips installed; the last time I did it, I think I lost a week although hopefully I'm better at it now. Probably the best way will be to purchase a new BBB and do the upgrade on it so I still have a working board to continue with in case real problems occur. Re updating the kernel, I think if I make the changes:

#if [ ! "x${test_rcnee}" = "x" ] ; then
to
if [ "x${test_rcnee}" = "x" ] ; then

then the else clause will be triggered. Alternatively, I guess I could comment out your repos from /etc/apt/sources.list and just leave the upgrade shell file as it is? Thanks again.
-Ken
p.s. would you recommend removing your repos from /etc/apt/sources.list?
On 15-09-21 05:08 PM, Robert Nelson wrote:
On Mon, Sep 21, 2015 at 3:50 PM, Bit Pusher <[email protected]> wrote:
Thanks Robert, I did the recommended upgrade to bone 76, but after the
upgrade and running uname -a, it still states bone 70.

The following NEW packages will be installed:
   linux-image-3.8.13-bone77
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 17.6 MB of archives.
After this operation, 41.2 MB of additional disk space will be used.
Get:1 http://repos.rcn-ee.com/debian/ wheezy/main linux-image-3.8.13-bone77
armhf 1wheezy [17.6 MB]
Fetched 17.6 MB in 1min 6s (263 kB/s)
Selecting previously unselected package linux-image-3.8.13-bone77.
(Reading database ... 121773 files and directories currently installed.)
Unpacking linux-image-3.8.13-bone77 (from
.../linux-image-3.8.13-bone77_1wheezy_armhf.deb) ...
Setting up linux-image-3.8.13-bone77 (1wheezy) ...
update-initramfs: Generating /boot/initrd.img-3.8.13-bone77
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
   mt7601u-modules-3.8.13-bone77
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 307 kB of archives.
After this operation, 612 kB of additional disk space will be used.
Get:1 http://repos.rcn-ee.com/debian/ wheezy/main
mt7601u-modules-3.8.13-bone77 armhf 1wheezy [307 kB]
Fetched 307 kB in 1s (159 kB/s)
Selecting previously unselected package mt7601u-modules-3.8.13-bone77.
(Reading database ... 123366 files and directories currently installed.)
Unpacking mt7601u-modules-3.8.13-bone77 (from
.../mt7601u-modules-3.8.13-bone77_1wheezy_armhf.deb) ...
Setting up mt7601u-modules-3.8.13-bone77 (1wheezy) ...
update-initramfs: Generating /boot/initrd.img-3.8.13-bone77
sudo reboot
Broadcast message from root@BBB3 (pts/0) (Mon Sep 21 16:15:33 2015):

The system is going down for reboot NOW!
logout
Connection to beaglew closed.

ssh martin@beaglew
Debian GNU/Linux 7

BeagleBoard.org BeagleBone Debian Image 2014-04-23
Ah that's why ^^, you are running 2014-04-23 and have the my repo enabled.

update_kernel assumes if the repo is enabled, simply install the
"linux-image-*.deb" is enough to update the boot script..

for "2014-04-23" you want to run these two commands in the else section:

https://github.com/RobertCNelson/boot-scripts/blob/master/tools/update_kernel.sh#L470-L471

So nuke the rest of that 'if' block, then it'll then work for you..

BTW/Warning, upgrading to v3.14.x is going to cause you bigger issues
with "2014-04-23" as the values we use for u-boot in the location of
the dtb (at the time of 2014-04-23) and v3.14.x 'fat' dtb's cause them
to over write the kernel location in memory.  So the board will
hardlock after u-boot jumps to the kernel..

The safe bet for to look at updating to the 2015-07-28 image: (it's
also wheezy and 3.8.x)

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-07-28

as it's just the natural progression of rolling updates from 2014-04-23 image..

Regards,


--
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/d/optout.

Reply via email to