Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Upgrading kernel to 4.16.x and higher

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
Halaspa
Posts: 1
Joined: 2018-07-18 22:13

Upgrading kernel to 4.16.x and higher

#1 Post by Halaspa »

I have two laptops, HP2000 with an AMD E-300, HP Pavilion G6 with Intel i3. I've got a base Debian 9 load that came with 4.9 kernel. I've compiled kernel 4.14.56 on both. Have not been successful compiling 4.15 or greater on either. Attempted to compile 4.17.8 today on the G6. Failed during make deb-pkg.

Any thoughts on why anything higher than 4.14 kernels fail to compile?

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Upgrading kernel to 4.16.x and higher

#2 Post by Head_on_a_Stick »

Halaspa wrote:Failed during make deb-pkg
You should post the full output of the failed command.

Why are you not using the kernel version from backports?

https://packages.debian.org/stretch-bac ... mage-amd64
deadbang

Wheelerof4te
Posts: 1454
Joined: 2015-08-30 20:14

Re: Upgrading kernel to 4.16.x and higher

#3 Post by Wheelerof4te »

For the newer kernels, you need few additional packages, flex and bison. Maybe some other, read what warnings make gives you.

It would be best and the fastest to just install kernel from backports.

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Upgrading kernel to 4.16.x and higher

#4 Post by stevepusser »

Maybe the error messages thrown up by a failed build could possibly be of use to solve your groovy mystery? They help me solve FTBFS for quite a few backports that I do...Virtualbox 5.2.16 in the last ten minutes, for example.

I believe that newer kernels also need libelf-dev to compile. FWIW, I also have backported Debian 4.17.6 and Liquorix 4.17.6 based kernels in separate Stretch openSUSE build service repos.

https://build.opensuse.org/package/show ... linux-4.17

https://build.opensuse.org/package/show ... uorix-4.17
MX Linux packager and developer

User avatar
dotlj
Posts: 646
Joined: 2009-12-25 17:21

Re: Upgrading kernel to 4.16.x and higher

#5 Post by dotlj »

If you are running Stable with backports, you will see that 4.14, 4.15. 4.16 and 4.17 are available.
You can install any or all with no trouble.
4.14 runs nicely.
4.15 includes patches for Spectre and Meltdown but if you use VirtualBox, you won't be able to use VirtualBox because it requires an newer versions of other packages.
4.16 has lots of networking support and AMD GPU support if that helps you
4.17 improves security and performance

Code: Select all

aptitude search linux-image
c   linux-image-4.14.0-0.bpo.2-amd64            -                                                      
i   linux-image-4.14.0-0.bpo.3-amd64            - Linux 4.14 for 64-bit PCs                            
i   linux-image-4.15.0-0.bpo.2-amd64            - Linux 4.15 for 64-bit PCs                            
c   linux-image-4.16.0-0.bpo.1-amd64            -                                                      
p   linux-image-4.16.0-0.bpo.2-amd64            - Linux 4.16 for 64-bit PCs                            
p   linux-image-4.16.0-0.bpo.2-amd64-dbg        - Debug symbols for linux-image-4.16.0-0.bpo.2-amd64   
p   linux-image-4.16.0-0.bpo.2-cloud-amd64      - Linux 4.16 for x86-64 cloud                          
p   linux-image-4.16.0-0.bpo.2-cloud-amd64-dbg  - Debug symbols for linux-image-4.16.0-0.bpo.2-cloud-am
p   linux-image-4.16.0-0.bpo.2-rt-amd64         - Linux 4.16 for 64-bit PCs, PREEMPT_RT                
p   linux-image-4.16.0-0.bpo.2-rt-amd64-dbg     - Debug symbols for linux-image-4.16.0-0.bpo.2-rt-amd64
c   linux-image-4.16.0-2-amd64                  - Linux 4.16 for 64-bit PCs                            
p   linux-image-4.16.0-2-amd64-dbg              - Debug symbols for linux-image-4.16.0-2-amd64         
p   linux-image-4.16.0-2-cloud-amd64            - Linux 4.16 for x86-64 cloud                          
p   linux-image-4.16.0-2-cloud-amd64-dbg        - Debug symbols for linux-image-4.16.0-2-cloud-amd64   
p   linux-image-4.16.0-2-rt-amd64               - Linux 4.16 for 64-bit PCs, PREEMPT_RT                
p   linux-image-4.16.0-2-rt-amd64-dbg           - Debug symbols for linux-image-4.16.0-2-rt-amd64      
p   linux-image-4.17.0-1-amd64                  - Linux 4.17 for 64-bit PCs                            
p   linux-image-4.17.0-1-amd64-dbg              - Debug symbols for linux-image-4.17.0-1-amd64         
p   linux-image-4.17.0-1-cloud-amd64            - Linux 4.17 for x86-64 cloud                          
p   linux-image-4.17.0-1-cloud-amd64-dbg        - Debug symbols for linux-image-4.17.0-1-cloud-amd64 

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Upgrading kernel to 4.16.x and higher

#6 Post by stevepusser »

dotlj wrote:If you are running Stable with backports, you will see that 4.14, 4.15. 4.16 and 4.17 are available.
You can install any or all with no trouble.
4.14 runs nicely.
4.15 includes patches for Spectre and Meltdown but if you use VirtualBox, you won't be able to use VirtualBox because it requires an newer versions of other packages.
4.16 has lots of networking support and AMD GPU support if that helps you
4.17 improves security and performance

Code: Select all

aptitude search linux-image
c   linux-image-4.14.0-0.bpo.2-amd64            -                                                      
i   linux-image-4.14.0-0.bpo.3-amd64            - Linux 4.14 for 64-bit PCs                            
i   linux-image-4.15.0-0.bpo.2-amd64            - Linux 4.15 for 64-bit PCs                            
c   linux-image-4.16.0-0.bpo.1-amd64            -                                                      
p   linux-image-4.16.0-0.bpo.2-amd64            - Linux 4.16 for 64-bit PCs                            
p   linux-image-4.16.0-0.bpo.2-amd64-dbg        - Debug symbols for linux-image-4.16.0-0.bpo.2-amd64   
p   linux-image-4.16.0-0.bpo.2-cloud-amd64      - Linux 4.16 for x86-64 cloud                          
p   linux-image-4.16.0-0.bpo.2-cloud-amd64-dbg  - Debug symbols for linux-image-4.16.0-0.bpo.2-cloud-am
p   linux-image-4.16.0-0.bpo.2-rt-amd64         - Linux 4.16 for 64-bit PCs, PREEMPT_RT                
p   linux-image-4.16.0-0.bpo.2-rt-amd64-dbg     - Debug symbols for linux-image-4.16.0-0.bpo.2-rt-amd64
c   linux-image-4.16.0-2-amd64                  - Linux 4.16 for 64-bit PCs                            
p   linux-image-4.16.0-2-amd64-dbg              - Debug symbols for linux-image-4.16.0-2-amd64         
p   linux-image-4.16.0-2-cloud-amd64            - Linux 4.16 for x86-64 cloud                          
p   linux-image-4.16.0-2-cloud-amd64-dbg        - Debug symbols for linux-image-4.16.0-2-cloud-amd64   
p   linux-image-4.16.0-2-rt-amd64               - Linux 4.16 for 64-bit PCs, PREEMPT_RT                
p   linux-image-4.16.0-2-rt-amd64-dbg           - Debug symbols for linux-image-4.16.0-2-rt-amd64      
p   linux-image-4.17.0-1-amd64                  - Linux 4.17 for 64-bit PCs                            
p   linux-image-4.17.0-1-amd64-dbg              - Debug symbols for linux-image-4.17.0-1-amd64         
p   linux-image-4.17.0-1-cloud-amd64            - Linux 4.17 for x86-64 cloud                          
p   linux-image-4.17.0-1-cloud-amd64-dbg        - Debug symbols for linux-image-4.17.0-1-cloud-amd64 
FWIW, Virtual Box 5.2.14 and 5.2.16 build and work with 4.17 kernels on a Stretch base. Those are backported upstream Debian versions, not the packages from Oracle. The Oracle versions might work, but I haven't tested those.

I also remember that VBox requires libelf-dev to compile with newer kernels, so you should make sure to have that installed if the kernel headers don't pull that in.
MX Linux packager and developer

Post Reply