How to install a new Kernel (Debian)

Hi all,

since the kernel that comes with the Debian image from armhf doesn’t support midi I decided to try to build my own (first time.)

I used the instructions from here

http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Upgradedistro"device-tree-compiler"package

to build a kernel that includes the snd-seq modules. After a few hickups and a lot of waiting (I built on the BBB) I have now a deploy directory with the following files:

3.8.13-bone24.1.config
3.8.13-bone24.1-firmware.tar.gz
3.8.13-bone24.1.zImage
3.8.13-bone24.1-dtbs.tar.gz
3.8.13-bone24.1-modules.tar.gz

Newbie that I am, I tried at first to just copy the missing modules to /lib/modules/3.8.13-bone20 only to find out that this doesn’t work, because the modules only work with the specific kernel version they were built with.

So, now I’m ready to try to install the new kernel and of course (newbie that I am) I’m afraid I’ll brick my BBB. That’s why I ask:

What’s the best / safest way to try this new kernel without losing the old one? I’ve often heard that people have more than one kernel installed from which they choose one on boot. Is this possible with UBoot? And if yes, how?

(I know there’s an install_kernel.sh script in my linux-dev folder but it seems to assume that I built on a seperate computer and want to put the kernel on an sd card. I’d like to do it by hand.)

My naive guess at the moment would be to just untar and put

3.8.13-bone24.1-modules.tar.gz into /lib/modules

3.8.13-bone24.1.config, 3.8.13-bone24.1-dtbs.tar.gz and 3.8.13-bone24.1.zImage into /boot (after backing up the originals)

and 3.8.13-bone24.1-firmware.tar.gz into /lib (again after backing up the current firmware folder)

I’d also change the zImage link in /boot to my new kernel image.

Does this have a chance to work? Do I have to configure anything else?

If this doesn’t work I would like to at least be able to boot into Angstrom, mount my sd card and redo my changes.

Thanks a lot in advance,
Axel

Why dont you just follow the instructions provided by Robert on the link you pasted a link to ?

Hi all,

since the kernel that comes with the Debian image from armhf doesn't support
midi I decided to try to build my own (first time.)

I used the instructions from here

http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Upgradedistro"device-tree-compiler"package

to build a kernel that includes the snd-seq modules. After a few hickups and
a lot of waiting (I built on the BBB) I have now a deploy directory with the
following files:

3.8.13-bone24.1.config
3.8.13-bone24.1-firmware.tar.gz
3.8.13-bone24.1.zImage
3.8.13-bone24.1-dtbs.tar.gz
3.8.13-bone24.1-modules.tar.gz

Newbie that I am, I tried at first to just copy the missing modules to
/lib/modules/3.8.13-bone20 only to find out that this doesn't work, because
the modules only work with the specific kernel version they were built with.

So, now I'm ready to try to install the new kernel and of course (newbie
that I am) I'm afraid I'll brick my BBB. That's why I ask:

What's the best / safest way to try this new kernel without losing the old
one? I've often heard that people have more than one kernel installed from
which they choose one on boot. Is this possible with UBoot? And if yes, how?

(I know there's an install_kernel.sh script in my linux-dev folder but it
seems to assume that I built on a seperate computer and want to put the
kernel on an sd card. I'd like to do it by hand.)

Yeah, i haven't tweaked it yet for "native" installs... So don't run
it native yet..

My naive guess at the moment would be to just untar and put

3.8.13-bone24.1-modules.tar.gz into /lib/modules

this creates a new directory (3.8.13-bone24.1), so no worries on
breaking your old one..

3.8.13-bone24.1.config, 3.8.13-bone24.1-dtbs.tar.gz and
3.8.13-bone24.1.zImage into /boot (after backing up the originals)

and 3.8.13-bone24.1-firmware.tar.gz into /lib (again after backing up the
current firmware folder)

I'd also change the zImage link in /boot to my new kernel image.

mv zImage zImage_back
cp new_zImage zImage

Does this have a chance to work? Do I have to configure anything else?

If this doesn't work I would like to at least be able to boot into Angstrom,
mount my sd card and redo my changes.

Or just "re-flash" with the Angstrom image? Over kill, but it would "undo" it..

Regards,