Package Details: linux-fsync-nobara-bin 6.8.7-1

Git Clone URL: https://aur.archlinux.org/linux-fsync-nobara-bin.git (read-only, click to copy)
Package Base: linux-fsync-nobara-bin
Description: The Linux kernel and modules of Nobara Project - Prebuilt version
Upstream URL: https://nobaraproject.org
Licenses: GPL2
Provides: KSMBD-MODULE, NTFS3-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Submitter: figue
Maintainer: figue
Last Packager: figue
Votes: 9
Popularity: 0.87
First Submitted: 2022-11-15 19:21 (UTC)
Last Updated: 2024-04-19 22:42 (UTC)

Dependencies (5)

Required by (5)

Sources (6)

Latest Comments

1 2 3 4 Next › Last »

LukeShortCloud commented on 2024-04-03 15:52 (UTC)

@figue You are right, thanks for the clarification. I guess the header files are coming from kernel-devel then. My DKMS modules are building fine.

figue commented on 2024-04-02 22:30 (UTC)

@LukeShortCloud headers are included, and dkms modules should build fine.

LukeShortCloud commented on 2024-04-02 22:12 (UTC) (edited on 2024-04-02 22:13 (UTC) by LukeShortCloud)

Somewhat related to an earlier comment, can kernel-headers be included? That should help out with DKMS modules. The package is available at: https://download.copr.fedorainfracloud.org/results/sentry/kernel-fsync/fedora-${fedora}-x86_64/${l_build_id}-kernel/kernel-headers-${pkgver}-${extras}.x86_64.rpm

Hkntai commented on 2024-01-23 19:45 (UTC)

After wiping yay's cache it works! Amazing work

figue commented on 2024-01-23 17:56 (UTC)

@Hkntai I think I've figured out why... I've pushed 595ffe9bb5f8 a fix. Can you refresh your local repo and rebuild?

Hkntai commented on 2024-01-23 01:46 (UTC) (edited on 2024-01-23 01:47 (UTC) by Hkntai)

It seems that this package somehow doesnt trigger the dkms hooks to auto rebuild the dkms modules. This causes the issue that the modules have to be manually installed every update. This might have to do with the fact that the hooks only activates whenever the headers packages are updated on normal kernels

orlfman commented on 2023-12-28 17:38 (UTC)

does this one use the new EEVDF scheduler?

nadanke commented on 2023-12-10 11:19 (UTC)

@Mithras: if you do gpg --locate-keys torvalds@kernel.org it works

Mithras commented on 2023-10-21 03:15 (UTC) (edited on 2023-10-21 03:19 (UTC) by Mithras)

Well, for anybody else having this issue: https://unix.stackexchange.com/questions/696474 Essentially fedora is being fedora. You have to sign nvidia-dkms module if you want secure boot because fedora decided to ignore module.sig_enforce=0.

Mithras commented on 2023-10-20 04:43 (UTC) (edited on 2023-10-20 04:46 (UTC) by Mithras)

Can somebody confirm it works for nvidia-beta-dkms? It boots but doesn't load nvidia with "failed to insert module nvidia_uvm" for me.

No, I didn't forget to generate dkms:

$ dkms status
nvidia/545.23.06, 6.5.7-201.fsync.fc38.x86_64, x86_64: installed
nvidia/545.23.06, 6.5.7-arch1-1, x86_64: installed

No, no errors from dracut. Dracut log for linux is the exact same as for linux-fsync-nobara-bin.

No it's not related to secure boot (I build UKIs and sign the whole thing):

$ sudo sbctl verify
Verifying file database and EFI images in /efi...
✓ /efi/EFI/BOOT/BOOTX64.EFI is signed
✓ /efi/EFI/Linux/archlinux-linux-fsync-nobara-bin.efi is signed
✓ /efi/EFI/Linux/archlinux-linux.efi is signed
✓ /efi/EFI/systemd/systemd-bootx64.efi is signed