Linux kernel mainline git

Linux kernel mainline git

A continuation of the free version of ukuu.

This branch is not ahead of the upstream master.

No new commits yet. Enjoy your day!

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Ubuntu Mainline Kernel Installer

This is a tool for installing the latest mainline Linux kernel on Ubuntu-based distributions.

• Fetches list of available kernels from Ubuntu Mainline PPA
• Optionally watches and displays notifications when a new kernel update is available
• Downloads and installs packages automatically
• Display available and installed kernels conveniently
• Install/Uninstall kernels from gui
• For each kernel, the related packages (headers & modules) are installed or uninstalled at the same time

Downloads & Source Code

mainline is written using Vala and GTK3. Source code and binaries are available from the GitHub project page.

mainline is a fork of ukuu

The original author stopped maintaining the original GPL version of ukuu and switched to a paid license for future versions.

Enhancements / Deviations from the original author’s final GPL version

• (from stevenpowerd) Options controlling the internet connection check
• (from cloyce) Option to include or hide pre-release kernels
• Changed name from «ukuu» to «mainline»
• Removed all GRUB options
• Removed all donate buttons, links, dialogs
• Remove source cruft
• Better temp and cache directory behavior
• Better desktop notification behavior

• Make the notification bg process detect when the user logs off and exit itself.
• Save & restore window dimensions.
• Move the notification/dbus code into the app and make an «applet mode»

About

A continuation of the free version of ukuu.

Источник

Linux kernel mainline git

Bash script for Ubuntu (and derivatives as LinuxMint) to easily (un)install kernels from the Ubuntu Kernel PPA.

⚠️ Use this script at your own risk. Be aware that the kernels installed by this script are unsupported

🔓 Do not use this script if you don’t have to or don’t know what you are doing. You won’t be covered by any security guarantees. The intended purpose by Ubuntu for the mainline ppa kernels is for debugging issues.

ℹ️ We strongly advise to keep the default Ubuntu kernel installed as there is no safeguard that at least one kernel is installed on your system.

If you want to automatically check for a new kernel version when you login:

This script needs elevated privileges when installing or uninstalling kernels.

Either run this script with sudo or configure the path to sudo within the script to sudo automatically

Install latest version:

Uninstall a version from a list

• bash
• gnucoreutils
• dpkg
• wget (since 2018-12-14 as kernel ppa is now https only)

• libnotify-bin (to show notify bubble when new version is found)
• bsdmainutils (format output of -l, -r with column)
• gpg (to check the signature of the checksum file)
• sha1sum/sha256sum (to check the .deb checksums)
• sudo

• Support daily kernel builds (on hold until there is significant demand for this, PRs are also welcome)

About

Bash script for Ubuntu (and derivatives) to easily (un)install kernels from the Ubuntu Kernel PPA

Источник

Linux kernel mainline git

Makes it easy to install and check for new mainline kernels

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

This Updater was made to alert the user of update for mainline kernels and to make installing them noob/newbie friendly.
You can manually install the kernels from here without using this script.

If you think this looks long and complicated, it is just because I have listed 5 different ways you can download this project, based on your personal preferences. If you want a recommendation just use either Terminal Install or Recovery Console Install

Download the zip archive (there is a button near the top of the page) and extract it
Drag and drop the install file into a terminal window and press enter
If that does not work type «bash » then repeat the above step
It will look like bash ‘/path/to/install’
Type your login password when prompted

Step 2: Download (Method 1/5: Use git )

Step 2: Download (Method 2/5: Use wget to download a zip archive and extract it)

Step 2: Download (Method 3/5: Use curl to download a zip archive and extract it)

Step 2: Download (Method 4/5: Use wget to download a tar.gz archive and extract it)

Step 2: Download (Method 5/5: Use curl to download a tar.gz archive and extract it)

Step 3: Run the install script (If you used git for Step 2)

Step 3: Run the install script (If you did NOT use git for Step 2)

Step 4: Check for kernel update (If you would like a release candidate kernel remove -no-rc from this command)

Step 5: Install the new kernel (That is the reason you are here right?)

You can view the source code of that script if you like.

KernelUpdateChecker -f -r quantal -no-rc -v 3.5
This would force the script to generate a install script for the latest 3.5 kernel compiled for quantal that is not a release candidate even if you are running a newer kernel
-f forces the script to make a installer regardless of now new the current running kernel is
-l tells the script to use lowlatency kernels
-r quantal tells the script to use quantal kernels even if you are using raring (13.04) or precise (12.04), defaults to the output of lsb_release -cs
-no-rc tells the script to ignore release candidate kernels
-v 3.5 tells the script you only want a kernel with a version number starting with 3.5, you can use the entire kernel version number to force a exact version
-nh tells the script you only want a kernel without header packages (required by eg: virtualbox and nvidia’s drivers)
/tmp/kernel-update —silent will install the kernel without asking questions
/tmp/kernel-update —download-only will download the script, tell you were it downloaded it to, list the downloaded files, and exit
/tmp/kernel-update —uninstall will purge the kernel it would normally install from the system
If there is no update /tmp/kernel-update will exit without doing anything, keep in mind that /tmp/kernel-update does not exist until a little over 60 seconds after login
If the new kernel is detected as not installed it will exit with status 1, will exit normally if it did not try to install it
For help documentation, other options and alternative variants please use this command:
KernelUpdateChecker -h

These 2 commands will uninstall the Kernel Updater

Источник

Ubuntu Wiki

MainlineBuilds

Introduction

By default, Ubuntu systems run with the Ubuntu kernels provided by the Ubuntu repositories. However it is handy to be able to test with unmodified upstream kernels to help locate problems in Ubuntu kernel patches, or to confirm that upstream has fixed a specific issue. To this end we now offer select upstream kernel builds. These kernels are made from unmodified kernel source but using the Ubuntu kernel configuration files. These are then packaged as Ubuntu .deb files for simple installation, saving you the time of compiling kernels, and debugging build issues.

These kernels are not supported and are not appropriate for production use.

How do I install an upstream kernel?

Following these steps in order will help you successfully test an upstream kernel.

Prepare OS to install an upstream kernel

First, if one is using select proprietary or out-of-tree modules (e.g. bcmwl, fglrx, NVIDIA proprietary graphics drivers, VirtualBox, etc.) unless there is an extra package available for the version you are testing, you will need to uninstall the module first, in order to test the mainline kernel. If you do not uninstall these modules first, then the upstream kernel may fail to install, or boot.

Choose the proper upstream kernel files

The build directories are nicely organized into per architecture groups. For example, if one is using a 64-bit/amd64 architecture and wants the generic kernel version you would want those files marked A, from the appropriate group.
If you want the low latency version, B.

Download upstream kernel files from the Ubuntu archive

Few things can compromise the security of a Linux system worse than a compromised kernel

We urge you to carefully verify the integrity of any and all downloaded kernel packages as explained below.

The Mainline kernel archive has a directory for each tagged release version, with packages for the generic and lowlatency configurations inside.

Note: If you are testing to isolate a bug or regression, please do not use the daily folder. Instead, use the latest mainline kernel at the top from the link above.

Install all upstream kernel files

Execute the following command against each of the downloaded files in a terminal of your choosing:

If no errors show up, reboot while holding Shift then select «Advanced options for Ubuntu», then select and boot into the new entry that looks something like:

Problems installing upstream kernels

Virtualbox

Some errors that may occur while attempting to install an upstream kernel are the result of VirtualBox being installed. For example,

As per above, you need to either install the modules-extra package, if available, or uninstall VirtualBox.

Unsatisfied dependencies

A failure to install can also result from the installed version of Ubuntu lacking the newer packages the upstream kernel is dependent on for the install to succeed. For example,

If you already have the package referenced by the error message (in this instance, libssl1.1) installed but the version number is beneath the new kernel’s requirements, then you would first need to upgrade your Ubuntu installation to a newer release. However, if libssl1.1 is not installed at all, and the version that comes with your release is sufficient, then install libssl1.1.

Other install errors

If for some reason the kernel you attempted to build failed, and it’s not due to the above, then continue to test the next most recent kernel version until you can test to the issue.

Uninstalling upstream kernels

The upstream kernels have their own ABI namespace, so they install side by side with the stock Ubuntu kernels (each kernel has a separate directory under /lib/modules/VERSION for example). This means that you can keep several mainline and Ubuntu stock kernels installed at the same time and select the one you need from the GRUB boot menu.

If you want to uninstall an upstream kernel once your need for installing it has abated, execute the following to find the exact name of the kernel packages you need to uninstall:

and then execute the following to uninstall them:

Remember that several packages can belong to one kernel version; common headers plus the architecture specific headers, image and modules are to be expected at a minimum.

Mainline kernel build toolchain

These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 «Trusty Tahr» / 16.04 «Xenial Xerus» / 18.04 «Bionic Beaver», etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds.

Mainline kernel mapping to Ubuntu kernel

The Ubuntu kernel is not bit-for-bit the same as the mainline. However, one may find the upstream release that the Ubuntu kernel is based on via the Ubuntu to mainline mapping table.

Support (BEWARE: there is none)

The mainline kernel builds are produced for debugging purposes and therefore come with no support. Use them at your own risk.

Kernel source code trees

In each directory of the above-linked archive there is a file named COMMIT which defines the base commit in Linus Torvalds’ master tree from which they were built. The patches in the same directory . -* are applied on top of this commit to make the build tree. A mirror of Linus’ tree is available from git://kernel.ubuntu.com/virgin/linux.git.

First download the COMMIT and patch files . -* from the mainline build in question to a temporary directory:

Verifying mainline build binaries

To provide verification that the published builds are 1. built by the Ubuntu mainline build system, and 1. are bit-for-bit identical copies of the files on the server,

the individual files are checksummed and the results are published as a file named CHECKSUMS in the same directory. This file is in turn signed by the mainline builder using the GPG key below, which can be validated against its record from the Ubuntu Keyserver.

The verification can be done by running the following commands:

1. Import the above public key to your keyring (if you haven’t already done that):
2. Download the CHECKSUMS and CHECKSUMS.gpg files from the build directory and verify if the CHECKSUMS is signed with the above key:
3. Verify the checksums of downloaded deb files: You should get a line ending with «OK» for each of downloaded deb file and each type of checksums that are given in the CHECKSUMS file.

Upstream kernel details

We currently build five sets of upstream kernels. All formal tags from Linus’ tree and from the stable trees, plus:

the tip of the drm-next head of Dave Airlie’s linux repository daily,

the tip of the drm-intel-next head of Keith Packard’s linux repository daily until 2012, after which it has been taken over by Daniel Vetter at http://cgit.freedesktop.org/drm-intel/, and in particular, the drm-intel-next branch,
the tip of the master branch of the debloat-testing tree daily,

tags from the combined v2.6.32.x.y tree (by StefanBader) which is v2.6.32.x with DRM from 2.6.33.y.

This makes these kernels closer to the Lucid kernels which are based on 2.6.32 kernels with DRM backported from the 2.6.33 series.

The tagged releases (as made by Linus and the stable maintainers) are found under a directory matching their tag name and which kernel configuration they were built with ( — ).

Daily tip of the tree builds are found in the daily sub-directory named for the date they were made.

Each build directory contains the header and image .deb files for the generic flavour i386 and amd64 architectures, as well lowlatency.

Can I install and use a mainline kernel in a live environment?

No. One has two choices to use a mainline kernel:

1. Install the mainline kernel in an installed environment, restart, and choose this newly installed kernel.
2. Build a live environment with the new kernel in it. Given the amount of effort involved in doing this, it is easiest to use an installed OS to test the mainline kernel.

Kernel/MainlineBuilds (последним исправлял пользователь roguescholar 2020-03-26 22:30:32)

Источник