Package Base Details: linux-nitrous

Git Clone URL: https://aur.archlinux.org/linux-nitrous.git (read-only, click to copy)
Submitter: superboringdev
Maintainer: superboringdev
Last Packager: superboringdev
Votes: 6
Popularity: 0.57
First Submitted: 2019-11-05 16:41
Last Updated: 2020-08-04 19:27

Pinned Comments

superboringdev commented on 2020-03-23 19:25

Important: Starting today this repository will compile the kernel from source – the binary package is now available in a custom repository: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#linux-nitrous

From now on the prebuilt kernel will be built using clang 10 as clang 9 has some weird non-determinism as per https://github.com/ClangBuiltLinux/linux/issues/908

From now on, the linux-nitrous binary package can be installed by adding following lines to your /etc/pacman/pacman.conf:

[linux-nitrous]
Server = https://github.com/xdevs23/linux-nitrous/releases/latest/download/

Just install/update it using pacman.

You probably need to add my key before being able to install my packages:

sudo pacman-key --recv-keys E9C2DECAC962CB3AF1376D44148A9E3C9C3E3BF0
sudo pacman-key --lsign-key E9C2DECAC962CB3AF1376D44148A9E3C9C3E3BF0

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

superboringdev commented on 2020-04-03 07:05

@dedguy21 the nvidia driver does not appear to be compatible with Linux 5.6 (it is with an early version of 5.6-rc). Please try one of the following solutions/workarounds:

My workaround (don't do this if you don't know what you're doing, this might mess up future nvidia driver installation procedures and you should know how to revert that before continuing):

Download the latest NVIDIA Vulkan 1.2 Developer Beta (e. g. 440.66.08) and put it into some subdirectory, let's say ~/nvidia

Run following commands:

$ cd ~/nvidia
$ wget -O kernel-5.6.patch https://gitlab.com/snippets/1945940/raw
$ sh ./*.run -x
$ cd NVIDIA*
$ patch -p1 -i ../kernel-5.6.patch

now log out and switch to a tty using CTRL+ALT+F<n> (e. g. CTRL+ALT+F3) and log in there.

$ sudo systemctl disable --now gdm # replace gdm with your display manager, e. g. sddm, lightdm, whatever it is or stop it manually. this command will stop your display manager and log you out of all DM sessions

If you have nouveau installed, make sure it's disabled! If you have any other nvidia driver installed, uninstall them now.

Now reboot and you will be greeted with a TTY. Log in there and do the following:

$ cd ~/nvidia/NVIDIA*
$ ./nvidia-installer --dkms

Follow all the steps. It will probably fail but no reason to worry.

Make sure you have clang installed!

Now edit /var/lib/dkms/nvidia/440.66.08/source/dkms.conf and replace the corresponding line with this one:

MAKE[0]="'make' -j4 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=${kernelver} IGNORE_CC_MISMATCH=1 CC=clang HOSTCC=clang modules"

the crucial part is IGNORE_CC_MISMATCH=1 CC=clang HOSTCC=clang

Now run sudo pacman -S linux-nitrous-headers (or equivalent) to rebuild the DKMS modules. In case it fails again, make sure the dkms.conf file still has the changes and run the dkms command that pacman provides manually, for example:

sudo dkms install nvidia/440.66.08 -k 5.6.2-nitrous+

After this the driver is fully installed and you can enable your DM again, e. g.:

sudo systemctl enable gdm

Now reboot.

dedguy21 commented on 2020-04-03 06:56

I can use dkms for all my modules except nvidia-dkms always errors out.

vboxhost-dkms (works) acpi_call-dkms (works) bbswitch-dkms (works) Nvidia-dkms (fails)

It builds in other kernels (tested in Zen, LQX, Clear)

I saved a copy of my var logs to share but you probably can run a test and reproduce it fairly quickly.

superboringdev commented on 2020-03-26 06:50

@dedguy21 Thank you!

This package was previously a binary package. @eschwartz suggested that using a custom repository is a better way of doing this and thus I changed this one to one that compiles from source (as it should be) and created a custom repository. The cool thing is that if the package was already installed, once the repository is added to the pacman config, it will upgrade the previously installed package without any issues.

dedguy21 commented on 2020-03-26 02:41

I have to up vote this package.

I appreciate it that you provided a bin version, as it's a pain in the butt having to recompile a kernel after every update

superboringdev commented on 2020-03-23 20:21

Alright, I'll keep them in the custom repository then.

I didn't notice that there were .sig files in this git repository until you answered my question about redundancy. I simply overlooked it so thanks for pointing it out.

This is a really great community :)

eschwartz commented on 2020-03-23 20:18

They're extremely useful for the Pacman repository, since pacman -U https://.../<filename>.pkg.tar.xz will validate those to make sure the binary product is signed, and repo-add could in theory be changed in future to use detached signatures rather than storing the .sig files as base64'ed blobs inside the linux-nitrous.db file (that's a topic for the pacman-dev mailing list though).

It's just they're not very useful to the PKGBUILD which isn't doing anything with them. :D

superboringdev commented on 2020-03-23 20:10

Oh I'm sorry, I didn't notice that those were pushed as well, I just removed them and adjusted the .gitignore file accordingly. Sorry for that!

Should I keep uploading them to the repository itself though or are they redundant there as well?

eschwartz commented on 2020-03-23 20:07

They are redundant, and redundant things waste time and space and clutter up git log.

But also binary files don't compress well in git, and the AUR has checks to deny pushes of files that are above a certain limit... but allowing kernel .config and other moderate sized files is a balance we have to strike, so sometimes things sneak in, often by accident. We'd prefer to keep the server disk usage down where possible. Hence it would be greatly appreciated to prevent any more of these from getting uploaded.

Thanks!

superboringdev commented on 2020-03-23 19:55

@eschwartz I can remove them from the script I use to upload those files.

Is it bad that they are uploaded or are they just redundant? AFAIK they only contain the signature but since I don't have a lot of experience in these kind of things, I'm not too sure about it.

eschwartz commented on 2020-03-23 19:50

Hey -- you're accidentally committing .pkg.tar.xz.sig files to git. Can you please add this to your .gitignore?