LinuxQuestions.org - hummingboard : selecting kernel after upgrade

- Slackware - ARM (https://www.linuxquestions.org/questions/slackware-arm-108/)

- - hummingboard : selecting kernel after upgrade (https://www.linuxquestions.org/questions/slackware-arm-108/hummingboard-selecting-kernel-after-upgrade-4175618254/)

hummingboard : selecting kernel after upgrade

Dear all,

I have a cubox (hummingboard) running Slackware 14.2.
The kernel as been recently upgraded (to 4.13.5) using slackpkg current but I just realized that it still booting on the original one (3.14.14).
I'm not an expert in kernel, especially on arms.
That;d be wonderful with you could help me one this matter.
Here are some info you may need:

Code:

uname -a

Linux sanguo 3.14.14-armv7 #19 SMP Sun Mar 15 19:02:55 GMT 2015 armv7l Freescale i.MX6 Quad/DualLite (Device Tree) GNU/Linux

Code:

ls -ltr /boot/

total 39556

-rw------- 1 root root      309 Jan  1  1980 uEnv.txt

-rw------- 1 root root    34097 Mar  8  2015 imx6q-hummingboard.dtb

-rw------- 1 root root    33568 Mar  8  2015 imx6q-cubox-i.dtb

-rw------- 1 root root    32624 Mar  8  2015 imx6dl-hummingboard.dtb

-rw------- 1 root root    32095 Mar  8  2015 imx6dl-cubox-i.dtb

-rw------- 1 root root  5992680 Mar 15  2015 zImage

-rw------- 1 root root    5120 Mar 15  2015 README

-rw------- 1 root root    2530 Sep 26  2016 README-kernels.txt

-rw------- 1 root root  4500640 Oct  6 15:37 zImage-armv7-4.13.5

-rw------- 1 root root 11168364 Oct  6 15:37 uinitrd-armv7-4.13.5

-rw------- 1 root root  4500704 Oct  6 15:37 uImage-armv7-4.13.5

-rw------- 1 root root 11168300 Oct  6 15:37 initrd-armv7-4.13.5

-rw------- 1 root root  205654 Oct  6 15:37 config-armv7-4.13.5

-rw------- 1 root root  2757600 Oct  6 15:37 System.map-armv7-4.13.5

drwx------ 2 root root    55296 Oct  6 15:41 dtb-4.13.5

Code:

ls -ltr /usr/src/

total 12

drwxrwxr-x 24 root root 4096 Jan 11  2016 linux-4.4

drwxr-xr-x  3 root root 4096 Sep 19  2016 linux-4.7.2

drwxr-xr-x 24 root root 4096 Oct  6 13:47 linux-4.13.5

lrwxrwxrwx  1 root root  12 Oct  8 20:12 linux -> linux-4.13.5

Code:

ls -l /lib/modules/

total 8

drwxr-xr-x 3 root root 4096 Nov 23 22:29 3.14.14-armv7

drwxr-xr-x 3 root root 4096 Oct  8 19:38 4.13.5-armv7

How can I actually boot using kernel 4.13.5 ?

Thank you.

Quote:

Originally Posted by aihaike (Post 5784426)

The kernel as been recently upgraded (to 4.13.5) using slackpkg current but I just realized that it still booting on the original one (3.14.14).

The Hummingboard isn't officially supported, and the Kernel shipped with 14.2 was the 4.4 series (the version in patches is 4.4.92).
You shouldn't use packages from -current within 14.2 - they aren't compatible.

Presumably the official kernel in 14.2 didn't support the Hummingboard, so the Kernel you're running must be somebody's from the community perhaps? Have a look at the instructions you followed initially and see if there's a Kernel update there.

Quote:

Originally Posted by aihaike (Post 5784426)

Dear all,

I have a cubox (hummingboard) running Slackware 14.2.
The kernel as been recently upgraded (to 4.13.5) using slackpkg current but I just realized that it still booting on the original one (3.14.14).

How can I actually boot using kernel 4.13.5 ?

Thank you.

hi aihaike,

I'm guessing by the kernel version(s) you're dealing with you've initially used SolidRun's Ignition installer tool or you've visited humbo.fatdog.eu at some point in order to install Slackware ARM on the Cubox. "The latest HumBo installer was released on Sunday 15th March 2015 and uses kernel 3.14.14-armv7." The Ignition installer tool uses the same installer image that FatDog.eu provides. Or used to, at least. The HumBo installer is for Slackware ARM 14.2 and not Slackware ARM -current. What Mozes said, "You shouldn't use packages from -current within 14.2 - they aren't compatible." is very important! You're in for a world of pain if you attempt to mix and match -current (hard float port) and 14.2 (soft float port) packages.

Slackware, being the wonderful and highly configurable system that it is, allows you to achieve results in many different ways. But (un)fortunately, there's no 'rpi-update' for the Hummingboard/Cubox to make it easy when upgrading the kernel. So, a back-to-basics approach is required. It means you're going to learn something other than where to point and click or which 'apt-get -y install' type command to use.

You've used 'slackpkg' to upgrade the kernel. I've never done this. On Slackware ARM I've always done it by the old-school method and compiled my own kernel(s).

Is the HumBo project on FatDog.eu going to be updated? In a word, "No." Or at least not by me. Back in 2014/2015 when I worked on this project there was fantastic support from SolidRun. Their technical director is a fan of Slackware (it was the first Linux distro he'd used) and he wanted Slackware ARM to be included in the list of available OS for the Hummingboard. Since then, although SolidRun are still keen to promote Slackware, there has been no interest or activity in the HumBo project from users or the community as a whole. When I say no interest, I mean zero/nada/zilch/nought. I bet /dev/null has more interest in it!

Anyway, unless somebody else has released an updated kernel, I suspect you're going to have to compile your own kernel in order to be successful. As a wiser man than I once said to me, "Time to roll your sleeves up and be prepared for some hard work!"

Exaga, drmozes,

Thank you so munch for you useful replies.
Yes, I use the the instructions from humbo.fatdog.eu.
It's pretty much clear now and I understand my mistake.
Thanks again.

Quote:

Originally Posted by aihaike (Post 5785377)

Exaga, drmozes,

Thank you so munch for you useful replies.
Yes, I use the the instructions from humbo.fatdog.eu.
It's pretty much clear now and I understand my mistake.
Thanks again.

Je vous en pris. :hattip: