Package Details: linux-git 5.10rc2.r81.g4ef8451b3326-1

Git Clone URL: (read-only, click to copy)
Package Base: linux-git
Description: The Linux (Git) kernel and modules
Upstream URL:
Keywords: kernel linux
Licenses: GPL2
Replaces: wireguard-arch
Submitter: jonathanio
Maintainer: jonathanio
Last Packager: jonathanio
Votes: 7
Popularity: 0.152044
First Submitted: 2019-12-22 10:10
Last Updated: 2020-11-04 21:11

Required by (6)

Sources (2)

Pinned Comments

jonathanio commented on 2019-12-22 10:14

The last version of the linux-git package was disowned and deleted. I've restored it taken ownership, as I do make use of this package.

This package will automatically update it's version

Note: This is a -git package and the version will automatically update to the latest mainline commit when it is run, having pulled down the branch from the repository. It will normally only be updated between major versions in order to include any updated configuration for new modules and features or settings changes.

Latest Comments

1 2 3 4 5 Next › Last »

IOAOI commented on 2021-01-07 02:31

If you follow these instructions: and do makepkg -o then checkout an older version somehow and run makepkg -e there are errors as "version" is now wrong. In _package ():

  cd $_srcname
  make -s kernelrelease > version   <--- added
  local kernver="$(<version)"

this avoided those errors. (Only tested that on one build mind you.) Presumably the wiki info predates this commit about a year ago:

ArthurBorsboom commented on 2020-12-09 12:57

Kernel 5.10.0-rc7 can be build if you revert 1 commit; this is build issue upstream (see linux-next-git package comments).

git revert 3351b16af494 --no-edit

After the build of 5.10.0-rc7 and rebooting my system (AMD Renoir 4800U), it hangs with a black screen.

To fix this I had to use my running kernel config, which I found in /proc/config.gz

Could it be that the config in this package is not in line with the normal 'linux' package (outdated?) and needs fixing?

sickcodes commented on 2020-11-30 18:36

Thanks all!

I built 5.10rc6 fine and I am booted on Linux 5.10.0-rc6-1-git.

Used the config from /proc/config.gz

Also skipped making docs as I was getting Latex errors of some sort.

yay linux-git --getpkgbuild --force
cd linux-git

# remove html docs
sed -i -e 's/\"\$pkgbase-docs\"//' PKGBUILD
sed -i -e 's/rm\ -r\ \"\$builddir\/Documentation\"//' PKGBUILD
sed -i -e 's/make\ htmldocs//' PKGBUILD
sed -i -e 's/make\ /make\ -j'${N}'\ /g' PKGBUILD
sed -i -e 's/^pkgver\=.*/pkgver\='${RC}'/' PKGBUILD

# use old config
zcat /proc/config.gz > config

makepkg -si

sickcodes commented on 2020-11-30 12:42

@iamazat & @jonathanio thank you for that amazing tip. I've massively increased the job, having lived in slow lane for over a year now. Have added loglevel, will let you know. Also I moved the markdown to a gist as it was bloating this comments section. Will test higher rc, thanks @sandy8925, and will post logs, brb!

jonathanio commented on 2020-11-30 12:37

@iamazat @sickcodes if you're using makepkg, you can set MAKEFLAGS in your /etc/makepkg.conf (along with any other relevant flags you want) and it will apply to all builds, not just the current build or checkout! :)

jonathanio commented on 2020-11-30 12:35

@sickcodes, further to @sandy8925, look for the following at the end of your build:

==> Finished making: linux-git 5.10rc6.r0.gb65054597872-1 (Mon 30 Nov 2020 06:45:15 GMT)

This tells you what your true build version is, as the version will automatically update to the latest commit on the master branch every time it is built.

jonathanio commented on 2020-11-30 12:31

@sickcodes I'd suggest adding loglevel to your kernel parameters and setting it to 4 or above. I think the default is 3 IIRC. Probably 6 or 7 would be best.

Hopefully, that'll give you more information during the boot process as to what if failing, or pausing, and maybe why. I do test it on my own laptop, and it is capable of booting, while the current config is based on Arch Linux 5.9 kernel, with a few extra options set for the 5.10 release.

sandy8925 commented on 2020-11-30 12:30

@sickcodes - Sometimes failure to boot is due to upstream code having a bug. Try building a newer or older commit/RC and see if that helps. Usually they fix it up in a later RC and before stable release.

iamazat commented on 2020-11-30 12:18

Super fast build:

MAKEFLAGS=-j$(( $(getconf _NPROCESSORS_ONLN)*2 )) make

sickcodes commented on 2020-11-30 12:15

Any tips on getting this to boot?

It rc2 seems to hang on boot.

Closest I got was to the root recovery shell.

Tried all of these from rEFInd boot loader as well as super grub disk EFI USB boot: