Jump to content

Replace the kernel to the custom compiled kernel


Recommended Posts

Posted

First of all sorry for the newbie's question.

I compiled a kernel with custom configuration to use this instruction: https://docs.armbian.com/Developer-Guide_Build-Preparation/

OS: Ubuntu Bionic 18.04 x64

apt -y install git
git clone https://github.com/armbian/build
cd build
./compile.sh \
BOARD=orangepizero \
BRANCH=default \
BUILD_DESKTOP=no \
KERNEL_ONLY=yes \
KERNEL_CONFIGURE=yes

After the kernel build is complete, the output directory contains

output/config
linux-sun8i-default.config
output/debs
/extra
armbian-config_5.99_all.deb
armbian-firmware-full_5.99_all.deb
armbian-firmware_5.99_all.deb
linux-headers-sun8i_5.99_armhf.deb
linux-image-sun8i_5.99_armhf.deb
linux-source-default-sun8i_5.99_all.deb
linux-u-boot-orangepizero_5.99_armhf.deb

Copied to the device this files

linux-headers-sun8i_5.99_armhf.deb
linux-image-sun8i_5.99_armhf.deb

Executed

sudo dpkg -i linux-headers-sun8i_5.99_armhf.deb
sudo dpkg -i linux-image-sun8i_5.99_armhf.deb

The kernel hasn't changed.

Could you explain how to replace the kernel on the device, please?
Thank you very much for your reply.

Posted

That is correct procedure.

 

17 minutes ago, Qwalcon said:

The kernel hasn't changed.

 

Have you reboot? Version is the same anyway. Did you check build date ... what have you changed?  

Posted
4 hours ago, Igor said:

what have you changed?

I tried to compile kernel with following configuration: https://criu.org/Linux_kernel

General setup options
CONFIG_CHECKPOINT_RESTORE=y (Checkpoint/restore support)

Networking support -> Networking options options for sock-diag subsystem

 

CONFIG_UNIX_DIAG=y (Unix domain sockets -> UNIX: socket monitoring interface)
CONFIG_INET_DIAG=y (TCP/IP networking -> INET: socket monitoring interface)
CONFIG_INET_UDP_DIAG=y (TCP/IP networking -> INET: socket monitoring interface -> UDP: socket monitoring interface)

CONFIG_NETFILTER_XT_MARK=y (Networking support -> Networking options -> Network packet filtering framework (Netfilter)   -> Core Netfilter Configuration -> Netfilter Xtables support (required for ip_tables)
  -> nfmark target and match support)
CONFIG_TUN=y (Device Driver -> Network device support -> Universal TUN/TAP device driver support)

Posted
7 hours ago, Qwalcon said:

BRANCH=default \


The problem might be here. Branch default is legacy kernel version 3.4.y which is EOL. Features which you need might not be supported and we are also officially ditching it next week.

 

NEXT is 4.19.y which will be upgraded to 5.3.y soon.

Posted
On 11/16/2019 at 11:39 PM, Igor said:

NEXT is 4.19.y which will be upgraded to 5.3.y soon.

Thank you very much for you answer.
I choose NEXT. The kernel was replaced.

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines